Files
iD/data/presets/defaults.json
Bryan Housel 1f2420e599 Prefer more specific 'Crosswalk' preset over generic 'Crossing'
Many new users in my area are getting this wrong or skipping crossings entirely because:
1. Most crossings people want to map really are `crossing=zebra`.
2. 'zebra' is not a common term in the US so users don't know to pick it.
3. Popup help for 'Crossing' shows a zebra, so users think that's what they picked.
2014-05-24 12:20:52 -04:00

49 lines
1.1 KiB
JSON

{
"area": [
"category-landuse",
"category-building",
"category-water-area",
"leisure/park",
"amenity/hospital",
"amenity/place_of_worship",
"amenity/cafe",
"amenity/restaurant",
"area"
],
"line": [
"category-road",
"category-rail",
"category-path",
"category-water-line",
"power/line",
"line"
],
"point": [
"leisure/park",
"amenity/hospital",
"amenity/place_of_worship",
"amenity/cafe",
"amenity/restaurant",
"amenity/bar",
"amenity/bank",
"shop/supermarket",
"point"
],
"vertex": [
"highway/crosswalk",
"railway/level_crossing",
"highway/traffic_signals",
"highway/turning_circle",
"highway/mini_roundabout",
"highway/motorway_junction",
"vertex"
],
"relation": [
"category-route",
"category-restriction",
"type/boundary",
"type/multipolygon",
"relation"
]
}