You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've already done some work towards this by making fewer import-related things hard-coded.
There's now an OverpassImporter class that fetches some OSM data using the Overpass API and then imports it. The following tests represent the work-in-progress on how that class is currently being used:
There's now support for an XML-based configuration file. See this minimal example for San José and the more complex example for Berlin that uses multiple route definitions and processing instructions.
The following tasks use such configuration files:
openmetromaps-cli osm-import file
openmetromaps-cli osm-import overpass
openmetromaps-cli osm-query
openmetromaps-cli osm-inspect
The task osm-import overpass can be used to import via Overpass API and the only input required is a configuration file. The task osm-import file uses a configuration file, too, but imports from a local OSM file instead. The task osm-query also operates on a configuration file, but just downloads the specified data from Overpass API for further processing or for use with the osm-import file task. Task osm-inspect is the (draft) importer tool that allows you to inspect the data that is going to be imported, perform the actual import and in the future should also offer support for configuring the data imported more fine-grained.
It would be great to handle the data extraction from OSM with a config file (instead of having to write code).
We will need a bounding box and some tags to filter (usually the
route
/route_master
tags and/ornetwork
tags)Something like the json file from the osm2gtfs project would be great :
The text was updated successfully, but these errors were encountered: