User:Voludu2/Private Installations View history

Style Guides
VisualWikitext
(→‎Smaller Installations: Size doesn't matter)
(→‎Larger Installations: Size doesn't matter)
Line 95: Line 95:
==All other Installations==
==All other Installations==
Blah blah blah
Blah blah blah
== 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.
=== Larger Installation Treatment common attributes: ===
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.
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.
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.
----
<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.
----
=== Preferred Treatment: Larger Installations ===
[[File:pi_graphic4.png|right|250px|Access Point detail - Preferred Treatment]]
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|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|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) will likewise be isolated in the same manner or '''Alternate Treatment''' from the larger installation.
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.
A detriment of this treatment is a more complex structure than the alternate treatment for larger installations.
----
<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.
----
=== Alternate Treatment: Larger Installations ===
[[File:pi_graphic5.png|right|250px|Access Point detail - Alternate Treatment]]
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.
[[File:pi_large_alt1.jpg|500px|left|Alternate Treatment for Larger Installations]]
Nested private installations (wholly within another private installation) will likewise be isolated in the same manner or '''Preferred Treatment''' from the larger installation.
Benefit of this alternate treatment is that it is structurally simpler than the preferred treatment.
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.
----
<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.
----
=== Larger Installation: Other Notes / Details ===
==== 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.
You can find the hours of gates or entry points through the private installation website or by calling the appropriate private installation authority.
==== D. Area Places for Access/Entry Points ====
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 ==
== Installations with Special Rules ==

Revision as of 00:29, 8 December 2014

Template:ReturnToEditingManual

This page covers the mapping techniques to use for private installations and for neighborhoods that have restricted access of some kind.

Introduction

Definitions

Military Bases
Military Bases
Gated Community
Gated Community
Gated Community
Gated Community
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.
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


Member
Anyone who can use any of the entrance or exit gates at the installation, including the the more restricted "members only", "residents only", "employees only, "base personnel only", "military ID only" , "authorized personnel only", etc gates (if any) used at the installation.
Visitor
Anyone limited to certain entrance and/or exit gates. This could be the pizza delivery driver, the cousin from Peoria, the tourist visiting the air force base to see the military museum, etc.

Requirements

Figure 1. General Concept

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.

Figure 2. Nested access on Private Installations.

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.

Finally, While visitors must not be routed through member-only entrances and exits, Waze must not throw map errors when members drive through member-only entrances and exits. This means these entrances must not be disconnected or prohibited by red arrows or time based restrictions.

Approach

Because Waze cannot recognize who has access to these installations and who does not, we focus on appropriate directions for visitors; preventimg inappropriate or illegal through-routing driving directions, while giving good driving directions within the installation and exiting once they get inside. Members are expected to have more knowledge of the installation. If they wish to use a specific member entrance gate, they can add it as a stop along the way. This may not result in the ideal routing for the members, but is the best Waze map editors can achieve 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. It is not necessary and generally not desirable to use the private road type on every road inside the installation.

The five types of gates are: simple gate; visitor entrance; visitor exit; member entrance; member exit. For the simplest type of installation, where visitors may use every entrance and every exit gate at all times, a simple gate is sufficient.

For any installation that has at least one visitor entrance or exit, plus at least one member-only entrance or exit, the simple gate will not allow proper routing out of the installation -- the other four types of gates must be used.

Underlying logic

The current approach to constructing gates takes advantage of the Waze routing penalty system to control traffic flow. When a Private Road segment is used on the map, the Waze routing server imposes a routing penalty when transitioning from a Private segment to any other road type. When a destination is on a private segment, there is no penalty to enter the private roadway. However if the destination is on the far side of the private road on a standard street, Waze will try to avoid driving through the 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. To inhibit routes that travel through private installations, Waze editors can employ private segments at the entrances to the installations.

Gate recipes

All house numbers inside the installation should be applied inside the gates, not on any of the gate segments.

  • Simple Gate -- a 5-meter 2-way private road segment.
  • Visitor Entrance -- a 5-meter one way private road segment heading into the installation
  • Guest Exit -- (nothing) no private segment is needed. Use the same road type as the rest of the road the gate is on.
  • Member Entrance -- Three 5-meter one-way segments, headed into the installation, in this order: private, street, private. If a point place is used to mark the gate, place it in the middle of the innermost private segment.
  • Member Exit -- one private segment. If a point place is used to mark the gate, place it in the middle of the private segment.

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

Simple Installations

If all the entrances and exits can be used by visitors as well as members, this is a simple installation, and simple gates are used at every entrance and exit. This is true no matter the size of the installation, the number or types of roads used inside, or the number of gates., as long as they are all simple gates. Simple gates cannot be mixed with any other types of gates. The advantage of this approach is that it is simple to understand and simple to maintain. If necessary, the simple gates can be locked, and the roads inside the installation can be of any appropriate type. If absolutely necessary, a divided simple gate can be used.

All other Installations

Blah blah blah

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.  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.  A general rule is to not mark specific locations with a Place unless the public installation website provides that information via directors or maps.  Specific examples of what not to map include organizational names occupying buildings, building numbers, hangar numbers, etc. when they are not publicly available.  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

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

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

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.

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

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.

Template:ReturnToEditingManual

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