User:PesachZ/SyncScratch View history

m (Copying text of wiki page for coparison with the "New Jersey/AM/Editor/Area2" page)
m (Copying text of wiki page for coparison with the "Wisconsin/Major roads/Main" page)
Line 1: Line 1:
<!---------------------- DO NOT MODIFY THIS TOP CODE ------------------------------
<!-- This page is only transcluded into (displayed on) the main page for this state. See more detailed instructions below. --><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--
------------------------ SCROLL DOWN FOR INSTRUCTIONS -----------------------------><noinclude><!--Keep hard coded due to unique page address--><div class="center"><span class="noprint plainlinks purgelink" style="{{Road/style}}backgrhttps://wiki.waze.com/wiki/index.php?title=New_Jersey&action=purge#Other_Area_Editorsound-color:#93c4d3">[{{FULLURL:{{#titleparts:{{PAGENAME}}|-3}}|action=purge}}#Other_Area_Editors <span title="Return to the Other Area Editor table">&nbsp;Press here to return to the Other Area Editors table to see your changes&nbsp;</span>]</span></div></noinclude><includeonly><!--
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>
 
=== Functional Classifications ===
Wisconsin follows the [[National_resources/USA/Functional_classification|Functional Classification]] (FC) system for the USA.
 
To help update the current Wisconsin roadways to the new functional classifications, go to the [[Wisconsin/Resources|Wisconsin Functional Classification Inventory]]. 
<br /><small>Links to the FC maps for the state of Wisconsin can be found on the [[{{BasePage2}}/Resources]] page.</small>
 
 
==== Minimum Road Lock Standard ====
{| class="wikitable" style="text-align:center"
!colspan="3" style="background-color:#6699cc"|Minimum Road Lock Standard
|-
|style="font-weight:bold; background-color:#ccffcc"|Segment Type
|style="font-weight:bold; background-color:#ccffcc"|Direction
|style="font-weight:bold; background-color:#ccffcc"|Level
|-
|{{Freeway|Freeway}}
|
|5
|-
|{{Ramp|Ramp}}
|
|HCS*
|-
|{{Major Highway|Major Highway}}
|
|3
|-A
|{{Minor Highway|Minor Highway}}
|
|3
|-
|rowspan="2"|{{Primary Street|Primary Street}}
|One-way
|3
|-
|Two-way
|2
|-
|rowspan="2"|{{Street|Street}}<br>{{Private Road|Private Road}}
|One-way
|2
|-
|Two-way
|1
|-
|{{Railroad|Railroad}}
|
|2
|-
|{{Ferry|Ferry}}
|
|2
|-
|{{Runway|Runway}}
|
|5
|-
|Other Named Types
|
|1
|-
|style="font-weight:bold; background-color:#ffffcc"|Segment Group
|style="font-weight:bold; background-color:#ffffcc"|
|style="font-weight:bold; background-color:#ffffcc"|Level
|-
|Construction Areas<br><small>''(changes without aerial images)''</small>
|
|3
|}
''Terms''
* HCS - Highest Connecting Segment
 
===== Additional Info =====
====== Expectations ======
We understand that higher locks mean there is less available to lower rank and beginning editors. We would like to emphasize that Waze Map Editing is a community activity and, within the US, it is not possible to increase to rank 3 or above without community involvement. It is the responsibility of all members of the editing community to actively reach out, recruit, and mentor new editors.
 
It is OK to '''temporarily lock segments below standards''' for more junior editors. Area Managers are encouraged to monitor their areas for non-standard locks and follow up with other editors on any discrepancies. As a courtesy, any down-locks made outside your area should be brought to the attention of the local area manager.
 
====== One-Way Streets ======
The +1 locks on one-way segments originated as guidance from GLR RC GizmoGuy411 based on trends found while  performing Area Manager Reviews:
He would encourage editors to +1-lock one-way street/PS in order to explicitly signal, "Yes, the legwork has been done in order to confirm this segment really is one-way, and it's not a soft-directional issue."
 
 
=== Name Normalization ===
 
Wisconsin will use the following standards for road naming: <br />
Freeways - I-### <br />
US Highways - US-### <br />
State Highways - WIS-### <br />
County Highways - CH-XXX <br />
Forest Roads - FR-### <br />
{{mbox | type = warning | text = There are no Township (Town) Roads in the state. All Town Roads are named, and those names will be used. The only exceptions would be if the road signage states differently.}}<br />
 
 
=== Bridge and Overpass Segmentation Elevation (BOSE) ===
'''Please note that there are regional and national discussions ongoing for establishing standards beyond state level.  If those changes come in opposition to what we are doing here, then we will be changing to follow suit.'''<br />
 
Wisconsin has decided on a state standard for the segmentation of bridges and overpasses.<br />
 
The National Wiki contains the standard information regarding proper elevation of segments.  What we are doing in Wisconsin is expanding on those standards to create a more accurate representation of the segments.<br />
 
Basic elevation is determined using the following rules:
* All roads start at Ground elevation
* If a segment is above another segment, it should be set to +1 relative to the lower segment's elevation (to account for multiple segments overlapping)
* If a segment is a tunnel (not just an underpass), it should be set at -1, and Tunnel should be checked.<br />
 
'''Bridges'''<br />
Definition:
* If a segment travels over a river or body of water, it is considered a bridge
* If a segment travels over another segment, it is considered it a bridge (aka: overpass).
* If a segment is artificially elevated to pass over ground level objects and natural features, it is considered a bridge.<br />
 
Junctioning:<br />
Place a junction at the start/end of the bridge where the land falls away.
*If there is already a junction within 500 feet of the bridge, do not add a new junction.
*Do not junction a bridge if it is less than 75 feet in length.  If you believe you need to do so, contact an SM or LAM for approval.<br />
 
'''Ramps'''<br />
Ramps should always be set to Ground. The only time a ramp segment is set above or below ground is when it travels above or below another segment as a bridge or a tunnel. This is most often the case in large interchanges, like the Marquette interchange in Milwaukee. When a ramp traverses over or under another segment, you should follow the elevation guidelines listed above.<br />
 
Do not segment a ramp like you would for a bridge, unless it takes on several different elevations.<br />
 
Because of the complexity of interchanges, please contact your State Manager before making adjustments.<br />
 
'''Special Note'''
 
''This process was derived from the Seagull Effect created by the Australians.  The process has been unofficially called ‘seagulling’.  Please note that this word is a misuse of the Seagull Effect.  Using it may have unintended connotations.''
 
 
=== Additional notes for this state ===
 
====Dirt Roads====
In Wisconsin all drivable roads that are unpaved are considered Dirt Road/4X4 Trail; this is how drivers expect the "Avoid Dirt Roads" feature to behave. Note that Functional Classification '''WILL''' override the Dirt Road type. Set those roads to their proper PS, mH, MH, FW type.
 
The new Dirt Road checkbox is NOT to be used at this time, as it is currently non-functional.
 
====Toll Roads====
There are currently no toll roads in Wisconsin. No segments within the state of Wisconsin should be marked as 'Toll Road'.
 
====Pedestrian Boardwalk, Walking Trail, Stairway====
These should not be mapped without approval from a State Manager for Wisconsin or the Regional Coordinator. These segment types can cause routing issues even when not connected to a drivable segment.
 
 
====Solid White Lines====
It is not illegal to cross a solid white line in the state of Wisconsin, unless posted [https://docs.legis.wisconsin.gov/statutes/statutes/346/II/13/3 Wisconsin Statute 346.13(3)].
<br>
[[File:Solid White Line Statute.png|thumbnail]]
Some examples are: road edge lines, lane divider lines, or on/off ramp lane lines.  Even though it is not illegal, it is a safe driving practice to not cross these lines.  When mapping on/off ramps, please follow national guidelines in the [[Junction Style Guide/Interchanges]] section.
<br>
[[File:White Line Off Ramp.png|Off Ramp Example]]
<br><br>
[[File:White Line On Ramp.png|On Ramp Example]]
<br><br>
There may be times when this is impractical, in such instances, contact a State Manager for further guidance.
 
====Roundabouts at Freeway Interchanges====
When there are roundabouts at freeway interchanges, leave the connecting overpass/underpass roads un-named.  Waze will read forward to the next roundabout and provide proper TTS and visual prompts for the user to aid in proper lane selection at multi-lane roundabouts.
<br>Here is an example of when '''not''' to name the segment(s): [https://www.waze.com/editor/?env=usa&lon=-88.08134&lat=44.52407&layers=2981&zoom=5&segments=66002890 Do Not Name] 
 
====U-Turns====
 
U-turns in Wisconsin are permitted when:{{ref label|1|1}}
 
# The u-turn can be made in safety and without interfering with other traffic.
# Not upon any curve, or upon the approach to or near the crest of a grade, where the vehicle cannot be seen by the driver of any other vehicle approaching from either direction within five hundred (500) feet.
# Not explicitly prohibited by signage or local municipal law.
# You are not required to back up during the course of the u-turn in order to complete it.
 
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.
 
U-Turns are '''not''' allowed on any Freeway or Expressway.
 
{{note|1|1}} [https://docs.legis.wisconsin.gov/statutes/statutes/346/V/33 Wisconsin Statute 346.33]
 
====Construction Zones====
 
If a construction zone is expected to last one week or longer, the following options are allowed to be made to the area:
*Change speed limit to lower posted limit
*Add crossovers for traffic changes and make one-way Freeway segments two-way.
 
If any or all of these changes are made, add the construction zone to the following spreadsheet for easy reference and followup by other editors.
[https://docs.google.com/spreadsheets/d/1cBXF25qeT1etuIZjzQSunZThmiUgzHh2hmFjlJ8-iLM/edit?usp=sharing WI Construction Zones]
 
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
-- Editors: To add yourself to this Other Editor Area table, copy and paste the
---- This page is only transcluded into (displayed on) the main page for this state.
-- following template into the space below with the other {{AM/Editor|...}}
---- It directly follows the common guidelines applicable to all states. When this
-- templates. Add yourself into rank order (higher at top)then alphabetical order
---- page is present (even if blanked), it displaces any optional code that might be
-- by user name (A-Z)
---- in that section.
-------------------------------------------------------------------------------------
---- If the original optional code from the main page for this section is still
{{AM/Editor|YOUR_USER_NAME|YOUR_RANK#|YOUR_AREA|ANY_COMMENT}}
---- desired, it can be restored by adding the following code to the first line
-------------------------------------------------------------------------------------
---- between the "DO NOT MODIFY" lines on this page:
-- then in the Summary field enter "Added YOUR_USER_NAME" and press "Save page"
----   {{:USA/CommonState/Major_roads|optional}}
-------------------------------------------------------------------------------------
----
---------------------- DO NOT MODIFY CONTENT ABOVE THE LINE -------------------------
--------------------------------------------------------------------------------->|-
{{AM/Editor|eaglestailg8ter|4|Mid Atlantic & New England|gho=Robert M|pic=File:Avatar_eaglestailg8ter.jpg|Live Philly Burbs, AM NW Missouri, E Kansas, SE Nebraska, KC Metro - Columbia|badge1=AM}}
{{AM/Editor|JB15TM|4|NY/NJ Metro Areas|NJ Native, Mid-Michigan AM Westchester NY AM|gho=John Beck|pic=File:JB15TM.png|badge1=AM}}
{{AM/Editor|Odessit68|4|All of Pennsylvania|badge1=SM|gho=Alex Dreyzin|pic=File:Odessit68.jpg}}
{{AM/Editor|cshinn89|3|Pike county PA, northern NJ, & Orange county NY|gho=Christopher|pic=File:Avatar me.jpg|Thailand RM. Pike County PA AM. Former NJ Resident and Currently living in PA|badge1=sm|badge2=am|badge3=mr}}
{{AM/Editor|FraggleLock|3|Atlantic, Gloucester|NC}}
{{AM/Editor|Jdelosa|3|Brooklyn, NYC Area Manager, RTC All NJ NY Crossings|NYC Closure Team|badge1=mr|badge2=AM|gho=jdelosa|pic=File:Avatar jdelosa.jpg}}
{{AM/Editor|NJMedic2535|3|Burlington, Mercer & Ocean Counties|gho=Greg Clopp}}
{{AM/Editor|Rfrsw101|3|NYC Metro Area & Long Island, NY and I-78/95 Corridor, NJ|AM-Long Island, RM-Thailand|gho=Rfrsw101|pic=File: Avatar Rfrsw101.png|badge1=AM|badge2=SM}}
{{AM/Editor|Choppr7|2|Kenilworth to Brick|Resident Exit 105 |gho=Jeremy}}
{{AM/Editor|Cubanitoforever|2|NJ/NY|HELPING TO BEAT TRAFFIC|gho=Manuel}}
{{AM/Editor|DavidDogSP|2|South Jersey - Mainly Atlantic & Ocean County|NJ Native - You can call me David or DDS|gho=David A}}
{{AM/Editor|halcy0n|2|North & Central NJ|Monmouth County resident|gho=Mark L}}
{{AM/Editor|JohnVSJ|2|South Jersey|Camden County}}
{{AM/Editor|nemodio|2|Brunswicks, Windsors, Jamesburg, Monroe, Helmetta, Spotswood|Middlesex County|gho=neeravmodi}}
{{AM/Editor|PicktownMapper|2|Bridgeton and Vineland (Other States OH,PA,IN,IL,WI)|Resident of Pickerington,OH|gho=Ian|pic=File:Picktownmapper.png|200px|thumb|left|alt text}}
{{AM/Editor|skbernard1|2|North & Central NJ|Morris County resident|gho=Sean B}}
{{AM/Editor|Swami07601|2|Bergen County|Hackensack resident}}
{{AM/Editor|Abecedarium|1|NYC + Northern NJ–Morris,Passaic,Bergen County|Exit 161 — Willing to learn! |gho=Abecedarium}}
{{AM/Editor|makadiwal|1|Toms River, Lakewood, Brick|Ocean County}}
{{AM/Editor|jreed|2|Camden, Gloucester, and Burlington (southern) Counties||gho=Jay}}
 
<!------------------------------------------------------------------------------
---------------------- DO NOT MODIFY CONTENT BELOW THE LINE -------------------------
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
---- If there will be a full page for this section, use code similar to the wording
---- below to provide a hyperlink to that page. When creating the full page, use the
---- link on the talk page to ensure the preload data is provided to help with
---- formatting the page. Don't just use the red link from this section once it is
---- saved.
----
See [[{{BasePage2}}/Major roads]] for guidance in {{RootPage2}} that may not be universal to all other states.
----
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
--></includeonly>
---- This section has three possible purposes:
---- 1. It is only providing a hyperlink to the full page for this section.
---- 2. It is only providing some unique guidance for this state that differs from
---- other states.
---- 3. It is intentionally wiping out the general optional content for this section
---- for this state.
------------------------------------------------------------------------------------>

Revision as of 01:25, 20 September 2016


Functional Classifications

Wisconsin follows the Functional Classification (FC) system for the USA.

To help update the current Wisconsin roadways to the new functional classifications, go to the Wisconsin Functional Classification Inventory.
Links to the FC maps for the state of Wisconsin can be found on the PesachZ/Resources page.


Minimum Road Lock Standard

Minimum Road Lock Standard
Segment Type Direction Level
 Freeway  5
 Ramp  HCS*
 Major Highway  3
 Minor Highway  3
 Primary Street  One-way 3
Two-way 2
 Street 
 Private Road 
One-way 2
Two-way 1
 |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|  2
 • • • • Ferry • • • •   2
 ⁃     ⁃        ⁃        ⁃        ⁃ Runway ⁃        ⁃        ⁃        ⁃        ⁃  5
Other Named Types 1
Segment Group Level
Construction Areas
(changes without aerial images)
3

Terms

  • HCS - Highest Connecting Segment
Additional Info
Expectations

We understand that higher locks mean there is less available to lower rank and beginning editors. We would like to emphasize that Waze Map Editing is a community activity and, within the US, it is not possible to increase to rank 3 or above without community involvement. It is the responsibility of all members of the editing community to actively reach out, recruit, and mentor new editors.

It is OK to temporarily lock segments below standards for more junior editors. Area Managers are encouraged to monitor their areas for non-standard locks and follow up with other editors on any discrepancies. As a courtesy, any down-locks made outside your area should be brought to the attention of the local area manager.

One-Way Streets

The +1 locks on one-way segments originated as guidance from GLR RC GizmoGuy411 based on trends found while performing Area Manager Reviews: He would encourage editors to +1-lock one-way street/PS in order to explicitly signal, "Yes, the legwork has been done in order to confirm this segment really is one-way, and it's not a soft-directional issue."


Name Normalization

Wisconsin will use the following standards for road naming:
Freeways - I-###
US Highways - US-###
State Highways - WIS-###
County Highways - CH-XXX
Forest Roads - FR-###

There are no Township (Town) Roads in the state. All Town Roads are named, and those names will be used. The only exceptions would be if the road signage states differently.



Bridge and Overpass Segmentation Elevation (BOSE)

Please note that there are regional and national discussions ongoing for establishing standards beyond state level. If those changes come in opposition to what we are doing here, then we will be changing to follow suit.

Wisconsin has decided on a state standard for the segmentation of bridges and overpasses.

The National Wiki contains the standard information regarding proper elevation of segments. What we are doing in Wisconsin is expanding on those standards to create a more accurate representation of the segments.

Basic elevation is determined using the following rules:

  • All roads start at Ground elevation
  • If a segment is above another segment, it should be set to +1 relative to the lower segment's elevation (to account for multiple segments overlapping)
  • If a segment is a tunnel (not just an underpass), it should be set at -1, and Tunnel should be checked.

Bridges
Definition:

  • If a segment travels over a river or body of water, it is considered a bridge
  • If a segment travels over another segment, it is considered it a bridge (aka: overpass).
  • If a segment is artificially elevated to pass over ground level objects and natural features, it is considered a bridge.

Junctioning:
Place a junction at the start/end of the bridge where the land falls away.

  • If there is already a junction within 500 feet of the bridge, do not add a new junction.
  • Do not junction a bridge if it is less than 75 feet in length. If you believe you need to do so, contact an SM or LAM for approval.

Ramps
Ramps should always be set to Ground. The only time a ramp segment is set above or below ground is when it travels above or below another segment as a bridge or a tunnel. This is most often the case in large interchanges, like the Marquette interchange in Milwaukee. When a ramp traverses over or under another segment, you should follow the elevation guidelines listed above.

Do not segment a ramp like you would for a bridge, unless it takes on several different elevations.

Because of the complexity of interchanges, please contact your State Manager before making adjustments.

Special Note

This process was derived from the Seagull Effect created by the Australians. The process has been unofficially called ‘seagulling’. Please note that this word is a misuse of the Seagull Effect. Using it may have unintended connotations.


Additional notes for this state

Dirt Roads

In Wisconsin all drivable roads that are unpaved are considered Dirt Road/4X4 Trail; this is how drivers expect the "Avoid Dirt Roads" feature to behave. Note that Functional Classification WILL override the Dirt Road type. Set those roads to their proper PS, mH, MH, FW type.

The new Dirt Road checkbox is NOT to be used at this time, as it is currently non-functional.

Toll Roads

There are currently no toll roads in Wisconsin. No segments within the state of Wisconsin should be marked as 'Toll Road'.

Pedestrian Boardwalk, Walking Trail, Stairway

These should not be mapped without approval from a State Manager for Wisconsin or the Regional Coordinator. These segment types can cause routing issues even when not connected to a drivable segment.


Solid White Lines

It is not illegal to cross a solid white line in the state of Wisconsin, unless posted Wisconsin Statute 346.13(3).

Some examples are: road edge lines, lane divider lines, or on/off ramp lane lines. Even though it is not illegal, it is a safe driving practice to not cross these lines. When mapping on/off ramps, please follow national guidelines in the Junction Style Guide/Interchanges section.
Off Ramp Example

On Ramp Example

There may be times when this is impractical, in such instances, contact a State Manager for further guidance.

Roundabouts at Freeway Interchanges

When there are roundabouts at freeway interchanges, leave the connecting overpass/underpass roads un-named. Waze will read forward to the next roundabout and provide proper TTS and visual prompts for the user to aid in proper lane selection at multi-lane roundabouts.
Here is an example of when not to name the segment(s): Do Not Name

U-Turns

U-turns in Wisconsin are permitted when:[1]

  1. The u-turn can be made in safety and without interfering with other traffic.
  2. Not upon any curve, or upon the approach to or near the crest of a grade, where the vehicle cannot be seen by the driver of any other vehicle approaching from either direction within five hundred (500) feet.
  3. Not explicitly prohibited by signage or local municipal law.
  4. You are not required to back up during the course of the u-turn in order to complete it.

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.

U-Turns are not allowed on any Freeway or Expressway.

^1 Wisconsin Statute 346.33

Construction Zones

If a construction zone is expected to last one week or longer, the following options are allowed to be made to the area:

  • Change speed limit to lower posted limit
  • Add crossovers for traffic changes and make one-way Freeway segments two-way.

If any or all of these changes are made, add the construction zone to the following spreadsheet for easy reference and followup by other editors. WI Construction Zones