Difference between revisions of "User:Karlcr9911"

From Wazeopedia
m
m (PLA)
 
Line 1: Line 1:
==Locking Standards==
+
<!--if the section parameter is defined, do not place the visible banner, only as the code block for the top of a section-->{{GlobalMark/visible}}
Places should be completed as fully as possible anytime they are created or updated. At a ''minimum'', editors should:
+
<!--
*'''verify correct spelling''' of the name, using the guidelines below
+
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-----
*'''complete the address''', to help when choosing among search results in the app, and
+
####    This page has been curated  ####
*'''ensure the correct location''' of the Point or Stop Point, to guide drivers to the correct location. Note that this may not always be on the street side of the location.
+
####    to be included in the new    ####
Phone numbers and opening hours are also particularly helpful to Wazers. Complete them whenever possible, using an online search, if necessary. Photos should help Wazers recognize the destination when they arrive.  
+
####    Wazeopedia - GLOBAL Wiki.   ####
 +
####    Please do not make any      ####
 +
####    edits on this page without  ####
 +
####    PRIOR CONSENSUS in the Wiki  ####
 +
####    Updates and Discussions      ####
 +
####    forum thread for this page.  ####
 +
####    If a specific forum thread  ####
 +
####    for this page doesn't exist  ####
 +
####    please start one.           ####
 +
####        www.waze.com/forum/      ####
 +
####        viewforum.php?f=276      ####
 +
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-->
  
Recommended phone number formats: (903) 654-3210 or 903-654-3210  Others may not auto-dial properly in some phones.  
+
{{construction
 +
| contact    = http://www.waze.com/forum/viewtopic.php?f=276&t=87595
 +
| contacttype = forum
 +
| draft      = no
 +
| open        = no
 +
}}
  
When completed, places should be locked, to prevent inadvertent damage. Please don't lock places to their highest level until most of their information is completed, but do lock to a level higher than 1, once you have verified ''any'' information, to help protect from accidental damage through client submissions. The following are recommended (minimum) levels:
+
== Parking Lots ==
:5 - Hospitals, universities, park and ride lots, arenas, airports
 
:4 - Police Dept / Fire Station
 
:4 - Large areas - (State Parks, if mapped, etc.)
 
:3 - Gas Station
 
Most other places should be locked at 3, once completed.
 
  
==Naming Standards==
+
:''The decision to map a Parking-Lot '''Place''' is covered here, and the decision to map a Parking-Lot '''Road''' is covered in the [[Road Types (USA)#Parking Lot Road|Road type article for mapping parking lot roads]].''
We are standardizing the naming of most public facilities and businesses. This makes search results more consistent and useful, and gives Wazers a more professional and uniform experience. The names have been designed to work well with instant search, regular search, and to be clear and concise in the map display. Please follow these guidelines when naming the places described below.
 
  
Places which are part of a larger area place (e.g. place points for parking lots in a university area, separate ER entrances in a hospital area, etc.) should be named with their unique name followed by a hyphen and the name of the larger area they belong to. For example "ER - Parkland Hospital"
+
:''The forum discussion thread for the Parking-Lot Place is separate from the general Place thread, and is located [http://www.waze.com/forum/viewtopic.php?f=276&t=87595 here].''
 
===Government Agencies===  
 
  
All places for the following agencies should be named according to the standards as follows:
+
The '''Parking Lot''' 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.
  
'''City and County Offices''': City or County Name followed by City Hall or department or agency as appropriate, for example:
+
=== Area or Point ===
:"Dallas City Hall"
 
:"Travis County Probation"
 
:"Bexar County Courthouse"
 
  
'''Police and Sheriff's Departments''': City, Agency or Division Name followed by "Police Dept" or "Sheriff's Dept", for example:
+
Parking lot places can ONLY be added as an area as of August 14th, 2016 and only with the singular category of ''Parking Lot''.
:"Dallas Police Dept"
 
:"Austin Police - North Substation "
 
:"Tarrant County Sherrif's Dept"
 
:"Travis County Sherrif's Office"
 
  
'''Fire Stations''': Agency Name or abbreviation followed by “Fire Station – “ and the station number. For example:
+
==== Extent ====
:"DFD Fire Station - 15"
 
:"Austin Fire Station - 3"
 
:"Whitehouse Vol Fire Station - 2"
 
  
'''Light Rail Stations''': Start with the Agency, which line, followed by the station name. For example:
+
At this time, parking lots 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.
:"DART Rail – Akard Street Station"
 
:"DART Green Line – Fair Park Station"
 
  
In general, City Bus stops should not be mapped.  
+
For a mall or large shopping center, break the parking lot up into multiple lots (use your discretion or discuss with your State Manager(s) or RC for official guidance if necessary.)
  
'''United States Postal Service''': Start the name with CDP or Station name, then append “Post Office”. Place the City name and the ZIP code of the Post Office in the Description box, so it will be viewable in the app GO page.  Alternate name should be “USPS”. For example:
+
For underground garages it is hard to know the exact polygon, so try to estimate it based on your knowledge of the place, and in that case the accuracy of the entry point is even more important.
:"Oak Lawn Post Office"
 
:"White Rock Station Post Office"
 
  
Here is the USPS tool to find the names of specific post offices.
+
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.
https://tools.usps.com/go/POLocatorAction!input.action
 
  
 +
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.
  
'''US VA Hospitals/Centers/Clinics''': Should be named with their official name as the primary name. For VA hospitals/medical centers "(US Veterans Only)" should be added to the end of the primary name, and as the first line of the description. In the primary name, "VA" should be expanded as "Veterans Affairs", so as not to cause a TTS conflict with Virginia. Names can be shortened to remove extraneous words; for example, replace "Campus of the" from the official name with a hyphen (-). Any colloquial names should be added as alt names, so they are returned in search results, and also at the beginning of the description, so they are visible on the place preview page in the client. Some examples:
+
For planned parking features, 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. 
:"Veterans Affairs - Healthcare Center at Harlingen (US Veterans Only)"
+
 
:"Veterans Medical Clinic - McAllen"
+
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.
:"Veterans Affairs - North Texas Health Care System (US Veterans Only)"
+
 
 +
==== Naming ====
 +
 
 +
Like all Places, Parking-Lot Places should be named.
 +
 
 +
If a parking facility or area has a documented identity, such as "Beach Street Garage", "18th Avenue/Geary Lot", "City Lot #7", "Short-Term Parking", "Cell-Phone Lot", 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.
 +
 
 +
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.
 +
 
 +
As with all Area Places, do not use mapping abbreviations for any part of a Parking-Lot Place name.
 +
 
 +
==== Drawing ====
 +
 
 +
The Parking-Lot Area Place should never be attached/snapped to roads. Places snapped to roads are difficult to edit.
 +
 
 +
For planned parking features, 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. 
 +
 
 +
==== Airports ====
 +
 
 +
Airports typically distinguish between parking for different terminals, for short or long term, and for cell-phone/waiting. As common navigation destinations, such parking deserves to be marked with Parking-Lot Area Places and named according to the airport's documented nomenclature.
 +
 
 +
 
 +
==== Rental-car return ====
 +
 
 +
With the availability of the new "Car Rental" Place, rental-car facilities and returns, including at airports, should now 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.
 +
 
 +
=== On-premise 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 ===
 +
*Create a polygon surrounding the parking lot’s estimated perimeter (if you know its boundaries) and locate the entrance point in the original location.
 +
 
 +
*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.
 +
 
 +
=== The Parking-Lot Point Place ===
 +
 
 +
As of this writing, you can no longer add Parking Lots as a point place.
 +
 
 +
=== 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.

Latest revision as of 14:23, 10 August 2016

Wazeopedia.png
This new page is currently undergoing modifications. The information and guidance is currently considered accurate enough to be followed now. Content is being prepared by one or more users. Do not make any changes before you post a message in this forum.

Parking Lots

The decision to map a Parking-Lot Place is covered here, and the decision to map a Parking-Lot Road is covered in the Road type article for mapping parking lot roads.
The forum discussion thread for the Parking-Lot Place is separate from the general Place thread, and is located here.

The Parking Lot 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.

Area or Point

Parking lot places can ONLY be added as an area as of August 14th, 2016 and only with the singular category of Parking Lot.

Extent

At this time, parking lots 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.

For a mall or large shopping center, break the parking lot up into multiple lots (use your discretion or discuss with your State Manager(s) or RC for official guidance if necessary.)

For underground garages it is hard to know the exact polygon, so try to estimate it based on your knowledge of the place, and in that case the accuracy of the entry point is even more important.

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.

For planned parking features, 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.

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.

Naming

Like all Places, Parking-Lot Places should be named.

If a parking facility or area has a documented identity, such as "Beach Street Garage", "18th Avenue/Geary Lot", "City Lot #7", "Short-Term Parking", "Cell-Phone Lot", 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.

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.

As with all Area Places, do not use mapping abbreviations for any part of a Parking-Lot Place name.

Drawing

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

For planned parking features, 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.

Airports

Airports typically distinguish between parking for different terminals, for short or long term, and for cell-phone/waiting. As common navigation destinations, such parking deserves to be marked with Parking-Lot Area Places and named according to the airport's documented nomenclature.


Rental-car return

With the availability of the new "Car Rental" Place, rental-car facilities and returns, including at airports, should now 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.

On-premise 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

  • Create a polygon surrounding the parking lot’s estimated perimeter (if you know its boundaries) and locate the entrance point in the original location.
  • 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.

The Parking-Lot Point Place

As of this writing, you can no longer add Parking Lots as a point place.

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.