@mjacqu After having integrated more data with explicit measurement times, I would suggest that we replace the boolean column profile.utc with numeric column profile.utc_offset (hours) to report the offset to UTC (e.g. 0 if already UTC) if known. This would allow the reported hours to be used directly – no conversion required on our part and a clearer correspondence between the source and glenglat. Conversion to UTC by the user is simply a matter of adding hours to a datetime. And local (or local solar) time is anyway probably more meaningful for temperature measurements than UTC time.
@mjacqu After having integrated more data with explicit measurement times, I would suggest that we replace the boolean column
profile.utcwith numeric columnprofile.utc_offset(hours) to report the offset to UTC (e.g. 0 if already UTC) if known. This would allow the reported hours to be used directly – no conversion required on our part and a clearer correspondence between the source and glenglat. Conversion to UTC by the user is simply a matter of adding hours to a datetime. And local (or local solar) time is anyway probably more meaningful for temperature measurements than UTC time.