Hi
Thanks for working out what goes wrong with very small maps.
Although you are correct that the overview map only contains area
definition and background polygons which should not be dropped, in the
future the overview map should contain real map features so it might
be best to specifically
Hi Johann,
first some introduction to the overview map:
It's only used in mapsource.
If you have multiple tiles (for different areas) there is
exactly one polygon (rectangle) for each tile. The name for
the polygon is the name of the tile plus its map name (the
eight digit name).
It has a
Hi,
My current conclusions from both thread parts:
1) I should only disable the SizeFilter (we really, really
don't want to drop any polygon).
2) We should fix DP.
Does that make sense?
Elrond
___
mkgmap-dev mailing list
Hi,
Am 16.06.2009 um 20:39 schrieb Elrond:
My current conclusions from both thread parts:
1) I should only disable the SizeFilter (we really, really
don't want to drop any polygon).
For the overview map obviously not.
2) We should fix DP.
From what you explained about the overview map
Hi,
On Tue, Jun 16, 2009 at 10:49:45PM +0200, Thilo Hannemann wrote:
Hi,
Am 16.06.2009 um 20:39 schrieb Elrond:
My current conclusions from both thread parts:
1) I should only disable the SizeFilter (we really, really
don't want to drop any polygon).
For the overview map obviously
Hi,
okay, first part.
In my testing it turned out, that the SizeFilter and the
DouglasPeuckerFilter either dropped my small rectangles or
converted them to a triangle.
Removing the filters fixed this for me.
If you think, that the generated rectangles should be large
enough, so that they're
Hi,
okay, first part.
In general i find it an good idea to split up a problem into small
parts, but at the moment I cant see the whole thing. Why is it
neccessary break things down to smaller rectangles to get an improvement
in alignment?
Yes, I have seen this error and up to now i
