These guidelines should be followed when submitting data to the BGS MEDIN DAC for Geology, Geophysics and Backscatter. If you hold geological/geophysical data sets and are happy for these to be stored for the long-term and distributed by the DAC for future reuse please contact us at firstname.lastname@example.org.
Submission of Geology, Geophysics and Backscatter data
- The first stage is to provide an inventory of the data being offered for archiving. We will assess the contents and, if necessary, enter into discussion to clarify the information in it.
- Depending on the volume, type, and quality of the data, BGS may quote a cost for archiving the data.
- Generally data should be supplied as distinct survey datasets. Each should have a unique name/ID.
- If it’s not possible to submit full data holdings, metadata and data extents may be provided, so that your data are at least discoverable.
- BGS primarily accepts digital data only. Paper records will only be accepted where they contain unique, valuable information.
- Any data which is of geological interest may be submitted. If there are any biological, oceanographic or bathymetric components to the survey, we can forward data to other MEDIN DACs, or these can be submitted separately to the other DACs. More Information on submitting data to the other DACs.
Bathymetric data should be sent to the Bathymetry DAC operated by UKHO. Where bathymetric data received by the bathymetry DAC data contains a backscatter component, they will pass these data to us. Where possible the data should include processed backscatter data. If bathymetry/backscatter data is part of a wider seabed survey data set it may also be included in the submission to BGS.
Photo/video should be sent to the biological DAC operated by DASSH. If photo/video data is part of a wider seabed survey data set it may be included in the submission to BGS and we can forward to DASSH.
Renewables data should be submitted to The Crown Estate, Marine Data Exchange. Refer to the Crown Estate data requirements. You don't need to submit the data to the MEDIN DAC if you are already providing it to The Crown Estate. The data should be MEDIN compliant and will be archived with the DACs in the future.
Other (non-renewables) data (e.g. small works) which does not need to be submitted to The Crown Estate should be submitted directly to the DAC.
Oil and Gas
Oil and Gas data relating to exploration should be submitted to Oil & Gas UK/CDA. Metadata for Site Surveys should be submitted to the DAC and will be published on the MEDIN portal though we don’t hold the data.
Physical material such as core and grab samples can be accepted at the National Geological Repository.
Terms & Conditions
Data ownership and any terms and conditions should be clearly specified.
- The data owner retains the copyright of the original data and gives BGS permission to hold a copy and to distribute.
- Data will be made available under an Open Government Licence (OGL) whereby it can be used for any purpose without restriction, unless this has not been agreed with the data owner.
- The data owner is still required to be acknowledged under this licence, to ensure due credit is given.
- If you do not want your data to be released under these conditions please make this clear and specify any terms and conditions.
- Provide a brief statement to accompany data if required.
- Data may be supplied with an embargo date to allow future release.
MEDIN Discovery Metadata
Discovery metadata is information about your dataset that allows someone else to quickly understand where and when your dataset was collected and what type of data is available. The MEDIN Metadata Discovery Standard is compliant with other international conventions (INSPIRE, ISO19115) and is a 'marine profile' of the GEMINI2 standard. The metadata can be searched via the MEDIN portal which provides users with a single point of access to marine data for the UK.
- A MEDIN discovery metadata XML file should be generated for each dataset. MEDIN provides some metadata tools for this.
- Who creates the MEDIN discovery metadata (data provider or DAC) is dependant on the organisation. If the data provider has the capability to create MEDIN XML they may provide these directly to MEDIN. If this is not possible we can create on your behalf using information provided and forward for inclusion in the MEDIN portal.
- The data set title should be brief and precise and follow the format - Date, Organisation/Programme, Location, Type of survey.
- The abstract should be a clear and brief statement of what the dataset contains.
- Series metadata for the overall project/programme which the survey/data set is part of may also be supplied.
Controlled vocabularies are lists that can be used to describe datasets in a consistent way. MEDIN uses them both in the Discovery Metadata standard and the Data Guidelines. More information.
MEDIN Data Guidelines
MEDIN data guidelines are data archive standards specific to each data type which provide guidance on what information should be stored alongside your data to ensure others can use your data with confidence.
- The guidelines should be used to ensure that your data are MEDIN compliant
- Make it easier to ingest data into the DAC and to facilitate easy use and reuse of the data (collect once - use many times).
- Excel templates are provided if required.
- The relevant seabed survey guidelines which include bathymetry, sidescan sonar, seismic and sediment characteristics should be referred to for your data types.
MEDIN Compliant Data
There are 3 requirements to ensure that your data are MEDIN compliant:
- You supply General Metadata about your data
- You supply Detailed Metadata about your data – This may be included in a survey/cruise report or as additional metadata in spreadsheet
- Your data are in a format that the DAC accepts
- A cruise report should be submitted for each survey.This may contain the required detailed metadata.
- Spreadsheets of detailed metadata should be provided if possible – see MEDIN guideline for details.
- Details of instrumentation, software, processing, methods, formats, etc. should be included.
- Any other useful documents such as acquisition/processing/quality control reports/logs may be supplied where appropriate.
- Quality information/assessment of data and any problems with the data should be included.
- The coordinate reference system used should be clearly specified.
- Date and time should be provided in UTC or clearly specified local time zone.
General data guidance
- Standard data exchange formats should be used - see MEDIN guidelines for specific examples.
- Both raw and processed data may be submitted, provided clearly specified and useful.
- Data should be fully quality controlled by the data originator/provider before submission.
- Please ensure that the data is in its final form.
- Don’t include duplicate, draft, spurious files, empty folders within your submission.
- If your data is not in a format mentioned in the guidelines, please contact us.
- It is useful to provide GIS/shape files of survey extent polygons, multibeam polygons, geophysical lines, sample points. There is also a MEDIN GIS tool for creating metadata from ArcGIS layers.
- The BGS Survey Data Management Handbook may also be referred to.
Folder Structure/Data Organisation/File naming
As a seabed survey dataset may contain a range of various data types/formats/products it is important that data is well organised.
- Data should be organised in a well-defined documented folder structure such as the BGS Folder Structure, in a separate folder for each survey data set (named with the survey ID). There may be exceptions to this such as for a single data type/standalone dataset.
- Equipment types should be clearly specified.
- A summary checklist of data with numbers of each data type should be provided to give an overview of the submission.
- File naming conventions and consistency is important and documentation should match the filenames. Descriptive filenames may help explain the contents of files. Non-descriptive filenames should be adequately described.
- Individual filenames should be unique within a data set.
- A full listing of the data files can be included in the top level folder for each survey containing filenames, size, software package, short description.
- Standard data exchange formats should be used and clearly specified. e.g. segy/tif format for seismic data. See specific MEDIN data guideline for more information (e.g. seismic, sidecan sonar, bathymetry).
- Both raw and processed data may be accepted provided clearly specified, adequately described and formats are potentially useful.
- Formats which are outdated and not useful should not be submitted (e.g. sidescan sonar AGDS data).
- Other formats can be considered on a case by case basis – contact the DAC to discuss.
- Processed data should be corrected and have laybacks applied.
- Each line should have a distinct name/ID which should match filenames.
- Ensure navigation data is available for each line and make clear whether this is ship’s central reference navigation or corrected.
- GIS shape files of line location can be provided. Fix point positions will enable us to publish the locations through the Offshore Geoindex view service.
- Coordinate reference system used should be clearly specified (e.g. include in names of shape files).
- If any lines are missing, the reason why should be specified.
Seabed Sample Data
- Seabed sample data may be provided in spreadsheet or Access (e.g. Marine Recorder). See the data guideline for more details (e.g. Sediment and Rock Characteristics, Sediment Sampling by grab or core)
- Each core/grab should have distinct ID which should match filenames/data.
- Column heading/units should be clear.
- GIS shape files of point locations may be provided.
- Data will be incorporated into the BGS database system and made visible via the Offshore Geoindex view service. Work is ongoing on extend this to a download service.
- Alternatively data can be archived as received but might not then be available through view/download services.
- Currently access to data is by request email@example.com.
- It is also possible to issue datasets with Digital Object Identifiers (DOIs) on request so that datasets can be cited.