Skip to main content

Routed to a closed entrance

Questions

I was routed to a closed entrance coming from B408 and was not able to entrance the A31. In CarPlay it was not able to mark the entrance as closed, so the ABRP tried again and again to route me back. How is it possible to mark it as closed and get a valid new route?

Posted by ABRP User #38200 ·
Status: Awaiting Clarification4 comments

Log in to comment and vote

Comments4

  • Mahde - ABRP changed status to Awaiting Clarification
    Team•

    Jun 15

    Pinned

    Hello @ABRP User #38200,

    Please provide a link to the plan where this occurs. To do this;

    1. Plan the trip in ABRP

    2. Click/tap: ‘Share plan’

    3. Click/tap: ‘Share ABRP link’

    4. Paste the URL here

    ⚠️ IMPORTANT: Please exclude private addresses and the use of ‘my position’, home, work, etc., from the plan you post here publicly.

    Please send a screenshot of the specific part you want to be closed to not make other roads be closed.

  • ABRP User #811399

    •

    Jun 15

    This would be a very useful feature. On multiple occasions, I’ve run into routes that don’t work because of OSM errors or construction. It can be very hard to get ABRP to give you a new route that avoids the problem area.

    There are two (or maybe three) use cases that I see:

    • When a road is closed for a “project” (something that will take days or weeks to complete).

    • When a road is closed for a temporary “event” (something that will take hours like a parade or a major accident).

    • When the underlying OSM data is wrong or incomplete.

    The UI I envision would present a dialog that lets you indicate the type of problem so that the routing algorithm could have an estimate of the length of the closure and do better routing for other users going through the same area.

    In the case of problems that seem to stem from bad OSM data (e.g., a road that does not actually go through or seasonal or daily closures) it would be really great to automatically annotate the underlying OSM data with a tag that indicates the type of problem. It seems like that would help to prompt OSM editors to correct problems in their area.

    It might be nice to also add an option to have the problem added to a “to do list" for ABRP users who are also OSM editors.

    This bug report includes a couple of examples:

    https://abrp.featurebase.app/p/bad-routing-decisions

  • ABRP User #38200

    •

    Jun 15

    “Please send a screenshot of the specific part you want to be closed to not make other roads be closed.” → Don’t undestand what you mean. In my other navigation apps, I have an options I already used, to say road ahead closed for x Meters and the app search an alternative route. I don’t know how long the on-ramp will stay closed and why it was not marked as closed. I think this can happen in future and this is why in other navigation apps they is an option to mark is a closed manually. So it would be great to have this option in ABRP too.