If you are not coming from Katapult, you can build your setup from a map file instead. This is what to have ready.
What to send us, and what we finalize
A map file places poles and spans. It does not decide what crews fill in.
Send us a workbook or a list that covers:
Pole fields
Span fields
Photos you need
Which of those are a dropdown, and which are free text
We treat that list as the contract for the build. You check it off with us on a call. Icons come later. The fields and photos matter more.
You do not upload this workbook into Cloneable. Send it to us. We build the configuration from it.
A map file, in one of three formats
Cloneable accepts KML, KMZ and GeoJSON. A KMZ is just a zipped KML, and Cloneable unpacks it for you.
There is a size limit. It is generous, and Cloneable will tell you plainly if your file is over it, so this is not worth measuring in advance. If you do hit it, the usual fix is to split the file by area rather than to try to compress it.
Coordinates that actually line up
This is the part worth checking before you upload rather than after.
Cloneable connects your spans to your poles by matching the coordinates at each end of a line to the position of a point. Where the endpoints line up, you get spans properly attached to poles. Where they are off by enough to miss, you get lines that connect to nothing.
Line ends drawn close to their poles are fine. It is ends a long way out, or in a different place entirely, that will cost you time. See How spans connect to poles.
Administrator access, and this one is a real block
Only organization administrators can create a configuration, and the page itself turns you away rather than simply keeping the option out of your menu. Without administrator access, Cloneable tells you that you do not have permission to create or edit configurations, before you get into the wizard at all.
That is deliberate: it is better for Cloneable to stop you at the door than to let you fill in five steps and refuse you at the end.
Two things follow:
Working for Cloneable is not a substitute. If someone from Cloneable helps you, they need administrator access in your organization.
Importing is less restricted than configuring. Once a configuration exists, someone who is not an administrator can bring a map file in as a job. What they cannot do is create the configuration in the first place. If they try, Cloneable tells them to ask an administrator, and there is nothing else they can do from there.
So if a configuration does not exist yet, an administrator has to go first.
Know which of the two jobs you are doing
They use the same kind of file and they are easy to confuse.
You want to | Do this |
Set up your organization from scratch, deciding what your poles and spans are | |
Bring a batch of infrastructure into a job, using a setup that already exists |
If you start out, you do both, in that order. Build the configuration first, and Cloneable carries you straight into the import with your new configuration already selected.
The short version
A KML, KMZ or GeoJSON file
Line endpoints that sit on your point coordinates
Administrator access in your Cloneable organization
A view on which of your file's feature types are poles, which are spans, and which you do not need
A workbook or list of fields, photos, and dropdown versus free text, checked off with us