@ngalbraith I think we added the 'both automated and manual' clause to account for the case in Jessica's example in the above [comment](https://github.com/cf-convention/cf-conventions/issues/216#issuecomment-581714109), where there's a test with the generic `quality_flag` name that is manually performed with its own flagging scheme that is combined with the `gross_range_test_quality_flag` automated test which follows a different flagging scheme.
I think it also generally conveys the point that an aggregate flag is the one that a data user should query if they want to obtain the best data as @roy-lowry mentioned, however it was determined to be so - which also goes to your point [above](https://github.com/cf-convention/cf-conventions/issues/216#issuecomment-580802399) about how 'letting those systems document their own method of setting the value of the aggregate is important'. We were trying to add some flexibility in the definition. I think we've come to agreement, however, so I don't want to sidetrack, hoping this helps explain that particular phrasing and why we chose to include it. @japamment can we close the book on this addition when you are able to revisit it again, I suppose after the three week holding period? Many thanks for everyone's input on this. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/216#issuecomment-582640328 This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
