(Created page with "===== SE Region "Gated Communities" ===== SE Region adapts the concept of Resident-centric model of private installations. This means we route with the routing favoring the r...") |
|||
| Line 18: | Line 18: | ||
'''How to create the standard gate - otherwise known as the "Diamond Gate"''' | '''How to create the standard gate - otherwise known locally as the "Diamond Gate"''' | ||
The old way of creating the standard gate was to split the road into 2 roads with the "in bound" road having a segment as a Private Road. As time progressed we have moved to a cleaner looking and just as effective - "diamond gate". | The old way of creating the standard gate was to split the road into 2 roads with the "in bound" road having a segment as a Private Road. As time progressed we have moved to a cleaner looking and just as effective - "diamond gate". | ||
[[File:Diamond gate.jpg|thumbnail|left|Diamond Gate]] | [[File:Diamond gate.jpg|thumbnail|left|Diamond Gate]] | ||
Revision as of 05:08, 30 January 2016
SE Region "Gated Communities"
SE Region adapts the concept of Resident-centric model of private installations. This means we route with the routing favoring the resident versus the guest of the private installation. It is the responsibility of the resident to tell their guest which gate / road is best suited for entry - as most likely they will either have to stop at the guard shack to check in or put in some type of code to access the installation anyway.
All access points within the private installation should have the same penalty so that Waze will route to nearest / fastest route to the destination. If the private installation is one (1) access point - it does not need a penalty as Waze will not be able to route THROUGH the private installation.
Due to the complexity of "gates" and private installations - the lock level should be set at 5. If you are editing or creating a gate for a private installation - please request an uplock in either the Forums or the appropriate Slack Channel for the SE Region.
Concept of On, Off, but NEVER through
Simply put- Waze should be able to route TO or FROM a destination or start point within the private installation, but Waze SHOULD NOT be allowed to use the private installation roads as a "cut through" to bypass intersections.
Which kind of gate should be used: STANDARD GATE
A standard gate effectively produces the effect that we want - "On, Off, Never through".
How to create the standard gate - otherwise known locally as the "Diamond Gate"
The old way of creating the standard gate was to split the road into 2 roads with the "in bound" road having a segment as a Private Road. As time progressed we have moved to a cleaner looking and just as effective - "diamond gate".
Step 1. Find the "gate" of the installation. Break the segment over top of the gate / guard shack into 3 smaller segments by either using the cut tool or by connecting roads then deleting the segments. Step 1
Step 2. Break apart the center nodes Step 2
Step 3. Connect the A to B then click the micro-node and drag it out to create the first half of the diamond. Repeat for the other side. Step 3
Step 4. On the inbound into the private installation - change the direction to 1-way into the complex and road type to Private. On the outbound: change to 1-way going towards the public roads, but leave road type as street (no penalty occurs) Step 4
Step 5. Since there were changes in the direction of the roads - double check for Reverse Connectivity (Revcons) and also Turn Restrictions. Do not allow the turn back into the installation nor going back out to the public roads. Also make sure U-turns are disabled. Put in a Uplock request when finished. Step 5