Grouping stops about osm2gtfs HOT 13 CLOSED

Strange that it doesn't tell you to walk from stop A2 to stop A4.

But in general, I agree that we should have support for parent_stations and stop_area relations.

Your dataset should be sufficiently small to add the parent station manually and see if that helps with the problem. Maybe it is worth a try.

from osm2gtfs.

With the stops grouped in a station Transportr tell me to walk from stop A2 and A4, and the results make more sense. Here are the results, image at 2:43pm is without station and image at 2:40pm is with station.

from osm2gtfs.

Thanks for the screenshots. Looks good. If you want to work on this, maybe let's merge your incofer branch first. It seems to be in a usable state already.

from osm2gtfs.

Sure I'll work on this issue.

You mean the incofer branch of public-transport-enabler and Transportr ?

from osm2gtfs.

Sure I'll work on this issue.

Awesome! :)

You mean the incofer branch of public-transport-enabler and Transportr ?

No, I meant the incofer provider for osm2gtfs.

from osm2gtfs.

Honestly I wasn't expecting to merge it, but if you agree I think it's great!.

from osm2gtfs.

In my opinion, all other creators should ideally be merged here. This makes sense for example when we refactor the code. If the creators live in other repositories, they need to be manually adjusted to whatever changed in the upstream repository.

from osm2gtfs.

I have a working draft for this issue: https://github.com/jamescr/osm2gtfs/tree/issue-55. Now It's only working for Incofer but I'll appreciate any comment before extending it to fenix. By the way i have one doubts about stop/stop_areas, a OSM stop/platform could be member of more than one stop_area?

from osm2gtfs.

Great! :)

Just gave it a quick look and I wonder whether it is necessary to make an extra query per stop_area. Couldn't this data be returned by @xamanu's new optimized query?

from osm2gtfs.

The problem with the stop_area is that those aren't part of the relations that describe a route. Stops and platforms are part of a stop_area relation. Anyway I'll look at @xamanu query to be sure if I could reused it.

from osm2gtfs.

I have implemented an alternative solution that uses the _query_stops() with a little modification to get the stop_areas. Also includes a different approach on handling stops (similar in some way to the routes variants and masters). Again I have been testing with incofer but this is only a request for comments draft.

from osm2gtfs.

Nice! I didn't review it, but looks like with this solution, you don't need to make additional queries. Great!
Do you personally prefer this solution over the other one?

from osm2gtfs.

Yes I think the alternative solution is better. I hope I could finish it by the end of the week.

from osm2gtfs.