[Kst] [Bug 243684] Handling of formatted timestamps as a valid field in input files

[netterfield at astro.utoronto.ca]

https://bugs.kde.org/show_bug.cgi?id=243684


netterfield at astro.utoronto.ca changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |netterfield at astro.utoronto.
                   |                            |ca




--- Comment #3 from  <netterfield astro utoronto ca>  2011-12-05 13:50:37 ---
-the data source should return time in double precision, like all other
vectors.  The plots know how to interpret double precision ctime-epoch seconds,
and double precision Julian Day.
-The user should be able to chose between seconds since the start of 1970
('ctime') or Julian Day.  If the date is before 1970, only Julian Day should be
accepted.
-A double precision 'ctime' epoch time has ~1 microsecond precision.  Julian
day  is more like a ms.
-Date and Time in separate columns should be merged into a single vector.  I
can't see a use case to keep them separate.
-There are lots of time formats!  We need a way to detect/select them.
ISO_8601 should be easily detectable.  Many others, however, are not.  We could
use some heuristics to guess defaults (eg, MM <= 12, or dd <= 31, etc), in
order to set defaults, and disable some options, but it isn't going to be easy
to be accurate in general.

for ISO 8601, see 

http://en.wikipedia.org/wiki/ISO_8601 

In Canada, we have absorbed many different time 'standards' so I am
particularly sensitive to this mess.

http://en.wikipedia.org/wiki/Date_and_time_notation_in_Canada

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.