Changes between Version 63 and Version 64 of DevelopersGuide/DefaultPresets

Timestamp:

2022-08-21T10:32:15+02:00 (3 years ago)

Author:

leni

Comment:

lower case; commas; `; singular

DevelopersGuide/DefaultPresets

@@ -1 +1 @@
 [[TranslatedPages]]
 [[PageOutline(2-10, Table of Contents)]]
-= Defaultpresets Guidelines
+= Defaultpresets Guidelines =
 
 This page contains rough guidelines for the [source:/trunk/resources/data/defaultpresets.xml defaultpresets] and new icons.
+
 
 == New Tags and Values ==
@@ -10 +11 @@
 
 Basically we have to make sure that the preset menu isn't too cluttered, because it would get hard to find the useful every-day stuff if we had too many exotic entries. New tags and values should have:
-* a proper documentation in the [osmwiki: OSM-wiki]
-* decent usage numbers (absolute and by number of mappers)
-* world wide usage
-* Controversial cases (like `contact:phone=*` vs. `phone=*`) need to be decided case by case.
-* If a features is only mapped by a handful of specialists, it is better suited for an [wikitr:/Presets#PublishanewAvailablepresetsitem external preset]. Usually this includes tagging schemes restriced to one specific country, hobby, sport or profession. Instead of creating an own external preset you could also extend [wikitr:/Presets/NewTags].
+* a proper documentation in the [osmwiki: OSM-wiki],
+* decent usage numbers (absolute and by number of mappers),
+* world wide usage,
+* controversial cases (like `contact:phone=*` vs. `phone=*`) need to be decided case by case,
+* if a features is only mapped by a handful of specialists, it is better suited for an [wikitr:/Presets#PublishanewAvailablepresetsitem external preset]. Usually this includes tagging schemes restriced to one specific country, hobby, sport or profession. Instead of creating an own external preset you could also extend [wikitr:/Presets/NewTags].
 
 **Note**:
@@ -28 +29 @@
 * The icon must be **identifiable at a size of 16 pixels**. This is the default size the icons are displayed in the [wikitr:/Help/MapView Map View] on standard dpi (not hidpi) screens.
 * The **license** needs to be compatible with GPL3 (like PD or CC0). A good source for Icons is [https://openclipart.org openclipart.org] (all icons there are PD), [https://publicdomainvectors.org/ publicdomainvectors.org] (all icons CC0), [https://freesvg.org/ freesvg.org] (all icons CC0) or [http://osm-icons.org/wiki/Icons osm-icons.org] (a lot are CC0). You can also check if JOSM already has a fitting unused icon in one of its icon folders: [browser:josm/trunk/resources/images used icons] and [browser:josm/trunk/nodist/images unused icons].
-* If the tag applies to nodes, the icon in the MapView and the icon of the preset should be the same if possible. (It is not possible when different features use the same preset, e.g. crossing=island and crossing=traffic_signals have different icons, but are handled in only one preset "Pedestrian Crossing".)
+* If the tag applies to nodes, the icon in the MapView and the icon of the preset should be the same if possible. (It is not possible when different features use the same preset, e.g. `crossing=island` and `crossing=traffic_signals` have different icons, but are handled in only one preset "Pedestrian Crossing".)
 * Icons with transparent background must **not be only black or only white**. Otherwise if one uses a black or white background (no aerial imagery as background) in the Map View black or white icons would be invisible. Workaround: if you want to use a black icon add a square white background to the icon instead of a transparent background or better use a white halo. \\
- Examples: [[Image(BlackWhiteIcon.png,middle,link=)]] Colored icons are preferred though.
+ Example: [[Image(BlackWhiteIcon.png,middle,link=)]] Colored icons are preferred though.
 * The icon should hide as less as possible in the mapview, so colourful icons with transparent background are preferred over black/white icons with square background.
 * The icon should be understandable in all countries.