GML to KML Converter
Making OGC GML — common in European INSPIRE datasets and WFS responses — viewable in Google Earth for non-GIS stakeholders.
Common issues converting GML to KML
- GML's srsName often points to a projected or non-WGS84 CRS; KML requires WGS 84, so coordinates are reprojected — verify the source srsName first.
- GML 3 with EPSG:4326 uses lat/lon axis order where KML expects lon/lat; the converter handles the swap, but a malformed source axis order is the usual cause of flipped output.
- Complex GML features (nested properties, multiple geometry members) flatten to KML Placemarks with attributes in ExtendedData; deeply nested structures may simplify.
- GML application schemas vary widely; very domain-specific schemas may carry properties the generic mapping labels generically.
Frequently asked questions
Does it handle INSPIRE GML?
Yes for the geometry and standard attributes; highly specialized INSPIRE feature types map their geometry and surface properties in ExtendedData.
Why is my data in the wrong place?
Almost always srsName axis order (lat/lon vs lon/lat) in the source GML. The converter assumes the declared EPSG code's official axis order.
GML 2 or GML 3?
Both common encodings are read; geometry elements are detected regardless of version.
Can Google Earth open the result directly?
Yes — the output is standard KML that loads in Google Earth and Google My Maps (within My Maps' 5 MB limit).