same first expression for lines and polygons (style branch)
Moin, I am using the style branch, so I don't know, whether this is also a problem for the main trunk. In my polygons file have a line like highway=pedestrian & area=yes [0x01 resolution 22] in my lines file I have a line like highway=pedestrian & area=!yes [0x02 resolution 22] With such a style, all the pedestrian lines without the area tag are missing in my map. If I change the polygon file to area=yes & highway=pedestrian [0x01 resolution 22] both the areas and the lines get into my maps. Gruss Torsten
Torsten Leistikow wrote:
Moin,
I am using the style branch, so I don't know, whether this is also a problem for the main trunk.
In my polygons file have a line like
highway=pedestrian & area=yes [0x01 resolution 22]
in my lines file I have a line like
highway=pedestrian & area=!yes [0x02 resolution 22]
With such a style, all the pedestrian lines without the area tag are missing in my map.
If I change the polygon file to
area=yes & highway=pedestrian [0x01 resolution 22]
both the areas and the lines get into my maps.
that does look like the old bug of != that was not working correctly bug got fixed (however probably too late for the style-branch fork). Still there are issues with !. For example & ( key!=value | key2!=value ) cannot be used (also tries like & !(key=value | key=value) are not usable so only possible way is to use & key!=value & key2!=value ... Currently there is no possibility to get an object into both polygon and line (even with the multiple garmin elements patch / "continue" )
Gruss Torsten _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Felix Hartmann schrieb:
that does look like the old bug of != that was not working correctly bug got fixed (however probably too late for the style-branch fork). Still there are issues with !. For example & ( key!=value | key2!=value ) cannot be used (also tries like & !(key=value | key=value) are not usable so only possible way is to use & key!=value & key2!=value ...
Might be, that this is the source of the problem. I just thought, that the first expression was the reason, because switching the order worked.
Currently there is no possibility to get an object into both polygon and line (even with the multiple garmin elements patch / "continue" )
Actually in this example I want to have either the polygon or the line. But in general I do not have any problems with creating both elements from one single object. For example I have an object barrier=fence and acces=no. In my map I get the line for the fence as well as the whole area drawn as not accessible. Gruss Torsten
Torsten Leistikow wrote:
Felix Hartmann schrieb:
that does look like the old bug of != that was not working correctly bug got fixed (however probably too late for the style-branch fork). Still there are issues with !. For example & ( key!=value | key2!=value ) cannot be used (also tries like & !(key=value | key=value) are not usable so only possible way is to use & key!=value & key2!=value ...
Might be, that this is the source of the problem. I just thought, that the first expression was the reason, because switching the order worked.
Currently there is no possibility to get an object into both polygon and line (even with the multiple garmin elements patch / "continue" )
Actually in this example I want to have either the polygon or the line.
But in general I do not have any problems with creating both elements from one single object. For example I have an object barrier=fence and acces=no. In my map I get the line for the fence as well as the whole area drawn as not accessible.
that is no problem because the wording is different. but it would be impossible for example to render riverbank=yes both as line and as polygon (line before polygon, so if in lines file there is a rule riverbank=yes you can't have it in polygon file, even if you set continue in the line file).
Gruss Torsten _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Clinton Gladstone schrieb:
On Nov 6, 2009, at 17:55, Torsten Leistikow wrote:
highway=pedestrian & area=!yes [0x02 resolution 22]
Should that not be != instead of "=!"?
Yes, sure. That typing error is not in my style, it is just in the e-mail. Gruss Torsten
participants (3)
-
Clinton Gladstone -
Felix Hartmann -
Torsten Leistikow