You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's no field to enable remaining-route reporting, even though the API supports it: enabling it makes trip-update notifications include the remainingRoute (GeoJSON polyline + per-segment traffic), as documented in Handle trip data and the Pub/Sub reference. We understand the corresponding field is enable_remaining_route_reporting (field 4), but it isn't present in the published proto.
Impact
gRPC clients generated from this proto can't request the remaining route, so their notifications never include remainingRoute.
As a workaround we hand-add enable_remaining_route_reporting = 4 to our vendored copy and set it on CreateTrip — this diverges from upstream.
Tested locally: with the field added and set on CreateTrip, the live API accepts the request and the resulting Pub/Sub notifications include remainingRoute — confirming the field exists server-side at number 4 and just isn't published here.
Request
Please publish enable_remaining_route_reporting (field 4) to TripConfig so the public gRPC proto matches the API behavior.
We could also open a PR if needed.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi team 👋 thanks for publishing and maintaining these API definitions. We ran into a small gap in the Nav Connect proto and wanted to flag it.
Discrepancy
In
google/maps/navconnect/v1/navconnect_service.proto, messageTripConfigexposes only:enable_high_frequency_updates = 1enable_pubsub = 2pubsub_field_mask = 3There's no field to enable remaining-route reporting, even though the API supports it: enabling it makes trip-update notifications include the
remainingRoute(GeoJSON polyline + per-segment traffic), as documented in Handle trip data and the Pub/Sub reference. We understand the corresponding field isenable_remaining_route_reporting(field 4), but it isn't present in the published proto.Impact
gRPC clients generated from this proto can't request the remaining route, so their notifications never include
remainingRoute.As a workaround we hand-add
enable_remaining_route_reporting = 4to our vendored copy and set it onCreateTrip— this diverges from upstream.Tested locally: with the field added and set on
CreateTrip, the live API accepts the request and the resulting Pub/Sub notifications includeremainingRoute— confirming the field exists server-side at number 4 and just isn't published here.Request
Please publish
enable_remaining_route_reporting(field 4) toTripConfigso the public gRPC proto matches the API behavior.We could also open a PR if needed.
All reactions