Export a completed session
- Open History. Find the session by product, field, or date range, then tap it to open Session Details.
- Check the details. Review the field, product, application rate and water volume. Edit incorrect entries before exporting.
- Choose Export GeoJSON or Export KML. AgriPath creates the selected file and opens your phone's share sheet.
- Choose a destination. Available options depend on the apps installed on your phone. An email or cloud destination may need internet access.
- Open the received file. Confirm that the coverage appears in the expected location and that the recipient can access the session details.
You can also use Save & Export GeoJSON or Save & Export KML after tapping Finish Job. This saves the session to History before sharing. Cancelling the share sheet does not delete the saved session.
Choose a file format
| Format | Useful when | What AgriPath writes |
|---|---|---|
| GeoJSON | The recipient uses software that imports GeoJSON map data. | A FeatureCollection with a polygon for each recorded coverage segment and session details in its properties. |
| KML | The recipient uses Google Earth or another KML-compatible viewer. | Polygon placemarks with session details in ExtendedData. |
Both formats describe the same saved coverage. Neither includes satellite-image tiles. The receiving viewer supplies its own background map, and how it displays the extra session details varies by viewer.
What is included in the export
- Recorded spray-coverage polygons and the session identifier.
- Session start date and time, fixed boom width in feet, and total applied acres.
- Product, application rate, water volume in gallons, and field name/id when entered or assigned.
- An area-definition note explaining that totals include repeated passes and are not unique field area.
The field name identifies the assigned field; it does not add a separate field-boundary polygon to the session export. The export also does not include a weather snapshot, PDF report, or satellite image. Product and rate are the values entered by the user, not measurements from the sprayer.
If sharing fails or a file looks empty
A session must contain recorded spray coverage to export. A field boundary by itself is not a spray-session export. If the share destination fails, keep the saved session and try again from History. Use the offline guide to distinguish local file creation from delivery through an online service.
An export is a copy for review or sharing, not a full app backup. AgriPath does not currently import these files to restore its database. Clearing app storage or uninstalling can remove local records, so retain any exported copies you need separately.
Check the recipient's record requirements before relying on an export for reporting. Coverage inherits the limitations of phone GPS; a GPS record alone does not establish regulatory compliance.