Hi, On Thu, Feb 10, WanMil wrote:
I have fixed that in r1838 but I cannot test if it works with IBM java. Maybe you want to test it and give a feedback if the fix works.
Thanks for the fix! It's now working with IBM Java and SUN Java. But after my tests I will stay with SUN Java: For some to me unknown reasons, it is much faster (factor 10 or more). But the result is still not exactly what I need: on some tiles the sea is now blue, on others it still has the color of land. If you move the mouse on it, the garmin device is telling you it's "sea", so only the color is wrong. Needs to play much more with it... Thorsten
Hi,
On Thu, Feb 10, WanMil wrote:
Thorsten,
which JRE are you using? This error should not happen with a Sun(Oracle) JRE 1.6.0_23.
It's IBM Java:
java version "1.6.0" Java(TM) SE Runtime Environment (build pxa6460sr9-20101125_01(SR9)) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr9-20101124_69295 (JIT enabled, AOT enabled)
Will try now with SUN Java, never thought about that.
Thorsten
I'm building my own OSM map for Garmins since quite some time, but now I wanted to fix the issue, that the sea isn't drawn correctly. For this I played with the generate-sea option. But independent to which value I set this option, I always get this java error after quite some time:
java.lang.ClassCastException: java.util.TreeMap$1 incompatible with java.util.NavigableSet at uk.me.parabola.mkgmap.reader.osm.SeaGenerator.createInnerWays(SeaGenerator.java:518) at uk.me.parabola.mkgmap.reader.osm.SeaGenerator.end(SeaGenerator.java:337) at uk.me.parabola.mkgmap.reader.osm.OsmReadingHooksChain.end(OsmReadingHooksChain.java:78) at uk.me.parabola.mkgmap.reader.osm.xml.Osm5MapDataSource.load(Osm5MapDataSource.java:73) at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:145) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:56) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:220) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:217) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314) at java.util.concurrent.FutureTask.run(FutureTask.java:149) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919) at java.lang.Thread.run(Thread.java:736) Exiting - if you want to carry on regardless, use the --keep-going option
I tested snapshot 1812 and 1829.
Any idea what causes this and how to fix/workaround this?
Thanks, Thorsten _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg)