Re: [gdal-dev] Time in GDAL

2017-10-16 Thread Dmitry Baryshnikov
Hi, For some imagery metadata the Acquisition date and time is the center of scene (end timestamp minus start). Also for one-shot camera there is only the one moment there the imagery was captured. I believe that this 3 parameters (SATELLITEID, CLOUDCOVER, ACQUISITIONDATETIME) are common for

Re: [gdal-dev] Time in GDAL

2017-10-15 Thread Luke
Just a comment from an end user: perhaps ACQUISITIONDATETIME could store start and end times using ISO 8601 intervals (forward slash separator) - start date time/end date time Luke -- Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html

Re: [gdal-dev] Time in GDAL

2017-10-15 Thread Even Rouault
Hi Edzer, > Currently, parsing this from the metadata strings is > possible but messy and ad hoc, error prone, and has to be done by each > client for every driver. Agreed that metadata handling can be messy and is a bit in freestyle mode between drivers. In GDAL 2.0, Dmitry introduced metadata

[gdal-dev] Time in GDAL

2017-10-15 Thread Edzer Pebesma
Hi, last week the openEO project [1] started, in which we aim to develop an interface (api) to cloud-based processing of Earth observation (EO) imagery. For this project, GDAL has been the blueprint in terms of successfully integrating the diverse landscape of file formats [2]. The project allocat