Depth data - coverage

Definition: (**The dataset is under production and downloadable files are not available yet**.) The data set shows the coverage of bathymetric mapped areas in the Norwegian coastal and sea areas.

Updated: 07.10.2024
Owner: Norwegian Mapping Authority

Usage

The data set can be used to get a rough overview of available data, when planning activities in an area. Modern data has been collected using multi-beam echo sounders, while older data using single beam echo sounders or other older equipment.

Explanation of assessment of FAIR principles:

There have made various tests to evaluate datasets in relation to the FAIR criteria. These are our interpretations, which then assess the criteria in relation to standards and protocols used for spatial data in Norway and Europe. For more information on which calculations we use for each indicator, look at the details of FAIR assessments for each specific dataset.

Read more Read less

Good (over 90%): The dataset adheres to the FAIR principles in a good way. You must do qualitative research yourself to assess any measures to further improve conditions regarding re-use.

Satisfactory (75-90%): The dataset meets many of the FAIR principles, but should be improved in several areas to ensure reuse.

Needs improvement (50-75%): The dataset meets a few of the FAIR principles in a good way, and needs to be improved in several areas.

Poor (less than 50%): The dataset has major shortcomings in terms of meeting FAIR principles and needs to be improved in many areas

FAIR-status: 48%

90%

Findable: Metadata and data should be easy to find for both humans and computers. Machine-readable metadata are essential for automatic discovery of datasets and services

Details Read less

  • F1: (Meta)data are assigned a globally unique and persistent identifier
    • It is checked that there is metadata in Geonorge. (All metadata in Geonorge have persistent and unique identifiers and are searchable on the web). The request returns metadata in a standardized form. (weight 25)
  • F2: Data are described with rich metadata
    • At least three thematic keywords must be entered in the metadata (weight 10)
    • Title should be a maximum of 105 characters to provide a simple and consistent name that is easy searchable (weight 5)
    • The description should be at least 200 characters to be able to provide sufficient information about the dataset and not longer than 600 characters to obtain a good but concise and precise description of what the dataset contains. (There are specific metadata elements where you can enter supplementary information, lineage, quality, update frequency, possibly link to other documentation such as Data Product Specifications, Product sheets, etc). (weight 10)
  • F3: Metadata clearly and explicitly include the identifier of the data they describe
    • Metadata should have a unique reference to the dataset. Datasets should not only be referred to by name, but also by the unique identifier (uuid) for the dataset. This must be entered in the metadata together with a namespace. (Datasets are defined with unique IDs in Geonorge's namespace register if they have entered dataset-IDs in metadata) (weight 25)
  • F4: (Meta)data are registered or indexed in a searchable resource
    • Metadata located in Geonorge is searchable through CSW API (OGC) and DCAT API (W3C). This makes metadata searchable through standardized APIs for the geodata industry, research and science and "open data" industry both nationally and internationally. (weight 25)
25%

Accessible: Datasets must be accessible through standardized and open interfaces.

Details Read less

  • A1: Datasets are available through standard web protocols and open standardised services
    • It is checked whether the dataset has a "direct" download service (WFS or WCS) (weight 15)
    • It is checked whether the dataset has a view service (WMS or WMTS) (weight 15)
    • It is checked whether the dataset is available through the "Geonorge download api" (weight 15)
    • Checking if dataset is available as a download service for predefined datasets (Atom Feed) (weight 5)
    • It is checked whether the protocols that provide access to the datasets are openly accessible and readable with standard IT tools. Which we consider to be sufficient if one has provided a download URL with Https response (weight 40)
    • The protocol allows for an authentication and authorisation procedure, where necessary
  • A2: Metadata are accessible, even when the data are no longer available
30%

Interoperabel: The data usually need to be integrated with other data. In addition, the data need to interoperate with applications or workflows for analysis, storage, and processing.

Details Read less

  • I1: Metadata and datasets are represented through international, well-documented and accessible standards.
    • Metadata for geodata must be established in accordance with the metadata standard ISO19115. (Metadata in Geonorge is based on the mentioned standard.) (weight 20)
    • The dataset should be available in internationally known open formats. Check for GML for vector data or tiff / jpg for raster data and NetCDF (weight 10)
    • If the dataset is offered as GML, the dataset must validat according to the Data Product Specification's UML model (weight 20)
  • I2: Metadata and datasets shall use vocabularies, concepts and code lists and refer to searchable resources on the web that are managed with unique identifiers.
    • Topic category must be filled in metadata to categorize the dataset in an international context (weight 10)
    • National theme category must be filled in metadata to categorize the dataset in a national context (weight 10)
  • I3: (Meta)data include qualified references to other (meta)data
    • Metadata must refer to terms that are described / defined in the dataset's UML model in Geonorge's object catalog (SOSI model register) (weight 10)
    • The dataset must be modeled in UML and the metadata must refer to the UML model in Geonorge's object catalog (SOSI model register) (weight 20)
50%

Reusable: The ultimate goal of FAIR is to optimise the reuse of data. To achieve this, metadata and data should be well-described so that they can be replicated and/or combined in different settings.

Details Read less

  • R1.1: (Meta)data are released with a clear and accessible and resolvable data usage license
    • Licenses in the Geonorge register meet this requirement (weight 30)
  • R1.2: Metadata about quality, coverage, processing, calculations, etc. must be provided.
    • Lineage must be provided with more than 200 characters (weight 10)
    • Update frequency must be specified in metadata (weight 5)
    • Link to Data Product Specification must exist in metadata(weight 10)
    • Scale for the dataset must be provided in the metadata(weight 5)v
    • Coverage map must be provided in the metadata (by municipality or grid) (weight 5)
    • Purpose must be provided in the metadata (weight 5)
  • R1.3 (Meta)data meet domain-relevant community standards
    • Metadata must follow the standards: ISO19115 and DCAT-AP-NO (weight 15)
    • Datasets are delivered on international open vector formats such as GML or raster / gridded data such as TIFF / JPEG / NetCDF (weight 15)

Mareano status

  • useable
    Metadata

    For metadata quality to be good, metadata must be validated in Geonorge's metadata editor. This means that all required fields must be filled in. Otherwise, metadata is considered as usable if they exists.

  • deficient
    Product spesification

    In order to achieve good fulfilment of requirements, the metadata should link to an approved SOSI Data Product Specification for the dataset. Other referenced data product specifications may provide usable fulfilment of requirements. Otherwise, status will be deficient .

  • deficient
    SOSI requirement status

    In order to achieve good fulfilment of requirements, downloadable SOSI files must validate against the UML model in the Data Product Specification. It will be clear from the metadata whether SOSI files conform to the data product specification. If there are downloadable SOSI files, then it will qualify for usable fulfilment of requirements. Otherwise, status will be deficient .

  • deficient
    GML requirement status

    In order to achieve good fulfilment of requirements, downloadable GML files must validate against UML model in the Data Product Specification. (It will be clear from the metadata whether GML files comply with the data product specification.) If there are downloadable GML files, then it will qualify for usable fulfilment of requirements. Otherwise, status will be deficient .

  • deficient
    WMS status

    In order to achieve good fulfilment of requirements, the service must meet the most important requirements in Geonorge's application for service status. If there is a WMS service, it will qualify for usable fulfilment of requirements. In both cases, metadata must be linked to metadata of the dataset. Otherwise, status will be deficient .

  • good
    WFS status

    In order to achieve good fulfilment of requirements, the service must meet the most important requirements in Geonorge's application for service status. If there is a WFS service, it will qualify for usable fulfilment of requirements. In both cases, metadata must be linked to metadata of the dataset. Otherwise, status will be deficient .

  • deficient
    ATOM feed status

    In order to achieve good fulfilment of requirements, the dataset must be available through an atomic feed service registered in Geonorge. Otherwise, status will be deficient .

  • good
    Download requirements status

    If the dataset is provided through an atom feed or a WFS where requirements are well met, this will qualify for good fulfilment of requirements. If the dataset is only available as WFS with usable fulfilment of requirements, this qualifies for the grade usable . Otherwise, status will be deficient .

Back