User:PesachZ/SyncScratch View history

m (Copying text of wiki page for coparison with the "Connecticut/Cities and towns" page)
m (Copying text of wiki page for coparison with the "Texas" page)
Line 1: Line 1:
The state of [[Connecticut]] is divided into 169 Cities and Towns. When assigning the "City" property to Road Segments please use this list.
Below you will find information related to using Waze in the State of Texas. All editors in the state are required to have a non [http://www.waze.com/support/answer?q=16055987 usa_username], have their [http://www.waze.com/forum private messaging] turned on, and turn live users on in the [[Map_Editor_Interface_and_Controls#Layers|layers]] menu. '''Do not edit in ''Invisible'' mode if you are a rank 3 or below.''' Please pay attention to the chat window in the lower right-hand part the map editor (and introduce yourself if you're a first-time editor). You can find useful info there and ask questions. You can also find useful information at the Texas [https://www.waze.com/forum/viewforum.php?f=237 forum page]. You can also [https://docs.google.com/forms/d/e/1FAIpQLSfbxW5YFRywjEChR08S8X2pk7yWy0zl2Ou6bsiiaYIR73uYDw/viewform join Slack] and chat with Texas editors, as well as the state managers (SM) and regional coordinator (RC). Once you receive the Slack invitation, login and join the #texas channel.
<big>


"FCL" links are for the Connecticut DOT's [[National resources/USA/Functional classification|functional classification]] maps for each town, which are in PDF format.
== Cities and towns ==


[[File:CT Town Map.png|700px|CT Town Map]] {{AlphaIndexStart|2}}
There are 6386 Cities and Towns spread across 254 counties in the state. See [http://en.wikipedia.org/wiki/List_of_cities_in_Texas Cities in Texas] for proper naming information.


== A ==
City names should be everything inside of the city limits. City limits are clearly defined by the green signs. Use of Google Maps to find where a city is highly discouraged.


*Andover ([http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/001fcl.pdf FCL])
== Roads in Texas ==
*Ansonia ([http://ansonia.mapxpress.net/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/002fcl.pdf FCL])
*Ashford ([http://54.83.239.177/html5viewer/?viewer=neccoggis2 NECCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/003fcl.pdf FCL])
*Avon ([http://107.20.209.214/AvonCT_Public/Default.html GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/004fcl.pdf FCL])


== B ==
=== Road naming ===
<div>Interstates = I-XX</div>
<div>US Highway = US-XX</div>
<div>State Highway = SH-XX</div>
<div>State Loop = Loop XX</div>
<div>State Spur = Spur XX</div>
<div>State Park Road = Park Rd XX</div>
<div>State Recreational Road = Recreational Rd XX</div>
<div>Farm/Ranch to Market = FM/RM XX</div>
<div>County Road = CR-XX</div>
<div>Private Road = Private Rd XX</div>


*Barkhamsted ([http://www.mapgeo.com/barkhamstedct/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/005fcl.pdf FCL])
'''Business Roads'''
*Beacon Falls ([http://beaconfalls.mapxpress.net/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/006fcl.pdf FCL])
<div>All business roads should be suffixed with BUS:</div>
*Berlin ([http://www.berlingis.com/ags_map/ GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/007fcl.pdf FCL])
<div>Business Interstate = I-XX BUS</div>
*Bethany ([http://bethany.mapxpress.net/ags_map/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/008fcl.pdf FCL])
<div>Business US Highway = US-XX BUS</div>
*Bethel ([http://107.20.209.214/BethelCT_Public/index.html GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/009fcl.pdf FCL])
*Bethlehem ([http://bethlehem.mapxpress.net/ags_map/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/010fcl.pdf FCL])
*Bloomfield ([http://www.bloomfieldct.gov/gis/pages/maps-assessor PLAT], [http://themdc.maps.arcgis.com/apps/webappviewer/index.html?id=4a513162be744e3d87955b0fc0ae87d0 MDC GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/011fcl.pdf FCL])
*Bolton ([http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/012fcl.pdf FCL])
*Bozrah ([http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/013fcl.pdf FCL])
*Branford ([http://www.branfordgis.com/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/014fcl.pdf FCL])
*Bridgeport ([http://metrocog.mapxpress.net/Bridgeport/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/015fcl.pdf FCL])
*Bridgewater ([http://www.bridgewatertownhall.org/pages/BridgewaterCT_Assessor/maps/S01E5F3B6 PLAT], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/016fcl.pdf FCL])
*Bristol ([http://bristol.mapxpress.net/ags_map/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/017fcl.pdf FCL])
*Brookfield ([http://brookfield.mapxpress.net/ags_map/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/018fcl.pdf FCL])
*Brooklyn ([http://54.83.239.177/html5viewer/?viewer=neccoggis2 NECCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/019fcl.pdf FCL])
*Burlington ([http://burlington.mapxpress.net/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/020fcl.pdf FCL])


== C ==
[[Suffix|Road Naming Abbreviations & Suffixes]]


*Canaan ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/021fcl.pdf FCL])
'''Interstates throughout the state'''
*Canterbury ([http://54.83.239.177/html5viewer/?viewer=neccoggis2 NECCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/022fcl.pdf FCL])
*Canton ([http://canton.mapxpress.net/portal.asp GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/023fcl.pdf FCL])
*Chaplin ([http://54.83.239.177/html5viewer/?viewer=neccoggis2 NECCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/024fcl.pdf FCL])
*Cheshire ([http://cheshire.mapxpress.net/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/025fcl.pdf FCL])
*Chester ([http://www.mainstreetmaps.com/CT/Chester/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/026fcl.pdf FCL])
*Clinton ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/027fcl.pdf FCL])
*Colchester ([http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/028fcl.pdf FCL])
*Colebrook ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/029fcl.pdf FCL])
*Columbia ([http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/030fcl.pdf FCL])
*Cornwall ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/031fcl.pdf FCL])
*Coventry ([http://coventry.mapxpress.net/ags_map/ GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/032fcl.pdf FCL])
*Cromwell ([http://www.mapgeo.com/CromwellCT/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/033fcl.pdf FCL])


== D ==
*<span style="color: rgb(0, 0, 0); font-family: arial; font-size: 17px; line-height: 24.764999389648438px;">I-2 Rio Grande Valley</span>
*<span style="color: rgb(0, 0, 0); font-family: arial; font-size: 17px; line-height: 24.764999389648438px;">I-10 New Mexico to Louisiana</span>
*<span style="color: rgb(0, 0, 0); font-family: arial; font-size: 17px; line-height: 24.764999389648438px;">I-20 Midland/Odessa to Louisiana</span>
*<span style="color: rgb(0, 0, 0); font-family: arial; font-size: 17px; line-height: 24.764999389648438px;">I-27 Lubbock to Amarillo</span>
*<span style="color: rgb(0, 0, 0); font-family: arial; font-size: 17px; line-height: 24.764999389648438px;">I-30 Fort Worth to Arkansas</span>
*<span style="color: rgb(0, 0, 0); font-family: arial; font-size: 17px; line-height: 24.764999389648438px;">I-35 Mexico to Oklahoma</span>
*<span style="color: rgb(0, 0, 0); font-family: arial; font-size: 17px; line-height: 24.764999389648438px;">I-35E Hillsboro to Denton through Dallas</span>
*<span style="color: rgb(0, 0, 0); font-family: arial; font-size: 17px; line-height: 24.764999389648438px;">I-35W Hillsboro to Denton through Fort Worth</span>
*<span style="color: rgb(0, 0, 0); font-family: arial; font-size: 17px; line-height: 24.764999389648438px;">I-37 Corpus Christi to San Antonio</span>
*<span style="color: rgb(0, 0, 0); font-family: arial; font-size: 17px; line-height: 24.764999389648438px;">I-40 New Mexico to Oklahoma</span>
*<span style="color: rgb(0, 0, 0); font-family: arial; font-size: 17px; line-height: 24.764999389648438px;">I-45 Galveston to Dallas</span>
*<span style="color: rgb(0, 0, 0); font-family: arial; font-size: 17px; line-height: 24.764999389648438px;">I-69 Brownsville/Edinburg/Laredo to Texarkana (will follow US-59)</span>
*<span style="color: rgb(0, 0, 0); font-family: arial; font-size: 17px; line-height: 24.764999389648438px;">I-369 Spur to west side of Texarkana</span>
*<span style="color: rgb(0, 0, 0); font-family: arial; font-size: 17px; line-height: 24.764999389648438px;">I-410 Loop around San Antonio</span>
*<span style="color: rgb(0, 0, 0); font-family: arial; font-size: 17px; line-height: 24.764999389648438px;">I-610 Loop around Houston</span>
*<span style="color: rgb(0, 0, 0); font-family: arial; font-size: 17px; line-height: 24.764999389648438px;">I-635 Spur through DFW Metroplex</span>
*<span style="color: rgb(0, 0, 0); font-family: arial; font-size: 17px; line-height: 24.764999389648438px;">I-820 Loop around Fort Worth&nbsp;</span>


*Danbury ([http://webmap.jws.com/taxmap/viewer.aspx?JWSCONFIG=CT_Danbury_public GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/034fcl.pdf FCL])
=== Special roads ===
*Darien ([http://www.mapgeo.com/DarienCT/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/035fcl.pdf FCL])
*Deep River ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/122fcl.pdf FCL])
*Derby ([http://derby.mapxpress.net/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/036fcl.pdf FCL])
*Durham ([http://www.townofdurhamct.org/content/28562/27546/27641.aspx PLAT], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/037fcl.pdf FCL])


== E ==
*[[Best map editing practice#When to Split a Two-Way Road (and when not to)|When not to divide a two-way road]]
*[[Best map editing practice|Divided Roads]]
*[[Carpool, HOV, Transit lanes|Carpool, HOV, Transit lanes]]
*[[Creating and Editing a roundabout|Roundabouts and Traffic Circles]]
*[[Creating_and_Editing_street_segments#Fix_the_end-node_on_culs-de-sac_and_dead-ends|Cul-de-sacs]]
*[[Road types/USA#Dirt|Dirt Roads]]. In Texas '''ALL''' roads that are unpaved or gravel are considered dirt roads as this is how GPS Nav users (any brand) expect the "Avoid Dirt Roads" feature to behave.  These roads should be deleted when going through farm land, ranch land, or mountainous areas throughout the state, as they are most likely base import roads and not real roads. For roads which are labeled with names and are actually dirt on SATIMG, please keep these and make them dirt roads.
*[[Road types/USA#Parking Lot Road|Parking Lot Roads]]
*[[Best map editing practice#Toll roads|Toll Roads]]
*[http://en.wikipedia.org/wiki/Frontage_road Frontage roads] Name as "Frontage Rd" unless the corresponding highway has an alternate name. I-635 Frontage roads are labeled as "Lyndon B Johnson Freeway" as that is the local name for I-635.
*Alleys and driveways are '''NOT MAPPED'''
*Any road which is a main road for a state park can be a {{Primary Street}}. Other roads can be {{Street}}.


*East Granby ([http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/039fcl.pdf FCL])
=== Non-drivable roads ===
*East Haddam ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/040fcl.pdf FCL])
*East Hampton ([http://hosting.tighebond.com/EastHamptonCT_Public/index.html GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/041fcl.pdf FCL])
*East Hartford ([https://www.mapsonline.net/easthartfordct/index.html GIS], [http://themdc.maps.arcgis.com/apps/webappviewer/index.html?id=4a513162be744e3d87955b0fc0ae87d0 MDC GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/042fcl.pdf FCL])
*East Haven ([http://easthaven.mapxpress.net/ags_map/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/043fcl.pdf FCL])
*East Lyme ([http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/044fcl.pdf FCL])
*East Windsor ([http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/046fcl.pdf FCL])
*Eastford ([http://54.83.239.177/html5viewer/?viewer=neccoggis2 NECCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/038fcl.pdf FCL])
*Easton ([https://maps.gbrct.org/EastonGIS/Viewer.html GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/045fcl.pdf FCL])
*Ellington ([http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/047fcl.pdf FCL])
*Enfield ([http://host.cdmsmithgis.com/enfieldct/ GIS], [http://enfield-ct.gov/145/Assessor-Maps PLAT]. [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/048fcl.pdf FCL])
*Essex ([http://www.mapgeo.com/EssexCT/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/049fcl.pdf FCL])


== F ==
Generally, if a road can't be driven on (e.g. Walking Trail, Pedestrian Boardwalk, Stairway, Ranch road in the middle of nowhere) then it should not be mapped in Waze. This is due to the way the routing engine works, as Waze '''WILL''' route users to drive on these "Non-Drivable" road types.


*Fairfield ([http://metrocog.mapxpress.net/Fairfield GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/050fcl.pdf FCL])
'''[[Railroads|Railroads]]''' mapped in Texas should follow the current standard of editing. All crossings should be connected to drivable segments accordingly. If no crossing exists, elevate the segment accordingly.
*Farmington ([http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/051fcl.pdf FCL])
*Franklin ([http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/052fcl.pdf FCL])


== G ==
'''ONLY enter a name for the railroad segment if the tracks are historical in nature, a major landmark, or a routine destination for Wazers. In TX, very few segments should be named and most 'routine destinations' will be covered by a Place point/area for the train station.'''


*Glastonbury ([https://gis.glastonbury-ct.gov/SLV/Viewer.html?Viewer=Glastonbury%20Public GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/053fcl.pdf FCL])
The Waze app now renders railroad tracks as such so naming serves little purpose any longer.
*Goshen ([http://goshen.mapxpress.net/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/054fcl.pdf FCL])
*Granby ([http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/055fcl.pdf FCL])
*Greenwich ([http://www.greenwichct.org/upload/medialibrary/e50/Greenwich-StreetMap.pdf Street Map], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/056fcl.pdf FCL])
*Griswold ([http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/057fcl.pdf FCL])
*Groton ([http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/058fcl.pdf FCL])
*Guilford ([http://www.guilfordgis.com/ags_map/default.htm GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/059fcl.pdf FCL])


== H ==
=== Miscellaneous ===
U-turns are labeled as "Turnaround" and set to whatever type identified in FC (if not typed in FC, match it to the lowest road type that it touches - similar to AGCs).


*Haddam ([http://107.20.209.214/HaddamCT_Public/index.html GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/060fcl.pdf FCL])
=== Road Lock Standards ===
*Hamden ([http://www.hamdengis.com/ags_map/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/061fcl.pdf FCL])
{{Lock Standard State|TX}}
*Hampton ([http://54.83.239.177/html5viewer/?viewer=neccoggis2 NECCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/062fcl.pdf FCL])
*Hartford ([http://gis1.hartford.gov/propertyviewer/index.html GIS], [http://themdc.maps.arcgis.com/apps/webappviewer/index.html?id=4a513162be744e3d87955b0fc0ae87d0 MDC GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/063fcl.pdf FCL])
*Hartland ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/064fcl.pdf FCL])
*Harwinton ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/065fcl.pdf FCL])
*Hebron ([http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/066fcl.pdf FCL])


{{Anchor|I}}{{Anchor|J}}
== Functional Classification of Roads ==


== K ==
See [[Road names/USA]] and [[Road types/USA]].


*Kent ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/067fcl.pdf FCL])
Texas participates in functional classification across the entire state. We promote a hybrid FC to ensure for the best routing possible for all Wazers. The hybrid FC basically means a state highway would never be typed less than Minor Highway (mH).
*Killingly ([http://www.caigisonline.com/KillinglyCT/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/068fcl.pdf FCL])
*Killingworth ([http://hosting.tighebond.com/KillingworthCT_Public/index.html GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/069fcl.pdf FCL])


== L ==
'''Frontage roads''' along Freeways should be matched to FC.  If FC does not list the frontage road, type it as a Primary Street.


*Lebanon ([http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/070fcl.pdf FCL])
'''Turnarounds''' (those labeled as Turnaround, not cross-overs), should be matched to FC. If FC does not list the Turnaround, match it to the lowest road type that it touches - similar to AGCs.
*Ledyard ([http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/071fcl.pdf FCL])
*Lisbon ([http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/072fcl.pdf FCL])
*Litchfield ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/073fcl.pdf FCL])
*Lyme ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/074fcl.pdf FCL])


== M ==
=== FC cross reference ===


*Madison ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/075fcl.pdf FCL])
Refer to this chart to determine the road type of a given paved public road based on the functional class.
*Manchester ([http://gis1.townofmanchester.org/PublicToMMI2/index.html GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/076fcl.pdf FCL])
*Mansfield ([http://www.mainstreetmaps.com/CT/Mansfield/# GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], , [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/077fcl.pdf FCL])
**Storrs
*Marlborough ([http://www.mapgeo.com/marlboroughct/ GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/078fcl.pdf FCL])
*Meriden ([http://gis.meridenct.gov/meriden/default.aspx GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/079fcl.pdf FCL])
*Middlebury ([http://middlebury.mapxpress.net/ags_map/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/080fcl.pdf FCL])
*Middlefield ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/081fcl.pdf FCL])
*Middletown ([http://gis.cityofmiddletown.com/middletownct/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/082fcl.pdf FCL])
*Milford ([http://milford.mapxpress.net/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/083fcl.pdf FCL])
*Monroe ([https://maps.gbrct.org/MonroeGIS/Viewer.html GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/084fcl.pdf FCL])
*Montville ([http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/085fcl.pdf FCL])
*Morris ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/086fcl.pdf FCL])


== N ==
To use this chart, first determine the functional class of a road, and whether it is a signed, numbered highway in a particular highway system.


*Naugatuck ([http://naugatuck.mapxpress.net/ags_map/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/087fcl.pdf FCL])
Where the column for the road's highway system and the row for the road's functional class meet, you will find the proper road type for that particular road.
*Newington ([http://themdc.maps.arcgis.com/apps/webappviewer/index.html?id=4a513162be744e3d87955b0fc0ae87d0 MDC GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/093fcl.pdf FCL])
*Newtown ([http://maps.newtown-ct.gov/ags_map/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/096fcl.pdf FCL])
*New Britain ([http://newbritain.mapxpress.net/ GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/088fcl.pdf FCL])
*New Canaan ([http://107.20.209.214/NewCanaanCT_Public/index.html GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/089fcl.pdf FCL])
*New Fairfield ([http://hosting.tighebond.com/NewFairfieldCT_Public GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/090fcl.pdf FCL])
*New Hartford ([http://www.newhartfordgis.com/ags_map/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/091fcl.pdf FCL])
*New Haven ([http://www.cityofnewhaven.com/Maps/ City Maps Page], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/092fcl.pdf FCL])
*New London ([http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/094fcl.pdf FCL])
*New Milford ([http://mapgeo.com/newmilfordct/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/095fcl.pdf FCL])
*Norfolk ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/097fcl.pdf FCL])
*North Branford ([http://107.20.209.214/NorthBranfordCT_Public/index.html GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/098fcl.pdf FCL])
*North Canaan ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/099fcl.pdf FCL])
*North Haven ([http://www.mapgeo.com/northhavenct/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/100fcl.pdf FCL])
*North Stonington ([http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/101fcl.pdf FCL])
*Norwalk ([http://host.cdmsmithgis.com/norwalkct/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/102fcl.pdf FCL])
*Norwich ([http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/103fcl.pdf FCL])


== O ==
A number of examples are given below the chart.


*Old Lyme ([http://www.mapgeo.com/OldLymeCT/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/104fcl.pdf FCL])
*Old Saybrook ([http://www.oldsaybrookct.org/Pages/OldSaybrookCT_Land/GIS_Data GIS Download], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/105fcl.pdf FCL])
*Orange ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/106fcl.pdf FCL])
*Oxford ([http://oxford.mapxpress.net/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/107fcl.pdf FCL])


== P ==
<div style="font-size:smaller">
{| border="1" style="border-collapse:collapse; text-align:center"
! scope="row" rowspan="2" colspan="2"|
! colspan="8"| <big>Highway Systems</big>
|-
! Interstate
! Interstate Business Loop/Spur
! US Hwy (incl. some [[wikipedia:special routes|special routes]])
! US Hwy BUS, SPUR, LOOP
! State Hwy (incl. some special routes)
! State Hwy BUS, SPUR{{ref label|a|a}}, LOOP, Frontage Rd
! FM / County Route
! Locally-maintained
|-
|
| ''example''
| I-10 E
| I-94 Business
| US-190
| US-460 Business
| SR-23
| SR-400 Loop
| FM 40 / CR-15
| Robertson St
|-
! scope="row" rowspan="8" style="width:28px"| <big>F<br>u<br>n<br>c<br>t<br>i<br>o<br>n<br>a<br>l<br> <br>C<br>l<br>a<br>s<br>s</big><!-- Temp placeholder -->
| {{font color|white|blue|'''Interstate'''}}{{ref label|b|b}}||{{Freeway|Fw}} ||n/a||n/a||n/a||n/a||n/a||n/a||n/a
|-
| {{font color|white|black|'''Other Freeway'''}}{{ref label|c|c}}||n/a||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}
|-
| {{font color|white|black|'''Other Expressway'''}}{{ref label|d|d}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}
|-
| {{font color|black|red|'''Other Principal Arterial'''}}{{ref label|e|e}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}
|-
| {{font color|white|green|'''Minor Arterial'''}}{{ref label|f|f}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}
|-
| {{font color|white|purple|'''Major Collector'''}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}||{{Primary Street|PS}}||{{Primary Street|PS}}
|-
| {{font color|black|yellow|'''Minor Collector'''}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}||{{Primary Street|PS}}||{{Primary Street|PS}}
|-
| {{font color|black|gray|'''Local/not mapped'''}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}||{{Street}}||{{Street}}
|}
{{note|a|a}} When a state highway "SPUR" route is used to connect a state highway with another state highway, a US highway, or an Interstate (i.e., when it is used as a connector/CONN route), use the first state highway column.


*Plainfield ([http://54.83.239.177/html5viewer/?viewer=neccoggis2 NECCOG GIS], [http://www.mapgeo.com/plainfieldct GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/108fcl.pdf FCL])
{{note|b|b}} Also known as '''Principal Arterial - Interstate'''.
*Plainville ([http://plainville.mapxpress.net/ags_map/ GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/109fcl.pdf FCL])
*Plymouth ([http://plymouth.mapxpress.net/ags_map/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/110fcl.pdf FCL])
*Pomfret ([http://54.83.239.177/html5viewer/?viewer=neccoggis2 NECCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/111fcl.pdf FCL])
*Portland ([https://towntech.maps.arcgis.com/apps/Solutions/s2.html?appid=71686193554b49478ad63fca5e1edd7c GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/112fcl.pdf FCL])
*Preston ([http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/113fcl.pdf FCL])
*Prospect ([http://www.mapgeo.com/ProspectCT/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/114fcl.pdf FCL])
*Putnam ([http://54.83.239.177/html5viewer/?viewer=neccoggis2 NECCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/115fcl.pdf FCL])


{{Anchor|Q}}
{{note|c|c}} Also known as '''Principal Arterial - Freeway'''.


== R ==
{{note|d|d}} Also known as '''Principal Arterial - Expressway'''.


*Redding ([http://gis2.cdmsmith.com/reddingct/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/116fcl.pdf FCL])
{{note|e|e}} Also known as '''Principal Arterial'''.
*Ridgefield ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/117fcl.pdf FCL])
*Rocky Hill ([http://www.mapsonline.net/rockyhillct/index.html GIS], [http://themdc.maps.arcgis.com/apps/webappviewer/index.html?id=4a513162be744e3d87955b0fc0ae87d0 MDC GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/118fcl.pdf FCL])
*Roxbury ([http://qpublic9.qpublic.net/qpmap4/map.php?county=ct_roxbury&layers=parcels+roads+lakes&mapmode GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/119fcl.pdf FCL])


== S ==
{{note|f|f}} Also known as '''Other Arterial'''.


*Salem ([http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/120fcl.pdf FCL])
*Salisbury ([http://salisburyct.us/offices/assessor/assessormaps PLAT], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/121fcl.pdf FCL])
*Scotland [http://54.83.239.177/html5viewer/?viewer=neccoggis2 NECCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/123fcl.pdf FCL])
*Seymour ([http://www.seymourgis.com/ags_map/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/124fcl.pdf FCL])
*Sharon ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/125fcl.pdf FCL])
*Shelton ([http://shelton.mapxpress.net/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/126fcl.pdf FCL])
*Sherman ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/127fcl.pdf FCL])
*Simsbury ([http://simsbury.mapxpress.net/ags_map/ GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/128fcl.pdf FCL])
*Somers ([http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/129fcl.pdf FCL])
*South Windsor ([http://southwindsor.mapxpress.net/ GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/132fcl.pdf FCL])
*Southbury ([http://southbury.mapxpress.net/ags_map/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/130fcl.pdf FCL])
*Southington ([http://gis.southington.org/ GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/131fcl.pdf FCL])
*Sprague ([http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/133fcl.pdf FCL])
*Stafford ([http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/134fcl.pdf FCL])
*Stamford ([http://stamfordct.maps.arcgis.com/apps/SimpleViewer/index.html?appid=43213c0fc1b449feb72f21fdd7bed715 PLAT], [http://www.stamfordchamber.com/map/map.pdf Street Map (CofC)],[http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/135fcl.pdf FCL])
*Sterling ([http://hosting.tighebond.com/SterlingCT_Public/index.html GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/136fcl.pdf FCL])
*Stonington ([http://gis.stonington-ct.gov/ags_map/ GIS], [http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/137fcl.pdf FCL])
*Stratford ([https://maps.gbrct.org/stratfordgis/viewer.html GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/138fcl.pdf FCL])
*Suffield ([http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/139fcl.pdf FCL])


== T ==
For example,
* An Interstate Business Loop classified as a Minor Arterial is a {{Major Highway}}.
* A US Highway classified as a Minor Arterial is a {{Major Highway}}.
* A US Highway Spur route classified as a Minor Arterial is a {{Minor Highway}}.
* A State Highway classified as an Other Freeway is a {{Freeway}}.
* A State Highway classified as a Collector is a {{Minor Highway}}.
* A County Route classified as a Minor Arterial is a {{Minor Highway}}.
* A County Route classified as a Collector is a {{Primary Street}}
* A locally-maintained road classified as an Other Principal Arterial is a {{Major Highway}}.
* A locally-maintained road  classified as a Collector is a {{Primary Street}}.


*Thomaston ([http://thomaston.mapxpress.net/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/140fcl.pdf FCL])
*Thompson ([http://54.83.239.177/html5viewer/?viewer=neccoggis2 NECCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/141fcl.pdf FCL])
*Tolland ([http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/142fcl.pdf FCL])
*Torrington ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/143fcl.pdf FCL] [http://www.torringtonct.org/Public_Documents/TorringtonCT_Engineering/Published%20Maps/Street%20Map%20with%20Grid%202012.pdf Street Map] [http://arcgisserv.torringtonct.org/Apps/Zoning%20and%20Land%20Use/ GIS (Zoning)])
*Trumbull ([https://maps.gbrct.org/TrumbullGIS/Viewer.html GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/144fcl.pdf FCL])


== U ==
{| border="1" style="border-collapse:collapse;margin: 1em auto 1em auto; text-align:center"
|+ '''Legend'''
|-
| {{Freeway|Fw}}||{{Freeway}}
|-
| {{Major Highway|Major}}||{{Major Highway}}
|-
| {{Minor Highway|Minor}}||{{Minor Highway}}
|-
| {{Primary Street|PS}}||{{Primary Street}}
|-
| {{Street|Street}}||{{Street}}
|}
</div>


*Union ([http://54.83.239.177/html5viewer/?viewer=neccoggis2 NECCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/145fcl.pdf FCL])
===FC issues by TxDot===
If you find any issues where FC changes unexpectedly such as in the image (the small section of green in between 2 red sections), please let the Texas Regional Coordinator (RC) know exactly where this is located, so TxDOT can be notified.
[[File:FC_issue.png|thumbnail|center]]


== V ==
== Places Locking Standards==
Places should be completed as fully as possible anytime they are created or updated. At a ''minimum'', editors should:
*'''verify correct spelling''' of the name, using the guidelines below
*'''complete the address''', to help when choosing among search results in the app, and
*'''ensure the correct location''' of the Point or Stop Point, to guide drivers to the correct location. Note that this may not always be on the street side of the location.
Phone numbers and opening hours are also particularly helpful to Wazers. Complete them whenever possible, using an online search, if necessary. Photos should help Wazers recognize the destination when they arrive.


*Vernon ([http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/146fcl.pdf FCL])
When completed, places should be locked, to prevent inadvertent damage. Please don't lock places to their highest level until most of their information is completed, but do lock to a level higher than 1, once you have verified ''any'' information, to help protect from accidental damage through client submissions. The following are recommended (minimum) levels:
**Rockville
:4 - Hospitals, universities, park and ride lots, arenas, airports
*Voluntown ([http://54.83.239.177/html5viewer/?viewer=neccoggis2 NECCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/147fcl.pdf FCL])
:4 - Large areas - (State Parks, if mapped, etc.)
:3 - Police Dept / Fire Station and all government buildings
:3 - Gas Station
Most other places should be locked at 3, once completed.


== W ==
==Naming Standards==
We are standardizing the naming of most public facilities and businesses. This makes search results more consistent and useful, and gives Wazers a more professional and uniform experience. The names have been designed to work well with instant search, regular search, and to be clear and concise in the map display. Please follow these guidelines when naming the places described below.


*Wallingford ([http://www.town.wallingford.ct.us/images/customer-files/wlfdmap.pdf Street Map-PDF], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/148fcl.pdf FCL])
Places which are part of a larger area place (e.g. place points for parking lots in a university area, separate ER entrances in a hospital area, etc.) should be named with their unique name followed by a hyphen and the name of the larger area they belong to. For example "ER - Parkland Hospital"
*Warren ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/149fcl.pdf FCL])
*Washington ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/150fcl.pdf FCL])
===Government Agencies===  
*Waterbury ([http://waterburyct.maps.arcgis.com/apps/Viewer/index.html?appid=0e1a5721af9b4f5ca4fe6286abcf4105/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/151fcl.pdf FCL])
*Waterford ([http://wtfd.maps.arcgis.com/home/ GIS], [http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/152fcl.pdf FCL])
*Watertown ([http://107.20.209.214/watertownct_public/default.html GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/153fcl.pdf FCL])
*West Hartford ([http://host.appgeo.com/westhartfordct/Map.aspx GIS], [http://themdc.maps.arcgis.com/apps/webappviewer/index.html?id=4a513162be744e3d87955b0fc0ae87d0 MDC GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/155fcl.pdf FCL])
*West Haven ([http://www.westhavengis.com/ags_map/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/156fcl.pdf FCL])
*Westbrook ([http://www.mapgeo.com/WestbrookCT/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/154fcl.pdf FCL])
*Weston ([http://www.westonct.gov/townhall/27652/28144/28210/386254 PLAT], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/157fcl.pdf FCL])
*Westport ([https://geopower.jws.com/westport/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/158fcl.pdf FCL])
*Wethersfield ([http://themdc.maps.arcgis.com/apps/webappviewer/index.html?id=4a513162be744e3d87955b0fc0ae87d0 MDC GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/159fcl.pdf FCL])
*Willington ([http://willington.mapxpress.net/ags_map/ GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/160fcl.pdf FCL])
*Wilton ([http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/161fcl.pdf FCL])
*Winchester ([http://www.townofwinchester.org/tax-assessor/pages/tax-assessor-maps PLAT], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/162fcl.pdf FCL])
**Winsted
*Windham ([http://host.appgeo.com/sccog/Default.aspx SCCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/163fcl.pdf FCL])
**Willimantic
*Windsor ([http://themdc.maps.arcgis.com/apps/webappviewer/index.html?id=4a513162be744e3d87955b0fc0ae87d0 MDC GIS], [http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/164fcl.pdf FCL])
*Windsor Locks ([http://www.mapgeo.com/crcogct/ CRCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/165fcl.pdf FCL])
*Wolcott ([http://wolcott.mapxpress.net/ags_map/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/166fcl.pdf FCL])
*Woodbridge ([http://woodbridge.mapxpress.net/ags_map/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/167fcl.pdf FCL])
*Woodbury ([http://woodbury.mapxpress.net/ GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/168fcl.pdf FCL])
*Woodstock ([http://54.83.239.177/html5viewer/?viewer=neccoggis2 NECCOG GIS], [http://www.ct.gov/dot/lib/dot/documents/dpolicy/policymaps/fcl/pdf/169fcl.pdf FCL])


{{Anchor|X}}{{Anchor|Y}}{{Anchor|Z}} {{AlphaIndexEnd}}
All places for the following agencies should be named according to the standards as follows:
Source: [http://portal.ct.gov/cities_and_towns/ CT.gov: Towns & Cities in Connecticut]


== Statewide GIS ==
'''City and County Offices''': City or County Name followed by City Hall or department or agency as appropriate, for example:
:"Dallas City Hall"
:"Travis County Probation"
:"Bexar County Courthouse"


*[http://ctecoapp1.uconn.edu/advancedviewer/ CT ECO/DEEP] - Connecticut Environmental Conditions Online (CT ECO) is the collaborative work of the Connecticut Department of Energy and Environmental Protection (DEEP) and the University of Connecticut Center for Land Use Education and Research (CLEAR) to share environmental and natural resource information with the general public. '''NOTE:''' This is not a street map, but it does contain streets. It is a useful resource, but should not be the determining factor when making mapping decisions.
'''Police and Sheriff's Departments''': City, Agency or Division Name followed by "Police Station/Dept" or "Sheriff's Office/Dept" (should match signage), for example:
:"Dallas Police Dept"
:"Austin Police - North Substation "
:"Tarrant County Sheriff's Dept"
:"Travis County Sheriff's Office"


== Regional GIS ==
'''Fire Stations''': Agency Name or abbreviation followed by “Fire Station – “ and the station number. For example:
:"DFD Fire Station - 15"
:"Austin Fire Station - 3"
:"Whitehouse Vol Fire Station - 2"


*[http://themdc.maps.arcgis.com/apps/webappviewer/index.html?id=4a513162be744e3d87955b0fc0ae87d0 The MDC] - Bloomfield, East Hartford, Hartford, Newington, Rocky Hill, West Hartford, Wethersfield, and Windsor
'''Light Rail Stations''': Start with the Agency, which line, followed by the station name. For example:
*[http://www.mapgeo.com/crcogct/ Capitol Region Council of Governments] - Andover, Avon, Berlin, Bloomfield, Bolton, Canton, Columbia, Coventry, East Granby, East Hartford, East Winsor, Ellington, Enfield, Farmington, Glastonbury, Granby, Hartford, Hebron, Manchester, Mansfield, Marlborough, New Britain, Newington, Plainville, Rocky Hill, Simsbury, Somers, South Windsor, Southington, Suffield, Tolland, Vernon, West Hartford, Wethersfield, Willington, Windsor, Windsor Locks
:"DART Rail – Akard Street Station"
*[http://54.83.239.177/html5viewer/?viewer=neccoggis2 Northeast Connecticut Council of Governments] - Ashford, Brooklyn, Canterbury, Chaplin, Eastford, Hampton, Killingly*, Plainfield, Pomfret, Putnam, Scotland, Sterling, Thompson, Union, Voluntown, Woodstock (*Killingly does not participate in the Council's GIS, they have their own, see link above)
:"DART Green Line – Fair Park Station"
*[http://host.appgeo.com/sccog/Default.aspx Southeastern Connecticut Council of Governments] - Bozrah, Colchester, East Lyme, Franklin, Griswold, Groton, Lebanon, Ledyard, Lisbon, Montville, New London, North Stonington, Norwich, Preston, Salem, Sprague, Stonington, Waterford, Windham, Mashantucket Pequot Tribal Nation, Mohegan Tribal Nation
*[http://cogcnvgis.com/ Council of Governments, Central Naugatuck Valley] - Ansonia, Beacon Falls, Bethlehem, Bristol, Cheshire, Derby, Middlebury, Naugatuck, Oxford, Prospect, Seymour, Shelton, Southbury, Thomaston, Waterbury, Watertown, Wolcott, Woodbury '''NOTE:''' This site only provides link to the town specific sites, so the regional link is not listed above.
*[http://www.wincog-gis.org/ Windham Region Council of Governments] '''NO LONGER OPERATIONAL''' - Chaplin, Columbia, Coventry, Hampton, Lebanon, Mansfield, Scotland, Willington, Windham


[[Category:Connecticut]]<br/>[[Category:Make Subpage|Make_Subpage]]
In general, City Bus stops should not be mapped.
 
'''United States Postal Service''': Start the name with CDP or Station name, then append “Post Office”. Place the City name and the ZIP code of the Post Office in the Description box, so it will be viewable in the app GO page.  Alternate name should be “USPS”.  For example:
:"Oak Lawn Post Office"
:"White Rock Station Post Office"
 
Here is the USPS tool to find the names of specific post offices.
https://tools.usps.com/go/POLocatorAction!input.action
 
 
'''US VA Hospitals/Centers/Clinics''': Should be named with their official name as the primary name. For VA hospitals/medical centers "(US Veterans Only)" should be added to the end of the primary name, and as the first line of the description. In the primary name, "VA" should be expanded as "Veterans Affairs", so as not to cause a TTS conflict with Virginia. Names can be shortened to remove extraneous words; for example, replace "Campus of the" from the official name with a hyphen (-). Any colloquial names should be added as alt names, so they are returned in search results, and also at the beginning of the description, so they are visible on the place preview page in the client. Some examples:
:"Veterans Affairs - Healthcare Center at Harlingen (US Veterans Only)"
:"Veterans Medical Clinic - McAllen"
:"Veterans Affairs - North Texas Health Care System (US Veterans Only)"
 
===Gas Stations===
You should familiarize yourself with the [https://wiki.waze.com/wiki/Places/Gas_Station gas stations wiki] - specifically naming, branding, and stop points.
 
== Places ==
 
=== Parking Lots ===
[https://wazeopedia.waze.com/wiki/USA/Places/Parking_lot Parking Lot Wiki Guidance]
 
'''Info for Places'''
 
Please provide as much info about a place as possible. However, '''DO NOT COPY FROM WEBSITES''' as this is plagiarism and will not be tolerated. The most common form is copying straight from Wikipedia. Please refrain from copy/paste anything from websites into the description field. They will be removed when discovered.
 
Recommended phone number formats: (903) 654-3210 or 903-654-3210  | Others may not auto-dial properly in some phones.
 
=== When to use Area or Point in Texas ===
 
Here is the Texas guidance on selecting Area or Point for Places in the Waze Map Editor. '''All areas are to be landmarked from fence line to fence line''' to include all parking lots, roads, and anything associated with the property.
 
{{Red|The Primary Category for a Place is used to determine whether to use a Point or Area.}}
 
{{Red|Lock level should only be set once all details are in place - name, address, hours, phone number, etc.}}
 
{{#widget:Iframe
|url=https://docs.google.com/spreadsheets/d/19IccubJYFHTk4KccyE8cn04Ag3viYMtbG9_AbcBxM1M/pubhtml?gid=0&amp;single=true&amp;widget=true&amp;headers=false"
|width=100%
|height=700
|border=0
}}
 
[//docs.google.com/spreadsheets/d/19IccubJYFHTk4KccyE8cn04Ag3viYMtbG9_AbcBxM1M/pubhtml?gid=0&amp;single=true View this list full-screen in Google Sheets]
 
===Place Name Harmonization===
These name spellings are standardized so that Wazers will receive consistent results when searching in the client. Please use them when you edit one of these chain or franchise businesses.
 
If you don't find the business you're looking for, please  [https://docs.google.com/forms/d/e/1FAIpQLSffod9dqCPA4Km9ZBPOf3HFrbEecKZBqF3ONK_9DV94GKEGmg/viewform?usp=send_form#start=embed '''use this form'''] to submit the missing information.
<br />
'''Fast food chains or businesses that can sometimes be nested inside other businesses should be labeled as such.  For example, if a Starbucks is inside Target or a Subway is inside Walmart, you would list it as ''Starbucks (inside Target)'' or ''Subway (inside Walmart)'' as the primary business name.  This will allow for Wazers searching for a Starbucks or Subway to immediately know they may be routing to a coffee shop or sandwich shop with no drive-thru or standalone business as they may want or expect.'''
<br /><br />
'''Eating / drinking establishments at airports, and known to be inside the secured area, should not be added in Waze.'''
<br /><br />
'''If inside a military installation or area of restricted access, these establishments can be added with the tag of ''(Restricted Access)'' ; McDonald's (Restricted Access).  This will still route Wazers to these businesses but it lets them know they must have the proper credentials to access the location.'''
<br /><br />
'''Apartment complexes will use the category "Lodging" and should be placed at the main office.  Use Office Hours if available'''<br />
'''Assisted Living, Nursing Homes and Hospice will use the category "Lodging" and "Personal Care"'''<BR />
'''Do not map kiosks.  i.e.  RedBox, Stand Alone ATM, Ice Machines''' <br>
<br />
{{#widget:Iframe
|url=https://docs.google.com/spreadsheets/d/1-f-JTWY5UnBx-rFTa4qhyGMYdHBZWNirUTOgn222zMY/pubhtml?gid=213409140&amp;single=true&amp;widget=true&amp;headers=false"
|width=100%
|height=700
|border=0
}}
 
[//docs.google.com/spreadsheets/d/1-f-JTWY5UnBx-rFTa4qhyGMYdHBZWNirUTOgn222zMY/pubhtml?gid=213409140&single=true View this list full-screen in Google Sheets]
 
 
<!--{| border="1" cellpadding="2" width="100%" class="sortable" style="font-size: small;"
|-
! width="23%" style="background-color: rgb(89, 137, 158); color: white;" | Parent
! width="27%" style="background-color: rgb(89, 137, 158); color: white;" | Category
! width="8%" style="background-color: rgb(89, 137, 158); color: white;" | Type
! width="42%" class="unsortable" style="background-color: rgb(89, 137, 158); color: white;" | Comments
|-
| Car Services
| Car Wash
| Point
|
|-
| Car Services
| Charging Station
| Point
|
|-
| Car Services
| Garage / Automotive Shop
| Point
|
|-
| Car Services
| Gas Station
| Area
| Many gas stations also have convenience stores and ATMs. Remember to use "Gas Station" as the primary category and the add any others which are relevant.
|-
| Car Services
| [https://wazeopedia.waze.com/wiki/USA/Places/Parking_lot]
| Both
|-
| Transportation
| Airport
| Area
| Special-handling
|-
| Transportation
| Bridge
| '''NONE'''
|
|-
| Transportation
| Bus Station
| Both
| Greyhound stations are area, city bus stops, point
|-
| Transportation
| Ferry Pier
| Point
|
|-
| Transportation
| Junction / Interchange
| '''NONE'''
|
|-
| Transportation
| Seaport / Marina / Harbor
| Area
| Size-dependent.
|-
| Transportation
| Subway Station
| '''NONE'''
|
|-
| Transportation
| Taxi Station
| Point
|
|-
| Transportation
| Train Station
| Point
|
|-
| Transportation
| Tunnel
| '''NONE'''
|
|-
| Professional and public
| Cemetery
| '''NONE'''
|
|-
| Professional and public
| City Hall
| Area
|
|-
| Professional and public
| College / University
| Area
|
|-
| Professional and public
| Conventions / Event Center
| Area
| Size-dependent
|-
| Professional and public
| Courthouse
| Area
|
|-
| Professional and public
| Embassy / Consulate
| Area
|
|-
| Professional and public
| Factory / Industrial
| '''NONE'''
|
|-
| Professional and public
| Fire Department
| Area
|
|-
| Professional and public
| Government
| Area
|
|-
| Professional and public
| Hospital / Medical Care
| Area
| '''ONLY''' Hospitals, Emergency Rooms, and places offering ''Urgent'' Medical Care should use this category. ERs encompassed in a hospital Place Area should be points.
 
Clinics and Medical offices which ''do not'' offer urgent medical care for Walk-ins should use the Office category (and any other appropriate category) instead.
|-
| Professional and public
| Information Point
| Point
|
|-
| Professional and public
| Kindergarten
| Point
|
|-
| Professional and public
| Library
| Point
|
|-
| Professional and public
| Military
| '''NONE'''
| See below
|-
| Professional and public
| Offices
| Point
|
|-
| Professional and public
| Organization or Association
| Point
|
|-
| Professional and public
| Police Station
| Area
|
|-
| Professional and public
| Prison / Correctional Facility
| '''NONE'''
|
|-
| Professional and public
| Post Office
| Area
|
|-
| Professional and public
| Religious Center
| Area
|
|-
| Professional and public
| School
| Area
|
|-
| Shopping and services
| Arts & Crafts
| Point
|
|-
| Shopping and services
| ATM
| '''NONE'''
|
|-
| Shopping and services
| Bank / Financial
| Point
|
|-
| Shopping and services
| Bookstore
| Point
|
|-
| Shopping and services
| Car Dealership
| Point
| Size-dependent
|-
| Shopping and services
| Car Rental
| Point
|
|-
| Shopping and services
| Convenience Store
| Point
|
|-
| Shopping and services
| Currency Exchange
| Point
|
|-
| Shopping and services
| Department Store
| Point
|
|-
| Shopping and services
| Electronics
| Point
|
|-
| Shopping and services
| Fashion and Clothing
| Point
|
|-
| Shopping and services
| Flowers
| Point
|
|-
| Shopping and services
| Furniture / Home Store
| Point
|
|-
| Shopping and services
| Gifts
| Point
|
|-
| Shopping and services
| Gym / Fitness
| Point
|
|-
| Shopping and services
| Hardware Store
| Point
|
|-
| Shopping and services
| Jewelry
| Point
|
|-
| Shopping and services
| Laundry / Dry Cleaning
| Point
|
|-
| Shopping and services
| Market
| Point
|
|-
| Shopping and services
| Music Store
| Point
|
|-
| Shopping and services
| Personal Care
| Point
|
|-
| Shopping and services
| Pet Store / Veterinarian
| Point
|
|-
| Shopping and services
| Pharmacy
| Point
|
|-
| Shopping and services
| Photography
| Point
|
|-
| Shopping and services
| Shopping Center
| Area
|
|-
| Shopping and services
| Sporting Goods
| Point
|
|-
| Shopping and services
| Supermarket / Grocery
| Point
| Standalone could be an Area, but a Point if it is part of larger shopping mall/center.
|-
| Shopping and services
| Swimming Pool
| Point
|
|-
| Shopping and services
| Toy Store
| Point
|
|-
| Shopping and services
| Travel Agency
| Point
|
|-
| Food and drink
| Bakery
| Point
|
|-
| Food and drink
| Bar
| Point
|
|-
| Food and drink
| Coffee shop
| Point
|
|-
| Food and drink
| Dessert
| Point
|
|-
| Food and drink
| Fast Food
| Point
|
|-
| Food and drink
| Food Court
| Point
|
|-
| Food and drink
| Ice Cream
| Point
|
|-
| Food and drink
| Restaurant
| Point
|
|-
| Culture & entertainment
| Art Gallery
| Point
|
|-
| Culture & entertainment
| Casino
| Area
| There's only one casino in Texas
|-
| Culture & entertainment
| Club
| Point
|
|-
| Culture & entertainment
| Game Club
| Point
|
|-
| Culture & entertainment
| Movie Theater
| Point
|
|-
| Culture & entertainment
| Museum
| Point
|
|-
| Culture & entertainment
| Music Venue
| Point
|
|-
| Culture & entertainment
| Performing Arts Venue
| Point
|
|-
| Culture & entertainment
| Racing Track
| Area
|
|-
| Culture & entertainment
| Stadium / Arena
| Area
|
|-
| Culture & entertainment
| Theme Park
| Area
|
|-
| Culture & entertainment
| Theater
| Point
|
|-
| Culture & entertainment
| Tourist Attraction / Historic Site
| Both
| Size-dependent. If not sure, ask
|-
| Culture & entertainment
| Zoo / Aquarium
| Area
| Size-dependent
|-
| Other
| Construction Site
| '''NONE'''
|
|-
| Other
| Residence / Home
| Point
|
|-
| Lodging
| Bed & Breakfast
| Point
|
|-
| Lodging
| Camping / Trailer Park
| Point
|
|-
| Lodging
| Cottage / Cabin
| Point
|
|-
| Lodging
| Hostel
| Point
|
|-
| Lodging
| Hotel
| Point
|
|-
| Outdoors
| Beach
| '''NONE'''
|
|-
| Outdoors
| Golf Course
| Area
|
|-
| Outdoors
| Park
| Area
|
|-
| Outdoors
| Playground
| Point
|
|-
| Outdoors
| Plaza
| Point
|
|-
| Outdoors
| Promenade
| Point
| Unsure about mapping these at all
|-
| Outdoors
| Scenic Lookout / Viewpoint
| Point
|
|-
| Outdoors
| Ski Area
| '''NONE'''
| Not in Texas
|-
| Outdoors
| Sports Court
| Point
|
|-
| Natural features
| Farm
| '''NONE'''
|
|-
| Natural features
| Forest / Grove
| Area
| Only map official state/national forests, not every stand of trees.
|-
| Natural features
| Island
| '''NONE'''
|
|-
| Natural features
| River / Stream
| '''NONE'''
|
|-
| Natural features
| Sea / Lake / Pond
| '''NONE'''
| <br/>
|}
-->
 
== Texas GIS Websites ==
 
<big>[[Texas/GIS|Texas GIS/CAD Websites]]</big><br />
 
== Major construction projects ==
 
See [http://www.txdot.gov/ TxDot] for a list of '''LONG TERM''' road closures & changes to traffic flow that impact the Waze map.
 
If you are aware or made aware of any long term closures (construction, work closures and emergency closures), please fill out [https://docs.google.com/forms/d/1oGINt4UEkBV0Par5VCingXzTZpJq9KjG8GbZpGqbRow/viewform this form]. Your submission will be reviewed by US Champs and submitted to the Waze team upon approval.
 
==== I-35 (Austin to DFW) ====
 
==== SH-360 Toll Arlington/Grand Prairie/Mansfield ====
The new SH-360 tollway is in progress between I-20 and US-287.  It will include 3-4 mainlanes in each direction along with direct connectors to US-287 in Mansfield.
 
[http://www.drive360south.com/ SH-360 Toll Project Information]
 
[https://www.youtube.com/watch?v=V4X-AVauGco SH-360 Toll Video]
 
==== SH-360 / I-30 Interchange Arlington ====
One of the last relics of the old Dallas-Fort Worth Turnpike, the I-30 / SH-360 interchange, is getting a makeover.  It will be upgraded to a four level stack interchange with continuous frontage roads on SH-360 and a reconfiguration of Six Flags Dr.
 
[https://www.keep30360moving.org/ I-30 / SH-360 Interchange Project Information]
 
[https://www.youtube.com/watch?v=yPFjiH8xYQM I-30 / SH-360 Interchange Video]
 
==== I-35W Fort Worth (North Tarrant Express) ====
I-35W is being reconstructed from downtown Fort Worth to US-287.  The new configuration will include tolled express lanes along with upgraded interchanges at SH-121, I-820 and US-287.
 
[http://www.northtarrantexpress.com/ North Tarrant Express Main Page]
 
[http://www.northtarrantexpress.com/LaneClosuresNew.asp North Tarrant Express - Lane Closures]
 
==== I-35E Dallas to Denton (35 Express) ====
Thirty miles of I-35E is being rebuilt from I-635 in Dallas to US-380 in Denton.  It will include two tolled reversible express lanes, new interchanges at FM 407 and Belt Line Rd and new bridges across Lake Lewisville.
 
[http://www.35express.org/ 35 Express Main Page]
 
[http://www.35express.org/traffic.php 35 Express - Lane Closures]
 
==== SH-183 / SH-114 / Loop 12 (Midtown Express) ====
The express lanes on SH-183 (Bedford) and SH-114 (Grapevine) will be extended eastward through Irving and past the SH-183/SH-114 merge into Dallas.  Express lanes will also be extend on Loop 12 from I-35E to SH-183 in Irving. 
 
[http://drivemidtown.com/ Midtown Express Main Page]
 
[http://drivemidtown.com/know/closures-and-traffic-pattern-changes/ Midtown Express - Lane Closures]
 
==== SH-121 / SH-114 / SH-360 / I-635 Grapevine (DFW Connector) ====
Primary DFW Connector construction is complete, but more improvements to the connector are still in progress including the SH-121 / SH-360 interchange upgrade.
 
[http://www.dfwconnector.com/ DFW Connector Main Page]
 
[http://www.dfwconnector.com/laneclosures.php DFW Connector - Lane Closures]
 
== Cameras ==
 
Currently, the only way to add cameras to the editor are from the app. When placing a camera in the app, drop a general error with "RLC W" where W = the direction the camera is facing. This will allow other editors to know which way the camera is facing when they go to approve it in the editor.
 
=== Red light cameras ===
 
Red Light Cameras are '''LEGAL''' in the State of Texas.
 
Contrary to popular belief, these cameras do not sit on the top of lights at an intersection. If you've gotten to an intersection, you've already passed the red light camera.These cameras mounted on traffic signals are used as part of the signal control. These compare sequential images of the intersection approach to determine if there is a vehicle (car, truck, motorcycle, bicycle, etc) waiting and will trigger the sequence. These devices '''CANNOT''' issue tickets.
 
There are traditional traffic monitoring cameras covering most of the major highways in the state. These send live feeds to the various traffic agencies around the state and are for monitoring traffic only.
 
*[[Cameras|Know your Cameras]]
 
=== Speed Cameras ===
 
Speed cameras are currently '''ILLEGAL''' in the State of Texas. Any request for a speed camera, or any approved speed cameras need to be removed from the map.
 
==Speed Limits==
 
[[Speed limits/USA|Click to view the USA Speed Limits Wiki Page]]
 
=== {{@|Where speed limits change}} ===
 
Speed limits should change where they legally go in effect for your state, that may be at the sign, a specified distance before the sign, or the nearest intersection. When a speed limit changes in the middle of a segment, {{u|a new junction should be added to support the SL change}}.
* However '''a new junction should never be added for a SL if it will be within 200 feet of an existing junction''', or potential junction.
* A new junction should always be added if it will be more than 1,000 feet from the nearest existing, or potential junction.
 
=== {{@|Creating a new junction for a speed limit change}} ===
 
When creating a new junction solely for the sake of showing a speed limit change, you can attempt to get more value from the junction. Survey the area around the speed limit change, determine if there is a PLR or other segment which should be connected to the road and would result in a junction. You may find that there's a parking lot which could benefit from being added to the map within the allowable distance of 200 feet (or more depending on your area) to where the SL changes. In such a case connect that segment and use that junction. Otherwise you should create a new junction to show where the SL changes.
 
On roads where traffic for one turn direction typically backs up waiting to make the turn further than 200 feet, and traffic going straight or turning the other direction does not have to wait as long to pass through, turn delays can be affected even with the new junction 200 feet away. In these cases you may choose to extend the buffer zone to beyond the point where traffic backs up, and instead make the change at an existing junction node. These situations are governed by editor discretion and local guidance.
 
{{expand|nt=yes|
It is very important that we do not create new junctions too close to existing intersections, yet marking the speed limit change too far can have a negative impact on the user experience.
 
The minimum distance of 200 feet was chosen because a distance less than that is negligible, and unnoticeable in the client experience. It is not much different than the delay we expect with GPS lag and error anyway. For example think of where you hear the turn prompts announced, they can sometimes precede a junction by up to 200 feet.
 
We have confirmed directly with the routing developers that adding a junction node connecting only 2 segments does not have an associated [[routing penalty]]. We have also confirmed that creating and adding new junction nodes where necessary using these above guidelines will not have a negative effect on route calculation.
 
However there is a legitimate concern when adding new junctions too close to existing intersections / interchanges, that they may interfere with and pollute the ability for Waze calculate accurate [[turn delays]].
 
The reason to use a minimum of 200 feet from the nearest junction as a buffer is to account for turn delay calculations.
If we create junction nodes very close to intersections we will effectively eliminate Waze's ability to differentiate the time it takes to go straight, vs the time to turn left or right. {{u|A distance of less than 200 feet between junctions poses a significant risk to the ETA calculations (turn delays).}} Over 200 feet it is up to local practice , and the editor's discretion to determine if a junction node there will negatively impact turn delay calculations. We must stipulate a minimum buffer zone, but it doesn't need to be exact. The area between 200-1,000 feet is open to interpretation, editor discretion, and local guidance.
 
If an exit or turn lane does back up over 1,000 feet, it is unlikely that traffic beyond the 1,000 mark will be drastically affected by the new junction placed that far away. ''However specific exceptions with the consultation of Regional Coordinators, or State Managers will always be allowed.''
 
: The turn delay issue could potentially be mitigated by adding [[User:CBenson/Junction_Box|Junction Boxes]] to each of these situations to correct them. However doing so would result in a lot more work for editors, and a lot more strain on the servers. It would make it harder to manage these intersections since all the included segments, and turns get locked from editing. It will have an effect on route calculation timing as well. We therefore had to come up with a compromise that is still visibly accurate, without anything being noticeably different to the client user, yet maintaining the ability for Waze to calculate proper ETA timing through intersections.
| the rationale behind these rules.}}
 
[[File:Mbox construction yellow.png|120px|right]]
[[File:Work zone SL.png|120px|right|Work Zone Speed Limit sign]]
=== {{@|Work zones}} ===
Speed limits in work zones are often lowered to protect workers and prevent collisions. If these speed limits appear on regulatory black and white signs, they '''MAY''' be added to the associated WME road segments. '''Speed limits should only be changed in work zones when the change will be in effect for at least 30 days.'''
Add the construction zone speed limit to the affected segments and place a [CONSTRUCTION] note on the map listing the official speed limit so when construction is complete, an editor can easily reset the speed limit.
 
== Military Bases ==
 
Texas has a long-standing tradition for support the US military. If you have questions concerning any military base in the state, please do not hesitate to ask. All military bases in the state are set to the current [[Military Bases|installation]] standard.
 
*All gates at the military bases are set to private road in/street out with some gates having restrictions on them for the various gate closures.
*If you know of any changes in the hours of a gate, please let a US Champ know and they will adjust it accordingly.
*All gates are locked at a level 5.
 
Landmarks approved for military bases are:
 
*Commissary
*PX/BX
*Gas stations
*Parks
*Museums
 
== To do list ==
 
Want to help out with the map in Texas? Add missing streets, Solve [[Update requests|URs]], ask questions to anyone listed below, and seek out advice when/where needed. Please adhere to the rules for editing.
 
'''''Upcoming Construction Projects'''''
 
== Mapping utilities ==
 
*[http://www.txdot.gov/apps/statewide_mapping/StatewidePlanningMap.html TxDot Maps]
*[http://www.drivetexas.org Road Conditions] throughout the state.
*[http://en.wikipedia.org/wiki/Texas_state_highways List] of State Routes in Texas
 
== Editors in the State ==
 
<center>
{{#widget:Iframe
|url=https://docs.google.com/spreadsheets/d/1Mtelh237DkIsko2h59IKpsBJ4HngxEGMbcPTC-59kTI/pubhtml?gid=0&amp;single=true&amp;widget=true&amp;headers=false"
|width=65%
|height=700
|border=0
}}
</center>
 
 
If you are an editor in Texas, or a USA Country Manager that does a lot of work in Texas, please ask to be added.
 
[//docs.google.com/spreadsheets/d/1Mtelh237DkIsko2h59IKpsBJ4HngxEGMbcPTC-59kTI/edit?usp=sharing/pubhtml View this list full-screen in Google Sheets]
 
== Discipline ==
 
Waze has been designed to be an open community with various levels of editors. Rank 5 and 6 editors are senior editors. They are here to help you and are to be respected at all times. Instructions from senior editors are to be followed, unless it conflicts with this page. If you have any questions or issues, please feel free to PM one of the rank 6s or 5s in the list (if you're having a problem with one, please PM the regional coordinators). We will try to handle the issue as quickly and peacefully as possible.
 
You may want to check [https://wiki.waze.com/wiki/Common_editing_mistakes common editing mistakes] to see if you are editing properly. Although It is not possible to list every occurrence of problems which can occur in the editor, the following are some examples of what has happened in the past:
<ul style="/* insecure input */">
<li>Deleting and redrawing roads</li>
<li>Creating mass amounts of parking lot roads</li>
<li>Creating roads on top of already existing roads</li>
<li>Disrespect to higher ranking editors</li>
<li>Not cleaning up your own mess</li>
<li>Not responding to private messages in a timely manner (usually 48 hours)</li>
<li>Willful damage to the map</li>
<li>Editing just to clear geometry nodes will result in an instant blocking of your editing rights</li>
</ul>
 
Everyone is allowed one free pass, but disciplinary actions after the first occurrence for the above may include:
<ul style="/* insecure input */">
<li>Formal mentoring</li>
<li>Temporary suspension of editing rights</li>
<li>Permanent suspension of editing rights</li>
</ul>
 
==User Reports (URs)==
 
[[Update Requests in Waze Map Editor]]
 
Texas editors: As of 9/2/16, the waiting time for responses to Speed Limit URs (SLURs) has been reduced from 7 days to 3 days.  This only applies to SLURs.

Revision as of 13:59, 16 February 2017

Below you will find information related to using Waze in the State of Texas. All editors in the state are required to have a non usa_username, have their private messaging turned on, and turn live users on in the layers menu. Do not edit in Invisible mode if you are a rank 3 or below. Please pay attention to the chat window in the lower right-hand part the map editor (and introduce yourself if you're a first-time editor). You can find useful info there and ask questions. You can also find useful information at the Texas forum page. You can also join Slack and chat with Texas editors, as well as the state managers (SM) and regional coordinator (RC). Once you receive the Slack invitation, login and join the #texas channel.

Cities and towns

There are 6386 Cities and Towns spread across 254 counties in the state. See Cities in Texas for proper naming information.

City names should be everything inside of the city limits. City limits are clearly defined by the green signs. Use of Google Maps to find where a city is highly discouraged.

Roads in Texas

Road naming

Interstates = I-XX
US Highway = US-XX
State Highway = SH-XX
State Loop = Loop XX
State Spur = Spur XX
State Park Road = Park Rd XX
State Recreational Road = Recreational Rd XX
Farm/Ranch to Market = FM/RM XX
County Road = CR-XX
Private Road = Private Rd XX

Business Roads

All business roads should be suffixed with BUS:
Business Interstate = I-XX BUS
Business US Highway = US-XX BUS

Road Naming Abbreviations & Suffixes

Interstates throughout the state

  • I-2 Rio Grande Valley
  • I-10 New Mexico to Louisiana
  • I-20 Midland/Odessa to Louisiana
  • I-27 Lubbock to Amarillo
  • I-30 Fort Worth to Arkansas
  • I-35 Mexico to Oklahoma
  • I-35E Hillsboro to Denton through Dallas
  • I-35W Hillsboro to Denton through Fort Worth
  • I-37 Corpus Christi to San Antonio
  • I-40 New Mexico to Oklahoma
  • I-45 Galveston to Dallas
  • I-69 Brownsville/Edinburg/Laredo to Texarkana (will follow US-59)
  • I-369 Spur to west side of Texarkana
  • I-410 Loop around San Antonio
  • I-610 Loop around Houston
  • I-635 Spur through DFW Metroplex
  • I-820 Loop around Fort Worth 

Special roads

  • When not to divide a two-way road
  • Divided Roads
  • Carpool, HOV, Transit lanes
  • Roundabouts and Traffic Circles
  • Cul-de-sacs
  • Dirt Roads. In Texas ALL roads that are unpaved or gravel are considered dirt roads as this is how GPS Nav users (any brand) expect the "Avoid Dirt Roads" feature to behave. These roads should be deleted when going through farm land, ranch land, or mountainous areas throughout the state, as they are most likely base import roads and not real roads. For roads which are labeled with names and are actually dirt on SATIMG, please keep these and make them dirt roads.
  • Parking Lot Roads
  • Toll Roads
  • Frontage roads Name as "Frontage Rd" unless the corresponding highway has an alternate name. I-635 Frontage roads are labeled as "Lyndon B Johnson Freeway" as that is the local name for I-635.
  • Alleys and driveways are NOT MAPPED
  • Any road which is a main road for a state park can be a  Primary Street . Other roads can be  Street .

Non-drivable roads

Generally, if a road can't be driven on (e.g. Walking Trail, Pedestrian Boardwalk, Stairway, Ranch road in the middle of nowhere) then it should not be mapped in Waze. This is due to the way the routing engine works, as Waze WILL route users to drive on these "Non-Drivable" road types.

Railroads mapped in Texas should follow the current standard of editing. All crossings should be connected to drivable segments accordingly. If no crossing exists, elevate the segment accordingly.

ONLY enter a name for the railroad segment if the tracks are historical in nature, a major landmark, or a routine destination for Wazers. In TX, very few segments should be named and most 'routine destinations' will be covered by a Place point/area for the train station.

The Waze app now renders railroad tracks as such so naming serves little purpose any longer.

Miscellaneous

U-turns are labeled as "Turnaround" and set to whatever type identified in FC (if not typed in FC, match it to the lowest road type that it touches - similar to AGCs).

Road Lock Standards

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.

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

Functional Classification of Roads

See Road names/USA and Road types/USA.

Texas participates in functional classification across the entire state. We promote a hybrid FC to ensure for the best routing possible for all Wazers. The hybrid FC basically means a state highway would never be typed less than Minor Highway (mH).

Frontage roads along Freeways should be matched to FC. If FC does not list the frontage road, type it as a Primary Street.

Turnarounds (those labeled as Turnaround, not cross-overs), should be matched to FC. If FC does not list the Turnaround, match it to the lowest road type that it touches - similar to AGCs.

FC cross reference

Refer to this chart to determine the road type of a given paved public road based on the functional class.

To use this chart, first determine the functional class of a road, and whether it is a signed, numbered highway in a particular highway system.

Where the column for the road's highway system and the row for the road's functional class meet, you will find the proper road type for that particular road.

A number of examples are given below the chart.


Highway Systems
Interstate Interstate Business Loop/Spur US Hwy (incl. some special routes) US Hwy BUS, SPUR, LOOP State Hwy (incl. some special routes) State Hwy BUS, SPUR[a], LOOP, Frontage Rd FM / County Route Locally-maintained
example I-10 E I-94 Business US-190 US-460 Business SR-23 SR-400 Loop FM 40 / CR-15 Robertson St
F
u
n
c
t
i
o
n
a
l

C
l
a
s
s
Interstate[b]  Fw  n/a n/a n/a n/a n/a n/a n/a
Other Freeway[c] n/a  Fw   Fw   Fw   Fw   Fw   Fw   Fw 
Other Expressway[d] n/a  Major   Major   Major   Major   Major   Major   Major 
Other Principal Arterial[e] n/a  Major   Major   Major   Major   Major   Major   Major 
Minor Arterial[f] n/a  Major   Major   Minor   Minor   Minor   Minor   Minor 
Major Collector n/a  Major   Major   Minor   Minor   PS   PS   PS 
Minor Collector n/a  Major   Major   Minor   Minor   PS   PS   PS 
Local/not mapped n/a  Major   Major   Minor   Minor   PS   Street   Street 

^a When a state highway "SPUR" route is used to connect a state highway with another state highway, a US highway, or an Interstate (i.e., when it is used as a connector/CONN route), use the first state highway column.

^b Also known as Principal Arterial - Interstate.

^c Also known as Principal Arterial - Freeway.

^d Also known as Principal Arterial - Expressway.

^e Also known as Principal Arterial.

^f Also known as Other Arterial.


For example,

  • An Interstate Business Loop classified as a Minor Arterial is a  Major Highway .
  • A US Highway classified as a Minor Arterial is a  Major Highway .
  • A US Highway Spur route classified as a Minor Arterial is a  Minor Highway .
  • A State Highway classified as an Other Freeway is a  Freeway .
  • A State Highway classified as a Collector is a  Minor Highway .
  • A County Route classified as a Minor Arterial is a  Minor Highway .
  • A County Route classified as a Collector is a  Primary Street 
  • A locally-maintained road classified as an Other Principal Arterial is a  Major Highway .
  • A locally-maintained road classified as a Collector is a  Primary Street .


Legend
 Fw   Freeway 
 Major   Major Highway 
 Minor   Minor Highway 
 PS   Primary Street 
 Street   Street 

FC issues by TxDot

If you find any issues where FC changes unexpectedly such as in the image (the small section of green in between 2 red sections), please let the Texas Regional Coordinator (RC) know exactly where this is located, so TxDOT can be notified.

Places Locking Standards

Places should be completed as fully as possible anytime they are created or updated. At a minimum, editors should:

  • verify correct spelling of the name, using the guidelines below
  • complete the address, to help when choosing among search results in the app, and
  • ensure the correct location of the Point or Stop Point, to guide drivers to the correct location. Note that this may not always be on the street side of the location.

Phone numbers and opening hours are also particularly helpful to Wazers. Complete them whenever possible, using an online search, if necessary. Photos should help Wazers recognize the destination when they arrive.

When completed, places should be locked, to prevent inadvertent damage. Please don't lock places to their highest level until most of their information is completed, but do lock to a level higher than 1, once you have verified any information, to help protect from accidental damage through client submissions. The following are recommended (minimum) levels:

4 - Hospitals, universities, park and ride lots, arenas, airports
4 - Large areas - (State Parks, if mapped, etc.)
3 - Police Dept / Fire Station and all government buildings
3 - Gas Station

Most other places should be locked at 3, once completed.

Naming Standards

We are standardizing the naming of most public facilities and businesses. This makes search results more consistent and useful, and gives Wazers a more professional and uniform experience. The names have been designed to work well with instant search, regular search, and to be clear and concise in the map display. Please follow these guidelines when naming the places described below.

Places which are part of a larger area place (e.g. place points for parking lots in a university area, separate ER entrances in a hospital area, etc.) should be named with their unique name followed by a hyphen and the name of the larger area they belong to. For example "ER - Parkland Hospital"

Government Agencies

All places for the following agencies should be named according to the standards as follows:

City and County Offices: City or County Name followed by City Hall or department or agency as appropriate, for example:

"Dallas City Hall"
"Travis County Probation"
"Bexar County Courthouse"

Police and Sheriff's Departments: City, Agency or Division Name followed by "Police Station/Dept" or "Sheriff's Office/Dept" (should match signage), for example:

"Dallas Police Dept"
"Austin Police - North Substation "
"Tarrant County Sheriff's Dept"
"Travis County Sheriff's Office"

Fire Stations: Agency Name or abbreviation followed by “Fire Station – “ and the station number. For example:

"DFD Fire Station - 15"
"Austin Fire Station - 3"
"Whitehouse Vol Fire Station - 2"

Light Rail Stations: Start with the Agency, which line, followed by the station name. For example:

"DART Rail – Akard Street Station"
"DART Green Line – Fair Park Station"

In general, City Bus stops should not be mapped.

United States Postal Service: Start the name with CDP or Station name, then append “Post Office”. Place the City name and the ZIP code of the Post Office in the Description box, so it will be viewable in the app GO page. Alternate name should be “USPS”. For example:

"Oak Lawn Post Office"
"White Rock Station Post Office"

Here is the USPS tool to find the names of specific post offices. https://tools.usps.com/go/POLocatorAction!input.action


US VA Hospitals/Centers/Clinics: Should be named with their official name as the primary name. For VA hospitals/medical centers "(US Veterans Only)" should be added to the end of the primary name, and as the first line of the description. In the primary name, "VA" should be expanded as "Veterans Affairs", so as not to cause a TTS conflict with Virginia. Names can be shortened to remove extraneous words; for example, replace "Campus of the" from the official name with a hyphen (-). Any colloquial names should be added as alt names, so they are returned in search results, and also at the beginning of the description, so they are visible on the place preview page in the client. Some examples:

"Veterans Affairs - Healthcare Center at Harlingen (US Veterans Only)"
"Veterans Medical Clinic - McAllen"
"Veterans Affairs - North Texas Health Care System (US Veterans Only)"

Gas Stations

You should familiarize yourself with the gas stations wiki - specifically naming, branding, and stop points.

Places

Parking Lots

Parking Lot Wiki Guidance

Info for Places

Please provide as much info about a place as possible. However, DO NOT COPY FROM WEBSITES as this is plagiarism and will not be tolerated. The most common form is copying straight from Wikipedia. Please refrain from copy/paste anything from websites into the description field. They will be removed when discovered.

Recommended phone number formats: (903) 654-3210 or 903-654-3210 | Others may not auto-dial properly in some phones.

When to use Area or Point in Texas

Here is the Texas guidance on selecting Area or Point for Places in the Waze Map Editor. All areas are to be landmarked from fence line to fence line to include all parking lots, roads, and anything associated with the property.

The Primary Category for a Place is used to determine whether to use a Point or Area.

Lock level should only be set once all details are in place - name, address, hours, phone number, etc.

View this list full-screen in Google Sheets

Place Name Harmonization

These name spellings are standardized so that Wazers will receive consistent results when searching in the client. Please use them when you edit one of these chain or franchise businesses.

If you don't find the business you're looking for, please use this form to submit the missing information.
Fast food chains or businesses that can sometimes be nested inside other businesses should be labeled as such. For example, if a Starbucks is inside Target or a Subway is inside Walmart, you would list it as Starbucks (inside Target) or Subway (inside Walmart) as the primary business name. This will allow for Wazers searching for a Starbucks or Subway to immediately know they may be routing to a coffee shop or sandwich shop with no drive-thru or standalone business as they may want or expect.

Eating / drinking establishments at airports, and known to be inside the secured area, should not be added in Waze.

If inside a military installation or area of restricted access, these establishments can be added with the tag of (Restricted Access) ; McDonald's (Restricted Access). This will still route Wazers to these businesses but it lets them know they must have the proper credentials to access the location.

Apartment complexes will use the category "Lodging" and should be placed at the main office. Use Office Hours if available
Assisted Living, Nursing Homes and Hospice will use the category "Lodging" and "Personal Care"
Do not map kiosks. i.e. RedBox, Stand Alone ATM, Ice Machines

View this list full-screen in Google Sheets


Texas GIS Websites

Texas GIS/CAD Websites

Major construction projects

See TxDot for a list of LONG TERM road closures & changes to traffic flow that impact the Waze map.

If you are aware or made aware of any long term closures (construction, work closures and emergency closures), please fill out this form. Your submission will be reviewed by US Champs and submitted to the Waze team upon approval.

I-35 (Austin to DFW)

SH-360 Toll Arlington/Grand Prairie/Mansfield

The new SH-360 tollway is in progress between I-20 and US-287. It will include 3-4 mainlanes in each direction along with direct connectors to US-287 in Mansfield.

SH-360 Toll Project Information

SH-360 Toll Video

SH-360 / I-30 Interchange Arlington

One of the last relics of the old Dallas-Fort Worth Turnpike, the I-30 / SH-360 interchange, is getting a makeover. It will be upgraded to a four level stack interchange with continuous frontage roads on SH-360 and a reconfiguration of Six Flags Dr.

I-30 / SH-360 Interchange Project Information

I-30 / SH-360 Interchange Video

I-35W Fort Worth (North Tarrant Express)

I-35W is being reconstructed from downtown Fort Worth to US-287. The new configuration will include tolled express lanes along with upgraded interchanges at SH-121, I-820 and US-287.

North Tarrant Express Main Page

North Tarrant Express - Lane Closures

I-35E Dallas to Denton (35 Express)

Thirty miles of I-35E is being rebuilt from I-635 in Dallas to US-380 in Denton. It will include two tolled reversible express lanes, new interchanges at FM 407 and Belt Line Rd and new bridges across Lake Lewisville.

35 Express Main Page

35 Express - Lane Closures

SH-183 / SH-114 / Loop 12 (Midtown Express)

The express lanes on SH-183 (Bedford) and SH-114 (Grapevine) will be extended eastward through Irving and past the SH-183/SH-114 merge into Dallas. Express lanes will also be extend on Loop 12 from I-35E to SH-183 in Irving.

Midtown Express Main Page

Midtown Express - Lane Closures

SH-121 / SH-114 / SH-360 / I-635 Grapevine (DFW Connector)

Primary DFW Connector construction is complete, but more improvements to the connector are still in progress including the SH-121 / SH-360 interchange upgrade.

DFW Connector Main Page

DFW Connector - Lane Closures

Cameras

Currently, the only way to add cameras to the editor are from the app. When placing a camera in the app, drop a general error with "RLC W" where W = the direction the camera is facing. This will allow other editors to know which way the camera is facing when they go to approve it in the editor.

Red light cameras

Red Light Cameras are LEGAL in the State of Texas.

Contrary to popular belief, these cameras do not sit on the top of lights at an intersection. If you've gotten to an intersection, you've already passed the red light camera.These cameras mounted on traffic signals are used as part of the signal control. These compare sequential images of the intersection approach to determine if there is a vehicle (car, truck, motorcycle, bicycle, etc) waiting and will trigger the sequence. These devices CANNOT issue tickets.

There are traditional traffic monitoring cameras covering most of the major highways in the state. These send live feeds to the various traffic agencies around the state and are for monitoring traffic only.

Speed Cameras

Speed cameras are currently ILLEGAL in the State of Texas. Any request for a speed camera, or any approved speed cameras need to be removed from the map.

Speed Limits

Click to view the USA Speed Limits Wiki Page

Where speed limits change link to this section

Speed limits should change where they legally go in effect for your state, that may be at the sign, a specified distance before the sign, or the nearest intersection. When a speed limit changes in the middle of a segment, a new junction should be added to support the SL change.

  • However a new junction should never be added for a SL if it will be within 200 feet of an existing junction, or potential junction.
  • A new junction should always be added if it will be more than 1,000 feet from the nearest existing, or potential junction.

Creating a new junction for a speed limit change link to this section

When creating a new junction solely for the sake of showing a speed limit change, you can attempt to get more value from the junction. Survey the area around the speed limit change, determine if there is a PLR or other segment which should be connected to the road and would result in a junction. You may find that there's a parking lot which could benefit from being added to the map within the allowable distance of 200 feet (or more depending on your area) to where the SL changes. In such a case connect that segment and use that junction. Otherwise you should create a new junction to show where the SL changes.

On roads where traffic for one turn direction typically backs up waiting to make the turn further than 200 feet, and traffic going straight or turning the other direction does not have to wait as long to pass through, turn delays can be affected even with the new junction 200 feet away. In these cases you may choose to extend the buffer zone to beyond the point where traffic backs up, and instead make the change at an existing junction node. These situations are governed by editor discretion and local guidance.

Click Expand for details on the rationale behind these rules.

It is very important that we do not create new junctions too close to existing intersections, yet marking the speed limit change too far can have a negative impact on the user experience.

The minimum distance of 200 feet was chosen because a distance less than that is negligible, and unnoticeable in the client experience. It is not much different than the delay we expect with GPS lag and error anyway. For example think of where you hear the turn prompts announced, they can sometimes precede a junction by up to 200 feet.

We have confirmed directly with the routing developers that adding a junction node connecting only 2 segments does not have an associated routing penalty. We have also confirmed that creating and adding new junction nodes where necessary using these above guidelines will not have a negative effect on route calculation.

However there is a legitimate concern when adding new junctions too close to existing intersections / interchanges, that they may interfere with and pollute the ability for Waze calculate accurate turn delays.

The reason to use a minimum of 200 feet from the nearest junction as a buffer is to account for turn delay calculations. If we create junction nodes very close to intersections we will effectively eliminate Waze's ability to differentiate the time it takes to go straight, vs the time to turn left or right. A distance of less than 200 feet between junctions poses a significant risk to the ETA calculations (turn delays). Over 200 feet it is up to local practice , and the editor's discretion to determine if a junction node there will negatively impact turn delay calculations. We must stipulate a minimum buffer zone, but it doesn't need to be exact. The area between 200-1,000 feet is open to interpretation, editor discretion, and local guidance.

If an exit or turn lane does back up over 1,000 feet, it is unlikely that traffic beyond the 1,000 mark will be drastically affected by the new junction placed that far away. However specific exceptions with the consultation of Regional Coordinators, or State Managers will always be allowed.

The turn delay issue could potentially be mitigated by adding Junction Boxes to each of these situations to correct them. However doing so would result in a lot more work for editors, and a lot more strain on the servers. It would make it harder to manage these intersections since all the included segments, and turns get locked from editing. It will have an effect on route calculation timing as well. We therefore had to come up with a compromise that is still visibly accurate, without anything being noticeably different to the client user, yet maintaining the ability for Waze to calculate proper ETA timing through intersections.
Work Zone Speed Limit sign
Work Zone Speed Limit sign

Work zones link to this section

Speed limits in work zones are often lowered to protect workers and prevent collisions. If these speed limits appear on regulatory black and white signs, they MAY be added to the associated WME road segments. Speed limits should only be changed in work zones when the change will be in effect for at least 30 days. Add the construction zone speed limit to the affected segments and place a [CONSTRUCTION] note on the map listing the official speed limit so when construction is complete, an editor can easily reset the speed limit.

Military Bases

Texas has a long-standing tradition for support the US military. If you have questions concerning any military base in the state, please do not hesitate to ask. All military bases in the state are set to the current installation standard.

  • All gates at the military bases are set to private road in/street out with some gates having restrictions on them for the various gate closures.
  • If you know of any changes in the hours of a gate, please let a US Champ know and they will adjust it accordingly.
  • All gates are locked at a level 5.

Landmarks approved for military bases are:

  • Commissary
  • PX/BX
  • Gas stations
  • Parks
  • Museums

To do list

Want to help out with the map in Texas? Add missing streets, Solve URs, ask questions to anyone listed below, and seek out advice when/where needed. Please adhere to the rules for editing.

Upcoming Construction Projects

Mapping utilities

Editors in the State


If you are an editor in Texas, or a USA Country Manager that does a lot of work in Texas, please ask to be added.

View this list full-screen in Google Sheets

Discipline

Waze has been designed to be an open community with various levels of editors. Rank 5 and 6 editors are senior editors. They are here to help you and are to be respected at all times. Instructions from senior editors are to be followed, unless it conflicts with this page. If you have any questions or issues, please feel free to PM one of the rank 6s or 5s in the list (if you're having a problem with one, please PM the regional coordinators). We will try to handle the issue as quickly and peacefully as possible.

You may want to check common editing mistakes to see if you are editing properly. Although It is not possible to list every occurrence of problems which can occur in the editor, the following are some examples of what has happened in the past:

  • Deleting and redrawing roads
  • Creating mass amounts of parking lot roads
  • Creating roads on top of already existing roads
  • Disrespect to higher ranking editors
  • Not cleaning up your own mess
  • Not responding to private messages in a timely manner (usually 48 hours)
  • Willful damage to the map
  • Editing just to clear geometry nodes will result in an instant blocking of your editing rights

Everyone is allowed one free pass, but disciplinary actions after the first occurrence for the above may include:

  • Formal mentoring
  • Temporary suspension of editing rights
  • Permanent suspension of editing rights

User Reports (URs)

Update Requests in Waze Map Editor

Texas editors: As of 9/2/16, the waiting time for responses to Speed Limit URs (SLURs) has been reduced from 7 days to 3 days. This only applies to SLURs.