[gtfs2netexfr] Help needed to pinpoint cause of "unused lines" pruning about transit_model

[thbar]

@woshilapin thanks for the feedback and sorry for the long delay in responding. I will close for now, because there is no clear proof of anything. We must do more debugging on the GTFS file itself, then see if I need to re-open or not! Thanks for your feedback in all cases, I'll go ahead and close.

[woshilapin]

Hi @thbar,

I don't see any other tools than checking the logs to try and understand what is going on. Although, even the logs are not exhaustive, so you might end up in a dead end trying to understand what is going on from those logs.

There is however, one thing that might be worth mentioning. You are mentioning lines in GTFS... but GTFS doesn't have the notion of line: it's a route. Even if at first glance, it might seem like a different word for the same concept, it is not. In NeTEx, there is the notion of both Line and Route.

In transit_model, we're using an Intermediate Representation (IR) called NTFS which also has the notions of line and route [1]. And therefore, we're first transforming GTFS into NTFS, then NTFS into NeTEx. This is an implementation detail but with this information, you can now take a look to the specification to convert GTFS into NTFS that will explain the rules behind the conversion from a GTFS route into both NTFS line and route (and therefore, into Line and Route in NeTEx).

Please come back to us if you need more details on some part of these documentations, or even on some implementation details.

[1]: The notion of line and route in NTFS and in NeTEx might be slightly different. If you want more information about that, look at the specification for converting from NTFS to NeTEx.

[woshilapin]

Hi @thbar, have you had the chance to take a look at it? I'm wondering if we should keep the issue open or not?