...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
The required incoming metadata record has three levels as modelled below, with metadata values being inherited as it is collected left to right:
...
Metadata Level 1 - Data Owner
Metadata Level 2 - Primary Survey/Mission/Voyage Record
Metadata Category | General | Citation | Survey | Technical |
Metadata Fields |
|
Optional underlined |
| Survey Profile
|
The minimum requirement for a survey geometry/shape is a bounding box, although it is recognised that this is not an effective definition for extensive or complex surveys. The preference is that additional shapes are also provided as shapefiles or in Well Known Text (WKT) formats. These could include a line shape for Ship Tracks, a polygon definition for a bathymetry swath, a polygon boundary that encompasses a gridded product generated from the data.
...
Level 3 Metadata - Data Product Metadata
Metadata Category | General | Citation | Survey | Technical |
The following fields will be inherited from the Survey metadata above unless they require modification Green inherited by default; Will be copied from the Survey if left blank; Unique to this record | ||||
Metadata Fields |
|
Optional underlined |
| Dataset/Product Profile
|
Downloadable Excel worksheet template.
...
Category | Definition | Fields | Specific Field Definitions | Example Data |
General | Basic information about the data package being submitted. | Survey title (full) | A short phrase or sentence describing the dataset. In many discovery systems, the title will be displayed in the results list from a search, and therefore should be human readable and reasonable to display in a list of such names. | MH370 Phase 1 150m Bathymetry datasets |
Survey ID | The ID assigned to the survey, relevant especially when an ID may be how the survey is more widely referenced. | GA-4421, SONJN05MV, IN2020_V01 | ||
Abstract | A paragraph describing the dataset, analogous to an abstract for a paper. | On behalf of Australia, the Australian Transport Safety Bureau (ATSB) is leading search operations for missing Malaysian airlines flight MH370 in the Southern Indian Ocean. Geoscience Australia provided advice, expertise and support to the ATSB to facilitate bathymetric surveys … [for full abstract visit http://pid.geoscience.gov.au/dataset/100315 ] | ||
Lineage | Information about the events or source data used in constructing the data specified by the scope or lack of knowledge about lineage. | “link-to-lineage-statement” OR | ||
| Full text: | |||
Lineage can be complex to record, so can be actively linked within a metadata record either to a file within the dataset being submitted or to a hosted location where the lineage statement may be found. If neither of these options are preferred, a full narrative may also be provided. | “The MH370 Search bathymetry Surveys, GA-4421 GP1483 was acquired by the Australian Government through ATSB/GA on-board the MV Fugro Equator from the 05th of June to the 30th of July 2016, GA-4422 through the Chinese Navy Vessel Zhu Kezhen 872 from the 3rd June to 31 August 2014 and from the 5th January to the 30 April 2015 for the MV Fugro Supporter………” | |||
Data Collected | Types of Data Collected during the Survey. This may be a list of data types/collections for which one or more subsequent metadata records may be required. | Bathymetry, Backscatter, Imagery, Samples, Magnetics, Seismic etc | ||
Contact for the Data | Information that is related to contacts for the data | Data Owner | The person and/or organisation that owns the submitted data for the purpose of empowering The Commonwealth of Australia (Geoscience Australia) representing the AusSeabed community to act as a custodian. | Deakin University |
Custodian | The person and/or organisation that accepts, archives and disseminates the data | Commonwealth of Australia | ||
Point of Contact | The person and/or contact details for initiating contact regarding the data. This may be the Principal Investigator or Chief Scientist | Commonwealth of Australia (Geoscience Australia) | ||
[Principal Investigator/[Full Name] (xyz@ga.gov.au) | ||||
Cnr Jerrabomberra Ave and Hindmarsh Dr GPO Box 378, Canberra, ACT, 2601, Australia | ||||
Call 1800 800 173, 02 6249 9960 | ||||
Collecting Entity | The organisation that was responsible for collecting the data being described. | Australian Transport Safety Bureau (ATSB) | ||
Citation | Information that is collected to ensure appropriate credit is assigned for the data being provided, and ensuring the data’s intended use of the data is clear. | Attribution Citation | Statement of attribution that must be included whenever the data being provided is distributed/redistributed or used by another organisation. | 2017. MH370 Phase 1 150m Bathymetry datasets (GA-4421, GA-4422 & GA-4430). Geoscience Australia, Canberra. http://pid.geoscience.gov.au/dataset/100315 DOI://… |
Legal Constraints | Restrictions and legal prerequisites for accessing and using the resource or metadata | Creative Commons Attribution 4.0 International Licence | ||
Access Constraints | Details of any constraints that are not determined under the licence constraints regarding the access to the information being provided. Access constraints are applied to assure the protection of privacy or intellectual property, and any | As per licence | ||
special restrictions or limitations on obtaining the resource or metadata | ||||
Use Constraints | Details of any constraints that are not determined under the licence constraints regarding the use of the information being provided. | As per licence | ||
Country (of data ownership) | Country of the owner of the data. | Australia | ||
Survey Details | This information defines the Departure and Arrival details for the Survey | Start Location | The location, departure point or Port the survey started from; or The start location of a particular data collection process | Perth |
End Location | The location, arrival point or Port the survey ended at; or The end location of a particular data collection process | Perth | ||
Start Date Time | The Survey Start date (and time); or The start datetime of a particular data collection process | Dec 31 2020 OR [20201221T13:45:30] | ||
End Date Time | The Survey End data (and time); or The end datetime of a particular data collection process | Jan 6 2021 OR [ 2021-0106T15:30:30] | ||
Survey Positioning Data | The information provided in the positioning data provides for both an overview of the survey’s coverage, and the primary coordination reference system that was used to collect/prepare the survey data. | Survey area (general) | Plain English description of the location of the survey. | Indian ocean approximately 1100nm off the coast of Perth Australia. |
Sea Areas | One or more defined Ocean, Sea or Water body names as defined | Indian Ocean, Southern Ocean | ||
Survey bounding box coordinates | The detailed coordinates of the survey. This may be provided in a variety of formats, however full positioning information is required. |
78.00, -42.00, 116.00, -12.00 | ||
| ||||
Coordinate reference system - Bounding Box | The coordinate reference system used to define the survey bounding box. |
| ||
Coordinate reference system - Survey Data | The coordinate reference system used for data collection. | "WGS 84 Geographic (EPSG:4326)"' | ||
Reference System | The finer details of the reference system used for data collection. | Horizontal Datum | The horizontal reference datum for data collection | WGS84 or GDA2020 |
Vertical Datum | The vertical reference datum for data collection | MSL or EGM2008 | ||
|
| Coordinate Epoch | Date range during which the coordinates were captured. This is used for defining the dynamic datum. This can be derived by re-using the Survey Start and End DateTimes. | Dec 31 2020 to Jan 6 2021 OR [20201221T13:45:30 – 2021-0106T15:30:30] |
Survey Configuration | The configuration of the survey as it ran. | Platform type | The platform hosting the instruments and sensors used to collect the data. | Ship, AUV |
Platform Name | The name of the platform used to collect submitted data | RV Investigator | ||
Instrument type | The type of instrument used to capture the data. Suggested values are: | Multi-beam Echosounder | ||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
Sensor type | The type of sensor used to collect the data being provided. Should include Brand eg Kongsberg and Model EM2040 | Kongsberg EM2040 | ||
Sensor parameter | The parameter or function as defined or measured by the specific Sensor type. | e.g Frequency at which the survey was conducted. | ||
Sensor value | The defined or measured value assigned to the Sensor. This may be a single value or a range | 200-400 | ||
Sensor UOM | The Unit of Measure associated with the value for the specific sensor type | kHz |
...