Convert OSM to GML
Turn OSM 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 OSM files on the dialor turn it to pick what to do
OpenStreetMap data as GML 3.2.Points, lines and polygons with their tags, in one GML file.
What you get
One GML 3.2 document with a single feature type that holds all the features and their attributes. The coordinates stay in the source's coordinate system, and no separate schema file is written.
Tagged nodes become points. Ways become lines, or polygons when they are closed and tagged as areas. Route and multipolygon relations become multilines and multipolygons.
How tags are stored
Common tags such as name, highway and building become columns. The other tags are kept as JSON in other_tags.
Lists and nested values become JSON text. When some features have heights and others do not, the ones without get a height of 0.
What is left behind
Untagged nodes are dropped. Relations other than route and multipolygon are dropped too, and so are versions and authors.
If the source has several layers, they are joined into one feature type. A layer column names where each feature came from. See every GML conversion for other ways to produce GML.
OSM and GML.What each format is.
The formats
OpenStreetMap Data
OpenStreetMap nodes, ways and relations with their tags, as .osm XML or the smaller .osm.pbf.
- Extensions
- .osm .osm.pbf
- MIME type
- application
/vnd .openstreetmap .data +xml - 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 OSM to GML conversion through the API, for your app or your agent.
$ cv convert report.osm report.gml$ cv convert report.osm report.gmlQuestions.What people ask about OSM to GML.
Yes. Common tags such as name, highway and building become columns, and the other tags are kept as JSON in other_tags.
GML 3.2. The file has one feature type and no separate schema file.
No. The coordinates stay in the source's coordinate system.
No. Versions and authors are dropped, along with untagged nodes and relations other than route and multipolygon.