|
|
| (29 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| ({{font color|red|'''DRAFTː '''}} NOT IN USE AT THIS TIME)
| |
|
| |
|
| | {{Special:Prefixindex/{{FULLPAGENAME}}/}} |
|
| |
|
| Below is information on the Waze V.E.O.C. The Virtual Emergency Operations Center or VEOC was setup to help areas experiencing a very high volume of closures do to an event. For those in the events path. If you can help out safely then great. Your first priority is taking care of you and yours. We will find other editors not affected by the event to help with closures. Your safety is much more important that getting a road closed in Waze.
| |
| == Dedicated Slack Team Waze USA VEOC ==
| |
|
| |
|
| * The team was created to allow greater flexibility of feeds, channels, etc and be independent of any region
| | ({{font color|red|'''DRAFTː '''}} NOT IN USE AT THIS TIME) |
| * waze-usa-emergencies.slack.com is the web address of the team.
| |
| * If you need an invite please use the following form http://bit.ly/Waze_USA_VEOC
| |
| | |
| == USA Emergency Procedure Resources==
| |
| | |
| * Depending on the nature of the event you may want to extend the closure end date/time to past the reported end time for the event. For example, with major flooding how will the road condition be known until the water recedes? For snow/ice is 24/48 hours enough time for the plows and snow/ice treatment to work so roads can be opened? This is a suggestion as it is difficult for the reporting agency to know how long a road will need to be closed when the event is still occurring. It is easier to remove a closure once than to keep extending it several times a day/week. In past events we worked over 1,100 different road closures. This is not to encourage a set and forget it approach. It will be up to the locals to review the sheet and adjust/remove the closers as needed.
| |
| | |
| * Do you want to allow traffic to auto open a closure or do you want Waze to ignore traffic when inputting a closure?
| |
| | |
| * Be mindful of your editor's availability when setting end time on closures. Do you really want your closures ending at 8am when most people are still dealing with morning routines? Having them end at 5pm is not any better for the same reason.
| |
| | |
| * When closing a segment it is helpful to list the between roads in case more closures are needed on the same road name in a different location(s). Saying Main St is closed it not much help if you have three different parts of Main St to close in the same city/county. Saying Main St is closed between 1st St and 5th St as an example lets other verify if anything needs to be done with the other reported closures.
| |
| | |
| * We need to close all the segments that are reported by the source agency not just the segment we think needs closing. There might be barricades in place for all the reported segments even though a small portion of the road might be affected. The source agency needs to trust that we are going to close whatever segments they say are closed.
| |
| | |
| *For road segments flagged as local traffic only closures the suggestion is to keep the segment closed but can be overridden by CM/RC or SM as needed.
| |
| *For long term closures due to damage/washout please place a Map Comment over the area with any reference links showing the damage. For the title it is suggested to use the name of the storm - related closure. Example Harvey related closure.
| |
| | |
| =====Waze Catastrophic Event Closure Tracking=====
| |
| | |
| Below is the google form and google sheet currently being used to track closures in weather related events. The form is for use by anyone and feeds the sheet. The sheet is used by those that can do the closures. Be sure these match the ones that are pinned to the #usa-emergencies channel on the usaregions.slack.com team
| |
| | |
| * [https://docs.google.com/forms/d/e/1FAIpQLSduFs5gPUtGZo0fJX5wsJzZY7cjvdMksXgJPXAOVc0Z_nSRbQ/viewform Waze USA Irma Weather Closures Entry Form]
| |
| * [https://docs.google.com/forms/d/e/1FAIpQLSd2jmYSQ8sUV5u6JH0PBI7y_swRn9s5VV6bUyQvKdKkh7FH8A/viewform Waze USA Harvey Weather Closures Entry Form]
| |
| | |
| Below is the google sheet currently being used to track closures in weather related events.
| |
| | |
| * [https://docs.google.com/spreadsheets/d/1KSg4bMTHMRjaQDDoF7ZfJ4PmDuZPLMWqlH7K-dSN9jc/edit?usp=sharing Waze USA Irma Weather Closures Tracking Sheet]
| |
| * [https://docs.google.com/spreadsheets/d/12cyUhPsNTv7IMZY5RUKKasTaCViB6BTi1BeZf27A1n4/edit#gid=712145152 Waze USA Harvey Weather Closures Tracking Sheet]
| |
| | |
| Below is a Form Filler Script created by crazycaveman. It saves a lot of time for the people adding them to the sheet. You will need tapermonkey to install.
| |
| | |
| * [https://greasyfork.org/scripts/23367-wme-form-filler/code/WME%20Form%20Filler.user.js Form Filler Script] V 1.3.6 Last updated 09/06/2017 Please make sure you are using this version or newer for Irma.
| |
| * [https://greasyfork.org/en/scripts/23367-wme-form-filler Form Filler Script] V 1.3.5 Last updated 08/16/2017 Please make sure you are using this version for Harvey.
| |
| | |
| =====WME tips, short cuts, etc=====
| |
| | |
| * To select all segments between two other segments, first select a segment, then use {{key press|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. {{font color|red|'''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.
| |
| | |
| =====Google sheet tips, short cuts, etc=====
| |
| | |
| * To change the view and only see a certain condition Click on ('''Data''') then ('''Filter views)''' then choose the one you want from the choices on the far right. Using the <code>'''Filter'''</code> option instead of the <code>'''Filter Views'''</code> will affect everyone's view.
| |
|
| |
| '''DATA FILTER VIEW FOR SPECIFIC STATE (This will not affect the view of others)'''
| |
| * You will need to do the following steps
| |
| # Data->Filter Views -> Closure By State (View)
| |
| # click the gear icon in Data Filter View
| |
| # click Duplicate. This should make a copy of the Data View
| |
| # Change the name of from "Closure By State) to the state(s) you want to see (ie NC Closures) as name<>. This will be in the upper left hand corner above the column letters.
| |
| # Go to cell I3 and click the filter icon.
| |
| # Select the state you want to filter. Deselect others as necessary.
| |
| # This will now create the data filter view for that particular state.
| |
| | |
| '''COLUMN C'''
| |
| * This is the Permalink to the closure with the layers stripped out. ('''''Please do not edit anything in this column''''')
| |
| | |
| '''UPDATING TIME CHECKED''' -
| |
| * Updating the time checked in Column H "LAST CHECKED TIME" is as simple as changing the name (Has to be a name change) in Column G "LAST CHECKED BY" or typing something in Column E (ie I usually just type the number 1). It should automatically update to the current time.
| |
| | |
| '''SORTING'''
| |
| * Do so sparingly and probably with a warning to other editors.
| |
| | |
| {{font color|red|'''ROW DELETION'''}}
| |
| * If for some reason an editor deletes out a row. Please click on the words ROW DELETION to re-execute the DUP SCRIPT. It is located at the top of Column P
| |
| | |
| '''COLUMN F "Type"'''
| |
| {| class="wikitable"
| |
| |-
| |
| ! Type !! Usage
| |
| |-
| |
| | zOPEN || Open in Waze
| |
| |-
| |
| | CLOSED || Closed in Waze
| |
| |-
| |
| | NEEDS OPENED || Needs to be validated and open or extended as needed
| |
| |-
| |
| | REPORTED || Needs to be closed in Waze by editor with access to location
| |
| |-
| |
| | UNLISTED || No longer found on source location. Needs closure removed and marked as open
| |
| |-
| |
| | DUPLICATE || Segment ID(s) found in other closure Permalink(s)
| |
| |-
| |
| | EXTEND/SHORTEN || Closure still in effect just needs date/time adjusted to match new information.
| |
| |-
| |
| | NEEDS OPEN NOT LISTED || Closure in WME but not listed on closure sheet.
| |
| |}
| |
| | |
| * If a line has expired and is reopened in real life please change to zOPEN in column F
| |
| | |
| '''COLUMNS A-D'''
| |
| * Are not editable as they are derived data. If the closure date/time needs extended please edit the date/time in Column T
| |
| | |
| =====Google sheet changes since Harvey=====
| |
| * Sort order changed, now---- State, Current waze Status, County/Parish/Municipality, then Closure Ending Date/time.
| |
| =====Slack Suggestions=====
| |
| * Slack users that are helping with the closures should setup a keyword of closure for being pinged when attention is needed. Example :closure:
| |
| | |
| =====WME Suggestions=====
| |
| * 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.<br />
| |
|
| |
| * For extremely long sections of segments please provide the beginning and ending segments. The editor doing the closure will fill in the between segments.
| |
| | |
| *Zoom Levels... When creating a PL for a closure please be sure you are zoomed in to at least Level 4 [100 M | 500 Ft]
| |
| | |
| =====US County Overlays=====
| |
| | |
| * {{font color|red|'''Important'''}} below you will find a county overlay script that will show the boundaries and place the county name in the upper left corner with the city/state. This is very important to use so that you can verify you are closing the correct road segment in the correct county. Some road names are used in more than one county.
| |
| | |
| * The following US County Overlays comes from Rick Zabel.
| |
| * The link to the forum post can be found here. https://www.waze.com/forum/viewtopic.php?f=819&t=153709
| |
| * If the script does not work you may need to try the following. [https://www.waze.com/forum/viewtopic.php?f=819&t=153709&start=30#p1569139 US County Overlays Fix]
| |
| | |
| | |
| <div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
| |
| | |
| * [https://greasyfork.org/en/scripts/11423-wme-counties-alabama-census-2014/ Alabama]
| |
| * [https://greasyfork.org/en/scripts/11512-wme-counties-alaska-5m-census-2014/ Alaska]
| |
| * [https://greasyfork.org/en/scripts/11425-wme-counties-arizona-census-2014/ Arizona]
| |
| * [https://greasyfork.org/en/scripts/11426-wme-counties-arkansas-census-2014/ Arkansas]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11428-wme-counties-california-census-2014/ California]
| |
| * [https://greasyfork.org/en/scripts/11429-wme-counties-colorado-census-2014/ Colorado]
| |
| * [https://greasyfork.org/en/scripts/11430-wme-counties-connecticut-census-2014/ Connecticut]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11431-wme-counties-delaware-census-2014/ Delaware]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11421-wme-florida-counties-overlay-census-2014/ Florida]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11432-wme-counties-georgia-census-2014/ Georgia]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11445-wme-counties-hawaii-census-2014/ Hawaii]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11441-wme-counties-idaho-census-2014/ Idaho]
| |
| * [https://greasyfork.org/en/scripts/8297-wme-counties-illinois-census-2014/ Illinois]
| |
| * [https://greasyfork.org/en/scripts/11442-wme-counties-indiana-census-2014/ Indiana]
| |
| * [https://greasyfork.org/en/scripts/11446-wme-counties-iowa-census-2014/ Iowa]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11447-wme-counties-kansas-census-2014/ Kansas]
| |
| * [https://greasyfork.org/en/scripts/11448-wme-counties-kentucky-census-2014/ Kentucky]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11449-wme-counties-louisiana-census-2014/ Louisiana]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11450-wme-counties-maine-census-2014/ Maine]
| |
| * [https://greasyfork.org/en/scripts/11451-wme-counties-maryland-census-2014/ Maryland]
| |
| * [https://greasyfork.org/en/scripts/11452-wme-counties-massachusetts-census-2014/ Massachusetts]
| |
| * [https://greasyfork.org/en/scripts/11453-wme-counties-michigan-census-2014/ Michigan]
| |
| * [https://greasyfork.org/en/scripts/11454-wme-counties-minnesota-census-2014/ Minnesota]
| |
| * [https://greasyfork.org/en/scripts/11455-wme-counties-mississippi-census-2014/ Mississippi]
| |
| * [https://greasyfork.org/en/scripts/11456-wme-counties-missouri-census-2014/ Missouri]
| |
| * [https://greasyfork.org/en/scripts/11457-wme-counties-montana-census-2014/ Montana]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11458-wme-counties-nebraska-census-2014/ Nebraska]
| |
| * [https://greasyfork.org/en/scripts/11459-wme-counties-nevada-census-2014/ Nevada]
| |
| * [https://greasyfork.org/en/scripts/11460-wme-counties-new-hampshire-census-2014/ New Hampshire]
| |
| * [https://greasyfork.org/en/scripts/11461-wme-counties-new-jersey-census-2014/ New Jersey]
| |
| * [https://greasyfork.org/en/scripts/11462-wme-counties-new-mexico-census-2014/ New Mexico]
| |
| * [https://greasyfork.org/en/scripts/11463-wme-counties-new-york-census-2014/ New York]
| |
| * [https://greasyfork.org/en/scripts/11464-wme-counties-north-carolina-census-2014/ North Carolina]
| |
| * [https://greasyfork.org/en/scripts/11465-wme-counties-north-dakota-census-2014/ North Dakota ]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11240-wme-counties-ohio-census-2014/ Ohio]
| |
| * [https://greasyfork.org/en/scripts/11466-wme-counties-oklahoma-census-2014/ Oklahoma]
| |
| * [https://greasyfork.org/en/scripts/11469-wme-counties-oregon-census-2014/ Oregon]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11470-wme-counties-pennsylvania-census-2014/ Pennsylvania]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11471-wme-counties-rhode-island-census-2014/ Rhode Island]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11440-wme-counties-south-carolina-census-2014/ South Carolina]
| |
| * [https://greasyfork.org/en/scripts/11472-wme-counties-south-dakota-census-2014/ South Dakota]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11474-wme-counties-tennessee-census-2014/ Tennessee]
| |
| * [https://greasyfork.org/en/scripts/11513-wme-counties-texas-5m-census-2014/ Texas]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11475-wme-counties-utah-census-2014/ Utah]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11476-wme-counties-vermont-census-2014/ Vermont]
| |
| * [https://greasyfork.org/en/scripts/11497-wme-counties-west-virginia-census-2014/ Virginia]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11496-wme-counties-washington-census-2014/ Washington]
| |
| * [https://greasyfork.org/en/scripts/11602-wme-counties-west-virginia-census-2014/ West Virginia]
| |
| * [https://greasyfork.org/en/scripts/11498-wme-counties-wisconsin-census-2014/ Wisconsin]
| |
| * [https://greasyfork.org/en/scripts/11499-wme-counties-wyoming-census-2014/ Wyoming]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11514-wme-counties-district-of-columbia-census-2014/ District of Columbia]
| |
| | |
| | |
| * [https://greasyfork.org/en/scripts/11473-wme-counties-puerto-rico-census-2014/ Puerto Rico]
| |
| * [https://greasyfork.org/en/scripts/11810-wme-counties-puerto-rico-districts-census-2014/ Puerto Rico's districts]
| |
| | |
| </div>
| |
