Could easily be a novice mistake, but these two waypoints are about 3 meters apart, and yet I haven’t been able to route a course between them that is less than 57km.
This happens in multiple routing apps, which makes me think it’s a problem with the underlying osm data.
I believe the fix would be to mark the trails as having an intersection (as in one of them not being on an overpass) for routing algorithms to be able to find the 4m route instead of the 57km one, is that correct? How can I mark them as intersecting? When I query features at an intersection I don’t see anything that marks them as a place where you can or can’t transfer from one road to the other.
I found that after selecting the path it suggested some issues, one of which was that the paths may be connected. I have submitted an edit to do just that.
I’m guessing this is resolved!
I am happy you found the solution.
Please note, that depending on the application the changes may appear with a delay of hours or months. So it might take a while until the routing is fixed.
Oh wow. I checked “I would like someone to review my changes”. Is there a long backlog for change reviews? I’m tempted to submit another change that doesn’t have that checked if it won’t mess stuff up but might make the change live sooner…
Review is not blocking. It’s just a flag for local mappers who might want to check beginner’s work.
yes, indeed, all edits that you upload become instantly live, the review checkbox is just a “flag”, asking the community to review your edit, but there is no “queue” (AFAIK): sometimes the review will happen soon after, but sometimes also after months or never.
Note that one of the two ways is a footway (not allowing bicycles), the other is a path (allowing bicycles).