Nathan Selikoff

@barbeau good question - just looked and there is not a similar method. However, I found a workaround using `realtime.transit_realtime.Position.toObject`: ```js const feed = realtime.transit_realtime.FeedMessage.decode(protobuf); feed.entity.forEach((entity) => { if (entity.vehicle)...

We asked our Google Transit contact whether to include vehicle entities for non-revenue trips and received this response: > "Regarding cases where the vehicle is not assigned a vehicle or...

@barbeau pretty sure it's the latter. However, they're also indicating that they have recently started integrating the vehicle positions feed into Google Maps. I don't have any details beyond that...

@barbeau FYI Google's QA will currently throw a warning if both `trip_update.delay` and `stop_time_update.arrival/departure.time`are provided, and `trip_update.delay` takes precedence: `INVALID_TRIP_UPDATE_DELAY_USAGE` 

@barbeau I agree, StopTimeEvent `time` is preferable to StopTimeEvent `delay`. In this case Google's warning is about TripUpdate `delay`, which is still listed as experimental in the spec ([GTFS-realtime TripUpdate](https://developers.google.com/transit/gtfs-realtime/reference/#message_tripupdate))....

Thanks for the quick reply and info @martgnz

Thanks @laidig and @barbeau that's helpful. If it's more desirable to have artifacts in Conveyal's Maven repo vs Github that's understandable but in that case updating the README would be...

I've come across this issue as well, with the latest GTFS file from the JTA (not available online at the moment).