v2.6.0
Summary
Launch Pad 2.6.0 adds boundary Shapefile download and boundary import endpoints and a path plan group listing. Route geometry in routing responses is now GeoJSON.
Breaking Changes
Route geometry is now GeoJSON
routePartGeometry on route parts returned by POST /api/routes/create and POST /api/routes/path-to-geometry is now a GeoJSON LineString instead of an array of [x, y] coordinate pairs. Read coordinates from the geometry object.
Before
"routePartGeometry": [[-113.9, 51.0], [-113.8, 51.0]]
After
"routePartGeometry": {
"type": "LineString",
"coordinates": [[-113.9, 51.0], [-113.8, 51.0]]
}
New Features
1. Boundary Shapefile Download
Download a boundary as a zipped Shapefile. Multi-part boundaries are supported and obstacle rings become holes.
| Method | Endpoint | Description |
|---|---|---|
| GET | /api/boundaries/{boundaryId}/shapefile |
Download a boundary as a zipped Shapefile |
2. Boundary Import for Existing Fields
Import a boundary onto an existing field from GeoJSON or WKT, or from a zipped Shapefile in WGS84. Both endpoints return BoundaryImportResponse; becameEffectiveActive tells you whether the import became the field's active boundary.
| Method | Endpoint | Description |
|---|---|---|
| POST | /api/fields/{fieldId}/boundary/import/geometry |
Import a boundary onto an existing field from GeoJSON or WKT |
| POST | /api/fields/{fieldId}/boundary/import/file |
Import a boundary onto an existing field from a zipped Shapefile (WGS84) |
| Property | Condition | Description |
|---|---|---|
becameEffectiveActive |
Both import endpoints | Whether the imported boundary became the field's active boundary |
3. Path Plan Group Plans
List the path plans in a group.
| Method | Endpoint | Description |
|---|---|---|
| GET | /api/path-plan-groups/{pathPlanGroupId}/path-plans |
List the path plans in a group |
Improvements
- Route job responses now include wheelTrafficArea and cumulative traffic area in routeStats for equipment with track and tire widths.
- Boundary parts may carry the new UnworkedInterior part type, used by logged data boundaries for unworked ground that is not an obstacle.
- Reported areas and lengths are now corrected for map-projection scale bias; values shift by up to 0.19%.
New Schemas
| Schema | Description |
|---|---|
BoundaryImportGeometryRequest |
Geometry payload for importing a boundary onto a field |
BoundaryImportResponse |
Result of a boundary import |
ReferenceLineCore |
Shared reference line schema |
Questions?
For questions about these API changes, please contact [email protected] or refer to the API documentation.