Modify

Opened 5 years ago

Last modified 3 years ago

#12103 new enhancement

Show split way dialog only for high value geometries

Reported by: planemad Owned by: team
Priority: normal Milestone:
Component: Core Version: tested
Keywords: split, history Cc:

Description (last modified by planemad)

The recent split way/reuse history dialog is a useful power feature, however in most cases this is not a critical decision to take for a mapper, especially if the object does not have much of a history or is trivial split at the end of a long way, in which case its safe to assume we want the history on the longer way.

Also one would need to check the history of the objects for context to make an informed decision on which way to choose rather than blindly selecting off a list. The current dialog blocks any other activity and one is forced to make a decision just to continue, resulting in a not so expert decision.

As a quick fix, i'd like to suggest showing the dialog only for ways where the object split meets certain conditions:

  • Object version > 5
  • or Object has had two versions in the last month
  • or Object has high value tags (boundary, coastline...)

This would allow triggering advanced dialogs like this for objects whose history has a high value rather than for every geometry. This hopefully forces the mapper to cancel the dialog and check the object history to make a better decision than what happens currently.


In future, the object history might need a bit of a rethinking from a high level perspective. If a boundary is split, the history of the parent is still relevant to both ways and should not result in a completely new object that has no relationship to its past. Anyway, thats something to bikeshed on elsewhere.

Attachments (0)

Change History (6)

comment:1 Changed 5 years ago by planemad

Description: modified (diff)

comment:2 Changed 5 years ago by planemad

Description: modified (diff)

comment:3 Changed 5 years ago by DeeHants

This sounds reasonable. IMO, it should be possible to force it to appear with a modifier key.
It'd be nice if the version check value could be configured too.

comment:4 in reply to:  3 Changed 5 years ago by planemad

Replying to DeeHants:

This sounds reasonable. IMO, it should be possible to force it to appear with a modifier key.
It'd be nice if the version check value could be configured too.

Yes, a modifier key to force the dialog when needed sounds like a good solution as well and much easier to implement.

comment:5 Changed 3 years ago by aceman

Interesting idea.
Maybe showing the object history directly in the question dialog would be helpful. Yes, that may need to fetch the history from the database so would slow the dialog even more. But I would pay that price. Preserving proper history is very important for future edits. It is already bad enough that only one of the objects can get the history. That is a very bad shortcoming of the OSM DB/API.

The question dialog could also automatically preselect the longer way (if it doesn't already) so that the user could confirm it faster. It may need some thought whether longer means more nodes, or more meters.

comment:6 in reply to:  5 Changed 3 years ago by Klumbumbus

Replying to aceman:

The question dialog could also automatically preselect the longer way (if it doesn't already) so that the user could confirm it faster. It may need some thought whether longer means more nodes, or more meters.

See Help/Action/SplitWay#Usingoldobjectid

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new 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 planemad
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment


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

 
Note: See TracTickets for help on using tickets.