v2.1.0
Summary
v2.1.0 adds new endpoints for routing to a target geometry, gives John Deere exports an opt-out for tramline reduction, exposes pre-validation notices on export jobs, and supports the {{FieldName}} placeholder in export naming templates.
New Features
1. Route to a Target Geometry
Generates a path from a starting position inside (or near) a field to a target Point or LineString using an existing route's path plan data. Reuses tracks, headland passes, swath width, and turn radius from the source plan, and handles headland traversal as needed. Coordinates must be in WGS84 (longitude, latitude).
| Method | Endpoint | Description |
|---|---|---|
| POST | /api/routes/path-to-geometry |
Build a path from a start position to a target Point or LineString |
Properties
| Property | Type | Description |
|---|---|---|
routeId |
Guid | Existing route whose path plan data is used as the source |
fieldStart |
double[] | [longitude, latitude] WGS84 starting position; does not have to be inside the boundary |
fieldStartAngle |
double? | Optional starting heading in degrees |
target |
Geometry | Target Point or LineString to route to |
useTracks |
bool | Whether tracks may be used as part of the generated path |
| Property | Condition | Description |
|---|---|---|
(body) |
200 OK | GeoJSON FeatureCollection of route parts from start to target |
2. Export Pre-Validation Notices
Export job responses now include warnings the UI can render before the user confirms a download or push. Notices cover boundary geometry counts that exceed monitor limits, mismatched boundaries across multiple plans for the same field, naming that will be truncated, missing data that was requested to be included, and any guidance-level warnings.
3. Skip Tramline Reduction for John Deere Exports
John Deere export options now accept a flag to skip the tramline reduction step. With reduction off, all geometries are exported as-is, which is needed for monitors that can handle more than 256 geometries. With reduction on (the default), the export behavior is unchanged.
4. {{FieldName}} Export Naming Template
Export naming templates now support the {{FieldName}} placeholder, in addition to the existing options. A handful of previously missing template values are now also populated correctly.
Improvements
- Repeated routing requests reuse cached node ordering when the inputs that affect it have not changed, giving faster turnaround when tweaking other settings.
- CN1 exports no longer fail intermittently due to an area calculation on the wrong geometry layer.
Questions?
For questions about these API changes, please contact [email protected] or refer to the API documentation.