Skip to main content

Speed Limit Went to 60 MPH in 25 MPH Zone

Bug Reports

When driving across Highway 16 on Wollochet / Pioneer (the route segment in the attached plan) the speed limit should drop from 35 MPH to 25 MPH. Instead I noticed that as I was heading down Pioneer in a 25 MPH area ABRP was showing the speed limit as 60 MPH.

My best guess is that ABRP may have picked up the speed limit from the highway as I passed over, but that’s just a guess.

https://abetterrouteplanner.com/?plan_uuid=2-6a45dd20-56a9b8438c5bc2cf904da2c5

Where does this happen?
ABRP version number (found at bottom of settings menu)
Posted by ABRP User #811399 ·
Status: In Review3 comments

Log in to comment and vote

Comments3

  • Nikola changed status to Awaiting Clarification
    Team•

    Jul 2

    Pinned

    Hi Doug,

    I’ve looked into it abit and i can see that the road/bridge that goes over the highway completely lacks data on speedlimit, it is set to zero. Now i don’t know if that is the issue, but could be. When doing a fake drive, the speed limit is set to 56 just before reaching the bridge.

    The best way to get this fixed is to correct the map directly on OpenStreetMap.org.

    Once the changes are made in OSM, they will eventually be reflected in a future ABRP map update.

    • ABRP User #811399

      •

      Jul 2

      There is something very odd going on with ABRP speed limits. The speed limits around Gig Harbor / Tacoma (where I do most of my driving) used to be accurate. But over the last few months, I’ve noticed that they are now anything but accurate.

      The first problem I noticed was with an advisory speed in a roundabout that was tagged as a speed limit in OSM at least two years ago (based on the timestamp of the last edit in that area). I reported that in Bad Speed Limits Around Gig Harbor, WA with examples in the comments and also in Where Does the Speed Limit Value Come From?

      with a short route showing the problem at the roundabout.

      Another common place where there are speed limit errors in the area are when coming off of a highway. The speed limit will stay at the highway speed until something forces it to change. It appears from looking at some of the places where this happens that there is no maxspeed tag on the segment of road that you exit onto. I’m not sure why this used to work, but I’m pretty sure that it did.

      At the very least, it seems that ABRP could notice that the road you exited onto didn’t have a speed limit and stop displaying a speed limit value. At least that way a driver wouldn’t be misled. Arguably you should know that a secondary or tertiary street won’t have a 60 MPH speed limit, but I’ve also seen this happen on city streets where the speed limit goes from say 35 down to 25 MPH, that might be harder for a driver from out of town to pick up.

  • Nikola

    Team•

    Jul 2

    Hello Doug,

    Thanks for reporting this, im looking into it, will reply shortly