Open colton-nevs opened 2 years ago
Actually, matching shapes to an OSM network is quite error prone due to inaccuracies in geometry and using route information from OSM can avoid the need for map matching. However, the option to make use of shapes would still be valuable.
We just didn't get around to implementing this yet.
Rather, since net.GetOptimalPath() exists it would be much better to use that rather than mapping straight line traces between stops.
It seems that the community script gtfs2pt.py draws a straight line between stop locations for each trip and then maps this trace to the network using tracemapper.py, if OSM routes are not supplied. If they are supplied, it instead matches the trace to a route existing in the OSM file (essentially only producing a schedule for the routes existing in OSM using the GTFS data).
Unless I'm misunderstanding, this seems rather silly if shapes.txt is in the GTFS data. One would imagine that the GTFS shapes could be more trustworthy than OSM routes.