Identification
From DGIWG
Revision as of 12:08, 29 July 2019 by DNK Hjelmager (talk | contribs)
| Identifier | Title / Description | Value Domain | Card | Condition | Metadata class | Guidelines | Example |
| RSTITLE
[DMF/Core]
|
Resource Title
This is a characteristic and often a unique name by which the resource is known.
|
Free Text
Default is To be determined
|
1 | DMF/Core defines the minimum set of metadata elements to be implemented by any metadata catalogue. This set satisfies the discovery use case. | Default value is “To be determined” but it is strongly recommended to find a better and proper title for the resource. | For WebServices: RSTITLE should be equal to name in the capabilities * A service name/title should be included in the data product specification if a service distribution is foreseen for the product
For dataset or series:ProductName_MapSeries_SheetNumber_edition * ASRP_JOG_1501-A_NK-32-03_01-GSGS
| |
| RSALT
[DMF/Common]
|
Resource Alternate Title
This is a short name, a more colloquial name or a name in another language by which the resource is known.
|
Free Text | 0..1 | DMF/Common is an additional set of metadata elements for a more complete description of any type of resource supported by DMF. It extends DMF/Core and covers discovery and basic evaluation use cases. | For webservices: RSALT for webservice should be used if more information needed (eg. series served by the service, purpose of the service, etc.)
For Hard copy maps: RSALT Could be used to mention: * Title of the map as it is
For datasets and series: Ex: SAC_M5219A/Sheet2-SouthEastEngland
| ||
| RSABSTR
[DMF/Core]
|
Resource Abstract
This is a brief textual summary of the content of the resource.
|
Free Text
Default is To be determined
|
1 | DMF/Core defines the minimum set of metadata elements to be implemented by any metadata catalogue. This set satisfies the discovery use case. | The abstract should include human-readable information to explain the product specificity. It can be used for research purposes (give an overview of the content), providing definitions or a general understanding of what the data is.
Default value is “To be determined” but it is strongly recommended to find a better and proper abstract for the resource.
Recommendations:
• Address all levels of understanding in the abstract for the different users
• Include an indication on the geographic area covered by the data
• Include the version of the data if several versions are available
• Avoid any reference to a responsible party
• Avoid acronyms or define them (either in the title or in the abstract).
• Use generated values : * Based on fixed on fixed values (in a register for example)
|
Abstract examples:
"Air Information: Airfield limits; radio aids; isogonals; full graticule at 15' interval with ticks at 1' interval; Maximum Terrain Elevations/Maximum Elevation Figures; vertical obstructions above 200 feet; restricted airspace; powerlines. Base information: International and administrative boundaries; relief by contours (interval varies), layer tints, hillshading, surface features, elevations in feet; towns classified by population and importance, settlements by built-up area or building symbols; roads classified by surface, width and weatherability, route markers, tracks, trails; railways classified by gauge/number of tracks; vegetation, cultivation; water and coastal features; glossary; bilingual legend on some sheets."
"This set of products provides level U near-infrared and colored orthorectified mosaic made from Pleiades satellite(s) images focusing on People's Democratic Republic of Algeria and Republic of Mali."
"A matrix of heighted data points representing the Earth’s topographic surface in a regular mesh pattern of horizontal and vertical coordinates."
"The orthorectified scenes were processed by Mapping and Charting Establishment - Department of National Defence - Canada."
"Multinational Geospatial Co-production Program (MGCP) dataset covering the 1°×1° degree cell between 3 and 4 longitudes and 6 and 7 latitudes."
| |
| RSPURP
[DMF/Core]
|
Resource Purpose
This is a summary of the intentions with which the resource was developed.
|
Free Text | 0..1 | DMF/Core defines the minimum set of metadata elements to be implemented by any metadata catalogue. This set satisfies the discovery use case. | |||
| RSTYPE
[DMF/Core]
|
Resource Type Code
This is the type code of the resource described by the metadata: resources listed in the codelist are the only types of resources in the scope of DMF.
|
Resource Type Codelist
Default is dataset |
1 | DMF/Core defines the minimum set of metadata elements to be implemented by any metadata catalogue. This set satisfies the discovery use case. | Dataset | ||
| RSTYPN
[DMF/Core]
|
Resource Type Name
This is the type name of the resource described by the metadata.
|
Free Text | 0..1 | RSTYPN value shall differ from RSTYPE when it is set, in order to provide a more comprehensive name for the type of resource. | DMF/Core defines the minimum set of metadata elements to be implemented by any metadata catalogue. This set satisfies the discovery use case. | RSTYPN should be documented if RSTYPE not equal to dataset | |
| RSED
[DMF/Core]
|
Resource Edition
This is the version identifier of the resource.
|
String | 0..1 | DMF/Core defines the minimum set of metadata elements to be implemented by any metadata catalogue. This set satisfies the discovery use case. | Ed. 1. | ||
| RSEDDAT
[DMF/Core]
|
Resource Edition Date
This is the reference date of this edition of the resource (see RSED).
|
Date or DateTime | 0..1 | Strongly recommended for products that have an edition. | DMF/Core defines the minimum set of metadata elements to be implemented by any metadata catalogue. This set satisfies the discovery use case. | Should be taken from the product specification. | 2017-10-12 or 2017-10-12T11:15:00 |
| RSID
[DMF/Core]
|
Resource Identifier
This is a value uniquely identifying the resource within a specific context.
|
Identifier | 0..* | It is highly recommended to provide at least a unique identifier code value (i.e., a code independent of any namespace, a UUID). | DMF/Core defines the minimum set of metadata elements to be implemented by any metadata catalogue. This set satisfies the discovery use case. | If a national stock number (NSN) or a national reference number (NRN) is set, there should be an instance of RSID for both of them | code: lakes
codeSpace: urn:eu:europa:ec:jrc:rdsi:id:dataset:ccm2.1 Ex of NSN: 7644011234567
|
| RSKWDS
[DMF/Core]
|
Resource Keyword Set
Set of keywords used to describe the resource.
|
Controlled Vocabulary | 0..* | DMF/Core defines the minimum set of metadata elements to be implemented by any metadata catalogue. This set satisfies the discovery use case. | The keywords should be taken from an online thesaurus, controlled vocabulary or ontology; | Mali, topographic map, DTOX | |
| THUMB
[DMF/Core]
|
Resource Thumbnail
Link access to the thumbnail of the resource.
|
URI
URL or File Path |
0..1 | DMF/Core defines the minimum set of metadata elements to be implemented by any metadata catalogue. This set satisfies the discovery use case. | https://www.nato.int/fmn/exercise_x/thumb.jpg; | ||
| GPHICS
[DMF/Common]
|
Resource Graphics
Sample, overview or other illustration of the resource.
|
Browse Graphic | 0..* | One value of the following values should be used for GPHICS.description: 'Overview' (overall illustration for the resource), 'Sample' (representative extract of the resource, illustrating data density), 'Legend' (legend for the resource) or 'TilingScheme' (partitioning of the space). | DMF/Common is an additional set of metadata elements for a more complete description of any type of resource supported by DMF. It extends DMF/Core and covers discovery and basic evaluation use cases. | GPHICS.linkage Should be a URL or File Path:
|
https://www.nato.int/fmn/exercise_x/thumb.jpg; |
| RSSRES
[DMF/Core]
|
Resource Spatial Resolution
Factor which provides a general understanding of the density of spatial data in the resource or describes the range of resolution in which a digital resource may be used.
|
Resolution | 0..* | One instance of Resolution containing a horizontal ground sample distance is mandatory for the sensor class. | DMF/Core defines the minimum set of metadata elements to be implemented by any metadata catalogue. This set satisfies the discovery use case. | This element should be repeated when describing the upper and lower range. It is not applicable to non-geo data. | 1:50000 or 1:40000 – 1:60000
distance.value = 0.25
distance.unit = meter
|
| RSTRES
[DMF/Common]
|
Resource Temporal Resolution
Smallest resolvable temporal period in a resource.
|
Interval Length | 0..* | DMF/Common is an additional set of metadata elements for a more complete description of any type of resource supported by DMF. It extends DMF/Core and covers discovery and basic evaluation use cases. | 2008-01-01T11:45:30 to 2008-12-31T09:10:00 | ||
| RSRPTP
[DMF/Core]
|
Resource Spatial Representation Type
This describes the method used to spatially represent geographic information.
|
Spatial Representation Type Codelist | 0..1 | DMF/Core defines the minimum set of metadata elements to be implemented by any metadata catalogue. This set satisfies the discovery use case. | Not applicable to analogue data. | Vector | |
| RSTOPIC
[DMF/Core]
|
Resource Topic Category
The topic category is a high-level classification scheme to assist in the grouping and topic-based search of available spatial data resources.
|
Topic Category Enumeration
Default is imageryBaseMapsEarthCover |
0..* | Mandatory if RSTYPE equal to dataset or series | DMF/Core defines the minimum set of metadata elements to be implemented by any metadata catalogue. This set satisfies the discovery use case. | There is no specific topic category defined for topographic dataset and series. The best match is imageryBaseMapsEarthCover code. | · intelligenceMilitary · boundaries · society · disaster |
