Modify

Opened 7 years ago

Last modified 5 years ago

#7513 reopened enhancement

[Patch] Warn non-experts when combining ways with conflicting tags or ways being part of relations

Reported by: simon04 Owned by: team
Priority: normal Milestone:
Component: Core Version:
Keywords: Cc:

Description (last modified by simon04)

To reduce erroneous edits, I suggest to warn non-experts when combining ways with conflicting tags or ways being part of relations. The aim is to minimize broken route relations or highways being tunnel/brigde for several kilometers at the same time.

For non-experts, show the dialog 1 (if needed), show the dialog 2 (if needed), show the CombinePrimitiveResolverDialog (if needed).

Attachments (4)

combine_tags.png (7.1 KB) - added by simon04 7 years ago.
combine_relations.png (8.3 KB) - added by simon04 7 years ago.
7513.patch (26.5 KB) - added by simon04 7 years ago.
7513_bugfix.patch (6.8 KB) - added by simon04 7 years ago.

Download all attachments as: .zip

Change History (16)

Changed 7 years ago by simon04

Attachment: combine_tags.png added

Changed 7 years ago by simon04

Attachment: combine_relations.png added

comment:1 Changed 7 years ago by simon04

Description: modified (diff)
Summary: Warn non-experts when combining ways with conflicting tags or ways being part of relations[Patch] Warn non-experts when combining ways with conflicting tags or ways being part of relations

Changed 7 years ago by simon04

Attachment: 7513.patch added

comment:2 Changed 7 years ago by simon04

Patch attached … This comes with some cleanup of the CombinePrimitiveResolverDialog code which was replicated at least 3 times in the core.

What do you think? I'm happy to hear some comments. :-)

comment:3 Changed 7 years ago by simon04

Description: modified (diff)

comment:4 in reply to:  2 ; Changed 7 years ago by skyper

Replying to simon04:

What do you think? I'm happy to hear some comments. :-)

For tags, I think it is smoother to show this dialog after the "tag conflict dialog" with a button to go back to the "tag conflict dialog".

comment:5 in reply to:  4 Changed 7 years ago by simon04

Replying to skyper:

For tags, I think it is smoother to show this dialog after the "tag conflict dialog" with a button to go back to the "tag conflict dialog".

The "new" dialog is intended to somehow explain the situation (why another dialog is going to appear) and the dangers (may lead to unwanted results). If the user chooses to abort, the tag conflict dialog does not need to be shown at all. Therefore, I would show the new dialog before showing a more complicated tag conflict dialog.

comment:6 Changed 7 years ago by simon04

Resolution: fixed
Status: newclosed

In 5132/josm:

fix #7513 - Warn non-experts when combining ways with conflicting tags or ways being part of relations

comment:7 Changed 7 years ago by simon04

Resolution: fixed
Status: closedreopened

From comment:11:ticket:4842

Now it raises conflicts even with untagged objects.

I have an node with addr:housenumber=19 as tag and part of a associatedStreet relation and merge it with a node id:0 with no tages but part of a closed way and I get the tag conflict dialogue shown.

comment:8 Changed 7 years ago by simon04

attachment:7513_bugfix.patch​ restores original behaviour (i.e., before r5132). However, the original implementation seems to be a quirk to me: When merging nodes, the conflict dialog is skipped when the nodes are part of at most 1 relation. Why is it safe up to one relation, but no longer when 2 or more relations are involved?

Changed 7 years ago by simon04

Attachment: 7513_bugfix.patch added

comment:9 in reply to:  8 Changed 7 years ago by skyper

Replying to simon04:

attachment:7513_bugfix.patch​ restores original behaviour (i.e., before r5132). However, the original implementation seems to be a quirk to me: When merging nodes, the conflict dialog is skipped when the nodes are part of at most 1 relation. Why is it safe up to one relation, but no longer when 2 or more relations are involved?

Can not think of any problem as long as one node does not have any tags nor memberships. Concerning ways I am not sure as you could easily break relations that way.

comment:10 Changed 6 years ago by stoecker

Hmm. What is the status of this? Apply it or not?

comment:11 Changed 6 years ago by stoecker

@simon04: Status?

comment:12 Changed 5 years ago by simon04

Actually, I forgot this ticket and the idea in the patch. We could still apply it … ;-)

Modify Ticket

Change Properties
Set your email in Preferences
Action
as reopened The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to simon04
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.