Stay organized with collections
Save and categorize content based on your preferences.
You can provide information about garbage trucks and snowplows through a
feed. The appropriate vehicle (see above for illustrations) can then be
presented both in the Waze map and the Live Map based on the listing details
you provide. These listings won’t affect estimated times of arrival or
navigation for car drivers who are using the Waze app.
Moving vehicle elements
Use the parameters in the following table to create a moving vehicle feed.
This feed is a separate feed file from the
incidents and
road closure feed files.
| Element |
Required? |
Tag input |
Description |
| truck |
Required |
Free text |
A unique ID for each vehicle. It must be at least 3 alphanumeric
characters in length.
<truck id="qV11DEayKr">...</truck> |
| location |
Required |
Lat lon |
Latitude and longitude coordinates that describe the location of the
vehicle. It should have at least 6 values after the decimal point for
sufficient accuracy.
<location>40.510090 -110.006902</location>
|
| status |
Required |
WORKING or NOT_WORKING |
Whether or not the vehicle is in service.
<status>WORKING</status>
|
| type |
Required |
GARBAGE or SNOW |
The specific vehicle type.
<type>SNOW</type>
|
| heading |
Required |
azimuth |
The vehicle heading direction in degrees. This is a positive integer
between 0 and 359. (0 = North, 90 = East, and so on.)
<heading>120</heading>
|
Moving vehicle examples
The following examples show a single moving vehicle entry in both XML and
JSON formats.
XML example
The following is an example of a single moving vehicle item in XML.
<truck id="45345345">
<location>51.510090 -0.006902</location>
<status>NOT_WORKING</status>
<type>SNOW</type>
<heading>50</heading>
<speed_kmh>7</speed_kmh>
<updatetime>2018-09-04-01T00:00:00-05:00</updatetime>
</truck>
JSON example
The following is an example of a single moving vehicle item in JSON.
{
"id": "45345345",
"location": "51.510090 -0.006902",
"status": "NOT_WORKING",
"type": "SNOW",
"heading": "50",
"speed_kmh": "7"
}
The following examples show an entire incident feed file in both XML and
JSON formats.
XML feed file
The following is an example of a complete moving vehicle feed file
using XML.
<trucks>
<truck id="45345345">
<location>51.510090 -0.006902</location>
<status>NOT_WORKING</status>
<type>SNOW</type>
<heading>50</heading>
<speed_kmh>7</speed_kmh>
<updatetime>2024-09-04T00:00:00-05:00</updatetime>
</truck>
<truck id="545346">
<location>50.310090 -0.006923</location>
<status>WORKING</status>
<type>SNOW</type>
<heading>120</heading>
<speed_kmh>32</speed_kmh>
<updatetime>2024-10-03T00:00:00-05:00</updatetime>
</truck>
<truck id="345345567">
<location>51.500090 -0.004702</location>
<status>NOT_WORKING</status>
<type>SNOW</type>
<heading>120</heading>
<speed_kmh>0</speed_kmh>
<updatetime>2024-09-30T00:00:00-05:00</updatetime>
</truck>
</trucks>
JSON feed file
The following is an example of a complete moving vehicle feed file
using JSON.
{
"trucks": [
{
"id": "45345345",
"location": "51.510090 -0.006902",
"status": "NOT_WORKING",
"type": "SNOW",
"heading": "50"
},
{
"id":"545346",
"location": "50.310090 -0.006923",
"status": "WORKING",
"type": "SNOW",
"heading": "120"
},
{
"id":"345345567",
"location": "51.500090 -0.004702",
"status": "NOT_WORKING",
"type": "SNOW",
"heading": "120"
}
]
}
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 2024-10-29 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 2024-10-29 UTC."],[[["\u003cp\u003eShare real-time locations of garbage trucks and snowplows through a data feed for display on Waze maps.\u003c/p\u003e\n"],["\u003cp\u003eThis data feed does not impact Waze's navigation or estimated arrival times for regular drivers.\u003c/p\u003e\n"],["\u003cp\u003eDefine each vehicle with a unique ID, location, status (working or not), type (garbage or snow), and heading.\u003c/p\u003e\n"],["\u003cp\u003eData feeds can be provided in either XML or JSON format, adhering to the specified structure and parameters.\u003c/p\u003e\n"],["\u003cp\u003eRefer to provided examples for structuring individual vehicle entries and complete feed files in both XML and JSON.\u003c/p\u003e\n"]]],["A feed provides real-time information about garbage trucks and snowplows, displayed on Waze maps. Each vehicle entry requires a unique alphanumeric ID, precise latitude/longitude coordinates, and a status (WORKING/NOT_WORKING). It should also include a vehicle type (GARBAGE/SNOW) and heading direction in degrees. This feed, distinct from incident/road closure feeds, does not affect driver ETAs. Examples are provided in XML and JSON formats, showcasing single entries and entire feed files.\n"],null,["Moving vehicle information\n==========================\n\n\nYou can provide information about garbage trucks and snowplows through a\nfeed. The appropriate vehicle (see above for illustrations) can then be\npresented both in the Waze map and the Live Map based on the listing details\nyou provide. These listings won't affect estimated times of arrival or\nnavigation for car drivers who are using the Waze app.\n\n\u003cbr /\u003e\n\nMoving vehicle elements\n-----------------------\n\nUse the parameters in the following table to create a moving vehicle feed.\nThis feed is a separate feed file from the\n[incidents](../data-feed/incident-information) and\n[road closure](../data-feed/road-closure-information) feed files.\n\n| Element | Required? | Tag input | Description |\n|----------|-----------|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| truck | Required | Free text | A unique ID for each vehicle. It must be at least 3 alphanumeric characters in length. ``` \u003ctruck id=\"qV11DEayKr\"\u003e...\u003c/truck\u003e ``` |\n| location | Required | Lat lon | Latitude and longitude coordinates that describe the location of the vehicle. It should have at least 6 values after the decimal point for sufficient accuracy. ``` \u003clocation\u003e40.510090 -110.006902\u003c/location\u003e ``` |\n| status | Required | `WORKING` or `NOT_WORKING` | Whether or not the vehicle is in service. ``` \u003cstatus\u003eWORKING\u003c/status\u003e ``` |\n| type | Required | `GARBAGE` or `SNOW` | The specific vehicle type. ``` \u003ctype\u003eSNOW\u003c/type\u003e ``` |\n| heading | Required | azimuth | The vehicle heading direction in degrees. This is a positive integer between 0 and 359. (0 = North, 90 = East, and so on.) ``` \u003cheading\u003e120\u003c/heading\u003e ``` |\n\nMoving vehicle examples\n-----------------------\n\nThe following examples show a single moving vehicle entry in both XML and\nJSON formats. \n\n### XML example\n\nThe following is an example of a single moving vehicle item in XML. \n\n```carbon\n\u003ctruck id=\"45345345\"\u003e\n \u003clocation\u003e51.510090 -0.006902\u003c/location\u003e\n \u003cstatus\u003eNOT_WORKING\u003c/status\u003e\n \u003ctype\u003eSNOW\u003c/type\u003e\n \u003cheading\u003e50\u003c/heading\u003e\n \u003cspeed_kmh\u003e7\u003c/speed_kmh\u003e\n \u003cupdatetime\u003e2018-09-04-01T00:00:00-05:00\u003c/updatetime\u003e\n\u003c/truck\u003e\n```\n\n### JSON example\n\nThe following is an example of a single moving vehicle item in JSON. \n\n```carbon\n{\n \"id\": \"45345345\",\n \"location\": \"51.510090 -0.006902\",\n \"status\": \"NOT_WORKING\",\n \"type\": \"SNOW\",\n \"heading\": \"50\",\n \"speed_kmh\": \"7\"\n}\n```\n\nThe following examples show an entire incident feed file in both XML and\nJSON formats. \n\n### XML feed file\n\nThe following is an example of a complete moving vehicle feed file\nusing XML. \n\n```carbon\n\u003ctrucks\u003e\n \u003ctruck id=\"45345345\"\u003e\n \u003clocation\u003e51.510090 -0.006902\u003c/location\u003e\n \u003cstatus\u003eNOT_WORKING\u003c/status\u003e\n \u003ctype\u003eSNOW\u003c/type\u003e\n \u003cheading\u003e50\u003c/heading\u003e\n \u003cspeed_kmh\u003e7\u003c/speed_kmh\u003e\n \u003cupdatetime\u003e2024-09-04T00:00:00-05:00\u003c/updatetime\u003e\n \u003c/truck\u003e\n \u003ctruck id=\"545346\"\u003e\n \u003clocation\u003e50.310090 -0.006923\u003c/location\u003e\n \u003cstatus\u003eWORKING\u003c/status\u003e\n \u003ctype\u003eSNOW\u003c/type\u003e\n \u003cheading\u003e120\u003c/heading\u003e\n \u003cspeed_kmh\u003e32\u003c/speed_kmh\u003e\n \u003cupdatetime\u003e2024-10-03T00:00:00-05:00\u003c/updatetime\u003e\n \u003c/truck\u003e\n \u003ctruck id=\"345345567\"\u003e\n \u003clocation\u003e51.500090 -0.004702\u003c/location\u003e\n \u003cstatus\u003eNOT_WORKING\u003c/status\u003e\n \u003ctype\u003eSNOW\u003c/type\u003e\n \u003cheading\u003e120\u003c/heading\u003e\n \u003cspeed_kmh\u003e0\u003c/speed_kmh\u003e\n \u003cupdatetime\u003e2024-09-30T00:00:00-05:00\u003c/updatetime\u003e\n \u003c/truck\u003e\n\u003c/trucks\u003e\n```\n\n### JSON feed file\n\nThe following is an example of a complete moving vehicle feed file\nusing JSON. \n\n```carbon\n{\n \"trucks\": [\n {\n \"id\": \"45345345\",\n \"location\": \"51.510090 -0.006902\",\n \"status\": \"NOT_WORKING\",\n \"type\": \"SNOW\",\n \"heading\": \"50\"\n },\n {\n \"id\":\"545346\",\n \"location\": \"50.310090 -0.006923\",\n \"status\": \"WORKING\",\n \"type\": \"SNOW\",\n \"heading\": \"120\"\n },\n {\n \"id\":\"345345567\",\n \"location\": \"51.500090 -0.004702\",\n \"status\": \"NOT_WORKING\",\n \"type\": \"SNOW\",\n \"heading\": \"120\"\n }\n ]\n}\n```"]]
