The new Waze Wiki, aka Wazeopedia, is now live at Wazeopedia.waze.com! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.

Please do not make any more updates to these legacy wiki pages, all future updates should be made in your country's local Wazeopedia.

Clock over a larger globe

Difference between revisions of "Texas/Mapraid"

From waze
Jump to: navigation, search
(Recommended Tools for Houston: Correcting MapRaid overlay link and title)
 
(118 intermediate revisions by 13 users not shown)
Line 1: Line 1:
{{mbox|image=[[File:clock.png|40px]]|text='''MapRaid! Houston,Texas''' will begin on '''2015-01-11, Sunday. 19:00 UTC'''. The raid will last for roughly 7 days.}}
+
{{USRedirect}}
{{Mbox|image=[[File:Application clipboard.png|40px]]|text='''''To join MapRaid! Houston, TX please fill out [http://docs.google.com/forms/d/1Jl_GzKZ58j_FhNNy8MIYt1_7sLOQWqBGINe_V_hiAnM/viewform this form].'''''}}
+
 
 +
{{mbox|image=[[File:clock.png|40px]]
 +
|text='''MapRaid!Dallas,Texas''' {{#ifexpr:{{#time:xNU|2015-02-13T0000}}>{{#time:xNU|}}<!-- check if raid started yet-->
 +
|will begin on '''2015-02-13, Friday. 00:00 UTC'''. The raid will last for roughly 7 days.<br>{{red|'''Please do not make any edits in the raid area until after the raid begins (00:00 UTC)}}<!--text to show before raid starts-->
 +
|has begun on '''2015-02-13, Friday. 00:00 UTC'''. The raid will last for roughly 7 days.}}<!--text to show after raid starts-->}}
 +
{{Mbox|image=[[File:Application clipboard.png|40px]]|text={{#ifexpr:{{#time:xNU|2015-01-22T0500}}>{{#time:xNU|}}|'''Registration is now open for MapRaid! DFW. If you would like to participate please fill out [http://docs.google.com/forms/d/1G2cjP6yySf-6koq5U8QK6oz2fzATbXQL26HNHFqGuOw/viewform this form] before 2015-01-21 05:00 UTC.'''|Registration for the MapRaid! is now closed. To hear about future MapRaids please join the [http://wazemapraid.slack.com MapRaid ''#''Slack].}}}}
 
{{mbox
 
{{mbox
 
| type      = critical
 
| type      = critical
| textstyle  = color: red; font-weight: bold; font-style: italic;
+
| text      = {{red|'''''Please be sure to explore this Wiki page, and <!--
| text      = Please be sure to explore the Wiki page. Also, check back regularly in case of added materials.<br>You are only seeing modifications of this page made up until {{#time:D, j M Y H:i:s T}}, make sure to log in to the wiki to see the latest updates.
+
----------------------------
 +
REMOVED because page is now transcluded to bottom of this page
 +
[[Texas/Mapraid/15-01-Houston|the specific page for the Houston Jan '15 raid]]. Also,
 +
------------------------------> check back regularly in case of added materials.'''''}}<br>'''You are only seeing modifications of this page made up until {{#time:D, j M Y H:i:s T}}, make sure to {{U|log in to the wiki}} to see the latest updates.'''
 
}}
 
}}
 
+
<!-- After changing the link in the box above to point to a new MapRaid! page, delete this comment line so the following is left on the page:
 
+
''To see the results, and other information specific to MapRaid in Houston during Jan 2015, see the [[Texas/Mapraid/15-01-Houston|archived page]].''
 +
-->
 
==Welcome to Texas!==
 
==Welcome to Texas!==
  
 
== Mission ==
 
== Mission ==
  
Our primary mission will be to handle the URs, and PURs, followed by Place validation, and general map verification.  
+
Our primary mission is to fix what is broken as well as fine tune what is already working. This will be handled through a variety of ways:
 +
* Handling URs and MPs
 +
* Fixing streets (correcting elevation, turns, extra nodes, alternate names, etc)
 +
* Routing corrections (usually found in URs or by randomly attempting to route between points and looking for irregularities)
 +
* FC errors (but do not downgrade without getting local guidance! See FC warning immediately below.)
 +
 
 +
<!-- '''PURs, followed by Place validation, are being handled EXCLUSIVELY by Team 10, please refer all places updates to them.'''  -->
 
{{mbox
 
{{mbox
 
| type      = critical
 
| type      = critical
 
| small      = left
 
| small      = left
 
| textstyle  = color: red; font-weight: bold; font-style: italic;
 
| textstyle  = color: red; font-weight: bold; font-style: italic;
| text      = Functional Classification (FC) has been fully implemented for the LA area. Some road types deviate intentionally from the state DOTs classifications. If you find a road which you feel is not classified correctly or set to the right type, please contact a local champ or State Manager (SM) before making changes.
+
| text      = Functional Classification (FC) has been fully implemented for the MAPRAID area. Some road types may deviate intentionally from the state DOTs classifications. Please consider contacting a local champ or State Manager (SM) before downgrading a road type.
 
| smalltext  = Text for the top of article sections.
 
| smalltext  = Text for the top of article sections.
 
}}
 
}}
Line 25: Line 40:
 
{{Username|txemt}} - South Central Regional Coordinator  - available
 
{{Username|txemt}} - South Central Regional Coordinator  - available
  
{{Username|jasonh300}} -South Central Regional Coordinator-  
+
<!-- {{Username|jasonh300}} -South Central Regional Coordinator- removed pending response form editor if he wishes to participate -->
  
 
{{Username|driving79}} -Southeast Regional Coordinator-  
 
{{Username|driving79}} -Southeast Regional Coordinator-  
  
{{Username|pjlasl}} - US Champ, US CM, Texas SM -  
+
{{Username|pjlasl}} - US Champ, US CM, Texas SM - ''Currently Unavailable''
  
 
{{Username|ctpoole}} - Texas SM
 
{{Username|ctpoole}} - Texas SM
  
{{Username|karlcr9911}} - Texas SM - available after the 7th
+
{{Username|karlcr9911}} - Texas SM
  
 
{{Username|jakflash}} - Houston area editor
 
{{Username|jakflash}} - Houston area editor
  
 
{{Username|coontex}} - Houston area editor
 
{{Username|coontex}} - Houston area editor
 
{{Username|jakflash}} - Houston area editor
 
  
 
==Important!==
 
==Important!==
'''Please do not alter any of the following road ''types'' without first consulting a [[#Local Hosts | Local Host]]''':  Freeway, Ramp, Major Highway, minor Highway, Primary Street.
+
'''Please do not alter any of the following road ''types'' without first consulting a [[#Local Hosts | Local Host]] (unless changes are being made to match Functional Classification (FC))''':  Freeway, Ramp, Major Highway, minor Highway, Primary Street. You may edit these roads, but do not change the type of the segment (excluding FC work).  Confirmation should be obtained before making changes to any of these road types that go '''''against''''' FC.
  
'''Please do not mass-edit''' Do not perform edits which will affect large numbers of segments at once. The edit history of segments is highly valuable in the process of solving URs. Mass editing effectively mass erases this history, permanently. We ask that all necessary processes which might affect large portions of the map, or long stretches of roads, be reserved until near the end of the MapRaid. This includes the “Select entire street” function.
+
'''Please do not mass-edit''' Do not perform edits which will affect large numbers of segments at once. The edit history of segments is highly valuable in the process of solving URs. Mass editing effectively mass erases this history, permanently. We ask that all necessary processes which might affect large portions of the map, or long stretches of roads, be reserved until near the end of the MapRaid. This includes the “Select entire street” function. To facilitate this process in an orderly fashion, we have the [[#Scheduled Edits|Scheduled Edits list]] below. Please document any mass edits which are required, and you will be given first chance to make those edits when the time is right.
  
'''Anything locked at 5 or 6?''' Please check with a local editor before making changes. Rank 5 and 6 editors - consider keeping highlights active for locks 5 and 6.
+
'''Anything locked at 5 or 6?''' Please check with a local editor before making changes.<br />
 +
If you are a rank 5 or 6 editor - consider keeping highlights active for locks 5 and 6.
  
'''Close nodes''' We make extensive use of the "micro-dogleg" technique, where a geometry node is carefully placed, at full zoom, directly next to a junction node, in order to set the angle to create a desired Turn/Stay/Exit prompt. Please watch for these if you move any junction node, and be sure to recreate the same angle at the new location.
+
'''Close nodes''' We make extensive use of the "[[Glossary#mDL | micro-dogleg]]" technique, where a geometry node is carefully placed, at full zoom, directly next to a junction node, in order to set the angle to create a desired Turn/Stay/Exit prompt. Please watch for these if you move any junction node, and be sure to recreate the same angle at the new location.
  
 
==Local Guidance==
 
==Local Guidance==
Line 54: Line 68:
 
===Functional Classification===
 
===Functional Classification===
  
In the United States, we set our road types using a national standard called Functional Classification (FC). You can read a detailed explanation in our [http://wiki.waze.com/wiki/Road_types/USA#Functional_classification Road Type Wiki]
+
'''Functional Class''': [http://www.txdot.gov/apps/statewide_mapping/StatewidePlanningMap.html TxDot Functional Class] Look for FC along the right hand side.
  
The Functional Classification has been completed in the Houston Area. Occasionally, we find short segments that were missed in the selection process for conversion, and it is important that these be corrected for routing continuity. In general, however, we ask that Road Types not be changed without consulting one of the [[#Local Hosts | Local Hosts]]. In isolated cases, we have chosen to deviate from official classifications, due to errors or outdated information in the TxDot FC maps, or to better accommodate real-life situations and Waze quirks. It is important that these remain intact. Sometimes dirt roads may appear higher on FC maps but shouldn't be used by Waze for routing.
+
In the United States, we set our road types using a national standard called Functional Classification (FC). You can read a detailed explanation in our [[Road_types/USA#Functional_classification|Road Type Wiki]]
 +
 
 +
The Functional Classification has been completed in the DFW Area. Occasionally, we find short segments that were missed in the selection process for conversion, and it is important that these be corrected for routing continuity. If you see FC wrong, please correct it if you're 100% sure it's wrong. If you're not sure, please ask a local, karlcr9911, or txemt. In isolated cases, we have chosen to deviate from official classifications, due to errors or outdated information in the TxDot FC maps, or to better accommodate real-life situations and Waze quirks. It is important that these remain intact. Sometimes dirt roads may appear higher on FC maps but shouldn't be used by Waze for routing.
  
 
If you find an area that doesn't seem to be complete please bring it to the attention of a Local Host for review.  
 
If you find an area that doesn't seem to be complete please bring it to the attention of a Local Host for review.  
  
We observe the following minimum lock levels for Waze road types:
+
'''TxDot functional classification classifies roads as'''
 +
*An Interstate, Principal Arterial Freeway & Expressway is a {{Freeway}}
 +
*Any road that acts, looks, & feels like a freeway should be set to {{Freeway}} road type.
 +
*An Principal Arterial-Other is a {{Major Highway}}
 +
*An Minor Arterial is a {{Minor Highway}}
 +
*An Collector is a {{Primary Street}}
 +
*All other roads are to be classified as {{Street}}
  
{{Freeway}} - 5
+
=== Locking Standard ===
 +
{{Lock Standard State|TX}}
  
{{Ramp}} - locked to the level of the main road it is for
+
===Elevation===
 +
In general, all freeways should have an elevation of ground.  Roads running over or under the freeways will have an elevation of +1 or -1.  Where two freeways cross, the overpass should generally have +1 elevation. More complicated junctions may need more complicated treatment; apply the principal of "freeway defines ground level whenever possible" and keep elevations as sensible as possible. Remember that this region is not very hilly.
  
{{Major Highway}} (MH) - 4 - In some dense metropolitan areas, the minimum lock for MH can be 5
+
===UR & MP Guidance===
 +
<!--------------------------- old text from LA
 +
As the MapRaid Texas begins, the greater Houston area has over 6,000 open Update Requests (URs) and over 500 Map Problems (MPs); some of the URs are older than 300 days. Investigating and responding to these URs and MPs will be a primary objective of the MapRaid teams. Therefore, a [[California/Map_Raid_LA/UR_Guidance|UR Guidance]] page has been created to help guide teams through the maze of MPs and URs.<br />
 +
--------------------------------------->
  
{{minor Highway}} (mH) - 3  - In some dense metropolitan areas, the minimum lock for mH can be 4
+
Responding to Update Requests (URs), and Map Problems (MPs) will be the primary focus of the MapRaid teams. Please make sure to follow the guidance on dealing with URs and MPs as they are clearly explained in the [[UR|UR wiki page]]. Be especially careful to always leave a comment when closing a UR to explain why you are closing it, or how you fixed it. ''If there is no problem with the map to fix, don't mark it as solved, mark is Not Identified".''<br />
 +
'''Our only variation for the MapRaid from the [[UR|general guidance on handling URs]], is that we are reducing the 7 day wait periods to 3 days.''' You still must comment and wait 3 days, then comment again before closing a UR as "Not Identified". If you are able to fully diagnose and fix the problem, then comment what the fix was, and close it as "Solved".
  
{{Primary Street}} (PS) - 2
+
'''We should not be sending ''reminder'' comments after the 3 days.''' We send one comment asking for info, if there is no response after 3 days, close the UR. Please try to solve the UR, if that's not possible mark it as ''Not Identified''. ''(We should still be sending a closing comment before closing, and it's OK to send follow up comments if you need additional information after the first response.)''
  
{{Street}} - 1, or as needed
+
As per [[Texas#User Reports (URs)|Texas UR policy]] please keep UR response comments to a minimum, short and to the point. Aim for not more than 3-4 lines total. The [[#Recommended Tools|UrComments script (link below)]] already has a long list of canned UR responses which have been vetted by a group of senior editors.
  
Note that these are minimums and, for protection, certain segments may be at higher lock levels. If you find a road locked to a higher level than its minimum, please leave it locked no lower than that level when you have finished editing.
+
<!--#####This box will only appear on the page after 2015-02-15 23:00 UTC
 +
-->{{#ifexpr:{{#time:xNU|2015-02-15T2300}}<{{#time:xNU|}}|{{mbox
 +
| textstyle  = color: black; font-weight: bold;
 +
| text      = As we have now reached 3 days since the beginning of the Raid, and URs are being closed, please double check that the UR you are closing still is not/cannot be solved. Sometimes a question has been left for verification, and a map correction delayed, pending a response/no response. Please make sure to attempt to fix or get help if need before closing any UR.
  
'''TxDot functional classification classifies roads as'''
+
Also, DO always leave a closing comment; no UR should be closed without one.
*An Urban Interstate, Urban Principal Arterial Freeway & Expressway is a {{Freeway}}
+
}} }}
*Any road that acts, looks, & feels like a freeway should be set to {{Freeway}} road type.
+
*An Urban Principal Arterial-Other is a {{Major Highway}}
+
*An Urban Minor Arterial is a {{Minor Highway}}
+
*An Urban Collector is a {{Primary Street}}
+
*All other roads are to be classified as {{Street}}
+
  
 
===Place Editing===
 
===Place Editing===
 
+
<!-- {{mbox|type=critical|text='''{{red|NOTE:}} All Places edits should be handled EXCLUSIVELY by [http://wazemapraid.slack.com/messages/-mr_hou_team10/ Team 10 - PURs, Waze Sheets].'''}} -->
Not only were our URs and PURs out of control, places from both editors and trusted users have become a major issue. Misspelled names, wrong categories, missing addresses (EVERY business place should have an address!!) poor location and incorrectly assigned photos are all over the map. Use the powerful Place Browser (link below) and the information on the [[California/Places | '''Place editing''']] page to get these places corrected.
+
Not only were our URs and PURs out of control, Places from both editors and trusted users have become a major issue. Misspelled names, wrong categories, missing addresses ''(EVERY business place should have an address!!)'', poor location, and incorrectly assigned photos are all over the map. Use the powerful [[#Recommended Tools|Place Browser (link below)]] and the information on the [[Texas#When_to_use_Area_or_Point_in_Texas|'''Place editing''']] section of the Texas page to get these places corrected.
  
 
Please use good judgement when approving photos. Any photo which has nothing to do with the actual place, reject. This is including, but not limited to body parts, car parts, bathrooms, children, & animals. If you're not sure, please ask one of the senior editors.  
 
Please use good judgement when approving photos. Any photo which has nothing to do with the actual place, reject. This is including, but not limited to body parts, car parts, bathrooms, children, & animals. If you're not sure, please ask one of the senior editors.  
  
 
'''Gas Stations'''<br>
 
'''Gas Stations'''<br>
Gas Stations should be locked to level 3 but, only after all data fields in the gas station have been filled. At least ensure that Brand, Name and Address have information. Remember to ask a hosting local if you need help identifying gas station information.
+
Gas Stations should be locked to level 3 but, only after all data fields in the gas station have been filled. At least ensure that Brand, Name and Address have information. Remember to ask a [[#Local Hosts|local host]] if you need help identifying gas station information.
 +
 
 +
For editors below rank 3, once you have completely filled out a gas station with the minimum required information, please lock to your level and then ask for a lock request.
 +
 
 +
Finally, DO NOT USE THE BRAND "UNBRANDED". If it is a no brand gas station, just leave the brand field blank.
  
For editors below rank 3, once you have completely filled out a gas station with the min required information, please ask for a lock request.
+
'''Locking Standard'''
 +
*Lock at rank 5: hospitals, universities, park and ride lots, arenas, airports.
 +
*Lock at 3: any other place that has at least a correct category correct name, and correct address with house number..
 +
*If you cannot lock high enough because of rank, lock as high as you can, and get help from a higher-ranked editor to lock properly.  You can keep a personal list of [[Permalink]]s to share with the other editor.
  
===Toll Roads / HOV / HOT / Truck Lanes===
+
===Toll Roads / HOV / HOT===
  
 
It is our custom to mark the toll checkbox  on the entire sections of Toll Roads to include those ramps which are tolled. HOV and HOT road types have already been set correctly according to our local practices. If you have a question about one of these lanes, please contact a [[#Local Hosts | Local Host]].
 
It is our custom to mark the toll checkbox  on the entire sections of Toll Roads to include those ramps which are tolled. HOV and HOT road types have already been set correctly according to our local practices. If you have a question about one of these lanes, please contact a [[#Local Hosts | Local Host]].
Line 101: Line 134:
 
===Construction===
 
===Construction===
  
Houston has been under construction over the last 40 years. There are a number of major construction projects in process within the overall MapRaid area. These construction projects can cause frequent intermittent road closures. Many closures change daily and cause great numbers of URs to appear. When handling URs in one of these areas, be aware that reports of "Turn not allowed", "Missing road", "Wrong driving direction" are common, but may not indicate a map problem that can be fixed, because the physical road situation will change before our edits can take effect.
+
DFW Is going through an explosion of neighborhoods and new subdivisions. There may be some of these which are not on the editor, so if you see a missing road, see if there is an actual neighborhood by turning on the GPS tracks. There are a number of major construction projects in process within the overall MapRaid area. These construction projects can cause frequent intermittent road closures. Many closures change daily and cause great numbers of URs to appear. When handling URs in one of these areas, be aware that reports of "Turn not allowed", "Missing road", "Wrong driving direction" are common, but may not indicate a map problem that can be fixed, because the physical road situation will change before our edits can take effect.
  
 
LINKS:
 
LINKS:
Line 107: Line 140:
 
[http://drivetexas.org Texas driving conditions and road construction]
 
[http://drivetexas.org Texas driving conditions and road construction]
  
[http://www.txdot.gov/inside-txdot/projects/studies/houston.html Houston area road construction]
+
<!-- [http://www.txdot.gov/inside-txdot/projects/studies/houston.html Houston area road construction]
  
 
[http://www.i69texasalliance.com/ I-69] US-59 is being converted to interstate standards to become I-69. They have officially designated US-59 as I-69 through most of the Houston area already, but TxDot has been slow to make the changes on the signs. If there are any URs about US-59 not being I-69, simply explain TxDot has been slow to make changes. There are many maps which have already shown the changes through the area.
 
[http://www.i69texasalliance.com/ I-69] US-59 is being converted to interstate standards to become I-69. They have officially designated US-59 as I-69 through most of the Houston area already, but TxDot has been slow to make the changes on the signs. If there are any URs about US-59 not being I-69, simply explain TxDot has been slow to make changes. There are many maps which have already shown the changes through the area.
 +
-->
  
 
===U-turns===
 
===U-turns===
  
  
In Texas, U-turns are generally allowed unless unsafe, or specifically denied by signage. In general we can confirm, lock or "harden" U-turns (click to remove the Purple question mark indicating a soft turn -- see [[Turn_restrictions#Turn_restrictions|the Wiki]]) on residential streets, but please avoid confirming them on major streets.
+
In Texas, U-turns are generally allowed unless unsafe, or specifically denied by signage. In general we can confirm, lock or "harden" U-turns (click to remove the Purple question mark indicating a soft turn -- see [[Turn_restrictions#Turn_restrictions|the Wiki]]). U-turns are not named unless there as an official sign. All U-turns along freeways are normally named "Turnaround."
  
 
===Alleys===
 
===Alleys===
  
Alleys are '''not mapped''' in the State of Texas
+
Alleys are '''not mapped''' in the State of Texas and '''should be deleted'''.  This has been confirmed per txemt.
  
===UR & MP Guidance===
+
===Private Roads===
As the MapRaid Texas begins, the greaterHouston area has over 6,000 open Update Requests (URs) and over 500 Map Problems (MPs); some of the URs are older than 300 days. Investigating and responding to these URs and MPs will be a primary objective of the MapRaid teams. Therefore, a [[California/Map_Raid_LA/UR_Guidance|UR Guidance]] page has been created to help guide teams through the maze of MPs and URs.<br />
+
Private roads are used only for specific purposes. Before creating new private roads or working with existing private roads, please consult txemt.
 
+
{{mbox
+
| small      = left
+
| textstyle  = color: black; font-weight: bold;
+
| text      = As we have now reached 7 days from the beginning of the Raid, and URs are being closed, please double check that the UR you are closing still is not/cannot be solved. Sometimes a question has been left for verification, and a map correction delayed, pending a response/no response.
+
 
+
Also, DO always leave a closing comment; no UR should be closed without one.
+
| smalltext  = Text for the top of article sections.
+
}}
+
  
 
===Cameras===
 
===Cameras===
Line 136: Line 161:
 
'''Speed Cameras''' are illegal to use in the State of Texas
 
'''Speed Cameras''' are illegal to use in the State of Texas
  
Red light cameras are illegal to use in the City of Houston, however that does not apply to the various suburbs in the area.
+
'''Red light cameras''' Are used in various places -- check for information for each municipality.<br />
Following is a list of Cities known to currently use '''Red Light Cameras''':
+
For a list of DFW cameras, please click here: [[#Cameras_2 | DFW Cameras]]
*Baytown
+
*Humble
+
*Jersey Village
+
*Lake Jackson
+
*Sugar Land
+
  
 
==Mapping Resources==
 
==Mapping Resources==
 +
'''Functional Class''': [http://www.txdot.gov/apps/statewide_mapping/StatewidePlanningMap.html TxDot Functional Class]
  
:[http://www.txdot.gov/apps/statewide_mapping/StatewidePlanningMap.html TxDot Functional Class]
+
== Communication ==
 +
Communication will be handled primarily in ''#''Slack Channels and WME chat can also be used. The [http://www.waze.com/forum/viewtopic.php?f=819&t=95038 WME Chat addon] is recommended.
 +
Special Slack channels will be set up and named by raid location and group. {{U|Please be sure to join the slack WazeMapRaid Team and join the channels for the specific MapRaid and group you are assigned to.}}
  
:[http://mycity.houstontx.gov/home/MyCityMapViewer.html?sid=1Houston GIS]
+
'''Click here to get your [http://bit.ly/GetWazeSlackInvite Slack invitation]. Be sure to choose {{u|WazeMapRaid}} to the MapRaid question.'''
  
:[http://www.hcad.org/maps/default.asp Harris County property appraisor] Click to your region
+
If you have an issue getting into the slack team and channels, please reach out to one of the [[#Team members|MapRaid organizers]].
  
== Communication ==
 
Communication will be handled mainly in Google Hangouts (HOs) and WME chat which means WME Chat addon will be required (which can be found [http://www.waze.com/forum/viewtopic.php?f=819&t=95038 here]).
 
Chat rooms will be split up and named by location or group.
 
  
In addition, there is a Waze Forum dedicated to the MapRaid [http://www.waze.com/forum/viewforum.php?f=1350 here], where questions can be asked, and specific issues may be identified as the Raid progresses.
+
=== Unlock and lock requests ===
 +
 
 +
Unlock and lock requests should be handled in your teams slack channel. Each team has at least one rank 5 editor, most have more, and all but one team has a rank 6 editor. If you cant get a response in your teams channel, you can try the [http://wazemapraid.slack.com/messages/-dallas-general/ general MapRaid! Dallas channel].
 +
 
 +
Due to the close group and rapid time frame for editing, we can accomplish things much faster if we handle it all in-house. There is no need to post unlock requests to the forum for MapRaid! related edits.
 +
 
 +
Unlock requests should include the permalink preferably without layers, the changes you would like to make, and the reasoning behind the changes you'd like to make.
  
 
== Reference Links ==
 
== Reference Links ==
Line 169: Line 195:
 
*[[WME Chat|All about using the WME Chat]]
 
*[[WME Chat|All about using the WME Chat]]
 
*[[Community Plugins, Extensions and Tools]] where you'll links and descriptions to most of the editing scripts being used. Some of these are essential to good editing, and others make the editing process much easier. WME Validator, URO+, and WME Toolbox are highly recommended.
 
*[[Community Plugins, Extensions and Tools]] where you'll links and descriptions to most of the editing scripts being used. Some of these are essential to good editing, and others make the editing process much easier. WME Validator, URO+, and WME Toolbox are highly recommended.
*[https://wiki.waze.com/wiki/Texas Texas Wiki]
+
*[[Texas|Texas Wiki]]
  
=== Recommended Tools for Houston===
+
=== Recommended Tools ===
* The [https://greasyfork.org/en/scripts/7306-wme-mapraid-mapraid-houston-overlay Houston MapRaid Group/Region Overlay] is available on GreasyFork to indicate the Group areas on the map as you work. You will need TamperMonkey (Chrome) or GreaseMonkey (Firefox) to install and use this.
+
* The [//greasyfork.org/en/scripts/7509-wme-mapraid-dallas-raid-overlay Dallas MapRaid Group/Region Overlay] is available on GreasyFork to indicate the Group areas on the map as you work. You will need TamperMonkey (Chrome) or GreaseMonkey (Firefox) to install and use this. <small>By: {{Username|Davielde}}, updated by {{Username|Rickzabel}}</small>
  
* [http://www.google.com/url?q=http%3A%2F%2Fwiki.waze.com%2Fwiki%2FUser%3ARickzabel%2FUrComments%2F&sa=D&sntz=1&usg=AFQjCNF3YdPXqECiZuPNd9F3MqtR2xgSiQ UR Comments] - a tremendous time and labor saving tool with automation and integration with URO+, to help with working URs. Read the documentation.  
+
* [http://www.google.com/url?q=http%3A%2F%2Fwiki.waze.com%2Fwiki%2FUser%3ARickzabel%2FUrComments%2F&sa=D&sntz=1&usg=AFQjCNF3YdPXqECiZuPNd9F3MqtR2xgSiQ UrComments] - a tremendous time and labor saving tool with automation and integration with URO+, to help with working URs. Read the documentation. <small>By: {{Username|Rickzabel}}</small>
  
* [http://joyriding-001-site1.myasp.net/?group=MapRaidLA Place Browser] - In combination with the Place Name Harmonization list, this is an invaluable tool for working on existing places. Be sure to click the About tab to get an overview of the tool.
+
* [http://w-tools.org/PlaceBrowser?group=MapRaidDallas Place Browser] - This tool lists all places in the specified area, and flags some things that MIGHT be problems.  It is up to you to decide what to do with this information. Be sure to apply the global, national, and local guidelines for places. Be sure to click the About tab to get an overview of the tool. <small>By: {{Username|Joyriding}}</small><!-- <br>'''{{red|NOTE:}} All Places edits should be handled EXCLUSIVELY by Team 10 - PURs, Waze Sheets.''' -->
  
* The [http://drive.google.com/file/d/0B8WbeRGWGEOjQ1BvbHFtYlJSV2pIOVdyQlgtRmJzQUtHNjRz WME Reference Sheet<sup><small><nowiki>[PDF]</nowiki></small></sup>] is a printable double-sided tri-fold quick reference guide to some of the common topics used in WME.
+
* The [http://drive.google.com/file/d/0B8WbeRGWGEOjQ1BvbHFtYlJSV2pIOVdyQlgtRmJzQUtHNjRz WME Reference Sheet<sup><small><nowiki>[PDF]</nowiki></small></sup>] is a printable double-sided tri-fold quick reference guide to some of the common topics used in WME. <small>By: {{Username|Xevell}}</small>
  
* [https://www.waze.com/forum/viewtopic.php?t=76488 Validator] is a script that validates a map area in Waze Map Editor, highlights issues and generates a very detailed report with wiki references and solutions.<br>
+
* [http://www.waze.com/forum/viewtopic.php?t=76488 Validator] is a script that validates a map area in Waze Map Editor, highlights issues and generates a very detailed report with wiki references and solutions.<br>Download links:
Download links:
+
** For Chrome browser please download the script at [http://chrome.google.com/webstore/detail/wme-validator/baojhpeknpmkhplkcnpdcficcaaniaih Chrome Web Store]
* For Chrome browser please download the script at [http://chrome.google.com/webstore/detail/wme-validator/baojhpeknpmkhplkcnpdcficcaaniaih Chrome Web Store]
+
** For Firefox browser please download the script at [http://greasyfork.org/scripts/1571-wme-validator GreasyFork.org]<br>''Note: for Firefox browser you also need Greasemonkey or Tampermonkey installed.''
* For Firefox browser please download the script at [https://greasyfork.org/scripts/1571-wme-validator GreasyFork.org]
+
''Note: for Firefox browser you also need Greasemonkey or Tampermonkey installed.''
+
  
* [http://greasyfork.org/en/scripts/2103-wme-chat-addon WME Chat Addon] is a script that  improves the WME chat GUI. For a list of all the features check the thread [https://www.waze.com/forum/viewtopic.php?f=819&t=95038 here].
+
* [http://greasyfork.org/en/scripts/2103-wme-chat-addon WME Chat Addon] is a script that  improves the WME chat GUI. For a list of all the features check the thread [http://www.waze.com/forum/viewtopic.php?f=819&t=95038 here]. <small>By: {{Username|Dummyd2}}</small>
  Tapermonkey/Greasmonkey is required to use this script
+
** Tapermonkey/Greasmonkey is required to use this script
 
----
 
----
  
{{Mbox|type=forum|text=Click [http://www.waze.com/forum/viewtopic.php?f=3&t=120113 here to view the MapRaid! LA forum] thread}}
+
{{Mbox|type=forum|text=Click [http://www.waze.com/forum/viewtopic.php?f=237&t=123311 here to view the MapRaid! Texas forum] thread}}
  
 
== Mapraid edit lists ==
 
== Mapraid edit lists ==
Line 199: Line 223:
  
 
These are edits which need to be completed but must be postponed in order to retain history for UR Solving. These edits are designated to specific editors to complete, once they get the green light from the MapRaid! leaders.
 
These are edits which need to be completed but must be postponed in order to retain history for UR Solving. These edits are designated to specific editors to complete, once they get the green light from the MapRaid! leaders.
{{Mbox|type=critical|text=<big><big>'''These editing tasks have been delegated to specific editors for future completion at the end of MapRaid! LA. {{red|Please {{u|DO NOT EDIT or try to fix any of these items unless you are the designated "Editor to Complete"}} for that item in the list.}} These edits may only be completed once the {{u|"Continue When"}} instructions on the row for that item are met. If you have any questions please ask one of the listed [[#Local Hosts|Local Hosts]].'''</big></big>}}<br />
+
{{Mbox|type=critical|text='''These editing tasks have been delegated to specific editors for future completion at the end of MapRaid! {{RootPage}}. {{red|Please {{u|DO NOT EDIT or try to fix any of these items unless you are the designated "Editor to Complete"}} for that item in the list.}} These edits may only be completed once the {{u|"Continue When"}} instructions on the row for that item are met. If you have any questions please ask one of the listed [[#Local Hosts|Local Hosts]].'''}}<br />
  
'''<big>Please enter new information on [http://docs.google.com/forms/d/161SBxzMA5KzvDYKoiLqBcdH_TsXNV6pXRfIHL_gpnwY/viewform? this form]</big>'''
+
'''<big>Please enter new information on [http://docs.google.com/forms/d/1WNj-n8T_S5Hf7FIb27gy0hbLS3pNSzMA2YlSe7ZBwBk/viewform this form]</big>'''
  
[http://docs.google.com/spreadsheets/d/1eiXLMZicyM9AL0wnZxCOSYlmlHqwVkxT7NrV0416GBk/pubhtml?gid=488622377&single=true Click here to view this list in fullscreen]
+
[http://docs.google.com/spreadsheets/d/1YeUbqT6EJwXk8xOP4bcMMgCNN1F_JgE9Q-zAPYHac7w/pubhtml?gid=488622377&single=true Click here to view this list in fullscreen]
 
{{#widget:Google Spreadsheet
 
{{#widget:Google Spreadsheet
|key=1eiXLMZicyM9AL0wnZxCOSYlmlHqwVkxT7NrV0416GBk
+
|key=1YeUbqT6EJwXk8xOP4bcMMgCNN1F_JgE9Q-zAPYHac7w
 
|width=100%
 
|width=100%
 
|height=300
 
|height=300
Line 218: Line 242:
 
* A turn really allowed/prohibited, etc.
 
* A turn really allowed/prohibited, etc.
  
'''<big>To make a new request, or respond to an existing request, please use [http://docs.google.com/forms/d/1U1dSWZ8ZkNQa_FGldXDenDGvB2xsuD2N6vYczFW_eXY/viewform this form].</big>'''
+
'''<big>To make a new request, or respond to an existing request, please use [http://docs.google.com/forms/d/1vcMfcIt3fekSv7c5e87oMMkXNHG5m2Bt_3IigUb-bIE/viewform this form].</big>'''
  
[http://docs.google.com/spreadsheets/d/1KkgTWfNYflSZI4XFZmUktUbwoX3hVJBW2yvEdg1sC68/pubhtml Click here to view this list in fullscreen]
+
[http://docs.google.com/spreadsheets/d/19UWh12nABZ0cL9OVM_2REjUZjqAID7DPkRxgeALzAlU/pubhtml?gid=1980374929&single=true Click here to view this list in fullscreen]
 
{{#widget:Google Spreadsheet
 
{{#widget:Google Spreadsheet
|key=1KkgTWfNYflSZI4XFZmUktUbwoX3hVJBW2yvEdg1sC68
+
|key=19UWh12nABZ0cL9OVM_2REjUZjqAID7DPkRxgeALzAlU
 
|width=100%
 
|width=100%
 
|height=300
 
|height=300
 
|page=false}}
 
|page=false}}
 +
 +
== Mapraid Dallas Feb 2015 ==
 +
{{Anchor|15-01-DFW}}
 +
{{/15-01-DFW}}
 +
 +
 
[[Category:Mapraid]]
 
[[Category:Mapraid]]

Latest revision as of 02:23, 17 February 2017



Clock.png
MapRaid!Dallas,Texas has begun on 2015-02-13, Friday. 00:00 UTC. The raid will last for roughly 7 days.
Application clipboard.png
Registration for the MapRaid! is now closed. To hear about future MapRaids please join the MapRaid #Slack.
Please be sure to explore this Wiki page, and check back regularly in case of added materials.
You are only seeing modifications of this page made up until Tue, 10 Dec 2019 10:35:11 UTC, make sure to log in to the wiki to see the latest updates.

Welcome to Texas!

Mission

Our primary mission is to fix what is broken as well as fine tune what is already working. This will be handled through a variety of ways:

  • Handling URs and MPs
  • Fixing streets (correcting elevation, turns, extra nodes, alternate names, etc)
  • Routing corrections (usually found in URs or by randomly attempting to route between points and looking for irregularities)
  • FC errors (but do not downgrade without getting local guidance! See FC warning immediately below.)
Functional Classification (FC) has been fully implemented for the MAPRAID area. Some road types may deviate intentionally from the state DOTs classifications. Please consider contacting a local champ or State Manager (SM) before downgrading a road type.

Local Hosts

txemt (PM) - South Central Regional Coordinator - available


driving79 (PM) -Southeast Regional Coordinator-

pjlasl (PM) - US Champ, US CM, Texas SM - Currently Unavailable

ctpoole (PM) - Texas SM

karlcr9911 (PM) - Texas SM

jakflash (PM) - Houston area editor

coontex (PM) - Houston area editor

Important!

Please do not alter any of the following road types without first consulting a Local Host (unless changes are being made to match Functional Classification (FC)): Freeway, Ramp, Major Highway, minor Highway, Primary Street. You may edit these roads, but do not change the type of the segment (excluding FC work). Confirmation should be obtained before making changes to any of these road types that go against FC.

Please do not mass-edit Do not perform edits which will affect large numbers of segments at once. The edit history of segments is highly valuable in the process of solving URs. Mass editing effectively mass erases this history, permanently. We ask that all necessary processes which might affect large portions of the map, or long stretches of roads, be reserved until near the end of the MapRaid. This includes the “Select entire street” function. To facilitate this process in an orderly fashion, we have the Scheduled Edits list below. Please document any mass edits which are required, and you will be given first chance to make those edits when the time is right.

Anything locked at 5 or 6? Please check with a local editor before making changes.
If you are a rank 5 or 6 editor - consider keeping highlights active for locks 5 and 6.

Close nodes We make extensive use of the " micro-dogleg" technique, where a geometry node is carefully placed, at full zoom, directly next to a junction node, in order to set the angle to create a desired Turn/Stay/Exit prompt. Please watch for these if you move any junction node, and be sure to recreate the same angle at the new location.

Local Guidance

Functional Classification

Functional Class: TxDot Functional Class Look for FC along the right hand side.

In the United States, we set our road types using a national standard called Functional Classification (FC). You can read a detailed explanation in our Road Type Wiki

The Functional Classification has been completed in the DFW Area. Occasionally, we find short segments that were missed in the selection process for conversion, and it is important that these be corrected for routing continuity. If you see FC wrong, please correct it if you're 100% sure it's wrong. If you're not sure, please ask a local, karlcr9911, or txemt. In isolated cases, we have chosen to deviate from official classifications, due to errors or outdated information in the TxDot FC maps, or to better accommodate real-life situations and Waze quirks. It is important that these remain intact. Sometimes dirt roads may appear higher on FC maps but shouldn't be used by Waze for routing.

If you find an area that doesn't seem to be complete please bring it to the attention of a Local Host for review.

TxDot functional classification classifies roads as

  • An Interstate, Principal Arterial Freeway & Expressway is a  Freeway 
  • Any road that acts, looks, & feels like a freeway should be set to  Freeway  road type.
  • An Principal Arterial-Other is a  Major Highway 
  • An Minor Arterial is a  Minor Highway 
  • An Collector is a  Primary Street 
  • All other roads are to be classified as  Street 

Locking Standard

In Texas 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. If you find a road locked to a higher level than its minimum, please leave it locked no lower than that level when you have finished editing.

Texas Minimum Locking Rank Standard
Segment Type Lock Level
 Freeway  5
 Ramp  4
 Major Highway  4
 Minor Highway  3
 Primary Street  2
 Street  Automatic (1)
 |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|  2
 • • • • Ferry • • • •   5
 Private Road  2

Elevation

In general, all freeways should have an elevation of ground. Roads running over or under the freeways will have an elevation of +1 or -1. Where two freeways cross, the overpass should generally have +1 elevation. More complicated junctions may need more complicated treatment; apply the principal of "freeway defines ground level whenever possible" and keep elevations as sensible as possible. Remember that this region is not very hilly.

UR & MP Guidance

Responding to Update Requests (URs), and Map Problems (MPs) will be the primary focus of the MapRaid teams. Please make sure to follow the guidance on dealing with URs and MPs as they are clearly explained in the UR wiki page. Be especially careful to always leave a comment when closing a UR to explain why you are closing it, or how you fixed it. If there is no problem with the map to fix, don't mark it as solved, mark is Not Identified".
Our only variation for the MapRaid from the general guidance on handling URs, is that we are reducing the 7 day wait periods to 3 days. You still must comment and wait 3 days, then comment again before closing a UR as "Not Identified". If you are able to fully diagnose and fix the problem, then comment what the fix was, and close it as "Solved".

We should not be sending reminder comments after the 3 days. We send one comment asking for info, if there is no response after 3 days, close the UR. Please try to solve the UR, if that's not possible mark it as Not Identified. (We should still be sending a closing comment before closing, and it's OK to send follow up comments if you need additional information after the first response.)

As per Texas UR policy please keep UR response comments to a minimum, short and to the point. Aim for not more than 3-4 lines total. The UrComments script (link below) already has a long list of canned UR responses which have been vetted by a group of senior editors.

As we have now reached 3 days since the beginning of the Raid, and URs are being closed, please double check that the UR you are closing still is not/cannot be solved. Sometimes a question has been left for verification, and a map correction delayed, pending a response/no response. Please make sure to attempt to fix or get help if need before closing any UR. Also, DO always leave a closing comment; no UR should be closed without one.

Place Editing

Not only were our URs and PURs out of control, Places from both editors and trusted users have become a major issue. Misspelled names, wrong categories, missing addresses (EVERY business place should have an address!!), poor location, and incorrectly assigned photos are all over the map. Use the powerful Place Browser (link below) and the information on the Place editing section of the Texas page to get these places corrected.

Please use good judgement when approving photos. Any photo which has nothing to do with the actual place, reject. This is including, but not limited to body parts, car parts, bathrooms, children, & animals. If you're not sure, please ask one of the senior editors.

Gas Stations
Gas Stations should be locked to level 3 but, only after all data fields in the gas station have been filled. At least ensure that Brand, Name and Address have information. Remember to ask a local host if you need help identifying gas station information.

For editors below rank 3, once you have completely filled out a gas station with the minimum required information, please lock to your level and then ask for a lock request.

Finally, DO NOT USE THE BRAND "UNBRANDED". If it is a no brand gas station, just leave the brand field blank.

Locking Standard

  • Lock at rank 5: hospitals, universities, park and ride lots, arenas, airports.
  • Lock at 3: any other place that has at least a correct category correct name, and correct address with house number..
  • If you cannot lock high enough because of rank, lock as high as you can, and get help from a higher-ranked editor to lock properly. You can keep a personal list of Permalinks to share with the other editor.

Toll Roads / HOV / HOT

It is our custom to mark the toll checkbox on the entire sections of Toll Roads to include those ramps which are tolled. HOV and HOT road types have already been set correctly according to our local practices. If you have a question about one of these lanes, please contact a Local Host.

Construction

DFW Is going through an explosion of neighborhoods and new subdivisions. There may be some of these which are not on the editor, so if you see a missing road, see if there is an actual neighborhood by turning on the GPS tracks. There are a number of major construction projects in process within the overall MapRaid area. These construction projects can cause frequent intermittent road closures. Many closures change daily and cause great numbers of URs to appear. When handling URs in one of these areas, be aware that reports of "Turn not allowed", "Missing road", "Wrong driving direction" are common, but may not indicate a map problem that can be fixed, because the physical road situation will change before our edits can take effect.

LINKS:

Texas driving conditions and road construction


U-turns

In Texas, U-turns are generally allowed unless unsafe, or specifically denied by signage. In general we can confirm, lock or "harden" U-turns (click to remove the Purple question mark indicating a soft turn -- see the Wiki). U-turns are not named unless there as an official sign. All U-turns along freeways are normally named "Turnaround."

Alleys

Alleys are not mapped in the State of Texas and should be deleted. This has been confirmed per txemt.

Private Roads

Private roads are used only for specific purposes. Before creating new private roads or working with existing private roads, please consult txemt.

Cameras

Speed Cameras are illegal to use in the State of Texas

Red light cameras Are used in various places -- check for information for each municipality.
For a list of DFW cameras, please click here: DFW Cameras

Mapping Resources

Functional Class: TxDot Functional Class

Communication

Communication will be handled primarily in #Slack Channels and WME chat can also be used. The WME Chat addon is recommended. Special Slack channels will be set up and named by raid location and group. Please be sure to join the slack WazeMapRaid Team and join the channels for the specific MapRaid and group you are assigned to.

Click here to get your Slack invitation. Be sure to choose WazeMapRaid to the MapRaid question.

If you have an issue getting into the slack team and channels, please reach out to one of the MapRaid organizers.


Unlock and lock requests

Unlock and lock requests should be handled in your teams slack channel. Each team has at least one rank 5 editor, most have more, and all but one team has a rank 6 editor. If you cant get a response in your teams channel, you can try the general MapRaid! Dallas channel.

Due to the close group and rapid time frame for editing, we can accomplish things much faster if we handle it all in-house. There is no need to post unlock requests to the forum for MapRaid! related edits.

Unlock requests should include the permalink preferably without layers, the changes you would like to make, and the reasoning behind the changes you'd like to make.

Reference Links

The Basics

Recommended Tools

  • UrComments - a tremendous time and labor saving tool with automation and integration with URO+, to help with working URs. Read the documentation. By: Rickzabel (PM)
  • Place Browser - This tool lists all places in the specified area, and flags some things that MIGHT be problems. It is up to you to decide what to do with this information. Be sure to apply the global, national, and local guidelines for places. Be sure to click the About tab to get an overview of the tool. By: Joyriding (PM)
  • Validator is a script that validates a map area in Waze Map Editor, highlights issues and generates a very detailed report with wiki references and solutions.
    Download links:
    • For Chrome browser please download the script at Chrome Web Store
    • For Firefox browser please download the script at GreasyFork.org
      Note: for Firefox browser you also need Greasemonkey or Tampermonkey installed.
  • WME Chat Addon is a script that improves the WME chat GUI. For a list of all the features check the thread here. By: Dummyd2 (PM)
    • Tapermonkey/Greasmonkey is required to use this script

Click here to view the MapRaid! Texas forum thread

Mapraid edit lists

Spreadsheets and forms are being used to streamline management of various group efforts and track important edits. Below you can find links to use these these forms, sheets, and see the lists.

Scheduled Edits

These are edits which need to be completed but must be postponed in order to retain history for UR Solving. These edits are designated to specific editors to complete, once they get the green light from the MapRaid! leaders.

These editing tasks have been delegated to specific editors for future completion at the end of MapRaid! Texas. Please DO NOT EDIT or try to fix any of these items unless you are the designated "Editor to Complete" for that item in the list. These edits may only be completed once the "Continue When" instructions on the row for that item are met. If you have any questions please ask one of the listed Local Hosts.

Please enter new information on this form

Click here to view this list in fullscreen

Boots on the ground

We need local boots on the ground to check things. Please add requests for locals to go and scout things in person, as in on the road. Some examples when this would be used include to check and see if:

  • The street view is accurate,
  • A road is really closed,
  • A turn really allowed/prohibited, etc.

To make a new request, or respond to an existing request, please use this form.

Click here to view this list in fullscreen

Mapraid Dallas Feb 2015


DFW Area

DFW Is going through an explosion of neighborhoods and new subdivisions. There may be some of these which are not on the editor, so if you see a missing road, see if there is an actual neighborhood by turning on the GPS tracks.

Apartment Complexes

All roads should be a parking lot road.

Construction

Mapping Resources

TxDot Functional Class

GIS

NTTA - North TX Tollway Authority

DNT - Dallas North Tollway

Cameras

Speed Cameras are illegal to use in the State of Texas

The following is a list of Cities known to currently use Red Light Cameras. This may be updated as the raid goes on.

Farmer's Branch Red Light Camera are located at the following intersections:

    Marsh & Valley View
    Spring Valley & Inwood
    Valley View & Webb Chapel
    Valley View & Luna
    Webb Chapel & Valwood
    Midway & Alpha
    SH-10 West direction @ Precinct Line Rd
    Pipeline Rd East and West direction @ Precinct Line Rd,
    Precinct Line Rd North and South direction @ Bedford-Euless Rd,
    Precinct Line Rd South direction @ Harwood Rd
    I-820 S exit ramp direction @ Pipeline Rd/Glenview Dr


Mapraid Dallas.png

Raid Area

The MapRaid! area will be divided among 11 teams

This Tampermonkey script WME Overlay shows the DFW Mapraid area boundaries.

Results

Check back here after the raid is completed to see the results and achievements

MapRaid Promotions

Some editors really let their bright side out, and let their community skills shine. This is even more evident in a concerted group effort with high-density editing like a MapRaid!. Editors of all ranks working closely with each other and the Champs, really lets us everyone get to know each other, and allows certain editors to be recognized for their skills and effort.

When the Champs see someone consistently editing well, interacting well with the community, and knowledgeable of the various details from the Wiki, they can issue promotions. This can be anything from the size of a managed area, to a rank increase, or even a new role.

Watch here for promotion announcements during and after the raid.

Team members

MapRaid! Dallas
Regional Coordinator: TxEmt (PM)
Username (rank) Team Assigned Comments Team Area
bz2012(5) [PM] Profile L5.png 01 - Mansfield Badge AreaManager.png
Mapraid Dallas group 01.png

Team map area. Click image to open Waze Map Editor (WME) to this location

#Slack Channel
jdojeda(5) [PM] Profile L5.png 01 - Mansfield Badge AreaManager.png
BlueTiger68(4) [PM] Profile L4.png 01 - Mansfield Badge StateManager.png
ct13(4) [PM] Profile L4.png 01 - Mansfield Badge AreaManager.png
Kayos_On_The_Road(3) [PM] Profile L3.png 01 - Mansfield Badge AreaManager.png
tckma(3) [PM] Profile L3.png 01 - Mansfield Badge AreaManager.png
awhardin(2) [PM] Profile L2.png 01 - Mansfield Badge AreaManager.png
geopgeop(2) [PM] Profile L2.png 01 - Mansfield Badge AreaManager.png
jhwk74(2) [PM] Profile L2.png 01 - Mansfield Badge AreaManager.png
uscwaller(2) [PM] Profile L2.png 01 - Mansfield Badge AreaManager.png
driving79(6) [PM] Profile L6.png 02 - Cleburne BadgeRC-Temp.pngBadge LocalChamp.png
Mapraid Dallas group 02.png

Team map area. Click image to open Waze Map Editor (WME) to this location

#Slack Channel
bart99gt(5) [PM] Profile L5.png 02 - Cleburne Badge StateManager.png
Jreno2(4) [PM] Profile L4.png 02 - Cleburne Badge AreaManager.png
SteveInArk(4) [PM] Profile L4.png 02 - Cleburne Badge AreaManager.png
tcalvert317(4) [PM] Profile L4.png 02 - Cleburne Badge AreaManager.png
subcritical71_3(3) [PM] Profile L3.png 02 - Cleburne Badge AreaManager.png
TimC42(3) [PM] Profile L3.png 02 - Cleburne Badge AreaManager.png
Mulligan87(2) [PM] Profile L2.png 02 - Cleburne Badge AreaManager.png
Umarth735(2) [PM] Profile L2.png 02 - Cleburne Badge AreaManager.png
PyroEskimo(1) [PM] Profile L1.png 02 - Cleburne Badge AreaManager.png
sketch(6) [PM] Profile L6.png 03 - Ft Worth Badge MapRaider.pngBadge GlobalChamp.png
Mapraid Dallas group 03.png

Team map area. Click image to open Waze Map Editor (WME) to this location

#Slack Channel
ArlenBystander(5) [PM] Profile L5.png 03 - Ft Worth Badge CountryManager.png
Ctpoole(5) [PM] Profile L5.png 03 - Ft Worth Badge StateManager.png
Helgramite(5) [PM] Profile L5.png 03 - Ft Worth Badge StateManager.pngBadge Mentor.png
PhantomSoul(5) [PM] Profile L5.png 03 - Ft Worth Badge MapRaider.pngBadge StateManager.png
PleaseDriveFast(4) [PM] Profile L4.png 03 - Ft Worth Badge AreaManager.png
AgentW4C(3) [PM] Profile L3.png 03 - Ft Worth Badge AreaManager.png
SAR85(3) [PM] Profile L3.png 03 - Ft Worth Badge AreaManager.png
aspherical1(2) [PM] Profile L2.png 03 - Ft Worth Badge AreaManager.png
Davisnado(2) [PM] Profile L2.png 03 - Ft Worth Badge AreaManager.png
lordmogra [PM] Profile L2.png 03 - Ft Worth Badge AreaManager.png
TXEMT(6) [PM] Profile L6.png 04 - Dallas BadgeRC-Temp.pngBadge LocalChamp.png
Mapraid Dallas group 04.png

Team map area. Click image to open Waze Map Editor (WME) to this location

#Slack Channel
Gasparfox(5) [PM] Profile L5.png 04 - Dallas Badge LocalChamp.png
qwaletee(5) [PM] Profile L5.png 04 - Dallas Badge MapRaider.pngBadge StateManager.png
ialangford(4) [PM] Profile L4.png 04 - Dallas Badge AreaManager.png
yb6kos(4) [PM] Profile L4.png 04 - Dallas Badge AreaManager.png
adetia(3) [PM] Profile L3.png 04 - Dallas Badge AreaManager.png
hackmycomputer(2) [PM] Profile L2.png 04 - Dallas Badge AreaManager.png
Kinematic(2) [PM] Profile L2.png 04 - Dallas Badge AreaManager.png
kkarkid(2) [PM] Profile L2.png 04 - Dallas Badge AreaManager.png
wallydury(1) [PM] Profile L1.png 04 - Dallas Badge AreaManager.png
ply8808(5) [PM] Profile L5.png 05 - Mid Cities Badge MapRaider.pngBadge CountryManager.png
Mapraid Dallas group 05.png

Team map area. Click image to open Waze Map Editor (WME) to this location

#Slack Channel
hardian_n(4) [PM] Profile L4.png 05 - Mid Cities Badge AreaManager.png
hitfactor(4) [PM] Profile L4.png 05 - Mid Cities Badge AreaManager.png
Poncewattle(3) [PM] Profile L3.png 05 - Mid Cities Badge AreaManager.png
voludu2(3) [PM] Profile L3.png 05 - Mid Cities Badge AreaManager.png
BarfmanTheGreat(2) [PM] Profile L2.png 05 - Mid Cities Badge AreaManager.png
ComstockMine(2) [PM] Profile L2.png 05 - Mid Cities Badge AreaManager.png
Gazoo4U(2) [PM] Profile L2.png 05 - Mid Cities Badge AreaManager.png
Tomskii(2) [PM] Profile L2.png 05 - Mid Cities Badge AreaManager.png
nightshadeNOLA(1) [PM] Profile L1.png 05 - Mid Cities Badge AreaManager.png
crazycaveman(5) [PM] Profile L5.png 06 - North Dallas Badge StateManager.png
Mapraid Dallas group 06.png

Team map area. Click image to open Waze Map Editor (WME) to this location

#Slack Channel
dbwiddis(4) [PM] Profile L4.png 06 - North Dallas Badge AreaManager.png
t0cableguy(4) [PM] Profile L4.png 06 - North Dallas Badge StateManager.png
faromasa(3) [PM] Profile L3.png 06 - North Dallas Badge AreaManager.png
JasonN899(3) [PM] Profile L3.png 06 - North Dallas Badge AreaManager.png
Young7Up(3) [PM] Profile L3.png 06 - North Dallas Badge AreaManager.png
DustinHetzel(2) [PM] Profile L2.png 06 - North Dallas Badge MapRaider.png
frankthetankk(2) [PM] Profile L2.png 06 - North Dallas Badge AreaManager.png
restless_in_nb(2) [PM] Profile L2.png 06 - North Dallas Badge AreaManager.png
SeekingSerenity(2) [PM] Profile L2.png 06 - North Dallas Badge AreaManager.png
TwoEightZero(2) [PM] Profile L2.png 06 - North Dallas Badge AreaManager.png
MojaveCactusMonkey(5) [PM] Profile L5.png 07 - Lewisville Badge MapRaider.pngBadge StateManager.png
Mapraid Dallas group 07.png

Team map area. Click image to open Waze Map Editor (WME) to this location

#Slack Channel
pumrum(5) [PM] Profile L5.png 07 - Lewisville Badge MapRaider.pngBadge StateManager.png
SkiDooGuy(5) [PM] Profile L5.png 07 - Lewisville Badge MapRaider.pngBadge StateManager.png
GS-1905(3) [PM] Profile L3.png 07 - Lewisville Badge AreaManager.png
jaywazin(3) [PM] Profile L3.png 07 - Lewisville Badge AreaManager.png
john-cole(3) [PM] Profile L3.png 07 - Lewisville Badge AreaManager.png
Joyriding(3) [PM] Profile L3.png 07 - Lewisville Badge AreaManager.png
SanzClew(3) [PM] Profile L3.png 07 - Lewisville Badge AreaManager.png
whoaitspete(3) [PM] Profile L3.png 07 - Lewisville Badge MapRaider.pngBadge AreaManager.png
DashKS(2) [PM] Profile L2.png 07 - Lewisville Badge AreaManager.png
JButz2(2) [PM] Profile L2.png 07 - Lewisville Badge AreaManager.png
Ohmanrayman(2) [PM] Profile L2.png 07 - Lewisville Badge AreaManager.png
Trotskyist(2) [PM] Profile L2.png 07 - Lewisville Badge AreaManager.png
Rivermedic(5) [PM] Profile L5.png 08 - Lancaster Badge AreaManager.png
Mapraid Dallas group 08.png

Team map area. Click image to open Waze Map Editor (WME) to this location

#Slack Channel
coontex(4) [PM] Profile L4.png 08 - Lancaster Badge AreaManager.png
HuckD(4) [PM] Profile L4.png 08 - Lancaster Badge AreaManager.png
okladriver(3) [PM] Profile L3.png 08 - Lancaster Badge AreaManager.png
triage685(3) [PM] Profile L3.png 08 - Lancaster Badge AreaManager.png
banchormin(2) [PM] Profile L2.png 08 - Lancaster Badge AreaManager.png
DorahaMandi(2) [PM] Profile L2.png 08 - Lancaster Badge AreaManager.png
Rooksie(2) [PM] Profile L2.png 08 - Lancaster Badge AreaManager.png
UberGenius(2) [PM] Profile L2.png 08 - Lancaster Badge AreaManager.png
kyhtak(1) [PM] Profile L1.png 08 - Lancaster Badge AreaManager.png
manoeuvre(5) [PM] Profile L5.png 09 - Mesquite Badge MapRaider.pngBadge LocalChamp.png
Mapraid Dallas group 09.png

Team map area. Click image to open Waze Map Editor (WME) to this location

#Slack Channel
dmcrandall(4) [PM] Profile L4.png 09 - Mesquite Badge StateManager.png
KuniaKid(4) [PM] Profile L4.png 09 - Mesquite Badge StateManager.png
shadoh(4) [PM] Profile L4.png 09 - Mesquite Badge AreaManager.png
jbrianj(3) [PM] Profile L3.png 09 - Mesquite Badge AreaManager.png
qazxcvbnmm(3) [PM] Profile L3.png 09 - Mesquite Badge AreaManager.png
emdesigns(2) [PM] Profile L2.png 09 - Mesquite Badge AreaManager.png
kjg53(2) [PM] Profile L2.png 09 - Mesquite Badge AreaManager.png
Raiden38(2) [PM] Profile L2.png 09 - Mesquite Badge AreaManager.png
redspawn2k2(2) [PM] Profile L2.png 09 - Mesquite Badge AreaManager.png
orbitc(6) [PM] Profile L6.png 10 - Keller Badge MapRaider.pngBadgeRC-Temp.pngBadge LocalChamp.pngBadge Mentor Local Champ.png
Mapraid Dallas group 10.png

Team map area. Click image to open Waze Map Editor (WME) to this location

#Slack Channel
Machete808(5) [PM] Profile L5.png 10 - Keller Badge StateManager.png
Jakflash(4) [PM] Profile L4.png 10 - Keller Badge StateManager.png
ulle2(4) [PM] Profile L4.png 10 - Keller Badge AreaManager.png
OSUBigToe(3) [PM] Profile L3.png 10 - Keller Badge AreaManager.png
poweruser10(3) [PM] Profile L3.png 10 - Keller Badge AreaManager.png
e-sarge(2) [PM] Profile L2.png 10 - Keller Badge AreaManager.png
jr1982jr(2) [PM] Profile L2.png 10 - Keller Badge AreaManager.png
JustinS83(2) [PM] Profile L2.png 10 - Keller Badge AreaManager.png
mudge42(2) [PM] Profile L2.png 10 - Keller Badge AreaManager.png
spedracr(2) [PM] Profile L2.png 10 - Keller Badge AreaManager.png
karlcr9911(5) [PM] Profile L5.png 11 - Weatherford Badge StateManager.png
Mapraid Dallas group 11.png

Team map area. Click image to open Waze Map Editor (WME) to this location

#Slack Channel
Olestas(5) [PM] Profile L5.png 11 - Weatherford Badge MapRaider.pngBadge CountryManager.png
FzNk(4) [PM] Profile L4.png 11 - Weatherford Badge StateManager.png
iamrioo(4) [PM] Profile L4.png 11 - Weatherford Badge AreaManager.png
Bluediemond(3) [PM] Profile L3.png 11 - Weatherford Badge AreaManager.png
kwrigh01(3) [PM] Profile L3.png 11 - Weatherford Badge MapRaider.pngBadge AreaManager.png
autenil(2) [PM] Profile L2.png 11 - Weatherford Badge AreaManager.png
Doryphore_(2) [PM] Profile L2.png 11 - Weatherford Badge AreaManager.png
gunnargsd(2) [PM] Profile L2.png 11 - Weatherford Badge AreaManager.png
mkovnick(2) [PM] Profile L2.png 11 - Weatherford Badge AreaManager.png