Noémie

I have a fix ready:  https://github.com/Jungle-Bus/osm2gtfs/compare/python3...Jungle-Bus:fix_shapes But we need to merge #160 first :wink:

Thanks for these improvements @jamescr , I've updated the PR :+1: Does anyone want to have a look ?

I think it would be a good addition to osm2gtfs :+1: But IMHY we should wait for it is fully integrated into the official GTFS spec. For the record :...

Hello, its seems that you are using python3. For now, osm2gtfs only supports python2. Have a look at [Jungle Bus fork](https://github.com/Jungle-Bus/osm2gtfs) or at [this pending PR](https://github.com/grote/osm2gtfs/pull/160) to see if if...

It is not the option that seems to win the vote but I prefer my last suggestion to use the `relation id` as `route_id`: - we already use `osm id`...

To sum up, we have an agreement on the following: - [ ] in `osm_connector`, handle `route_id` duplicates by warning the user and appending something at the end - [...

I agree : I don't think adding city to stop name is a good GTFS practice. In my opinion, this could be handled in a custom creator if really needed

 

We have a pretty good start in this repo : https://github.com/osm-without-borders/cosmogony_explorer - [x] Visual coverage by zone type - [x] View zone metadata - [x] Explore the hierarchy

Anyway, we have two candidate approaches to build the hierarchy (geographical inclusion and wikidata). We may choose one, and create some QA checks or additional tools to test our data...