Convert TOPOJSON to GML
Turn TOPOJSON files into GML. A GML 3.2 document with one feature type holding the features and their attributes, in the source's coordinate system and without a separate schema file.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop TOPOJSON files on the dialor turn it to pick what to do
TopoJSON as a GML 3.2 document.One file with your features and their attributes, in the source's coordinate system.
What you get
A GML 3.2 document with one feature type that holds all the features and their attributes. The coordinates stay in the coordinate system of the TopoJSON file.
There is no separate schema file. The GML document stands on its own.
What changes
When some features have heights and others do not, the features without a height get a height of 0.
Lists and nested values in the attributes become JSON text.
Files with several layers
Several layers are joined into one feature type. A layer column names the layer each feature came from, so you can still tell them apart.
For other routes from this format, see every TOPOJSON conversion.
TOPOJSON and GML.What each format is.
The formats
TopoJSON
TopoJSON, GeoJSON's compact cousin that shares borders between shapes, as D3 maps use it.
- Extensions
- .topojson
- MIME type
- application
/topo +json - Kind
- Text and data
GML
Geography Markup Language, the OGC's XML for map features, as WFS services send it.
- Extensions
- .gml
- MIME type
- application
/gml +xml - Kind
- Text and data
In your code.The same TOPOJSON to GML conversion through the API, for your app or your agent.
$ cv convert report.topojson report.gml$ cv convert report.topojson report.gmlQuestions.What people ask about TOPOJSON to GML.
Yes. The features stay in the coordinate system of the source.
The layers are joined into one feature type. Each feature has a layer column that names the layer it came from.
No. The output is one GML file without a separate schema file.
They become JSON text. Nested values are handled the same way.