Hi,
Am 09.01.2011 11:55, schrieb Steve Ratcliffe:
Hi
[I'm forwarding the message below as it didn't go out normally as the
picture was too big. I've reduced the image size somewhat.]
Thanks.
The ignore-osm-bounds option really should be removed as ignoring the
bounds is quite likely to
On 1/9/2011 5:55 AM, Steve Ratcliffe wrote:
The ignore-osm-bounds option really should be removed as ignoring the
bounds is quite likely to lead to all sorts of problems. So there is
nothing really wrong here. Why are you using the option?
Regards,
..Steve
Steve,
I use it for test
Hi
I tried it because of this:
'When reading OSM files, ignore any bounds elements.
With this option selected generate-sea sometimes works better,
but routing accross tiles will not work.'
That does seem to give a little too much encouragement to use the option :)
When it was
I use it for test maps that I generate from JOSM files. In such files
there are tons of osmbounds and IIRC mkgmap only uses one of them
(first, last?) and the rest of the data gets thrown out. In that case I
use ignore-osm-bound to ensure all data is used in the map.
Indeed I realise
