Implement private road tagging (#1174)
Fixes #1066 This PR adds a new field `access` in the transportation layer, which will be set to `no` if the `access` tag is either `no` or `private`. While `private` is the more popular value by a 17:1 ratio, I went with `no` because it's smaller in the tiles. In addition, the text `no` opens up the future possibility of other text-based access values such as `destination`, `customers`, or `permit`. The screenshot below shows an example of access tagging for a road on a military base: 
This commit is contained in:
committed by
GitHub
parent
fdb9ae58cd
commit
45d825e212
@@ -92,6 +92,10 @@ service_field: &service
|
||||
key: service
|
||||
name: service
|
||||
type: string
|
||||
access_field: &access
|
||||
key: access
|
||||
name: access
|
||||
type: string
|
||||
usage_field: &usage
|
||||
key: usage
|
||||
name: usage
|
||||
@@ -183,6 +187,7 @@ tables:
|
||||
- *oneway
|
||||
- *area
|
||||
- *service
|
||||
- *access
|
||||
- *usage
|
||||
- *public_transport
|
||||
- *man_made
|
||||
|
||||
Reference in New Issue
Block a user