How to read CSV files (missing versus zero)
As the discussion has rolled out I am sure we can all agree that "Missing data and zero are two totally different things and should never be interchanged. "
Obviously I never intended to have a meaning other than stated with the sentence above. The problem which arose is however that when creating comma separated files it turns out that the contents of the files varies a lot depending on which system is creating the data files.
Therefore I asked :
In other words the question is how to read ",.," should it be: Option 1: as 0.0 (which is current behaviour) or Option 2: .
My worry was that around the world in some places some systems export a zero as ",.," whereas in other areas as ",,"
From the messages added by users I decided to implement the latter option.
That is in one of the next builds you will see that:
Any content of a comma separated file will be imported as : missing if the content of the csv file is: ,., or ,, for a given field.
A similar question is related to reading of "empty" boolean fields. E.g. access exports these as "FALSE" or "NO", not as "no value".
There is only one cure to this type of problem: The software should not be given control of standards. The standard should be settled by the user or the user community.
Regards
Jens Lauritsen. EpiData Association
I'm a novice epidata user and am calculating elapsed time for a procedure (never more than a few hours) which can cross midnight. This is implicit if the ending time is less than the starttime. Can anyone suggest how modify the code below to add a day when the endtime is after midnight? Thanks! --Dale
BEFORE FILE DEFINE varStartTime ########.##### DEFINE varEndTIME ########.##### END
STARTTIM RANGE 0 23.59 END
ENDTIME RANGE 0 23.59 AFTER ENTRY varStartTime=STARTDAT+TIME2NUM(STARTTIM) varEndTime=STARTDAT+TIME2NUM(ENDTIME) HOURSMIN=NUM2TIME(varEndTime-varStartTime) END
HOURSMIN NOENTER END
epidata-list@lists.umanitoba.ca wrote:
As the discussion has rolled out I am sure we can all agree that "Missing data and zero are two totally different things and should never be interchanged. "
Obviously I never intended to have a meaning other than stated with the sentence above. The problem which arose is however that when creating comma separated files it turns out that the contents of the files varies a lot depending on which system is creating the data files.
Therefore I asked :
In other words the question is how to read ",.," should it be: Option 1: as 0.0 (which is current behaviour) or Option 2: .
My worry was that around the world in some places some systems export a zero as ",.," whereas in other areas as ",,"
From the messages added by users I decided to implement the latter option.
That is in one of the next builds you will see that:
Any content of a comma separated file will be imported as : missing if the content of the csv file is: ,., or ,, for a given field.
A similar question is related to reading of "empty" boolean fields. E.g. access exports these as "FALSE" or "NO", not as "no value".
There is only one cure to this type of problem: The software should not be given control of standards. The standard should be settled by the user or the user community.
Regards
Jens Lauritsen. EpiData Association
EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
participants (1)
-
epidata-list＠lists.umanitoba.ca