Version 1598 was commited by steve on 2010-03-06 13:42:30 + (Sat, 06 Mar
2010)
v3 of the patch is taken from r1596.
I have slightly modified it compared to v2. Just some minor improvements and
the merging to the patches that have been already committed.
Summary: Reduce number of cuts in
I have run several times splitter on a 15.1 GB file (actually on cache
from that file) obtained from Srtm2OSM on machine A (Athlon 64 3000 Ghz,
3GB RAM) using the following command:
time java -Xmx2500M -jar splitter.jar --mapid=63240101 --mixed=true
--cache=/160GB/cache_srtm/peninsula/
Hi Dani,
What have I to put i which file so that routing goes not across
unpaved tracks?
Please look at the default style, resources/style/default/lines, for
mkgmap:unpaved=1, and set Avoid unpaved roads in the routing options
on your device.
Side note: I wish there were a widely used
Hi Daniela,
Hi!
One street shoes a gap that does not seem to be in the osm data:
http://www.deltadelta.de/nmz/sc21.png
vs.
http://www.openstreetmap.org/?lat=48.08617lon=11.50167zoom=17layers=B000FTF
I tried to navigate to the Bad Forstenrieder Park. Since one can not
pass this gap,
Hi!
When I select in my Garmin device: Find - Shopping - (Menu) Select
Category, I get a list of categories. At the end of the list I have
currently 9 times other. But each other category summarizes just one
sort of shops (modulo tagging errors). Is there a possibility to change
the other
Hi Marko!
Please look at the default style, resources/style/default/lines, for
mkgmap:unpaved=1, and set Avoid unpaved roads in the routing options
on your device.
Now it hops also over the gap. Funny, the now chosen route is also much
shorter than the first one. :-))
Thanks a lot!
Mark Burton escribió:
Hi Carlos,
I don't know the answer to your problem but I note that you are using a
different VM on machine B. I would have thought it was worth trying the
same VM as used on machine A.
Using sun java as in machine A fixed the problem for splitter, although
mkgmap still
Carlos,
Using sun java as in machine A fixed the problem for splitter, although
mkgmap still needs a slightly higher amount of memory. May it be due to
--max-jobs?
Sure, if you have more cores available than before, --max-jobs will
process that number of maps in parallel so it will take more
