For the time being, there's plenty to do now we can set the navigation points of migrated place:areas :up
AIUI, UK guidance has, upto now, used the logic that if you're using waze you're assumed to be in a car and therefore the destination waze should take you to (and therefore sometimes the only needed landmark for a place
) is the carpark. Entirely logical to me.The generic (but US biased) wiki page for Places:ParkingLot
uses very strong language against this for some very common UK scenarios - most notably supermarkets/shopping centres/stadiumsIf you ignore the Places spin on it:
It just boils down to a difference in how we/they treat parking. So, do we use this opportunity to change how we treat parking, or else it's an easy decision to just delete that bit and replace with the current UK guidance.not ignoring the Places spin, but keeping UK parking guidance
With Places you can add many sub-categories to a Place:area, including "Parking Lot"
suggestion: enlarge existing shopping/stadia building landmarks to encompass the adjacent parking, add a "Parking Lot" sub-class, move the Place:area destination marker to the entrance/parking lot road nearest the entrance. Delete the migrated/existing parking lot landmark. Or, vice-versa. Leave the existing ParkingLot Area, but add a sub-class for shopping center (sic) etc and expand it to cover the buildings.