User:DCLemur/DRAFTVEOC Overview** View history

Latest revision as of 16:54, 6 June 2020

The Virtual Emergency Operations Center (VEOC) is Waze USA's centralized project for managing responses to catastrophic weather events. (These events include hurricanes, mud and landslides, floods, winter storms, earthquakes, and large fires.) The VEOC complements and enhances a state or region's ability to manage its map needs; editors from all over the USA are able to come together to the aid of the affected community members. Additionally, local, state and national emergency officials can coordinate and communicate directly and in real time with the Waze community. The result is a continually updated map with the most accurate road condition information available, a valuable resource for first responders and wazers alike.

WELCOME

Welcome! All members of the Waze editing community are encouraged to join the effort to help those affected by these crisis events. There are opportunities for all editors, regardless of rank or experience. We appreciate your contribution to this project, whether it's locating shelters or closed roads or making a few edits to the map. Each and every one moves us one step forward towards reaching our goal: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx!

MISSION & BENEFITS

VEOC's primary mission is to coordinate national efforts to provide an effective response to a major crisis event when the local editing community requests assistance whether overwhelmed or incapacitated (for safety reasons or otherwise) and are unable to respond appropriately.

Efforts are focused on ensuring that the map reflects the current conditions before, during, and after the crisis event. Wazers receive accurate routing when evacuating (and when returning home afterwards). Activated emergency shelters are highlighted on the map to assist those who choose to remain in the area. Understanding the current status of roads allows first responders to continue to provide services to the community during and after the event.

Participation in a VEOC operation allows visiting editors to learn about new communities and regions from local and experienced editors. Relationships are formed and strengthened throughout the community: locally, regionally, and nationally. Each gathering of Waze editors builds a stronger community. The post-op evaluation, which includes analysis of the MTE reports and data, provides leadership the opportunity to critically review the process and procedures and make improvements to the system.

COMMUNICATION

The VEOC has a dedicated server in Discord,<active link name Waze USA VEOC>, for communication.

General Channels

The following channels are available for specific discussions in the main server which are not VEOC event specific:

# front door: Links to event's sheets and forms.
# lobby: Announcements and status updates including the current WAZECON level.
# veoc-sheet-forms: Discussion of spreadsheet and forms issues.
# suggestions: Submit proposals on how to improve the VEOC process. ALL ideas are welcome.
# invite: Tracks editors joining the server and announces their arrival.
# previous-sheet-links: Links to past events.
# armchair storm chat: Informal talk related to the storm, forecast models, how "you" think it will track, its impact, etc. Please Do Not post anything related to closures or places - post in the appropriate CURRENT OPS channel.
# gho-castaways: Channel available for editors without Discord access. The CommunityGHObot syncs the posts in Google Hangouts (GHO) <link to actual HO> and posts them in this channel.

Event-Specific Channels

Each VEOC event uses the CURRENT OPS category for communications. Channel name is appended with the date, YYYY_MM and the event name. Channels can include:

# chat_yyyy_mm_event_name:

# closures_yyyy_mm_event_name: Road closures

# open_yyyy_mm_event_name: Road openings

# feeds_yyyy_mm_event_name: Feeds from localities

# places_yyyy_mm_event_name:

RESOURCES

Forms & Sheets

These forms are pinned in the Discord VEOC server in the #front_door channel.

The xxxxxxxxxxxxxxxxx sheet (real life example) is used to track shelter activity. This (Waze staff) sheet is named as follows: "[VEOC Event Name] , [country] , [calendar year] " - pins ". <link to VEOC shelter tracking sheet Instructions>
The VEOC Road Closure Form is activated by pressing the button in WME. The data entered into this form is fed to the VEOC Road Closures Sheet for action. <link to VEOC Road Closure Form Instructions>
The VEOC Road Closures Tracking Sheet (sample) is the google sheet used to track closure and re-opening activity. Used by editors who have the ability to edit segments in the affected areas to process closures submitted by others, update or remove closures as needed, and submit closures if not using the form. <link to VEOC Closures Tracking Sheet Instructions> [spedracr expanded]

Browser Tools

A script manager is required if using scripts. We recommend the installation of TamperMonkey. (Some scripts do not work with the current version of GreaseMonkey.)

Toolbox Extension for Chrome. WME is optimized for Chrome.

Toolbox For Firefox

Scripts for WME

Form Filler Script , Activated by the push of a button in WME. Select the affected road. Pulls data from WME and queries the editor for the balance of required information. Transfers the data into the VEOC Road Closures Tracking sheet. Improves productivity and reduces opportunities for errors.

WME Government Boundaries Superimposes county boundaries on the map and places the county name, with the city and state, in the upper left corner of WME. Use to verify that you are locating and/or closing the correct road segment. (Some road names are used in more than one county within a state.)

WME Me! Assists in identifying an accurate longitude and latitude. (Zoom in and place your WME Me! icon on the center of the place. Copy the longitude/latitude information from WME.)

CRISIS RESPONSE PROCESS

Prior to VEOC activation, each serious weather event is tracked and a Waze readiness level or state of alert, WAZECON, is posted in the lobby. (Changes in WAZECON levels are also posted there.) A message similar to this can be posted as well: "Currently, local editors have the situation under control and are handling it within their local channel in their regional server."

File:Waze Emergency Response Activation Levels Spedracr.png|1800px|frame|alt=A chart with explanations of the WAZECON Levels 1 through 5.

Step 1 - Activate the VEOC. When possible, the editor community leaders activate the VEOC for a region or area of their country at least three (3) days in advance of the impact of a crisis event requiring support. They alert the waze crisis team via email.

Step 2 - Establish Crisis Event Infrastructure. Leaders create an MTE (Major Traffic Event) under which all closures will be created. The USA VEOC Admin team creates the necessary Discord channels including those required to monitor media feeds. They also post in Discord the updated closure form, closure sheet, and form filler script. (Leadership can link to the VEOC Setup Procedures doc for detailed process information.)

Step 3 - Notify Community & Request Editing Freeze. Leaders communicate that the VEOC is activated via Discord, GHO, forums, etc. All editing is stopped or suspended in the affected area so that closures can be placed as needed. (Any edit, which forces a change to the segment id, will need to be processed via a tile update (TU) before a closure can be added to that segment.)

Step 4 - Add Emergency Shelters to the Map.

The Waze crisis team (staff) emails leaders a google sheet with all known available shelters. (Editors can also add shelters to list from confirmed official sources.)
Editors locate and add them to the map. (All editors, regardless of rank or experience, are encouraged to help locate shelters, verify/update information and determine their status.)
Once mapped, the Waze crisis team will add a special xxxxxxxxx to each shelter.
The xxxxx will appear in the client when a wazer searches for “Help”.

Step 5 - Input Road Closures.

Step 6 - Monitor Feeds & Other Media Outlets.

Step 7 - Reopen Roads and Close Shelters as Reported.

Step 8 - Deactivate VEOC. Once the number of active closures has dropped low enough so that the local editors can take over managing them, the VEOC is closed. A post mortem is conducted by leadership to discuss what improvements can be made to the process in advance of the next event. Closure statistics and data are available for evaluation (via the MTE event designation). Ideas which have been posted in the "# suggestions" channel are included in this review.

How Can I Help?

All editors whether local or from the community at large, regardless of rank or experience, are encouraged to join the effort and help those in the affected area(s). The desire to help is all that is required. The focus of VEOC efforts center on quickly locating and adding emergency shelters. We also focus on identifying, locating, and adding road closures to the map. All editors can assist in determining the locations of emergency shelters as well as those segments which need to be closed. Others are who have editing or closure rights in the crisis area can add to or modify the map.

Many hands are needed and appreciated. The efforts are ongoing as long as the VEOC is active. The notification rate for road closures spikes at times during and after the event. Each post needs to be reviewed and addressed, so staying current or up-to-date becomes more challenging. Over time, once the weather related event has subsided, the activities start to shift towards removing closures and opening the roads up to traffic. Once the situation becomes manageable by local editors, the VEOC event is closed and deactivated.

Locate Emergency Shelters (All Editors)

Waze staff provides and maintains the shelter tracking sheet, named " [Staff Event Name] - pins - YYYY (year) ". (If shelters are found locally, we add them directly to the sheet.)" Editors determine the shelter's location on the map and record the longitude and latitude on the sheet. Editors with editing ability (R3+) add the shelter to the map with its information. Detailed instructions are available at <add hyperlink> Shelter Tracking Sheet Instructions.

Add Emergency Shelters to WME (Editors with Local Editing Rights)

Shelters need to be added as soon as possible following the declaration of a VEOC event. Wazers will be looking for assistance as to what their relocation options are. Corrections needed to the shelter information are made on the sheet to match the place point. Detailed instructions are available on the Shelter Tracking Sheet Instructions page, beginning at <add hyperlink>.

Locate Road Closures (All Editors)

VEOC editors create, populate, and maintain the Road Closures Sheet primarily through data supplied by the Closure Form." "Detailed instructions are available at <add hyperlink> Closure Form Instructions (scriptless) for those who are editing without scripts and at <add hyperlink> Closure Form Instructions w/ Form Filler Script when using Form Filler.

Add/Update/Remove Road Closures in WME (Editors with Closure Rights)

IMPORTANT GUIDELINES

Remember: All commercial maps, including Google Maps, are prohibited as Waze sources. Privately owned data can not be used for Waze mapping. This is critical: Data found to have come from a non-approved source can cause Waze to lose all the contributed data in a large area.

TIPS, TRICKS, & SHORTCUTS

The instructions provided below highlights some information which can be particularly helpful when working VEOC.

Discord

Discord users that are helping with the closures should setup a keyword of closure for being pinged when attention is needed. To add a keyword, use !keyword add keywordhere. You can use multiple words, but note that you will only be messaged if the entire phrase you use is a match. To add multiple separate keywords, you need to use the command multiple times in individual messages. For more information on Discord and keywords see Discord Wazeopedia Keyword Subscriptions

WME

To select all segments between two other segments, first select a segment, then use alt+click to select a second segment. The editor will add to the selection group the segments in-between the first and second segments, based mostly on the street name, but also on simple straight lines. Important Be sure to check and make sure the proper segments are selected before making closures or submitting PL for processing of closures.
Zoom level..."Please make sure that you are zoomed out and centered to a level that shows the segments you are asking for assistance with. As a general guideline, Fwy and MH can't be zoomed out any farther than zoom 2 (2000 ft), mH and PS can't be zoomed out any farther than zoom 3 (1000 ft) and Streets and below can't be zoomed out any farther than zoom 4 (500 ft). If you are unsure, Please test your PL pasting it into a new browser tab/window to make sure proper segments are selected.
For long term road closures please do a MC explaining why. Also put in the subject line "RCD road washout" or "RCD bridge damage" after RCD (Road Closure Damage) then the filer option on UR-MP-Tracking can be used to find them later.
Do not make any edits to a segment that will force a change of the segment id. If the segment id changes you will need to wait for a tile update before you can add a closure to the segment.
For extremely long sections of segments please provide the beginning and ending segments. The editor doing the closure will fill in the between segments.
Suggest using MC (Map Comments) for bridges or interchanges that have local names like Spaghetti Junction in Atlanta GA or Theo Barrs Bridge in Pensacola, FL using LRM (Local Reference Marker) will allow a filter to be done using UR-MP script to search the MC for that state. This works even if you do not have edit access in that state as of Jan 2018. Subject to change with UR-MP script updates

Closure Form

Closure Sheet

Please submit ideas for inclusion by sending an <add hyperlink>email to VEOC.wiki.tips.

NON-VEOC ISSUES

At this time, there is no formal process to address those map issues which were detected during a VEOC event but were beyond the scope of the VEOC mission. Discussions are underway to determine how this can best be addressed. (Forms and/or spreadsheets may be developed to help local editors located and address these important map issues.)

REFERENCE LINKS

Adding Places in WME Places#Point place

Real Time Closures in WME Real time closures#Real time closures in WME

Instructions & Requirements for Browsers when using Scripts Scripts#Browser requirements

ADMIN TEAM

This dedicated team was created as a national team; it is independent of any specific region. This team composition allows greater flexibility in the creation and maintenance of feeds, channels, etc which are needed for effective VEOC management. The team coordinates the creation of the communications infrastructure for an event and assists local leadership where needed.

Closure Form & Sheet: crazycaveman (SAT ARC), Owner; Maintenance assisted by dbsooner (SCR/SER), spedracr (SER)
Form Filler Script: crazycaveman (SAT ARC); Script maintenance for closure sheet
Other editors with process knowledge:

Driving79 (SER RC) karlcr9911 (SCR RC) Jakflash (SER LC) spankdog (SER LC)

itzwolf (SER ARC) grsmhiker (SAT MSM) jwe252 (SAT CM) LostRiver2008 (SER)

LINKED PAGE: How to Process the Shelter Tracking Sheet

LINKED PAGE: Closure Form Instructions (Scriptless)

* indicates the REQUIRED FIELDS (minimum needed).

Step 1 - Open the <make hyperlink> VEOC Closure Form in one window.

Step 2 - Enter your Waze username in the field, * SUBMITTED BY .

Step 3 - Open the <make hyperlink> Waze Map Editor (WME) in a new window and locate the segment(s) needing action.

Step 4 - Determine the * TYPE of action needed. Using the dropdown list, select one and add:

REPORTED - If you are unable to close it, OR
CLOSED - If it is already closed OR you can and will close it, OR
NEEDS OPEN NOT LISTED - If it is currently closed OR it is not listed on the sheet OR it needs to be re-opened and you are unable to open it.

Step 5 - Create a permalink for the selected segments and paste into the Waze Permalink field.

Step 6 - Set the Closure Direction (direction of traffic flow to be closed) in the report by selecting either "One-Way" or "Two-Way" from the dropdown list.

Step 7 - Note the Reason for the road closure ("Flooding", "Downed trees", "Downed power lines", etc).

Step 8 - Set the * Closure Ending Date/Time to either the date/time provided by the report source OR the expiration date/time set for the event by VEOC / community leadership.

Step 9 - Record the CLOSED STREET NAME.

Step 10 - Identify the cross street at one end of the closed segment(s). Type the name in the CLOSURE FROM (Street Name) field. Identify and record the cross street on the other end in the CLOSURE TO (Street Name) field.

Step 11 - Set the * STATE.

Step 10 - Set the COUNTY/COMMUNITY/PARISH.

Step 11 - Record the SOURCE (which is usually the reporting agency). Include a link to the posted closure if one is available.

Step 12 - You may enter information into the NOTES field.

Step 13 - Press the blue SUBMIT button.

LINKED PAGE: Closure Form Instructions w/Form Filler Script

* indicates the REQUIRED FIELDS (minimum needed).

Step 1 - Open the <make hyperlink> Waze Map Editor (WME) in a new window and locate the segment(s) needing action.

Step 2 - Ensure USA VEOC closures is selected in the segment information pane and click Go To Form.

Step 3 - The Closure Form will appear in a new window with some of the form pre-filled, including

* SUBMITTED BY (should be your Waze username),

TYPE (based on if a closure already exists on segments or not),

Waze Permalink (should be a PL to the selected segments), and,

* CLOSED STREET Name

Step 4 Review TYPE selected. If needed, change it to one of the following:

REPORTED - If you are unable to close it, OR
CLOSED - If it is already closed OR you can and will close it, OR
NEEDS OPEN NOT LISTED - If it is currently closed OR it is not listed on the sheet OR it needs to be re-opened and you are unable to open it.

Step 5 - Set the Closure Direction (direction of traffic flow to be closed) in the report by selecting either "One-Way" or "Two-Way" from the dropdown list.

Step 6 - Note the Reason for the road closure ("Flooding", "Downed trees", "Downed power lines", etc).

Step 7 - Set the * Closure Ending Date/Time to either the date/time provided by the report source OR the expiration date/time set for the event by VEOC / community leadership.

Step 8 - Identify the cross street at one end of the closed segment(s). Type the name in the CLOSURE FROM (Street Name) field. Identify and record the cross street on the other end in the CLOSURE TO (Street Name) field.

Step 9 - Set the * STATE.