Hello Felix, ok, I think I understand the problem. Did you try using something like osmfilter to delete data which is not needed before using splitter? Would that be an option? Gerd Felix Hartmann-2 wrote
The problem are tiles with loads of nodes, that are not used by default style (or I think virtually most styles, except maybe openseemap). So you end up with mkgmap rendering 1 or 2 tiles, with say 10 nodes only (if at all). On 20.11.2012 16:21, GerdP wrote:
Felix Hartmann-2 wrote
Well, split France and then I think it is obvious, why there are problems (especially as if you choose a low maxnodes value for france, you still produce maps that crash Garmin GPS devices, once installed/active)... Well, I don't want to crash my GPS ;-) If I split france (an older extract) with maxnodes=1000000 I see messages like this: Area (43.5498046875,1.23046875) to (43.7255859375,1.40625) contains 1.013.349 nodes but can't be split further
Is that the obvious problem you are talking about? If I got this right, you have to use a higher resolution to fix that (with my extract, resolution=14 was enough. I don't know what you have to change in mkgmap settings to work with that.
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/splitter-r239-tp5736433p5736622.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- keep on biking and discovering new trails
Felix openmtbmap.org & www.velomap.org
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/splitter-r239-tp5736433p5736738.html Sent from the Mkgmap Development mailing list archive at Nabble.com.