KSevcik Posted February 19, 2021 Share Posted February 19, 2021 Description: Was planning a longer route to Morgan City, St Mary, LA, USA, and ABRP routed it strangely. I started poking and it looks like ABRP doesn't believe a chunk of US 90 exists. Type: Webpage planned Link to Plan: https://abetterrouteplanner.com/?plan_uuid=151a8e38-3bdf-4757-be2d-bebca55b01d5 Replication Steps: Click plan link As you can see on the plan, the route only approaches the waypoints on the road, but never routes on the road. Here's a link to part of that highway on OSM: https://www.openstreetmap.org/way/117379972#map=17/29.70142/-91.38017 It's listed as a Trunk Road? Not sure if that's relevant, but the problematic section is where it changes from "motorway" to "trunk". Link to comment Share on other sites More sharing options...
CBenson Posted February 22, 2021 Share Posted February 22, 2021 This really looks to me to be a coding issue in OSM: https://www.openstreetmap.org/directions?engine=fossgis_osrm_car&route=29.72338%2C-91.40956%3B29.69412%2C-91.34048#map=10/30.0487/-91.5076 But I can't figure out what's wrong or how to fix it. Link to comment Share on other sites More sharing options...
KSevcik Posted February 23, 2021 Author Share Posted February 23, 2021 So I've figured out the issue, but I don't know OSM etiquette for fixing it. The issue is that whole stretch has the tag proposed=motorway. I assume because someone thinks that's how to tag it as a proposed upgrade to the existing highway? But this breaks OSRM, per taginfo's notes on the proposed=motorway tag: I assume the fix is to just delete the proposed=motorway tag, but I've never (yet) edited OSM, and don't know if that info should be shunted to some other tag/feature. I guess the other fix is for OSRM to switch to whatever OSMaxx is doing and only ignore ways that are highway=proposed. But I expect that's a heavier lift than just fixing the data in OSM. Link to comment Share on other sites More sharing options...
KSevcik Posted February 23, 2021 Author Share Posted February 23, 2021 Alright, I created an OSM account and deleted the tag myself. I'm assuming that will fix it when the change propagates. Also looks like I've collected a new hobby to amuse myself with at lunch. 1 Link to comment Share on other sites More sharing options...
CBenson Posted February 27, 2021 Share Posted February 27, 2021 Impressed by your identification and fix of the issue in OSM. I'm wondering why ABRP still won't route there. Link to comment Share on other sites More sharing options...
KSevcik Posted March 1, 2021 Author Share Posted March 1, 2021 I'm wondering that myself. They say they update from OSM weekly, so maybe it hasn't gotten pulled yet. I'm giving it a few more days before I start worrying about it. Link to comment Share on other sites More sharing options...
CBenson Posted March 11, 2021 Share Posted March 11, 2021 Still wondering why this routes the long way around. Link to comment Share on other sites More sharing options...
KSevcik Posted March 12, 2021 Author Share Posted March 12, 2021 Ditto. It's still fixed in OpenStreetMaps. At this point I think this needs someone with more in depth knowledge of when/how ABRP is pulling the data and what they're using for routing. Maybe a minor change like that wasn't enough to trigger an update? Link to comment Share on other sites More sharing options...
KSevcik Posted March 14, 2021 Author Share Posted March 14, 2021 And I randomly checked again today and it's fixed. Unless someone shows up to inform me otherwise, I guess I'm going to assume OSM edits take 3ish weeks to propagate. 1 Link to comment Share on other sites More sharing options...
