Improve trip display name heuristics

[jbruechert]

No description provided.

[jbruechert]

This at least fixes empty strings for MAV and names like "A1" in Austria. If there is documentation on how google maps uses the different values, that would probably be useful to improve this further.

[Altonss]

This at least fixes empty strings for MAV and names like "A1" in Austria. If there is documentation on how google maps uses the different values, that would probably be useful to improve this further.

Some information about how Google Maps handles this is available here: https://developers.google.com/transit/gtfs/data-modeling/route-modeling-guide .

[jbruechert]

Some information about how Google Maps handles this is available here: https://developers.google.com/transit/gtfs/data-modeling/route-modeling-guide .

Interesting, sounds like they only use the route name?

[Altonss]

Some information about how Google Maps handles this is available here: https://developers.google.com/transit/gtfs/data-modeling/route-modeling-guide .

Interesting, sounds like they only use the route name?

Yes, basically their logic is :
route_short_name or route_long_name (route_short_name overrides route_long_name, if given in the feed)

[jbruechert]

I think the results in the test files also look significantly better now