John Beck
My feedback
4 results found
-
177 votes
An error occurred while saving the comment -
18 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
An error occurred while saving the comment The added visual would be helpful
-
22 votes
An error occurred while saving the comment 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.
-
120 votes
This latest change to add NONE into the field just adds more time for each edit.