Hi, I use '--generate-sea=extend-sea-sectors,close-gaps=2000,floodblocker' to generate the sea in my map. Between the sea polygones are little gaps. They aren't a problem, but the map looks better without them. Any hints? Gruß Josef -- PGP Schlüssel: 311D1055 http://keyserver.pgp.com
Hi, Am 27.03.2011 17:30, schrieb Josef Latt:
Hi,
I use '--generate-sea=extend-sea-sectors,close-gaps=2000,floodblocker' to generate the sea in my map. Between the sea polygones are little gaps. They aren't a problem, but the map looks better without them.
Any hints?
Concerns lakes, too.
Gruß Josef
-- PGP Schlüssel: 311D1055 http://keyserver.pgp.com
Am 27.03.2011 18:14, schrieb Josef Latt:
Hi,
Am 27.03.2011 17:30, schrieb Josef Latt:
Hi,
I use '--generate-sea=extend-sea-sectors,close-gaps=2000,floodblocker' to generate the sea in my map. Between the sea polygones are little gaps. They aren't a problem, but the map looks better without them.
Any hints?
Concerns lakes, too.
Gruß Josef
Hi Josef, the real reason is unknown. The lines you see are the cuts of the multipolyon processing. I tried to track down that problem but I could not find a problem of mkgmap. So I guess that MapSource does not render it correctly. At least MapSource paints water blue with a little grey border and you see that border at each cut line. WanMil
On 04/03/2011 12:47 PM, WanMil wrote:
the real reason is unknown. The lines you see are the cuts of the multipolyon processing. I tried to track down that problem but I could not find a problem of mkgmap.
Have you tested if it helps to create the cuts at multiples of 2048 in garmin units like the tile borders?
Am 03.04.2011 14:03, schrieb Ralf kleineisel:
On 04/03/2011 12:47 PM, WanMil wrote:
the real reason is unknown. The lines you see are the cuts of the multipolyon processing. I tried to track down that problem but I could not find a problem of mkgmap.
Have you tested if it helps to create the cuts at multiples of 2048 in garmin units like the tile borders?
No I haven't but it will be worth to try it where it is possible. Maybe it reduces the artefacts.
On 04/03/2011 12:47 PM, WanMil wrote:
the real reason is unknown. The lines you see are the cuts of the multipolyon processing. I tried to track down that problem but I could not find a problem of mkgmap.
Have you tested if it helps to create the cuts at multiples of 2048 in garmin units like the tile borders?
Good idea!! Using the multiples of 2048 reduces the artefacts very much. I will post a patch soon. WanMil
Hi Wanmil, Am 03.04.2011 12:47, schrieb WanMil:
Am 27.03.2011 18:14, schrieb Josef Latt:
Hi,
Am 27.03.2011 17:30, schrieb Josef Latt:
Hi,
I use '--generate-sea=extend-sea-sectors,close-gaps=2000,floodblocker' to generate the sea in my map. Between the sea polygones are little gaps. They aren't a problem, but the map looks better without them.
Any hints?
Concerns lakes, too.
Gruß Josef
Hi Josef,
the real reason is unknown. The lines you see are the cuts of the multipolyon processing. I tried to track down that problem but I could not find a problem of mkgmap. So I guess that MapSource does not render it correctly. At least MapSource paints water blue with a little grey border and you see that border at each cut line.
Forgot to write that I use QLandkarteGT. Another thing. The thickness of some gaps change with the zoomlevel. Josef -- PGP Schlüssel: 311D1055 http://keyserver.pgp.com
participants (3)
-
Josef Latt -
Ralf kleineisel -
WanMil