Time in milliseconds: Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
A time in milliseconds of 0, corresponds to 00:00:00:000 January 1st, 1970 in the [https://en.wikipedia.org/wiki/Coordinated_Universal_Time UTC time zone].
Time can be stored as a number of milliseconds past a chosen starting point, also known as the epoch.
 
In the {{software}}, a time in milliseconds of 0, corresponds to 00:00:00:000 January 1st, 1970 in the [https://en.wikipedia.org/wiki/Coordinated_Universal_Time UTC time zone].
 
==Notes==
* Items in the {{software}} can store time as an attribute, in which case this number is stored as a double.
: When interpreted by the {{software}}, this double (decimal) number is first converted to a long number  (no decimals, but larger range) before interpreting this as a time offset in milliseconds.
: Keep this in mind when manually adjusting attributes representing time in milliseconds, or when interpreting time data using the API.
 
{{article end
|seealso=
* [[Dates (Heat Overlay)]]
}}
[[Category:unit]]

Latest revision as of 16:01, 21 February 2023

Time can be stored as a number of milliseconds past a chosen starting point, also known as the epoch.

In the Tygron Platform, a time in milliseconds of 0, corresponds to 00:00:00:000 January 1st, 1970 in the UTC time zone.

Notes

  • Items in the Tygron Platform can store time as an attribute, in which case this number is stored as a double.
When interpreted by the Tygron Platform, this double (decimal) number is first converted to a long number (no decimals, but larger range) before interpreting this as a time offset in milliseconds.
Keep this in mind when manually adjusting attributes representing time in milliseconds, or when interpreting time data using the API.