Suggestion for timestamp data in RTTI

[Ashcon Partovi]

When querying bus data, you currently receive a human-readable version of the last seen timestamp of a bus (ie. "04:56:17 pm"). This creates edge-case problems at midnight where the timestamp is relative to the previous day and the query is in the next day. I'm also guessing daylight savings shifts will also skew data. It would be a lot simpler for developers if this data was in ISO format, so we don't have to guess the date of the timestamp. Virtually every Translink application/api I've seen on GitHub tries to guess the ISO-format and I thought it would be easier and safer if this information was just provided in the first place.

[Dennis Tsang]

Agreed with this!

Dennis

On Sat, Oct 20, 2018 at 17:04 Ashcon Partovi <ashcon....@gmail.com> wrote:

When querying bus data, you currently receive a human-readable version of the last seen timestamp of a bus (ie. "04:56:17 pm"). This creates edge-case problems at midnight where the timestamp is relative to the previous day and the query is in the next day. I'm also guessing daylight savings shifts will also skew data. It would be a lot simpler for developers if this data was in ISO format, so we don't have to guess the date of the timestamp. Virtually every Translink application/api I've seen on GitHub tries to guess the ISO-format and I thought it would be easier and safer if this information was just provided in the first place.

--
You received this message because you are subscribed to the Google Groups "TransLink Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to translink-develo...@googlegroups.com.
To post to this group, send email to translink-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/translink-developers/5752f6eb-ad9b-47f0-a2e8-194bd50840e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Fraser Parlane]

+1 on this.

On Saturday, October 20, 2018 at 6:25:39 PM UTC-7, Dennis Tsang wrote:

Agreed with this!

Dennis

On Sat, Oct 20, 2018 at 17:04 Ashcon Partovi <ashcon...@gmail.com> wrote:

When querying bus data, you currently receive a human-readable version of the last seen timestamp of a bus (ie. "04:56:17 pm"). This creates edge-case problems at midnight where the timestamp is relative to the previous day and the query is in the next day. I'm also guessing daylight savings shifts will also skew data. It would be a lot simpler for developers if this data was in ISO format, so we don't have to guess the date of the timestamp. Virtually every Translink application/api I've seen on GitHub tries to guess the ISO-format and I thought it would be easier and safer if this information was just provided in the first place.

--
You received this message because you are subscribed to the Google Groups "TransLink Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to translink-developers+unsub...@googlegroups.com.