-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Problems with presets and tagging on closed ways drawn with line tool instead of area tool #1293
Comments
In short: why? |
Because i can :-) and am used to it doing it that way and the geom is valid aswell. I do really appreciate that you try to take a fresh approach in editing maps and dont just copy every bit of josm. |
Also, in a quick test: if I add building=yes to a close line, the next time you click on the polygon, it's in the building preset, so the tag is not 'thrown away' but is integrated into the preset interface. Do you still see the Other preset or do you see the Building preset? |
It isn't lost. The feature is now recognized as an area and the building=yes tag is shown in the preset field: You may be interested in #1181 (Show all tags in 'Additional tags' area) or #1214. |
Are those changes already live on openstreetmap.us? I cant confirm it (tried with ff and safari)
|
#1295 is the underlying bug here. |
I draw a closed way using the line drawing tool (not area tool).
Now i want to tag it with "building=yes".
At first i try using the Building preset but it wont show up when i search for it. No chance.
So i fall back using the "Other" preset.
At the bottom in the inspector view i add the tag building=yes. But this tag is never applied. After reopening the inspector view the tag is lost.
So i end up that i cannot apply a building=yes on a closed way drawn with the line tool.
I do really like that users get a push using the area drawing tool instead of using the line drawing tool. But to have no chance to apply the tag at all is a bit too strict in my opinion.
The text was updated successfully, but these errors were encountered: