Hi, I create my own map with OSM data for Germany from geofabrik (http://download.geofabrik.de/osm/europe/germany.osm.bz2) and the following setting. java -ea -Xmx2560M -jar mkgmap.jar \ --description=OSM_DE \ --country-name=Deutschland --country-abbr=DE \ --name-tag-list="name:de,name,int_name" \ --style-file=./mkgmap-style/ \ --generate-sea=multipolygon,extend-sea-sectors,close-gaps=1000 \ --family-id=1331 --product-id=1 \ --series-name=OSM_Deutschland \ --family-name=OSM_Deutschland \ --area-name=Deutschland \ --overview-mapname=OSM_Deutschland \ --tdbfile \ --draw-priority=25 \ --latin1 \ --ignore-maxspeeds \ --ignore-turn-restrictions \ -c template.args 1331.TYP As you can see in the attached screenshot, there is a region, which is overlapped by the sea. Is this a problem of mkgmap? Thanks Josef
Some days ago there was a report of an bad coastline in this region (german forum or talk-de, I don't remember exactly). But I thought it was already fixed. Maybe you should download an new extract. aighes -- View this message in context: http://gis.638310.n2.nabble.com/Option-generate-sea-buggy-tp5642279p5642516.... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Am 16.10.2010 20:27, schrieb aighes:
Some days ago there was a report of an bad coastline in this region (german forum or talk-de, I don't remember exactly). But I thought it was already fixed. Maybe you should download an new extract.
I tried it with several extracts after the fix. The screenshot is from the extract yesterday. Josef
On Sun, Oct 17, 2010 at 08:34:42AM +0200, Josef Latt wrote:
I tried it with several extracts after the fix. The screenshot is from the extract yesterday.
Did you enable the logging and search for any coastline warnings in the log? Something like this should do the trick: java -Xmx1024m -ea -Dlog.config=logging.properties -jar mkgmap.jar ... grep -i coastline mkgmap.log.0 You can get a logging.properties file from http://www.polkupyoraily.net/osm/ or more specifically at http://www.polkupyoraily.net/osm/files/logging.properties Best regards, Marko
On Sun, Oct 17, 2010 at 08:33:10 BST 2010, Marko Mäkelä wrote:
I tried it with several extracts after the fix. The screenshot is from the extract yesterday.
Did you enable the logging and search for any coastline warnings in the log?
Something like this should do the trick: java -Xmx1024m -ea -Dlog.config=logging.properties -jar mkgmap.jar ... grep -i coastline mkgmap.log.0
You can get a logging.properties file from http://www.polkupyoraily.net/osm/ or more specifically at http://www.polkupyoraily.net/osm/files/logging.properties
The log shows only one problem with coastline but not in this region. It's here: http://www.openstreetmap.org/?lat=53.7711&lon=14.2342&zoom=12&layers=M Josef
Maybe it's caused by the geofabrik extract of germany.osm because I notice the same problems happen for the same region (near Emden) if I use the Benelux abstract from planet.openstreetmap.nl For my Benelux maps I have use the europe.osm extract from geofabrik and then split it with a wider border area. (It was me who reported an error with the coast line on the openstreetmap forum, but this has already been fixed last week). Maybe the German extract has a border area that is too small so some coastlines get broken?
On Sun, Oct 17, 2010 at 09:17:33PM +0200, Minko wrote:
Maybe it's caused by the geofabrik extract of germany.osm because I notice the same problems happen for the same region (near Emden) if I use the Benelux abstract from planet.openstreetmap.nl For my Benelux maps I have use the europe.osm extract from geofabrik and then split it with a wider border area.
My workaround for this problem is to move the endpoints of the coastline to the tile borders. This is part of my osm2img.sh script: bzip2 -dc "$OSM_BZ2"| perl -e \ 'my $del=0; while(<>){ $del=1 if (/<relation.* version="1".* user="usm78-gis"/); s/(<node id="28954644".*lat=)"60\.51564"/$1"59.326172"/; s/(<node id="29193143".*lon=)"24\.12826"/$1"19.072266"/; print unless $del; $del=0 if m|</relation>|; }'| tee "$OSM"| $JAVACMD $JAVACMD_OPTIONS -jar splitter.jar --split-file=areas.list
Maybe the German extract has a border area that is too small so some coastlines get broken?
That should be easy to check. Just extract the natural=coastline ways from the German extract with Osmosis, and load the result in JOSM. That is how I fixed the generate-sea for my map of Finland. Something like this should do the trick: osmosis --rx germany.osm --tf accept-ways natural=coastline --used-node --wx germany-coastline.osm Marko
Am 18.10.2010 09:33, schrieb Marko Mäkelä:
On Sun, Oct 17, 2010 at 09:17:33PM +0200, Minko wrote:
Maybe it's caused by the geofabrik extract of germany.osm because I notice the same problems happen for the same region (near Emden) if I use the Benelux abstract from planet.openstreetmap.nl For my Benelux maps I have use the europe.osm extract from geofabrik and then split it with a wider border area.
My workaround for this problem is to move the endpoints of the coastline to the tile borders. This is part of my osm2img.sh script:
bzip2 -dc "$OSM_BZ2"| perl -e \ 'my $del=0; while(<>){ $del=1 if (/<relation.* version="1".* user="usm78-gis"/); s/(<node id="28954644".*lat=)"60\.51564"/$1"59.326172"/; s/(<node id="29193143".*lon=)"24\.12826"/$1"19.072266"/; print unless $del; $del=0 if m|</relation>|; }'| tee "$OSM"| $JAVACMD $JAVACMD_OPTIONS -jar splitter.jar --split-file=areas.list
Sorry, this is to high for me.
Maybe the German extract has a border area that is too small so some coastlines get broken?
That should be easy to check. Just extract the natural=coastline ways from the German extract with Osmosis, and load the result in JOSM. That is how I fixed the generate-sea for my map of Finland. Something like this should do the trick:
osmosis --rx germany.osm --tf accept-ways natural=coastline --used-node --wx germany-coastline.osm
As Minko I use now europe.osm and cut out a rectangular piece with osmosis. Map is now good. The disadvantage is, that I have to download 5,4 GB instead of 1 GB and creating the map takes half a day instead of one and a half hours. I wrote the problem to geofabrik. Thanks Josef
Hi Josef, Do you use the bzip2 or the pbf binary format? The pbf is smaller (3,6gb) and it doesn't take that much time to cut out an extract for the benelux with osmosis. Josef wrote: As Minko I use now europe.osm and cut out a rectangular piece with osmosis. Map is now good. The disadvantage is, that I have to download 5,4 GB instead of 1 GB and creating the map takes half a day instead of one and a half hours. I wrote the problem to geofabrik. Thanks Josef _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (4)
-
aighes -
Josef Latt -
Marko Mäkelä -
Minko