User:PesachZ/SyncScratch View history

Wazeopedia Global Page
VisualWikitext
m (Copying text of wiki page for coparison with the "Wisconsin/Major roads/Main" page)
m (Copying text of wiki page for coparison with the "Connected Citizens Program" page)
Line 1: Line 1:
<!-- This page is only transcluded into (displayed on) the main page for this state. See more detailed instructions below. --><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--
<!--if the section parameter is defined, do not place the visible banner, only as the code block for the top of a section-->{{GlobalMark/visible}}
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>  
<!--
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-----
####    This page has been curated  ####
####    to be included in the new    ####
####    Wazeopedia - GLOBAL Wiki.  ####
####    Please do not make any      ####
####    edits on this page without  ####
####    PRIOR CONSENSUS in the Wiki  ####
####    Updates and Discussions      ####
####    forum thread for this page.  ####
####    If a specific forum thread  ####
####    for this page doesn't exist  ####
####    please start one.            ####
####        www.waze.com/forum/     ####
####        viewforum.php?f=276      ####
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-->


=== Functional Classifications ===
The Waze Connected Citizens program, also known as CCP brings cities and citizens together to answer the questions “What’s happening, and where?” We exchange publicly available incident and road closure reports, enabling our government partners to respond more immediately to accidents and congestion on their roads. In turn, we aggregate our partners' data on the Waze platform, resulting in one of the most succinct, thorough overviews of current road conditions today.  
Wisconsin follows the [[National_resources/USA/Functional_classification|Functional Classification]] (FC) system for the USA.


To help update the current Wisconsin roadways to the new functional classifications, go to the [[Wisconsin/Resources|Wisconsin Functional Classification Inventory]].
With the addition of city data, Wazers will be even safer on the roads and more knowledgeable about construction, marathons, floods or anything else that can cause delays. And for our government partners, publicly-available Waze data is a powerful tool to build more efficient cities. Real-time information from drivers is essential; no one knows more about what's happening in a city than the people who live there. In an era with smart phones, smart cars and smart homes, isn't it about time we start building smarter cities?
<br /><small>Links to the FC maps for the state of Wisconsin can be found on the [[{{BasePage2}}/Resources]] page.</small>




==== Minimum Road Lock Standard ====
==Details==
{| class="wikitable" style="text-align:center"
The mission of Waze Connected Citizens is to help Wazers, cities and citizens collaborate to improve their community and answer the question "What's happening on our roads right now, and where?" The program promotes more efficient traffic monitoring by sharing crowdsourced incident reports from Waze drivers. Established as a two-way data share, Waze receives partner input such as feeds from road sensors, adds publicly available incident and road closure reports from the Waze traffic platform and returns one of the most succinct, thorough overviews of current road conditions today.
!colspan="3" style="background-color:#6699cc"|Minimum Road Lock Standard
|-
|style="font-weight:bold; background-color:#ccffcc"|Segment Type
|style="font-weight:bold; background-color:#ccffcc"|Direction
|style="font-weight:bold; background-color:#ccffcc"|Level
|-
|{{Freeway|Freeway}}
|
|5
|-
|{{Ramp|Ramp}}
|
|HCS*
|-
|{{Major Highway|Major Highway}}
|
|3
|-A
|{{Minor Highway|Minor Highway}}
|
|3
|-
|rowspan="2"|{{Primary Street|Primary Street}}
|One-way
|3
|-
|Two-way
|2
|-
|rowspan="2"|{{Street|Street}}<br>{{Private Road|Private Road}}
|One-way
|2
|-
|Two-way
|1
|-
|{{Railroad|Railroad}}
|
|2
|-
|{{Ferry|Ferry}}
|
|2
|-
|{{Runway|Runway}}
|
|5
|-
|Other Named Types
|
|1
|-
|style="font-weight:bold; background-color:#ffffcc"|Segment Group
|style="font-weight:bold; background-color:#ffffcc"|
|style="font-weight:bold; background-color:#ffffcc"|Level
|-
|Construction Areas<br><small>''(changes without aerial images)''</small>
|
|3
|}
''Terms''
* HCS - Highest Connecting Segment


===== Additional Info =====
With the addition of city data, Wazers will be even safer on the roads and more knowledgeable about construction, marathons, floods or anything else that can cause delays. And for cities, real-time information from drivers is essential; no one knows more about what's happening in a city than the people who live there.
====== Expectations ======
We understand that higher locks mean there is less available to lower rank and beginning editors. We would like to emphasize that Waze Map Editing is a community activity and, within the US, it is not possible to increase to rank 3 or above without community involvement. It is the responsibility of all members of the editing community to actively reach out, recruit, and mentor new editors.


It is OK to '''temporarily lock segments below standards''' for more junior editors. Area Managers are encouraged to monitor their areas for non-standard locks and follow up with other editors on any discrepancies. As a courtesy, any down-locks made outside your area should be brought to the attention of the local area manager.
The Connected Citizens Program is an ongoing partnership between Waze and various international government agencies to share publicly-available data in order to accomplish two goals:
*Improve the quality of the Waze App
*Utilize Waze data to improve city planning, inform infrastructure decisions and increase the efficiency of day-to-day operations


====== One-Way Streets ======
Waze exchanges publicly available incident and road closure reports, enabling our government partners to respond more immediately to accidents and congestion on their roads. In turn, Waze aggregates the partners' data on the Waze App platform, resulting in succinct and thorough overviews of current road conditions.
The +1 locks on one-way segments originated as guidance from GLR RC GizmoGuy411 based on trends found while  performing Area Manager Reviews:
He would encourage editors to +1-lock one-way street/PS in order to explicitly signal, "Yes, the legwork has been done in order to confirm this segment really is one-way, and it's not a soft-directional issue."


== Existing Partners ==
The first ten partners in the program, called the “W10” by Waze, are Rio de Janeiro, Brazil; Barcelona, Spain; Jakarta, Indonesia; Tel Aviv, Israel; San Jose, Costa Rica; Boston, Massachusetts; Los Angeles County, California; as well as the New York Police Department and the states of Utah and Florida.


=== Name Normalization ===
'''Current Connected Citizen Partners, by Region:'''


Wisconsin will use the following standards for road naming: <br />
''Here is list of Partners as of October 2016''
Freeways - I-### <br />
US Highways - US-### <br />
State Highways - WIS-### <br />
County Highways - CH-XXX <br />
[https://wiki.waze.com/wiki/Forest_Service_Roads Forest Roads] - FR-### <br />
{{mbox | type = warning | text = There are no Township (Town) Roads in the state. All Town Roads are named, and those names will be used. The only exceptions would be if the road signage states differently.}}<br />


'''North America – 72 Partners'''
# Alabama – Department of Transportation
# California – Caltrans
# California – City of Cupertino City Hall
# California – City of Los Angeles
# California – City of Sacramento
# California – City of San Francisco
# California – Los Angeles Metropolitan Transportation Authority
# California – Paramedics Plus (Genesis Pulse)
# California – Town of Los Gatos
# Canada – Ville de Montreal
# Colorado – City of Colorado Springs
# Colorado – Douglas County
# District of Columbia – D.C. Department of Transportation
# Florida – City of Miami Beach
# Florida – City of Tampa
# Florida – Florida Department of Transportation
# Florida – Paramedics Plus (Genesis Pulse)
# Florida – Miami-Dade County
# Florida – Sunstar EMS (Genesis Pulse)
# Georgia – Bartow County
# Georgia – City of Atlanta
# Georgia – City of Johns Creek
# Georgia – City of West Jackson
# Georgia – Georgia Department of Transportation
# Georgia – Georgia Emergency Management & Homeland Security Agency
# Illinois – City of Evanston
# Illinois – City of Naperville
# Indiana – City of Bloomington
# Indiana – Paramedics Plus (Genesis Pulse)
# Indiana – Three Rivers Ambulance Authority (Genesis Pulse)
# Iowa – Iowa Department of Transportation
# Kentucky – City of Louisville
# Kentucky – Kentucky Transportation Cabinet
# Louisiana – City-Parish of Baton Rouge
# Louisiana – Louisiana Department of Transportation and Development
# Maine – Maine Department of Transportation
# Maryland – University of Maryland
# Maryland – St. Mary’s Emergency Services and Technology
# Massachusetts – City of Boston
# Massachusetts – City of Cambridge (Kleinfelder East)
# Massachusetts – Capital Strategic Solutions
# Massachusetts – Massachusetts Department of Transportation
# Missouri – CoxHealth (Genesis Pulse)
# Missouri – Mercy EMS (Genesis Pulse)
# Missouri – Taney County Ambulance Directory (Genesis Pulse)
# National – SeeClickFix (nonprofit partner)
# National – United States Department of Transportation
# Nebraska – Nebraska Department of Roads
# Nevada - Regional Transportation Commission of Southern Nevada (RTCSVN)
# New Hampshire – New Hampshire Department of Transportation
# New Jersey – City of Jersey City
# New Jersey – Jersey City EMS (Genesis Pulse)
# North Carolina – City of Charlotte
# North Carolina – City of Greensboro
# North Carolina – City of Raleigh
# Ohio – Town of Dublin
# Oregon – Oregon Department of Transportation
# Pennsylvania – Pennsylvania Department of Transportation
# Pennsylvania – Pennsylvania Turnpike Authority
# Pennsylvania – Wilkes-Barre Township Police Department
# Rhode Island – City of Providence
# Rhode Island – Rhode Island Turnpike & Bridge Authority
# South Dakota – Paramedics Plus (Genesis Pulse)
# Tennessee – Tennessee Department of Transportation
# Texas – CareFlite (Genesis Pulse)
# Texas – Champion EMS (Genesis Pulse)
# Texas – ETMC EMS (Genesis Pulse)
# Texas - City of Fort Worth
# Texas – LifeNet EMS (Genesis Pulse)
# Utah – Utah Department of Transportation
# Vermont – Vermont Department of Transportation
# Virginia – City of Arlington
# Virginia – Portsmouth Police Department


=== Bridge and Overpass Segmentation Elevation (BOSE) ===
'''Latin America - 10 Partners'''
'''Please note that there are regional and national discussions ongoing for establishing standards beyond state level.  If those changes come in opposition to what we are doing here, then we will be changing to follow suit.'''<br />
# Brazil – City of Petropolis
# Brazil – City of Vitoria
# Brazil – Juiz de Fora Secretary of Transport and Transit Secretaria de Transporte e Transito
# Brazil – Rio de Janeiro Center for Traffic Operations (COR)
# Colombia – Bogata Instituto de Desarrollo Urbano
# Costa Rica – Ministry of Transport
# Mexico – City of Puebla
# Mexico – Delegacion Miguel Hidalgo (Mexico City)
# Mexico – La Sultana de Norte (Monterrey)
# Peru – Muncipalidad de Miraflores


Wisconsin has decided on a state standard for the segmentation of bridges and overpasses.<br />
'''Europe - 14 Partners'''
# Belgium – City of Ghent
# Estonia – Tarktee (Smart Roads)
# France – Department of Var
# France – Northern France, Tollway Authority
# Hungary – BKK Center for Budapest Transport
# Latvia – City of Riga
# Latvia – Latvia State Roads
# Lithuania – Lithuania Road Administration
# Netherlands – National Data Warehouse for Traffic Information
# Portugal – Brisa/Via Verde (Portugal Tollway Authority)
# Rome – Rome Center for Mobility
# Spain – City of Barcelona
# Spain – Government of Catalonia
# United Kingdom – Transport for London


The National Wiki contains the standard information regarding proper elevation of segments.  What we are doing in Wisconsin is expanding on those standards to create a more accurate representation of the segments.<br />
'''Middle East - 2 Partners'''
# Israel - City of Tel-Aviv
# Israel - Holon Municipality


Basic elevation is determined using the following rules:
'''Asia-Pacific - 2 Partners'''
* All roads start at Ground elevation
# Indonesia - City of Jakarta
* If a segment is above another segment, it should be set to +1 relative to the lower segment's elevation (to account for multiple segments overlapping)
# Australia - Transportation Management Centre of New South Wales
* If a segment is a tunnel (not just an underpass), it should be set at -1, and Tunnel should be checked.<br />


'''Bridges'''<br />
== How to Join ==
Definition:
* If a segment travels over a river or body of water, it is considered a bridge
* If a segment travels over another segment, it is considered it a bridge (aka: overpass).
* If a segment is artificially elevated to pass over ground level objects and natural features, it is considered a bridge.<br />


Junctioning:<br />
Currently Waze offers data exchange programs with government entities and private road owners and operators. Please fill out the [http://docs.google.com/a/penthion.nl/forms/d/19BGX1zD6HCLvx5nNMQnfrSRS3ZiVft_Q6G2GPiRMVqE/viewform Waze Data Exchange Interest Form] to share data with Waze and to apply for participation in Waze's Connected Citizens program.
Place a junction at the start/end of the bridge where the land falls away.
*If there is already a junction within 500 feet of the bridge, do not add a new junction.
*Do not junction a bridge if it is less than 75 feet in length. If you believe you need to do so, contact an SM or LAM for approval.<br />


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


Do not segment a ramp like you would for a bridge, unless it takes on several different elevations.<br />
Local Government Agencies, Municipalities, Cities, States, Departments of Transportation, Departments of Public Works, Utility Companies, 911 Emergency Dispatch Centers and Police Departments


Because of the complexity of interchanges, please contact your State Manager before making adjustments.<br />
Several qualifications:
*Waze aims to work with partners who have additional sources of data, such as road closures, street cameras or road sensors, not found within the Waze app
*Geographical diversity
*Technical capability
*Eagerness and readiness to innovate
*Waze needs in the market (need more data or want to grow focus markets)


'''Special Note'''
== References ==


''This process was derived from the Seagull Effect created by the Australians.  The process has been unofficially called ‘seagulling’.  Please note that this word is a misuse of the Seagull Effect. Using it may have unintended connotations.''
'''Word Doc:''' [http://docs.google.com/document/d/1msH86f0Uh9DoRT0srC1a-MMYjhwF8hTqHiR4-AeS72U/edit Connected Citizens Program Summary]


Waze CCP Homepage:[http://www.waze.com/ccp Waze Connected Citizens Program]


=== Additional notes for this state ===
Waze CCP Blog post: [http://www.waze.com/connectedcitizens Waze Connected Citizens Program Blog Post]


====Dirt Roads====
Waze Data CCP: [http://data-waze.com/2014/10/01/introducing-the-w10-and-the-new-connected-citizens-platformprogram/ Introducing the W10 And The New Connected Citizens Platform]
All drivable unpaved (Dirt/Gravel) roads should be classified as per Functional Classification. The Unpaved checkbox should then be selected, as this will allow the "Avoid Dirt Roads" feature in Waze to behave properly.


Trails and non-standard roads that may require special equipment to drive on, should either not be mapped, or be classified as an "Off Road / Not Maintained" road with the Unpaved checkbox ticked.
Video: [http://www.youtube.com/watch?v=YmRW47XJfhQ Waze Connected Citizens Launch Highlights | Waze] (1:25)


====Toll Roads====
Video: [http://www.youtube.com/watch?v=AMqbh3rqZRs Waze W10 10/1/14 Launch Event Panel, hosted by Baratunde Thurston] (46:44)
There are currently no toll roads in Wisconsin. No segments within the state of Wisconsin should be marked as 'Toll Road'.


====Pedestrian Boardwalk, Walking Trail, Stairway====
Video: [http://launch.newsinc.com/share.html?trackingGroup=69017&siteSection=ndn&videoId=27379259 NYPD Partners with Waze for Road Safety] (1:13)
These should not be mapped without approval from a State Manager for Wisconsin or the Regional Coordinator. These segment types can cause routing issues even when not connected to a drivable segment.


Video: [http://www.cbsnews.com/videos/waze-navigation-app-teams-up-with-cities-states-to-share-traffic-data/ Waze navigation app teams up with cities, states to share traffic data] (4:11)


====Solid White Lines====
Article: [http://www.prnewswire.com/news-releases/waze-launches-connected-citizens-program-debuts-inaugural-w10-277867931.html Waze Launches Connected Citizens Program, Debuts Inaugural "W10"]
It is not illegal to cross a solid white line in the state of Wisconsin, unless posted [https://docs.legis.wisconsin.gov/statutes/statutes/346/II/13/3 Wisconsin Statute 346.13(3)].
<br>
[[File:Solid White Line Statute.png|thumbnail]]
Some examples are: road edge lines, lane divider lines, or on/off ramp lane lines. Even though it is not illegal, it is a safe driving practice to not cross these lines.  When mapping on/off ramps, please follow national guidelines in the [[Junction Style Guide/Interchanges]] section.
<br>
[[File:White Line Off Ramp.png|Off Ramp Example]]
<br><br>
[[File:White Line On Ramp.png|On Ramp Example]]
<br><br>
There may be times when this is impractical, in such instances, contact a State Manager for further guidance.


====Roundabouts at Freeway Interchanges====
Press Release: [http://transportation.ky.gov/Pages/PressReleasePage.aspx?&FilterField1=ID&FilterValue1=113 Kentucky Transportation Cabinet among first partners with Waze]
When there are roundabouts at freeway interchanges, leave the connecting overpass/underpass roads un-named.  Waze will read forward to the next roundabout and provide proper TTS and visual prompts for the user to aid in proper lane selection at multi-lane roundabouts.
<br>Here is an example of when '''not''' to name the segment(s): [https://www.waze.com/editor/?env=usa&lon=-88.08134&lat=44.52407&layers=2981&zoom=5&segments=66002890 Do Not Name]


====U-Turns====
Press Release:[http://www.dot.state.fl.us/trafficoperations/Newsletters/2014/2014-Aug.pdf FDOT, The Waze Connection]


U-turns in Wisconsin are permitted when:{{ref label|1|1}}
Press Release:[http://pulsesite.genesisworld.com/2015/10/06/the-genesis-group-joins-waze-connected-citizens-program/, The Genesis Group Joins Waze CCP]


# The u-turn can be made in safety and without interfering with other traffic.
Forum: [http://www.waze.com/forum/viewtopic.php?f=129&t=120169 CCP Forum Post]
# Not upon any curve, or upon the approach to or near the crest of a grade, where the vehicle cannot be seen by the driver of any other vehicle approaching from either direction within five hundred (500) feet.
# Not explicitly prohibited by signage or local municipal law.
# You are not required to back up during the course of the u-turn in order to complete it.


For Waze routing, u-turns should only be enabled where they provide the potential for improved routing, which includes recovering from missed turns. A common example is a median-divided primary street that has homes/businesses with their driveways/entrances directly on it, where reaching them would otherwise require lengthy, multi-turn deviations through side roads in order to end up on the correct side of the median.
Forum: [http://www.waze.com/forum/viewtopic.php?f=129&t=120169#p1038875 Canned CCP Template]


U-Turns are '''not''' allowed on any Freeway or Expressway.
Message format: [http://wazeblogs-en.blogspot.ie/p/connected-citizens-partner-feeds-specs.html CIFS: Connected Citizens Partner Feeds Specs]
 
{{note|1|1}} [https://docs.legis.wisconsin.gov/statutes/statutes/346/V/33 Wisconsin Statute 346.33]
 
====Construction Zones====
 
If a construction zone is expected to last one week or longer, the following options are allowed to be made to the area:
*Change speed limit to lower posted limit
*Add crossovers for traffic changes and make one-way Freeway segments two-way.
 
If any or all of these changes are made, add the construction zone to the following spreadsheet for easy reference and followup by other editors.
[https://docs.google.com/spreadsheets/d/1cBXF25qeT1etuIZjzQSunZThmiUgzHh2hmFjlJ8-iLM/edit?usp=sharing WI Construction Zones]
 
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----
-------------------------------------------------------------------------------------
---- This page is only transcluded into (displayed on) the main page for this state.
---- It directly follows the common guidelines applicable to all states. When this
---- page is present (even if blanked), it displaces any optional code that might be
---- in that section.
---- If the original optional code from the main page for this section is still
---- desired, it can be restored by adding the following code to the first line
---- between the "DO NOT MODIFY" lines on this page:
----  {{:USA/CommonState/Major_roads|optional}}
----
-------------------------------------------------------------------------------------
---- If there will be a full page for this section, use code similar to the wording
---- below to provide a hyperlink to that page. When creating the full page, use the
---- link on the talk page to ensure the preload data is provided to help with
---- formatting the page. Don't just use the red link from this section once it is
---- saved.
----
See [[{{BasePage2}}/Major roads]] for guidance in {{RootPage2}} that may not be universal to all other states.
----
-------------------------------------------------------------------------------------
---- This section has three possible purposes:
---- 1. It is only providing a hyperlink to the full page for this section.
---- 2. It is only providing some unique guidance for this state that differs from
---- other states.
---- 3. It is intentionally wiping out the general optional content for this section
---- for this state.
------------------------------------------------------------------------------------>

Revision as of 04:11, 16 February 2017

This page was nominated to be a Wazeopedia Global page. Forum to discuss nomination.

The Waze Connected Citizens program, also known as CCP brings cities and citizens together to answer the questions “What’s happening, and where?” We exchange publicly available incident and road closure reports, enabling our government partners to respond more immediately to accidents and congestion on their roads. In turn, we aggregate our partners' data on the Waze platform, resulting in one of the most succinct, thorough overviews of current road conditions today.

With the addition of city data, Wazers will be even safer on the roads and more knowledgeable about construction, marathons, floods or anything else that can cause delays. And for our government partners, publicly-available Waze data is a powerful tool to build more efficient cities. Real-time information from drivers is essential; no one knows more about what's happening in a city than the people who live there. In an era with smart phones, smart cars and smart homes, isn't it about time we start building smarter cities?


Details

The mission of Waze Connected Citizens is to help Wazers, cities and citizens collaborate to improve their community and answer the question "What's happening on our roads right now, and where?" The program promotes more efficient traffic monitoring by sharing crowdsourced incident reports from Waze drivers. Established as a two-way data share, Waze receives partner input such as feeds from road sensors, adds publicly available incident and road closure reports from the Waze traffic platform and returns one of the most succinct, thorough overviews of current road conditions today.

With the addition of city data, Wazers will be even safer on the roads and more knowledgeable about construction, marathons, floods or anything else that can cause delays. And for cities, real-time information from drivers is essential; no one knows more about what's happening in a city than the people who live there.

The Connected Citizens Program is an ongoing partnership between Waze and various international government agencies to share publicly-available data in order to accomplish two goals:

  • Improve the quality of the Waze App
  • Utilize Waze data to improve city planning, inform infrastructure decisions and increase the efficiency of day-to-day operations

Waze exchanges publicly available incident and road closure reports, enabling our government partners to respond more immediately to accidents and congestion on their roads. In turn, Waze aggregates the partners' data on the Waze App platform, resulting in succinct and thorough overviews of current road conditions.

Existing Partners

The first ten partners in the program, called the “W10” by Waze, are Rio de Janeiro, Brazil; Barcelona, Spain; Jakarta, Indonesia; Tel Aviv, Israel; San Jose, Costa Rica; Boston, Massachusetts; Los Angeles County, California; as well as the New York Police Department and the states of Utah and Florida.

Current Connected Citizen Partners, by Region:

Here is list of Partners as of October 2016

North America – 72 Partners

  1. Alabama – Department of Transportation
  2. California – Caltrans
  3. California – City of Cupertino City Hall
  4. California – City of Los Angeles
  5. California – City of Sacramento
  6. California – City of San Francisco
  7. California – Los Angeles Metropolitan Transportation Authority
  8. California – Paramedics Plus (Genesis Pulse)
  9. California – Town of Los Gatos
  10. Canada – Ville de Montreal
  11. Colorado – City of Colorado Springs
  12. Colorado – Douglas County
  13. District of Columbia – D.C. Department of Transportation
  14. Florida – City of Miami Beach
  15. Florida – City of Tampa
  16. Florida – Florida Department of Transportation
  17. Florida – Paramedics Plus (Genesis Pulse)
  18. Florida – Miami-Dade County
  19. Florida – Sunstar EMS (Genesis Pulse)
  20. Georgia – Bartow County
  21. Georgia – City of Atlanta
  22. Georgia – City of Johns Creek
  23. Georgia – City of West Jackson
  24. Georgia – Georgia Department of Transportation
  25. Georgia – Georgia Emergency Management & Homeland Security Agency
  26. Illinois – City of Evanston
  27. Illinois – City of Naperville
  28. Indiana – City of Bloomington
  29. Indiana – Paramedics Plus (Genesis Pulse)
  30. Indiana – Three Rivers Ambulance Authority (Genesis Pulse)
  31. Iowa – Iowa Department of Transportation
  32. Kentucky – City of Louisville
  33. Kentucky – Kentucky Transportation Cabinet
  34. Louisiana – City-Parish of Baton Rouge
  35. Louisiana – Louisiana Department of Transportation and Development
  36. Maine – Maine Department of Transportation
  37. Maryland – University of Maryland
  38. Maryland – St. Mary’s Emergency Services and Technology
  39. Massachusetts – City of Boston
  40. Massachusetts – City of Cambridge (Kleinfelder East)
  41. Massachusetts – Capital Strategic Solutions
  42. Massachusetts – Massachusetts Department of Transportation
  43. Missouri – CoxHealth (Genesis Pulse)
  44. Missouri – Mercy EMS (Genesis Pulse)
  45. Missouri – Taney County Ambulance Directory (Genesis Pulse)
  46. National – SeeClickFix (nonprofit partner)
  47. National – United States Department of Transportation
  48. Nebraska – Nebraska Department of Roads
  49. Nevada - Regional Transportation Commission of Southern Nevada (RTCSVN)
  50. New Hampshire – New Hampshire Department of Transportation
  51. New Jersey – City of Jersey City
  52. New Jersey – Jersey City EMS (Genesis Pulse)
  53. North Carolina – City of Charlotte
  54. North Carolina – City of Greensboro
  55. North Carolina – City of Raleigh
  56. Ohio – Town of Dublin
  57. Oregon – Oregon Department of Transportation
  58. Pennsylvania – Pennsylvania Department of Transportation
  59. Pennsylvania – Pennsylvania Turnpike Authority
  60. Pennsylvania – Wilkes-Barre Township Police Department
  61. Rhode Island – City of Providence
  62. Rhode Island – Rhode Island Turnpike & Bridge Authority
  63. South Dakota – Paramedics Plus (Genesis Pulse)
  64. Tennessee – Tennessee Department of Transportation
  65. Texas – CareFlite (Genesis Pulse)
  66. Texas – Champion EMS (Genesis Pulse)
  67. Texas – ETMC EMS (Genesis Pulse)
  68. Texas - City of Fort Worth
  69. Texas – LifeNet EMS (Genesis Pulse)
  70. Utah – Utah Department of Transportation
  71. Vermont – Vermont Department of Transportation
  72. Virginia – City of Arlington
  73. Virginia – Portsmouth Police Department

Latin America - 10 Partners

  1. Brazil – City of Petropolis
  2. Brazil – City of Vitoria
  3. Brazil – Juiz de Fora Secretary of Transport and Transit Secretaria de Transporte e Transito
  4. Brazil – Rio de Janeiro Center for Traffic Operations (COR)
  5. Colombia – Bogata Instituto de Desarrollo Urbano
  6. Costa Rica – Ministry of Transport
  7. Mexico – City of Puebla
  8. Mexico – Delegacion Miguel Hidalgo (Mexico City)
  9. Mexico – La Sultana de Norte (Monterrey)
  10. Peru – Muncipalidad de Miraflores

Europe - 14 Partners

  1. Belgium – City of Ghent
  2. Estonia – Tarktee (Smart Roads)
  3. France – Department of Var
  4. France – Northern France, Tollway Authority
  5. Hungary – BKK Center for Budapest Transport
  6. Latvia – City of Riga
  7. Latvia – Latvia State Roads
  8. Lithuania – Lithuania Road Administration
  9. Netherlands – National Data Warehouse for Traffic Information
  10. Portugal – Brisa/Via Verde (Portugal Tollway Authority)
  11. Rome – Rome Center for Mobility
  12. Spain – City of Barcelona
  13. Spain – Government of Catalonia
  14. United Kingdom – Transport for London

Middle East - 2 Partners

  1. Israel - City of Tel-Aviv
  2. Israel - Holon Municipality

Asia-Pacific - 2 Partners

  1. Indonesia - City of Jakarta
  2. Australia - Transportation Management Centre of New South Wales

How to Join

Currently Waze offers data exchange programs with government entities and private road owners and operators. Please fill out the Waze Data Exchange Interest Form to share data with Waze and to apply for participation in Waze's Connected Citizens program.

Who can Join

Local Government Agencies, Municipalities, Cities, States, Departments of Transportation, Departments of Public Works, Utility Companies, 911 Emergency Dispatch Centers and Police Departments

Several qualifications:

  • Waze aims to work with partners who have additional sources of data, such as road closures, street cameras or road sensors, not found within the Waze app
  • Geographical diversity
  • Technical capability
  • Eagerness and readiness to innovate
  • Waze needs in the market (need more data or want to grow focus markets)

References

Word Doc: Connected Citizens Program Summary

Waze CCP Homepage:Waze Connected Citizens Program

Waze CCP Blog post: Waze Connected Citizens Program Blog Post

Waze Data CCP: Introducing the W10 And The New Connected Citizens Platform

Video: Waze Connected Citizens Launch Highlights | Waze (1:25)

Video: Waze W10 10/1/14 Launch Event Panel, hosted by Baratunde Thurston (46:44)

Video: NYPD Partners with Waze for Road Safety (1:13)

Video: Waze navigation app teams up with cities, states to share traffic data (4:11)

Article: Waze Launches Connected Citizens Program, Debuts Inaugural "W10"

Press Release: Kentucky Transportation Cabinet among first partners with Waze

Press Release:FDOT, The Waze Connection

Press Release:The Genesis Group Joins Waze CCP

Forum: CCP Forum Post

Forum: Canned CCP Template

Message format: CIFS: Connected Citizens Partner Feeds Specs

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