last_updated_on doesn't update properly?

[Jacob Lynn]

I'm using the Mashape API and the last_updated_on field seems to be inaccurate.

If I repeatedly request the /vehicles.json endpoint for a given agency, the buses are clearly moving, because the lat/lons, etc for a given vehicle_id will change. However, the last_updated_on for a given vehicle_id stays the same over many requests. In general, the timestamp seems to only change every 10 minutes or so, while the underlying data is changing quite frequently, every 30 seconds or less.

Is this behavior a bug? If not, there doesn't seem to be any other way to see how "fresh" a given location is, or exactly what timestamp it's associated with. I've noticed the same behavior with several agencies (Triangle Transit, Chapel Hill, etc).

[Stu Zhao]

Hi Jacob,

It is a behavior. The field "last_updated_on" does not reflect the position update time. I agree that the API needs to reflect position update time. We'll look for a fix in the near future.

--

Yanglei (Stu) Zhao

TransLōc, Inc.

Email: stu....@transloc.com

--
You received this message because you are subscribed to the Google Groups "TransLoc API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to transloc-api...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Stu Zhao]

Hi Jacob,

We just deployed a fix that made "last_updated_on" reflect the previous location update time.

[Jacob Lynn]

Thanks Stu! I can confirm that the APIs I checked (Chapel Hill and Triangle Transit) are now working as intended.