TDLR: This article is for background reading for Step 4 of the Katapult import process. 99% of the time, customers do not need to spend much time on Step 4, just make sure to focus on whether you need either pole measurements or midspan measurements on any custom nodes you bring in.
Katapult and Cloneable do not always use the same words for the same things. Matching them up is step 4 of the import, and it decides whether a thing on your map behaves like a pole or is just a dot with data attached.
The three things you match up
Cloneable object | What it is for | Cloneable's guess on a full import |
Pole | Utility pole with measurements and attachments | A node type called pole |
Span | Cable span between poles | A connection type called aerial cable |
Guy Anchor | Guy wire anchor point. Also asks for an export connection type, the Katapult connection your anchors go back out as; it starts at down guy | existing anchor, falling back to new anchor |
Anything matched to one of these inherits everything Cloneable knows how to do with it: how it is measured, how it connects, how it exports.
None of the three is forced. Each selector offers to use defaults, and the step lets you continue either way. Its only check is the box confirming you reviewed your mappings.
A missed pole match is the single most expensive mistake on this step, because everything about pole measurement depends on it. Check the guesses rather than trusting them.
Everything else becomes a custom object
On screen: Map your Katapult node types to standard data objects. Unmapped nodes will be imported as custom data objects.
A custom object still appears on the map and still collects data. It will not export as a pole, and it offers no measurement unless you give it a measurement style.
On a fresh import everything in the unmapped list arrives ticked, so your job is pruning: do my crews need to see this in the field? If it is Katapult bookkeeping, untick it. You can change this later.
Points get a measurement style: none for a marker, pole or midspan for something crews measure that way. Lines do not.
Span is the cable; midspans are points you actually collect the height measurements.
Underground routes
An underground route in Katapult is usually drawn as a run of short segments between vaults, handholes or pedestals. Cloneable brings the whole route across as one line, so a fielder sees and edits one route rather than a dozen pieces.
The line keeps Katapult's line style, so an underground route looks the same as it does in Katapult.
It keeps Katapult's segment lengths, so footage still adds up.
Edits to the route in Cloneable export back to Katapult.
Like any other line, an underground route has no measurement style. Tick its connection type in the unmapped list if your crews need to see or edit it.
Worked example
Katapult type | Became |
pole | Pole |
aerial cable | Span |
existing anchor | Guy Anchor |
map note | Custom point |
reference | Custom point |
down guy | Custom line |
slack span | Custom line |
overhead guy | Custom line |
pole to pole guy | Custom line |
underground cable [CONFIRM: Katapult type name] | Custom line (one line per route) |
Three matched, seven brought across as custom objects. The guy runs became custom lines rather than spans, because a guy is not a cable span between two poles even though it looks like a line on the map. The underground run became one custom line for the whole route.
The rule in one line. Match it if your crews will measure it. Bring it across as a custom object if they only need to see it. Leave it off if neither is true.
How it looks is separate from what it is. Matching decides how an object behaves; step 5 decides how it looks, including whether it keeps Katapult's style.