My only solution has been to try to remember to change the time zone in my account settings before uploading a batch from a different time zone. Then to remember to set it back afterward. Certainly not ideal, but it does the job (if I remember).
There has been some thinking around trying to automatically set the time zone based on the geographic coordinates of each observation. But this will still fail if:
- the observer forgets to change the time on their device(s) to the local time (that’s me!), and/or
- the observer’s coordinates are imprecise enough (have a large enough “accuracy” circle) that they overlap more than one time zone
- the observation is initially saved without coordinates