Where: web portal, the map-file import. Needs: a configuration that already exists; any role can run the import.
When you finish: the file's poles and spans are objects in a job and you have checked the count.
No configuration yet? The import needs somewhere to put things. If you are an admin, Cloneable offers to build one from the file you just uploaded; see Build your configuration from a map file. If you are not, Cloneable tells you to ask an organization admin, and there is nothing else to do from this screen. If you just built a configuration from a file, Cloneable brings you here with it already selected.
The five steps
Upload file. Drop in your KML, KMZ or GeoJSON. Cloneable unpacks a KMZ. When it parses, it tells you how many points and lines it found. Read that number. If you expected two hundred poles and it found twenty, stop here.
The file parsed: 10 points and 9 lines found. Check that number, then choose Next.
Select Job. Use an existing job or create one. A new job needs a name and a configuration, and the wizard names which is missing. The new job is created as soon as you choose Next here, so if you stop after this step, an empty job stays in your list.
Create new job, with a Configuration and a Job name. The job is created when you choose Next.
Map Types. For every kind of feature in the file, say which template it becomes, or skip it. Every row starts on Skip import. These choices are for this import only and are not saved to your configuration. See the warning below.
Each type in the file, its object count, and the template it becomes.
Preview. Look it over.
Import. Choose Start import. Cloneable confirms it completed and how many objects it created.
Unmapped types are skipped, and skipping does not feel like deleting. Each row shows a count; a row reading seven objects means seven things will not exist if you leave it unmapped. The wizard stops you only if you mapped nothing at all. Work down the whole list.
Mapping each type to a template, row by row.
Check the result
Compare the objects created with the points and lines found at the start. Twenty points and twelve lines should give thirty-two objects. If the total is short, something was left unmapped or an object failed to save; the import log lists anything Cloneable could not create.
10 points and 9 lines gave 19 objects. View on map is ringed.
Take the offer to open the map and check that spans attached to poles rather than floating on their own. See How spans connect to poles.
If the import fails
Cloneable tells you when the whole run could not proceed. Go back through the steps: did the file parse, are the job and configuration set, are your types mapped. Do not start again with a new file.
Cloneable does not stop for a single object it could not create, so a run can report success and still have made fewer objects than expected. That is why the count is worth checking every time.
Related