The Waze feed type in ArcGIS Velocity sends HTTPS requests to the specified Waze URL with relevant parameters. Data from the Waze API is returned with minimal configuration.
Examples
The following are example uses of the Waze feed:
- Waze alert and traffic information help communities monitor and respond to real-time driver traffic reports, identify problem areas reported by drivers, and run analysis on data over time to feed data-driven decisions.
- 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 Waze feed:
- The feed polls the Waze endpoints to load data at the rate specified by 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 the feed is started at 8:03 a.m., the first request for data will occur at 8:05 a.m., the next at 8:10 a.m., and so on.
- The ArcGIS Velocity subscription license levels have limits to how much data can be ingested by a feed as summarized below. If feeds exceed the ingestion limit of your license level, a message is written to the logs and an email is sent 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. For more information about ArcGIS Velocity licensing, see Licensing. 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 Waze 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 | Specifies the type of information that will be returned from Waze. The options are Alerts, Irregularities, and Traffic. | String |
Alert type (Conditional) | The types of alerts that will appear. This parameter is active when Waze information type is set to Alerts. The alert type options are as follows:
| String |
Number of thumbs up | Specifies whether a ThumbsUp field will be added to alerts that have been liked by Waze users. When set to True, the response time is slower. | Boolean |
Include partner alerts | Specifies whether alerts reported by partner feeds will be included in addition to alerts reported by Waze users. When set to False, the output will only include alerts reported by Waze users. | Boolean |
Include only partner alerts | Specifies whether only alerts reported by partner feeds will be included. When set to False, alerts reported by partner feeds and Waze users through the app will be included. | Boolean |
Additional logging | Specifies whether logging for raw HTTP requests and responses issued by Velocity to the Waze endpoint will be enabled. This parameter is optional. Note:Only enable this parameter for troubleshooting purposes and disable it when troubleshooting is complete. Once enabled, start the feed, and the debug level logs will be available on the feed logs page. Contact Esri Technical Support for assistance with troubleshooting if necessary. | Boolean |
Considerations and limitations
The following are considerations and limitations when using the Waze 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.