User:Tordanik/Paving stone details
This proposal contains subtags for surface=paving_stones, which allow mapping the dimensions and style of the stones.
Currently, the list of values for the surface key contains such oddities as "paving_stones:20" and "paving_stones:30" – attempts to tag the dimensions of the paving stones. The database reveals more surface values of that kind, e.g. "paving_stones:double_t".
However, creating a new surface value for each paving stone variant causes problems for applications trying to support the surface key. This proposal tries to introduce a more standard tagging style using separate tags instead.
The following keys are introduced by this proposal:
Paving stone dimensions
paving_stones:length describe the dimensions of each individual paving stones.
Square paving stones only require one of these tags to be set. With patterns that use multiple sizes (see e.g. "tudor" below), the dimension of the largest stone in the pattern is relevant.
Paving stone shape
paving_stones:shape describes the shape of the individual paving stones.
Paving stone pattern
paving_stones:pattern describes how the paving stones are arranged. Most paving stone shapes only allow a few patterns. The
half_bond pattern is the default for the shapes defined in this proposal.
Paving stone colour
paving_stones:colour describes the colour of the paving stones, using the value syntax of Key:colour. Ideally, the colour should represent the conditions under direct sunlight.
Paving stone direction
paving_stones:direction describes the orientation of the paving stone pattern. It uses the syntax for Key:direction angles.
If the tag is not set, then paving stone patterns should default to following the way's direction.
This proposal deprecates the tags
- surface = paving_stones:20
- surface = paving_stones:30
and variations thereof.