Opened 11 years ago

Last modified 6 years ago

#11048 new enhancement

Improve properties.remember-recently-added-tags=true behaviour — at Initial Version

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

Description

I've given the change from #10812 some time, but I can't get used to it because of the unexpected behaviour sometimes.

F.e., I often draw new higways (mostly driveways and tracks). I do this with the following keys that are kind of programmed in my fingers: ALT+A > "hi" > TAB > "ser" > ENTER. This worked before, and still works in 90% of the cases. However, it also happens that I tag something historic (a mill or memorial f.e.). But when I tag the next highway, I consistently end up with a tag "historic=service".

So I either have to learn to type "hig" for "highway" instead of just "hi", or I have to learn to check every proposal before I hit tab or enter. Both make the process slower. The same happens between "name" and "natural", or "lanes" and "landuse", or sometimes with values, s.a. "track" and "traffic_signals".

As a first improvement to this behaviour, I'd suggest to give a score to every tag, based on how often you use it. Since I use highway more than historic, the highway key would have a bigger score, and be the default one.

A second improvement could be to let the score from above degrade with time. F.e. I might be interested in mapping landuse for a period of time, and then turn my attention to lanes. When the score degrades with time (via a fast formula, f.e. half the existing score every session), the default would change from landuse to lanes after a few sessions.

A different improvement might be to also consider the OSM datatype. When I tag highway=traffic_signals, I always do that on nodes, while highway=track always happens on a way element. So different suggestions could be given to different datatypes. This doesn't always work though, as f.e. lanes and landuse are both mostly tagged on way types.

Thanks for giving this a thought.

Change History (0)

Note: See TracTickets for help on using tickets.