On Dienstag, 20. Jänner 2026 00:22:53 Mitteleuropäische Normalzeit Michael 
Keller wrote:
> Tēnā koutou katoa.
> 
> On Mon, 19 Jan 2026 at 02:35, Berthold Stoeger <[email protected]>
> 
> wrote:
> > Please observe that I am _not_ talking about full timezone or DST
> > information.
> > I am talking about the offset between local time and GMT/UTC at the start
> > of
> > the dive. This datum is well defined and stable, albeit potentially
> > unknown on
> > import.
> 
> Ok. How do you imagine this being set, and what do you think it should be
> used for?
> Also, should this offset be in minutes, or do we need seconds?

For example my old dive computer reported this value. Otherwise I would say 
it's a UI issue. One could default to local time offset or to "unknown". Also, 
the user should be able to edit this value, obviously.

Storing it in second is probably best, as the local time field also has 
seconds granularity.

The information should be used to calculate N2 loading between dives, wasn't 
that the point?

I just noted that this might have to be implemented in the planner, where you 
can set the date.

> > should throw an error.
> 
> Agreed, as long as 'one dive computer has an offset set, the others have
> 'don't know'' is not considered a conflict - I suspect this will cover most
> of the cases where this is relevant.
> Also not sure if 'throw an error' is user friendly - I'd go for allowing
> the diver to select what the correct offset is.
> 
> > I would suggest placing full timezone/DST information, as provided by the
> > divecomputer, in extra_data.
> 
> If we have it - from looking at Garmin's format, best we can do is probably
> an offset to UTC. And placing this into Extra Info and then using it to
> feed into the offset on the dive is not the cleanest way to do this.

If we have an offset to UTC, then of course we should use that directly. I was 
thinking about extended "this country with active DST" kind of information 
that should go into extra_data.

Berthold

_______________________________________________
subsurface mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to