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 "User:Karlcr9911"

From waze
Jump to: navigation, search
m (PLA)
m
Line 1: Line 1:
<!--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}}
+
== Overview ==
<!--
+
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-----
+
####    This page has been curated  ####
+
####    to be included in the new    ####
+
####    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      ####
+
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-->
+
  
{{construction
+
Multi-State Manager, or "MSM," is a formal role in the US editor self-management system.
| contact    = http://www.waze.com/forum/viewtopic.php?f=276&t=87595
+
| contacttype = forum
+
| draft      = no
+
| open        = no
+
}}
+
  
== Parking Lots ==
+
== Roles & Responsibilities ==
  
:''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]].''
+
Multi-State Managers are granted some or all of the [[State Manager/USA#Roles_.26_Responsibilities | roles and responsibilities]] of a "full" [[State_Manager/USA | State Manager]] for the states within their MSM area by their [[Regional Coordinator/USA | Regional Coordinator]].  
  
:''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].''
+
Each Regional Coordinator identifies the exact portions of the State Manager role that MSM's are expected to perform for the states included in their purview. As such, the specific implementation of the role is likely to differ between regions.
  
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.
+
Each Regional Coordinator also identifies the states included in each MSM's purview; the collection of states granted may differ for each MSM within a region.
  
=== Area or Point ===
+
== Requirements ==
  
Parking lot places can ONLY be added as an area as of August 14th, 2016 and only with the singular category of ''Parking Lot''.  
+
The Requirements to be eligible for the Multi-State Manager role are identical to those of [[State Manager/USA#Requirements | State Managers]].
  
==== Extent ====
+
Ideally, a State Manager would be rank 4 and a Multi-State Manager would be rank 5.  This can vary by region and at the needs of each Regional Coordinator.
  
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.
+
== How to become a Multi-State Manager ==
  
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.)
+
Regional Coordinators grant Multi-State Manager promotions to State Managers in their regions.
 
+
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.
+

Revision as of 19:46, 27 April 2017

Overview

Multi-State Manager, or "MSM," is a formal role in the US editor self-management system.

Roles & Responsibilities

Multi-State Managers are granted some or all of the roles and responsibilities of a "full" State Manager for the states within their MSM area by their Regional Coordinator.

Each Regional Coordinator identifies the exact portions of the State Manager role that MSM's are expected to perform for the states included in their purview. As such, the specific implementation of the role is likely to differ between regions.

Each Regional Coordinator also identifies the states included in each MSM's purview; the collection of states granted may differ for each MSM within a region.

Requirements

The Requirements to be eligible for the Multi-State Manager role are identical to those of State Managers.

Ideally, a State Manager would be rank 4 and a Multi-State Manager would be rank 5. This can vary by region and at the needs of each Regional Coordinator.

How to become a Multi-State Manager

Regional Coordinators grant Multi-State Manager promotions to State Managers in their regions.