Echtzeit-Straßendaten bieten aktuelle Informationen zu Straßenzuständen und Ereignissen auf Ihren ausgewählten Routen, was ein dynamisches Monitoring und eine schnelle Reaktion ermöglicht. Diese Daten unterscheiden sich von den regelmäßig erfassten Daten, die in BigQuery verfügbar sind, und eignen sich für Szenarien, in denen aktuelle Informationen erforderlich sind.
Diese Daten werden kontinuierlich gestreamt und umfassen die Fahrtdauer, die die Fahrtzeiten auf einer Route angibt, sowie Intervalle für Geschwindigkeitsmessungen, die die Verkehrsdichte entlang der Route zeigen.
Damit Sie auf Echtzeit-Straßendaten zugreifen können, muss Ihr Vertrag das Paket „Real-Time Operations“ enthalten.
Pub/Sub-Abo für Intervalle für Reisedauer und Geschwindigkeitsmessung erstellen
Sie erhalten dedizierte Google Cloud Pub/Sub-Themen, über die Sie die Echtzeitdaten für alle von Ihnen erstellten Routen abonnieren können.
Das folgende Codebeispiel zeigt das Format des Themas mit binärer Codierung:
projects/maps-platform-roads-management/topics/rmi-roadsinformation-PROJECT_NUMBER
Wir stellen auch ein weiteres Thema mit JSON-Codierung (mit dem Suffix -json) bereit. Sie müssen das Ihnen bereitgestellte Pub/Sub-Thema abonnieren, um Echtzeit-Datennachrichten zu erhalten. Eine kurze Übersicht zum Abonnieren und Verarbeiten von Nachrichten aus einem Cloud Pub/Sub-Thema finden Sie unter Thema abonnieren.
Schema für Reisedauer und Geschwindigkeitsmessintervalle
Jede Echtzeitdatennachricht enthält Daten wie:
- Straßendetails wie
duration_in_seconds,static_duration_in_seconds,speed_reading_offsets(offsetbasierte Intervalle für Geschwindigkeitsmessungen),retrieval_timestampundhas_road_closure. - Routenkennungen wie
selected_route_idunddisplay_name.
Jede Nachricht wird im folgenden Protobuf-Format veröffentlicht.
syntax = "proto3"; // Contains the road information like travel duration and speed reading // intervals for a selected route. message RoadsInformation { // Legacy message. May stop being populated on or after November 9, 2026. // Use top-level duration_in_seconds and static_duration_in_seconds instead. message TravelDuration { // The duration of travel through the route based on current road // conditions. float duration_in_seconds = 1; // The duration of travel through the route without taking road // conditions into consideration. float static_duration_in_seconds = 2; } message Timestamp { // Represents seconds of UTC time since Unix epoch // 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to // 9999-12-31T23:59:59Z inclusive. int64 seconds = 1; // Non-negative fractions of a second at nanosecond resolution. Negative // second values with fractions must still have non-negative nanos values // that count forward in time. Must be from 0 to 999,999,999 // inclusive. int32 nanos = 2; } // Legacy message representing the latitude and longitude of a coordinate // within a coordinate-based speed reading interval. message LatLng { float latitude = 1; float longitude = 2; } // Legacy coordinate-based speed reading interval message. May stop being // populated on or after November 9, 2026. Use SpeedReadingOffset instead. message SpeedReadingInterval { // The coordinates on the polyline for the speed reading interval. repeated LatLng interval_coordinates = 1; // Describes the categorized current speed of road conditions. // Possible values are: // - "NORMAL": Road is flowing smoothly, no slowdown is detected. // - "SLOW": Slowdown detected, but no congestion formed. // - "TRAFFIC_JAM": Traffic jam detected. In this legacy field, heavy // traffic jams (dark red) are also reported as "TRAFFIC_JAM"; // "TRAFFIC_JAM_HEAVY" is never used. string speed = 2; } // Offset-based speed reading interval along the route. message SpeedReadingOffset { // The distance offset from the start of the route in meters for the start // of the interval (inclusive). int32 start_offset = 1; // The distance offset from the start of the route in meters for the end of // the interval (exclusive; equals the start_offset of the subsequent // interval). int32 end_offset = 2; // Describes the categorized current speed of traffic, aligned with the // colors in the Google Maps traffic layer. Possible values are: // - "NORMAL" (green): Traffic is flowing smoothly, no slowdown is detected. // - "SLOW" (yellow): Slowdown detected, but no traffic jam formed. // - "TRAFFIC_JAM" (red): Traffic jam detected. // - "TRAFFIC_JAM_HEAVY" (dark red): Heavy traffic jam detected (available // as of October 8, 2026). string speed = 3; } // Id for selected_route. string selected_route_id = 1; // User provided name for the route. string display_name = 2; // Legacy coordinate-based speed reading intervals. May stop being populated // on or after November 9, 2026. Use speed_reading_offsets instead. repeated SpeedReadingInterval speed_reading_intervals = 3; // Legacy travel time information. May stop being populated on or after // November 9, 2026. Use duration_in_seconds and static_duration_in_seconds // instead. TravelDuration travel_duration = 4; // Legacy timestamp when the road data was collected. May stop being populated // on or after November 9, 2026. Use retrieval_timestamp instead. Timestamp retrieval_time = 5; // Contains a geojson polyline representing the optimal route determined // based on user's input waypoints. string route_geometry = 6; // Road segment place IDs along the route. They follow topological order // and are always connected. repeated string road_segment_ids = 7; // Offset-based speed reading intervals representing traffic density across // the route; each interval is demarcated by the distance offset from the // start of the route. Omitted when has_road_closure is true. repeated SpeedReadingOffset speed_reading_offsets = 8; // The duration of travel through the route based on current traffic // conditions. Omitted when has_road_closure is true. float duration_in_seconds = 9; // The duration of travel through the route without taking traffic // conditions into consideration. float static_duration_in_seconds = 10; // The time the traffic data was collected, as an RFC 3339 UTC timestamp // string (for example, "2026-10-08T15:04:05+00:00"). string retrieval_timestamp = 11; // Whether there is a full road closure on the route. When true, // duration_in_seconds and speed_reading_offsets are omitted because the // route is impassable. Omitted when road closure information is undetermined. bool has_road_closure = 12; }
Offsetbasierte Geschwindigkeitsmessintervalle und Feldmigration
Ab dem 8. Oktober 2026 werden Geschwindigkeitsintervalle im versatzbasierten Feld speed_reading_offsets angegeben. Jedes Intervall wird durch start_offset (einschließlich) und end_offset (ausschließlich) in Metern vom Start der Route abgegrenzt und enthält die vierte Geschwindigkeitskategorie TRAFFIC_JAM_HEAVY. Weitere Informationen zu Geschwindigkeitskategorien und Intervallformaten finden Sie unter Intervalle für Geschwindigkeitsmessungen.
In der folgenden Tabelle wird jedes Legacy-Pub/Sub-Feld (das ab dem 9. November 2026 möglicherweise nicht mehr ausgefüllt wird) dem entsprechenden Ersatzfeld zugeordnet:
| Legacy-Feld | Ersatzfeld | Hinweise |
|---|---|---|
speed_reading_intervals |
speed_reading_offsets |
Verwendet Meter-Offsets (start_offset, end_offset) anstelle von Polylinienkoordinaten und fügt die Geschwindigkeitskategorie TRAFFIC_JAM_HEAVY hinzu. |
travel_duration.duration_in_seconds |
duration_in_seconds |
Wird zu einem übergeordneten float-Feld vereinfacht. |
travel_duration.static_duration_in_seconds |
static_duration_in_seconds |
Wird zu einem übergeordneten float-Feld vereinfacht. |
retrieval_time |
retrieval_timestamp |
Formatiert als RFC 3339-String, der von BigQuery-Abos automatisch in TIMESTAMP konvertiert wird. |
Routendaten mit Pub/Sub zu BigQuery streamen
Sie können ein Pub/Sub-Abo so konfigurieren, dass Straßendaten direkt in eine BigQuery-Tabelle gestreamt werden. Dies ermöglicht eine robuste Datenspeicherung und leistungsstarke Analysen der bereitgestellten Routeninformationen. Bevor Sie diese Art von Abo einrichten, müssen Sie in Ihrem BigQuery-Projekt ein geeignetes Dataset und eine geeignete Tabelle erstellen, in die die Daten geschrieben werden sollen.
Eine ausführliche Anleitung zum Erstellen eines Pub/Sub-Abos, das in BigQuery schreibt, finden Sie unter Daten in BigQuery streamen.
Erstellen Sie das BigQuery-Abo für das JSON-codierte Thema. Wählen Sie beim Konfigurieren des Abos Tabellenschema verwenden aus und aktivieren Sie Unbekannte Felder verwerfen, damit Ihre Aufnahmepipeline auch dann reibungslos funktioniert, wenn neue Felder hinzugefügt werden. Wenn Sie neue Felder wie speed_reading_offsets speichern möchten, fügen Sie der Tabelle die entsprechenden Spalten hinzu.
Schema der BigQuery-Tabelle
Die in Ihrem Pub/Sub-Thema veröffentlichten Nachrichten, die auch in Ihre BigQuery-Tabelle geschrieben werden können, entsprechen dem folgenden Schema. Sie sollten dieses Schema beim Erstellen Ihrer BigQuery-Zieltabelle verwenden, um die Kompatibilität zu gewährleisten.
[ { "mode": "NULLABLE", "name": "selected_route_id", "type": "STRING", "description": "Id for selected_route." }, { "mode": "NULLABLE", "name": "display_name", "type": "STRING", "description": "User provided name for the route." }, { "fields": [ { "mode": "NULLABLE", "name": "speed", "type": "STRING", "description": "Describes the categorized current speed of traffic. Possible values are: \"NORMAL\": Traffic is flowing smoothly, no slowdown is detected. \"SLOW\": Slowdown detected, but no traffic jam formed. \"TRAFFIC_JAM\": Traffic jam detected (groups red and dark red segments; does not include \"TRAFFIC_JAM_HEAVY\")." }, { "fields": [ { "mode": "NULLABLE", "name": "latitude", "type": "NUMERIC" }, { "mode": "NULLABLE", "name": "longitude", "type": "NUMERIC" } ], "mode": "REPEATED", "name": "interval_coordinates", "type": "RECORD", "description": "The geometry for this interval" } ], "mode": "REPEATED", "name": "speed_reading_intervals", "type": "RECORD", "description": "Legacy coordinate-based speed reading intervals. May stop being populated on or after November 9, 2026. Use speed_reading_offsets instead." }, { "fields": [ { "mode": "NULLABLE", "name": "duration_in_seconds", "type": "FLOAT", "description": "The duration of travel through the route based on\ncurrent traffic conditions." }, { "mode": "NULLABLE", "name": "static_duration_in_seconds", "type": "FLOAT", "description": "The duration of travel through the route without\ntaking traffic conditions into consideration." } ], "mode": "NULLABLE", "name": "travel_duration", "type": "RECORD", "description": "Legacy travel time information. May stop being populated on or after November 9, 2026. Use top-level duration_in_seconds and static_duration_in_seconds instead." }, { "fields": [ { "mode": "NULLABLE", "name": "seconds", "type": "INTEGER", "description": "Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive." }, { "mode": "NULLABLE", "name": "nanos", "type": "INTEGER", "description": "Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive." } ], "mode": "NULLABLE", "name": "retrieval_time", "type": "RECORD", "description": "Legacy timestamp when the traffic data was collected. May stop being populated on or after November 9, 2026. Use retrieval_timestamp instead." }, { "mode": "NULLABLE", "name": "route_geometry", "type": "STRING", "description": "Contains a geojson polyline representing the optimal route determined based on user's input waypoints" }, { "mode": "REPEATED", "name": "road_segment_ids", "type": "STRING", "description": "Road segment place IDs along the route. They follow topological order and are always connected" }, { "fields": [ { "mode": "NULLABLE", "name": "start_offset", "type": "INTEGER", "description": "The distance offset from the start of the route in meters for the start of the interval (inclusive)." }, { "mode": "NULLABLE", "name": "end_offset", "type": "INTEGER", "description": "The distance offset from the start of the route in meters for the end of the interval (exclusive; equals the start_offset of the subsequent interval)." }, { "mode": "NULLABLE", "name": "speed", "type": "STRING", "description": "Describes the categorized current speed of traffic, aligned with the colors in the Google Maps traffic layer. Possible values are: \"NORMAL\" (green): Traffic is flowing smoothly, no slowdown is detected. \"SLOW\" (yellow): Slowdown detected, but no traffic jam formed. \"TRAFFIC_JAM\" (red): Traffic jam detected. \"TRAFFIC_JAM_HEAVY\" (dark red): Heavy traffic jam detected (available as of October 8, 2026)." } ], "mode": "REPEATED", "name": "speed_reading_offsets", "type": "RECORD", "description": "Offset-based speed reading intervals representing traffic density across the route; each interval is demarcated by the distance offset from the start of the route. Omitted when has_road_closure is true." }, { "mode": "NULLABLE", "name": "duration_in_seconds", "type": "FLOAT", "description": "The duration of travel through the route based on current traffic conditions. Omitted when has_road_closure is true." }, { "mode": "NULLABLE", "name": "static_duration_in_seconds", "type": "FLOAT", "description": "The duration of travel through the route without taking traffic conditions into consideration." }, { "mode": "NULLABLE", "name": "retrieval_timestamp", "type": "TIMESTAMP", "description": "The time the traffic data was collected." }, { "mode": "NULLABLE", "name": "has_road_closure", "type": "BOOLEAN", "description": "Whether there is a full road closure on the route. When true, duration_in_seconds and speed_reading_offsets are omitted because the route is impassable. A NULL value indicates that road closure information is undetermined." } ]