Where: background reading before you prepare a map file.
When you finish: you know why line ends must sit on pole positions, what to check in the file first, and how to spot a span that did not attach.
When you import a map file, Cloneable has to work out which spans belong to which poles. Nothing in your file says so directly: it holds points and it holds lines.
On screen: Lines will automatically link to point objects based on matching endpoint coordinates. Make sure your KML data has properly aligned coordinates for accurate relationships.
A line finds a pole because the end of the line is where the pole is. Cloneable matches an exact coordinate first, then looks for a point close by, so ends drawn near their poles still attach. Ends a long way out attach to nothing.
If your file also carries attributes naming the point at each end of a line, Cloneable can fall back to those.
Files exported from a system that already knows which span attaches to which pole are usually fine. Lines drawn by hand over an aerial image are where trouble starts.
Check before you import
Ask whoever produced the file how far out the line ends are. Close is fine; far away or elsewhere on the map is not.
Check the poles and the lines come from the same source. Two sources merged into one file, especially after a coordinate conversion, is where mismatches come from.
Spot-check a pole with several spans and see whether the line ends land on or near it.
Check after you import
Open the job on the map.
Look at whether spans are attached to poles or sitting on their own. Do this before crews go out; a span that did not attach is a five-minute fix in the office and a wasted trip in the field.
Do not rely on the object count for this. Twenty points and twelve lines should give thirty-two objects, and that check catches missing objects. It does not catch unlinked ones, because an unattached line is still an object. Counts tell you everything arrived; only the map tells you it arrived connected.
If things did not link
Fix the file, not the import: move the line ends onto the point coordinates in whatever produced the file.
Import again into a fresh job.
Correcting coordinates at source is quicker than reconnecting spans one at a time, and it means the next batch from the same source works too.
Related