
Hi Clinton,
I'll look at the fragment and see if the problem looks similar to the one I described.
Thanks.
In the meantime this error is giving me a lot of grief:
- The JOSM routing plugin works fine on the route. - Validator does not return anything significant. - The highway where the error occurs is all one segment. Splitting it does not help.
My hunch is that the data is OK but we're encoding it wrong for some reason.
The only thing that corrects the error is to recreate the highway node by node. There must be something in the data which JOSM does not display, which causes the error. I'll try to reduce the osm extract to a reasonablehe size in order to see if anything is noticeable.
Thanks for your (and everyone else's) help.
Certainly, a small example that exhibits the problem would be very useful. The reason why I think the encoding is wrong is because when I experimented with using smaller limits on the number of points in a line, some of these problems went away. Cutting the line into smaller segments doesn't change the position of the points but, somehow, it made a difference. Cheers, Mark