Opened 12 years ago
Closed 6 years ago
#8663 closed enhancement (fixed)
preset: object type "closedway" should not be included in type "way"
| Reported by: | skyper | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | latest |
| Keywords: | preset | Cc: |
Description
The object type closedway is include in type way but it makes more sense to use them as two different objects in order to distinguish between areas and linear objects.
Attachments (0)
Change History (10)
comment:1 by , 12 years ago
| Version: | → latest |
|---|
comment:2 by , 12 years ago
comment:3 by , 12 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:5 by , 12 years ago
| Resolution: | wontfix |
|---|---|
| Status: | closed → reopened |
comment:6 by , 12 years ago
| Type: | defect → enhancement |
|---|
follow-up: 8 comment:7 by , 10 years ago
The behaviour did change and closed ways are no longer part of way. Not sure if it was intended though. Personally I do not have one favourite solution but I understand that excluding closed ways explicitly might have some advantages.
comment:8 by , 10 years ago
Replying to skyper:
The behaviour did change and closed ways are no longer part of
way. Not sure if it was intended though. Personally I do not have one favourite solution but I understand that excluding closed ways explicitly might have some advantages.
Is the solution now accepted and we can close this ticket ?
comment:9 by , 10 years ago
comment:10 by , 6 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
No. There always will be cases where closed ways aren't areas. Excluding closed ways from ways would result in very strange behaviour, which users will hardly understand.