Why is the conversion described as "loosy"?
The conversion is "loosy" because KML and GPX are different formats with different feature sets. Some KML elements, styles, and custom data cannot be accurately represented in GPX, so the uploader preserves the core route and waypoint data but may drop or simplify unsupported details.
What KML features may be lost during conversion?
- KML styling and icons
- extended data and custom metadata
- folders and nested feature structures
- 3D coordinates and altitude-specific details beyond basic elevation
- some KML geometry types such as polygons and advanced overlays
What is preserved in the conversion?
- waypoints
- tracks and routes
- basic coordinates and timestamps when available
What does the "Skip unsupported geometry and continue" toggle do?
When the toggle is off, the converter stays strict and stops if it finds unsupported geometry. When the toggle is on, unsupported shapes are skipped and the supported parts of the file are still converted. Examples include KML polygons, linear rings, models, and multi-tracks.
Can I expect the converted GPX file to look exactly like the original KML?
No. The output is intended for practical use in GPX-compatible applications, not as an exact visual or structural duplicate of the original KML.
How should I use the uploader for the best results?
Use it for KML files that contain simple route, track, or waypoint data. Avoid relying on it for files with heavy styling, custom attributes, or complex KML-specific features.
What if I need the full KML data preserved?
If you need the full original KML content, keep the KML file and use a tool or viewer that supports KML directly instead of converting it to GPX.