GA Contributing Hub Incoming Data Policies

The data hub is being developed as a multi-component suite of services that are underpinned by a federated data storage model, with each connected data store being referred to as a “contributing hub”. At the time of writing, there are two contributing hubs under development, one at GA and one at CSIRO. Outlined below are the incoming data policies for the GA Contributing Hub.

Data Acceptance Policies

The following are the principles for data being accepted into The GA contributing Hub:

1. Data must be owned by GA (GA is the lead organisation of the survey) or GA must be a partner/collaborator in its acquisition, or

2. If GA has not held an interest in the acquisition or preparation of the data, teh GA Contributing Hub will accept the data if the data is not readily available through another publically accessible channel. 

3. Data can only be submitted by an agreed Contributing Data partner. The basis for becoming a contributing data partner can be found in the becoming a contributing partner document. 

4. Data must be provided in the prescribed formats outlined in appendix 1. 

5. Data must be submitted along with contributing organisation profile, providing GA with the right to store, distribute and process the data for its own outputs.  

   1. Authority to publish does not negate the need for GA to provide appropriate citation to the data.

   2. The contributing organisation is aware that the visualisation of the data may not be identical to what is supplied from them (e.g. the publishing pipeline standardizes visualisation output of any survey data, ensuring that hillshades and standard colour ramps are applied to the data).

6. Data is supplied with appropriate metadata and conforms to the standard template that will be supplied to the contributing organisation.

7. In order for data to be processed to a AusSeabed consistent output, data should be provided in one of the identified incoming formats outlined in the AusSeabed Guidelines ver 2.0 or should be easily converted to align with these formats. Specifically:

   1. All incoming data should include any auxiliary data required to meet the AusSeabed Guidelines. 

   2. All incoming data should include all relevant metadata outlined in the guidelines.

Incoming Channels (future state)

Two incoming data submission channels will be supported into the future:

1. The provision of a physical hard drive that will then be registered into The Hub’s infrastructure. This option will:

   1. Provide an ongoing service that reflects the way data has always been provided by surveyors. This will allow for a gradual education process, as well as a maturation of the tools and management practices within AusSeabed to evolve as data managers into the future. 

   2. Support the provision of historical archives which is expected to be a significant source of previously unpublished bathymetry data in the first couple of years of operation. 

2. The registration of an external data provider into The Hub’s infrastructure for direct submission. This option will:

   1. Begin to service more technical users who would like to partner with GA to provide the data during, or immediately after survey for rapid visualisation and access. 

   2. Allow for rapid connection between the various components of the datahub and therefore support a “Real time” narrative of the survey’s progress. 

Data Levels

Standard definitions of data levels are necessary to inform how data has been processed and to ensure consistently and limit ambiguity when discussing, delivering or describing data. The following definitions are modelled on those defined by NASA for Earth Observations data products.

Data Versions

Versioning of bathymetry data is classified as V0 and V1 and directly refers to the vertical datum that the data is published as, as well as the state of the data.

Version 0

V0 (Version 0) bathymetry data is published at geodetic vertical datums (e.g. Mean Sea Level (MSL)) and is mainly refers to data that has been manually cleaned, and distributed for release.

Rough Notes

At the time of writing there is a considerable “backlog” of data that has been cleaned for delivery in response to a client request but has either:

1. Been distributed through GA’s public facing tools as a bespoke deliverable (either for an individual survey, or as part of a compilation), or

2. Has never been distributed at all. 

In both of these instances, the data represents a product of value, albeit limited in that the processing that has been undertaken to date has not been explicitly captured. It is with this data in mind that the GA-ASB data hub is defining a “version 0” for this backlog data. 

• Important to note – “version 0” is not relevant to any new, incoming data, or data that has never been cleaned or is only partially cleaned previously. Version 0 represents a “quick win” and will be replaced at a later date. 

Version 1

V1 (Version 1) is classified as bathymetry data that may have been manually cleaned, surface cleaned, and exported to two vertical datums, Ellipsoid and MSL. This version will be used for all new surveys.

Rough Notes

Version 1 represents the first, truly consistent processing outcome for the GA ASB Data Hub data. Any data within the existing backlog that has not been produced as a V0 will be produced as a V1, via a prioritised publication schedule that takes into account both backlog and new incoming data. 

Version 1 will be:

1. Created using an automated, reproducible processing pipeline