User:Voludu2/Private Installations View history

Style guides
VisualWikitext
m (Text replacement - "Category:Style Guides" to "Category:Style guides")
 
(79 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{ReturnToEditingManual}}
{{ReturnTo | Editing manual | the editing manual}}
 
This page covers the mapping techniques to use for private installations and for neighborhoods that have restricted access of some kind.


This page tells how to map private installations and gated residential communities. These are places with one or more "controlled access points" or "gates". These methods give good routes in and out of private installations. They do not tell wazers to take short cuts through private installations. {{As of|December 2014}}, these are the best known approaches. Always consult the state manager or regional coordinator to make sure you use the method preferred for the region. Work with an editor who has experience using these method.
== Introduction ==
== Introduction ==


Line 13: Line 12:
[[File:pi_gated-community3.jpg|right|300px|Gated Community]]
[[File:pi_gated-community3.jpg|right|300px|Gated Community]]
;Private Installation
;Private Installation
:A restricted-access set of drivable roads connected at one or more points to a public road network. This could be a gated residential community, an industrial site, a pharmaceutical research campus, a secure government installation, a military base, or any other type of  installation with at least one access control point (see gate) or more than one private road. The simplest example is a single private community street protected by a gate. Larger installations might include several types of roads. The largest USA installation is White Sands Missile Range at 3,200 square miles, larger than the USA’s smallest state, and includes dirt roads, primary streets and highways. Large installations might even have smaller private installations inside of them which are closed to most of those who are inside the larger installation.
:A set of drivable roads connected to the public road network, with one or more "gates" or "controlled access points". Some examples are: a gated community, a factory site, a military base. The simplest example is one private street protected by one gate. The largest USA private installation is White Sands Missile Range with 3,200 square miles. It includes dirt roads, primary streets and highways. A large private installation may even have smaller private installations inside of them.
 
;Gate
;Gate
:Any of the points at which the installation connects to the public road network. These might have guarded or card-operated gates, "door buzzers", security cameras, or severe tire damage strips, or simply a sign stating that the road ahead is private or for members, authorized vehicles, etc.   Regardless of the physical form, we will refer to these access control points as gates
:Any point where a private installation road connects to the public road network. At these points might be a gate, traffic spikes, a guard, or simply a road sign. Gate opening might be controlled by cards, or remote "door buzzers". From now on, we will call all of these access control points "gates".


;Visitor
;Visitor
;Member. (Resident? )
:Visitors must use '''visitor gates'''. They must not use '''member gates'''.Some examples are: the pizza delivery driver, the cousin from Peoria, the tourist visiting the air force base to see the military museum.
==Purpose==
;Member
:Members may use both '''visitor gates''' and '''member gates'''. These member gates might have signs which say "members only", "residents only", "employees only", "authorized personnel only" or "military ID only".


Because Waze cannot recognize who has access to these installations and who does not, we focus on prevent inappropriate or illegal through-routing driving directions, while giving good driving directions within the installation and exiting once they get inside.
=== Purpose ===


=== Requirements ===
====Routing must be reasonable====


[[File:pi_graphic1.png|frame|Figure 1. General Concept]]
[[File:pi_graphic1.png|frame|Figure 1. General Concept]]If a wazer starts and ends a drive outside the installation, Waze must not choose a route through the installation, even if it is faster.  It must go around to get from point A to point B in figure 1. If the wazer is driving into or out of the installation, waze must choose a gate that gives the best route (from A to C or from C to A in figure 1).<br clear="all>
If both the start and end points are outside the installation, Waze must not choose a route through the installations.  If the start or end point is inside the installation, Waze be able to must find an appropriate route through and into or out of the installation, as well as through the outside roads. Figure 1 shows the general concept of a private installation which is embedded in a public road network. In this case there are two access points. Waze should route around the private installation from A to B even though a shorter or faster route might exist through the installation. Waze should also be able to route from A to C or C to A, where C is located within the private installation.
[[File:pi_graphic3.png|left | frame|Figure 2. Nested access on Private Installations.]]If one private installation is "nested" inside another private installation, routes must also be reasonable. The route from A to B in figure 2 must not go through a nested installation. a route from the deepest nested level to or from public roads (C to D or D to C in figure 2) uses the best gates.  A route between different nested levels (between E and F) does not involve any nested installations it does not need to visit.


[[File:pi_graphic3.png|left | frame|Figure 2. Nested access on Private Installations.]]
Waze should be able to take advantage of the characteristics of different road types and avoid dirt roads if the wazer requests it.


Figure 2 shows a more complex private installation with nested levels of access. Waze must oute on or off of a private installation at any level of nested access without entering a separate access area of a deeper level. Route A to B illustrates this concept. Additionally, Waze should be able to navigate from a deeper level of nested access to any other point including off the private installation. Routes between points C and D illustrates routing onto or off of the private installation. Routes between points E to F shows navigation between nested levels. Waze must also be able to take into account the different road types in a larger installation when choosing the best route.
====Must not cause map errors====
Waze must not throw map errors when members drive through any entrances and exits. This means roads must not be disconnected or prohibited by red arrows at member gates.
 
====As simple and straightforward as possible====
While it is important to lock gates at a high enough level to prevent novice editors from breaking them, the gates should be easy for editors to spot and understand. In visitor-centric constructions, time based restrictions should not be used to prevent waze from routing wazers through member-only gates all day every day for all time.


=== Approach ===
=== Approach ===
Waze does not know who is a visitor and who is member, so we can't get Waze to give different directions for each. We have to choose whether to focus on members or visitors. This is the best Waze map editors can do with the tools currently available.


Focus on the access points or gates, and control access by using the correct "recipe" for each type of gate.
To make this work, editors must focus on the access points or gates, and control access by using the correct "recipe" for each type of gate.
Inside the installation, every type of road can be used where appropriate. It is not necessary and generally not desirable to use the private road type on every road inside the installation.
Inside the installation, every type of road can be used where appropriate. Do not make all the roads private inside the installation.  
 
For the simplest type of installation, with only a single entrance/exit gate area used for both residents and guests,  there is no need to prevent "through traffic".  A "simple gate" is sufficient.
 
If  there is more than one exit, or of there is at least one resident and one guest entrance, the simple gate will not work. Instead, choose from these four types of gates:
 
Guest entrance
Guest exit
Resident entrance
Residence exit
 
=== Underlying logic ===
 
Waze uses a [[Routing_penalties#Segment_properties|routing penalty]] system to control traffic flow. This approach for controlling traffic into and through private installations depends upon that routing logic. When a Private or Parking Lot segment is used on the map, the Waze routing server places a routing penalty when transitioning '''from''' a Private or Parking Lot segment '''to''' and non-private or non-parking lot segment. When a destination is a parking lot, there is no penalty to reach the parking lot. However if the destination is on the far side of a parking lot on a standard street, Waze will try to avoid driving through the parking lot to get to the street on the other side. The same is true for private segment types.
 
=== Places / City Names for Private Installations ===
 
Should a private installation be marked over it's entire area as a Place Area (old landmark)?  Not always. Very small private installations are usually marked by a Area Place over their entire area. This does not make sense for larger private installations that might have other Places within them or that are actually cities. For these larger installations, use the city field of all street names to name the private installation.
 
In general here is specific guidance about Private Installations use of Places or City Names:
 
* Does the state DOT consider it a city? If so, then use City Names in each street to identify the installation.
* Does the US Post Office consider it a city with it's own zip code? If so, then use City Names.
* Does the local community consider it a city like entity? Then maybe it should have a City Name if it is large, or an Area Place if it is small.
* Is it large enough that an overall Area Place on the Private Installation would obscure finer detail Area Places below? If so, use City Names. If not, use an Area Place to denote the Private Installation.
 
What smaller Place should be included within a larger private installation?  We should generally follow the [http://wiki.waze.com/wiki/Places rules that are set for Places in cities and areas]. In addition to these, you might also consider marking the following as Places because they are critical navigation and destination points:
 
* Entry/Exit gates (Place Area)
* Visitor Centers (Place Area)
* Museums and other similar destinations the installation may maintain
* Memorials
* Parade Fields
* Items locally useful for navigation
 
You should avoid mapping Places that are specific to private or military uses on a private installation. See the [http://wiki.waze.com/wiki/Places Places Wiki Page] for specifics about using an Area or Point for these items.
 
=== Background Testing ===
 
Significant testing of these suggestions have been tested on actual private installations of various types and discussed in the Waze Forum. You may wish to test your edits. Here are some suggestions of how you may accomplish this after you make edits.
* Monitor that area for User Reports.
* Test drive.
** Navigate between two distant points outside the private installation to ensure no through-routing.
** Navigate from outside to inside the private installation, drive around the outside of the private installation and ensure rerouting occurs to the logical nearest gate.
** If you have access to the private installation, repeat the above, by by driving around inside the installation.
* Test routes in Live Map to ensure no through-routing and good on/off installation routing.
* Test routes in client by setting various "from" and "to" destinations without having to drive.
 
== Smaller Installations ==
 
=== Definition - Smaller Installations ===
 
'''NOTE: This approach of "Smaller Installations" is now being questioned due to routing problems observed when using this approach. We suggest that you use the "Larger Installations" approach in all cases for the moment.'''
 
Smaller installations are those private installations or communities with few roads that can be easily represented by only normal street types and that have a single level of access control. Specifying exact size is not effective because of significant variation in these installations. Typically these attributes might indicate an installation is small:  (a) less than 20-30 roads, (b) no secondary or highway streets needed.
 
Moderate sized installations between "smaller" and "larger" will exist and discretion of the local editor should be considered.
 
=== Examples ===
 
* Small gated/private community
* Gated country club with smaller area
* Private school
* Small closed commercial campus
* Very Small Military sites (e.g., National Guard armories)
* Smaller Government sites
 
This does '''not''' include paid parking lots and other parking facilities. These are to be mapped with parking lot roads. See the Special Rules section below.
 
=== Preferred Approach: Smaller Installations ===
 
[[File:pi_gated-community4.jpg|right|400px|Gated Community - Smaller Installation]]
 
Mark all roads internal to these areas as private roads.
 
Benefits of this approach are simplicity and a more robust solution to naïve editor error. If a new connection is made to this private road network from the public road network, no additional traffic will accidentally route through the region. In addition, manual locks are not usually required which allows other editors to more easily make changes.
 
Detriments of this approach are that no dirt roads, primary streets, or highways may be identified and multiple levels of access control are difficult or impossible.
 
 
=== Smaller Installation: Other Notes / Details ===
 
==== A. Mixing road types in a smaller installation ====
 
Because smaller installations are often most easily handled with all private road segments, we presented just one approach. Editors may see need for mixing other road types such as street, dirt, and parking lot within a smaller installation. Note that a single rogue normal street segment or clusters of street segments within an area set to all private roads will be avoided similarly to a private road or cluster of private roads within an area of street segments.
 
==== B. Guest Gates & Resident Gates ====
<div>Some, usually moderate sized installations, like private communities, may have some gates that are used by residents only and others that are used by residents and guests. &nbsp;Resident-only gates might be unmanned and have automated access with radio tags, card swipes, or code entry. &nbsp;Guest gates are often manned by guards that decide if access is permissible. &nbsp;Furthermore, egress by anyone is usually permitted through a guest and resident-only gate.</div><div><br/></div><div>'''Note: In Private Installation communities sufficiently large to have both guest gates and resident gates, it is recommended that roads within that installation be handled like larger installations - regular street types.''' &nbsp;This is because variations on handling differences between resident gates and visitor/resident gates will work more easily if the internal road network is not all private.</div><div><br/></div><div>There is no means to automatically route a particular Wazer through the right kind of gate because Waze does not know if the particular client is a resident or not and there is no logic in the map or client to differentiate which gate to access. &nbsp;Use of mapping per this Private Installations page will typically route to the nearest entry point.</div><div><br/></div><div>A work-around for this situation is to use a sufficiently large Area Place (so it is visible) to mark the guest access points to the Private Installation. &nbsp;Name the Area Place "X Guest Gate," where X is the name of the Private installation. &nbsp;You may use other appropriate wording. &nbsp;Then have the Wazers route to this Area Place through search or by touching it on the client display and routing to it. &nbsp;After entry into the gate, the Wazer can route to the intended destination. &nbsp;For those who know how to add a waypoint (or stop) to a Waze route the process is as follows. &nbsp;First route to the intended destination. &nbsp;Then next immediately &nbsp;route again to the Guest Gate. &nbsp;The Waze Client will ask if this should be a new stop on the route. &nbsp;Reply "yes." &nbsp;Waze will then route first to the appropriate gate, then to the indented destination within the Private Installation. &nbsp;Routing out of the installation will use the nearest gate unless this process is also followed.</div><div><br/></div><div>Do not disconnect roads to alter routing into Private Installations because this does not reflect reality in the road system, impacts residents that can enter any gate, and stops people from routing out of the Private Installation.</div><div><br/></div>
 
== Larger Installations ==
 
=== Definition: Larger Installations ===
 
Larger installations are those private installations or communities that are large enough such that there is some reason to have primary streets or highways or because that installation requires multiple levels of access control (installations within installations). Specifying exact size is not effective because of significant variation in these installations. Typically these attributes might indicate an installation is large: (a) more than 20-30 roads, (b) secondary or highway streets needed.
 
Moderate sized installations between "smaller" and "larger" will exist and discretion of the local editor should be considered.
 
=== Examples: ===
 
* Larger Military base
* Larger Government sites
* Huge hunting lodge and hunting grounds, ranches, etc.
* Large closed commercial campus
* Large country club or private communities with multiple entrances


Private installations covered by this article do '''not''' include airports or theme parks. See the bottom of this article for special rules concerning roads in airports and theme parks.
The six types of gates can be divided into two classes -- simple and everything else. For the simplest type of installation, where there is only one exit, a simple gate will work. For any installation that has more than one exit, the simple gate will cause strange routing out of the installation -- we don't know why -- and the other types of gates must be used. Never mix the simple gate with the other types of gates in the same installation.


=== Larger Installation Treatment common attributes: ===
=== Why this works===


The general approach is to isolate the entire installation from the public road network with private roads or one-way exit roads. This will prevent Waze from routing through a private installation unless the route begins or ends on the installation. All roads within an installation will be of type appropriate for that road (dirt road, street, primary street, minor highway, major highway, freeway). In order to prevent novice editors from changing these access controls, the private and one-way roads, and any necessary connecting roads should be locked at a level as high as appropriate or possible.
The current approach to constructing gates takes advantage of the Waze [[Routing_penalties#Segment_properties|routing penalty]] system to control driving directions. For every route that includes private segments, Waze imposes a penalty each time the route goes from ''from''' a Private segment '''to''' any other road type. This causes Waze to avoid driving through a private segment to get to the street on the other side, even if it has to find a longer and more time-consuming route to get there. Because of this, Waze editors can use private segments at gates to prevent Waze from giving routes that short-cut through private installations.


Benefits of the two following treatments are allowing full use of road types within the installation resulting in better routing and a simple logical notion that the private segments (or one-way segments) represent the gates or guards on a road protecting entrance into an installation. It also allows nested levels of access control. The approach for smaller installations does not allow this to occur.
==How to ==
All the segments used in gate recipes must be at least {{:Segment length/Minimum}} long. Check the house numbers.  If they are supposed to be inside the installation, make sure they are not on any of the gate segments.


Detriments of the two following treatments are that the private road segments isolating the installation from the public road network and internal nested installations should be locked to prevent change by novice editors. In addition, a novice user could connect one or more new roads between the installation and the public road network that would potentially begin to have Waze route through installation roads that are not accessible; however, this would require two such errors by the novice and should result in URs and those areas could be repaired and locked in the future.
Remember to follow all [[Junction_Style_Guide#Loops|best editing practices]], including the rule against [[Junction_Style_Guide#Loops|two segments sharing the same two junction nodes]].


----
===Simple Installations===
=====Gate recipes=====
* Simple Gate -- one  2-way private road segment. If a place is used to mark the gate, put the stop point in the middle of the segment. Do not mix simple gates with any other type of gate in the same installation.
=====Application=====
If there is only a single entrance/exit, use a simple gate. If there is more than one exit or entrance,  do not use any simple gates.  If you use a Simple gate in a private installation with more than one exit, Waze will not find the best possible route out of the installation.


<span style="color: red"><b>Warning:</b></span>  Do not mix the two treatments (preferred & alternate) shown below on the same nested level of a private installation. If you do, exit routing from an installation would favor the one-way regular exit roads and avoid the two-way entrance/exits. This would create incorrect exit routing. You may mix the preferred/alternate treatments at different nested levels. For instance you may use the preferred treatment at the first level of an installation and then use the alternate treatment for a second internal nested level.
===All other installations===
{{mbox|type=forum|text=for the ongoing discussion of member-centric vs resident-centric routing, please see [http://www.waze.com/forum/viewtopic.php?f=276&t=51419&start=10#p1006240 the current forum discussion]}}
====Current Standard: Member-centric method====
This method is used throughout the US, except in California, Arizona, and Nevada. Check with your State Manager or Regional Coordinator. Waze will use traffic information to route Wazers through the best gate for members.  Visitors might be routed through a member gate and be refused admittance when they get there. Visitors can select the gate of their choice as their destination or "add a stop".


----
=====Gate Recipes=====
 
*Standard gate -- a one one-way private road segment heading into the installation, paired with a one-way segment heading out of the installation.  The outgoing segment is of the same road type as the segments on either side of it. If a place is used to mark the gate, put the stop point as close as possible to the physical location of the gate.
=== Preferred Treatment: Larger Installations ===


=====Application=====
[[File:pi_graphic4.png|right|250px|Access Point detail - Preferred Treatment]]
[[File:pi_graphic4.png|right|250px|Access Point detail - Preferred Treatment]]
Each entrance to the installation should be connected by a one-way divided road entering and exiting the installation. The entering one-way road will include one private road segment. The exiting one-way road will be the same type of road (usually street, primary street, or minor highway) as the segments on either side of it. This structure often mimics the actual lanes for such installations. The private road segments, one way exiting segments, and surrounding roads should be locked with a high enough level lock to prevent novice editors from deleting or changing this control.


Each entrance to the installation should be connected by a one-way split road entering and exiting the installation. The entering one-way road will include one private road segment. The exiting one-way road will be of one segment using the appropriate type of that road (usually street, primary street, or minor highway). This structure often mimics the actual lanes for such installations. The private road segments, one way exiting segments, and surrounding roads should be locked with a high enough level lock to prevent novice editors from deleting or changing this control.
[[File:pi_large_gate1.jpg|frame|center|Larger installation preferred treatment example. Note that this road is of a "primary" type but the private segment used for the inbound lane is used to prevent through-routing.]]


[[File:pi_large_gate1.jpg|center|frame|Larger installation preferred treatment example. Note that this road is of a "primary" type but the private segment used for the inbound lane is used to prevent through-routing.]]
[[File:pi_large_gate2.jpg|frame|center|Larger installation preferred treatment example. Note that this road is of a regular "street" type. The private road segment is used for the inbound lane.]]


[[File:pi_large_gate2.jpg|center|frame|Larger installation preferred treatment example. Note that this road is of a regular "street" type. The private road segment is used for the inbound lane.]]
Nested private installations (wholly within another private installation) can be treated by this method or by one of the other methods.


Nested private installations (wholly within another private installation) will likewise be isolated in the same manner or '''Alternate Treatment''' from the larger installation.
;Pros
:The exiting road can be of any type and introduces no penalty to routing out of the installation.
;Cons
:A little more complicated than the simple approach.


Benefits of this preferred treatment is that it allows the exiting road to be of any type and of no penalty to routing out of the installation.
{{mbox|type=warning|text=See warning above in the "Common Attributes" section about mixing the preferred and alternate treatments within the same nested level of a private installation.}}


A detriment of this treatment is a more complex structure than the alternate treatment for larger installations.
====Visitor-centric method====
In the US, this approach is used in California, Arizona, and Nevada.  Do not use it anywhere else in the U.S. Check with your state manager or regional coordinator for more information.
Waze will route everyone through the visitor's gates, which everyone can travel through. Waze does not route anyone through the member gates.  Anyone wishing to use a specific member gate can "add a stop" at that gate.  This method allows Waze to use traffic information to find the best route from among all available visitor gates. Members who live or work in the installation and travel in and out daily might not get the best route from Waze.


----
=====Gate recipes=====
* Visitor Entrance -- one one-way private road segment heading into the installation. If a place is used, put the stop point next to the middle of the private segment.
* Visitor Exit -- (nothing) no private segment is needed. Use the same road type as the rest of the road the gate is on.  If a place is used to mark the gate, put the stop point as close as possible to the physical location of the gate.
* Member Entrance -- Three one-way segments, headed into the installation, in this order: private, street, private.  If a place is used to mark the gate, put the stop point next to the middle of the middle street segment.
* Member Exit -- one one-way private segment.  If a point place is used to mark the gate, put the stop point next to the middle of the private segment.
* Member 2-way gate -- Three 2-way segments, in this order: private, street, private.  If a place is used to mark the gate, put the stop point next to the middle of the middle (street) segment.
* Closed Gates or fences -- these are closed nearly all the time, and only opened for special purposes -- disconnect the road at this point.


<span style="color: red"><b>Warning:</b></span> See warning above in the "Common Attributes" section about mixing the preferred and alternate treatments within the same nested level of a private installation.
=====Application=====
A visitor entrance and visitor exit are combined as a
[[File:Gate Types Example.png|thumb|400px|All types of Entrance and exit gates. ''courtesy ottonomy'']]If there is more than one entrance or exit, do not use any simple gates.  Instead,  select from the other types of gates.<!--
[[File:pi_large_gate2.jpg|thumb|400px|Visitor entrance and exit gates.]][[File:pi_graphic4.png|left|250px|Visitor entrance and exit gates.]]-->Usually, gates come in matched entrance/exit pairs, but sometimes a single member-only exit is located at some distance from any entrances in a gated community.  Remember that if visitors and guests can use a gate at the same location, even if they have separate lanes, it is not normally necessary to create separate gates on the map. Simply use a visitor entrance or exit: Wazers can generally follow the signs to enter or exit via the correct lane.
<br clear="all"/>


----
===Nested Private Installations===
When one private installation is located inside another,  simply follow the same rules to construct all the gates for the smaller installation within the larger.


=== Alternate Treatment: Larger Installations ===
=== Checking your work ===


[[File:pi_graphic5.png|right|250px|Access Point detail - Alternate Treatment]]
Check your work. If you run into any routing problems, check the discussions on the forums and ask questions in chat.
*Use the Waze Live Map to test routing between several pairs of test points inside and outside the installation.
* choose both  "from" and "to" destinations from the mobile app to see the routes.
* Expect to see routes involving visitor gates.
* Watch for User Reports in the area.  If users complain Waze will not route them through member-only gates, point them to how to add a stop along the way to go through their preferred gate. Waze can only route through the visitors gates
* if you have acces to the installation, try driving around  outside, inside, from, and to the installation.  Go off-route.  Check that Waze re-routing makes sense -- routes in or out are always to the most sensible gate to reach your destination, not necessarily the nearest gate.


An alternate approach for these installations is to connect to public road networks through one short private two-way road segment at each entrance or exit to the installation. This effectively isolates the entire installation from the public road network unless a route begins or ends within the installation. All roads within an installation will be of type appropriate for that road (dirt road, street, primary street, minor highway, major highway, freeway). The private road segments and surrounding roads should be locked with a high enough level lock to prevent novice editors from deleting or changing this control.
==Optional ingredients==
<!-- this is a comment and will not be visible in the document -->
<!--
===Point places for gates===
These should generally only be used for very large installations, such as large military bases. It is rare for a gate itself to be a destination for wazers.
-->
===Gate Closures and Restrictions ===
If some gates are closed at certain times of day or days of the week, or on certain dates, use  [[Scheduled Restrictions]] on the affected gate.  Apply the restriction to just one gate segment.  For a member entrance, apply it to the last-traversed (innermost) segment.  Check to make sure entrance/exit pairs have the same closing hours.You can find the hours of gates or entry points through the private installation website or by calling the appropriate private installation authority.


[[File:pi_large_alt1.jpg|500px|left|Alternate Treatment for Larger Installations]]
=== Places or City Names ===


Nested private installations (wholly within another private installation) will likewise be isolated in the same manner or '''Preferred Treatment''' from the larger installation.
Small private installations are usually marked by a Area Place over their entire area. This does not make sense for larger private installations that might have other Places within them or that are actually cities. For these larger installations, use the city field of all street names to name the private installation.  


Benefit of this alternate treatment is that it is structurally simpler than the preferred treatment.
If it meets any of these criteria, treat it as a city:
* Does the state DOT consider it a city?
* Does the US Post Office consider it a city with it's own zip code?
* Is it large enough that an overall Area Place on the Private Installation would obscure finer detail Area Places below?
Finally, if the local community considers it a city like entity, then maybe it should have a City Name if it is large, or an Area Place if it is small.


Detriment of this treatment is that it does not allow any road type to be used for the exiting protective one-way segments in the preferred treatment.
For places within the installation, follow the [[Places |guidelines for point and area places]]. Also consider marking the following as Places because they are critical navigation and destination points:
 
* Entry/Exit gates (Place Area)
----
* Visitor Centers (Place Area)
 
* Museums and other similar visitor destinations
<span style="color: red"><b>Warning:</b></span> See warning above in the "Common Attributes" section about mixing the preferred and alternate treatments within the same nested level of a private installation.
* Memorials
 
* Parade Fields
----
* Items locally useful for navigation
 
===Alerting other Editors===
=== Larger Installation: Other Notes / Details ===
Lock the gate segments so beginner editors will not break them. If a road is permanently blocked, disconnect the road at that point and leave a note. To create a note, use the Live Map to report a map problem. Begin the description with [NOTE], give your username, and explain the edit.
 
==== A. Public Roads Across Private Installations ====
 
Many larger military bases and perhaps other private installations sometimes have long right-of-way permissions for a publicly accessible road, often times this is a highway or primary street. (e.g., US-70 through White Sands Missile Range.) These highways run across the private installation with no restriction to traffic but provide no access to the installation itself. Editors should not create any access restrictions in these regions. Because these roads are often times fenced off on both sides from the private installation, editors should be on the look out for private installation roads inappropriately connected to the public road. These are usually locked off by gates most of the time, in which case the road can be disconnected or have a gap. Some of these are entry/exit gates with treatments noted above.
 
==== B. Preventing Other Editors from Making Mistakes ====
 
One method of preventing mistakes from novice editors has already been discussed, locking of the private road segments and surrounding segments. There is another approach that may be valuable.
 
Larger private installations, such as a military base, that are embedded in a city often have legacy roads that used to connect to the public road network. From the Waze Editor aerial images, it can look like these roads actually connect to the private installation, when upon closer inspection (if possible) there is really a fence that permanently blocks the road. There may also be a fence gate that is closed most of the time, only opened when guards are present. In both these situations, there should be no road connection, or a gap in the road network within the Waze Editor.
 
Novice editors or experienced editors that are not paying attention, may accidentally connect these roads when they should not be connected. One should lock these segments. One may also put a signpost only available to editors noting this issue. Until Waze implements signposts for editors, one may use Live Map to inert a Problem Report at the location, then go back to that report in the editor and enter a note such as "Do not delete this report. &nbsp;Fence gate at this location is always closed." This should alert and remind editors that the roads should not be connected.
 
==== C. Gate Closures and Restrictions ====
 
Many larger installations will have access/entry points or gates that have limited hours or that are closed on certain holidays. Utilize [[Scheduled Restrictions]] in the editor to allow Waze to know when to route through a particular gate. These are typically not turn restrictions, but restrictions on traversing a segment. Some gates can be very isolated on larger installations so routing may navigate someone 10 to 30 minutes to a closed gate.


When doing this, enable [[Scheduled Restrictions]] for only one segment in each direction to reduce editing errors and maintenance. This segment should be the private road segment on the inbound direction (or the single two-way private segment). For entry points with a one-way outbound regular road type, it should be the segment adjacent to the private inbound segment. Scheduled restrictions would usually be the same on these two segments unless the private installation has differing entry and exit policy.
==Places with special rules==
===Military Bases and Government Installations ===


You can find the hours of gates or entry points through the private installation website or by calling the appropriate private installation authority.
Do not mark specific locations with a Place unless the it his is already public information found on road maps or the installation's public website, in maps or directories. Secure installations often do not provide information about hangar numbers, building numbers, organizational names.


==== D. Area Places for Access/Entry Points ====
====Landmarks (Places) approved for military bases ====
 
Entry points for larger Private Installations are typically named such as "North Gate" or "Maxwell Gate." These are Area Places that are useful for those using Waze to understand their location relative to the Access Point. It is suggested an Area Place of type "Professional and public" then "Government" be generated over the larger region of the Access Point and named with the short name of that Access Point. Do not make the Area Place just the size of the guard houses or other features. Make it large enough to encompass the area so that it is easily seen on the Waze client.
 
If you do not know the name of the Access Point, do not create an Area Place. Names of Access Points may be known locally or found on on a website about the private installation.
 
Additional information about Places is in the [[#Military_Bases_and_Government_Installations|Special Rules section]].
 
== Installations with Special Rules ==
 
=== Military Bases and Government Installations ===
 
While road treatment is covered in the body of this Wiki page, questions often arise about what items to landmark by adding Area and Point Places on these facilities. &nbsp;This is particularly important if you have access to these locations as a resident, worker, or visitor and use that access to learn something about the Private Installation. &nbsp;A general rule is to not mark specific locations with a Place unless the public installation website provides that information via directors or maps. &nbsp;Specific examples of what not to map include organizational names occupying buildings, building numbers, hangar numbers, etc. when they are not publicly available. &nbsp;Examples of items to usually map include gates, visitor access points, and frequent destinations like marching fields, parks, museums, etc.
 
==== Landmarks (Places) approved for military bases ====
<ul style="/* insecure input */">
<ul style="/* insecure input */">
<li>Commissary</li>
<li>Commissary</li>
Line 242: Line 155:
<li>Parks</li>
<li>Parks</li>
<li>Museums</li>
<li>Museums</li>
<li>Visitor Gates</li>
</ul>
</ul>


Line 254: Line 168:
=== Airports ===
=== Airports ===


Do not map the private, restricted-access roads on airport grounds at all. Map airport roads which are accessible to the public (terminal pick-up/drop-off roads, parking lot access roads, etc.) as public roads, not as private installations.
Only map airport roads which are accessible to the public (terminal pick-up/drop-off roads, parking lot access roads, etc.).  Do not map "air-side" restricted road networks that allow traffic for baggage carts, service vehicles, airplane fuel tankers, etc. Here's why:
 
Airports have "air-side" restricted road networks that allow traffic for baggage carts, service vehicles, airplane fuel tankers, etc. While it may be tempting to map this road network either as an isolated set of roads or with provisions cited elsewhere in this document for Private Installations, this should not be done. Here's why:


*A large number of people use Waze to navigate to airports. The particular search service or function that returns a GPS coordinate to Waze may be in error, placing the destination marker nearer to the air-side private road network of the airport than to the public airport roads. This could lead to an incorrect route or even an impossible-to-reach destination, which would frustrate the traveler.
* Wazers use a variety of terms to search for airports. This means that, often, they wind up with a search result that came from a non-Waze service, and these are often closer to the air-side roads than to the public airport roads. Editors have carefully adjusted the map around most large airports to take this into account.  Adding these private roads can cause Waze to route wazers to the "wrong side" of the airport through roads they will not be able to enter, and may cause them to miss their flights.
*The private air-side road network of an airport tends to be both close to and accessible from the public road networks around the airport and therefore is more prone to this navigation error.
* The private air-side roads often run close to public roads.  GPS error can cause Waze to think wazers on a public road are actually on the private road.  
*Very few people use the private road network of an airport, relative to the great number that use an airport's public access roads. To those that have requested this function, we apologize. The benefit of doing this for few would likely inconvenience many. We suggest routing to the nearest spot to your destination (i.e., the gate) on the public road network.
* Very few people use the private road network of an airport. A lot of people use an airport's public access roads.  
* For those who want to navigate to employee or service entrances, create point places.  
We apologize to airport employees and service providers.  


In some cases, military bases hold public airports. In such situations, some discretion and creativity may be needed to decide which roads on the airport should not be mapped and which on the military base should be mapped. Usually there is a second perimeter around the airport separating it from the base.
When public airports are within military bases, use care  and creativity in deciding which airport roads and which base roads should and should not be mapped. Check routing after making any changes.


{{ReturnToEditingManual}}
{{ReturnTo | Editing manual | the editing manual}}


[[Category:Style Guides]]
[[Category:Style guides]]

Latest revision as of 06:25, 14 August 2022

This page tells how to map private installations and gated residential communities. These are places with one or more "controlled access points" or "gates". These methods give good routes in and out of private installations. They do not tell wazers to take short cuts through private installations. As of December 2014, these are the best known approaches. Always consult the state manager or regional coordinator to make sure you use the method preferred for the region. Work with an editor who has experience using these method.

Introduction

Definitions

Military Bases
Military Bases
Gated Community
Gated Community
Gated Community
Gated Community
Private Installation
A set of drivable roads connected to the public road network, with one or more "gates" or "controlled access points". Some examples are: a gated community, a factory site, a military base. The simplest example is one private street protected by one gate. The largest USA private installation is White Sands Missile Range with 3,200 square miles. It includes dirt roads, primary streets and highways. A large private installation may even have smaller private installations inside of them.
Gate
Any point where a private installation road connects to the public road network. At these points might be a gate, traffic spikes, a guard, or simply a road sign. Gate opening might be controlled by cards, or remote "door buzzers". From now on, we will call all of these access control points "gates".
Visitor
Visitors must use visitor gates. They must not use member gates.Some examples are: the pizza delivery driver, the cousin from Peoria, the tourist visiting the air force base to see the military museum.
Member
Members may use both visitor gates and member gates. These member gates might have signs which say "members only", "residents only", "employees only", "authorized personnel only" or "military ID only".

Purpose

Routing must be reasonable

Figure 1. General Concept

If a wazer starts and ends a drive outside the installation, Waze must not choose a route through the installation, even if it is faster. It must go around to get from point A to point B in figure 1. If the wazer is driving into or out of the installation, waze must choose a gate that gives the best route (from A to C or from C to A in figure 1).

Figure 2. Nested access on Private Installations.

If one private installation is "nested" inside another private installation, routes must also be reasonable. The route from A to B in figure 2 must not go through a nested installation. a route from the deepest nested level to or from public roads (C to D or D to C in figure 2) uses the best gates. A route between different nested levels (between E and F) does not involve any nested installations it does not need to visit.

Waze should be able to take advantage of the characteristics of different road types and avoid dirt roads if the wazer requests it.

Must not cause map errors

Waze must not throw map errors when members drive through any entrances and exits. This means roads must not be disconnected or prohibited by red arrows at member gates.

As simple and straightforward as possible

While it is important to lock gates at a high enough level to prevent novice editors from breaking them, the gates should be easy for editors to spot and understand. In visitor-centric constructions, time based restrictions should not be used to prevent waze from routing wazers through member-only gates all day every day for all time.

Approach

Waze does not know who is a visitor and who is member, so we can't get Waze to give different directions for each. We have to choose whether to focus on members or visitors. This is the best Waze map editors can do with the tools currently available.

To make this work, editors must focus on the access points or gates, and control access by using the correct "recipe" for each type of gate. Inside the installation, every type of road can be used where appropriate. Do not make all the roads private inside the installation.

The six types of gates can be divided into two classes -- simple and everything else. For the simplest type of installation, where there is only one exit, a simple gate will work. For any installation that has more than one exit, the simple gate will cause strange routing out of the installation -- we don't know why -- and the other types of gates must be used. Never mix the simple gate with the other types of gates in the same installation.

Why this works

The current approach to constructing gates takes advantage of the Waze routing penalty system to control driving directions. For every route that includes private segments, Waze imposes a penalty each time the route goes from from' a Private segment to any other road type. This causes Waze to avoid driving through a private segment to get to the street on the other side, even if it has to find a longer and more time-consuming route to get there. Because of this, Waze editors can use private segments at gates to prevent Waze from giving routes that short-cut through private installations.

How to

All the segments used in gate recipes must be at least 19.69 ft (6 m) long. Check the house numbers. If they are supposed to be inside the installation, make sure they are not on any of the gate segments.

Remember to follow all best editing practices, including the rule against two segments sharing the same two junction nodes.

Simple Installations

Gate recipes
  • Simple Gate -- one 2-way private road segment. If a place is used to mark the gate, put the stop point in the middle of the segment. Do not mix simple gates with any other type of gate in the same installation.
Application

If there is only a single entrance/exit, use a simple gate. If there is more than one exit or entrance, do not use any simple gates. If you use a Simple gate in a private installation with more than one exit, Waze will not find the best possible route out of the installation.

All other installations

 for the ongoing discussion of member-centric vs resident-centric routing, please see the current forum discussion

Current Standard: Member-centric method

This method is used throughout the US, except in California, Arizona, and Nevada. Check with your State Manager or Regional Coordinator. Waze will use traffic information to route Wazers through the best gate for members. Visitors might be routed through a member gate and be refused admittance when they get there. Visitors can select the gate of their choice as their destination or "add a stop".

Gate Recipes
  • Standard gate -- a one one-way private road segment heading into the installation, paired with a one-way segment heading out of the installation. The outgoing segment is of the same road type as the segments on either side of it. If a place is used to mark the gate, put the stop point as close as possible to the physical location of the gate.
Application
Access Point detail - Preferred Treatment
Access Point detail - Preferred Treatment

Each entrance to the installation should be connected by a one-way divided road entering and exiting the installation. The entering one-way road will include one private road segment. The exiting one-way road will be the same type of road (usually street, primary street, or minor highway) as the segments on either side of it. This structure often mimics the actual lanes for such installations. The private road segments, one way exiting segments, and surrounding roads should be locked with a high enough level lock to prevent novice editors from deleting or changing this control.

Larger installation preferred treatment example. Note that this road is of a "primary" type but the private segment used for the inbound lane is used to prevent through-routing.
Larger installation preferred treatment example. Note that this road is of a regular "street" type. The private road segment is used for the inbound lane.

Nested private installations (wholly within another private installation) can be treated by this method or by one of the other methods.

Pros
The exiting road can be of any type and introduces no penalty to routing out of the installation.
Cons
A little more complicated than the simple approach.
 See warning above in the "Common Attributes" section about mixing the preferred and alternate treatments within the same nested level of a private installation.

Visitor-centric method

In the US, this approach is used in California, Arizona, and Nevada. Do not use it anywhere else in the U.S. Check with your state manager or regional coordinator for more information. Waze will route everyone through the visitor's gates, which everyone can travel through. Waze does not route anyone through the member gates. Anyone wishing to use a specific member gate can "add a stop" at that gate. This method allows Waze to use traffic information to find the best route from among all available visitor gates. Members who live or work in the installation and travel in and out daily might not get the best route from Waze.

Gate recipes
  • Visitor Entrance -- one one-way private road segment heading into the installation. If a place is used, put the stop point next to the middle of the private segment.
  • Visitor Exit -- (nothing) no private segment is needed. Use the same road type as the rest of the road the gate is on. If a place is used to mark the gate, put the stop point as close as possible to the physical location of the gate.
  • Member Entrance -- Three one-way segments, headed into the installation, in this order: private, street, private. If a place is used to mark the gate, put the stop point next to the middle of the middle street segment.
  • Member Exit -- one one-way private segment. If a point place is used to mark the gate, put the stop point next to the middle of the private segment.
  • Member 2-way gate -- Three 2-way segments, in this order: private, street, private. If a place is used to mark the gate, put the stop point next to the middle of the middle (street) segment.
  • Closed Gates or fences -- these are closed nearly all the time, and only opened for special purposes -- disconnect the road at this point.
Application

A visitor entrance and visitor exit are combined as a

All types of Entrance and exit gates. courtesy ottonomy

If there is more than one entrance or exit, do not use any simple gates. Instead, select from the other types of gates.Usually, gates come in matched entrance/exit pairs, but sometimes a single member-only exit is located at some distance from any entrances in a gated community. Remember that if visitors and guests can use a gate at the same location, even if they have separate lanes, it is not normally necessary to create separate gates on the map. Simply use a visitor entrance or exit: Wazers can generally follow the signs to enter or exit via the correct lane.


Nested Private Installations

When one private installation is located inside another, simply follow the same rules to construct all the gates for the smaller installation within the larger.

Checking your work

Check your work. If you run into any routing problems, check the discussions on the forums and ask questions in chat.

  • Use the Waze Live Map to test routing between several pairs of test points inside and outside the installation.
  • choose both "from" and "to" destinations from the mobile app to see the routes.
  • Expect to see routes involving visitor gates.
  • Watch for User Reports in the area. If users complain Waze will not route them through member-only gates, point them to how to add a stop along the way to go through their preferred gate. Waze can only route through the visitors gates
  • if you have acces to the installation, try driving around outside, inside, from, and to the installation. Go off-route. Check that Waze re-routing makes sense -- routes in or out are always to the most sensible gate to reach your destination, not necessarily the nearest gate.

Optional ingredients

Gate Closures and Restrictions

If some gates are closed at certain times of day or days of the week, or on certain dates, use Scheduled Restrictions on the affected gate. Apply the restriction to just one gate segment. For a member entrance, apply it to the last-traversed (innermost) segment. Check to make sure entrance/exit pairs have the same closing hours.You can find the hours of gates or entry points through the private installation website or by calling the appropriate private installation authority.

Places or City Names

Small private installations are usually marked by a Area Place over their entire area. This does not make sense for larger private installations that might have other Places within them or that are actually cities. For these larger installations, use the city field of all street names to name the private installation.

If it meets any of these criteria, treat it as a city:

  • Does the state DOT consider it a city?
  • Does the US Post Office consider it a city with it's own zip code?
  • Is it large enough that an overall Area Place on the Private Installation would obscure finer detail Area Places below?

Finally, if the local community considers it a city like entity, then maybe it should have a City Name if it is large, or an Area Place if it is small.

For places within the installation, follow the guidelines for point and area places. Also consider marking the following as Places because they are critical navigation and destination points:

  • Entry/Exit gates (Place Area)
  • Visitor Centers (Place Area)
  • Museums and other similar visitor destinations
  • Memorials
  • Parade Fields
  • Items locally useful for navigation

Alerting other Editors

Lock the gate segments so beginner editors will not break them. If a road is permanently blocked, disconnect the road at that point and leave a note. To create a note, use the Live Map to report a map problem. Begin the description with [NOTE], give your username, and explain the edit.

Places with special rules

Military Bases and Government Installations

Do not mark specific locations with a Place unless the it his is already public information found on road maps or the installation's public website, in maps or directories. Secure installations often do not provide information about hangar numbers, building numbers, organizational names.

Landmarks (Places) approved for military bases

  • Commissary
  • PX/BX
  • Gas stations
  • Parks
  • Museums
  • Visitor Gates

Parking Lots

Paid parking lots and other parking facilities are to be mapped with parking lot roads, and not according to the Private Installation rules defined in this article. See Best map editing practice#Parking Lots.

Theme Parks

Publicly accessible roads in a theme park, even after a pay-station/gate, are to be mapped with parking lot roads, similarly to other paid parking lots. Furthermore, be careful with mapping the "backstage" private roads which are only to be used by employees. It may be wise to not map these roads, similarly to "air-side" airport roads as described below (but to a lesser extent), so that routes are given to the public entrance of the theme park facility.

Airports

Only map airport roads which are accessible to the public (terminal pick-up/drop-off roads, parking lot access roads, etc.). Do not map "air-side" restricted road networks that allow traffic for baggage carts, service vehicles, airplane fuel tankers, etc. Here's why:

  • Wazers use a variety of terms to search for airports. This means that, often, they wind up with a search result that came from a non-Waze service, and these are often closer to the air-side roads than to the public airport roads. Editors have carefully adjusted the map around most large airports to take this into account. Adding these private roads can cause Waze to route wazers to the "wrong side" of the airport through roads they will not be able to enter, and may cause them to miss their flights.
  • The private air-side roads often run close to public roads. GPS error can cause Waze to think wazers on a public road are actually on the private road.
  • Very few people use the private road network of an airport. A lot of people use an airport's public access roads.
  • For those who want to navigate to employee or service entrances, create point places.

We apologize to airport employees and service providers.

When public airports are within military bases, use care and creativity in deciding which airport roads and which base roads should and should not be mapped. Check routing after making any changes.

Retrieved from "https://www.waze.com/wiki/USA/index.php?title=User:Voludu2/Private_Installations&oldid=176811"