Open westnordost opened 6 months ago
It's not too hard to process the access schema server-side to derive access for car/pedestrian/bike. Generally for rendering you want to simplify access levels into yes, some cases, and not the general public. It's not obvious if we should do that or the styles should.
We also want to avoid having three access attributes on every single road - we don't need to know that cars are allowed on a residential road because that's the norm and to include that property on every road would inflate tile size.
Right, I think a single access
value that applies for the expected vehicle type would be fine for the purpose of displaying a restriction on the map. Suggestions:
For all roads down to service roads (but except pedestrian roads), only the access
, vehicle
and motor_vehicle
key is considered. This means that if there is an access restriction for trucks only, this information is not included in the layer, which is fine for general purpose base maps, IMO
For values...
designated
coalesces to yes
permissive
coalesces to either yes or limited. I think the latter would be better
customers
, destination
, agricultural
, forestry
, delivery
, discouraged
coalesces to limited
permit
coalesces to limited. I think it is mostly used for residential parking (residential parking permits). So, in that regard a bit similar as destination
for roads.
(bicycle, horse, ... etc) dismount
coalesces to no
military
, private
coalesce to no
all other values are ignored
The information whether a road is accessible to the general public is currently missing from the vector tiles.
It would be convenient if the access restrictions would be conflated somehow, as on OSM, the
access
schema is quite complex. E.g. relevant for car drivers is not onlyaccess
but alsomotor_vehicle
.