Remote Control App: Crash During Route Creation

Issue Description

Users may experience a critical failure when attempting to generate a flight route within the Remote Control app. The symptoms include:
    A field boundary is successfully created and uploaded via the Applicator View.
    The field data is synced/pushed to the Remote Control.
    Upon attempting to create an operational route, the Remote Control app stops responding (hangs) or crashes.


Root Cause

The crash is caused by invalid polygon geometry within the field boundary. Specifically, the system cannot currently process boundaries that contain internal segments that "bisect" the field.
If a boundary line crosses through the interior of the shape—effectively splitting one field into two or more connected sub-sections—the routing engine fails. The Ceres Air Remote Control App does not yet support multi-field route generation within a single boundary container.


Resolution

To resolve this, you must ensure the field boundary is a single, continuous, and enclosed shape with no internal overlapping lines or intersecting boundaries.

Recommended Actions

Choose one of the following methods to fix the boundary:
  • Simplify the Boundary: Edit the field in the Applicator View to remove any internal lines, ensuring there is only one outer perimeter.
  • Segment the Fields: If the area truly requires two distinct sections, delete the "bisecting" boundary and save them as two separate, independent field files.


Best Practices: Field Boundary Creation

To ensure the Remote Control App generates flight routes efficiently and without errors, follow these geometric guidelines when mapping fields in the Applicator View.

1. Maintain Geometric Integrity

The routing engine requires a "Simple Polygon." To avoid app crashes:
  • No Self-Intersection: Ensure boundary lines never cross over themselves (forming a "figure-8").
  • No Internal Bisecting Lines: Avoid drawing lines that cut through the middle of the field. The boundary should only represent the outer perimeter.
  • Closed Loops Only: Always ensure the start and end points are snapped together to create a fully enclosed shape.

2. Managing Complex Fields

If a single physical location has distinct sections (e.g., divided by a road, a wide treeline, or a fence):
  • Create Multiple Fields: Instead of one complex boundary, save them as "Field A" and "Field B."
  • Avoid "Neck" Connections: Do not connect two large areas with a very thin "neck" of pixels, as this can confuse the pathfinding algorithm.

3. Handling Obstacles (No-Spray Zones)

When dealing with internal obstacles like silos, power poles, or ponds:
  • Use the "Hole" or "No-Spray" Tool: If the software supports it, define these as internal exclusions rather than trying to wrap the main boundary around them in a single continuous line.
  • Buffer Zones: Always leave a small margin of error (buffer) between the boundary and physical hazards to account for GPS variance.

4. Optimize Node Density

  • Limit Points: Avoid creating hundreds of individual points for a straight edge. Use the minimum number of nodes required to define the shape. High node density can slow down the sync process between the Applicator View and the Remote Control.