Log of sub-optimal routing results @Entur

[t2gran]

This issue will be used to collect a list of travel searches witch are strange or sub-optimal. There might no be something wrong with OTP for all of them, it could be tuning, missing features or filtering. We will use this issue to log things we think are stage. Then for anything we think needs to be fixed we will create new issues or PRs for bugfixes.

Each case logged should include:

• A link to reproduce the problem

• At least one sentence to describe what is strange or sub-otimal.

  Version of OTP used (exact commit hash or JAR name)

  OTP2 - we test on the latest version of dev-2.x.

Data sets in use (links to GTFS and OSM PBF files)

• Transit, NeTEx, Entire Norway,
• Stops, Entire Norway (Current + future stops)
• osm data for all of Norway Transit data

Router config and graph build config JSON

Default should in most cases produce the same result, we might change the config over time.

[t2gran]

This issue was never used, we added new issues for every case.