Dados de vias em tempo real

Os dados de trânsito em tempo real fornecem atualizações sobre as condições das vias e eventos nas rotas selecionadas, permitindo monitoramento dinâmico e resposta rápida. Esses dados são diferentes dos coletados periodicamente disponíveis no BigQuery e são adequados para cenários que exigem informações oportunas.

Esses dados são transmitidos continuamente e incluem o tempo de viagem, que indica os tempos de deslocamento em um trajeto, e os intervalos de leitura de velocidade, que mostram a densidade do trânsito ao longo do trajeto.

Para acessar dados de vias em tempo real, seu contrato precisa incluir o pacote de operações em tempo real.

Criar uma assinatura do Pub/Sub para intervalos de leitura de velocidade e duração da viagem

Você vai receber tópicos dedicados do Google Cloud Pub/Sub, que são onde é possível assinar os dados em tempo real de todas as rotas criadas.

O exemplo de código a seguir mostra o formato do tópico usando codificação binária:

projects/maps-platform-roads-management/topics/rmi-roadsinformation-PROJECT_NUMBER

Também fornecemos outro tópico usando codificação JSON (com o sufixo -json). Você precisa se inscrever no tópico do Pub/Sub fornecido para receber mensagens de dados em tempo real. Consulte Inscrever-se em um tópico para ter uma visão geral rápida de como se inscrever e consumir mensagens de um tópico do Cloud Pub/Sub.

Esquema de duração da viagem e intervalos de leitura rápida

Cada mensagem de dados em tempo real incorpora dados como:

  • Detalhes da via, como duration_in_seconds, static_duration_in_seconds, speed_reading_offsets (intervalos de leitura de velocidade com base em deslocamento) e retrieval_timestamp.
  • Identificadores de rota, como selected_route_id e display_name.

Cada mensagem é publicada seguindo o formato Protobuf abaixo.

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.
  repeated SpeedReadingOffset speed_reading_offsets = 8;
  // The duration of travel through the route based on current traffic
  // conditions.
  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;
}

Intervalos de leitura rápida com base em ajuste e migração de campos

Desde 8 de outubro de 2026, os intervalos de leitura rápida são fornecidos no campo speed_reading_offsets com base no deslocamento, em que cada intervalo é demarcado por start_offset (inclusivo) e end_offset (exclusivo) em metros desde o início do trajeto, e inclui a quarta categoria de velocidade TRAFFIC_JAM_HEAVY. Para detalhes sobre categorias de velocidade e formatos de intervalo, consulte Intervalos de leitura dinâmica.

A tabela a seguir mapeia cada campo legado do Pub/Sub (que pode deixar de ser preenchido a partir de 9 de novembro de 2026) para o substituto:

Campo legado Campo de substituição Observações
speed_reading_intervals speed_reading_offsets Usa offsets de metro (start_offset, end_offset) em vez de coordenadas de polilinha e adiciona a categoria de velocidade TRAFFIC_JAM_HEAVY.
travel_duration.duration_in_seconds duration_in_seconds Nivelado em um campo float de nível superior.
travel_duration.static_duration_in_seconds static_duration_in_seconds Nivelado em um campo float de nível superior.
retrieval_time retrieval_timestamp Formatado como uma string RFC 3339, que as assinaturas do BigQuery convertem automaticamente em TIMESTAMP.

Transmitir dados de rota para o BigQuery usando o Pub/Sub

É possível configurar uma assinatura do Pub/Sub para transmitir dados de vias diretamente para uma tabela do BigQuery. Isso permite um armazenamento de dados robusto e análises avançadas das informações de rota fornecidas. Antes de configurar esse tipo de assinatura, crie um conjunto de dados e uma tabela adequados no projeto do BigQuery para gravar os dados.

Para instruções detalhadas sobre como criar uma assinatura do Pub/Sub que grava no BigQuery, consulte Streaming de dados para o BigQuery. Crie a assinatura do BigQuery no tópico codificado em JSON. Ao configurar a assinatura, selecione Usar esquema de tabela e ative Descartar campos desconhecidos para que o pipeline de ingestão continue funcionando sem problemas quando novos campos forem adicionados. Para armazenar novos campos, como speed_reading_offsets, adicione as colunas correspondentes à sua tabela.

Esquema da tabela do BigQuery

As mensagens publicadas no seu tópico do Pub/Sub, que também podem ser gravadas na sua tabela do BigQuery, obedecem ao seguinte esquema. Use esse esquema ao criar a tabela de destino do BigQuery para garantir a compatibilidade.

[
  {
    "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."
  },
  {
    "mode": "NULLABLE",
    "name": "duration_in_seconds",
    "type": "FLOAT",
    "description": "The duration of travel through the route based on current traffic conditions."
  },
  {
    "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."
  }
]