[mkgmap-dev] [PATCH v3] - Sub-optimal fix to limit excessive inter-node arc length

Tue Apr 28 13:59:38 BST 2009

Hi Mark,

On Tue, Apr 28, 2009 at 12:52:50PM +0100, Mark Burton wrote:
> What's wrong is that that way has a single segment that is too long for
> us to handle with the present code. If the code was smarter it could
> split that segment into chunks that were small enough to not cause a
> problem by just adding extra points. I don't have much spare time at the
> moment so I can't look at that right now but I will happily look at it
> in the future if no-one else beats me too it. If you can identify the
> way in question, just add some points to reduce the size of the segment.

I identified it with this patch:

+               String wayName = way.getName(); // only use for diagnostic messa
ges
+               if(wayName == null) {
+                       wayName = way.getTag("ref");
+                       if(wayName == null)
+                               wayName = way.toString();
+               }

The way.toString() spits out the latitude and longitude, among other
things:

SEVERE (StyledConverter): Way WAY: null(67.09045886993408/23.672125339508057) [note=In public domain (original Kekoil work),note=*,source=Landsat,source=*,highway=unclassified,highway=*] contains a segment that is longer than 16383 (routing will fail for that way)

With JOSM, I determined that it probably is this way:

http://www.openstreetmap.org/browse/way/24731243/history

Could the error message disclose the unit? 16383 doesn't say anything to me.
How could the problem be fixed in the map data? Split the way into two in
the middle?

If this only affects the routing along this way, I think I will just ignore
it for now.  It seems to be a minor road in the almost unpopulated areas of
Finland.

	Marko