1. Bob: The reason I'd like to have the option of timezones is that modern timestrings like ISO8601 often have them, so using Z to indicate UTC (which is indeed the majority of our timestamps) would both handle the common case and allow the possibility of using other timezones.
2. Kemp: It's not just for Google, but I don't know how broadly this would be used. AFAIK, the immediately adjacent community of people using big data and remote sensing have not settled on any standard yet, but it seems like the right time to establish one. 3. Even: yes, I'm not quite sure whether this should be handled on GDAL or TIFF level. Other GDAL-readable format like netcdf-cf have time standards already, but yes, geotiffs (and lately COGs = cloud-optimized geotiffs <https://www.cogeo.org/>) are the lingua franca of our community. Setting GDAL fields START_DATE and END_DATE indeed feels like a good solution, so I wanted to find out how to do this properly in the hope of creating a standard. On Thu, May 12, 2022 at 12:46 PM Bob Friesenhahn < [email protected]> wrote: > On Thu, 12 May 2022, Simon (Vsevolod) Ilyushchenko wrote: > > > >> > >> Can you assume DateTime is UTC with your particular files and use cases? > >> > > > > Yes, this is a good fallback option. > > I am not sure about established precedence, but this is much better > than being a mere fallback option as long as the recipient knows it is > UTC. This could be handled via documentation. > > Dealing with time zones is hard, and it assumes that both the writer > and the reader have knowledge of the current time zone, and access to > the time zone database necessary to do conversions. > > It may still be necessary for the writer and reader do to something > special to produce and consume UTC timestamps. > > Unix type systems (and those using NTP) have a system clock which is > on UTC time. > > Bob > -- > Bob Friesenhahn > [email protected], http://www.simplesystems.org/users/bfriesen/ > GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ > Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt >
_______________________________________________ Tiff mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/tiff
