DJI T100 Tutorial: How to Plot Multiple Fields and Program Flights

🇺🇸 U.S.A. FIRST — DJI Agras T100 Multi-Field Planning & Route Programming

Real agricultural drone jobs rarely consist of one perfectly rectangular field. Farms are often divided into several crop blocks separated by drainage ditches, windbreaks, access lanes, waterways, tree lines, or narrow strips of non-crop ground. When those fields need to be treated during the same operating window, the DJI Agras T100 can use Multiple Plots planning in Route Mode to organize individual blocks, connect accurate field boundaries, and—when appropriate—merge nearby plots into a more efficient operation.

This Ares Acres tutorial expands the DJI training workflow into a practical field-planning guide. It explains how to mark multiple field boundaries with the remote controller, account for windbreaks and ditches, close individual blocks, remove incorrect boundary lines, use Multitask, merge compatible fields, create non-application areas, and add missing obstacles before the aircraft executes the mission.

Ares Acres supports DJI Agras operators with aircraft, OEM parts, diagnostics, technical content, and field-operation resources. For T100 equipment and support, see the DJI Agras T100, DJI T100 Parts, DJI Agras Parts, DJI Accessories, the Ares Acres Product Catalog, or contact Ares Acres.

Prefer to watch instead of read? The video above demonstrates the core DJI workflow. This written guide adds the operational reasoning behind each step so that the route is not only created correctly in the controller, but also makes sense when the T100 reaches the field.

---

What You’ll Learn

• How to enter Multiple Plots planning in Route Mode.
• How to add boundary points using the handheld remote controller.
• Why points may need to be marked on both sides of windbreaks and ditches.
• How to exit continuous point marking.
• How to connect boundary points into closed field blocks.
• How to delete unnecessary boundary lines.
• How to save a multi-field plan.
• How Multitask relates to multi-field operations.
• When the Merge function can improve efficiency.
• How to interpret the source tutorial's approximately 20-meter merge guidance.
• How to generate a non-application area at a boundary.
• Why obstacles between merged plots still need to be planned.
• How to verify a route before flight.

Quick Answer: How Do You Plot Multiple Fields With the DJI Agras T100?

The most important concept is that Multiple Plots, Multitask, and Merge are not the same thing. Multiple Plots lets you plan more than one field. Multitask helps organize multiple planned blocks into a broader operation. Merge combines compatible neighboring blocks when doing so improves the mission. You do not need to merge every field just because the fields are close together.

Why Multiple-Field Planning Matters

Without a structured plan, fragmented farms can create unnecessary takeoffs, repeated setup, inefficient transitions, and confusion about where spraying or spreading should stop and restart. A multi-field route gives the operator a digital representation of the farm that can be reviewed before the T100 begins the mission.

Typical examples include:

• two neighboring corn fields separated by a ditch;
• small crop blocks divided by windbreaks;
• several irregular fields belonging to the same farm;
• adjacent fields planted with the same crop and using the same application plan;
• fields that should be worked in one operating sequence but should remain distinct blocks;
• small plots where repeated takeoff, landing, and route setup would waste time.

Multiple Plots vs. Multitask vs. Merge

Function	Purpose	Important limitation
Multiple Plots	Creates and stores several field blocks inside the planning workflow.	It does not automatically combine those fields.
Multitask	Allows multiple planned blocks/tasks to be selected as part of one broader operation.	It does not erase field boundaries by itself.
Merge	Combines selected neighboring plots when their geometry and operating requirements are compatible.	Nearby fields should not be merged automatically.
Non-Application Area	Defines a region where material should not be applied.	It does not replace accurate field boundaries, label restrictions, or obstacle planning.
Obstacle Planning	Represents hazards the planned route must account for.	Obstacle sensing and avoidance are assistance systems, not guarantees.

Before Planning: Walk or Inspect the Fields

Do not rely only on satellite imagery. A map can be outdated, and a field may contain hazards that are difficult to see from above. Before creating the mission, identify:

• the actual crop boundaries;
• drainage ditches and waterways;
• windbreaks and tree lines;
• utility poles and power lines;
• roads and access lanes;
• buildings and irrigation equipment;
• terrain changes;
• areas where application is prohibited or undesirable;
• possible takeoff and landing locations;
• safe transition routes between fields; and
• potential Return-to-Home paths.

Field planning should be paired with aircraft inspection. Before launch, use the DJI Agras T100/T50 Pre-Flight Safety Tutorial and verify the aircraft, payload system, batteries, propellers, landing gear, GNSS/RTK status, and operating area.

Step 1 — Enter Route Mode

From the DJI Agras operating interface, select Route Mode. Route Mode is the planned-field workflow used when the operator wants the aircraft to execute a structured route rather than manually flying each pass.

If you are new to this system, review the DJI Agras T100 Route Mode Field Planning & Task Execution Tutorial. That guide explains the broader Route Mode workflow, while this article focuses specifically on planning several field blocks.

Step 2 — Select Multiple Plots as the Operation Type

Inside Route Mode, select Multiple Plots as the operation type. This tells the controller that the job contains more than one field block.

At this stage, think in terms of real agricultural geometry. Your goal is not to make the map look visually clean. Your goal is to make the planned boundaries accurately represent where the T100 should and should not operate.

Step 3 — Click Add and Choose Add Points With Remote Controller

Click Add, then choose the option to add points using the remote controller.

The handheld controller becomes a positioning tool. The operator physically moves along the field boundary and records points in sequence. This is especially useful when the field edge is difficult to identify from satellite imagery or has changed since the map image was captured.

Step 4 — Mark Boundary Points in Sequence

Walk the field perimeter and mark points in order. Each point becomes part of the polygon that will define the operation block.

Good point placement should represent meaningful changes in the boundary. Straight field edges may require fewer points, while irregular curves, corners, terraces, waterways, or narrowing sections may require more.

Do not add points simply because you can. Too few points can oversimplify the geometry, while unnecessary points can make the plan harder to review. The objective is an accurate, readable boundary.

Step 5 — Mark Both Sides of Windbreaks or Ditches

The DJI training video specifically calls out windbreaks and ditches. When one of these features separates areas of the field, point marking may be required on both sides so the planner understands the physical separation.

This matters because a ditch or windbreak is not merely a line on the map. It may represent:

• a region where the aircraft should not apply material;
• a physical obstacle or terrain change;
• a separation between crop blocks;
• a transition zone the route should not cross casually;
• a legal, label, or agronomic buffer.

If the separation is operationally significant, represent it explicitly rather than assuming the aircraft will infer it.

Step 6 — Exit Continuous Point Marking

After you finish marking the required points, click a blank region of the planning interface to exit continuous point marking.

Stopping point entry before you begin connecting boundaries reduces accidental point placement and makes the next editing step easier.

Step 7 — Connect Boundary Points Into a Closed Block

Manually select two boundary points and connect them into a boundary line. Continue until the field polygon forms a closed block.

A closed block is important because the route planner needs a defined area inside which it can generate operation lines. An open boundary can create an ambiguous or invalid field geometry.

Field-Planning Check

Before moving to the next block, visually inspect the completed polygon:

• Does it follow the actual crop edge?
• Did it accidentally cross a ditch or windbreak?
• Does any line cut through a road or non-crop area?
• Is the field fully closed?
• Are all corners and narrow sections represented correctly?

Step 8 — Delete Unnecessary Boundary Lines

If a boundary line was created incorrectly, the tutorial shows that you can double click to delete the unnecessary line.

Use this to clean up planning mistakes before saving. Do not leave a questionable boundary in place simply because the controller accepts it. A planning error becomes an operational error once the mission is generated.

Step 9 — Repeat the Process for the Remaining Fields

Create each additional plot as its own closed block. At this stage, preserve the real separation between fields. Do not force neighboring plots into one shape before deciding whether a merge is actually appropriate.

When all individual fields are represented correctly, click Save and complete the initial planning process.

Step 10 — Turn on Multitask

For the merging workflow shown in the source tutorial, ensure Multitask is enabled.

Multitask is useful when the operator wants to work across several planned plots within a coordinated operation. This can reduce repetitive setup while preserving the ability to review the individual field blocks.

For interface orientation, see the DJI Agras T100/T50 Remote Operation View Tutorial.

Step 11 — Decide Whether Two Plots Should Be Merged

The DJI training video states that when multiple small plots are adjacent, within approximately 20 meters, and have consistent crop planting, the Merge function can be used to improve operational efficiency.

Good Merge Candidates

• Same crop.
• Same application product or material.
• Same target application rate.
• Similar operating altitude and speed requirements.
• Very small separation between the plots.
• No major obstacle or prohibited area between them.
• A logical transition can be created without crossing unsafe terrain or structures.

Poor Merge Candidates

• Different crops.
• Different chemicals, seeds, fertilizer, or application rates.
• A road, building, power line, tall windbreak, waterway, or other significant hazard between the fields.
• A boundary area that must remain untreated but has not been defined.
• A transition path that forces the aircraft into an undesirable location.
• Different legal or agronomic buffer requirements.

Step 12 — Select the Blocks and Click Merge

With Multitask enabled, select the field blocks that are candidates for a combined operation, then click Merge.

Do not confirm immediately. First review the geometry the controller proposes. The merged result should preserve the intended application area and should not accidentally convert the ground between the fields into an area that receives product.

Step 13 — Generate a Non-Application Area if the Boundary Should Not Be Treated

If the boundary region between the plots does not require application, the source tutorial shows that you can generate a non-application area at the boundary.

This is critical when the two crop blocks are close enough to merge operationally, but the ground between them should remain untreated.

Examples include:

• a grass strip;
• a narrow access lane;
• a drainage feature;
• a buffer area;
• a small patch of non-target vegetation;
• another region where label or agronomic restrictions prohibit application.

After the non-application area is generated, verify that it covers the intended region. Never assume the default geometry exactly matches the physical boundary.

Step 14 — Add Any Missing Obstacles Between Blocks

The DJI tutorial explicitly recommends supplementing obstacle planning when there are unplanned obstacles between blocks.

This is one of the most important steps in the entire process. Merging two fields changes how the planner may think about the mission, but it does not make trees, poles, ditches, buildings, or wires disappear.

Potential hazards between fields include:

• tree lines;
• windbreaks;
• utility poles;
• power lines;
• irrigation structures;
• buildings;
• fences;
• ditches;
• terrain rises;
• temporary equipment or vehicles.

Obstacle sensing and bypass functions can assist an operation, but they are not a substitute for correct route planning, field inspection, and operator supervision.

Step 15 — Confirm and Save the Plot

Once the merged geometry, non-application areas, and obstacle planning are correct, click Confirm and save the plot.

Saving the field is not the final safety check. Before flight, review the generated task and make sure the route lines and transitions make sense.

How to Review the Programmed Flight Before Launch

Before the T100 takes off, inspect the complete mission as if you were tracing the route manually. Ask:

• Where does the aircraft begin?
• Where does it end?
• What path will it use between plots?
• Does that path cross a road, ditch, tree line, pole, or building?
• Are all non-application areas represented?
• Do the field boundaries match the crop?
• Are application parameters correct for every block?
• Is the aircraft using a suitable heading and route direction?
• Does the Return-to-Home route remain safe?
• Is positioning quality acceptable?

If high-precision positioning is required for the operation, review the DJI Agras T100 D-RTK 3 Tutorial.

Decision Table: Keep Separate or Merge?

Condition	Likely better approach	Reason
Same crop, same product, same rate, small gap	Consider Merge	Can reduce repeated setup and improve route continuity.
Same crop but a ditch must remain untreated	Merge only with correct non-application planning	The transition area must not become an application zone.
Different crops or application rates	Keep separate	Different agronomic parameters create unnecessary risk.
Power line or tall windbreak between fields	Usually keep separate unless the route can be safely planned	Transition geometry may be more important than distance.
Fields are close but terrain is complex	Keep separate or plan carefully	Horizontal map distance does not describe vertical hazards.
Multiple small blocks on the same farm	Use Multiple Plots + Multitask	You can coordinate the job without forcing a merge.

Common Multi-Field Planning Mistakes

1. Merging Fields Only Because They Are Close

Distance is only one factor. Crop consistency, product, rate, obstacles, terrain, and transition routes matter.

2. Failing to Mark Both Sides of a Ditch or Windbreak

If a separation feature is operationally important, represent it clearly in the plan.

3. Leaving an Open Field Boundary

A field block should be properly closed before the mission is saved.

4. Treating Satellite Imagery as Ground Truth

Maps can be outdated or misaligned. Physical verification is still necessary.

5. Forgetting the Transition Route

A safe field can still produce an unsafe mission if the path between fields crosses a hazard.

6. Using a Non-Application Area as a Substitute for a Correct Boundary

Non-application areas are useful, but the underlying field geometry should still be accurate.

7. Assuming Obstacle Avoidance Guarantees Safety

Obstacle systems assist the pilot; they do not eliminate the need for route verification and supervision.

Troubleshooting Multi-Plot Planning

Problem	Possible cause	What to check
Field will not close correctly	Boundary points or lines were created out of sequence	Exit point marking, inspect the polygon, delete incorrect lines, then reconnect the correct points.
Merge produces an unwanted application area	Space between plots was included in the merged geometry	Create or adjust a non-application area before confirming.
Transition crosses a hazard	Obstacle or transition path was not included in planning	Add obstacle planning or keep the plots separate.
Field edge does not match reality	Map imagery is stale or inaccurate	Re-mark the boundary with the remote controller and physically verify the location.
Plots appear close but should not be merged	Different crop, rate, product, or hazard environment	Use Multiple Plots and Multitask without merging.
Route looks inefficient after saving	Field orientation or merge geometry may not suit the job	Reopen the planning workflow, review route direction and field grouping, and regenerate if needed.

Ares Acres Recommended Multi-Field Planning Workflow

1. Inspect all fields and transition areas physically.
2. Identify application and non-application regions.
3. Enter Route Mode and select Multiple Plots.
4. Mark each field independently with the remote controller.
5. Represent ditches and windbreaks accurately.
6. Close and verify every field block.
7. Save the individual plots.
8. Enable Multitask.
9. Select fields that share the same operational requirements.
10. Merge only when doing so clearly improves the mission.
11. Add non-application areas where the space between fields must remain untreated.
12. Add every relevant obstacle and inspect the transition route.
13. Review the generated flight path.
14. Verify positioning, aircraft health, payload, and battery status.
15. Launch only after the complete mission makes sense from takeoff through landing.

Related DJI Agras Operator Academy Tutorials

• DJI Agras T100 Route Mode Field Planning & Task Execution
• DJI Agras T100/T50 Remote Operation View Tutorial
• DJI Agras Remote Controller Activation Tutorial
• DJI Agras T100 D-RTK 3 Tutorial
• DJI Agras T100 A-B Operation Mode Tutorial
• DJI Agras T100 Manual & Manual Plus Tutorial
• The DJI T100 Spreading System Tutorial

FAQ: DJI T100 Multiple Fields & Route Programming

Can the DJI T100 plan more than one field in Route Mode?

Yes. The workflow shown in the source training video uses the Multiple Plots operation type so several field blocks can be planned and stored within the same broader planning process.

Do I need to merge every neighboring field?

No. Multiple Plots and Multitask can still be useful when the fields remain separate. Merge only when the fields are operationally compatible.

What does the approximately 20-meter rule mean?

The source DJI tutorial says adjacent small plots within approximately 20 meters with consistent crop planting can be candidates for merging. Treat that as workflow guidance, not as an automatic safety rule. Always evaluate obstacles, application parameters, terrain, and the transition route.

Why do I need to mark both sides of a ditch?

Because a ditch can represent a real separation between crop blocks or an area the aircraft should not treat or cross as part of a normal route.

What is a non-application area?

It is a planned region where the aircraft should not apply spray, seed, fertilizer, or other material. It can be especially useful when merged fields are separated by a narrow untreated strip.

Can a windbreak be treated as just a boundary line?

Not always. A windbreak may also be a physical obstacle. If it affects the route or transition between fields, it should be considered in obstacle planning as well.

What if there is an obstacle between two merged plots?

The source tutorial recommends supplementing the obstacle plan. Do not rely on the merge itself to account for a hazard that was never planned.

Should I trust satellite imagery for field boundaries?

Use it as a planning aid, not as unquestioned ground truth. Map imagery can be stale or offset. Remote-controller point marking and physical verification can improve accuracy.

Can I merge fields with different crops?

Generally, keeping them separate is more sensible because crop, product, rate, and application requirements may differ.

Does merging fields automatically improve efficiency?

Not always. A merge can reduce repetitive setup when fields are compatible, but it can also create an awkward transition or introduce non-target ground into the mission if used carelessly.

Should I inspect the transition path between fields?

Yes. The route between fields may contain hazards that do not exist inside either field polygon.

Does obstacle avoidance replace obstacle planning?

No. Obstacle sensing and bypass features are assistance systems. The operator remains responsible for field inspection, route planning, supervision, and compliance with applicable operating requirements.

What should I check before starting the programmed flight?

Confirm the field boundaries, non-application areas, route lines, transitions, obstacles, application parameters, positioning status, aircraft health, batteries, payload system, takeoff area, and Return-to-Home path.

Final Takeaway

The DJI Agras T100 Multiple Plots workflow is designed for the reality of fragmented agricultural land. The operator first creates accurate individual field blocks, then decides how those plots should be organized operationally. If neighboring fields share the same crop and application requirements and can be connected safely, Multitask and Merge can reduce unnecessary setup. If the space between fields should not receive material, create a non-application area. If hazards exist between plots, add them to the plan before flight.

The goal is not to create the largest possible merged field. The goal is to create the clearest, safest, and most operationally efficient digital representation of the farm.

---

What Is Ares Acres?

Ares Acres is a U.S.-based agricultural robotics company focused on DJI Agras aircraft, OEM parts, operator support, diagnostics, and technical education. Our growing DJI Agriculture Tutorials library is designed to help owners and operators understand the systems they use in the field—not simply purchase them.

Operational note: DJI Agras interface labels, menus, route-generation behavior, and available functions can vary by aircraft, controller, app version, firmware, payload, and region. Always verify the current aircraft interface and applicable DJI documentation before flight. Follow pesticide labels, local application rules, FAA requirements, airspace restrictions, and all other applicable operating requirements. Obstacle sensing, route planning, and RTK are assistance systems and do not eliminate the operator's responsibility to inspect and supervise the mission.