[mkgmap-dev] [PATCH v1 + v1] fix overview bounding box rounding + splitter rounding
From Felix Hartmann extremecarver at googlemail.com on Mon Jan 25 22:23:31 GMT 2010
On 25.01.2010 23:20, Mark Burton wrote: > Felix, > > >> So we need the splitter even if the tile needs no splitting. Correct? >> Maybe my problems with the legend map relate to me not passing it trough >> the splitter. Will try out if it makes a difference. >> > A side effect of using the splitter is that it rounds the boundaries of > the tiles. > > So if the boundaries of your map are already correctly rounded and the > map otherwise doesn't need splitting, you don't have to split it. > > But yes, running a map through the splitter is an easy way of rounding > the boundaries (assuming it's doing it right!) > > Mark > The fix to the splitter plus the patches DID it. However why is the map flooded if I don't put an natural=land all around it. I'm using "=polygons" Have you got any idea on this? I think if there is no sea polygon at all, the =polygons code should still create a natural=land on top of the blue background (I already noticed this, so bug is not new, but I assumed it to happen somehow due to the wrong overview map) - Should I open another thread for this? > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev at lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >
- Previous message: [mkgmap-dev] [PATCH v1 + v1] fix overview bounding box rounding + splitter rounding
- Next message: [mkgmap-dev] [PATCH v1 + v1] fix overview bounding box rounding + splitter rounding
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list