But, if our example client is on a trip to Mexico or Japan, the hour that would appear would change as it’s taken from his computer or network.
Specifically, my question is whether there is a way to force this to be a specific time zone. After all, wherever the viewer is, the timezone refers to the project timeframe, not the local and altered one.
In the dashboards, the time zone is derived from the browser’s current time zone, and the browser derives its time zone from the operating system’s current time zone. The device likely detects geolocation and updates its time zone.
The current approach allows the end user to understand, relative to their time zone, the age of the data (whether it was captured 10 minutes or 10 hours ago). This operation is not intuitive between different time zones.
I understand that, at some point, a user may need to know the age of data relative to another time zone. What would I do? The quick fix is to set the end user’s device time zone to the local time zone where the data is being captured.