User:PesachZ/SyncScratch View history

Revision as of 05:14, 16 February 2017

Press here to return to the SyncScratch section to see your changes

New editors should be sure to check out the following pages before editing the maps.
Best Map Editing Practice
Common Editing Mistakes
Waze Map Editor

The Wisconsin DOT provides various state, county, and Functional Classification maps.
GIS maps are maintained by the counties they serve.
See PesachZ/Resources for lists of these maps.

Editing Scripts

There are many scripts available to assist in editing. Waze User Scripts

When using the Validator script, it is recommended that you also install the Wisconsin Localization Validator Add-On

To display the county borders, install this script WME Counties Wisconsin Census 2014

The following scripts are also highly recommended (and is not all-inclusive of available scripts):

WME Chat Addon
WME Closest Segment
WME UR Comments
WME HN Tool
WME Color Highlights
UROverview Plus
WME Speeds
WME Road Selector
WME Clicksaver
WME KeepMyLayers

These scripts are more for advanced editing and monitoring:

WME Route Speeds
WME Route Checker
WME UR-MP Tracking
WME GIS

Wisconsin Google Drive Resources
We have a Google Drive that we use for documents and spreadsheets to help with many areas of editing in our state. The link is: Wisconsin Google Drive

@@ Line 2: / Line 2: @@
 ------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>
-==== Highway Status ====
+New editors should be sure to check out the following pages before editing the maps.<br/>
-The status for all interstates, federal, and state highways running through Idaho [[Idaho/Major_roads|are documented here]]. This includes any project status pertaining to those highways, as well as any known changes coming down the pike from ITD and/or other cities as we find out about them.
+[https://wiki.waze.com/wiki/Best_map_editing_practice Best Map Editing Practice]<br/>
+[https://wiki.waze.com/wiki/Common_editing_mistakes Common Editing Mistakes]<br/>
+[https://wiki.waze.com/wiki/Waze_Map_Editor Waze Map Editor]<br/>
-==== State highway naming ====
+* The Wisconsin DOT provides various state, county, and Functional Classification maps.
-[[File:ID-Highway-Blank.png|48px|left|frameless|Idaho Highway]]
+* GIS maps are maintained by the counties they serve.
-State highways are to be named '''SH-###'''<br><br>
+* See [[{{BasePage2}}/Resources]] for lists of these maps.
-There is [[Glossary#TTS|TTS support]] to name state highways as '''ID-###''' but doing this will cause the state shields to go away in the app. Until this is implemented fully, we will stick with the '''SH-###''' format.
+====Editing Scripts====
+There are many scripts available to assist in editing. [https://wiki.waze.com/wiki/Scripts Waze User Scripts]
-Exception: Ramp names can use the '''ID-###''' format since they do not carry shields.
+When using the [https://wiki.waze.com/wiki/Scripts#WME_Validator Validator] script, it is recommended that you also install the [https://greasyfork.org/en/scripts/8748-wme-validator-localization-for-wisconsin Wisconsin Localization Validator Add-On]
-==== County road naming ====
+To display the county borders, install this script [https://greasyfork.org/en/scripts/11498-wme-counties-wisconsin-census-2014 WME Counties Wisconsin Census 2014]
-[[File:WY-County-Blank.png|48px|left|frameless|Wyoming County]]County roads with the name designation of "County Road ##" or "Co Rd ##" are to be named in Waze as '''CR-##'''. This shortened version takes up less space on the map screen and is announced correctly as "County Road ##" while navigating with the Waze app.<br><br>
+The following scripts are also highly recommended (and is not all-inclusive of available scripts):
-==== Locking standard ====
+[https://wiki.waze.com/wiki/Scripts#WME_Chat_addon WME Chat Addon]<br>
+[https://greasyfork.org/en/scripts/8693-wme-closest-segment WME Closest Segment]<br>
+[https://wiki.waze.com/wiki/Scripts#URComments WME UR Comments]<br>
+[https://greasyfork.org/en/scripts/9183-wme-hn-tool WME HN Tool]<br>
+[https://wiki.waze.com/wiki/Scripts#WME_Color_Highlights WME Color Highlights]<br>
+[https://wiki.waze.com/wiki/Scripts#UR_Overview_Plus_.28URO.2B.29 UROverview Plus]<br>
+[https://greasyfork.org/en/scripts/12402-wme-speeds WME Speeds]<br>
+[https://wiki.waze.com/wiki/Scripts#WME_Road_Selector WME Road Selector]<br>
+[https://greasyfork.org/en/scripts/22059-wme-clicksaver WME Clicksaver]<br>
+[https://greasyfork.org/en/scripts/15698-wme-keepmylayers WME KeepMyLayers]<br>
-In Idaho, we have a set minimum standard for locking roads based on segment type. Any road of a certain segment type must be locked at least to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower.
+These scripts are more for advanced editing and monitoring:
-A great time to implement these locks is while bringing the road types of an area into compliance with the current US road type standards (FC and highway systems). Lock the roads based on type after they've been set to [[Road_types/USA#Public_roads|current US road type standards]].
+[https://wiki.waze.com/wiki/Scripts#WME_Route_Speeds_.28Traffic.29 WME Route Speeds]<br>
+[https://wiki.waze.com/wiki/Scripts#WME_Route_Checker WME Route Checker]<br>
+[https://greasyfork.org/en/scripts/1776-wme-ur-mp-tracking WME UR-MP Tracking]<br>
+[https://greasyfork.org/en/scripts/21228-wme-gis WME GIS]<br>
-{| class="wikitable" style="text-align:center; margin: 1em auto 1em auto; width: 40%"
+'''Wisconsin Google Drive Resources'''<br>
-|+ Idaho Minimum Locking Ranks
+We have a Google Drive that we use for documents and spreadsheets to help with many areas of editing in our state.  The link is: [https://drive.google.com/open?id=0B83plf0s6oCmdHFnNEZEQUFsVTA Wisconsin Google Drive]
-! Segment Type !! Rank
-|-
-| {{Freeway}}||4
-|-
-| {{Ramp}}||4
-|-
-| {{Major Highway}} || 3
-|-
-| {{Minor Highway}} || 2
-|-
-| {{Primary Street}} || 2
-|-
-| {{Railroad}}|| 2
-|-
-| All Others || 1
-|}
-==== Roads named N, S, E or W ====
-If you encounter any roads that are named N, S, E, or W, you must add a period (.) to the end of the letter. For example, West N Street is abbreviated as '''W N. St'''. County Road W is abbreviated as '''CR-W.''', and so on. This ensures the TTS system reads the road name as "County Road W" and not "County Road West."
-==== U-turns ====
-Page 2-10 of the [http://itd.idaho.gov/wp-content/uploads/2016/06/driver_manual.pdf Idaho Driver's Manual] says this about U-turns:
-:U-turns are not legal everywhere, so first look for prohibiting signs. When making a U-turn near a hill or curve, the law requires that you be able to see 500 feet in either direction. U-turns are prohibited in no-passing zones. Stop and yield to all traffic before completing a U-turn.
-For Waze routing, u-turns should only be enabled where they provide the potential for improved routing, which includes recovering from missed turns. A common example is a median-divided primary street that has homes/businesses with their driveways/entrances directly on it, where reaching them would otherwise require lengthy, multi-turn deviations through side roads in order to end up on the correct side of the median.
-==== Road Elevations ====
-These are the general guidelines for elevation in Idaho:
-* Drivable and non-drivable segments are handled the same way with elevation.
-* Set elevation to ground in most cases.
-** Segment(s) passing over other segment(s), rivers, major waterways, and ''all bridges'' shall have higher elevation, relative to ground.
-** Only elevate/lower the actual bridge/tunnel section of the road.
-** Elevation of overlapping segments should be set relative to each other, with the lowest segment as Ground (unless a tunnel).
-** Tunneled segments shall have lower elevation, relative to ground.
-** Only segments that "cannot see the sky" should have negative elevation (i.e. tunnels).
-** Only set elevation as low/high as necessary.
-* If you use the Bridge tool to join segments, be aware that it raises the elevation of the joined segment. Lower the joined segment as appropriate.
-* [[Elevation_-_bringing_the_Seagull_to_Australia|"Seagull"]] guidelines apply to elevation in Idaho.
-** Bridges should be cut at the start/end of the bridge.
-** Tunnels should be cut at least 15m/50ft '''before''' and '''after''' the tunnel, to allow time for the GPS to regain signal.
-** Do not cut segments for elevation purposes if the bridge/tunnel starts/stops within 60m/200ft of an existing junction.
 <!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----
@@ Line 79: / Line 52: @@
 ---- desired, it can be restored by adding the following code to the first line
 ---- between the "DO NOT MODIFY" lines on this page:
-----   {{:USA/CommonState/Major_roads|optional}}
+----   {{:USA/CommonState/Resources|optional}}
 ----
 -------------------------------------------------------------------------------------
@@ Line 88: / Line 61: @@
 ---- saved.
 ----
-See [[{{BasePage2}}/Major roads]] for guidance in {{RootPage2}} that may not be universal to all other states.
+See [[{{BasePage2}}/Resources]] for guidance in {{RootPage2}} that may not be universal to all other states.
 ----
 -------------------------------------------------------------------------------------

Search

User:PesachZ/SyncScratch View history

Revision as of 05:14, 16 February 2017

Editing Scripts