Time in milliseconds - Revision history

Frank@tygron.nl at 14:20, 13 April 2026

2026-04-13T14:20:07Z

← Older revision		Revision as of 14:20, 13 April 2026
Line 10:		Line 10:
	{{article end		{{article end
	\|seealso=		\|seealso=
	* [[Dates (Heat Overlay)]]		* [[Dates (Heat Stress Overlay)]]
	}}		}}
	[[Category:unit]]		[[Category:unit]]

Frank@tygron.nl at 16:01, 21 February 2023

2023-02-21T16:01:25Z

← Older revision		Revision as of 16:01, 21 February 2023
Line 8:		Line 8:
	: Keep this in mind when manually adjusting attributes representing time in milliseconds, or when interpreting time data using the API.		: 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]]		[[Category:unit]]

Frank@tygron.nl at 10:08, 21 July 2020

2020-07-21T10:08:47Z

← Older revision		Revision as of 10:08, 21 July 2020
Line 7:		Line 7:
	: 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.		: 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.		: Keep this in mind when manually adjusting attributes representing time in milliseconds, or when interpreting time data using the API.


			[[Category:unit]]

Frank@tygron.nl: /* Notes */

2020-07-21T10:08:06Z

Notes

← Older revision		Revision as of 10:08, 21 July 2020
Line 5:		Line 5:
	==Notes==		==Notes==
	* Items in the {{software}} can store time as an attribute, in which case this number is stored as a double.		* 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.		: 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.

Frank@tygron.nl: /* Notes */

2020-07-21T10:07:46Z

Notes

← Older revision		Revision as of 10:07, 21 July 2020
Line 4:		Line 4:

	==Notes==		==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.		* 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.

Frank@tygron.nl: /* Notes */

2020-07-21T10:02:44Z

Notes

← Older revision		Revision as of 10:02, 21 July 2020
Line 4:		Line 4:

	==Notes==		==Notes==
	* ~~Time is sometimes stored~~ as an attribute, in which case this number is stored as a double. When ~~interpretated~~ by the {{software}}, this double number is first converted to a long number 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.		* 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.

Frank@tygron.nl at 10:00, 21 July 2020

2020-07-21T10:00:50Z

← Older revision		Revision as of 10:00, 21 July 2020
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==
			* Time is sometimes stored as an attribute, in which case this number is stored as a double. When interpretated by the {{software}}, this double number is first converted to a long number 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.

Frank@tygron.nl at 09:49, 21 July 2020

2020-07-21T09:49:53Z

← Older revision		Revision as of 09:49, 21 July 2020
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].		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].

Frank@tygron.nl: Created page with "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]."

2020-07-21T09:35:05Z

Created page with "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]."

New page

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].