Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iD create one-member relation for node-POI #3812

Closed
stephankn opened this issue Feb 1, 2017 · 4 comments
Closed

iD create one-member relation for node-POI #3812

stephankn opened this issue Feb 1, 2017 · 4 comments
Assignees
Labels
usability An issue with ease-of-use or design validation An issue with the validation or Q/A code
Milestone

Comments

@stephankn
Copy link

I observe multiple instances of this weird tagging. All have in common that a new POI was added, typically only a node.
Weird is that this single node is then the only member of an untagged relation.

Either iD accidentally creates this or the UI makes it easy for the user to do such unintended mistakes in editing.

Version observed: iD 1.9.7
Example: https://www.openstreetmap.org/changeset/42664446

@tyrasd
Copy link
Member

tyrasd commented Feb 1, 2017

I believe this must happened by the user clicking on the large "+" button in the "all relations" section, and then selecting "new relation" without then selecting one of the presets (e.g. aborting the process by selecting another object).

There are two three potential improvements:

  • there should be a warning in the "save dialog" when creating/uploading an untagged relatin, similar to what's already shown for untagged ways/nodes.
  • I think that the relation should not be created until one of the presets is selected after clicking on "new relation" (users can still select the generic "relation" preset if they really want to create a untagged relation)
  • //edit: make add relation "+" button less prominent (see below)

@Paul012
Copy link

Paul012 commented Feb 1, 2017

Perhaps the All relations section shouldn't be expanded by default also. Having the large + button visible at the bottom of the column does have the potential to confuse new editors.

@tyrasd tyrasd added the usability An issue with ease-of-use or design label Feb 1, 2017
bhousel added a commit that referenced this issue Feb 1, 2017
@quincylvania quincylvania added the validation An issue with the validation or Q/A code label Apr 7, 2019
@quincylvania quincylvania self-assigned this Apr 7, 2019
@quincylvania quincylvania added this to the 2.15.0 milestone Apr 7, 2019
@quincylvania
Copy link
Collaborator

Rather than not creating the relation until after selecting a feature type (which would be really hard), I just made iD delete newly-created relations with no tags, memberships, or roles upon deselecting them. Basically this prevents empty relations from persisting if you click New Relation and then click away without doing anything.

Perhaps the All relations section shouldn't be expanded by default also. Having the large + button visible at the bottom of the column does have the potential to confuse new editors.

This sound fine but it doesn't seem critical now that we have the validation warning and the deletion behavior. If anyone really thinks we should do it then feel free to open another issue!

@quincylvania
Copy link
Collaborator

I also added a tooltip to hopefully make this button less mysterious 🦹‍♂️

Screen Shot 2019-04-07 at 2 03 01 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
usability An issue with ease-of-use or design validation An issue with the validation or Q/A code
Projects
None yet
Development

No branches or pull requests

4 participants