Aggregration

Tasks that SEACOOS aggregration process needs to perform to collect all partner QC info and perform further QC tests (e.g. nearest neighbor and model comparison) and flagging

• Scout needs to handle new attributes in CDL v3.0
• Scout needs to retreive qc_flag data and QC attributes from netCDF files and place into database tables
• What does scout do about non-existent (not in file) qc_flags?
• Database tables need to be modified to receive qc_flag data and attributes
• Define fields and algorithms to perform nearest neighbor check on recently inserted aggregrated data. This includes updating the database schema for required tables or atttributes for this QC check and timing the check to run after all lastest data have been added.
• Scout needs to address two possible vector uses in latest data. There are two ways to describe horizontal wind vectors, either using wind speed and direction or wind u- and v-components. What does scout look for in a file when looking for wind data? one type or the other or both? If just one, scout will need to be modified to handle one or the other.
• Does scout handle profiler data yet? (category = 'fixed-profiler' or 'moving-profiler') We will need this for ADCP data.
• Develop mechanism to update previously unavailable data as availabe or bad flagged data as good (not needed for the v3 test implementation)
• Ground work to consider Event Triggered test at RCOOS or partner level (not needed for the v3 test implementation)
• Ground work for performance monitoring by station, by provider, by whatever (not needed for the v3 test implementation)