In any case this shouldn't be a warning message IMHO, but an info message. That way real warnings could be logged without junk (junk from a position of simply rendering the map, without wanting to solve problems on the input - so if you not only create one map, but plenty to offer for download)... but the proposal is IMHO much better - but please as info and not as warning. (Warnings should be buffer overruns, tiles failing to compile due to various reasons, out of memory, and such grave errors). On 15.01.2013 12:12, GerdP wrote:
Hi,
I wonder if this message is really useful. I see this typically for large shapes, the last example from Thorsten has two identical large shapes (the island Rügen) http://www.openstreetmap.org/browse/relation/54400
The message is printed because area.getEstimatedSizes() returns values that are higher than some limits. The problem: area.getEstimatedSizes() ignores the filters which are used to reduce the number of points, so the error message may be printed without any reason.
I think it would be better to do something like this: oldPos = buffer.getPosition() add the shape bytes = buffer.getPosition() - oldPos; if (bytes > LIMIT) { print error message }
This would also allow to report the name of the shape that is probably corrupted. Of course, the same can be done for ways or node.
What do you think?
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/Why-do-we-have-the-Area-too-small-to-split-at... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org