v2.5.0
September 2026
v2.4.0 → v2.5.0
Summary
Launch Pad 2.5.0 extends the logged data upload requests with boundary controls and returns per-plan logged data metrics.
New Features
1. Logged Data Boundary Controls (Preview)
New fields on the logged data upload and process-as-logged-data requests control how a boundary is generated from the file.
| Method | Endpoint | Description |
|---|---|---|
| POST | /api/companies/{companyId}/field-operations/file-upload |
Accepts forceHeadlandBoundary and isLoggedData |
| POST | /api/companies/{companyId}/user-files/{userFileId}/process-as-logged-data |
Accepts forceHeadlandBoundary and replaceBoundary |
Properties
| Property | Type | Description |
|---|---|---|
forceHeadlandBoundary |
boolean, nullable | On the field-operation file upload and the process-as-logged-data body: omit it to let the server detect the pass type, true to force headland-pass handling, false to suppress it. |
replaceBoundary |
boolean, nullable | On the process-as-logged-data body: let a reprocessed file take over the field's logged data boundary. The previous boundary is archived and, when it was the field's active boundary, the field is repointed at the replacement. |
isLoggedData |
boolean | On the file upload request, marking an upload as logged data. |
Improvements
- Path plan responses now include loggedDataMetrics for plans built from logged data: area processed, total distance, total and operational durations, speeds, and the source used to determine swath width. Plans returned by the field path-plan list carry these metrics too.
- Swath width for logged data now prefers the width declared in the archive metadata over values inferred from the recorded passes, and swathWidthSource reports which was used.
- Boundary responses now explain a requested boundary that did not arrive, through boundaryAbsent and boundaryAbsenceReason.
- Route requests with a machine that has no axles, or a track or tire width of zero, are now rejected with InvalidEquipmentData instead of returning a plan that ignored the wheels.
- POST /api/routes/create is now rate limited at 10 requests per 60 seconds; the 429 response and its headers are unchanged.
New Schemas
| Schema | Description |
|---|---|
LoggedDataMetrics |
Persisted metrics describing how a logged data path plan was produced |
Questions?
For questions about these API changes, please contact [email protected] or refer to the API documentation.