User:Michelle-s/Access-Control areas

Proposal: Access-Control Area Polygons

Waze is looking to improve routing to destinations that lie within Access-controlled areas. Waze is also seeking to prevent routing through an Access-controlled area, when a destination is not inside that area. Waze users expect to get the fastest route to their destination, but they don’t want to be routed through a prohibited path. However, if their destination is within an Access-controlled area, it would be beneficial if the user could choose between the visitor gate or any gate / entrance along their route. Waze users need a simple-to-use interface to optimize their user-experience. This proposal is for Waze to create simple Access-Control area polygons. If the user’s destination lies within area that polygon area, then the user can be given the choice whether to route to the visitor gate or to be routed as a “trusted user” who can drive through any of the facility’s gates. Simplifying the application and definition of Access-Controlled areas can help solve the perpetual question whether an area should be set for employee/resident routing inside of a controlled area or for visitor routing. The process of giving a user the choice to go either through a visitor gate or through any gate is meant to simplify the access-control routing process and to remove the need to define “levels” of users. For example, the National Institute of Health in Maryland has Employees, Patients, Patient Visitors, General Visitors and Delivery drivers. An Access-Control area simplifies the routing for them to choose either one specific visitor gate or to drive through any of them.

1) This proposal is applicable for Access-Controlled areas, such as:

• Neighborhoods
• Neighborhoods
• Apartment complexes
• Condominium complexes
• Private Installations
• Resorts
• Employee access areas
• Gated corporate campuses
<
• Government Installations
• Military Installations

There are two types of simple Access-Controlled Areas: - One entrance - Multiple entrances ● Facility were all entrances are available for all residents/employees/visitors. ● Facility where the Visitor-Access office is co-located with the Main entrance. All other access gates require pre-approved access (Badge, decal, etc.) ● Facility where the Visitor-access office is located at a different location than at the main entrance. All other access gates require pre-approved access (Badge, decal, etc.)

Nested Access-controlled areas. Occasionally there is/are a second access-controlled area(s) inside of or next to the first Access-controlled area. Think of a higher security area inside of a larger access-control area. These installations have internally nested/adjacent Access-controlled areas which have their own distinct pre-approved access. In general, a nested area has a main access-control point with secondary gated entrances/exits. The Access-control office for a Nested Access-controlled area may be located outside of the area or at one of the gates of the nested controlled-access area

PROPOSAL: Add Access-control polygons to WME, in order to replace the current practice of using Private road segments to add routing penalties. The proposal is to create a controlled-access area polygon that integrates an area with routing functionality. Any house number, residential place point, point place, area place, street intersection, or latitude/longitude within the controlled-access area polygon will invoke the new procedure. Each Access-control Polygon will need to have a designated entry point for the area’s Visitor Center/Gate; with the understanding that an installation’s Visitor Access gate is not always co-located at the Main entrance gate. Remember that we cannot assume that an installation’s Main Gate and a Visitor Gate are always co-located. Therefore we have to be able to have assignable pins for the main entrance as well as a visitor entrance. This way an editor can set either configuration for each installation. Assume for the purpose of this routing process that Access-Control occurs 24/7, and is not yet based on time of day. For routing purposes, the discussion will need to be conducted about a standardization of the internal use of PRs (assorted private installations), PLRs (assorted private installations), LS and PS (Military Installations) within Private or other Access-controlled Areas. The addition of the Access-control Area polygon would remove the need for a PR segment for routing and access-controlled ingress/egress. Gates that have Time-based restrictions can retain that routing data within the road segments.

PROCESS: A User searches for their destination, using either the address or place name. If the destination’s stop point lies inside of a Controlled-access area, as determined by its area polygon, then the user receives a series of two prompts: 1. Pop-up #1 Destination is within a controlled-access Area. Is this where you want to go? -10 second timeout Default = Allow Else, Opt-out 2. Pop-up #2 (if allow or timeout occurs) Do you need to go to the Visitor Center/Gate? -10 second timeout Default = No (The User is routed directly to their destination through the closest entrance gate that is open.) Else, Opt-In (The User is routed to the Visitor Center/Gate)

Follow-on destination criteria: If in the user’s Waze App, their listed Home, Work or a Favorite place is situated inside the Access-control Polygon, then they’ll receive no pop-ups. This process assumes that the driver is a Trusted-user that has pre-approved access to the facility. This way, Waze avoids bothering users with unnecessary pop-ups each route.

Routing Inside of the Access-Control polygon: - Once a driver is located inside a Polygon, Waze can route them through the rest of the polygon to new destinations that are also inside the polygon or to route to any open exit gate with no prompts.

Outside of Polygon - Waze never gives a route through an Installation, if the destination does not lie inside of that polygon’s area.

Current routing practices: - This Current Waze guidance for routing Road Types for Private and Military Installations

Further discussion: Most Access-Controlled areas have gates that are open 24 hours; however, some visitor centers may have variable hours. Some will be open only during daytime hours. Others will be open only during night time hours. 1. Do we need the ability in the future to set Time-based hours for the access-control polygons? (Example: If the installation is open during the day, and is only access-controlled at night?) 2. Do we need the ability to set hours as Sunrise and Sunset, in order to support seasonal variations for access-control. (Example, the Volcano National Park on the Big Island of Hawaii is open 24/7; however, it is Access-controlled during daylight hours and is freely open after sunset.) 3. For now, treat installations where the main gate may differ from day to night time as exceptions. Installations may have different gates for late night deliveries, night-time controlled-access, or other third-shift configuration.