WaltG Posted September 1, 2021 Share Posted September 1, 2021 Description: No matter how I reset my route waypoints I can't make the plan go across the bridge. Route always backtracks or goes north to I 95 and back down. . Type: Using Web version. Win 10 Link to Plan: https://abetterrouteplanner.com/?plan_uuid=a8445733-b129-44be-bb6c-ffbd48cb985a Replication Steps: Ive tried clearing the plan and starting from different points. If I start north of the eastern shore, the route gets to the bridge and then doubles back until it can get to I-95 and go down the western side. I can't find any settings that say "Avoid large bridges" Remember, the more detail you can provide in your bug report, the faster we can fix it! Link to comment Share on other sites More sharing options...
tr6tevens Posted September 2, 2021 Share Posted September 2, 2021 I just ran into the exact same issue while planning a trip from DC to St Michaels and back. It will go east over the bridge, but not west. I know there were some brief westbound lane closures scheduled for 10pm -5am August 29 - Sept 1, so maybe ABRP took that into account, but hasn't updated? Link to comment Share on other sites More sharing options...
tr6tevens Posted September 9, 2021 Share Posted September 9, 2021 Confirmed that this is an issue that stems from the OpenStreetMap routing, and the fact that the northern span of the Chesapeake Bay bridge is identified as "one-way-reversible" (which some lanes are). See https://github.com/Project-OSRM/osrm-backend/issues/2837 I don't know if there's a way to have ABRP use the alternative Graphhopper API, but it gives a correct route. Link to comment Share on other sites More sharing options...
amer Posted October 10, 2021 Share Posted October 10, 2021 I experienced this last night too - using live routing, I had to go against the planner and the moment I cleared the Chesapeake Bay Bridge going west, it went back to normal. Link to comment Share on other sites More sharing options...
Bo-ABRP Posted November 18, 2021 Share Posted November 18, 2021 This has been solved now - we generally handle one-way-reversible lanes better. Link to comment Share on other sites More sharing options...