Share real-time traffic information with Waze drivers nearby. You can share:
- Road closures
- The location of vehicles like garbage trucks and snow plows
- Traffic incidents and alerts
To get started, create an XML or JSON format feed file containing your data for closures and traffic incidents. You can provide closure and incident information in the same feed. Learn more about creating a feed file for Waze.
Share your feed file with Waze:
- Log in to the Partner Hub
- At the top, click Toolbox
- Click Partner feed
+ New feed
- Give the feed a name
- Select the type of data and feed format
- Select the feed specification
- Under "Feed URL", click + Add URL and fill in the information
- Click Add URL
- Click Submit feed
+ New feedOnce your data feed is approved, you’ll get an email to let you know that your data is being shared with relevant drivers.
When sharing Waze’s data, please follow attribution guidelines. Learn more.
Got questions?
How do I fix map errors?
When Waze can't automatically match your closure data to road segments, it creates a map error for you to review. To resolve an error, find your error reason in the table below so map editors can update the segment details in the Waze Map Editor.
Once you've identified the error below, map editors can fix the map error in the Waze Map Editor. Learn how to fix map errors on Wazeopedia.
| Error reason | Explanation |
| NO_SEGMENTS_NEAR_POINT | Waze can’t find a matching road segment within 50 meters of the coordinates provided. This happens for one of the following reasons: There’s a street or direction mismatch, the segment is missing from the map, or the coordinates are too far from the nearest segment. |
| NO_SEGMENTS_MATCHING_TRAFFIC_DIRECTION | Waze can’t find segments due to a direction mismatch. For example, the polyline direction heads west, but the nearby segments head north. |
| CIRCULAR_POLYLINE | Waze doesn’t support events with circular polylines. A circular polyline has 3 or more pairs of coordinates where the first and last pairs are similar, creating a circular shape. |
| CANT_DETERMINE_TRAFFIC_DIRECTION | This happens when a single point is placed on a two-way road and the direction provided is “ONE_DIRECTION”. Our systems can’t determine which side of traffic is impacted based on the provided info. |
| FAILED_TO_FIND_ROUTE | Waze can’t find a route that matches the polyline. This is usually due to a street or direction mismatch, or an invalid polyline shape that spans multiple streets. |
| STREET_NAMES_DONT_MATCH | Closures can only affect one street or road on the Waze map. The closure’s start and end coordinates must have the same street name. |
| NO_ROUTE_BETWEEN_CANDIDATES | Waze can’t find a route that matches the polyline. This happens for one of the following reasons: There is no drivable path between the start and end points, the polyline goes over a different street in the middle, or the route includes a roundabout. |
| END_SEGMENT_FOUND_WITH_OPPOSITE_DIRECTION | The traffic direction at the end of the polyline is opposite to the road’s direction. This means the start and end of the closure have different traffic directions. |
| ROUTE_FOUND_BUT_DOES_NOT_MATCH_POLYLINE | The shared polyline doesn’t match any available routes because the geometry is too far apart. This occurs if any part of the polyline is more than 50 meters away from a nearby segment. |
| ROUTE_CONTAINS_UNSUPPORTED_SEGMENT_TYPE | The segment type isn’t supported for Feed closures. For example, Partner Feeds can’t share closures on a “Non-Routable Pedestrian Path.” |
| PARTNER_POLYLINE_EXCEEDS_MAX_DISTANCE | The polyline exceeds 20 km. Break this into several events with shorter polylines. |
| TOO_MANY_CLOSURES | The time range for a closure exceeds the limit of 150. If you exceed this, break the event into several events with different schedules.
Example: A single closure event from Saturday, June 14, 9 AM to Sunday, June 22, 9 PM with the schedule below counts as 6 separate time ranges.
Schedule:
Total time ranges (6 total):
|
| MISSING_START_TIME | The start time is missing. |
| FEED_CONFIGURATION | The Feed is configured to generate map problems for review instead of applying closures directly to the map. |
| BACKEND_ERROR | We’re still investigating this error. |