Our center has a project to explore the use of OSM as a repository and tool for
supporting multimodal trip planners (for example, bike to transit, ride the
bus, walk or bike to final destination). We are keenly interested in the
current discussion of transit and GTFS in OSM, because one of our
Ed,
Great to see someone from the CUTR efforts chiming in here.
Just to clarify one point, when you say locational errors in GTFS,
you're referring to issues with the source data from the particular
agencies that you're working with, rather than anything having to do
with the representation
I'm currently looking at Bus stops in Ottawa in OSM and finding similar
issues with the existing bus_stops. I'm seriously wondering where
stop_codes exist if one approach might be to import bus_stops using GTFS
data and use the GTFS tags such as stop_code etc from stops.txt
Many transport agencies/operators still don't have rider-facing stop
codes, and some may have them for only a subset of their stops.
However, as you say, where they *are* present, they present the most
stable dataset-local identifier for stop, if only because of the costs
involved in changing
