Hi all,
I wonder what splitter should do in this case:
Stephen uses paramter --max-nodes=80000
and splitter reports
"Highest node count in a single grid element is 557,084"
It is obvious that at least one tile will have much more than the requested
80.000 nodes,
on the other hand, the file africa.osm.pbf contains large nearly empty areas,
and that makes it very difficult to find a good split.
The current version r416 fails because it doesn't accept tiles with less than
5% of
the max-nodes value, so it searches for a solution where every tile has at
least 4000 nodes,
and that might not exist.
I see these options:
1) splitter can continue trying to split the data, accepting almost empty
output files
(e.g. some with < 5 nodes and very high aspect ratios like 32)
2) if that fails, splitter can set the max-nodes value to 557,084 and try again
3) or stop with an error message that tells the user that it is not possible
to split with the used resolution
4) or restart using a higher resolution (15 would be required here instead of
13),
@Stephen
What reason do you have to use such a small max-nodes value?
Would it be ok for you to use a higher one?
Gerd
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
