Personally I feel like it is implied that it is customer parking if it just says Parking - [Business].

Machete808 wrote:
Completely generic (For a single-business-single-lot):
Parking - [Business]
This is for businesses that are maybe standalone, where it's no doubt that the parking is for customers/patrons. The way the app currently works, if you want the lot to show up in search as an option, any restriction should be placed in the title and the restriction checkbox should be unchecked. This will change, though, at some point.

This was the obvious example I was referring to. I agree where there are restrictions they will need to be labeled as such to distinguish between other types of parking in the same general location.

AquaZR1 wrote:Personally I feel like it is implied that it is customer parking if it just says Parking - [Business].

While I agree with you that it is implied, there are case upon case of users not receiving the implied information (referring to the gas station with the name of NEX clearly as the first word in its name). I think we need to use the term "Customer Parking" in the name.

Although, I'm not sure having three standards from which to choose is a good idea. I'd like to conform to a single naming standard. But I'm open to keep all three usages with an explanation for use of each (i.e. why use one option over another, but not in all cases).

Nacron wrote: we should choose one and use it with fidelity instead of having multiple variances of the implied restriction

Agreed. But isn't Waze working toward a standard of "restricted" not showing up for other searches? For example, if we select the restricted option in the PLA options, parking for "McAdondons" wouldn't show up when searching for "AstroDollars Coffee" if they were in near proximity to each other.

For reference, the wiki section is here:

https://wazeopedia.waze.com/wiki/USA/Pl ... lot#Naming

The name always includes the business, or "entity served," preceded by something to describe it. This is how I read the four types of descriptions:


Completely generic (For a single-business-single-lot):
Parking - [Business]
This is for businesses that are maybe standalone, where it's no doubt that the parking is for customers/patrons. The way the app currently works, if you want the lot to show up in search as an option, any restriction should be placed in the title and the restriction checkbox should be unchecked. This will change, though, at some point.

Purpose descriptive (Where there is only one lot of the type):
Customer Parking - [Business] Employee Parking [Business], Student Parking [Business], etc.
This is to distinguish lots for a business/entity where there are various types. Like a campus, airport, etc.

Location descriptive (Where more than one lot serve the same purpose for the same place):
[Location] - [Business]
This is where multiple businesses are served by multiple lots, like in a shopping center. In this case, the "business" would be the shopping center's name.

Named (Where the lot is given an official name)

I think we should talk about specific examples that seem confusing, and see what local conventions we might need.

I should add that I've gleaned from discussion elsewhere that a future version of the app is going to enable lots that are restricted to a specific business/venue to be linked to that venue. So you would see this option only if that is your destination, I would gather. Referencing the remark by sketch, here:

viewtopic.php?f=1636&t=216110&p=1602884#p1602884

So in the case of a lot that is truly meant for only one venue, I would think we would need the [Customer Parking} descriptor only if there's maybe another lot nearby that's restricted some other purpose.

There are examples when the first approach Korey listed would seem right. Like the McDonalds in downtown Kailua would be "Parking - McDonald's."

But the parking for the McDonald's in Windward City Shopping Center might be better named "McDonald's Lot - Windward City Shopping Center." I mean, you wouldn't get towed if you were going to, say, the Ross's across the way if you parked there.

Not sure if there are customer-only signs posted at the Kailua McDonald's. If there are, I would then check the restriction box when that feature becomes more fully active.

We can look around the map and look for examples where we might want to refine the guidance in our own wiki.

Any ideas there?

I'm just concerned with the variances you'll see in the app. If one lot says Customer Parking - Walmart and then there's another lot that says Parking - Walgreens (customers only) the "customers only" might get visibly cut off causing someone to use the supposedly unrestricted parking lot. I think that if we are to use the customer restriction, we should choose one and use it with fidelity instead of having multiple variances of the implied restriction

The third example I listed was from the "restrictions" section of Wazeopedia:

Restricted parking
If there are posted signs restricting the lot to only one certain category of users (e.g. Customers, Residents, Staff, Attendees, Permit Holders, Faculty, Students, etc.) ONLY, then put that restriction in the name. If the lot is restricted to more than one category of users, then put "(restricted access)" in the name. Also put the details of the restriction in the description.
Examples:

"Parking - Starbucks (customers only)"
"Macy's Lot (customers only) - Big Hill Shopping Center"
Lot D (attendees only) - Cheery Stadium"
"Alpha Lot (permit only) - StudyHard University" Parking allowed by permit only ( even if permits are available to multiple groups (eg for Students, and Faculty)
"Bravo Lot (restricted access) - StudyHard University" Parking allowed for Students, and Faculty ONLY
"123 Somewhere St Lot (residents only)"
"345 Other St Lot (restricted access)" Parking allowed for resident, guests, and staff

Soon™