Hi,
while generating index with 2023 I got with some maps this error. Has
someone an idea what went wrong? It happens with my map of Germany and
Denmark, all other maps were ok. Processing of the tiles was fine for
all maps.
Henning
Exception in thread main
Hi steve,
Okay strange, tonight it went through without problems (255M reserved
when starting). Maybe something else was wrong then...
However could you change mkgmap to delete broken mdr files if it crashes
on low memory??
That would be a real troublesaver
I don't know how to find out
Info
i hope, i have correctly changed the Havelberg Islands mapping.
Now the havel-river has two new islands in a multipolygon=riverbank Relation.
i hope it works proper :-)
greetings
ludwich
Am 06.09.2011 um 09:05 schrieb Minko:
Both islands and the riverbank should be part of a
OK. 255 sounds a bit high but shouldn't be a problem all the same.
You may have noticed that I've started a index-memory branch. Currently this
does little more than print out memory use at various point during the process.
It would be useful to run it, particularly if it fails again.
..Steve
Klaus,
this is not possible unless the way has some special tags. So there is
no 'is_in' check in the style system.
I don't know if it is possible to define that graveyards polygons are
painted always on top so that the lines are not visible.
WanMil
Question: Is it possible to avoid the
