Hi, I just discovered a bug (this is happening on both trunk as well as
style-speed).
This rule is applied twice if both mtb:scale and mtb:scale:uphill are
present:
( mtb:scale=* | mtb:scale:uphill=* ) { set name='${name}
M${mtb:scale}${mtb:scale:uphill}' | '${name} M${mtb:scale}.' | '${name}
On 04/02/10 16:32, Felix Hartmann wrote:
Hi, I just discovered a bug (this is happening on both trunk as well as
style-speed).
Yes it sounds familiar.
I'll add the following test.
WAY
highway=road
mtb:scale=2
mtb:scale:uphill=yes
lines
( mtb:scale=* | mtb:scale:uphill=* )
{ set
Version 1555 was commited by marko on 2010-02-03 11:41:06 + (Wed, 03 Feb
2010)
Ignore multipolygons with fewer than 2 resolved elements.
I have doubts if that's a good idea.
If multipolygons are splitted by splitter it is possible that some
polygons are dropped because they are not
Version 1560 was commited by marko on 2010-02-04 20:30:44 + (Thu, 04 Feb
2010)
Revert r1555 after WanMil's feedback.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Thu, Feb 04, 2010 at 08:50:49PM +0100, WanMil wrote:
I have doubts if that's a good idea.
If multipolygons are splitted by splitter it is possible that some
polygons are dropped because they are not inside the tile bounds.
This makes it possible that the outer ring survives only.
The
On Thu, Feb 04, 2010 at 08:50:49PM +0100, WanMil wrote:
I have doubts if that's a good idea.
If multipolygons are splitted by splitter it is possible that some
polygons are dropped because they are not inside the tile bounds.
This makes it possible that the outer ring survives only.
The
The definition of the multipolygon says that the tags from the
multipolygon are used for the outer polygons (Tags describing the
multipolygon (e.g. landuse=forest) should go on the relation. The outer
way(s) should be left untagged, unless they describe something in their
own right.). If
