There’s a rural road near my home that OSM shows incorrectly. A bridge was destroyed 40+ years ago and never rebuilt, but OSM shows the road as going through. I used the ID editor to remove the points on the road back to where I know from first-hand knowledge that the road stops.
But, looking at the map (N35.551969/W98.609306), it still shows the underlying road (CR E1010) going for about 1km. I can’t use the query tool to select it and see its properties. Where does that come from and how do I make it match reality?
Here is the changeset from my edits last week:
If you zoom in and out, that underlying road appears like parts of it are missing. Is this something I need to edit as well as the points?
From what I can tell, your edits seem to have worked to shorten the road. What’s likely going on is you’re still seeing the map from before you edited the road. You can refresh the page and clear the cache by pressing Ctrl + F5, and that will probably show your changes.
When I look at it on a web browser or in JOSM it looks like your edits were successful. So I agree with @dylfitt that it is likely that your browser has cached the map tile files and if you refresh your browser’s cache you should see the new version.
Good grief. I should know better than that, I run web projects as my day job. I’m forever telling people to clear cache when testing features.
Anyway…
When I opened in a private tab, I see my edits, but at zoom level 16 (100m), I still see that road underneath. I think it’s the layers view. Perhaps those are regenerated on a less-frequent basis.
The point to note is that the geometry was imported in the early days of OSM from the Tiger dataset. So the error can’t be directly attributed to hallucinating by OSM
It is probably a good idea to update/remove the relevant tiger tagging whatever the US community thinks that is current best practice. Naturally fixing any other local issues with the data would be a welcome contribution too.
