Commit: r3081: merge from the high-prec-coord branch.
Version mkgmap-r3081 was committed by gerd on Thu, 06 Mar 2014 merge from the high-prec-coord branch. The expected effects are: - improved routing - less distorted lines caused by rounding to map units - smaller map size (~ 10%) because of various optimizations - larger "precompiled" sea and bounds data (~30%) - increased mkgmap run time (~ 10%)
Are there precompiled bounds and sea to download already somewhere? (the ones on mkgmap.org.uk are rather old, and the ones on pleiades are about the same size - hence same old format I assume). On 06.03.2014 08:40, svn commit wrote:
Version mkgmap-r3081 was committed by gerd on Thu, 06 Mar 2014
merge from the high-prec-coord branch.
The expected effects are: - improved routing - less distorted lines caused by rounding to map units - smaller map size (~ 10%) because of various optimizations - larger "precompiled" sea and bounds data (~30%) - increased mkgmap run time (~ 10%) _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
On Thu, Mar 06, Felix Hartmann wrote:
Are there precompiled bounds and sea to download already somewhere? (the ones on mkgmap.org.uk are rather old, and the ones on pleiades are about the same size - hence same old format I assume).
http://osm.thkukuk.de/data/ The size did grow up from 418MB to 624MB for the bounds. Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
thanks a lot. What happens if you use the old files? Mkgmap ran without throwing an error... On 06.03.2014 13:02, Thorsten Kukuk wrote:
On Thu, Mar 06, Felix Hartmann wrote:
Are there precompiled bounds and sea to download already somewhere? (the ones on mkgmap.org.uk are rather old, and the ones on pleiades are about the same size - hence same old format I assume). http://osm.thkukuk.de/data/
The size did grow up from 418MB to 624MB for the bounds.
Thorsten
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
On Thu, Mar 06, Felix Hartmann wrote:
thanks a lot. What happens if you use the old files? Mkgmap ran without throwing an error...
To my knowledge: nothing beside that some point in the near of a boundary could get wrong address tags, since the points are now more precise then the old boundary data is. Thorsten
On 06.03.2014 13:02, Thorsten Kukuk wrote:
On Thu, Mar 06, Felix Hartmann wrote:
Are there precompiled bounds and sea to download already somewhere? (the ones on mkgmap.org.uk are rather old, and the ones on pleiades are about the same size - hence same old format I assume). http://osm.thkukuk.de/data/
The size did grow up from 418MB to 624MB for the bounds.
Thorsten
-- keep on biking and discovering new trails
Felix openmtbmap.org & www.velomap.org
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
Hi,
thanks a lot. What happens if you use the old files? Mkgmap ran without throwing an error...
To my knowledge: nothing beside that some point in the near of a boundary could get wrong address tags, since the points are now more precise then the old boundary data is.
yes, that's all. The old version simplified the areas, the newer doesn't. The size increases so heavily because each point is saved with a 6 bits higher precision (each for lon + lat), and no simplification happens. I think this is not needed for boundary data, but I found no simple way to produce the old result. Gerd
Oh well - there seems to be some problem with the new sea file: java.lang.NullPointerException at uk.me.parabola.mkgmap.reader.osm.SeaGenerator$PrecompData.access$100(SeaGenerator.java:1486) at uk.me.parabola.mkgmap.reader.osm.SeaGenerator.addPrecompSea(SeaGenerator.java:616) at uk.me.parabola.mkgmap.reader.osm.SeaGenerator.end(SeaGenerator.java:847) at uk.me.parabola.mkgmap.reader.osm.OsmReadingHooksChain.end(OsmReadingHooksChain.java:79) at uk.me.parabola.mkgmap.reader.osm.bin.OsmBinMapDataSource.load(OsmBinMapDataSource.java:63) at uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.load(OsmMapDataSource.java:127) at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:167) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:63) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:220) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:216) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) nothing else changed besides using new instead of old sea file. splitter/mkgmap both trunk and latest svn version. (on compiling austria). On 06.03.2014 13:02, Thorsten Kukuk wrote:
On Thu, Mar 06, Felix Hartmann wrote:
Are there precompiled bounds and sea to download already somewhere? (the ones on mkgmap.org.uk are rather old, and the ones on pleiades are about the same size - hence same old format I assume). http://osm.thkukuk.de/data/
The size did grow up from 418MB to 624MB for the bounds.
Thorsten
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
interesting... sea in Austria, that's maybe the issue On Thu, Mar 6, 2014 at 1:26 PM, Felix Hartmann <extremecarver@gmail.com>wrote:
Oh well - there seems to be some problem with the new sea file:
java.lang.NullPointerException at uk.me.parabola.mkgmap.reader.osm.SeaGenerator$PrecompData. access$100(SeaGenerator.java:1486) at uk.me.parabola.mkgmap.reader.osm.SeaGenerator. addPrecompSea(SeaGenerator.java:616) at uk.me.parabola.mkgmap.reader.osm.SeaGenerator.end( SeaGenerator.java:847) at uk.me.parabola.mkgmap.reader.osm.OsmReadingHooksChain.end( OsmReadingHooksChain.java:79) at uk.me.parabola.mkgmap.reader.osm.bin.OsmBinMapDataSource. load(OsmBinMapDataSource.java:63) at uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.load( OsmMapDataSource.java:127) at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile( MapMaker.java:167) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:63) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:220) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:216) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
nothing else changed besides using new instead of old sea file. splitter/mkgmap both trunk and latest svn version. (on compiling austria).
On 06.03.2014 13:02, Thorsten Kukuk wrote:
On Thu, Mar 06, Felix Hartmann wrote:
Are there precompiled bounds and sea to download already somewhere?
(the ones on mkgmap.org.uk are rather old, and the ones on pleiades are about the same size - hence same old format I assume).
The size did grow up from 418MB to 624MB for the bounds.
Thorsten
-- keep on biking and discovering new trails
Felix openmtbmap.org & www.velomap.org
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Well there is Lake Neusiedl - which is entered as sea, Bodensee and some others maybe too? OSM gotten so complex that even some lakes need to be entered as sea (and it makes sense because otherwise lakes on country boundary would be empty or overflowing...). On 06.03.2014 13:33, Enrico Liboni wrote:
interesting... sea in Austria, that's maybe the issue
On Thu, Mar 6, 2014 at 1:26 PM, Felix Hartmann <extremecarver@gmail.com <mailto:extremecarver@gmail.com>> wrote:
Oh well - there seems to be some problem with the new sea file:
java.lang.NullPointerException at uk.me.parabola.mkgmap.reader.osm.SeaGenerator$PrecompData.access$100(SeaGenerator.java:1486) at uk.me.parabola.mkgmap.reader.osm.SeaGenerator.addPrecompSea(SeaGenerator.java:616) at uk.me.parabola.mkgmap.reader.osm.SeaGenerator.end(SeaGenerator.java:847) at uk.me.parabola.mkgmap.reader.osm.OsmReadingHooksChain.end(OsmReadingHooksChain.java:79) at uk.me.parabola.mkgmap.reader.osm.bin.OsmBinMapDataSource.load(OsmBinMapDataSource.java:63) at uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.load(OsmMapDataSource.java:127) at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:167) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:63) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:220) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:216) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
nothing else changed besides using new instead of old sea file. splitter/mkgmap both trunk and latest svn version. (on compiling austria).
On 06.03.2014 13:02, Thorsten Kukuk wrote:
On Thu, Mar 06, Felix Hartmann wrote:
Are there precompiled bounds and sea to download already somewhere? (the ones on mkgmap.org.uk <http://mkgmap.org.uk> are rather old, and the ones on pleiades are about the same size - hence same old format I assume).
The size did grow up from 418MB to 624MB for the bounds.
Thorsten
-- keep on biking and discovering new trails
Felix openmtbmap.org <http://openmtbmap.org> & www.velomap.org <http://www.velomap.org>
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk <mailto: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
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
It is up- and downward compatible. The difference is in the precision of the data. Old files are less precise. Gerd
To: mkgmap-dev@lists.mkgmap.org.uk From: chris66nrw@gmx.de Date: Thu, 6 Mar 2014 13:06:40 +0100 Subject: Re: [mkgmap-dev] Commit: r3081: merge from the high-prec-coord branch.
Am 06.03.2014 08:40, schrieb svn commit:
- larger "precompiled" sea and bounds data (~30%)
So, it's not compatible with old sea and bounds files?
chris
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (6)
-
chris66 -
Enrico Liboni -
Felix Hartmann -
Gerd Petermann -
svn commit -
Thorsten Kukuk