This section isn't needed because we don't source from OpenStreetMap at the low zooms.

(You'd just leave out surface from the list of drop_properties.)

done

Strangely enough concrete:lanes is a valid surface value in OSM:

• http://wiki.openstreetmap.org/wiki/Key:surface

But in Tilezen we generally avoid : and - in property names or values in favor of _.

That's controlled in the YAML config. So update where surface is added to include a mapping:

• https://github.com/tilezen/vector-datasource/blob/master/yaml/roads.yaml#L32

More like how we trap aerialway values to prevent j-bar from being exported in with the case statement:

https://github.com/tilezen/vector-datasource/blob/master/yaml/roads.yaml#L633

  - filter:
      aerialway:
        - drag_lift
        - platter
        - t-bar
        - goods
        - magic_carpet
        - rope_tow
        - "yes"
        - zip_line
        - j-bar
        - unknown
        - mixed_lift
        - canopy
        - cableway
    min_zoom: 15
    table: osm
    output:
      <<: *osm_highway_properties
      <<: *osm_network
      kind: aerialway
      kind_detail:
        case:
          - { when: { aerialway: 't-bar' }, then: 't_bar' }
          - { when: { aerialway: 'j-bar' }, then: 'j_bar' }
          - { when: { aerialway: 'yes' }, then: null }
          - else: { col: 'aerialway' }

We'll want to do this for a few values, TagInfo has the full details:

• https://taginfo.openstreetmap.org/keys/?key=surface#values

"But in Tilezen we generally avoid : and - in property names or values in favor of _."

There is also concrete:plates (other are not worth handling).

I will add it to the transform and documentation of surface value.

done

Our practice is to use comma before the and in a list:

Examples include is_bridge and is_tunnel, name, network, oneway, and ref.