The Waze feed sends a Hyper Text Transfer Protocol Secure (HTTPS) request to a specified Waze URL with relevant parameters.Data from the Waze API is returned with minimal configuration.
Examples
The following are example use cases for the feed:
- Waze alert and traffic information helps communities monitor and respond to real-time traffic reports from drivers, identify problem areas, and run analysis on data over time.
- Waze alerts are queried every 20 seconds to alert a local government of reported issues in their region.
Usage notes
Keep the following in mind when working with the feed:
- The feed polls the Waze endpoints to load data at the rate specified during the Feed Polling Interval step of the configuration wizard.
- When a polling interval is set, the polling occurs at regular time intervals as opposed to the start time of the feed. For example, if a feed is set to poll for data every five minutes, and started at 8:03 a.m., the first request for data occurs at 8:05 a.m., the next at 8:10 a.m., and so on.
- The Velocity subscription license level limits how much data can be ingested by a feed; these levels are summarized below. If feeds exceed the ingestion limit of your license level, a message is written to the logs and you will receive an email notifying you that the limit has been reached. If ingestion of data remains above the limit for more than an hour, the feed is stopped. Work with your Esri representative or Esri Technical Support to explore Velocity license levels that support your workflows, if necessary. License levels are as follows:
- Standard—Ingest and process data at 25 KB/second (approximately 100 events per second).
- Advanced—Ingest and process data at 250 KB/second (approximately 1,000 events per second).
- Dedicated—Ingest and process data at 2,500 KB/second (approximately 10,000 events per second).
Parameters
The following are the parameters for the feed:
| Parameter | Description | Data type |
|---|---|---|
| URL | The full URL to Waze. The expected URL format is https://www.waze.com/partnerhub-api/partners/<partner-id>/waze-feeds/<unique-token>, with <partner-id> and <unique-token> replaced with your specific values. Your specific URL can be accessed in the Waze Partner Hub. | String |
| Waze information type | The type of information returned from Waze. Options are Alerts, Irregularities, and Traffic. | String |
| Alert type (optional) | The types of alerts that appear include traffic incidents, road closures, and other relevant updates. This parameter is active when Waze information type is set to Alerts. The following are the alert types:
| String |
| Number of thumbs up | Specifies whether a ThumbsUp field is added to alerts liked by Waze users. When set to True, the response time is slower. The default is False. | Boolean |
| Include partner alerts | Specifies if alerts reported by partner feeds should be included in addition to alerts reported by Waze users. When set to False, the output includes alerts reported by Waze users. The default is True. | Boolean |
| Include only partner alerts | Specifies whether only alerts reported by partner feeds are included. When set to False, alerts reported by both partner feeds and Waze users through the app are included. The default is False. | Boolean |
| Additional logging (optional) | Specifies whether logging for raw HTTP requests and responses issued by Velocity to the Waze endpoint is available. The default is False. Note:Only turn on this parameter for troubleshooting and turn it off when troubleshooting is complete. Once turned on, start the feed, and the debug level logs are available on the feed logs page. Contact Esri Technical Support for assistance with troubleshooting. | Boolean |
Considerations and limitations
Consider the following when using the feed:
- A Waze partner ID and unique token is required to use this feed type. Your partner ID and unique token can be accessed in the Waze Partner Hub.
- The Waze feed type automatically configures key fields including geometry, time, and track ID.