ISO Data Identification

From DGIWG
Jump to: navigation, search

Data Identification

A Data Identification is an instance of gmd:MD_DataIdentification or one of its subclasses.

Its property instances are described below:


+ citation[1]:CI_Citation
  + title[1]:CharacterString RSTITLE - Default is To be determined
  + alternateTitle[0..1]:CharacterString RSALT (when set)
  + date[1..*]:CI_Date RSDATE (for each) -  See Note 1
    + date[1]:Date date - Default is 9999
    + dateType[1]:CI_DateTypeCode type - Default is publication
  + edition[0..1]:CharacterString RSED (when set)
  + editionDate[0..1]:Date RSEDDAT (when set)
  + identifier[0..1]:RS_Identifier When RSSHNA is set -  See Note 2
    + code[1]:CharacterString RSSHNA
    + codeSpace[1]:CharacterString
  + identifier[0..*]:RS_Identifier RSID (for each) -  See Identifier and Note 2
  + series[0..1]:CI_Series When RSSERI is set
    + name[1]:CharacterString RSSERI
+ abstract[1]:CharacterString RSABSTR - Default is To be determined
+ purpose[0..1]:CharacterString RSPURP (when set)
+ status[0..1]:MD_ProgressCode RSSTAT (when set)
+ pointOfContact[0..*]:CI_ResponsibleParty RSRPTY (for each) -  See Responsible Party
+ resourceMaintenance[0..1]:MD_MaintenanceInformation RSMTNC (when set)
  + maintenanceAndUpdateFrequency[1]:MD_MaintenanceFrequencyCode maintenanceFrequency - Default is unknown
  + dateOfNextUpdate[0..1]:Date maintenanceDate
  + maintenanceNote[0..1]:CharacterString maintenanceNote
+ graphicOverview[0..1]:MD_BrowseGraphic When THUMB is set
  + fileName[1]:CharacterString THUMB
  + fileDescription[1]:CharacterString thumbnail
+ graphicOverview[0..*]:MD_BrowseGraphic GPHICS (for each)
  + fileName[1]:CharacterString name (when linkage is not set)
  + fileName[1]:Anchor name (when linkage is set)
    + href[1]:CharacterString linkage
  + fileDescription[1]:CharacterString description
+ resourceFormat[0..1]:MD_Format RSFMT (when set) -  See Format
+ descriptiveKeywords[0..1]:MD_Keywords When DGITYP is set -  See Geospatial Information Type and Note 3
+ descriptiveKeywords[0..1]:MD_Keywords When RSGFLV is set -  See Resource Georeferencing Level and Note 3
+ descriptiveKeywords[0..1]:MD_Keywords When RSPREF is set -  See Resource Representation Form and Note 3
+ descriptiveKeywords[0..1]:MD_Keywords When RSDTLVL is set -  See Resource Data Level and Note 3
+ descriptiveKeywords[0..1]:MD_Keywords When RSTHEME is set -  See Resource Theme and Note 3
+ descriptiveKeywords[0..1]:MD_Keywords When ASSOC is set -  See Image Association Type and Note 3
+ descriptiveKeywords[0..1]:MD_Keywords When SPECTMOD is set -  See Spectral Mode and Note 3
+ descriptiveKeywords[0..*]:MD_Keywords RSKWDS (for each) -  See Resource Keyword Set and Note 3
+ resourceSpecificUsage[0..*]:MD_Usage RSSPUS (for each)
  + specificUsage[1]:CharacterString name
  + userDeterminedLimitations[0..1]:CharacterString limitation (when set)
  + userContactInfo[1]:CI_ResponsibleParty userContact -  See Note 10
+ resourceConstraints[0..*]:MD_SecurityConstraints RSSCST (when set) -  See Security Constraints and Note 4
+ resourceConstraints[0..*]:NGMP_Constraints RSREL (for each)
  + useLimitation[0..1]:CharacterString statementExtension
  + releasability[1]:NGMP_Releasability
    + addressee[0..*]:CI_ResponsibleParty For each addressee
      + organisationName[1]:CharacterString addressee
      + role[1]:CI_RoleCode user
    + statement[1]:CharacterString statement -  See Note 9
    + statement[0..*]:CharacterString disseminationConstraints (for each)
+ resourceConstraints[0..*]:MD_Constraints For each RSUSE
  + useLimitation[1]:CharacterString RSUSE
+ resourceConstraints[0..*]:MD_LegalConstraints RSLCST (for each) -  See Legal Constraints
+ spatialRepresentationType[0..1]:MD_SpatialRepresentationTypeCode RSRPTP
+ spatialResolution[0..1]:MD_Resolution RSSRES (for each) (when RSSRES.distance is set) -  See Note 6
  + distance[1]:Distance distance -  See Note 8
+ spatialResolution[0..*]:MD_Resolution RSSRES (for each) (when RSSRES.equivalentScale is set) -  See Note 6
  + equivalentScale[1]:MD_RepresentativeFraction
    + denominator[1]:Integer equivalentScale
+ language[1]:LanguageCode RSDLOC.language -  See Note 7
+ language[0..*]:LanguageCode RSTLOC.language (for each) (when RSTLOC is set)
+ characterSet[1..*]:MD_CharacterSetCode RSDLOC.encoding
+ characterSet[1..*]:MD_CharacterSetCode RSTLOC.encoding (for each) (when RSTLOC is set)
+ topicCategory[1..*]:MD_TopicCategoryCode RSTOPIC (for each) - Default is imageryBaseMapsEarthCover -  See Note 14
+ environmentDescription[0..1]:CharacterString RSENVD
+ extent[0..*]:EX_Extent RSEXT (for each) -  See Extent and Note 5
+ extent[0..*]:EX_Extent RSSRES (for each) (when RSSRES.levelOfDetail is set)
  + description[1]:CharacterString levelOfDetail -  See Note 11
+ extent[0..*]:EX_Extent RSSRES (for each) (when RSSRES.vertical is set)
  + description[1]:CharacterString vertical -  See Note 12
+ extent[0..*]:EX_Extent RSTRES (for each) (when set)
  + description[1]:CharacterString value & 10^-& factor & unit See Note 13
+ supplementalInformation[0..1]:CharacterString RSREM
Notes:
1. There may be many instances of the date property with different date types including publication, revision or creation. The order of these instances is not fixed.
2. There may be many instances of the identifier property corresponding to RSSHNA, RSID or identifiers out of DMF scope. The one corresponding to RSSHNA is the first one for which the codeSpace value matches RSSERI.
3. There may be many instances of the descriptiveKeywords property providing keywords from different thesauri. The order of these instances is not fixed.
4. There may be many instances of the resourceConstraints property. The order of these instances is not fixed.
5. Except for non-geographic data and loose services, one of boundingBox or geogId is mandatory.
6. There may be many instances of the spatialResolution property providing either equivalent scales or ground sample distances. The order of these instances is not fixed.
7. The language property can be defaulted to the value of the Metadata Language when the resource does not contain textual information.
8. Units of measures are implemented in the ISO metadata by reference to a unit of measure register. The URL of the reference can be derived from the codelist value of the DMF Property. See Additional Instructions
9. Default value for this element should be set by the implementer’s security policy.
10. Default values are role=user and organisationName=undefined
11. Preceded by "Level of detail: "
12. Preceded by "Vertical resolution: ". Value and unit are concatenated. Eg: 'Vertical resolution: 2 m'.
13. Preceded by "Temporal resolution: ". Eg: 'Temporal resolution: 5 10-3s'
14. If TopicCategory is "disaster" it should be mapped to a keyword.