I had a look at about 10 problem areas around my home in Chiang Mai NW Thailand and in every case it was just a small soi (road/lane) that just stopped.
There were certainly no “breaks” in the road.
Great idea for a tool though, nice work.
But I think to be useful the algorithm may need to be changed to decide what actually is a broken road.
thanks for the tool. I looked at some places in the South where I traced a lot from Bing. And yes: some “broken” roads are my work. In a Southern country, there are some clouds on the sky on every day, and some areas could not be traced due to the clouds. I decided to trace the visible parts of the roads nonetheless, they are useful for those people who are on some tracks nearby and try to find a road. With GPS tracks from my last holiday, I’ll likely fix some of them.
Thanks for the tool. I tried about 10 in and around Khon Kaen where I live and map. All false positive. JOSM validator is handy, good and gets them all before upload. Think I’ll stick to JOSM validator.
In Thailand there are a lot of highways obviously drawn by a major license change decliner from Bing without local knowledge. When I came across them during my mapping or my special cleanup of the Northeast I replaced them as time and local knowledge allowed. But there are still some or may be many which I left disconnected when enhancing or replacing major roads. They are unclassified, residential or tracks. They are sometimes disconnected, created by the disagreer and contain only or almost only nodes from the disagreer. I think they should be replaced or deleted in the automatic cleanup. Just reconnecting them would not improve the map but add to the expected automatic cleanup.
How often do you update your map? Does it evaluate the layer tag or noexit?
In case a road is a dead-end it might be wise to place a noexit tag on the last node. In case there is a footpath leading out that section of the way should be drawn and tagged accordingly. Somewhere in the (far) future we might have pedestrian routing.
stephankn, OSM inspector doesn’t do analysis of the whole routing graph. It just finds all the end nodes of lines, probably checks for noexit= tags, and finds out whether there are unconnected candidates.
Basically, for navigation purposes, there should always be a way from one higher-level to another higher-level road that will not make you go through service one. If it is the only way, then this road isn’t “service” one, it’s a higher class road.
I had a look at some of the road “islands” in Thailand. Mostly it’s residential roads connected to a lower class road, track, …
It might be worth checking the issues.
How often is your site updated? I came up with a lot of ways which looked already fine.
Actualy situations when residential roads are connected to a road network via track is only a minority of all cases. The majority is obvious topological errors - roads are not connected by common nodes, because they were potlached or a mapper just did not bother to connect them.
Here is an ilustration:
Roads cross, but do not intersect. Boxed roads are inaccessible for routing engines.