Preset
Most general-purpose editors come with a variety of presets to make tagging more accessible to new mappers or more efficient to experienced mappers. Each preset automatically applies primary feature key or tag to a feature, potentially along with one or more secondary tags for more specificity. A preset may also come with a dedicated UI with fields for common values or related keys. In some editors, a preset also determines how the editor renders the feature on the map canvas.
Presets have not been standardized across editors[1] and generally are not documented on this wiki's key and value description pages, but taginfo's Projects tab shows which presets use a given key or tag in each editor.
Presets by editor
iD
Presets are the main way that users add tags to a feature in iD, though they are labeled feature types in the UI. You choose a feature type after drawing the feature.
The presets are defined in the id-tagging-schema repository. iD additionally generates presets from the Name Suggestion Index. A preset can be limited to a specific country and data type.
Many presets have dropdown fields that suggest the most popular values for a particular key using data from taginfo, which in turn is derived from the OpenStreetMap database. Some of these values may be commonplace due to widespread community acceptance, while others may be commonplace due to a bulk import. If a popular value is inappropriate (for example, misspelled or a misnomer), it may be desirable to resolve the issue by organizing an effort to change the values directly in the database, possibly in conjunction with the formal Proposal process. For keys whose values have already been standardized yet have some errant common values due to an import, id-tagging-schema can be modified to hard-code the standard set of values for the key instead of automatically using taginfo.
Every Door
Every Door uses the same presets as iD.
Go Map!!
Go Map!! uses the same presets as iD[2].
StreetComplete
StreetComplete is a more directed editor that does not generally allow the user to map arbitrary features. However, it uses iD presets via osmfeatures to describe a task in terms of a feature type in the user's language.
JOSM
JOSM comes with a default list of presets and also allows you to create custom preset lists. A collection of community-maintained custom presets is available on the JOSM wiki.
Vespucci
Vespucci uses a fork of the JOSM preset files called beautified JOSM preset[3]. Vespucci additionally generates presets from the Name Suggestion Index [4]. (A proposed Google Summer of Code project would integrate Vespucci's enhanced preset format into JOSM.)
Merkaartor
Merkaartor comes with a default set of tag templates (*.mat) and also allows you to load custom template files.
Organic Maps
Organic Maps has a fixed selection of POI types [5][6].
OsmAnd
OsmAnd has a fixed selection of POI types.
Potlatch
Potlatch 1 and Potlatch 2's Basic tab present a small selection of presets. You can drag presets onto the map to create POIs or choose presets from a dropdown menu to tag ways.[7]
In Potlatch 1, the tag list panel also contained a dropdown menu for choosing from "presets" that were essentially human-readable names for feature tags.
Non-editor usage
The Overpass turbo query wizard recognizes queries of the form "preset" (in double quotation marks), where preset is the name of an iD preset in American English, so someone can easily query OpenStreetMap without necessarily knowing the specific tag they are looking for.
References
- ↑ https://github.com/osmlab/editor-presets/issues/1
- ↑ https://github.com/bryceco/GoMap/tree/master/src/presets/
- ↑ https://vespucci.io/tutorials/presets/
- ↑ https://vespucci.io/tutorials/name_suggestions/
- ↑ https://github.com/organicmaps/organicmaps/blob/master/data/editor.config
- ↑ https://github.com/organicmaps/organicmaps/blob/master/data/classificator.txt
- ↑ https://github.com/openstreetmap/potlatch2/tree/master/resources/map_features/
| ||||||||||||||||||