aggregation of Qualityflag

at the moment, the qualityflag generation for the aggregated data is useless, 
as it only repeats the first entry it finds for all other aggregation steps.

If I understand the Qualityflag calculation implementation correctly, then for 
each quality check a certain amount is added to the initial Qualityflag-level 
(even if the test was passed).

If this is the case, and also assuming that the amount that is added to the 
qualityflag is higher when a certain test is failed, then I would suggest the 
best thing to do is to take the maximum Qualityflag from any of the entries, so 
that one knows that for at least one entry of the aggregated data points a 
certain set of tests has been run and (assuming that all possible entries in 
Qualityflag are unique) that there potentially was a problem with at least one 
observation.

Is this a sensible approach or am I missing something?

Original issue reported on code.google.com by tim.appe...@gmail.com on 3 Jun 2012 at 9:32

environmentalinformatics-marburg / julendat

aggregation of Qualityflag #6