If you are not coming from Katapult, this is how your organization gets set up. You hand Cloneable a map file, tell it what the things in the file are, and it builds your configuration from that.

Cloneable describes it as turning a KML, KMZ or GeoJSON file into a saved configuration, then importing it as a job. Those are two stages, and this article is the first.

You need administrator access, and this page checks before you begin rather than at the end. See What you need before you start (map file).

Before you upload anything, the wizard also offers Map to an existing job instead in the top right. Use that instead of this wizard when you want to attach a file to a job you already have, rather than build a new configuration.

The wizard walks you through:

Cloneable ticks off steps you have finished as you go, so you can see where you are.

Drop in your file. If it is a KMZ, Cloneable tells you it extracts the archive and reads the contents, which takes a moment on a large one.

Three things can go wrong here and each says so plainly:

When it works, Cloneable confirms the file was parsed.

Cloneable groups your file's contents into the kinds of feature it found and shows you them. This is a sanity check: if a file you expected to hold hundreds of poles comes back with a handful of features, the problem is in the file rather than in Cloneable, and it is much cheaper to find out here.

The table also gives each detected type a confidence rating and a count. Worth checking the counts add up before moving on: in one real file, 13 poles plus 7 anchors made up 20 points, and 12 spans made up 12 lines, for 32 features across 3 types in total. If your own counts don't reconcile the same way, that's a sign to open the file rather than the wizard.

This is the step that does the real work. Cloneable knows your file has several kinds of feature. It does not know which of them are poles.

So you tell it. The choices include pole, span, span measurement and guy anchor, among others.

Suggestions for each mapping arrive pre-filled and marked Auto, so most of the time you are confirming rather than choosing from scratch. The role choices offered are also limited to what each geometry supports, so a line in your file cannot be mapped to a point role like pole or guy anchor.

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 this wrong and the fix is to come back and build the configuration again, so it is worth slowing down.

If a kind of feature in your file is not any of the offered things, that is fine and expected. Not everything in a map file needs to become a first-class object.

For each kind of feature, you choose what you want recorded against it. This is the same trade-off as anywhere else in Cloneable: every field you add is another thing somebody may have to fill in on a phone, and every field you leave out is data you will not have.

Some fields are always included and cannot be unticked. On Pole, that's job_id and location. On Span, it's job_id and related_poles. On Guy Anchor, it's job_id, location and related_pole. Everything else from the file is optional to track.

Each field you keep also has a dropdown letting you bind it to something other than the raw values sitting in your file: Plain text, an existing attachment option set, or an existing picklist such as pole_class, pole_species, pole_status or pole_type.

This is worth taking seriously. Leave a field on Plain text and you accept whatever strings happened to be sitting in the file, typos and all. Bind it to an existing picklist instead and every value gets checked against a vocabulary your organization already controls. It is the difference between importing something governed and importing a mess.

Give the configuration a name and create it. Cloneable confirms when it is done, and tells you plainly if it could not.

This step also asks for your Measurement units. On screen: "Feet (decimal)", "Feet & inches", "Metric (meters)". Alongside it, a summary panel shows the template count, the total field count, and the units you picked.

Worth knowing: the five-stage configuration wizard sets this same choice back in Stage 1, under the label "Imperial, feet as a decimal" rather than "Feet (decimal)". If you've read that article too, you'll meet the same setting twice under two different names. Each article quotes its own screen, so neither wording is being corrected to match the other.

If something is wrong, the wizard raises it on the step that caused it rather than letting you get to the end and failing there. That is deliberate. If you find yourself sent back a step, that is the wizard telling you where the actual problem is, not losing your place.

Creating the configuration does not put any infrastructure into a job yet. It sets up the shapes your data will land in.

Cloneable offers to carry you straight on to the import with your new configuration already selected, so you do not have to go and find it. See Bring your map file in as a job.

On success, the wizard actually offers you two buttons: Import a KML as a job or Done. Building the configuration and importing the job are two separate actions, and this is the point where you choose whether to do the second one now or come back to it later.