results in one or two dialog boxes saying the Fastest and/or Quietest routes are not available.
The error message is misleading and has been reported as an issue for CycleStreets.
The main problem though is that the mobile site is requesting the three main plan types: quietest,balanced and fastest individually using separate API calls.
In the journey planner version 1 API this would recreate the missing route plan types, but that will not work in version 2.
Instead the version 2 journey.retrieve API will return all available plans from the archive when the plans parameter is omitted or empty. (Otherwise it acts as as a filter.)
So the recommendation is to change the rendering of the mobile journey pages to be based on a single retrieval from the API. The displayed route plan types should be those returned from that call.
This fifty mile route around Salisbury:
https://www.cyclestreets.net/journey/95813197/
was created using an API key other than either the main one for CycleStreets desktop or Mobile app.
Only the
Balanced
route is available from the archive.Trying to display this route at:
https://m.cyclestreets.net/journey/95813197/
results in one or two dialog boxes saying the Fastest and/or Quietest routes are not available.
The error message is misleading and has been reported as an issue for CycleStreets.
The main problem though is that the mobile site is requesting the three main plan types: quietest,balanced and fastest individually using separate API calls.
In the journey planner version 1 API this would recreate the missing route plan types, but that will not work in version 2.
Instead the version 2
journey.retrieve
API will return all available plans from the archive when theplans
parameter is omitted or empty. (Otherwise it acts as as a filter.)So the recommendation is to change the rendering of the mobile journey pages to be based on a single retrieval from the API. The displayed route plan types should be those returned from that call.