Converts OpenStreetMap public transport data and schedule information into GTFS feeds for transit applications.
osm2gtfs is a Python tool that converts public transport data from OpenStreetMap and external schedule information into General Transit Feed Specification (GTFS) files. It solves the problem of generating standardized transit feeds from open data sources, enabling integration with mapping and trip planning applications. The tool retrieves network data via the Overpass API, combines it with schedule data, and outputs GTFS using the transitfeed library.
Transit agencies, city planners, open data advocates, and developers working on public transport applications who need to create or maintain GTFS feeds from open data sources.
Developers choose osm2gtfs because it provides a free, open-source solution for generating GTFS feeds from OpenStreetMap, avoiding proprietary data sources. Its extensible configuration allows adaptation to various cities and schedule formats, promoting transparency and community-driven transit data improvement.
Turn OpenStreetMap data and schedule information into GTFS
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Directly retrieves current public transport network data via the Overpass API, enabling use of open, community-maintained maps without proprietary dependencies.
Merges OSM network data with external schedule information to create complete GTFS feeds, addressing gaps where OSM lacks time data.
Supports new cities through customizable configuration files and code extensions, as outlined in the developer documentation, allowing adaptation to diverse transit systems.
Caches OSM data on disk for re-use, improving processing efficiency during repeated GTFS generation runs, as mentioned in the README.
Uses Google's transitfeed library for GTFS file generation, ensuring compatibility and reliability with standard GTFS specifications.
Requires creating a new configuration file for each city and providing external schedule data, which can be time-consuming and complex, as noted in the README.
Only includes configurations for a handful of cities, so users must extend the tool for most locations, increasing initial setup effort and reliance on community contributions.
Relies on separate schedule information sources that may not be readily available or standardized, potentially limiting usability without additional data preparation.
The accuracy of GTFS feeds depends on the completeness and correctness of OpenStreetMap data, which can vary by region and affect output reliability.