Greg Hutchins
Greg Hutchins
I was trying to create directions request with waypoints and passed a bad waypoint object in (extra nesting object around that {lat:..., lng:..} in the array. Effectively waypoints: [ {{lat:..,...
node client libraries for LMFS need these types see: https://developers.google.com/maps/documentation/transportation-logistics/last-mile-fleet-solution/fleet-performance/fleet-engine/gapic_client#nodejs_typescript
This attemps to get sample bigquery queries into a more easily consumed form than our documentation. For now, the set of queries is sources from my somewhat unstructured explorations. Once...
Now that fleet-debugger is reading from bigquery it should be straightforward to start exposing some sample queries that look at the entire fleet, instead of just a single vehicle.
Right now it's not obvious w/o deeply inspecting the jsonpayload that a given operation actually failed.
W/o actual routes in cloud logging we can't compute route deviations ... but we can show when nav sdk thinks the user is off route. Unclear how the OFFROUTE nav...
Actual pickup/dropoff points are redacted from the logs. Can infer locations by the nearest (in time) update vehicle call to the trip status change.
Add a toggle button that will show all the generated routes for a vehicle. Ideally compute a 'deviation score' based on actual route driven vs initial guided route.
fleet-debugger currently focuses on UpdateVehicle and ignores the GetVehicle/trip/task calls. We've been getting bug reports about what the JSJS or consumer SDK sees. we should be able to visualize the...
This is still pretty rough: doesn't support vehicle or time based filtering. But assuming you use the cloud logging ui to filter logs down to the period (and logs) of...