The Waze Connected Citizens Program (CCP) is a means for organizations to share road closure and incident datasets, and have them available in Waze. Refer to Waze: Working together for a smarter more sustainable future for more information.
How does ArcGIS work with the Waze CCP?
The ArcGIS platform can effectively exchange and share available traffic information publicly with Waze through the Waze CCP program.
Waze provides organizations with real-time, anonymous, Waze-generated incident and slow-down information directly from the source. In exchange, ArcGIS provides insights on real-time construction, crash, and road closure data to Waze.
Refer to ArcGIS Blog: Integrating Waze with ArcGIS through the Connected Citizens Program for more information. For more Waze CCP program user examples, refer to GeoNet: Esri and Waze examples.
Note: Organizations can participate in the Waze CCP program through ArcGIS Online, and do not require ArcGIS GeoEvent Server.
Can any ArcGIS service be published to Waze?
No, the ArcGIS service must be a feature service, or a hosted feature service. Live edits must be performed on these layers, and map services do not support editing. The published service must conform to the Closure and Incident Feed Specifications (CIFS).
What happens after the service is published?
When the map service is published, organizations can add live closures. To do so:
What is the best practice for participating in the Waze CCP?
The best practice for participating in the Waze CCP program is to check the map daily. It is the organization's responsibility to update and regularly input road closures. For example, organizations can have field workers edit the service with Collector for ArcGIS. Waze collates the updated information from the map every minute, and it takes approximately 10–11 minutes before edits are visible on the Waze map.
Can a user build an ArcGIS web app or Operations Dashboard using Waze's live alerts data?
Yes. One of the many benefits of being a member of the Waze CCP is the organization has access to the Waze Live Alerts Layer for ArcGIS Online in ArcGIS Marketplace. The Waze Live Alerts Layer is a self-refreshing feature layer (a feed) containing all crowd-sourced and CCP-sourced road hazards collected by Waze, with each hazard depicted as a point feature using Waze's symbology.
The steps below outline how to add the layer to a web map in ArcGIS Online, after the organization is approved to participate in the program. Once the Waze Live Alerts Layer is added to a web map, with the Waze symbology intact, users may begin building dashboards.
Note: The organization is provisioned for the Waze Live Alerts Layer when the organization is enrolled in the Waze CCP program.
What about the geometry?
Providing geometry to a third party does not guarantee proper alignment. Lining up data is the harvesting organization's responsibility. To add road closures, organizations can use the basemap, or alternatively use the Waze tiles from ArcGIS Online. Waze harvests the data within a fuzzy tolerance, and locates the right segment.
Can organizations create a lane closure service?
Organizations can create a lane closure service, but this is more for the benefit of the ArcGIS organization. Waze only looks at full road closures. This is because a four-lane road with one lane closed does not close the road. Organizations can mark lane closures as part of an incident's feed. Alternatively, a definition query can be used on the domain to push road closures only to Waze. This way, organizations can have road and lane closures in a feature service, with Waze only receiving and using the needed information.
Are users allowed to add additional fields or omit fields from the feature service?
All the required fields in the CIFS schema must be present. Organizations may add optional fields, and omit them from REST in the query Waze consumes.