Yes thank you, I reproduced that now with 4mio nodes a tile 2/210 were
too large
Understood
Am 12.11.2016 um 23:40 schrieb Carlos Dávila:
Right, then you'll receive something like this:
GRAVE (MapFailedException): usa/60248060.o5m: (thrown in
BufferedImgFileWriter.ensureSize()) There is not e
Right, then you'll receive something like this:
GRAVE (MapFailedException): usa/60248060.o5m: (thrown in
BufferedImgFileWriter.ensureSize()) There is not enough room in a single
garmin map for all the input data. The .osm file should be split into
smaller pieces first.
Number of MapFailedExcep
I am guessing that
Number of MapFailedExceptions: 0
Number of ExitExceptions: 0
would be non zero, if I choose to high nodecount in one tile?
Am 12.11.2016 um 10:05 schrieb Gerd Petermann:
Hi Jakob,
Jakob Mühldorfer-2 wrote
* Does the splitter print an error when max-nodes is too larg
Hi Jakob,
Jakob Mühldorfer-2 wrote
> * Does the splitter print an error when max-nodes is too large, or is
> it unpredictable and will it only fail on the GPS device
No. There is no specific limit on the number of nodes in the device, the
value is just an easy to calculate number which exp
Hi,
I tried to read all the docs and forums about max-nodes, but I still
have questions left:
* Does the splitter print an error when max-nodes is too large, or is
it unpredictable and will it only fail on the GPS device
* Do tiles with more nodes mean higher or lower draw performance on
