[Tagging] Feature Proposal - RFC - parking=street_side
Jeroen Hoek
mail at jeroenhoek.nl
Mon Oct 26 19:19:30 UTC 2020
On 26-10-2020 19:31, Matthew Woehlke wrote:
> Alternatively, clients might look at the sort of highway running
> through a parking area. A highway=tertiary is probably "street-side
> parking", while a highway=service, service=parking_aisle probably is
> not.
That's not a bad thought, but it would require connecting the
street-side parking area to the highway (e.g., by extending the area to
the middle of the carriage way), which goes against the principle of
mapping what is there. I don't think renderers tend to have this
information available in any case.
Another notion I had was that renderers could just use capacity=* as a
measure of how visible a parking amenity should be, but that would
require knowing the capacity, which is not always plausible (and it
could lure mappers into tagging a capacity value they deem suitable for
rendering reasons). Of course, using capacity=* as well as parking=* can
be useful to highlight huge parking facilities at an earlier zoom-level
(I think Carto uses only the area size at the moment to do this).
All in all simply adding this sub-tag value seems the clearer option.
More information about the Tagging
mailing list