Where: web portal, Export data on the job map, Export… in Edit multiple for part of a job, and Exports on the dashboard.
When you finish: you know the five export choices, how to export just part of a job, where to start each one, and how to check the file that came out.
The five export choices
Open the job on the map, then choose Export data on the left toolbar. It shows once a job is selected. The Choose export method window offers:
Choose export method, with all five options. Export to Katapult is greyed when the configuration has no Katapult export trigger.
Option | What you get | Pick it for |
Export to Katapult | All job data sent back into your Katapult system. Always the whole job | Katapult users. Needs your credential stored and the Katapult integration on in the configuration. |
Generate PDF Report | A report of selected poles and their measurements | People who want a document |
Export to KMZ | Map data for Google Earth or other GIS tools; can carry your field photos inside it | Mapping tools. With photos, expect a large file. |
Export to GeoJSON | Every point, span, line and polyline as one GeoJSON file | Mapping and analysis tools that prefer it |
Export to CSV (ZIP) | Poles, spans, measurements, custom points and lines, and guy wires as spreadsheets. Under Format, choose Separate files (ZIP) or Single combined CSV | Spreadsheets |
A KMZ export from Export data to the finished file.
Export to KMZ: its options, then Download (ringed).
Export to CSV: the Format choice, then Export CSV (ringed).
Your jobs list also has its own CSV download: one row per job, a summary rather than the field data. Its filename uses the universal (UTC) date, which may differ from your local date.
Job exports take the job's name by default, with spaces and punctuation turned into dashes, and you can rename before downloading.
If your organization sends data to Katapult or ArcGIS automatically, that is switched on per configuration and is separate from downloading a file. See Set up your configuration, stage by stage.
Export part of a job
For a phased project, or poles your crews collect as they come up, keep one job open for all of it and export just the part that is ready. Crews keep adding poles to the same job in the field.
Open the job on the map and choose Edit multiple.
Select the objects to export: click them on the map, or hold Shift and drag a box around them. You can also turn on Box select and drag without Shift, or pick search results from the search bar.
Choose Export…. The Choose export method window opens for your selection.
Pick Export to KMZ, Export to GeoJSON, Export to CSV (ZIP) or Generate PDF Report. Only the selected objects go into the file.
Export to Katapult is unavailable for a selection: Katapult always exports the whole job. Choose Clear in Edit multiple, then Export data, to send the job.
When the next part is ready, select it and export again. It is the same job and the same steps.
When the Katapult export asks about deleted items
If you deleted poles or lines in Cloneable that still exist in Katapult, Export to Katapult lists them and asks how to run:
Export only (the default): exports the job and leaves those records in Katapult.
Export and delete: removes those records from the Katapult job first, then exports. It asks you to confirm. Deleting in Katapult cannot be undone.
If a deleted pole still has lines attached, Katapult removes those lines when it deletes the pole. In Cloneable the lines stay.
Watch one run
Open Exports from your dashboard.
The status card shows an export in progress with a count, and a refresh button.
An in-flight job also shows on your dashboard with a relative time and offers to take you to the map.
Check it actually worked
The file arrived and is not suspiciously small. A tiny KMZ usually means photos were left out or the data was not there.
A finished KMZ export.
Open it once in whatever will consume it before you send it on.
The Exports view shows no issues for that job. See When an export does not finish.
Two things that look wrong and are not
You see | Why |
An export from last month is missing from the status card | The card covers the last seven days only. Older exports still happened. |
The summary counts and the issues list disagree | The summaries cover seven days; the issues list is not limited that way. Work from the list. |
Cloneable calls a failed export an issue, not an error, everywhere in the export views. It does not mean something less serious.
If the export link seems to do nothing, that is a different problem: My export link does not seem to do anything.
Related