
Mark Burton <markb@ordern.com> writes:
I slurped most of I95 into josm and it's a bit of a mess. For example, The Northbound carriageway is disconnected at node 73082202
Perhaps a town boundary - see below.
and just below that is a section of link road that's pointing in the wrong direction.
MassGIS data has the oneway property but not the direction. It was set randomly and is partially fixed. One of the reasons I want routing is to notice these problems - I have fixed a lot of them already.
Various spurious ways are lying around not connected to anything like they are left over from some previous version
That sounds worse than most areas, but agreed it needs fixing.
I did, however, manage to route over 50 km in both directions using mapsource so it can't be completely broken!
Some more data: I was able to route within a town. I found that on a highway between towns that the ways were not connected, and the ends that should have been had nodes with the same coordinates. Almost like boundary nodes at tile boundaries :-) "duplicate node, not connected" is an artifact of the MassGIS data which is segmented by town, so there are nodes more or less on the town border that are duplicated with disconnected ways. At this point I am convinced that 95%+ of my problem is bad data in Mass and not mkgmap. I withdraw my "routing broken in mass" complaint and will see where I am when the mass data is better - there may or may not be residual issues due to excessive node density, but hopefully not. Thanks for all the help and pointers.