I have a pretty simple question about road_access. My OSM data shows a way with “other_tags” where “road_access” is “private”. Yet when I import and start the server (version 10.0|2024-08-28T02:09:14Z (9,23,7,5,2,9)) locally and view the routing graph, the way shows up as “road_access”: “yes” and car_access/bike_access as “true”. Looking at the source code I imagined that this sort of a way would automatically and by default get “road_access”: “private”. I would like (for now at least) that private roads would block both bicycle and car. I thought this was the default.
Yes, this can be a bit confusing. An OSM way tagged as access=private should yield GH edges with encoded values road_access=private and car_access=false indeed. The latter can be changed using the block_private=false configuration.
Thank you for the heads up about other profiles. Everything seems to work as expected by using the correct OSM tag (“access”).
Regarding documentation, it would be marvelous to have a mapping table between OSM tags and different things in GH, e.g. which map to encoded values and in what way, and so on.
