Conditional access not getting respected during routing

[wolfy1339]

Routing engine

• OsmAnd's in-app offline routing
• Any online routing provider (YOURS, openrouteservice, OSRM, etc.)

Routing Profile

• Both the Bike and Pedestrian profiles with default settings
• Enable the Consider temporary limitations routing option

Start and end points

• Start: 46.88145, -71.47436 (Vélopiste Jacques-Cartier/Portneuf before intersection with an unnamed minor/unclassified road)
• End: 46.86870, -71.44179 (Just North of intersection between Corridor des Cheminots and Rue de la Méduse)

https://osmand.net/map/navigate/?start=46.881451,-71.474355&end=46.861889,-71.414577

Actual route

The router completely disregards the conditional access tags that are set on way/400207113 and routes using it.

Expected route

For the router to give another route that avoids the closed portion of the cycleway.

I would have expected the route to lok something more like this route:
https://osmand.net/map/navigate/?start=46.881451,-71.474355&end=46.868702,-71.441793&via=46.875507,-71.463565;46.871634,-71.451508&profile=bicycle#17/46.87132/-71.45486

Maps you used (online or offline)

• Offline maps offered within the OsmAnd app for download. Offline maps February 2025 + latest live updates
• Online (tile / raster) maps OSM website

Your Environment

OsmAnd Version: 4.9.10
Android version:15
Device model: Google Pixel 7 Pro

Anything else?

https://www.openstreetmap.org/way/400207113

[scaidermern]

no @ (2024 Nov 1-2025 Nov)
The end date has no day, only a month. Maybe OsmAnd can't handle this? 🤔

[vshcherb]

I think it doesn't support mix of values like no @ (2024 Nov-2025 Nov) is supported I guess

[wolfy1339]

think it doesn't support mix of values like no @ (2024 Nov-2025 Nov) is supported I guess

I'm having trouble understanding your comment, are you saying that the syntax of the conditional access isn't supported?

Or that this isn't supported in OSMAnd?

[scaidermern]

You specified year month day - year month. Try adding a day to the end date.

[wolfy1339]

I am aware. There is no more specific date than that currently.

[yuriiurshuliak]

The bug has been reproduced using the following steps:

1. Open the OsmAnd app.
2. Select the Bicycle or Pedestrian profile.
3. Enable the "Consider temporary limitations" option in routing settings.
4. Set the start and end points:
   • Start: 46.88145, -71.47436
   • End: 46.86870, -71.44179
5. Download the latest map version and enable live updates.
6. Generate a route.
7. Observed Issue: The app incorrectly routes through way/400207113, despite the conditional access restriction.

Additionally, we tested this on:

• OsmAnd Web Version
• OpenStreetMap (OSM) Bicycle Profile
• Routing Engines: OSRM, Valhalla, GraphHopper
• Google Maps (Bicycle Profile)

In all cases, the routing still passed through way/400207113, suggesting a possible issue with how conditional access restrictions are processed.

OsmAnd~ 5.0.0#4449m, released: 2025-02-24

OsmAnd	Web version	OSM