The new Waze Wiki, aka Wazeopedia, is now live at Wazeopedia.waze.com! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.

Please do not make any more updates to these legacy wiki pages, all future updates should be made in your country's local Wazeopedia.

Clock over a larger globe

Difference between revisions of "Places/Parking lot/USA"

From waze
Jump to: navigation, search
m (What not to do: Renaming)
 
(48 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
{{USRedirect}}
 +
{{mbox|text=New Parking features are being rolled out to the display of PLAs 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, since 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]]
 
[[File:Parking_sign.png|300px|thumb|right]]
== Parking Lots ==
 
The '''Parking Lot Area (PLA)''' 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.  Lots within ⅔ of a mile will be recommended based on a Wazers destination and as the feature matures, it'll recommend the 'most popular' lots that other Wazers have chosen when navigating to the same destination.
 
  
=== Area or Point ===
+
The '''Parking Lot Area (PLA)''' 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.
Parking lots can ONLY be added as an area as of August 1st, 2016 and only with the singular category of ''Parking Lot''.
+
 
 +
== {{@|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.
  
==== The Parking Lot Point Place ====
+
=== {{@|Parking lot point places}} ===
As of this writing, you can no longer add Parking Lots as a point place.
+
{{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|Map Problem]] (MP) report.  
+
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.
  
=== Extent ===
+
== {{@|Scope}} ==
At this time, parking lot areas (PLA) should not be added to businesses like gas stations or businesses with small parking lots (less than 20 spaces). This guidance may change in the future as further enhancements are made to the parking lot UI. Start by adding parking lots to event venues, shopping centers, airports, public use lots, garages, multi-use parking lots, etc.
+
{{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]]
 
[[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>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>For underground garages</u> it is hard to know the exact polygon, so try to estimate it based on your knowledge of the place. The accuracy of the entry point ([https://wiki.waze.com/wiki/Places#Setting_the_stop_point_for_a_Place '''Setting the stop point''']) is very important.
 
  
 
<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 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.
Line 24: Line 26:
 
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.
 
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.
+
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-premise Parking ====
+
=== {{@|On-premises parking}} ===
 
* It is important to create 2 separate places - one for the complex / place, and one for its designated parking lot.
 
* 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.
 
* Multiple parking lots for one premise: Create separate parking lots so the best parking lot can be recommended.
Line 32: Line 34:
 
* Multi-level lots should be created as single place with the shape of the overall parking surface outlined.
 
* Multi-level lots should be created as single place with the shape of the overall parking surface outlined.
  
==== Underground Parking Lots ====
+
=== {{@|Underground parking lots}} ===
* Create a polygon surrounding the parking lot’s estimated perimeter (if you know its boundaries) and locate the entrance point in the original location.
+
* 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.
 
* 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.
  
=== Creating and editing Parking Lot Areas ===
+
=== {{@|Rental-car lots}} ===
[[File:Waze_PLA_Example.jpg|300px|thumb|right|Outline building footprint only]]
+
*{{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.
  
==== Drawing ====
+
=== {{@|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:WME parking lots layer on.png|250px|right]]
 +
When editing or creating parking lots and related URs, MPs, & PURs, please make sure you have the Parking Lots layer turned on 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) Place should never be attached/snapped to roads. Places snapped to roads are difficult to edit.
 
The Parking Lot Area (PLA) Place should never be attached/snapped to roads. Places snapped to roads are difficult to edit.
  
 
For planned parking features to be announced later, it's important that the shape of the polygon be drawn as close as possible to the actual shape of the parking lot, including the entry/exit location. Keeping in mind that for multi-level garages, only the footprint of the structure should be outlined.
 
For planned parking features to be announced later, it's important that the shape of the polygon be drawn as close as possible to the actual shape of the parking lot, including the entry/exit location. Keeping in mind that for multi-level garages, only the footprint of the structure should be outlined.
  
==== Naming ====
+
If a lot spans both sides of a street (not counting PLRs obviously), it must be mapped so '''the polygon does not overlap the street'''. This may require drawing the lot as separate places.<br />
Like all Places, Parking Lot Area Places should be named.
+
''If the lot is elevated above the street however, and the lot actually covers the street, then the PLA may overlap the street as well.''
  
 +
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 Nassua 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 "Beach Street Garage", "18th Avenue/Geary Lot", "Lot 7 - <Stadium name>", "Short-Term Parking - <Airport name>", "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 "Park & Ride".
 
If a parking facility or area has a documented identity, such as "Beach Street Garage", "18th Avenue/Geary Lot", "Lot 7 - <Stadium name>", "Short-Term Parking - <Airport name>", "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 "Park & Ride".
  
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"; "SFO Domestic Garage" is sufficient.
+
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.   
 
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 can be used to name a lot if a more specific / official name does not exist.  (e.g., 1201 Conti lot; 2400 block Washington St garage). Check your local guidance for any variations.
+
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, know which lot it is when viewing the results list.  
  
As with all Area Places, do not use mapping abbreviations for any part of a Parking-Lot Place name.
+
==== {{@|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>
 +
'''Examples:'''
 +
* "Starbucks Parking (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''
  
==== Operator ====
+
=== {{@|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/USA|Regional Coordinator]] (RC).
 
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/USA|Regional Coordinator]] (RC).
  
==== Locking Standards ====
+
=== {{@|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.
+
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.
  
==== The Interface - More info ====
+
== {{@|Interface - more info}} ==
 
[[File:WME_PLA_UI_081016.jpg|400px|thumb|right|WME User Interface - More info tab]]
 
[[File:WME_PLA_UI_081016.jpg|400px|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.  
 
'''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.
 
*''Cars can exit when lot is closed'' - Check if the lot or garage does not restrict egress after the lot is considered closed.
*'''Cost'''
+
*'''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.
 
**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 #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)
 
***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 an approximately 1/2 mile (1 KM) radius should be taken into consideration for PLA cost determination where appropriate.
+
**Each lot within approximately mile (1 km) radius should be taken into consideration for PLA cost determination where appropriate.
  
 
*'''Services '''(select services listed below)
 
*'''Services '''(select services listed below)
 
**Reservations - Lot accepts reservations or accepts pre-paid parking passes or permits.
 
**Reservations - Lot accepts reservations or accepts pre-paid parking passes or permits.
**Disabilty parking - Spaces exist for handicap parking / wheelchair accessible spaces.
+
**Disability parking - Spaces exist for handicap parking / wheelchair accessible spaces.
 
**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).
 
**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
 
**Security - On-site security for the specific lot exists
Line 85: Line 141:
 
**A link to the specific parking lot or vendor's site (if applicable) is permissible here.
 
**A link to the specific parking lot or vendor's site (if applicable) is permissible here.
 
*'''Phone'''
 
*'''Phone'''
**The phone number to the main venue to which the parking lot belongs or to the parking lot vendor is permissible here.
+
**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}} ===
 +
{{Anchor|Examples}}{{Red|On-street parking should not be added at this time.}}
 +
 
 +
=== Gas stations ===
 +
Gas stations are already drawn on the map as an area, and typical usage includes parking to get gas. 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.
  
=== What does not qualify as a PLA? ===
+
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.
{{Red|On-street parking should not be added at this time.}}
+
  
==== Rental-car return ====
+
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.
With the availability of the "Car Rental" Place, rental car facilities and returns, including at airports, should be marked with that Place category. If the return location is a normal parking lot, then mark it with the parking lot category and the building as a separate place with the Car Rental category.
+

Latest revision as of 21:00, 27 February 2017


New Parking features are being rolled out to the display of PLAs 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, since the client is being updated. Initially we should focus on adding large and/or popular lots, but all lots should eventually be added.
Parking sign.png

The Parking Lot Area (PLA) 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 link to this section

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 link to this section

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 Problem (MP) report.

Scope link to this section

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 URs, etc.

Error creating thumbnail: File missing
Shopping Center PLA Example

For a mall or large shopping center, 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.)

If a lot is stacked (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.

If a lot has different entrances 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 link to this section

  • 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 link to this section

  • 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 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 link to this section

  • 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 link to this section

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 link to this section

Error creating thumbnail: File missing
When editing or creating parking lots and related URs, MPs, & PURs, please make sure you have the Parking Lots layer turned on so the existing PLAs on the map are not hidden.
Error creating thumbnail: File missing
Outline building footprint only

Drawing link to this section

The Parking Lot Area (PLA) Place should never be attached/snapped to roads. Places snapped to roads are difficult to edit.

For planned parking features to be announced later, it's important that the shape of the polygon be drawn as close as possible to the actual shape of the parking lot, including the entry/exit location. Keeping in mind that for multi-level garages, only the footprint of the structure should be outlined.

If a lot spans both sides of a street (not counting PLRs obviously), 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 however, and the lot actually covers the street, then the PLA may overlap the street as well.

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 (Setting the stop point) is very important.
Icon Parking
Error creating thumbnail: File missing
WRONG: Mapped to estimated underground Perimeter
Error creating thumbnail: File missing
CORRECT: mapped above ground, and entry/exit areas
Parking Garage - Yum! Center
Error creating thumbnail: File missing
WRONG: Multiple access points mapped as individual places for a single underground garage.
Error creating thumbnail: File missing
CORRECT: multiple access points included in a single polygon for an underground lot, the underground perimeter is not important.
Chemeketa Parkade Nassua Community College
Error creating thumbnail: File missing
CORRECT: Elevated lot built above street, mapped as a single PLA overlapping the street.
Error creating thumbnail: File missing
CORRECT:Ground level lots spanning streets mapped as separate PLAs. On-street parking not mapped as a PLA.

Naming link to this section

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

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, know which lot it is when viewing the results list.

Restricted parking link to this section

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:

  • "Starbucks Parking (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

Description link to this section

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.
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 link to this section

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).

Locking standards link to this section

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 link to this section

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
    • 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.
    • 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 specific parking lot or 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 link to this section

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 the guidance and do not add PLRs which are not necessary.

What does not qualify as a PLA? link to this section

On-street parking link to this section

On-street parking should not be added at this time.

Gas stations

Gas stations are already drawn on the map as an area, and typical usage includes parking to get gas. 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 link to this section

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.