* Having separate presets for Surveillance and Surveillance Camera means
we can show the camera related fields only if `surveillance:type=camera`
* Generally use Upper Case for labels and keep it short
* if list of values is really fixed, use options strings to make them translateable
* if list of values is not fixed, avoid adding placeholder, iD will fetch from taginfo
* Seems like value "ALPR" is preferred over "alpr"
https://wiki.openstreetmap.org/wiki/Tag:man_made%3Dsurveillancehttps://wiki.openstreetmap.org/wiki/Proposed_features/Extended_tags_for_Key:Surveillance
These are mandatory tags:
* `surveillance`
* `surveillance:type`
I do not feel that the following are important, they can be selected from
the drop down manually anyway:
* `operator`
* `name`
These tags are well established:
* `camera:type` has 15k users
* `camera:mount` has 13k users
* `surveillance:zone` has 17k users (mostly traffic is noted)
* `camera:direction` has 6k users
These tags are in the proposed status:
* `contact:webcam` usage is only starting
* `height`
People used various tags instead of `contact:webcam` in the past
because of it being a recent tag, and/or a lack of knowledge or being
mislead by the dropdown.
Thus it is difficult to quote an exact number, but by using complex
regexp queries, I could find thousands of usages for webcam links
when properly combining man_made/surveillance/camera and various
(sometimes invalid) keywords in the key or value part of a tag:
* `website`
* `image`
* `uri`, `url`, `link`, `http`, `contact`
* `stream`
* `webcam`
(closes#3218)
* Allow traffic calmings on vertex and line geometry where appropriate
* Add parallel_direction field to tag forward/backward
* Add generic traffic calming preset and type field
* Add traffic calming to defaults.json for "vertex" geometry
* Add a bunch of types that we didn't have before (island, dip, choker, etc)
* Add some search terms
taginfo returns results that match anywhere within the string. So in Canada, you might get results like US:CA:SF. This change filters out such results.
Added a variation of the combo field for road networks. If the field’s value is blank or shares a prefix with the current country code, search taginfo for values beginning with the country code and a colon.
Replaced the generic network field (network) with a specialized network type field (network) in the bicycle, foot, and hiking route relation presets. Added a network (cycle_network) field to the bicycle route relation preset.
For multiselect fields,
field.key should have a ':' on the end of it - we use as the prefix, not the real key
field.keys should contain the array of real keys being modified
see https://github.com/openstreetmap/iD/blob/master/js/id/ui/preset.js#L17-L45
The address field preset works like this also..
It contains an array of key.fields for all the subfields that might be set.
For multiselect fields, we don't know ahead of time what all the subfields are,
so we append to the list in `change()` and rebuild list in `tags()`
