ialokim

@prhod and @nlehuby: I was just wondering, whether fare information from GTFS is imported and used by Navitia or not? 🤔

@prhod Thanks for your answer! Great to hear you are working on it!

I've now written a first basic implementation for Estelí that only supports a fare per route, see the proposed `fares.json` [here](/mapanica/pt-data-esteli/blob/master/fares.json) and the working branch [here](https://github.com/mapanica/osm2gtfs/tree/fare-creator). Due to the poor...

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...

It's also worth mentioning the GTFS [`frequencies.txt`](https://developers.google.com/transit/gtfs/reference/#frequenciestxt), which is an alternative source of time information for exactly the situations described above. We should discuss whether to include the above mentioned...

> I think this has nothing to do with schedule. If we need it to be configurable I would put it into the config file. But I think it should...

> As far as I see this is most typical configuration and hasn't to do with schedule or time information. Yes, you are right, but why not supporting it within...

> Why do you need `included_lines`? Not sure if this is very specific to our Nicaraguan case, but we have a lot of bus services mapped in the `NI` (national)...

Thinking about it another time, I'm not very sure anymore whether this option is really needed: `included_lines` could be deduced from all the lines given in the `schedule.json` and `excluded_lines`...

The issue is much bigger. See #112. This one should be closed.