Managing Time Zones and Local Time - Revision history

Ollvihe at 00:15, 17 November 2021

2021-11-17T00:15:13Z

← Older revision		Revision as of 00:15, 17 November 2021
Line 1:		Line 1:
	When importing data to QPR ProcessAnalyzer, date and time data in different local times may be encountered. It's important that the times are interpreted correctly, so that they are comparable and for example durations between timestamps are calculated correctly.		When importing data to QPR ProcessAnalyzer, date and time data in different local times may be encountered. It's important that the times are interpreted correctly, so that they are comparable and for example durations between timestamps are calculated correctly. QPR ProcessAnalyzer doesn't store the time zone information, but instead records timestamps exactly as they have been imported to it. The models can thus contain timestamps from any time zones and it's just a matter of agreement, which time zone the timestamps represent.

	QPR ProcessAnalyzer doesn't store the time zone ~~differences separately~~, but instead ~~uses times that~~ have been imported to it. The models can thus contain timestamps from any time zones and it's just a matter of agreement, which time ~~zones~~ the timestamps ~~are from~~.

	When importing data with [[Importing_Data_to_Datatable_from_CSV_File\|CSV file import]], there is a difference whether timestamps in CSV files have the time zone information. If timestamps don't have the time zone, times are interpreted as such and they appear in the model exactly as imported. If the timestamps have the time zone information, timestamps are imported as UTC, to make timestamps with different time zones comparable with each other. It's also possible to import timestamps without the time zone in the date format (i.e. no "zzz") which will ignore the time zone and import timestamps like they didn't have the time zone information.		When importing data with [[Importing_Data_to_Datatable_from_CSV_File\|CSV file import]], there is a difference whether timestamps in CSV files have the time zone information. If timestamps don't have the time zone, times are interpreted as such and they appear in the model exactly as imported. If the timestamps have the time zone information, timestamps are imported as UTC, to make timestamps with different time zones comparable with each other. It's also possible to import timestamps without the time zone in the date format (i.e. no "zzz") which will ignore the time zone and import timestamps like they didn't have the time zone information.

Ollvihe at 00:13, 17 November 2021

2021-11-17T00:13:46Z

← Older revision		Revision as of 00:13, 17 November 2021
Line 3:		Line 3:
	QPR ProcessAnalyzer doesn't store the time zone differences separately, but instead uses times that have been imported to it. The models can thus contain timestamps from any time zones and it's just a matter of agreement, which time zones the timestamps are from.		QPR ProcessAnalyzer doesn't store the time zone differences separately, but instead uses times that have been imported to it. The models can thus contain timestamps from any time zones and it's just a matter of agreement, which time zones the timestamps are from.

	When importing data with [[Importing_Data_to_Datatable_from_CSV_File\|CSV file import]], timestamps in CSV files ~~may or may not~~ have time zone information. If timestamps don't have the time zone, times are interpreted as such and they appear in the model exactly as imported. If the timestamps have the time zone information, timestamps are imported as UTC, to make timestamps with different time zones comparable with each other. It's also possible to import timestamps without the time zone in the date format ("zzz") which will ignore the time zone and import timestamps like they didn't ~~contain~~ the time zone information.		When importing data with [[Importing_Data_to_Datatable_from_CSV_File\|CSV file import]], there is a difference whether timestamps in CSV files have the time zone information. If timestamps don't have the time zone, times are interpreted as such and they appear in the model exactly as imported. If the timestamps have the time zone information, timestamps are imported as UTC, to make timestamps with different time zones comparable with each other. It's also possible to import timestamps without the time zone in the date format (i.e. no "zzz") which will ignore the time zone and import timestamps like they didn't have the time zone information.

	As a recommended practice, if all time information is in a specific local time, timestamps can be imported in that time zone to QPR ProcessAnalyzer ~~models~~. If there are data where ~~there~~ events ~~recorded in~~ different time zones, it may be better to import timestamps as UTC to avoid any misinterpretation (this is done by including the time zone to the ~~imported~~ timestamps).		As a recommended practice, if all time information in the source data is in a specific local time, timestamps can be imported in that time zone to QPR ProcessAnalyzer. If there are data where events shown with different time zones, it may be better to import timestamps as UTC to avoid any misinterpretation (this is done by including the time zone to the date format in the data import). If desired, timestamps may be converted into a different time zone using a script.

	~~For example, the~~ CSV file contains the following data:		Example 1: CSV file contains the following data:
	<pre>		<pre>
	2021-05-16 08:34:12		2021-05-16 08:34:12
	</pre>		</pre>

	When ~~the~~ value is imported to a datatable, ~~and a model is created for the data, this timestamp~~ is shown exactly as it was imported, i.g 16th of May 2021 at 8:34:12.		When this value is imported to a datatable using date format yyyy-MM-dd HH:mm:ss, it is shown everywhere exactly as it was imported, i.e. 16th of May 2021 at 8:34:12.

	~~As another example, the~~ CSV file contains the following data:		Eaxmple 2: CSV file contains the following data:
	<pre>		<pre>
	2021-05-16 08:34:12+02:00		2021-05-16 08:34:12+02:00
	</pre>		</pre>

	When ~~the~~ value is imported to a datatable using date format yyyy-MM-dd HH:mm:sszzz, ~~this timestamp~~ is ~~shown~~ as UTC ~~in the model.~~ i.e. 16th of May 2021 at 6:34:12. If the CSV file is imported without the time zone (i.e. ~~zzz~~), the time zone is ignored and this timestamp is ~~shown as in the model~~ as 16th of May 2021 at 8:34:12.		When this value is imported to a datatable using date format yyyy-MM-dd HH:mm:sszzz, it is imported as UTC, i.e. 16th of May 2021 at 6:34:12. If the CSV file is imported without the time zone in the date format (i.e. yyyy-MM-dd HH:mm:ss), the time zone is ignored and this timestamp is imported as 16th of May 2021 at 8:34:12.

Ollvihe at 00:06, 17 November 2021

2021-11-17T00:06:10Z

← Older revision		Revision as of 00:06, 17 November 2021
Line 5:		Line 5:
	When importing data with [[Importing_Data_to_Datatable_from_CSV_File\|CSV file import]], timestamps in CSV files may or may not have time zone information. If timestamps don't have the time zone, times are interpreted as such and they appear in the model exactly as imported. If the timestamps have the time zone information, timestamps are imported as UTC, to make timestamps with different time zones comparable with each other. It's also possible to import timestamps without the time zone in the date format ("zzz") which will ignore the time zone and import timestamps like they didn't contain the time zone information.		When importing data with [[Importing_Data_to_Datatable_from_CSV_File\|CSV file import]], timestamps in CSV files may or may not have time zone information. If timestamps don't have the time zone, times are interpreted as such and they appear in the model exactly as imported. If the timestamps have the time zone information, timestamps are imported as UTC, to make timestamps with different time zones comparable with each other. It's also possible to import timestamps without the time zone in the date format ("zzz") which will ignore the time zone and import timestamps like they didn't contain the time zone information.

	As a recommended practice, if all time information is in a specific local time, timestamps can be imported in that time zone to QPR ProcessAnalyzer models. If there are data where there events recorded in different time zones, it may be better to import timestamps as UTC to avoid any ~~misinterpretaion~~ (this is done by including the time zone to the imported timestamps).		As a recommended practice, if all time information is in a specific local time, timestamps can be imported in that time zone to QPR ProcessAnalyzer models. If there are data where there events recorded in different time zones, it may be better to import timestamps as UTC to avoid any misinterpretation (this is done by including the time zone to the imported timestamps).

			For example, the CSV file contains the following data:
			<pre>
			2021-05-16 08:34:12
			</pre>

			When the value is imported to a datatable, and a model is created for the data, this timestamp is shown exactly as it was imported, i.g 16th of May 2021 at 8:34:12.

			As another example, the CSV file contains the following data:
			<pre>
			2021-05-16 08:34:12+02:00
			</pre>

			When the value is imported to a datatable using date format yyyy-MM-dd HH:mm:sszzz, this timestamp is shown as UTC in the model. i.e. 16th of May 2021 at 6:34:12. If the CSV file is imported without the time zone (i.e. zzz), the time zone is ignored and this timestamp is shown as in the model as 16th of May 2021 at 8:34:12.

Ollvihe at 14:11, 16 November 2021

2021-11-16T14:11:58Z

← Older revision		Revision as of 14:11, 16 November 2021
Line 1:		Line 1:
	When importing data to QPR ProcessAnalyzer, date and time data in different local times may be encountered. It's important that the times are interpreted correctly, so that they are comparable and for example durations between timestamps are calculated correctly.		When importing data to QPR ProcessAnalyzer, date and time data in different local times may be encountered. It's important that the times are interpreted correctly, so that they are comparable and for example durations between timestamps are calculated correctly.

	QPR ProcessAnalyzer doesn't store the time zone differences separately, but instead uses times that have been imported to it.		QPR ProcessAnalyzer doesn't store the time zone differences separately, but instead uses times that have been imported to it. The models can thus contain timestamps from any time zones and it's just a matter of agreement, which time zones the timestamps are from.

	When importing data with [[Importing_Data_to_Datatable_from_CSV_File\|CSV file import]], timestamps in CSV files may or may not have time zone information. If timestamps don't have the time zone, times are interpreted as such and they appear in the model exactly as imported. If the timestamps have the time zone information, timestamps are imported as UTC, to make timestamps with different time zones comparable with each other. It's also possible to import timestamps without the time zone in the date format ("zzz") which will ignore the time zone and import timestamps like they didn't contain the time zone information.		When importing data with [[Importing_Data_to_Datatable_from_CSV_File\|CSV file import]], timestamps in CSV files may or may not have time zone information. If timestamps don't have the time zone, times are interpreted as such and they appear in the model exactly as imported. If the timestamps have the time zone information, timestamps are imported as UTC, to make timestamps with different time zones comparable with each other. It's also possible to import timestamps without the time zone in the date format ("zzz") which will ignore the time zone and import timestamps like they didn't contain the time zone information.

			As a recommended practice, if all time information is in a specific local time, timestamps can be imported in that time zone to QPR ProcessAnalyzer models. If there are data where there events recorded in different time zones, it may be better to import timestamps as UTC to avoid any misinterpretaion (this is done by including the time zone to the imported timestamps).

Ollvihe: Created page with "When importing data to QPR ProcessAnalyzer, date and time data in different local times may be encountered. It's important that the times are interpreted correctly, so that th..."

2021-11-16T14:07:05Z

Created page with "When importing data to QPR ProcessAnalyzer, date and time data in different local times may be encountered. It's important that the times are interpreted correctly, so that th..."

New page

When importing data to QPR ProcessAnalyzer, date and time data in different local times may be encountered. It's important that the times are interpreted correctly, so that they are comparable and for example durations between timestamps are calculated correctly.

QPR ProcessAnalyzer doesn't store the time zone differences separately, but instead uses times that have been imported to it.

When importing data with [[Importing_Data_to_Datatable_from_CSV_File|CSV file import]], timestamps in CSV files may or may not have time zone information. If timestamps don't have the time zone, times are interpreted as such and they appear in the model exactly as imported. If the timestamps have the time zone information, timestamps are imported as UTC, to make timestamps with different time zones comparable with each other. It's also possible to import timestamps without the time zone in the date format ("zzz") which will ignore the time zone and import timestamps like they didn't contain the time zone information.