CLI tool to create OSM files from a variety of proprietary street network sources.
Converting arbitrary street data into the OSM data model has the following advantages:
- FOSS routing engines work out-of-the-box with your custom street data (e.g. Valhalla, GraphHopper, Openrouteservice and others)
- the entire OSM software ecosystem can be used for data processing (
osmium,osmosis,osm2pgsqletc.) - Storage-efficient protobuf (PBF) format to store the data which also allows for metadata tags
In case of interest or questions, please contact us on enquiry@gis-ops.com.
Disclaimer The converter has been designed to only work with street network data and is not suitable to produce OSM files for rendering or any other purpose.
- TomTom (including the MNL datasets, i.e. logistics: width/height/hazmat etc.)
- HERE
Generally the software can be used to output data suitable for any transportation profile. Note however, that most proprietary street datasets are optimized for motorized vehicles.
The software was designed to provide least resistance to extensibility, both in terms of extending functionality for already implemented providers and/or implementing a new data provider, other than TomTom or HERE.
Please contact us over enquiry@gis-ops.com in case of questions iwth regards to customization.
The following is a (not comprehensive) list of the general OSM tags we create/use for e.g. TomTom data:
- name
- highway
- oneway
- maxspeed (including
:hgv,:forward,:backwardand others) - Access restrictions motor_vehicle, motorcar, bus, psv etc
- All turn restrictions (except for turn restrictions > 2 way members)
- bridge
- tunnel
- hazmat (for truck profiles)
- maxweight (for truck profiles)
- maxheight (for truck profiles)
- maxwidth (for truck profiles)
- incline (for pedestrian)
The output OSM files have been validated against:
- Graphhopper
- Valhalla
- OpenRouteService
- JOSM
- QGIS
- osmosis
- osmium