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
New feature's default tags: remember recent past edits #590
Comments
|
👍 Though I'd lik a simple rule of how to do this.. thinking about: For a new feature, add in tags that you added for the last new feature of that type, but omit Should that cover it? |
|
Yes :) |
|
Yeah, definitely a pain
could this be confusing? tags are being set without any direct action by the user Presets ui isn't finished yet, but it looks like there will be a list of favorites for newly created nodes. What if this were just updated based on recent edits? That only covers the basic tags though |
|
Threshold of 2 or 3 uses for added to favorites? Still think default values are important. Else it's hard to know what to Sent from my handsful device. On Feb 1, 2013, at 11:17, Ansis Brammanis notifications@github.com wrote: Yeah, definitely a pain For a new feature, add in tags that you added for the last new feature of could this be confusing? tags are being set without any direct action by Presets ui isn't finished yet, but it looks like there will be a list of * — |
|
Okay: so @ansis and I have discussed: So automatically pulling tags from the previous edit would be weird. We don't want this to happen automatically. But a slight change should make this fine: Next to the presets, we should have like a 'last config' button that fills in the form, and when it does that, it notifies the user by, for instance, flashing the form. |
|
This needs to be no-click to be useful. Having to click a "last config" button more than doubles the amount of time I have to spend when mapping a bunch of houses or armchair-tracing a bunch of streets. In JOSM-land, I wrote a very hacky plugin to automatically apply tags from the object copied to the clipboard. That's not exactly obvious, though. Some ideas:
I realize this is a UX nightmare, but it makes it MUCH easier to map. The difference between JOSM with building tools plugin and without is huge. The plugin basically creates a new mode that always applies a building=yes tag to the polygons created while in that mode. It makes it possible to trace an entire city's buildings in a day. |
|
We now remember the last preset chosen and push it to the top of the list. It's a few steps away from remembering all tags, but pretty okay. |
|
This is much better! But I'm still having problems with the following use case: I zoom into Eureka, California. Woodley Island north of downtown has a Even though I clicked on the piers to see what their class was, adding a Request adding a special favorite for _Nathaniel |
|
I would like to see a function that would pretty much replicate http://josm.openstreetmap.de/wiki/Help/Action/PasteTags but a little smarter. (omit name= most importantly) |
|
It looks like iD doesn't remember any settings. Why are they not stored, e.g. in a cookie ? Example: |
It defaults to highway=residential now.
But I've been editing (adding) man_made:pier all day. Each new pier I draw I have to type over these bad highway=residential defaults.
Init to highway=residential, but build dict of recent tags:values and if a trend develops, default to top edit session tag:value pair.
The text was updated successfully, but these errors were encountered: