logo separator

[mkgmap-dev] Map display squeezed horizontally

From Gerd Petermann gpetermann_muenchen at hotmail.com on Mon Apr 22 06:28:07 BST 2013

Hello Michael,

> 47.15 5.75 55.15 15.15
> 
> This is a lot smaller than the areas covered by the almost empty tiles. 
> Even more, I am splitting the contour lines into parts, none of them 
> consisting of more than 2000 nodes, and then I am using osmosis to cut 
> them to the shape of Germany. I have to use osmosis' parameter 
> completeWays=yes when I am doing this, but even if 1999 out of the max 
> 2000 nodes of a contour line are outside the bounding polygon this 
> should be no more than a few kilometers.
> 
> It's difficult to find the few data inside the huge and almost empty 
> tiles without coastlines and cities, but at
> N 54° 42,0' E 13° 51,0'
> for example there are 3 ferry lines crossing: "Swinoujscie - 
> Trelleborg", "Finnlines" and "Klaipeda - Kiel". All these lines leave 
> the area my map should cover and seem to be included completely.

The question is only the bounding box, because that is used to calculate the 
tiles. So, maybe osmosis calculates a new bbox  on the data in the files.
In that case you should pass a bbox or polygon to osmosis.
> 
> 
> > You can use a polygon file with splitter to make sure that you only get
> > tiles for the wanted area.
> 
> Isn't a line starting inside the bounding polygon and ending outside 
> inluded completely if --keep-complete=false is not set?
yes, sure, but splitter will write tiless with different bounding boxes.
By the way, make sure that you don't use option  --ignore-osm-bounds in mkgmap.

Gerd

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20130422/8d5555e8/attachment.html 


More information about the mkgmap-dev mailing list