Managing Time Zones and Local Time: Difference between revisions
(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...") |
No edit summary |
||
| 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). | |||
Revision as of 14:11, 16 November 2021
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. 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 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).