Sort by
Author
Post time
Subject
Display
All posts
1 day
2 weeks
1 month
3 months
6 months
1 year
Post Reply

[Page update] Places/Parking lot

Post by
This wiki implies there is still urgency to create PLAs. Combined with the numerous problem alerts present on maps in my local area of missing PLAs, I began working on creating these. Over time, I've found most of them deleted without any explanation. After discussion on Discord, I now have a better understanding of why this is not as urgent.

This wiki should be updated to deownplay the need for PLAs for small parking lots. It's frustrating as a L1 editor to have work removed when official sources tell me they are needed.Further frustrating to not have an explanation until I bought it up in the #mentoring channel.

https://wazeopedia.waze.com/wiki/USA/Places/Parking_lot

POSTER_ID:17644202

1

Send a message

Re: [Page update] Places/Parking lot

Post by Inactive user -1649923503-
I think the future of what is in store for the Parking Lot Area project is quite uncertain...

In terms of parking lots that have names, we have one in Boston that clearly identifies itself as its address.

IWe also have the former John Hancock Tower, now called by its address (Globe Story on name change).

To ignore or not use a companies name because it is also the address, you loose out on the components of a place including: hours, details, proper entrance. Sure the address would also populate in the search results, and maybe one day Waze will give us the tools to link them together. I dont think that is enough of a reason to change the name of a business from what the company calls itself. I do agree that PLA should not be named by their address solely for the point of having a name, however in the circumstances that subs5 presented, where there is a business name that happens to be an address we should use it.
Inactive user -1649923503-
Posts: 1023
Has thanked: 404 times
Been thanked: 460 times
Send a message
-John
-------
https://j.mp/1BqcgbWhttps://s.waze.tools/c5.png
VT - State Manager
New England - Multi State Manager

Re: [Page update] Places/Parking lot

Post by Inactive user -1649923503-
I agree there is no need for alt names to be an address and cases that come up should be dealt with at a local level with your respective SM
Inactive user -1649923503-
Posts: 1023
Has thanked: 404 times
Been thanked: 460 times
Send a message
-John
-------
https://j.mp/1BqcgbWhttps://s.waze.tools/c5.png
VT - State Manager
New England - Multi State Manager

Re: [Page update] Places/Parking lot

Post by Inactive user -1649923503-
You have the heart of the issue. Is searching for an address duplicative process for a PLA?

Usually I would agree, we are trying to look at a small subset scenario where the business name is the address. I think another layer to this debate we haven’t discussed is if a business name is an address how would that work with an external provider result? That could be polluting our result field as it is, and with the 100 Clarendon Parking Garage scenario I listed, the PLA is directly over a freeway. Using other place data could result in undesirable search results. Granted this is resolved by place linking regardless of the PLA name.
Inactive user -1649923503-
Posts: 1023
Has thanked: 404 times
Been thanked: 460 times
Send a message
-John
-------
https://j.mp/1BqcgbWhttps://s.waze.tools/c5.png
VT - State Manager
New England - Multi State Manager

Re: [Page update] Places/Parking lot

Post by Inactive user -1649923503-
Maybe, scenarios where the parking garage name is the address should be handled on a case by case scenario with local leadership guidance and not explicitly forbidden. There are many nuances and clearly differences of opinions. How many entrances, where the entrances are, public vs restricted/private etc.
Inactive user -1649923503-
Posts: 1023
Has thanked: 404 times
Been thanked: 460 times
Send a message
-John
-------
https://j.mp/1BqcgbWhttps://s.waze.tools/c5.png
VT - State Manager
New England - Multi State Manager

Re: [Page update] Places/Parking lot

Post by Inactive user -1697532064-
I could be reading this thread wrong, but I think we agree that if a lot has an official name containing its address (The Garage at 100 Clarendon Street), or if it serves a building that uses its address as its official name (250 Poydras), there's no problem with using the address in the name. As for taking names given by a parking app that are just addresses, I'm not seeing support for that, and I don't agree with it. After all, WazeParking1 imported all those address names from ParkMe, and there's an issue with data sources anyway if we use address-names from parking apps that are incorrect. As others have said, if you want to support search for the correct entry location of standalone lots that occupy a whole address, use a RPP or HN, and make the lot public, so that it will display in the parking finder. As for unnamed lots that share an address with an unnamed building, I'd guess that those will not be public lots, and people navigating to the address in general would be best served by putting a RPP where the parking is.

The current guidance seems to imply that address should never be used in the name of a lot, even if that's the official name. I doubt that was the intent and think it should be clarified. As also discussed in Discord in the past few days, the current guidance seems to imply that we need to put a name on every lot, because the paragraph about leaving lots unnamed is sort of buried under examples. One other thing discussed was the use of multiple entry points for PLAs. In a related thread, we agreed that they should be used, and it's fairly straightforward.

Therefore, I'd like to make a counter-proposal:
Proposed naming section wrote:If a parking facility or area has a documented identity according to signs or owner-provided information, such as Beach Street Garage, 18th Avenue/Geary Lot, Lot 7 - <Stadium name>, Short-Term Parking - <Airport name>, Cell Phone Lot - <Airport name>, The Garage at 100 Clarendon Street, etc., its place should reflect that name to facilitate searches. Generic park-and-ride lots should be named consistently according to local custom, for example as Park & Ride.

The foundational guidance for naming a PLA when the lot serves another entity, is to follow this basic format:
[Parking Descriptor] <restrictions> - [Entity served]
The framework is not recursive. In other words, there is only one business served in any lot name, and the rest of the name is the descriptor. As a rule the descriptor will always have a word in it identifying it as parking, e.g. parking, garage, or lot. The descriptor can be:

Completely generic - For single-business - single-lot

Parking - Starbucks

Purpose descriptive - Where there is only one lot of the type

Customer Parking - Office Depot, Employee Parking - Office Depot, Visitor Parking - LSU Eunice, Employee Parking - MSY [airport]

Location descriptive - Where more than one lot serve the same purpose for the same place

Southeast Lot - Big Hill Shopping Center, Macy's Lot - Big Hill Shopping Center, Grand Blvd Lot - Big Hill Shopping Center, Target Garage - Big Hill Shopping Center, Dillard's South Lot - Big Hill Shopping Center, North Lot - Offices at Buildingtown Plaza

Named - Where the lot is given an official name

Garage 2A - Mercedes-Benz Superdome, Credit Card Lot - MSY

If a lot does not serve another entity and has no official and/or signed name, a block range or specific address should not be used to make up a name for a lot. Rather, leave the name blank, and be sure to add the address details in the address field. Some imported PLAs were created with the address or address block range as the name, these names should be removed accordingly. Check your local guidance for any variations.

NOTE: It is very important if there is no name for the lot that there be a proper address in the address field. If you don't know the exact address you should at least put the street the main entrance is on, and - if you can - an approximate house number. The address is needed to be displayed in the search results, and to differentiate the lot from all the others. Users can see the address displayed and know which lot it is when viewing the results list.

Examples
If a parking lot area place is contained within a larger area place, do not repeat the larger area's full name. For example, if the Domestic Garage is contained within the "SFO San Francisco International Airport" Area Place boundaries, it need not be named "SFO San Francisco International Airport Domestic Garage"; "Domestic Garage - SFO" is sufficient.

If a mall or shopping center has several lots which can be associated with various anchor stores in the mall/shopping center, the lots can be named for the anchor stores. For example: "Macy's Lot - Big Hill Shopping Center"

If a lot serves a building that uses its address as its official name, such as a high-rise residential development, the address may be used as part of the name. For example: "Parking Garage - 250 High"

In rare cases, a municipality or district provides public parking distinct from any other area place but without any documented or signed identity. These can be named after the municipality or district, for example, "Redwood City Public Parking". Do not use completely generic names such as "Parking" or "Public Parking" for anonymous parking facilities but rather leave them unnamed and add an address.
This changes the current section by:
  • Clarifying that addresses as official names of lots or entities served by lots can be used in the names of parking lots
  • Clarifying what an official name is (must be on signage or provided by the owner, i.e. not just what some parking app may say)
  • Moving the section on leaving certain lots unnamed to a place that is more logical and visible
  • Clarifying that the whole thing on not using addresses and leaving unnamed is intended for standalone lots without official names
Also within the drawing section, it adjusts language around entry locations to refer to multiple entry points, changes the link to point to the new guidance (when published) and adds the following
If a parking lot has multiple equally useful entrances, multiple entry points may be used.
The PLA page currently points to the general places page for info on setting entry points; this won't change as it would be redundant. There are a few changes to make capitalization consistent (as always I guess ;) )

draft
diff
Inactive user -1697532064-
Wiki Master
Wiki Master
Posts: 1308
Has thanked: 549 times
Been thanked: 703 times
Send a message
Galaxy S20 FE on Mint
Retired SM Ohio
Then you will know the truth, and the truth will set you free.
-John 8:32

Re: [Page update] Places/Parking lot

Post by Inactive user -1697532064-
That sounds good, using info from either the owner or the operator. And I like your example with "Parking - 901 New York Ave NW." It does appear that the address is used like the official name. We can add that as an example in the examples section. Is that good? Is there a better way to organize this?
Inactive user -1697532064-
Wiki Master
Wiki Master
Posts: 1308
Has thanked: 549 times
Been thanked: 703 times
Send a message
Galaxy S20 FE on Mint
Retired SM Ohio
Then you will know the truth, and the truth will set you free.
-John 8:32

Re: [Page update] Places/Parking lot

Post by Inactive user -1697532064-
Yeah, the reason for using the address in the name must be because it is the official name of the business. An address given as the name of a lot by an operator is not a reason to put it in the name in Waze. We've been over this. I think my most recent counter-proposal addresses it, but the organization of the text could be improved for clarity. I've modified my proposal a bit with some subsection headings, an intro about why we name things, elimination of the examples subheading (since examples are throughout) along with irrelevant examples and NOTE, and distribution of its content among the relevant new subsections. I also added Alan's example of Parking - 901 New York Avenue NW in there. I think if we organize the guidance a little better, confusion and perception of inconsistency can be eliminated. How's this? New text in red and moved text in blue:
Naming wrote: How to name a parking lot depends upon whether that lot serves another entity or whether it stands alone, intended for use by anyone whose destination is nearby.

Serves another entity
The foundational guidance for naming a PLA when the lot serves another entity, is to follow this basic format:
[Parking Descriptor] <restrictions> - [Entity served]
The framework is not recursive. In other words, there is only one business served in any lot name, and the rest of the name is the descriptor. As a rule the descriptor will always have a word in it identifying it as parking, e.g. parking, garage, or lot. The descriptor can be:

Completely generic - For single-business - single-lot

Parking - Starbucks, Parking Garage - 250 High

Purpose-descriptive - Where there is only one lot of the type

Customer Parking - Office Depot, Employee Parking - Office Depot, Visitor Parking - LSU Eunice, Employee Parking - MSY [airport]

Location-descriptive - Where more than one lot serve the same purpose for the same place

Southeast Lot - Big Hill Shopping Center, Macy's Lot - Big Hill Shopping Center, Grand Blvd Lot - Big Hill Shopping Center, Target Garage - Big Hill Shopping Center, Dillard's South Lot - Big Hill Shopping Center, North Lot - Offices at Buildingtown Plaza

Named - Where the lot is given an official name

Garage 2A - Mercedes-Benz Superdome, Credit Card Lot - MSY
Examples
If a parking lot area place is contained within a larger area place, do not repeat the larger area's full name. For example, if the Domestic Garage is contained within the "SFO San Francisco International Airport" Area Place boundaries, it need not be named "SFO San Francisco International Airport Domestic Garage"; "Domestic Garage - SFO" is sufficient.

If a mall or shopping center has several lots which can be associated with various anchor stores in the mall/shopping center, the lots can be named for the anchor stores. For example: "Macy's Lot - Big Hill Shopping Center"

If a lot serves a building that uses its address as its official name, such as a high-rise residential development, the address may be used as part of the name. For example: "Parking - 901 New York Avenue NW"

Standalone
If a parking facility or area has a documented identity according to signs or information from the owner or operator, such as Beach Street Garage, 18th Avenue/Geary Lot, Lot 7 - <Stadium name>, Short-Term Parking - <Airport name>, Cell Phone Lot - <Airport name> The Garage at 100 Clarendon Street, etc., its place should reflect that name to facilitate searches. Generic park-and-ride lots should be named consistently according to local custom, for example as Park & Ride.

In rare cases, a municipality or district provides public parking distinct from any other area place but without any documented or signed identity. These can be named after the municipality or district, for example as "Redwood City Public Parking".

Unnamed
If a lot does not serve another entity and has no official/signed individual or group identity, do not use a completely generic names such as "Parking" or "Public Parking"for anonymous parking facilities but rather leave them unnamed and add an address., or a block range or specific addressshould not be used to make up a name for athe lot. Rather, leave the name blank, and be sure to add the address details in the address field. Some imported PLAs were created with the address or address block range as the name; these names should be removed accordingly. Check your local guidance for any variations.

NOTE:It is very important if there is no name for the lot that there be a proper address in the address field. If you don't know the exact address you should at least put the street the main entrance is on, and - if you can - an approximate house number. The address is needed to be displayed in the search results, and to in order to differentiate the lot from all the others in the parking finder. Users can see the address displayed and know which lot it is when viewing the results list. If no address is entered, the lot will simply display as "Parking lot."
I also revised the mbox at the top of the page in accordance with what JM wrote earlier, that they aren't really rolling out new parking features to the app now; it has been three years. Here's what I propose for that:
new banner message wrote:New parking features have been rolled out to display parking lot areas in the client app. Convert parking lot point places to area places. New parking lot point places can no longer be created. Waze has also imported new parking lot places. Do not delete them unless instructed to do so. Use the guidance here to improve their name, data, shape, and placement. Add parking lots to the map in accordance with this page. Initially we should focus on adding large and/or popular lots, but all lots should eventually be added.
draft
new diff
Inactive user -1697532064-
Wiki Master
Wiki Master
Posts: 1308
Has thanked: 549 times
Been thanked: 703 times
Send a message
Galaxy S20 FE on Mint
Retired SM Ohio
Then you will know the truth, and the truth will set you free.
-John 8:32

Re: [Page update] Places/Parking lot

Post by Inactive user -1697532064-
Yeah that is pretty dated, so we should get rid of that statement. Things that were imported in 2016 should be deleted, if they are not there now.
Inactive user -1697532064-
Wiki Master
Wiki Master
Posts: 1308
Has thanked: 549 times
Been thanked: 703 times
Send a message
Galaxy S20 FE on Mint
Retired SM Ohio
Then you will know the truth, and the truth will set you free.
-John 8:32

Re: [Page update] Places/Parking lot

Post by Inactive user -1697532064-
SeveriorumPatrem wrote:Third criteria... Park and Ride lots. Named and set to restricted. They should be a destination, not a suggestion when you're doing something unrelated.
Why? If they're public, and you're going somewhere nearby that doesn't have parking, why shouldn't you get them as a suggestion?
Inactive user -1697532064-
Wiki Master
Wiki Master
Posts: 1308
Has thanked: 549 times
Been thanked: 703 times
Send a message
Galaxy S20 FE on Mint
Retired SM Ohio
Then you will know the truth, and the truth will set you free.
-John 8:32

Re: [Page update] Places/Parking lot

Post by Inactive user -1697532064-
I've noticed that the machine learning thing still happens to some extent, so that when navigating to certain places, Waze suggests a "most popular parking lot," and this can be of any type. That would be a reason to keep even restricted and private lots on the map.
Inactive user -1697532064-
Wiki Master
Wiki Master
Posts: 1308
Has thanked: 549 times
Been thanked: 703 times
Send a message
Galaxy S20 FE on Mint
Retired SM Ohio
Then you will know the truth, and the truth will set you free.
-John 8:32
Post Reply