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
When generating national GTFS feeds it is important to have the possibility to add some kind of city information to a Line or Itinerary because it is very likely that one name exists in various cities.
Example: MGA-110 (Bus number 110 in Managua, Nicaragua)
The text was updated successfully, but these errors were encountered:
I agree with @nlehuby . In your exemple, there is an aggregation of different types of information :
"Bus" is provided by the route_type
"110" is provided by the route_short_name
"Managua" should either be provided by the agency_name or be a more specific information in the route_name about the line
I quite don't like the idea of transforming the OSM informations in osm2gtfs, unless done in a specific creator.
The only point I see we should definitly change is the use of the route number (aka ref tag from OSM) as the route_id in the GTFS. It's very likely to encounter more than one routes with the same number that we would like to add to the same GTFS file. One very simple solution would be to use the master_route OSM id as GTFS route_id (similar to the stops/stations/shapes).
The only downside I see is that it would difficult human readability of the GTFS routes.txt and trips.txt, but I'm not sure whether this is very important.
When generating national GTFS feeds it is important to have the possibility to add some kind of city information to a Line or Itinerary because it is very likely that one name exists in various cities.
Example: MGA-110 (Bus number 110 in Managua, Nicaragua)
The text was updated successfully, but these errors were encountered: