The problem: There is an amenity - a hospital, museum, cave, and I want car navigation to guide me to the parking usually used there. Of course, we don’t always have such. But I don’t want navigation to drop me on the first class road, passing nearby with no single parking lot. What do you think? Is it possible for parking to be associated and eventually used by car navigation systems? Similar to Relation:associatedStreet.
3 Likes
You can use a site relation, but that’s not really supported by any data consumers
1 Like
Not really an answer to your question, but there is key:customers that specifies which neighboring amenity owns a parking tagged as access=customers. That has the drawbacks that a) it’s a textual attribute whose content may not exactly match the amenity name, and b) even if they match, the router would have to be smart enough to connect the two and lead you to the parking; according to Taginfo, no project does it.
Relation:site is more promising. With roles like parking, entrance, tickets, etc. Within car navigation (or mobile app in car mode) ot is more convenient for someone to be routed straight to the parking i/o some other place.