User:Markr4468 View history

VisualWikitext
No edit summary
mNo edit summary
Line 1: Line 1:
== Community ==
<nowiki><big>TEST PAGE</big></nowiki>


[https://www.waze.com/forum/index.php The Waze Forum] is a great place to find answers to previously asked questions and also a place to ask new ones. Below are links to the forums specific to West Virginia.
<nowiki>''</nowiki><nowiki><small>Sections of Main Wiki Page</small></nowiki><nowiki>''</nowiki>


* [https://www.waze.com/forum/viewforum.php?f=582 West Virginia Section of the Waze Forum]
* [https://www.waze.com/forum/viewforum.php?f=946 The Mid-Atlantic Region Forum]
* [https://www.waze.com/forum/viewforum.php?f=129 The USA Section of the Waze Forum]
* [https://www.waze.com/forum/viewforum.php?f=622 US Unlock and Update Requests Forum]


''[[Area_Manager|Area Managers]] for West Virginia can be found in [[West_Virginia#Area_Managers|the table below]].''


''New editors should consider checking into the [[Mentoring/Formal|Formal Mentoring Program]] available at no charge.''
<nowiki>== Closures ==</nowiki>


=== Waze West Virginia Google Hangout (GHO) ===


We have created a Google Hangout (GHO) just for West Virginia. The GHO is where you can go to interact and chat with fellow editors along with your Area and State Managers. It will give you good insight into the best practices and policies in regard to map editing plus give an easy, convenient way for editors to stay in touch, ask questions (''any questions, we all started at Rank #1 at some point''), request downlocks or review of your work and get Peer-to-Peer Mentoring. 


If you are editing in WV and have not already been invited, please send a PM (Private Message) to [https://www.waze.com/forum/memberlist.php?mode=viewprofile&u=16973197 Stephen] and/or [https://www.waze.com/forum/memberlist.php?mode=viewprofile&u=16946130 Todd-Roadtechie] along with your email address so that we can invite you to the hangout.
Construction Project or Emergencies that cause roads to be closed can be reported in the WV GHO. You will need to have a PL to the segment(s) that need closed, the start time and the end time, and the reason for the closure. 


=== West Virginia User Report Management Response Timeline ===


''(NOTE: all day values are relative to the date the FIRST editor response is sent to the reporter)''


'''Day 0'''
You can also report Construction projects or emergencies that cause roads to be closed on this <nowiki>[http://docs.google.com/forms/d/1oGINt4UEkBV0Par5VCingXzTZpJq9KjG8GbZpGqbRow/viewform Closure Form]</nowiki>.  Events that cause road closures should be reported on this <nowiki>[http://docs.google.com/forms/d/1R0XIsGkHQmk8Nc0U5DDID1PwMQWqLMwmindiLDFwcjo/viewform Event Form]</nowiki>.  Current closures and events in West Virginia that have been reported to Waze are shown in the <nowiki>[https://docs.google.com/spreadsheets/d/1uuqKJ66upFjKmrNCUtnVUeDkhPi0MB-chiGS_s_dNW0/pubhtml West Virginia Closure Sheet]</nowiki>.


The first editor who is able to respond to a User Report (UR) should attempt to resolve the UR. If they are successful, they should comment as such in the UR and mark it '''"Solved'''". If more information from the reporter is required to make progress towards closure, a response should be sent to the reporter containing the information needed for resolution.


'''Day 4+'''


Polite reminders should be sent to reporters who have not responded to the initial at any time, '''provided at least four full days have elapsed''' since the initial response was sent
<nowiki>=== Sources For Road Closures ===</nowiki>


'''Day 8+'''
<nowiki>[http://wv511.org/ WV511]</nowiki>


URs may be noted as closed due to lack of reporter response at any time, '''provided at least four full days have elapsed''' since the followup message was sent. These need to be marked as '''"Not Identified"''' and a brief comment sent.


'''Shared Ownership'''


All editors are considered to have equal ownership of and responsibility for all URs in West Virginia. All editors, regardless if they have worked the UR previously, may send any of the responses described above, provided they adhere the minimum time spacing guidance between responses. All editors are explicitly encouraged to attempt to resolve URs at any point during their lifecycle, even if others happen to be actively working it at the same time.
WV DOT Work Zones


'''Notes'''


The ideal timeline for UR response is when responses are sent as early as the minimum required time spacing between messages permits; experience has reliably shown that UR response rates are much higher when editors are able to send responses promptly. The 4+ day followup / reminder has shown remarkable improvement in reporter response everywhere that it has been implemented.


The script [[Scripts#URComments|URComments]] streamlines the process of responding to a UR and provides comments based on the UR type and can be edited prior to sending to fit your needs.
<nowiki>*</nowiki> <nowiki>[http://www.transportation.wv.gov/highways/districts/district-one/Pages/work-zones.aspx District  1]</nowiki> [Boone, Clay, Kanawha, Mason, Putnam]


=== Downlock Requests ===
<nowiki>*</nowiki> <nowiki>[http://www.transportation.wv.gov/highways/districts/district-two/Pages/work-zones.aspx District  2]</nowiki> [Cabell, Lincoln, Logan, Mingo, Wayne]


==== Definitions ====
<nowiki>*</nowiki> <nowiki>[http://www.transportation.wv.gov/highways/districts/district-three/Pages/highway-projects.aspx District 3]</nowiki> [Calhoun, Jackson, Pleasants, Ritchie, Roane, Wirt, Wood]
* Downlock (or Down-Lock): Term used to describe the process of adjusting the Segment Lock level in WME down to match the regional standards, or the Rank of an editor to allow them to edit the segment(s).
* Uplock (or Up-Lock): Term used to describe the process of adjusting Segment Lock levels up in WME. Often to its prior Segment Lock level before it was Down-Locked to match the Rank of an editor to allow them to edit the segment(s).
* Permalink (or PL): A URL aka browser link (http://...) that shows the map with the same view as the user who created the Permalink (PL). Location, zoom, layers, and selected segments will be the same. You can find the icon for the Permalink in the lower right corner of the WME screen (two chains linked together). When the mouse is hovered over the icon, press Control-C to copy the Permalink to the clipboard (or right-click it and choose copy). You can then paste the PL into an e-mail or forum message so others can access what you are seeing.


==== Request Format ====
<nowiki>*</nowiki> <nowiki>[http://www.transportation.wv.gov/highways/districts/district-four/Pages/work-zones.aspx District  4]</nowiki> [Doddridge, Harrison, Marion, Monongalia, Preston, Taylor]


A downlock request can made in the West Virginia Google Hangout. The request itself shall be constructed as follows:
<nowiki>*</nowiki> <nowiki>[http://www.transportation.wv.gov/highways/districts/district-five/Pages/work-zones.aspx District  5]</nowiki> [Berkeley, Grant, Hampshire, Hardy, Jefferson, Mineral, Morgan]


'''Dnlock Lx-Ly, "City", "Reason", PL'''
<nowiki>*</nowiki> <nowiki>[http://www.transportation.wv.gov/highways/districts/district-six/Pages/work-zones.aspx District  6]</nowiki> [Brooke, Hancock, Marshall, Ohio, Tyler, Wetzel]


* Lx = Current Lock Level
<nowiki>*</nowiki> <nowiki>[http://www.transportation.wv.gov/highways/districts/district-seven/Pages/work-zones.aspx District  7]</nowiki> [Barbour, Braxton, Gilmer, Lewis, Upshur, Webster]
* Ly = Proposed Lock Level
* City = Closest City the request is being requested. Such as Morgantown, Huntington, etc.
* Reason = Whatever Reason for the request. Examples include Speed Limits (SL), Elevation, Geometry, etc.
* Say Please!


===== Formatting the Permalink (PL) =====
<nowiki>*</nowiki> <nowiki>[http://www.transportation.wv.gov/highways/districts/district-eight/Pages/work-zones.aspx District  8]</nowiki> [Pendleton, Pocahontas, Randolph, Tucker]


''Zoom In! Selecting a PL at the widest extent (Zoom=0) will not enable the editor who may grant your request to select anything. If necessary, break up your PL into multiple requests.''
<nowiki>*</nowiki> <nowiki>[http://www.transportation.wv.gov/highways/districts/district-nine/Pages/work-zones.aspx District  9]</nowiki> [Fayette, Greenbrier, Monroe, Nicholas, Summers]


''And be patient; an editor may be occupied elsewhere, helping other editors or at their place of employment. ''
<nowiki>*</nowiki> <nowiki>[http://www.transportation.wv.gov/highways/districts/district-ten/Pages/work-zones.aspx District 10]</nowiki> [McDowell, Mercer, Raleigh, Wyoming]


'''Automatically:'''


Install [https://www.waze.com/forum/viewtopic.php?f=819&t=172335 WME Keep My Layers] (KML) before you copy your first PL. This will automate the process of stripping the PL of unnecessary and unwanted information, resulting in a clean efficient PL. If for any reason, this script does not function as intended, follow the instructions below under "Manually" to cleanup the PL.


'''Manually:'''
<nowiki>[http://www.transportation.wv.gov/highways/Highways-Projects/Pages/default.aspx WV DOT Highway Projects]</nowiki>


# Before copying a PL hover over the "chain link" icon and press the "Shift" key. This will eliminate the layers in your PL. This assumes you have installed [[Scripts#WME_Toolbox|WME Toolbox]] . Which you should.
# Delete all the information, starting with the "&" after the segment ID. For example, ...&segments=1234567&... Delete everything after the last number in segments. This also applies to &venues=123456789.1234567890.1234567 (for Places) and &MapUpdateRequest=1234567 (for URs)


'''Finished Example:'''


Dnlock L5-L2, Huntington, SLs, Elevation, https://www.waze.com/editor/?env=usa&lon=-82.42197&lat=38.39253&zoom=5&segments=65476746
City Engineers, Local TV, Newspapers, Radio, Twitter, Facebook, etc. 


=== Uplock Requests ===
Upon finishing your editing, create another PL with the segments needed to Uplock to the [[West_Virginia#Minimum_Lock_Standard|Minimum Lock Standard]]. Use the format '''Uplock Lx-Ly "PL"''' . This is done because the person performing the uplock may be using a mobile device and it is difficult to select the correct segments. Also, if you add a junction node for a speed limit or PLR, for example, it will create new segment IDs and those will not be the same as the original dnlock request.


--[[User:Markr4468|Markr4468]] ([[User talk:Markr4468|talk]]) 21:27, 22 April 2016 (UTC)
 
<nowiki>== Major Roads ==</nowiki>
 
 
 
<nowiki>=== WV Route Naming ===</nowiki>
 
<nowiki><big>Separate Page with this info</big></nowiki>
 
<nowiki>==== Introduction ====</nowiki>
 
<nowiki>''</nowiki>The West Virginia Department of Transportation (WVDOT) provides <nowiki>[http://www.transportation.wv.gov/highways/programplanning/gti/GIS/MAPS/Pages/WVMapGISSelect.aspx County Highway Maps]</nowiki> for each of the 55 Counties in West Virginia (WV). Those County Maps provide information on Route Designation for each road WV maintains. The following are the types of roads typically seen on each of the County Maps and how they should be named and typed in the Waze Map. At this time, WV does not have a GIS Functional Classification (FC) Map.
 
 
 
Any questions, please ask in the WV Google Hangout (WV GHO) or <nowiki>[[West_Virginia#Area_Managers|Private Message]]</nowiki> (PM) one of the State Managers. 
 
<nowiki>''</nowiki>
 
<nowiki>==== Interstate ====</nowiki>
 
 
 
<nowiki>[[File:WV_Interstate.PNG]]</nowiki>
 
 
 
<nowiki>*</nowiki> Waze Road Type – Freeway (FW)
 
<nowiki>*</nowiki> Name – I-64 N (direction is always one-way and always includes the cardinal direction)
 
<nowiki>*</nowiki> Lock Level - L5 or higher
 
<nowiki>==== US Route ====</nowiki>
 
 
 
<nowiki>[[File:US Route.PNG]]</nowiki>
 
 
 
<nowiki>*</nowiki> Waze Road Type – Typically Major Highway (MH) unless FC upgrades
 
<nowiki>*</nowiki> Name – US-60 (if divided/One-Way, include cardinal direction, e.g. US-60 N)
 
<nowiki>*</nowiki> <nowiki>''</nowiki>US BUS/SPUR/LOOP are Minor Highway (mH) unless FC upgrades<nowiki>''</nowiki>
 
<nowiki>*</nowiki> Lock Level - L4 or higher
 
<nowiki>==== WV State Route ====</nowiki>
 
 
 
<nowiki>[[File:WV_Route.PNG]]</nowiki>
 
 
 
<nowiki>*</nowiki> Waze Road Type – Typically Minor Highway (mH)
 
<nowiki>*</nowiki> Name – WV-10 (if divided/One-Way, include cardinal direction, e.g. WV-10 S)
 
<nowiki>*</nowiki> <nowiki>''</nowiki>WV BUS/SPUR/LOOP are Primary Street unless FC upgrades<nowiki>''</nowiki>
 
<nowiki>*</nowiki> Lock Level - L3 or higher
 
<nowiki>==== WV County Route ====</nowiki>
 
 
 
<nowiki>[[File:WV_County Route.PNG]]</nowiki>
 
 
 
<nowiki>*</nowiki> Waze Road Type – Street (unless FC upgrades higher)
 
<nowiki>*</nowiki> Name – CR-2 or CR-2/12
 
<nowiki>*</nowiki> Lock Level - Depends on FC; L1 or higher
 
 
 
<nowiki>==== WV HARP Route ====</nowiki>
 
 
 
<nowiki>[[File:WV_Harp_Route.PNG]]</nowiki>
 
 
 
<nowiki>*</nowiki> Waze Road Type – Street 
 
<nowiki>*</nowiki> Name – <nowiki>'''</nowiki>not typically used<nowiki>'''</nowiki>. Only if no name for that street can be found (please ask in the GHO first). HARP-901 or HARP-901/20. 
 
<nowiki>*</nowiki> Lock Level - L1
 
<nowiki>==== WV FANS Route ====</nowiki>
 
 
 
<nowiki>[[File:WV_FANS_Route.PNG]]</nowiki>
 
 
 
<nowiki>*</nowiki> Waze Road Type – Based on Functional Classification Only
 
<nowiki>*</nowiki> Name – <nowiki>'''</nowiki>Alt Name Only<nowiki>'''</nowiki> if FC upgrades road type to Primary Street or higher. Drop the leading digit. FANS-863
 
<nowiki>*</nowiki> Alt name is needed so we know that a FC upgrade has been applied to what normally should be "Street" in the Waze Map.
 
<nowiki>*</nowiki> Lock Level - Depends on FC; L2 or higher
 
 
 
<nowiki>==== Functional Classification ====</nowiki>
 
 
 
WV, at this time, does not have a GIS map that will make decision making as to the proper road type (Street/Primary Street/Minor Highway/Major Highway/Freeway) easy or quick. They do have a list of Federal Aid Roads which includes the roads with a functional classification of minor collector or higher. The issue we have found so far, is that it lists that classification by mile markers. We have no sure way of knowing where that classification starts and ends with any great deal of certainty. It can be done with some experience and common sense. Please work with the State Managers to learn more. You can review the <nowiki>[ftp://gis.transportation.wv.gov/HPMS_Reports/WV_FA_Roads_2015.pdf complete list]</nowiki> here. And StephenR1966 has put together a <nowiki>[https://docs.google.com/spreadsheets/d/1FUNOb5UqYToEZv-mSK5SVxfyUTZqVqJaJyL_otQlyVw/edit#gid=1099177487 Google Sheet]</nowiki> that translates the list into which roads the classification applies to. This is why it's important to have the correct road designation in either the primary or alternate name in order to find a particular road and apply the correct functional classification to it. <nowiki>''</nowiki>Note that some roads are listed as more than once; this means that they can be for example mH for part and MH for part and PS for part. Please ask in the GHO for more help if you find examples of this.<nowiki>''</nowiki>
 
 
 
<nowiki>==== NOTES ====</nowiki>
 
 
 
<nowiki>*</nowiki> Within City Limits, most roads should have a name; use that instead of the Route Designation and put the Route Designation as the Alt Name. Consult County GIS sources or Street View. 
 
<nowiki>*</nowiki> Most US and WV State Routes do not have a name unless inside city borders (e.g. Main St) or part of a major highway project (e.g. King Coal Highway). Even then, check street view to confirm the name is on the signs.  
 
<nowiki>*</nowiki> All WV County Roads do have a name; you can find it using Street View or County GIS sources. If you cannot find it, then use the Road Designation as the Primary.
 
<nowiki>*</nowiki> All FANS Roads are within City Limits. Only put a FANS Designation (and always as Alt Name) if FC upgrades that segment to PS or higher. That lets everyone know the reason for the FC upgrade.
 
<nowiki>*</nowiki> If the Primary Name includes a "city", then any alternate names must include the same city and vice-versa.  
 
<nowiki>*</nowiki> Do not deviate from the road type unless the correct Functional Classification has been applied. Doing so can and will create issues with routing.

Revision as of 15:49, 5 October 2016

<big>TEST PAGE</big>

''<small>Sections of Main Wiki Page</small>''


== Closures ==


Construction Project or Emergencies that cause roads to be closed can be reported in the WV GHO. You will need to have a PL to the segment(s) that need closed, the start time and the end time, and the reason for the closure. 


You can also report Construction projects or emergencies that cause roads to be closed on this [http://docs.google.com/forms/d/1oGINt4UEkBV0Par5VCingXzTZpJq9KjG8GbZpGqbRow/viewform Closure Form].  Events that cause road closures should be reported on this [http://docs.google.com/forms/d/1R0XIsGkHQmk8Nc0U5DDID1PwMQWqLMwmindiLDFwcjo/viewform Event Form].  Current closures and events in West Virginia that have been reported to Waze are shown in the [https://docs.google.com/spreadsheets/d/1uuqKJ66upFjKmrNCUtnVUeDkhPi0MB-chiGS_s_dNW0/pubhtml West Virginia Closure Sheet].


=== Sources For Road Closures ===

[http://wv511.org/ WV511]


WV DOT Work Zones


* [http://www.transportation.wv.gov/highways/districts/district-one/Pages/work-zones.aspx District  1] [Boone, Clay, Kanawha, Mason, Putnam]

* [http://www.transportation.wv.gov/highways/districts/district-two/Pages/work-zones.aspx District  2] [Cabell, Lincoln, Logan, Mingo, Wayne]

* [http://www.transportation.wv.gov/highways/districts/district-three/Pages/highway-projects.aspx District 3] [Calhoun, Jackson, Pleasants, Ritchie, Roane, Wirt, Wood]

* [http://www.transportation.wv.gov/highways/districts/district-four/Pages/work-zones.aspx District  4] [Doddridge, Harrison, Marion, Monongalia, Preston, Taylor]

* [http://www.transportation.wv.gov/highways/districts/district-five/Pages/work-zones.aspx District  5] [Berkeley, Grant, Hampshire, Hardy, Jefferson, Mineral, Morgan]

* [http://www.transportation.wv.gov/highways/districts/district-six/Pages/work-zones.aspx District  6] [Brooke, Hancock, Marshall, Ohio, Tyler, Wetzel]

* [http://www.transportation.wv.gov/highways/districts/district-seven/Pages/work-zones.aspx District  7] [Barbour, Braxton, Gilmer, Lewis, Upshur, Webster]

* [http://www.transportation.wv.gov/highways/districts/district-eight/Pages/work-zones.aspx District  8] [Pendleton, Pocahontas, Randolph, Tucker]

* [http://www.transportation.wv.gov/highways/districts/district-nine/Pages/work-zones.aspx District  9] [Fayette, Greenbrier, Monroe, Nicholas, Summers]

* [http://www.transportation.wv.gov/highways/districts/district-ten/Pages/work-zones.aspx District 10] [McDowell, Mercer, Raleigh, Wyoming]


[http://www.transportation.wv.gov/highways/Highways-Projects/Pages/default.aspx WV DOT Highway Projects]


City Engineers, Local TV, Newspapers, Radio, Twitter, Facebook, etc. 


== Major Roads ==


=== WV Route Naming ===

<big>Separate Page with this info</big>

==== Introduction ====

''The West Virginia Department of Transportation (WVDOT) provides [http://www.transportation.wv.gov/highways/programplanning/gti/GIS/MAPS/Pages/WVMapGISSelect.aspx County Highway Maps] for each of the 55 Counties in West Virginia (WV). Those County Maps provide information on Route Designation for each road WV maintains. The following are the types of roads typically seen on each of the County Maps and how they should be named and typed in the Waze Map. At this time, WV does not have a GIS Functional Classification (FC) Map.


Any questions, please ask in the WV Google Hangout (WV GHO) or [[West_Virginia#Area_Managers|Private Message]] (PM) one of the State Managers. 

''

==== Interstate ====


[[File:WV_Interstate.PNG]]


* Waze Road Type – Freeway (FW)

* Name – I-64 N (direction is always one-way and always includes the cardinal direction)

* Lock Level - L5 or higher

==== US Route ====


[[File:US Route.PNG]]


* Waze Road Type – Typically Major Highway (MH) unless FC upgrades

* Name – US-60 (if divided/One-Way, include cardinal direction, e.g. US-60 N)

* ''US BUS/SPUR/LOOP are Minor Highway (mH) unless FC upgrades''

* Lock Level - L4 or higher

==== WV State Route ====


[[File:WV_Route.PNG]]


* Waze Road Type – Typically Minor Highway (mH)

* Name – WV-10 (if divided/One-Way, include cardinal direction, e.g. WV-10 S)

* ''WV BUS/SPUR/LOOP are Primary Street unless FC upgrades''

* Lock Level - L3 or higher

==== WV County Route ====


[[File:WV_County Route.PNG]]


* Waze Road Type – Street (unless FC upgrades higher)

* Name – CR-2 or CR-2/12

* Lock Level - Depends on FC; L1 or higher


==== WV HARP Route ====


[[File:WV_Harp_Route.PNG]]


* Waze Road Type – Street 

* Name – '''not typically used'''. Only if no name for that street can be found (please ask in the GHO first). HARP-901 or HARP-901/20. 

* Lock Level - L1

==== WV FANS Route ====


[[File:WV_FANS_Route.PNG]]


* Waze Road Type – Based on Functional Classification Only

* Name – '''Alt Name Only''' if FC upgrades road type to Primary Street or higher. Drop the leading digit. FANS-863

* Alt name is needed so we know that a FC upgrade has been applied to what normally should be "Street" in the Waze Map.

* Lock Level - Depends on FC; L2 or higher


==== Functional Classification ====


WV, at this time, does not have a GIS map that will make decision making as to the proper road type (Street/Primary Street/Minor Highway/Major Highway/Freeway) easy or quick. They do have a list of Federal Aid Roads which includes the roads with a functional classification of minor collector or higher. The issue we have found so far, is that it lists that classification by mile markers. We have no sure way of knowing where that classification starts and ends with any great deal of certainty. It can be done with some experience and common sense. Please work with the State Managers to learn more. You can review the [ftp://gis.transportation.wv.gov/HPMS_Reports/WV_FA_Roads_2015.pdf complete list] here. And StephenR1966 has put together a [https://docs.google.com/spreadsheets/d/1FUNOb5UqYToEZv-mSK5SVxfyUTZqVqJaJyL_otQlyVw/edit#gid=1099177487 Google Sheet] that translates the list into which roads the classification applies to. This is why it's important to have the correct road designation in either the primary or alternate name in order to find a particular road and apply the correct functional classification to it. ''Note that some roads are listed as more than once; this means that they can be for example mH for part and MH for part and PS for part. Please ask in the GHO for more help if you find examples of this.''


==== NOTES ====


* Within City Limits, most roads should have a name; use that instead of the Route Designation and put the Route Designation as the Alt Name. Consult County GIS sources or Street View. 

* Most US and WV State Routes do not have a name unless inside city borders (e.g. Main St) or part of a major highway project (e.g. King Coal Highway). Even then, check street view to confirm the name is on the signs.  

* All WV County Roads do have a name; you can find it using Street View or County GIS sources. If you cannot find it, then use the Road Designation as the Primary.

* All FANS Roads are within City Limits. Only put a FANS Designation (and always as Alt Name) if FC upgrades that segment to PS or higher. That lets everyone know the reason for the FC upgrade.

* If the Primary Name includes a "city", then any alternate names must include the same city and vice-versa.  

* Do not deviate from the road type unless the correct Functional Classification has been applied. Doing so can and will create issues with routing.

Retrieved from "https://beta.waze.com/wiki/USA/index.php?title=User:Markr4468&oldid=149976"