Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Supply common dialogs when handling common objects #3904

Open
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Open

Supply common dialogs when handling common objects #3904

openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment

Comments

@openstreetmap-trac
Copy link

Reporter: Pepou
[Submitted to the original trac issue database at 5.18pm, Sunday, 10th July 2011]

With the current Potlatch2 versions (up to 2.2-18-g514f0d2), whenever an "internally unsupported" object (or key or tag or value, please apologize my ignorance) subtype is set (e.g. building=school'' instead of arbitrary ''building=yes), the otherwise excellent tag editor at the left side suddenly mutes into "Not recognized / unknown" information. There are a lot of tag types, where this can happen (and they will probably come drafted and approved faster, than Potlatch2 might be adding exact support for them) and it is impossible to use the dialog's comfort editing possibilities, if someone does know the advanced' texts by heart.

One workaround would be to temporarily change the value to e.g. building=yes'', edit all additional attributes (address, name, etc.) and change back the value to the example ''building=school. Which is a) not obvious for novices under a few weeks of usage, b) not straightforward and comfortable, c) not compatible with newly coming definition at all.

In such case, the upper dialog selector might instead change just to "Arbitrary building type" or "Unknown building type" or "Unknown road/track/etc type", but still supply all slelectors and tabs, which are commonly available for all known (to Potlatch2) building/highway/waterway/landuse/etc. types.

@openstreetmap-trac
Copy link
Author

Author: stevage
[Added to the original trac issue at 5.42am, Friday, 15th July 2011]

A couple of comments:

  1. For this specific case, we should use wildcards so that any "building=*" gets matched. We already support this.

  2. The whole way buildings and various amenities, facilities etc are conflated in Potlatch is a bit broken.

  3. There is probably a broader issue regarding how to handle objects that are partially matched, but if we address 1) and 2), it may become much less important.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant