Skip to main content

Bad Speed Limits Around Gig Harbor, WA

Bug Reports

I’ve noticed that the speed limits displayed in ABRP are often wrong in my corner of Washington state in the US. It seems like for some reason ABRP isn’t picking up some of the changes. For example:

  • ABRP picks up the advisory speed limit through a roundabout and doesn’t restore the original speed limit after the roundabout.

  • When exiting a limited access highway, ABRP does not pick up the speed limit for the city streets.

  • When the speed limit drops as you go into a denser area ABRP does not pick that up.

The problem seems widespread, so I don’t think it’s the result of a bad edit in OSM.

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

Log in to comment and vote

Comments7

  • ABRP User #811399

    •

    Jun 18

    Instead of “I don’t think it’s the result of a bad edit in OSM,” I should say “I don’t think it’s just the result of a bad edit in OSM.”

  • Bo (ABRP)

    Team•

    Jun 17

    Is this while free driving (i.e. without a plan) or is it with a plan?

    • ABRP User #811399

      •

      Jun 17

      Both. At least I’m pretty sure that it happens when free driving, and it definitely happens when on a plan.

      • Bo (ABRP)

        Team•

        Jun 18

        Thanks - can you create an example plan (preferably short) which illustrates the issue and share the URL here?

        • ABRP User #811399

          •

          Jun 18

          This one may still show the problem:

          https://abetterrouteplanner.com/?plan_uuid=2-6a339a45-b6b9c71728ca02996a106374

          I’m pretty sure this one is due to an erroneous ‘maxspeed’ tag that should be a ‘maxspeed:advisory’ tag at the roundabout near the start of the route. It drops the speed limit to 15 mph and it will remain there until you’re on the highway at the end of the route. I edited OSM to change the tags to advisory a couple of days ago, so it might be fixed now.

          This one shows a similar problem, but in this case the speed limit stays at 60 mph for quite a while:

          https://abetterrouteplanner.com/?plan_uuid=2-6a339b9d-79d78c2cb996e06b6a19d4a6

          The speed limit problem is new. I drive these routes frequently and ABRP used to get the speed limits right. I can find you more examples if you need them.

        • ABRP User #811399

          •

          Jun 30

          Would more examples be useful to you?

  • ABRP User #811399

    •

    Jun 13

    One of the places where this happens is at the roundabout on Stone Drive Northwest (

    https://www.openstreetmap.org/edit#map=20/47.2744167/-122.5840879). At this location, the road segment going from Eastbay to Stone Drive towards Highway 16 (roughly entering the roundabout on the west side and exiting on the east) was tagged “maxspeed=15 mph.” It looks like that tag was added about 2 years ago, so I don’t think that the tag is solely responsible for the change in ABRP’s behavior (the speed limit there used to be displayed correctly). I changed the tag today to “maxspeed:advisory=15 mph” to see if that fixes the problem. Note that the general problem of speed limits being displayed incorrectly occurs in at least three other places around the Gig Harbor area that I’ve noticed. All of them used to be displayed correctly.