Generates precise GTFS shapes for public transit feeds by map-matching schedule data to OpenStreetMap road networks.
pfaedle is a command-line tool that generates precise geographic shapes for public transit routes by map-matching General Transit Feed Specification (GTFS) schedule data to OpenStreetMap road and rail networks. It addresses the common issue of missing or inaccurate route geometries in transit feeds, producing high-quality shapes that reflect real-world paths.
Transit data engineers, GIS specialists, and developers working with GTFS feeds who need to enhance schedule data with accurate route geometries for visualization, analysis, or routing applications.
Developers choose pfaedle for its proven accuracy in map-matching transit schedules to OSM networks, its support for multiple transit modes, and its practical features like OSM filtering and Docker deployment, which streamline the process of generating production-ready GTFS shapes.
Precise map-matching for public transit feeds. Generates high-quality GTFS shapes from OSM data.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Converts GTFS schedule data into accurate, realistic paths along OSM networks, as shown in README visual comparisons that demonstrate significant improvements over station-to-station lines.
Supports various transit modes like tram, bus, rail, and ferry via configurable filters, allowing targeted processing based on route types or extended codes for granular control.
Includes OSM filtering to extract only relevant network data for a GTFS feed, reducing processing time and resource usage, as highlighted by the -X flag for optimized runs.
Available as a Docker container for easy, reproducible execution, simplifying setup and integration into CI/CD pipelines, with examples provided in the README.
Provides GeoJSON exports for calculated paths and routing graphs via flags like -T and --write-graph, enabling verification and analysis of map-matching results.
Requires building from source with dependencies like cmake and gcc, which can be challenging for users without a development background, despite Docker alternatives.
Solely relies on OpenStreetMap data, limiting its use in environments where other map sources are preferred or where OSM coverage is incomplete or outdated.
Lacks a graphical user interface, making it less accessible for non-technical users or for quick, ad-hoc tasks without scripting knowledge.
Processing large OSM files can be memory and CPU intensive, especially for extensive transit networks, though OSM filtering helps mitigate this.