User:PesachZ/SyncScratch View history

PesachZ
VisualWikitext
m (Copying text of wiki page for coparison with the "Basemap" page)
m (Copying text of wiki page for coparison with the "New York/Closures/Major" page)
 
(408 intermediate revisions by 5 users not shown)
Line 1: Line 1:
Waze map editors use the term basemap to refer to roads imported from external sources that have never been edited and for areas that contain them.
<!-- ========================
    ↓  EDITS TO THIS TABLE ARE MADE BELOW THE INSTRUCTIONS    ↓
==============================
This page is only viewed directly in the Major Events table on the Closures subpage.--><noinclude>[[Category:{{RootPage2}}]]
[{{fullurl:{{BasePage2}}/Closures|action{{=}}purge}} {{u|Click here to return to the {{RootPage2}}/Closures Subpage}}]<br/>


==Background==
These rows fill the major Event table, and are modified using the template {{tl|Event/Item}}. If you are working on a Major Event in {{RootPage2}}, please add add that event to this table. If the event is already listed, please add your username to the row, preceded by a pipe (|), and change the date to today's date in the <code>updated=</code> parameter.
A basemap (or base map) is a collection of reference data intended to provide visual orientation to users of a map, so that further details can be added and displayed on it in a meaningful way. It may include data on imagery, topography, roads, political boundaries or other things, depending on the purpose of the map. In many countries, Waze has licensed and imported data on roads and other features from various sources to serve as its basemap, and this is the foundation upon which users and map editors build to create a usable navigation system.


Depending on the data source used to import roads for each particular country, basemap roads require various updates from map editors in order to provide efficient navigation and useful display. This can involve confirming directions, turns, and names, adjusting geometry and connectivity, removing extraneous nodes and segments and setting road types, locks, elevations and other road attributes. Because they require specific cleanup from editors, and because they contain unique features relative to roads created and edited by users, map editors often refer to these unedited roads and areas that contain them simply as basemap.


==Basemap roads in the United States==
This template accepts many parameters which must be separated from each other using pipe characters (|), but can be placed in any order and will automatically  the correct parts of the table. To use a parameter you must keep the name of parameter (the part before the equals sign (=) identical to this list, and only modify what goes after the equals sign (=).
[[File:Basemap.jpg|right|350px]]
Waze imported [https://www.census.gov/geo/maps-data/data/tiger.html TIGER] data from the US Census Bureau to serve as its basemap in January, 2009. TIGER data provided somewhat accurate names, locations and cities/states for roads, but it did not include road directions, types, allowed turns, elevations, or any navigation history. Because this data was designed for location of people and places and not for navigation, it contained many odd angles and extraneous geometry and junction nodes when added to the Waze map.


The default road type for basemap roads is {{Street}}, but during and subsequent to importation, Waze ran automatic processes to assign road types based on names and other features. For example, most if not all roads with "I-xx" names (Interstate Highways) were first assigned as the type now called {{Major Highway}}, and later they were reassigned as {{Freeway}}. Other roads with variants of "highway" or "route" in their names were assigned as the type now called {{Minor Highway}}. Some roads were automatically assigned as {{Private Road}}, {{Dirt Road / 4X4 Trail|Unpaved}} or other types. None of these automatic road type changes were recorded as edits, so while most unedited basemap roads are {{Street|Streets}}, some of them have other types.
==Accepted parameters:==


Basemap roads in the USA have unknown direction and [[Soft and hard turns|soft restricted]] turns by default, but Waze is designed so that users add data to roads as they drive over them. When enough users drive over a road of unknown direction from node A to node B onto another segment, Waze will automatically set the direction to one way (A→B) and will set the turn from node B onto the other segment to soft enabled. If enough users drive from B to A on this same segment, Waze will then set the road to two way, but the turns will still be unconfirmed. These directions and turns remain guesses and are affected by various [[Routing penalties|routing penalties]] until set by an editor. Once a segment is edited and its turns are confirmed, penalties no longer apply to enabled turns, and any restricted turns and forbidden directions become absolute and will not be routed.
*<code>name=</code> The name of the event.
*<code>area=</code> The county or are the event takes place in.
*<code>date=</code> The estimated date(s) this event happens on.
*<code>road=</code> The main road(s) affected by this event.
*<code>pl=</code> A [[permalink]] to the affected road(s), or a link to documenting listing all the affected roads (usually a Waze event closure document).
*<code>source=</code> A link to an official information source for this event, a government website, the hosting organizations webpage, etc.
*<code>status=</code> Whether this event has been submitted to Waze yet for this season. It accepts the following options spelled only exactly as listed here in order to correctly change the color of the row, filled with anything else will display with a white background
**<code>not submitted</code> produces a red background
**<code>submitted</code> produces a light green background
**<code>in progress</code> produces an orange background.
*Up to six editors can be listed in the table for any event. These can be the editors who are working to get it submitted, maintain the segments, or just have special knowledge of the event/area. They are entered as unnamed parameters. Meaning they are to be entered between two pipe (|) characters of the adjacent parameters. Each editors name (without any spaces) should be separated with a pipe (|).
*<code>updated=</code> the date this event was last updated in this table. This is used to keep the table current, and identify stale entries.


==Identifying unedited basemap roads==
[[File:Basemap2.jpg|right|350px]]
Basemap areas are usually found where there are few GPS tracks. A lack of GPS tracks over roads could mean that there are not many Wazers driving there, that cellular data coverage is weak or even that the roads on the map are not drivable or do not exist. Whatever the reason, lack of GPS tracks is a good clue that unedited basemap roads are nearby, waiting to be edited.


It's easy to tell when the basemap roads were imported into an area, because most road segments will have the same creation date. If a road segment has that created date but ''does not have an updated date'' listed in its information, it is an unedited basemap road that needs to be updated. Additionally, features like unknown direction, unconfirmed turns, odd angles, excess nodes and segments that don't match imagery are clues that a road has not been edited much from its basemap state, even if it has been updated by someone.
The updated parameter (<code>|updated=YY/MM(/DD)|</code>) should be updated any time you update a row. Put the date you are modifying the row after the equals sign (=).  


== Editing basemap roads ==
The general information on [[Creating and editing road segments]] applies to editing basemap roads, but basemap roads have some unique features to look out for. Because of these features editors must be careful and thorough. Doing an incomplete job, such as only fixing geometry or deleting junction nodes, can turn a patch of roads from somewhat functional but clearly needing work to looking better but not working at all. This is because when a segment is edited, its direction is automatically confirmed, and when a turn is edited on the end node of a segment, the other turns from that node are automatically confirmed. Subsequent traffic cannot change confirmed (or "hard") turns and directions. More importantly, <u>updated roads with one way direction will not be routed in the opposite direction, and any remaining hard disabled turns at a node, even if hidden by unknown or one way direction, will not be routed at all</u>.


Here is a detailed procedure to follow when editing basemap roads:
The <code>|date=|</code>, and <code>|updated=|</code> parameters should use the format YY/MM/DD. The day of the month is optional. Using this format will make it easier to sort the list by updated date. This will help ensure the information on the list is current, and make it easy to find stale rows which may need to be adopted by other editors.
# '''Delete unnecessary road segments.''' Some basemap roads represent [[Driveways|driveways]], [[Walking trails|walking trails]], fences, waterways or nothing discernible at all. With few exceptions these should be removed from the map. Deleting these provides a more accurate map, better navigation and less work for editors.
# '''Adjust the connectivity.''' Oftentimes basemap roads will not connect where satellite imagery shows they should. They should be connected to provide proper routing. Any [[Junction Style Guide#Two-segment loops|one-segment or two-segment loops]] should be fixed. Conversely, improper connections such as those off bridges and through barriers should be fixed too. Use the [[Overpasses, Underpasses and Bridges|bridge tool]] to fix any bridges and disconnect any other roads where a junction is not passable.
# '''Delete unnecessary junction nodes.''' This allows Waze to use less resources when calculating routes and to give more accurate arrival times.
# '''Set the direction.''' If the direction of a road is unknown or one way, [[Determining one-way streets|determine what direction the road should be]] and set it. Remember that once you edit a one-way segment, even if you don't change the direction, Waze will consider its direction confirmed and will not route traffic in the opposite direction.
# '''Set the turns.''' Hidden turns are revealed after the direction has been set. [[Soft and hard turns|Confirm the turns]]; keyboard shortcuts such as Shift+Z to reveal restricted turns and Q+W on a node to allow all turns can help with this. Only allow U-turns where permitted by law.
# '''Confirm the name, city and state.''' Many roads are not within a city, particularly in rural areas, and some are not named either. Check the "none" box next to city and/or name in these cases. The [[Road names/USA|road names page]] and [[Using external sources|approved sources]] can help determine names, and the local wiki for the area in which you are editing may give further guidance on how roads are assigned to cities. Even in the middle of one state, basemap roads may erroneously be listed in a different state. This should be corrected. Check local GIS or other approved sources for help in determining city limits and state lines.
# '''Adjust the geometry.''' Most basemap roads will have excess geometry nodes that should be removed to make the map easier to maintain. Most basemap roads will also not be aligned very well with satellite imagery. Where the imagery is accurate, they should be adjusted to match it. Geonodes should also be adjusted around intersections to provide [[How Waze determines turn / keep / exit maneuvers|proper turn instructions]].
# '''Set the road type.''' Most basemap roads have the {{Street}} type, but the type may need to be changed to {{Dirt Road / 4X4 Trail|Unpaved}}, {{Private Road}} or something else. Satellite imagery can often determine whether a road is paved or not; see [[Road types/USA|road types]] for more information.
# '''Set the elevation.''' The default is ground, but bridges and tunnels should have negative or positive [[Creating and editing road segments#Road elevation|elevations]]. If the [[Overpasses, Underpasses and Bridges|bridge tool]] was used, make sure that elevations are not unnecessarily high.
# '''Set other road attributes.''' If a road has not been edited by anyone in Waze, it is unlikely that Google has street view to show speed limit signs, but it's good to check. Sometimes default [[Speed limits/USA|speed limits]] can be added based on applicable laws. Depending on road type, a [[Map protection|lock]] may also be warranted.


Basemap editing can be done well without [[Scripts|user scripts]], but for those who choose to use them, [[Scripts/WME_Toolbox|WME Toolbox]], [[Scripts/WME_Validator|WME Validator]] and [[Scripts/WME_Color_Highlights|WME Color Highlights]] are particularly helpful in pointing out potential problems in basemap.
 
For example an Event row should look like this;
 
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username|updated{{=}}14/08}}
 
 
If there are multiple editors it should look like this
 
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username1|username2|updated{{=}}14/08}}
 
 
 
'''Whenever you edit this table, please be sure to include the name of the event you are editing in the summary field under the edit box.'''
————————————————————————————————————
 
 
 
''The actual contents of this page '''will only be visible''' in the [[{{BasePage2 }}/Closures|Major Events table]], or when editing this page.''
 
==TO EDIT THIS TABLE CLICK HERE >> ==
</noinclude><includeonly><!--
------ DO NOT MODIFY ABOVE THIS LINE -----
======                              ======
======                              ======
======                              ======
====== DO NOT MODIFY ABOVE THIS LINE ====-->
{{Event/Item|name=New Years Celebration|area=NYC|road=Times Sq/Coney Island|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1716991474|date=12/31-01/01 annual|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/08}}
 
{{Event/Item|name=NYC 1/2 Marathon & St. Patricks' Day Parade|date=03 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=339510355|area=NYC|road=5 Boroughs|status=submitted|updated=2017/02/09|Rfrsw101|jdelosa|johnsninja58|PesachZ}}
 
{{Event/Item|name=July 4th Celebration|area=NYC|status=submitted|updated=2017/02/12|Rfrsw101|jdelosa|johnsninja58|PesachZ|road=FDR Dr|date=07/04 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1864894199|source=http://www.nyc.gov/html/dot/html/motorist/wkndtraf.shtml}}
 
{{Event/Item|name=Summer Streets|road=Park Ave|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1984749524|source=http://www.nyc.gov/html/dot/summerstreets/html/home/home.shtml|date=08 First 3 Sundays|area=NYC|status=submitted|updated=2017/02/10|Rfrsw101|jdelosa|johnsninja58|PesachZ}}
 
{{Event/Item|name=West Indian Day Parade|date=09 Labor Day annual|area=Kings|road=Eastern Pkwy, Classon-Rochester St Johns-Empire|source=http://maps.nyc.gov/streetclosure/|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1605830763|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/10}}
 
{{Event/Item|name=TD 5 Boro Bike Tour|area=NYC|date=05 First Sunday annual|road=5 Boroughs|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=790135118|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/08}}
 
{{Event/Item|name=NYC TCS Marathon|area=NYC|date=11 First Weekend annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=0|road=5 Boroughs|source=http://www.tcsnycmarathon.org/race-day/course|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/07}}
 
{{Event/Item|name=UN General Assembly|area=NYC|road=East Midtown|date=09 Last Two Weeks Annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1895099030|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/08}}
 
{{Event/Item|name=Macy's Thanksgiving Day Parade|area=NYC|road=Herald Square|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1774745119|date=11 Last Thursday Annual|source=http://social.macys.com/parade/#route|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/08}}
 
{{Event/Item|name=Chinese New Year Parades|date=01 or 02 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1190958434|area=NYC|road=Chinatown/8th Avenue/Flushing|status=submitted|updated=2017/02/08|Rfrsw101|jdelosa|johnsninja58|PesachZ}}
<!--- DO NOT MODIFY BELOW THIS LINE ------=====                                =====
=====                                =====
=====                                =====
----- DO NOT MODIFY BELOW THIS LINE ----->
</includeonly>

Latest revision as of 05:15, 19 February 2017

Click here to return to the PesachZ/Closures Subpage

These rows fill the major Event table, and are modified using the template {{Event/Item}}. If you are working on a Major Event in PesachZ, please add add that event to this table. If the event is already listed, please add your username to the row, preceded by a pipe (|), and change the date to today's date in the updated= parameter.


This template accepts many parameters which must be separated from each other using pipe characters (|), but can be placed in any order and will automatically the correct parts of the table. To use a parameter you must keep the name of parameter (the part before the equals sign (=) identical to this list, and only modify what goes after the equals sign (=).

Accepted parameters:

  • name= The name of the event.
  • area= The county or are the event takes place in.
  • date= The estimated date(s) this event happens on.
  • road= The main road(s) affected by this event.
  • pl= A permalink to the affected road(s), or a link to documenting listing all the affected roads (usually a Waze event closure document).
  • source= A link to an official information source for this event, a government website, the hosting organizations webpage, etc.
  • status= Whether this event has been submitted to Waze yet for this season. It accepts the following options spelled only exactly as listed here in order to correctly change the color of the row, filled with anything else will display with a white background
    • not submitted produces a red background
    • submitted produces a light green background
    • in progress produces an orange background.
  • Up to six editors can be listed in the table for any event. These can be the editors who are working to get it submitted, maintain the segments, or just have special knowledge of the event/area. They are entered as unnamed parameters. Meaning they are to be entered between two pipe (|) characters of the adjacent parameters. Each editors name (without any spaces) should be separated with a pipe (|).
  • updated= the date this event was last updated in this table. This is used to keep the table current, and identify stale entries.


The updated parameter (|updated=YY/MM(/DD)|) should be updated any time you update a row. Put the date you are modifying the row after the equals sign (=).


The |date=|, and |updated=| parameters should use the format YY/MM/DD. The day of the month is optional. Using this format will make it easier to sort the list by updated date. This will help ensure the information on the list is current, and make it easy to find stale rows which may need to be adopted by other editors.


For example an Event row should look like this;

{{Event/Item|date=14/10|in progress|username|updated=14/08}}


If there are multiple editors it should look like this

{{Event/Item|date=14/10|in progress|username1|username2|updated=14/08}}


Whenever you edit this table, please be sure to include the name of the event you are editing in the summary field under the edit box. ————————————————————————————————————


The actual contents of this page will only be visible in the Major Events table, or when editing this page.

TO EDIT THIS TABLE CLICK HERE >>

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