Opened 14 years ago
Closed 13 years ago
#5953 closed defect (fixed)
[Patch] groynes are always considered as "areas"
Reported by: | kellerma | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core validator | Version: | latest |
Keywords: | Cc: |
Description
Adding the tag "man_made=groyne" to a non-closed way leads to
a) immediately an area displayed
b) an error-message generated by the validator
However according to "Tag:man_made=groyne" in the wiki it's possilbe to have
non-closed ways as groynes so neither a) nor b) should happen.
Attachments (3)
Change History (8)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
The same error we see for "leisure=track": shouldn't be an area.
Thank you.
by , 14 years ago
Attachment: | 5953.patch added |
---|
by , 14 years ago
Attachment: | 5953_v2.patch added |
---|
comment:3 by , 14 years ago
Summary: | groynes are always considered as "areas" → [Patch] groynes are always considered as "areas" |
---|
This is due to some definitions in elemstyles.xml. The attached patch (_v2) resolves this issue for man_made=groyne as well as leisure=track.
comment:4 by , 14 years ago
This patch is wrong, Dropping area is an bug. You simply need to set closed="true", so unclosed ways aren't seen as area for this type anymore.
by , 14 years ago
Attachment: | 5953_v3.patch added |
---|
Correction: according to wiki-page "Map_Features" groynes can be ways as well areas.