Stay organized with collections
Save and categorize content based on your preferences.
Feed Setup
The following information will help you get your feeds set up and running correctly.
Feed file hosting
The Waze content acquisition system automatically fetches your feed data periodically. To ensure Waze retrieves the correct feed file:
- Make it accessible: Use standard network protocols (HTTP, HTTPS, FTP, or SFTP).
- Secure your data (optional): You can secure your feed with a username and password using BASIC authentication over HTTPS. You provide the login and password combination through Partner Hub.
- Ensure accessibility: Ensure the hosted file is accessible globally.
- To avoid disruptions in data fetching, please ensure your firewall does not block access based on country, IP address, or geographic region. These restrictions may prevent us from retrieving your feed data.
- We use a dynamic system for pulling closure and incident information. This means we don't use static IPs or support pre-authorized URL/domain/wildcard, or DNS entry authorization.
Feed frequency
The content acquisition system fetches data every few minutes. If you have special requirements regarding the feed frequency, add a note indicating this request when submitting the feed, or contact the Waze team so we can adjust our polling periods to reflect your feed update cycle.
XML validation
Waze uses the following XML schema to define the acceptable structure of a
Closure and Incidents Feed Specifications (CIFS) feed:
https://www.gstatic.com/road-incidents/cifsv2.xsd.
There are a number of tools available on the internet that can help you
validate the structure of your XML feeds. These include, but are not limited
to:
Critical feed changes
Before making any of the following changes, notify the Waze team by completing
this form
and editing your request in the Portal to identify the updated feed.
- Modifying, adding, or removing regions or countries from your feed.
- Updating the feed URL or any credentials required for accessing the
information.
- Changing the feed structure or tag names.
Feed specifications
A single feed file can provide information on multiple closures and
incidents. If you are providing information on multiple events, each closure
or incident must be detailed in a separate element and must have a unique Id. These
sections should use the local time and date. The CIFS specification
details all the tags available to describe your incidents and closures.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-02-12 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-02-12 UTC."],[[["\u003cp\u003eWaze automatically fetches feed data, requiring it to be accessible via standard network protocols like HTTP, HTTPS, FTP, or SFTP, and secured with BASIC or DIGEST authentication.\u003c/p\u003e\n"],["\u003cp\u003eEnsure your XML feed structure adheres to the Waze schema which can be validated using online tools.\u003c/p\u003e\n"],["\u003cp\u003eFor critical feed changes like region modifications, URL updates, or structural alterations, prior notification to the Waze team is essential.\u003c/p\u003e\n"],["\u003cp\u003eA single feed file can contain multiple events, each requiring a unique ID and detailed information as per the CIFS specification.\u003c/p\u003e\n"]]],["Waze automatically retrieves feed data via HTTP, HTTPS, FTP, or SFTP, with optional BASIC authentication. Hosted files must be globally accessible, without firewall restrictions based on country or IP. Data is fetched every few minutes, with adjustable frequency upon request. Feeds must adhere to the provided XML schema; validation tools are suggested. Notify Waze before making critical changes, such as modifying regions, URLs, credentials, or feed structure. Each closure or incident must be in a separate element with unique ID.\n"],null,["Feed Setup\n==========\n\nThe following information will help you get your feeds set up and running correctly.\n\nFeed file hosting\n-----------------\n\nThe Waze content acquisition system automatically fetches your feed data periodically. To ensure Waze retrieves the correct feed file:\n\n- **Make it accessible:** Use standard network protocols (HTTP, HTTPS, FTP, or SFTP).\n- **Secure your data (optional):** You can secure your feed with a username and password using BASIC authentication over HTTPS. You provide the login and password combination through Partner Hub.\n- **Ensure accessibility:** Ensure the hosted file is accessible globally.\n - To avoid disruptions in data fetching, please ensure your firewall does not block access based on country, IP address, or geographic region. These restrictions may prevent us from retrieving your feed data.\n - We use a dynamic system for pulling closure and incident information. This means we don't use static IPs or support pre-authorized URL/domain/wildcard, or DNS entry authorization.\n\nFeed frequency\n--------------\n\nThe content acquisition system fetches data every few minutes. If you have special requirements regarding the feed frequency, add a note indicating this request when submitting the feed, or [contact the Waze team](https://support.google.com/waze/partners/answer/7576817) so we can adjust our polling periods to reflect your feed update cycle.\n\nXML validation\n--------------\n\nWaze uses the following XML schema to define the acceptable structure of a\nClosure and Incidents Feed Specifications (CIFS) feed:\n\u003chttps://www.gstatic.com/road-incidents/cifsv2.xsd\u003e.\n\nThere are a number of tools available on the internet that can help you\nvalidate the structure of your XML feeds. These include, but are not limited\nto:\n\n- [http://www.w3.org/XML/Schema#Tools](http://www.w3.org/XML/Schema#Tools/a)\n- \u003chttp://www.xml.com/pub/a/2000/12/13/schematools.html\u003e\n- \u003chttp://xmlsoft.org/xmllint.html\u003e\n\nCritical feed changes\n---------------------\n\nBefore making any of the following changes, notify the Waze team by completing\n[this form](https://support.google.com/waze/partners/answer/7576817)\nand editing your request in the Portal to identify the updated feed.\n\n- Modifying, adding, or removing regions or countries from your feed.\n- Updating the feed URL or any credentials required for accessing the information.\n- Changing the feed structure or tag names.\n\nFeed specifications\n-------------------\n\nA single feed file can provide information on multiple closures and\nincidents. If you are providing information on multiple events, each closure\nor incident must be detailed in a separate element and must have a unique Id. These\nsections should use the local time and date. The [CIFS specification](../data-feed/cifs-specification)\ndetails all the tags available to describe your incidents and closures."]]
