null

Skip to end of banner
Go to start of banner

Completeness (Assessment)

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Definition

Completeness relates to the degree the data collected is as intended and complies with minimum requirements as per ASB standards. The Completeness Assessment is a cursory examination of data acquired or submitted to detect any obvious data gaps. This applies to the presence of required attributes, metadata, and acquisition reports detailing survey scope and any information relevant to the collection and supply of the dataset.  This check consists of two elements: Commission (excess or duplication) and omission (missing files/data). 

Checks

  1. Missing files, as apart from the subsequent Logical Consistency Assessment, are noted on a cursory check of supplied data (verify files are present). 

  2. Date of data reception is recorded. 

  3. Is the data published and available elsewhere? 

  4. Survey priority in the context of the Publication Schedule has been assigned. 

  5. Metadata including additional ancillary data is supplied as per outline of data submission. Storage on the Clearing House NAS has been allocated. 

Pass Requirements

External/internal dataset review. Data is identified as from a ‘Registered Contributing Partner’ or otherwise noted. Data submission retains a logical consistency to expectations (files appear consistent with initial data submission documents): 

  • L0 data – have initial QAX QA/QC checks been completed? 

  • L2 data – initial QAX report included with data? 

  • L3 data – minimum requirement of three band GeoTIFF (density, uncertainty, depth) - horizontal datum cannot be Mercator projection. 

Examples

 1. Pass example

Description  

Deakin University post-processed dataset. Handover dataset package includes three band GeoTIFF (or QAX QA/QC pass/fail check as per ASB standards). Also includes necessary metadata documentation for eCat record lineage and publication to the AusSeabed Portal. 

Test results  

What elements were there or not: 

  • If L3 has a CSAR or GeoTIFF been supplied? 

Pass 

Yes 

Explanation  

Passes are recorded in the ASB Survey checklist. Exceptions can be made for L3 datasets in the case where missing data is non-critical to publication (to be deliberated by the team and contributing hub). These are recorded in the checklist procedure. 

 2. Example 2

Description  

Australian Antarctic datasets are newly implemented for processing/publication. RSV Nuyina maiden voyage raw dataset was processed and the procedure documented. 

Test results  

What elements were there or not: 

  • If L0 product was the full complement of required data included (i.e. raw data, vessel configuration, SVP, Tide files, POSMV, TPU/CUBE related information, metadata, documentations/reports)? 

  • If L2 GSF were GSF files included? 

  • If L3 has a CSAR or GeoTIFF been supplied? 

Pass 

Under Revision 

Explanation  

Passes are recorded in the ASB Survey checklist. L0 raw datasets must meet minimum metadata/file requirements as per ASB standards.  

 3. Example 3

Description  

Australian Hydrographic Office HIPP datasets are a special case where specific datums/metadata lineage requirements are used. 

Test results  

What elements were there or not: 

  • L3 data at 30 m resolution supplied as a GeoTIFF 

  • Metadata relevant for lineage reporting as agreed between AHO and ASB. 

Pass 

Under Revision 

Explanation  

Passes are recorded in the ASB Survey checklist. L0 raw datasets must meet minimum metadata/file requirements as per ASB standards. 

  • No labels