Parking Lots Should Complete Navigation to a linked Place
Many Parking Lots were created with the big push a few years ago but never had much use other than the ones flagged as Public for downtown type parking areas.
For restricted type parking lots that only serve a single place, once a user enters the parking lot for the place, navigation should complete.
A link would need to exist between the parking lot area and the place point/area.
This would create a usefulness to these parking lot areas that were created, as currently they simply are clutter on the map and serve generally no purpose.
In the USA, most suburban businesses have their own private parking, so there is no point to mapping parking except for this suggestion.
At worst, implementing this suggestion will bring less annoying recalculating noise as the parking lot is circled looking for an open space. At best, it will lower requests to the routing server for the same reason.
John Beck commented
At best, the parking lot feature works when there is nearby PUBLIC parking, AND the user understands how to look in the app when they arrive to the area. This can be useful in city areas where there is not dedicated parking at the destination.
However, for the majority of mapped PLA, there is little to no navigation benefit. If the PLA did not exist, the user would search a place and get routed there - - with an acceptable parking lot at the destination. They just arrive and park. Unless there is a legitimate plan to link these lots to Waze places, there is no need for them. They also can cause confusion when a place is closed or moved, but the PLA is not updated. Yes, this is an editor issue, but would not be an issue at all if the PLA were not there. Again - this is for restricted PLA when a parking lot already exists at the searched place (most of the PLA cases).
Duplicate Waze place and PLA also create confusion for drivers attempting to update data. Often, place data is updated into the PLA by mistake.
A few exceptions can be useful, such as a numbered parking lot at a university campus - - that can be searched directly. Or a named parking lot for a shopping plaza, that might be searched as opposed to a specific place in the plaza.
I'm in favor of minimizing the effort to add non-public PLA until they become a supported feature.
Severiorum Patrem commented
As currently implemented, PLAs that are either truly public, or private PLAs specifically named as part of a larger campus or facility that could plausibly searched by name, are the only useful ones on the map, and they make up probably less than 5% of all PLAs. The remaining PLAs are map clutter collecting place updates and photos intended for other places, or occasionally leading to poor user experiences by their existence implying a place still exists when it has closed but the associated PLA didn't get deleted. Please finish this project or greenlight deleting all these spurious PLAs that don't fit the narrow criteria defined above.
Also finish the fixes to allow multiple entry points to work correctly on all platforms in production.
I would like to see this added