Browse Source

Remove 'type: overpass' - no longer necessary

master
parent
commit
aa4fb84f96
  1. 3
      example1.yaml
  2. 3
      example2.yaml
  3. 27
      example3.yaml
  4. 1
      example4.yaml
  5. 1
      example5.yaml
  6. 1
      roads1.yaml
  7. 1
      roads2.yaml

3
example1.yaml

@ -1,4 +1,3 @@
type: overpass
# From zoom level 15 on, load all nodes, ways and relations with amenity=restaurant.
query:
15: nwr[amenity=restaurant]
15: nwr[amenity=restaurant]

3
example2.yaml

@ -1,4 +1,3 @@
type: overpass
query:
15: nwr[amenity=fountain]
17: |
@ -14,4 +13,4 @@ feature:
{% elseif tags.amenity == 'drinking_water' %}
🚰
{% endif %}
{% endif %}

27
example3.yaml

@ -1,27 +0,0 @@
type: overpass
# Adding a category name (in English: "Example 3")
name:
en: Example 3
query:
15: nwr[amenity=fountain]
# This query uses a regular expression to match either fountain or drinking_water:
17: nwr[amenity~"^(fountain|drinking_water)$"]
feature:
description: |
{{ tagTrans('amenity', tags.amenity) }}
# Here, the correct icon for display is read from the 'const' structure
markerSign: |
{{ const[tags.amenity].icon }}
# We can use different markers depending on the type of item
markerSymbol: |
{{ markerPointer({ fillColor: const[tags.amenity].color }) }}
# This is for the marker in the listing in the sidebar
listMarkerSymbol: |
{{ markerCircle({ fillColor: const[tags.amenity].color }) }}
const:
fountain:
icon:
color: '#0000ff' # need to quote, because YAML would treat the color as comment
drinking_water:
icon: 🚰
color: '#007fff'

1
example4.yaml

@ -1,4 +1,3 @@
type: overpass
name:
en: Example 4
de: Beispiel 4

1
example5.yaml

@ -1,4 +1,3 @@
type: overpass
name:
en: Example 5
query:

1
roads1.yaml

@ -1,4 +1,3 @@
type: overpass
name:
en: Roads 1 # English name of the category
query:

1
roads2.yaml

@ -1,4 +1,3 @@
type: overpass
name:
en: Roads 2 # English name of the category
query:

Loading…
Cancel
Save