View source for Places/Parking lot Discussion View history

{{mbox|text=New Parking features are being rolled out to display Parking Lot Areas in the client app. It is now encouraged to convert point places to area places. New parking lot point places can no longer be created.

Waze is also importing Parking Lot Areas. Do not delete them unless instructed to do so. Use the guidance here to improve their name, data, shape, and placement. '''Current guidance is to add PLAs to the map, as the client is being updated.''' Initially we should focus on adding large and/or popular lots, but ''all'' lots should eventually be added.}}
[[File:Parking_sign.png|300px|thumb|right]]

The&nbsp;'''Parking Lot Area (PLA)'''&nbsp;Place marks a well-defined area constructed for off-street public or private parking, including parking structures and garages as well as at-grade lots. The parking lot feature in the app will recommend parking lots to Wazers navigating to a nearby destination. Waze will recommend lots within ⅔ mile of a Wazer's destination. As the feature matures, Waze will recommend the 'most popular' lots that other Wazers have chosen when navigating to the same destination.

== {{@|Area or point}} ==
{{Anchor|Area or Point}}Parking lots can ONLY be added as an area as of August 1st, 2016. They are a special place category; you cannot add other categories to a parking lot place, or convert/add a parking lot category to another kind of place.

=== {{@|Parking lot point places}} ===
{{Anchor|The Parking-Lot Point Place}}As of this writing, you can no longer add Parking Lots as a point place.

Existing point places should be evaluated for inclusion and either converted to an area if applicable or deleted to solve the [[Map Problems in Waze Map Editor#Parking lot input as point|Map Problem]] (MP) report.

== {{@|Scope}} ==
{{Anchor|Principles|General Public Use|General Purpose Use|Distinctive and Significant|Interpreting_.27distinctive_and_significant.27}}At this time, parking lot areas (PLA) should be added to '''all lots''' including businesses with small parking lots (less than 10 spaces). Start by adding parking lots to event venues, shopping centers, airports, public use lots, garages, multi-use parking lots, popular lots with heavy usage or [[Glossary#UR|UR]]s, etc.
[[File:Waze_PLA_Mall_Example.jpg|400px|thumb|right|Shopping Center PLA Example]]
<u>For a mall or large shopping center</u>, break the parking lot up into multiple lots, as shown in the image to the right (use your discretion or discuss with your State Manager(s) or RC for official guidance if necessary.)

<u>If a lot is stacked</u> (underground + surface), map it as one place covering the footprint of the parking lot / garage. Future UI enhancements may allow for better modeling of these lots.

<u>If a lot has different entrances</u> serving different levels of a multi-level garage and you cannot drive from one level to another to park, but rather the levels are served independently by different entrances, then they should be mapped as multiple places. 

Care must be taken that stacked areas like this do not obscure each other.  You do not want two areas with identical boundaries stacked on top of each other as it will be hard to notice or select the right one for editing in WME.

As with all Area Places, a Parking Lot Area Place's geometry nodes should not be allowed to "snap" to adjacent road segments or junctions while being adjusted. Doing so can make the Area Place, as well as the adjacent segments or junctions, more difficult to modify.

=== {{@|On-premises parking}} ===
* It is important to create 2 separate places - one for the complex / place, and one for its designated parking lot.
* Multiple parking lots for one premise: Create separate parking lots so the best parking lot can be recommended.
* Valet parking - Valet is a service attribute of a place but is also an attribute for a parking lot.
* Multi-level lots should be created as single place with the shape of the overall parking surface outlined.

=== {{@|Underground parking lots}} ===
* It is still important to map these correctly so they can be routed to properly, and recommended appropriately in the client to users. Since the underground portion of the garage is not visible to drivers, it is not important to be displayed fully in the app.
* To support the internal features of the client; The polygon must include all above ground areas, and the areas where it starts to go underground. See the [[#Drawing|Drawing section]] below for more details and examples on how to draw these lots.
* If parking lots overlap with a Place, do not add "Parking Lot" category to a Place. Create a separate Area polygon for the parking lot.

=== {{@|Rental-car lots}} ===
*{{Anchor|Rental-car return|Rental-car return lots}}With the availability of the "Car Rental" Place, rental car facilities and returns, including at airports, should be marked with the Car Rental Place category for the desk and/or the building. If there is any customer parking, or return vehicle parking, then mark that area with the parking lot category.

=== {{@|Temporary lots}} ===
* Temporary lots for use at festivals, parades, concerts, etc., where temporary parking is being established specifically for the event can be added and named accordingly. Taking care to ensure that any temporary lots that are added, are removed as soon as the event is complete. '''On-street parking should not be added as a temporary lot.'''

== {{@|Creating and editing parking lot areas}} ==
{{Anchor|Implementation}}
{{mbox|type=caution|text=[[File:PlacesMenu.png|right]]
When editing or creating parking lots and related URs, MPs, & PURs, please make sure you have the Parking Lots [[Map_Editor_Interface_and_Controls#Layers|layer]] enabled (under Places) so the existing PLAs on the map are not hidden.}}
[[File:Waze_PLA_Example.jpg|300px|thumb|right|Outline building footprint only]]
=== {{@|Drawing}} ===
{{Anchor|Extent}}
The Parking Lot Area (PLA) polygon should be drawn to include all parking spaces in the parking lot and the access lanes used to reach each parking space. To prevent creating overly complex polygons and unnecessary geometry points, small medians, curbed areas, and building corners on the scale of around 5 meters or less may be overlapped by the polygon and not cut out by extra geometry points. For multi-level garages, only the footprint of the structure should be outlined.

Parking lots should never be attached, snapped or have their geometry extremely close to roads as this tends to make editing them difficult. Avoid including or touching any roads outside the parking lot. If a lot spans both sides of a street (excluding Parking Lot Roads), it must be mapped so '''the polygon does not overlap the street'''. This may require drawing the lot as separate places. ''If the lot is elevated above the street and the lot actually covers the street, then the PLA may overlap the street as well.''

The entry/exit location should be added to the place and adjusted to the appropriate location.

The following are examples of Parking Lot Areas with excessive and sufficient detail:

<center>
{| class="wikitable"
| style="background: red;"|[[File:Excessive_Detail.jpg|350px|thumb|center|Overly complex shape]]
| style="background: lawngreen;"|[[File:Sufficient_Detail.jpg|350px|thumb|center|Accurate shape with sufficient detail]]
|}</center>

For underground garages  it is not important to draw the polygon to match the internal perimeter since there is no GPS signal underground. It is important that the polygon includes any above ground areas, and the underground areas near any entrances or exits in a single polygon. If a lot has more than one entrance/exit the polygon must be made to connect all the entrances and exits. You may use a PLR to show multiple entrances as well, allowing the routing to choose the best route to access the lot, just as an above ground lot is drawn. It is not important however to draw the polygon to the entire footprint of the garage. The accuracy of the entry point ([[Places#Setting_the_stop_point_for_a_Place|'''Setting the stop point''']]) is very important. {{Clear}}
<center>
{| class="wikitable"
| style="background: #BEDCE5;" colspan=2; align=center|'''[http://www.waze.com/editor/?env=usa&lon=-73.98899&lat=40.74062&zoom=7&venues=187433367.1874399210.3624518 Icon Parking]'''
|-
| style="background: red;"|[[File:Underground lot mapped to perimeter.png|400px|thumb|center|WRONG: Mapped to estimated underground Perimeter]]
| style="background: lawngreen;"|[[File:Underground lot mapped to entrance.png|350px|thumb|center|CORRECT: mapped above ground, and entry/exit areas]]
|-
| style="background: #BEDCE5;" colspan=2; align=center|'''[http://www.waze.com/editor/?env=usa&lon=-85.75334&lat=38.25737&zoom=6&venues=179700095.1797328626.3614708 Parking Garage - Yum! Center]'''
|-
| style="background: red;"|[[File:Underground lot with multiple places.png|375px|thumb|center|WRONG: Multiple access points mapped as individual places for a single underground garage.]]
| style="background: lawngreen;"|[[File:Underground lot with multiple access.png|350px|thumb|center|CORRECT: multiple access points included in a single polygon for an underground lot, the underground perimeter is not important.]]
|-
| style="background: #BEDCE5;" align=center|'''[http://www.waze.com/editor/?env=usa&lon=-123.03897&lat=44.94261&zoom=7&mode=0&venueFilter=2&venues=155320769.1552945550.3513573 Chemeketa Parkade]'''
| style="background: #BEDCE5;" align=center|'''[http://www.waze.com/editor/?env=usa&lon=-73.58783&lat=40.73257&zoom=6&venueFilter=2 Nassau Community College]'''
|-
| style="background: lawngreen;"|[[File:Elevated lot over street.png|375px|thumb|center|CORRECT: Elevated lot built above street, mapped as a single PLA overlapping the street.]]
| style="background: lawngreen;"|[[File:Ground level lots spanning streets mapped separate.png|375px|thumb|center|CORRECT:Ground level lots spanning streets mapped as separate PLAs. On-street parking not mapped as a PLA.]] 

|}</center>

=== {{@|Naming}} ===
If a parking facility or area has a documented identity, such as {{nowrapcode|Beach Street Garage}}, {{nowrapcode|18th Avenue/Geary Lot}}, {{nowrapcode|Lot 7 - <Stadium name>}}, {{nowrapcode|Short-Term Parking - <Airport name>}}, {{nowrapcode|Cell Phone Lot - <Airport name>}}, 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 {{nowrapcode|Park & Ride}}.

The foundational guidance for naming a PLA when the lot serves another entity, is to follow this basic format:<br />
'''<code>[Parking&nbsp;Descriptor]&nbsp;<restrictions>&nbsp;-&nbsp;[Entity&nbsp;served]</code>'''<br />
The framework is {{u|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
:: {{nowrapcode|Parking - Starbucks}}
* '''Purpose descriptive -'''  Where there is only one lot of the type
:: {{nowrapcode|Customer Parking - Office Depot}}, {{nowrapcode|Employee Parking - Office Depot}}, {{nowrapcode|Visitor Parking - LSU Eunice}}, {{nowrapcode|Employee Parking - MSY}} [airport]
* '''Location descriptive -''' Where more than one lot serve the same purpose for the same place
:: {{nowrapcode|Southeast Lot - Big Hill Shopping Center}}, {{nowrapcode|Macy's Lot - Big Hill Shopping Center}}, {{nowrapcode|Grand Blvd Lot - Big Hill Shopping Center}}, {{nowrapcode|Target Garage - Big Hill Shopping Center}}, {{nowrapcode|Dillard's South Lot - Big Hill Shopping Center}}, {{nowrapcode|North Lot - Offices at Buildingtown Plaza}}
* '''Named -''' Where the lot is given an official name
:: {{nowrapcode|Garage 2A - Mercedes-Benz Superdome}}, {{nowrapcode|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"  

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.  

A block range or specific address '''should not be used''' to name a lot. If the lot does not have an official and/or signed name, then 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 differentiate the lot from all the others. Users can see the address displayed, and know which lot it is when viewing the results list. 

==== {{@|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|description]].<br>

{{mbox|text=Omit the restriction in the name if it is self-explanatory (e.g., {{nowrapcode|Parking - Starbucks}}, is obviously for Starbucks patrons only).}}

'''Examples:'''
* {{nowrapcode|Parking - Starbucks  (employees only)}} ''Different from the patron parking''
* {{nowrapcode|Macy's Lot (customers only) - Big Hill Shopping Center}}
* {{nowrapcode|Lot D (attendees only) - Cheery Stadium}}
* {{nowrapcode|Alpha Lot (permit only) - StudyHard University}} ''Parking allowed by permit only ( even if permits are available to multiple groups (eg for Students, and Faculty)''
* {{nowrapcode|123 Somewhere St Lot (residents only)}}
* {{nowrapcode|Bravo Lot (restricted access) - StudyHard University}} ''Parking allowed for Students, and Faculty ONLY''
* {{nowrapcode|345 Other St Lot (restricted access)}} ''Parking allowed for resident, guests, and staff''

=== {{@|Description}} ===
Any lot which is fully restricted in some way (e.g. permit/resident/customer only), and not open to the public for general parking, must include that information as the first line of the description. If only some of the available spots are restricted, but there are some spots in the lot open to the public for general parking, then it should not be mentioned.<br>
'''Examples:'''
* "Parking by permit only."
* "Parking only for customers of John Doe's Supermarket"
* "Parking only for residents of 123 Something St, and their guests"
* "Parking restricted to 15 minutes or less"
* "Valet parking only"
If you know the details or times of the restrictions you may add that information in the descriptions as well for users to see. This will also help for when those features become available in WME to have the details handy for mapping.

=== {{@|Operator}} ===
When there is a recognized parking operator, select it from the list, otherwise, leave this field blank. If an Operator is missing from the list that you feel should be added, please send the information to your [[Regional Coordinator]] (RC).

==={{@|Lot Type}}===
[[File:Parking lot type.png|right]]
At the top of the 'More Info' tab when a parking lot is selected you can set the Primary Lot Type. This setting affects whether a lot will be recommended in the client app when a Wazer searches for nearby parking, or as a suggested lot when searching for a destination. '''Any lots marked here as Restricted or Private {{U|will not be recommended}} to any users in the app for the time being.''' As the feature is further developed, there will be the ability to set more details on these restrictions so the lots may be recommended under certain circumstances. {{As of|2017|03}} these are the guidelines accepted for the application of these settings, designed for optimal user experience.

*Mark all parking lots with unrestricted public access as '''Public'''. This includes free and publicly owned parking lots, as well as for-profit garages, in which a Wazer may park, regardless of intent.
*Mark parking lots where some restrictions apply (customers, patrons, visitors), but the ability to see or select between them is useful to a Wazer, as '''Public'''. For example, a university campus with multiple student, visitor, or faculty parking lots, or a large shopping center that contains multiple patron-only parking lots. A suburban fast food chain's parking lot is not.
**Otherwise, mark parking lots where some restrictions apply (customers, patrons, visitors) as '''Restricted'''.
*Mark parking lots where parking is restricted to a specific audience (residents of an apartment parking lot, employee garage of an office complex), but the ability to see or select between them is useful to a Wazer, as '''Public'''. For example, Employee, or permit parking at an airport, or large compound, large housing developments with multiple permitted lot, etc.
**Otherwise, mark parking lots where parking is restricted to a specific audience (residents of an apartment parking lot, employee garage of an office complex) as '''Private'''.

=== {{@|Locking standards}} ===
Due to this major shift in editing guidelines, it is recommended that once a Parking Lot Area (PLA) has been added, that it be locked to 3 to avoid newer editors, or those not familiar with the change, from editing or deleting the PLA.

== {{@|Interface - more info}} ==
[[File:WME_PLA_UI_081016.jpg|thumb|right|WME User Interface - More info tab]]

'''Opening hours''' - Hours lot is open. Set open times for the lot or select each day and the ''All day'' radio button for lots open 24 hours a day / 7 days a week. 
*''Cars can exit when lot is closed'' - Check if the lot or garage does not restrict egress after the lot is considered closed.
*'''Cost'''{{Anchor|Free versus paid parking}}
**Cost determination should be made based on parking lot fees for other similar and nearby lots for the same type of venue.
***Example #1:  Adding / editing parking lots near an airport; terminal parking may be the most expensive at $25/day, express parking the next level down (moderate) at $15/day and remote parking the next best option at $5/day (low).
***Example #2: Hotel parking; on-site $50/day (expensive), self-parking garage at $30/day (moderate), and off-site parking at $15/day (low)
**Each lot within approximately ⅔ mile (1 km) radius should be taken into consideration for PLA cost determination where appropriate.

*'''Services '''(select services listed below)
**Reservations - Lot accepts reservations or accepts pre-paid parking passes or permits.
**Disability parking - Spaces exist for handicap parking / wheelchair accessible spaces.
**Carpool Parking - Reserved spots exist for people who carpool to the location.
**EV Charging - Lot contains a station to charge electric vehicles.
{{mbox | type       = important| text = If adding the EV Charging Station attribute, also add a separate point Place for the EV station, as described in the [[Places/Charging station]] wiki.}}
**Car wash - A car wash is on premises within the parking lot (some airports and other venues have amenities such as this for those parking within the lot).
**Security - On-site security for the specific lot exists
*'''Number of Spots'''
**List the most accurate number of spots within the specified parking lot area polygon.
*'''Contact info'''
**A link to the main venue to which the parking lot belongs or to the parking lot vendor's site (if applicable) is permissible here.
*'''Phone'''
**The phone number for the main venue to which the parking lot belongs or to the parking lot vendor is permissible here.

== {{@|Parking lot roads}} ==
Don't forget to map any necessary [[parking lot roads]], to allow for proper navigation into and out of the parking lot. The parking lot place does not substitute roads needed for actual navigation.

'''Parking lot roads are not required simply because a lot qualifies for a PLA.''' It is OK for small lots which do not qualify for their own PLRs to still be mapped as a PLA. The two features are independent of each other. PLRs have an effect on routing which can sometimes be detrimental. While it is important to map the ''necessary'' PLRs, please follow [[Parking lot roads|the guidance]] and do not add PLRs which are not necessary.

== {{@|What does not qualify as a PLA?}} ==

=== {{@|On-street parking}} ===
[[File:LotsnoStreet.png|thumb|right|The surrounding parking lots have been mapped, but on-street parking along State St and College Ave has not been mapped.]]{{Anchor|Examples}}{{Red|On-street parking should not be added at this time.}}

=== {{@|Gas stations}} ===

[[Places/Gas station#Area_size|Gas stations]] are already drawn on the map as an area and typical usage includes parking to get gas or enter the convenience store (when present). They are therefore handled specially by the servers, and '''do not require an additional PLA to be drawn on top of the gas station area'''. However, if there is a significant parking area there which is worthy to be recommended to users who are navigating to nearby venues (e.g. a truck stop, etc.), then you ''may'' add a PLA there.

=== {{@|Valet only facility}} ===
Parking lots or garages accessed exclusively by valet staff, and situated away from the valet drop off point should not be added to the map. (If regular drivers are not allowed to drive up to the valet facility, and rather must drop the vehicle at a different location, and the valet drivers are the only ones driving to this facility location, then it serves no purpose being recommended ever.

In such cases, where the valet drop off is not near the stop point for the place it services, the valet drop off may be added as a PLA, and marked as valet only in the name.

If regular drivers are allowed to drop their vehicle at the valet facility, or there is mixed use of the facility where non-valet users can park as well, then a PLA '''should''' be added.
<!--[[File:No_PLA.jpg|500px|thumb|center|Where PLAs are not needed]]-->