You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: sulagaloh [Submitted to the original trac issue database at 4.23pm, Wednesday, 18th December 2013]
Potlatch2 is really a smart tool for editing OSM. I tried iD, but the workflow with that is much slower. So I really would appreciate to get some small enhancements of Potlatch 2 and go on working with the "outdated" software.
My issue is about managing multipolygon-relations. When you draw a grid of ways around different landuse-areas and assign the landuse-tags by multipolygons, the "select all members" function helps a lot to check, if a multipolygon ring is closed or maybe even has an erroneous split.
The way [http://www.openstreetmap.org/way/252236982] carries two mp-s: one landuse=residential, one landuse=farmland.
The table shows:
Relation ID Role
multipolygon 1955526 outer
multipolygon 2329226 outer
When you copy these two mp-s to a new way (like [http://www.openstreetmap.org/way/252236984)] and want to keep only the "farmland"-mp here, it's not easy to see which one is the right to delete. In this example both even end with "26" so it would be nice to get an info in the list (iD functions like this...):
Relation ID Role
multipolygon farmland 1955526 outer
multipolygon residential 2329226 outer
As a hack I used to enter ref-tags for the multipolygons, e.g.
Relation ID Role
multipolygon Felder 1955526 outer
multipolygon Eurishofen 2329226 outer
This helps a lot if you want to pick the right mp at first look. But unfortunately I got battled by an OSM-user who deleted all "inappropriate" use of the ref tag. Maybe he's even right with this, although I think my use of the ref-tag was quite something like a reference.
So here's my proposal:
Please display the text of the following multipolygon's tags in the relations-list, if available. (by this order, name- and ref-tag already implemented)
name
ref
landuse
natural
note
comment
Thank you very much.
The text was updated successfully, but these errors were encountered:
Reporter: sulagaloh
[Submitted to the original trac issue database at 4.23pm, Wednesday, 18th December 2013]
Potlatch2 is really a smart tool for editing OSM. I tried iD, but the workflow with that is much slower. So I really would appreciate to get some small enhancements of Potlatch 2 and go on working with the "outdated" software.
My issue is about managing multipolygon-relations. When you draw a grid of ways around different landuse-areas and assign the landuse-tags by multipolygons, the "select all members" function helps a lot to check, if a multipolygon ring is closed or maybe even has an erroneous split.
The way [http://www.openstreetmap.org/way/252236982] carries two mp-s: one landuse=residential, one landuse=farmland.
The table shows:
Relation ID Role
multipolygon 1955526 outer
multipolygon 2329226 outer
When you copy these two mp-s to a new way (like [http://www.openstreetmap.org/way/252236984)] and want to keep only the "farmland"-mp here, it's not easy to see which one is the right to delete. In this example both even end with "26" so it would be nice to get an info in the list (iD functions like this...):
Relation ID Role
multipolygon farmland 1955526 outer
multipolygon residential 2329226 outer
As a hack I used to enter ref-tags for the multipolygons, e.g.
Relation ID Role
multipolygon Felder 1955526 outer
multipolygon Eurishofen 2329226 outer
This helps a lot if you want to pick the right mp at first look. But unfortunately I got battled by an OSM-user who deleted all "inappropriate" use of the ref tag. Maybe he's even right with this, although I think my use of the ref-tag was quite something like a reference.
So here's my proposal:
Please display the text of the following multipolygon's tags in the relations-list, if available.
(by this order, name- and ref-tag already implemented)
Thank you very much.
The text was updated successfully, but these errors were encountered: