| A | B | C | D | E | F | G | H | I | J | K | |
|---|---|---|---|---|---|---|---|---|---|---|---|
1 | |||||||||||
2 | Welcome to the NC Waze Closures spreadsheet! | ||||||||||
3 | IMPORTANT: Please, NEVER SORT the sheet(s)! Formulas are setup based on the last update times, and sorting BREAKS that! | ||||||||||
4 | |||||||||||
5 | Overall Status (Col A) Key: | ||||||||||
6 | Column A | MEANING & ACTION REQUIRED | |||||||||
7 | - | This Closure has not been worked by any editors yet | |||||||||
8 | Closed | Closure added to WME | |||||||||
9 | Open | Closure is no longer active in WME | |||||||||
10 | Replaced | Newer information for this closure is located further down on the sheet | |||||||||
11 | Update RTC | Existing closure in WME needs to be updated with the information on this line | |||||||||
12 | Tile Update Needed | WME edit needs tile update before closure can be added | |||||||||
13 | Ready for RTC | An editor has located the segment(s) but unable to add closure in WME | |||||||||
14 | Open Needed | An editor has located the segment(s) but unable to remove closure in WME | |||||||||
15 | Verify Opened | Segment(s) needs to be verified that closure has ended in WME | |||||||||
16 | Verify Closure | Segment(s) needs to be verified that closure is still active or scheduled in WME | |||||||||
17 | Extend | Existing closure in WME needs to be updated through the end date/time listed | |||||||||
18 | Review Row ## | Same incident was previously marked as "Do Not Close" - review that row and determine if this updated incident should be closed. | |||||||||
19 | |||||||||||
20 | Understanding Staff, Feed, and NCDOT Accounts: | ||||||||||
21 | WazeFeed: This is an automated feed from NCDOT* directly into Waze. It will show scheduled closures 48 hours before their start time (except for daily/recurring closures, which do not show during their "off" hours), and typically shows within 10 minutes of the start time for immediate closures such as crashes, flooding, washouts, etc. We have build a custom script to populate NCDOT WazeFeed closures directly into this sheet. * Some other municipalities that are Waze For Cities partners will occasionally feed closures into Waze that also show up as WazeFeed closures. Charlotte and Cary are the two most common we see, but Raleigh and a few other cities also use this sometimes. When these municipalities use WazeFeed, these closures do not populate into this sheet automatically. | ||||||||||
22 | waze_roadclosures: This is an account used by Waze staff/contractors to directly add closures into WME. They often work hand in hand with Waze For Cities partner municipalities to add closures from other sources that aren't set up via a feed (e.g. Raleigh events that close downtown streets). They also monitor the DriveNC closures and will add closures that us volunteers haven't gotten to. | ||||||||||
23 | NC_DOT: This is a partner account that is used by NCDOT staff/contractors to log directly into WME and add/remove closures as needed. This is used relatively infrequently, but is a tool for times that major closures are not populating from WazeFeed and us volunteer editors also haven't added the closure. | ||||||||||
24 | |||||||||||
25 | How to Request Edit Access to This Spreadsheet: | ||||||||||
26 | Please send a Discord DM or Waze Message to any NC SM that includes your Google-linked email address (that is capable of editing Google Sheets) | ||||||||||
27 | NC SMs: The_Cre8r, s18slider, ABelter, elijahpruitt | ||||||||||
28 | |||||||||||
29 | Instructions for Using This Spreadsheet: | ||||||||||
30 | Locating & Verifying Closures | Verifying Openings | Closing Segments | ||||||||
31 | |||||||||||
32 | Locating & Verifying Closures - All Editors (regardless of rank or editable area) | ||||||||||
33 | Editors that do not have RTC permissions (L1 & L2), or those that do not have editable area where closures are located, can still assist by locating the segment(s) that need to be closed, and adding the permalink to those segment(s) into the spreadsheet. | ||||||||||
34 | |||||||||||
35 | 1) | Open the Active Closures sheet tab at the bottom of this Google Sheet | |||||||||
36 | 2) | (Optional) Set a Filter View: Go to the Data menu > Filter Views > Locate/Verify. Reminder: Never sort this spreadsheet, only use Filter Views! | |||||||||
37 | 3) | Pick the Closure/Row you wish to work and enter/select Working from the drop-down in Col B. This includes rows that are marked as Verify Closure and WazeFeed. | |||||||||
38 | 4) | Enter your Waze Username in Col C. (For first time, you will need to type your Waze Username. It will be added to drop-down automatically.) | |||||||||
39 | 5) | Open the information link from DriveNC.gov (Col F) AND the PL with approximate location of closure in WME (Col L) If you have the WME NCDOT Reports script installed you may not need to open the DriveNC link | |||||||||
40 | 6) | Using the information from DriveNC, identify which segment(s) in WME should be closed. Tips: The "Local Map" in the lower left of the DriveNC incident page often (but not always) highlights the portion of road that will be closed. Additionally, reading the Detour route (if provided) can provide additional clues. If you're using the NCDOT Reports script in WME, then the same line from DriveNC will show in WME; however you should still use your best judgment about the accuracy of the line -- sometimes NCDOT users will draw the detour route, for example. | |||||||||
41 | 7) | Verify that the start date (Col G), start time (Col H), end date (Col I) and end time (Col J) of the closure match between DriveNC and the spreadsheet (it may have been updated after the data was last pulled into this spreadsheet). If it's changed on DriveNC, update Cols G, H, I, or J accordingly | |||||||||
42 | Verify if the closure will be continuous, or is broken up (e.g. nightly closures). This is typically indicated in DriveNC in the "Road Work Days & Times" section, under the End date/time, but is sometimes only included in the description. If the closure is only for certain hours, indicate this in the Editor Notes (Col R) e.g. "nightly 9:30pm - 6am" | ||||||||||
43 | Verify the Road Name (Col N) and Direction of closure (Col O) | ||||||||||
44 | 8) | If the closure is already added to the segment(s), follow the steps below based on the WME user that added the closure: | |||||||||
45 | WazeFeed: If you are seeing the closure in WME with the WazeFeed username, then this spreadsheet will automatically record the PL within 5 minutes of the closure start time in WME. -- If it's a scheduled closure showing ahead of time, the recommended action is to update the status in Col B to Located and the username in Col C to WazeFeed after you've verified all information is correct. You do not need to add the PL in col E. -- If it's an active closure that is listed in the sheet as Verify Closure, then if the closure in WME matches the information (date, time, correct segments, correct direction, etc) in Step 7, you can update the status in Col B to Closed. You do not need to complete any additional steps below and can move on to the next closure (starting again at step 3 above). | ||||||||||
46 | waze_roadclosures or NC_DOT: Confirm that all information from Step 7 above matches what's been added as a closure in WME. Proceed with Step 10 below. | ||||||||||
47 | Another editor: Confirm that all information from Step 7 above matches what's been added as a closure in WME. Select all segments that are closed, then proceed with Step 10 below. You will also update the username (Col C) to the editor that closed the segment. If you observe a fellow editor frequently closing roads but not recording on this spreadsheet, please reach out to an SM. There may be legitimate reasons such as the ability to access WME but not Google Sheets at work. | ||||||||||
48 | 9) | If the closure is not added to any segment(s), then select all segments in WME that should be closed. | |||||||||
49 | 10) | Copy the Permalink (PL) from WME. Enter this PL for closure in Col E. Or, if you are unable to locate the segment(s) to close, mark Col B as Unable to Locate and move on to a new row (starting at step 3 above). | |||||||||
50 | 11) | If a reason for closure is provided from DriveNC, please enter it (succinctly) in the Reason Col P | |||||||||
51 | 12) | If the closure should be attached to an MTE, enter that MTE Name in Col Q, e.g. "Hurricane Florence - NC" Please try to match the MTE name from WME, however if unsure just enter the simplest form of it. Sometimes we drop the " - NC" part from the MTE in the dropdown, often to match NCDOT's event name. | |||||||||
52 | 13) | Update the Status drop-down in Col B based on the closure type: | |||||||||
53 | Located - for WazeFeed closures, or closures that you selected the segments for in step 9 This will indicate to editors with RTC permissions that they can use the provided PL to quickly close the road (or that WazeFeed already has) | ||||||||||
54 | Closed - for waze_roadclosures, NC_DOT, or other users This indicates that the closure is already in place on the segment and is accurate. | ||||||||||
55 | Verify Closure - for any closures you discover from any account that you believe have an issue based on the verifications in Step 7. Please also add notes into the Editor Notes (Col R) explaining the discrepancy. If the closure is live (vs scheduled), we also encourage you to post to #north_carolina on Discord to see if any editors that could correct it are available. | ||||||||||
56 | |||||||||||
57 | You will not make any changes to Cols A, D, L & M (these will autopopulate). All columns to the right of the black line in Col T are for NC SMs only (but may contain additional helpful info from NCDOT) | ||||||||||
58 | |||||||||||
59 | Verifying Openings - All Editors (regardless of rank or editable area) | ||||||||||
60 | Editors that do not have RTC permissions (L1 & L2), or those that do not have editable area where closures are located, can also assist by verifying that expired or inactive closures in the spreadsheet are also expired/removed in WME. | ||||||||||
61 | |||||||||||
62 | 1) | Open the Active Closures sheet tab at the bottom of this Google Sheet | |||||||||
63 | 2) | (Optional) Set a Filter View: Go to the Data menu > Filter Views > Verify Opened, (or Locate/Verify, or Verification Needed) Reminder: Never sort this spreadsheet, only use Filter Views! | |||||||||
64 | 3) | Pick a Closure/Row that is marked as Verify Open in Col A. | |||||||||
65 | 4) | Open up the PL in Col E in WME | |||||||||
66 | 5) | If the segment(s) are open in WME, i.e. there is no active or future closure on them, change the status in Col B to Open | |||||||||
67 | 6) | If the segment(s) still have closures active or scheduled in WME, but you are unable to remove the closures yourself, change Col B to Open Needed. Note: Sometimes there are multiple DriveNC closures on the same segment - verify the the DriveNC ID in the RTC Description to confirm if it's this closure that needs opened. This indicates to other editors that do have the necessary permissions/EA that the closure(s) need removed. | |||||||||
68 | |||||||||||
69 | Note: There may be some closure rows that are marked as Verify Open, but their source is not from DriveNC (e.g. URs). These are typically reviewed by the editor who placed the closure, or an AM or SM. | ||||||||||
70 | |||||||||||
71 | Closing Segments - R3+ Editors with editable or managed area | ||||||||||
72 | Editors that have RTC permissions (R3+) are encouraged to handle any RTCs that they can within their editable area (subject to road locks/rank). | ||||||||||
73 | |||||||||||
74 | 1) | Open the Active Closures sheet tab at the bottom of this Google Sheet | |||||||||
75 | 2) | (Optional) Set a Filter View: Go to the Data menu > Filter Views > Rows To Work - All (recommended; other views may be used for specific tasks). Reminder: Never sort this spreadsheet, only use Filter Views! | |||||||||
76 | 3) | No matter if you are working an unworked row or a row located by another editor, enter/select Working from the drop-down in Col B. This indicates to other editors in the sheet that it's actively being worked and that they should work another row. | |||||||||
77 | 4) | If working an unworked row, enter your Waze Username in Col C. If working a row located by another editor, leave their Waze Username in place. This is because we can see who entered the RTC in WME and the edit history of the Google Sheet, however if there are questions about the closure placement, we want to retain the history of who located it and give them credit for doing so. | |||||||||
78 | 5) | If working an unworked row, open the location PL from Col L in WME. If working a row located by another editor, open the PL from Col E with segments selected in WME. | |||||||||
79 | 6) | Apply the closure utilizing the information contained in the sheet (if working an unworked row, verify with DriveNC in case of updates). We typically utilize a generic reason and always include the DriveNC incident number in the RTC Description field. Select an applicable MTE if available, otherwise set to None. Tip: The WME NCDOT Reports script can greatly assist with this process by showing the DriveNC closure information in WME, and by generating a pre-created RTC Description that you can quickly copy/paste (or if you have enabled the script setting, can automatically be copied to clipboard when opening the report pop-up in WME) | |||||||||
80 | 7) | For unworked rows, copy the PL from WME and enter in Col E, or if unable to locate the segments to close, change Col B to Unable to Locate. | |||||||||
81 | 8) | Verify the start and end dates/times in the spreadsheet (in case DriveNC updated after the sheet was pulled) - Cols G, H, I, and J. (For Closures lasting more than 1 year, Enter RTC re-opening date in Col K.) | |||||||||
82 | 9) | Verify the Road Name (Col N) and Direction of closure (Col O) | |||||||||
83 | 10) | If a reason for closure is provided from DriveNC, please enter it (succinctly) in the Reason Col P. If you have any notes about the closure, add them to the Editor Notes in Col R (e.g. "nightly 9:30pm to 6am") | |||||||||
84 | 11) | If the closure should be attached to an MTE, enter that MTE Name in Col Q, e.g. "Hurricane Florence - NC" (Please try to match the MTE name from WME, however if unsure just enter the simplest form of it) | |||||||||
85 | 12) | Change Closure/Row status to Closed in Col B. The row should turn green; if it turns red, there is an error in one or more of the fields that will need reviewed. | |||||||||
86 | |||||||||||
87 | You will not make any changes to Cols A, D, L & M (these will autopopulate). All columns to the right of the black line in Col T are for NC SMs only. | ||||||||||
88 | |||||||||||
89 | |||||||||||
90 | |||||||||||