Convert OSM to FGB
Turn OSM files into FlatGeobuf. A FlatGeobuf with the features and their attributes in the source's coordinate system and a spatial index.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop OSM files on the dialor turn it to pick what to do
Map data in a file built for the web.Points, lines and polygons from your OSM file, with a spatial index.
What you get
One FlatGeobuf file with the features and their attributes in the source's coordinate system, plus a spatial index. Tagged nodes become points. Ways become lines or, when they are closed and tagged as areas, polygons.
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, so they stay with their feature.
Lists and nested values become JSON text.
What it leaves behind
Features without a geometry are left out. Untagged nodes, other relations, versions and authors are dropped.
If the source has several layers, they are joined into one. A layer column names where each feature came from.
See every OSM conversion for other formats you can start from.
OSM and FGB.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
FlatGeobuf
FlatGeobuf, a compact binary format for map features that streams over the web.
- Extensions
- .fgb
- MIME type
- application
/flatgeobuf - Kind
- Text and data
In your code.The same OSM to FGB conversion through the API, for your app or your agent.
$ cv convert report.osm report.fgb$ cv convert report.osm report.fgbQuestions.What people ask about OSM to FGB.
Tagged nodes become points. Ways become lines, or polygons when they are closed and tagged as areas.
Common tags such as name, highway and building get their own columns. All the other tags are kept as JSON in other_tags.
No. Versions and authors are dropped, along with untagged nodes and relations other than route and multipolygon relations.
They are joined into one layer in the output. A layer column names where each feature came from.