Closed pnorman closed 6 years ago
Sounds good. Some comments:
Do we really have no way to use osm water on low zoom?
Not really. There are some more experimental techniques, but nothing I want to deal with at the same time as everything else.
Fixed the other comments.
Normally I'd go with a just start coding approach for defining layers, but for #2 and my presentation I need a well-defined set of layers to start with.
I'm inclined to the following as a starting place
water
Contents
Polygonal water bodies.
Fields
water
:ocean
,lake
,river
,reservoir
, or value of OSMwater
tagOrdering
By size
water_names
Contents
Points with water names Sources as with
water
layer, except sources without name data can be ignored.Fields
name
: name of water bodywater
:ocean
,lake
,river
,reservoir
, or value of OSMwater
tagOrdering
By size then name as text
transport
Contents
Transportation linear features All from OSM data, with features appearing at the following zooms
motorway
: z6trunk
: z7primary
: z8tertiary
: z9residential
,unclassified
: z12service
,track
, and non-motorized types: z14_link
roads of any type not shown until z10Rail features not included for now.
If the feature is oneway, then the direction of it is the direction of travel.
Fields
name
: Name of roadref
: Reference of roadclass
: value ofhighway
tag, excluding _linklink
: True if the feature is a_link
, empty otherwiseoneway
: True if oneway=true or reversebrunnel
:tunnel
orbridge
for tunnels or bridges, with bridge taking priorityOrdering
By layer with highest layer first, ramp with ramps first, class with most significant first, then name