Allow route_type as argument about osm2gtfs HOT 5 CLOSED

I think the query improvements from #2 will make such a parameter unnecessary.

However, what happens if you want both? trains and busses?

from osm2gtfs.

It seems that If I add the "route_type" key/value to the config[query][tags], this issue is unnecessary.

Regarding to the scenario where I want buses and trains, It's possible but, that case would not be a two GTFS case?

from osm2gtfs.

It seems that If I add the "route_type" key/value to the config[query][tags], this issue is unnecessary.

Yes, we already have a config file, so I prefer it over having to specifing too many things as command line parameters.

Regarding to the scenario where I want buses and trains, It's possible but, that case would not be a two GTFS case?

You could do two different GTFS files, but I think you don't want that and there's plenty of GTFS files that include multiple transport products, even more than just bus and train. So we would need to think who that could be represented in the query. Doesn't Costa Rica also have trains and busses?

from osm2gtfs.

Yes, this seems to me a duplicate, as #2 will allow this.

IIf you want both in one GTFS, you could still try to find (or come up with) another tag that you put on all relations. Maybe the network could be the same. Or in the least and last case you could still come up with a custom tag in OSM: Something like network:union or even gtfs_group (now people are going to hang me :) ) But if they belong together in a GTFS, then they could also be stated to belong together in OSM. I don't see any problem here.

from osm2gtfs.

I got it, will be solved with issue #2 :-)

from osm2gtfs.