Opened 12 years ago
Closed 11 years ago
#9104 closed enhancement (fixed)
Better handling of semicolon in values: make it harder to add such values
Reported by: | skyper | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 14.02 |
Component: | Core | Version: | |
Keywords: | semicolon value | Cc: |
Description (last modified by )
The handling of semicolons could be enhanced. For background please have a look at:
- thread at talk@osm
- Jochen's blog an analyses
Two points came to my mind:
- make it harder to add semicolon separated values when combining by asking the user for interaction for each value with conflict and not automatically adding both values with semicolon as separator.
- Validator warnings/errors about semicolons in values where it makes no sense as many keys need single value to work.
Attachments (1)
Change History (11)
comment:1 by , 11 years ago
Description: | modified (diff) |
---|
comment:2 by , 11 years ago
Milestone: | → 14.02 |
---|---|
Owner: | changed from | to
Summary: | Better handling of semicolon in values → [Patch] Better handling of semicolon in values |
by , 11 years ago
Attachment: | 9104_1.patch added |
---|
comment:4 by , 11 years ago
Summary: | [Patch] Better handling of semicolon in values → Better handling of semicolon in values |
---|
comment:5 by , 11 years ago
Owner: | changed from | to
---|
comment:6 by , 11 years ago
For item 2, here's an analysis based on the TagInfo database: https://gist.github.com/anonymous/9058556
select key, sum(count_all), min(value), max(value) from tags where value like '%;%' group by key having sum(count_all) > 100
Using this list, we can identify some keys to whitelist.
comment:7 by , 11 years ago
That's a huge list. Can we sort it by number of total occurrences for each key?
comment:8 by , 11 years ago
Here you are: https://gist.github.com/9076516
This has been sorted with the very intuitive command sort --numeric-sort --key 4,4 --field-separator='"' --reverse semicolon.csv
;-)
comment:9 by , 11 years ago
Summary: | Better handling of semicolon in values → Better handling of semicolon in values: make it harder to add such values |
---|
Point 1 fixed. See #9757 for point 2 in next milestone.
comment:10 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
For item 1, the attached patch drops any default tag combining decision. The contained comment states:
For item 2, I would suggest to have a blacklist of keys resulting in a validation warning (like for
amenity
, …). For all other keys (except for a few whitelisted ones asref
,source
) a validation information should be generated.Since I do expect some discussion for both items, lets keep it for the
14.02
release.Please assist in providing blacklist+whitelist keys.