Where: web portal, Settings, then Configurations, New Configuration, From a KML file. Needs: the Org Admin role.
When you finish: Cloneable has a configuration built from your map file and offers to load the same file as your first job.
Before you start
An Org Admin login. The page turns non-admins away before the wizard opens.
A KML, KMZ or GeoJSON file. A KMZ is a zipped KML and Cloneable unpacks it. If the file is too large Cloneable says so; split it by area rather than compressing it.
Line ends that sit on or near your poles. Cloneable attaches a span to a pole by matching the coordinates at the end of the line to the pole's position. See How spans connect to poles.
A view of which features in the file are poles, which are spans, and which you do not need.
Two jobs, same kind of file. This article builds the configuration (what your poles and spans are). Loading a batch of poles into a job you already have is Bring your map file in as a job. Starting out, you do both, in that order. The wizard also offers Map to an existing job instead in the top right for the second case.
The five steps
Step | What you do |
Upload | Select your file |
Review | Check the kinds of feature Cloneable found |
Identify | Tell Cloneable what each kind of feature is |
Details | Choose what to track for each feature |
Create | Name and create the configuration |
1. Upload
Drop in the file. A KMZ is unpacked first, which takes a moment on a large one.
Wait for parsed successfully.
If it says | Do this |
Unsupported file | Check it is genuinely KML, KMZ or GeoJSON |
Too large | Split the file by area |
Could not parse, with a reason | Read the reason and fix the file; a malformed file fails the same way twice |
2. Review
Read the table of feature types, each with a confidence rating and a count.
Check the counts add up. In one real file, 13 poles plus 7 anchors made 20 points, and 12 spans made 12 lines, for 32 features across 3 types.
If a file you expected to hold hundreds of poles shows a handful, the problem is the file. Fix it there, not here.
3. Identify
For each kind of feature, confirm or change what it is: pole, span, span measurement, guy anchor, or one of the others.
Suggestions arrive pre-filled and marked Auto, so most of the time you confirm rather than choose. A line cannot be mapped to a point role such as pole.
Leave a feature unmapped if it is none of those. Not everything in a map file needs to become an object.
This is the decision everything downstream rests on. A feature identified as a pole gets everything Cloneable knows how to do with poles, including how it is measured in the field. Get it wrong and the fix is to build the configuration again.
4. Details
For each feature, tick the fields you want recorded. Every field you add is another thing someone fills in on a phone; every field you leave out is data you will not have.
Some fields are always included: on Pole, job_id and location; on Span, job_id and related_poles; on Guy Anchor, job_id, location and related_pole.
For each kept field, choose what it is bound to.
Binding | Effect |
Plain text | Accepts whatever strings are in the file, typos and all |
An existing attachment option set | Values checked against your attachment vocabulary |
An existing picklist (pole_class, pole_species, pole_status, pole_type) | Values checked against a list your organization already controls. Prefer this. |
5. Create
Name the configuration.
Pick Measurement units: Feet (decimal), Feet & inches, or Metric (meters). The five-stage editor shows this same setting later under the label Imperial - Feet Decimal (5.9 feet); it is one setting with two labels.
Read the summary: template count, total field count, units.
Create. Cloneable confirms, or tells you plainly if it could not.
If something is wrong, the wizard sends you back to the step that caused it rather than failing at the end. Being sent back a step is it telling you where the problem is.
What happens next
Creating the configuration sets up the shapes your data will land in. It does not put any poles into a job yet.
On success you get two buttons: Import a KML as a job, which carries your new configuration into the import already selected, and Done.
To load poles now, continue with Bring your map file in as a job. To finish the configuration's settings first, see Set up your configuration, stage by stage.
Related