FTTH Design from Google Earth to AutoCAD – KMZ Split & Import Workflow
KMZ Split & KMZ Import allow FTTH engineers to convert Google Earth survey data directly into AutoCAD designs.
Google Earth placemarks and routes are automatically transformed into blocks and polylines with correct coordinates and attributes — no MAPIMPORT, no QGIS, no manual redraw.
Who is this workflow designed for?
FTTH / FTTx network engineers
Fiber planners and designers
Telecom consultants and survey teams
Engineers using Google Earth for early-stage network planning
Why this workflow is different
Unlike traditional KMZ imports, this approach preserves the semantic meaning of survey data.
Placemark names become attributes, routes become clean polylines, and the result is immediately usable for FTTH engineering.
No need for
No MAPIMPORT profiles
No QGIS or GIS conversion tools
No manual redraw in AutoCAD
No loss of placemark names or meaning
From Google Earth Survey to AutoCAD Fiber Design
Many FTTH and FTTx engineers start their network planning in Google Earth.
Field surveys, desktop studies, and early design ideas are often captured as placemarks, routes, and zones in KMZ files.
The challenge begins when this data needs to be converted into a real AutoCAD design.
The KMZ Split & KMZ Import workflow bridges that gap.
What Problem Does This Solve?
Traditional workflows require:
MAPIMPORT profiles
QGIS or other conversion tools
Manual redrawing in AutoCAD
Lost object names and semantics
This leads to:
Time-consuming imports
Inconsistent results
Loss of survey intelligence
KMZ Split – Organize Google Earth Data by Type
The KMZ Split function analyzes a Google Earth KMZ and automatically separates it into logical object types, such as:
FTU / home connection points
Cabinets, handholes, poles
Trench routes and fiber paths
Design areas or boundaries
Each object type is saved as a separate KMZ, ready for controlled engineering import.
KMZ Import – Directly Into AutoCAD, No MAPIMPORT
The KMZ Import function reads these split KMZ files directly in AutoCAD, without using MAPIMPORT.
What happens automatically:
📍 Google Earth points → AutoCAD blocks
📏 Google Earth lines → LWPOLYLINE (even with only two coordinates)
🏷️ Placemark names → Block attributes
🗂️ Clean AutoCAD layers →
KMZ-POINT-001,KMZ-POLYLINE-001🌍 Accurate coordinates → WGS84 (LL84) to project CS
No prompts.
No scaling issues.
No lost metadata.
Why FTTH Engineers Prefer This Approach
This workflow matches how many fiber engineers already work:
Survey and planning in Google Earth
Export as KMZ
Immediate use in AutoCAD for engineering design
Key benefits:
No MAPIMPORT configuration
No QGIS dependency
Deterministic and repeatable results
Faster transition from survey to design
Scales to large FTTH rollout areas
Ideal FTTH & Fiber Network Use Cases
FTTH and FTTx network design
Fiber feasibility studies
City-wide or regional planning
Reuse of Google Earth survey data
Rapid conversion from field data to CAD design
Google Earth for Survey – AutoCAD for Engineering
Google Earth excels at visualization and data capture.
AutoCAD remains the standard for technical FTTH engineering.
The KMZ Split & Import workflow connects these tools seamlessly — allowing engineers to design where their data already lives.
Simple Survey to Design example
How to get from a GoogleEarth kmz to a FTTH / FTTX network design.
With our software we can convert Linestrings into LWPolylines and automatically create FTTH items (trench route, aerial route, duct, cables etc.) whatever is applicable.
We can convert Points into Temporary symbols while preserving the name (housenumber, handhole number etc.) that was used in GoogleEarth and automatically create FTTH items (ONT/FTU, Poles, Handholes/Manholes etc.).
An simple example:
We inserted some Placemarks at home locations and a Placemark at a handhole position. We also created a Path (polyline) for a possible/existing trench/duct route. The Placemarks at the home locations are not the real numbers, this is just an example of the functionality.
GoogleEarth can export a kmz file. A kmz file is a zip file that contains a Doc*.kml and *.png files.
Within the Document.kml file are Linestrings and Points. A single Linestring has multiple coordinates, a single Point has one coordinate.
1: GoogleEarth\Save\Save Place As: we saved this to a single KMZ file.
2: AutocadMap3D: with start our function c:KMZSPLIT and recognize different types of items and create separate kmz files
3: AutocadMap3D: we start our function c:KMZIMPORT and import the KMZ file(s).
Separate layers are made per item type. We made it as generic as possible in order to support all possible item/type names, concepts and languages.
We convert the polyline into an underground trail/duct trench. This can be New or Existing. Of course this can also be direct buried or an aerial trail.
We convert the handhole position in a handhole with the required properties: layer, color, text, number, BOQ etc.
There are different types of handholes and manholes already in our Menu and it is easy to add new types.
We convert the FTU/ONT positions into the right symbol with the required properties: layer, color, text, number, BOQ, split-ratio, etc.
In this simple example the split-ratio is 1:32 and FTU/ONT are to be connected via Duct.
The number you see above the round symbol is the Name that comes from GoogleEarth.
To create the DP locations we typically use our ITS-NetOptimus software to automatically create the network design for larger areas. But for this small example we just insert a DP location manually into the Handhole.
To create the Drop-cable routes we typically use our ITS-NetOptimus software to automatically create the drop-cable routes for larger areas. But for this small example we just use one of our Route functions.
We calculate the DP, check all connections and FTU/ONT and automatically create the Drop-cables with the correct properties: layer, color, labelling, cabletype, fibercount, livefiber amount, BOQ etc.
The dialog screen shows the fiber and splitter calculation of the DP. The calculation depends on the network concept settings.
Down: In this case the connected drop-cables for the 14 FTU/ONT’s were all with a 1:32 ratio. The software will calculate with any mix of ratio’s. For example: 1:1 (Bank), 1:32 (Homes).
Local: With this concept setting the DP uses 2 (1:8) splitters to connect 14 fibers.
Up: there are 2 fiber connection required with a split ratio of 1:4.
Fibers\Down total: 28 (This concept setting, each FTU/ONT gets a 2 cable-fiber connection (1 live + 1 spare).
Fibers\Down live: 14 (This concept setting, each FTU/ONT gets 1 live cable-fiber connection.
Splices: 16 (14 for the ‘DOWN’ side FTU/ONT live fibers + 2 for the ‘UP’ side of the splitters)
AutocadMap3D FTU-ONT properties dialog screen. All items in the network automatically get unique identifiers and all other required properties.
AutocadMap3D FTU-ONT to DP drop-cable properties dialog screen.
AutocadMap3D FTTH area calculation design check dialog screen. A quick check for an area if everything is properly connected. It will show the connected FTU/ONT’s, MDU/MNT, DP’s, Cabinets etc. and all cables.
Besides the design and calculation functions we also provide concept calculation functions. You simply change the network concept settings and redesign the whole network or part of the network by clicking on any Manipulation point at any level in the network..
AutocadMap3D FTTH network schematic drawings. The ITS schematic functions create a schematic from any manipulation location for all levels downward.
AutocadMap3D FTTH area reporting of the BOQ can be done by simply a click on an area-line. Export can be to one of our FTTH project planning software’s: ITS-NetProgress is an online webbased SaaS solution or ITS-NetProject is a local network installed Client-Server solution. You can also export to a CSV file for MS-Excel or any other spreadsheet solution.
AutocadMap3D FTTH network with a Hybrid view with the aerial photo and the roadmap.
Location: Rozengracht, Jordaan, Amsterdam, The Netherlands
FAQ
Can I import Google Earth KMZ files into AutoCAD without MAPIMPORT?
Yes. This workflow reads KMZ files directly and converts survey data into AutoCAD entities without MAPIMPORT or GIS tools.
Is this suitable for large FTTH rollout projects?
Yes. The workflow is deterministic, repeatable, and scalable for city-wide and regional fiber designs. The largest single project was for 6.3 million homes.
Can we automatically make a cost optimized FTTH network design with this data?
Yes, you can, have a look at our ITS-NetOptimus solution. Click here for a short explanation.
Summary
This workflow enables FTTH engineers to convert Google Earth survey data directly into AutoCAD network designs.
By splitting and importing KMZ files without MAPIMPORT or QGIS, survey placemarks and routes are transformed into structured blocks and polylines with correct coordinates, layers, and attributes — ready for engineering design.
