For presets and some fields, icons can be specified. They provide an additional hint to the user about what the respective OSM tags are about. Additionaly, icons can help to make presets more universally understood, as icons are even present when presets are not translated into all languages.
Icons from the below listed sources can be used. When specifying an icon, use the prefixed version of the name, for example "icon": "maki-park"
.
- Maki (
maki-
), map-specific icons from Mapbox - Temaki (
temaki-
), an expansion pack for Maki - Röntgen (available icons) (
roentgen-
), part of the Map Machine project - Font Awesome, thousands of general-purpose icons
- iD's presets-icons, iD's fields-icons (
iD-
)
A good place to submit a PR for a new icon is the Temaki project. This is because Temaki was specifically created for icons for tagging presets and has therefore relatively low acceptance criteria and short release cycles. But in principle, you could propose icons to be added to any of the listed sources above, if you prefer to do so.
In addition to the design guidelines, the following points should be considered when selecting or designing icons:
- icons should be as specific as possible for a given preset and not reused too much between presets
- icons should be universal and generic (i.e. not specific to a single region)
- icons are not images, i.e. don't need to be an exact depiction of the preset's features
For presets, it is possible to define an icon via the imageURL
property in addition to an icon
. The referenced image might be displayed by an editor instead of the icon
. For example, iD displays icons from imageURL
only when users have not disabled to show third party icons.
imageURL
is extensively used to specify the logos of brand presets by the name-suggestion-index project.