Details Ticket 804


Comment | Reply | Open


Serial Number 804
Subject r.in.gdal: writing map timestamp (wish)
Area wish
Queue grass
Requestors neteler@itc.it
Owner fwarmerdam
Status resolved
Last User Contact Never contacted
Current Priority 30
Final Priority 70
Due No date assigned
Last Action Thu Sep 20 14:47:30 2001 (7 yr ago)
Created Thu Sep 20 12:22:12 2001 (7 yr ago)

Transaction History Ticket 804


Thu, Sep 20 2001 12:22:12    Request created by guest  
Subject: r.in.gdal: writing map timestamp (wish)

grass downloaded at: CVS Server, Germany
grass sources source: yes, I am using the latest GRASS from CVS

Hi again,

a wish for r.in.gdal: It would be great if the map timestamp
would be written (see r.timestamp for coding).

There is a real need to keep the timestamp for maps, especially
in terms of multitemporal analysis. Since GRASS already provides
the DateTime library, we should use this feature for as much
modules as possible. However, it starts with the data import.

At least remote sensing image formats usually contain the
timestamp which is already extracted by the GDAL lib.

Thank in advance,

 Markus
Thu, Sep 20 2001 14:45:15    Taken by fwarmerdam  
Thu, Sep 20 2001 14:47:30    Status changed to resolved by fwarmerdam  
Thu, Sep 20 2001 14:47:30    Comments added by fwarmerdam  
Markus, 

I assume you wish that the original acquisition date of the scene would
be preserved, is that right?  

Currently there is no standardized way this is handled in GDAL.  It happens
to be captured in the metadata of some formats, such as CEOS, but not
in an organized way that an application could check for without having alot
of format specific rules. 

I will take your suggestion under consideration for GDAL. Let me know if I
have missed your point. 
Comment | Reply | Open

You are currently authenticated as guest.
[Show Configuration] [Login as another user]

Users Guide - Mail Commands - Homepage of RequestTracker 1.0.7 - list any request