Difference between revisions of "ISO 19115:2003/19139"

From Gcube Wiki
Jump to: navigation, search
(DQ_Scope)
(Core Metadata)
 
(13 intermediate revisions by the same user not shown)
Line 178: Line 178:
  
 
|-
 
|-
|rowspan="2"| 9
+
|| 9
|rowspan="2"| spatialRepresentationInfo (O)
+
|| spatialRepresentationInfo (O)
| colspan="2"| topologyLevel
+
| colspan="2"|  
||code which identifies the degree of complexity of the spatial relationships
+
||digital representation of spatial and temporal references systems used in the dataset
||1
+
||[[#MD_TopologyLevelCode | MD_TopologyLevelCode]]
+
 
+
|-
+
| colspan="2"| geometryObjects (O)
+
||information about the geometric objects used in the dataset
+
 
||N
 
||N
||[[#MD_GeometricObject | MD_GeometricObject]]
+
||[[#MD_SpatialRepresentation | MD_SpatialRepresentation]]
  
 
|-
 
|-
Line 197: Line 191:
 
|bgcolor=lightgrey|1
 
|bgcolor=lightgrey|1
 
|bgcolor=lightgrey|Lines 10-20
 
|bgcolor=lightgrey|Lines 10-20
 +
 +
|-
  
 
|-
 
|-
Line 425: Line 421:
  
 
== Metadata package data dictionaries ==
 
== Metadata package data dictionaries ==
 +
  
 
==== CI_Citation ====
 
==== CI_Citation ====
Line 488: Line 485:
  
 
|}
 
|}
 +
  
 
==== MD_DigitalTransferOptions ====  
 
==== MD_DigitalTransferOptions ====  
Line 521: Line 519:
  
 
|}
 
|}
 +
  
 
==== CI_OnlineResource ====  
 
==== CI_OnlineResource ====  
Line 585: Line 584:
  
 
|}
 
|}
 +
  
 
==== CI_Telephone ====  
 
==== CI_Telephone ====  
Line 630: Line 630:
  
 
|}
 
|}
 +
  
 
==== CI_Address ====  
 
==== CI_Address ====  
Line 760: Line 761:
  
 
|}
 
|}
 +
  
 
==== DQ_Scope ====
 
==== DQ_Scope ====
Line 791: Line 793:
 
||1
 
||1
 
||Class
 
||Class
||[[#MD_ScopeCode MD_ScopeCode ]]
+
||[[#MD_ScopeCode | MD_ScopeCode ]]
 
|-
 
|-
  
 
|}
 
|}
 +
 +
 +
==== LI_Lineage ====
 +
 +
{|border="1" cellpadding="5" cellspacing="0"
 +
 +
!
 +
! Name
 +
! Definition
 +
! Obligation / Condition
 +
! Max occurrence
 +
! Data type
 +
! Domain
 +
|-
 +
 +
<!-- LI_Lineage -->
 +
|bgcolor=lightgrey|54
 +
|bgcolor=lightgrey|'''LI_Lineage'''
 +
|bgcolor=lightgrey|extent of characteristics of the data for which the quality information is reported
 +
|bgcolor=lightgrey|Use obligation/condition from referencing object
 +
|bgcolor=lightgrey|Use maximum occurrence from referencing object
 +
|bgcolor=lightgrey| Class <<DataType>>
 +
|bgcolor=lightgrey|Lines 55-57
 +
|-
 +
 +
<!-- statement  -->
 +
||55
 +
||statement
 +
||general explanation of the data producer’s knowledge about the lineage of a dataset
 +
||C
 +
||1
 +
||CharacterString
 +
||Free text
 +
|-
 +
 +
<!-- processStep  -->
 +
||56
 +
||processStep
 +
||information about events in the life of a dataset specified by the scope
 +
||C
 +
||N
 +
||Association
 +
||[[#LI_ProcessStep | LI_ProcessStep]]
 +
|-
 +
 +
<!-- source  -->
 +
||57
 +
||source
 +
||information about the source data used in creating the data specified by the scope
 +
||C
 +
||N
 +
||Association
 +
||[[#LI_Source | LI_Source]]
 +
|-
 +
|}
 +
  
 
==== CI_DateTypeCode ====
 
==== CI_DateTypeCode ====
Line 821: Line 879:
  
 
|}
 
|}
 +
  
 
==== CI_RoleCode ====
 
==== CI_RoleCode ====
Line 949: Line 1,008:
  
 
|}
 
|}
 +
  
 
==== MD_CharacterSetCode ====
 
==== MD_CharacterSetCode ====
Line 957: Line 1,017:
 
_8859part1, _8859part11, _8859part14, _8859part15, _8859part2, _8859part3, _8859part4, _8859part5, _8859part6, _8859part7, _8859part8, _8859part9.
 
_8859part1, _8859part11, _8859part14, _8859part15, _8859part2, _8859part3, _8859part4, _8859part5, _8859part6, _8859part7, _8859part8, _8859part9.
 
</source>
 
</source>
 +
  
 
==== MD_ScopeCode ====
 
==== MD_ScopeCode ====
Line 1,174: Line 1,235:
  
 
|}
 
|}
 +
  
 
==== CI_PresentationFormCode ====
 
==== CI_PresentationFormCode ====
Line 1,254: Line 1,316:
  
 
|}
 
|}
 +
  
 
==== MD_KeywordTypeCode ====
 
==== MD_KeywordTypeCode ====
Line 1,304: Line 1,367:
  
 
This package contains information about the scope and frequency of updating data. MD_MaintenanceInformation entity is optional and contains mandatory and optional metadata elements.
 
This package contains information about the scope and frequency of updating data. MD_MaintenanceInformation entity is optional and contains mandatory and optional metadata elements.
 +
 +
 +
== Examples ==
 +
 +
==== MD_MetaData ====
 +
 +
<source lang="xml">
 +
 +
<fileIdentifier>
 +
<gco:CharacterString>33462e78-e5ab-11c3-737d-b3a61366d028</gco:CharacterString>
 +
</fileIdentifier>
 +
<language>
 +
<gco:CharacterString>eng</gco:CharacterString>
 +
</language>
 +
<hierarchyLevel>
 +
<MD_ScopeCode codeList="http://metadata.dgiwg.org/codelistRegistry?MD_ScopeCode" codeListValue="dataset"/>
 +
</hierarchyLevel>
 +
<contact>
 +
<CI_ResponsibleParty>
 +
<individualName>
 +
<gco:CharacterString>Mario Rossi</gco:CharacterString>
 +
</individualName>
 +
<organisationName>
 +
<gco:CharacterString>ISTI-CNR</gco:CharacterString>
 +
</organisationName>
 +
<contactInfo>
 +
<CI_Contact>
 +
<address>
 +
<CI_Address>
 +
<electronicMailAddress>
 +
<gco:CharacterString>rossi@isti.cnr.it</gco:CharacterString>
 +
</electronicMailAddress>
 +
</CI_Address>
 +
</address>
 +
</CI_Contact>
 +
</contactInfo>
 +
<role>
 +
<CI_RoleCode codeList="http://www.isotc211.org/2005/resources/codeList.xml#CI_RoleCode" codeListValue="pointOfContact">pointOfContact</CI_RoleCode>
 +
</role>
 +
</CI_ResponsibleParty>
 +
</contact>
 +
<dateStamp>
 +
<gco:Date>2013-03-09</gco:Date>
 +
</dateStamp>
 +
<metadataStandardName>
 +
<gco:CharacterString>ISO19119</gco:CharacterString>
 +
</metadataStandardName>
 +
<metadataStandardVersion>
 +
<gco:CharacterString>2005/PDAM 1</gco:CharacterString>
 +
</metadataStandardVersion>
 +
 +
</source>
 +
 +
==== DQ_DataQuality ====
 +
 +
<source lang="xml">
 +
 +
<dataQualityInfo>
 +
<DQ_DataQuality>
 +
<scope>
 +
<DQ_Scope>
 +
<level>
 +
<MD_ScopeCode codeList="http://www.isotc211.org/2005/resources/codeList.xml#MD_ScopeCode" codeListValue="dataset">dataset</MD_ScopeCode>
 +
</level>
 +
</DQ_Scope>
 +
</scope>
 +
<lineage>
 +
<LI_Lineage>
 +
<statement>
 +
<gco:CharacterString>
 +
                                        Source Data History: Exploration License boundaries were sourced from the official Mining Register license documents.
 +
                                                License boundaries are legally defined to follow lines of latitude and longitude.
 +
                                                The register has existed since 1930. Processing Steps: Coordinates entered by keyboard from license documents.
 +
                                                Linework cleaned to remove duplicate arcs. Data adjusted for accurate state border and coastline.
 +
                                                Where appropriate, cadastral parcels removed from license polygons.
 +
                                                Associated attribute data also captured from license documents.
 +
</gco:CharacterString>
 +
</statement>
 +
</LI_Lineage>
 +
</lineage>
 +
</DQ_DataQuality>
 +
</dataQualityInfo>
 +
 +
</source>

Latest revision as of 17:45, 11 April 2013


ISO 19115:2003 defines the schema required for describing geographic information and services. It provides information about the identification, the extent, the quality, the spatial and temporal schema, spatial reference, and distribution of digital geographic data.

ISO 19115:2003 is applicable to:

  • the cataloguing of datasets, clearinghouse activities, and the full description of datasets;
  • geographic datasets, dataset series, and individual geographic features and feature properties.

ISO 19115:2003 defines:

  • mandatory and conditional metadata sections, metadata entities, and metadata elements;
  • the minimum set of metadata required to serve the full range of metadata applications (data discovery, determining data fitness for use, data access, data transfer, and use of digital data);
  • optional metadata elements - to allow for a more extensive standard description of geographic data, if required;
  • a method for extending metadata to fit specialized needs.

ISO 19139 provides the XML implementation schema for ISO 19115 specifying the metadata record format and may be used to describe, validate, and exchange geospatial metadata prepared in XML.

Model

<gmd:MD_Metadata id="" uuid="" xmlns:gmd="http://www.isotc211.org/2005/gmd">
  <gmd:fileIdentifier>{0,1}</gmd:fileIdentifier>
  <gmd:language>{0,1}</gmd:language>
  <gmd:characterSet>{0,1}</gmd:characterSet>
  <gmd:parentIdentifier>{0,1}</gmd:parentIdentifier>
  <gmd:hierarchyLevel>{0,unbounded}</gmd:hierarchyLevel>
  <gmd:hierarchyLevelName>{0,unbounded}</gmd:hierarchyLevelName>
  <gmd:contact>{1,unbounded}</gmd:contact>
  <gmd:dateStamp>{1,1}</gmd:dateStamp>
  <gmd:metadataStandardName>{0,1}</gmd:metadataStandardName>
  <gmd:metadataStandardVersion>{0,1}</gmd:metadataStandardVersion>
  <gmd:dataSetURI>{0,1}</gmd:dataSetURI>
  <gmd:locale>{0,unbounded}</gmd:locale>
  <gmd:spatialRepresentationInfo>{0,unbounded}</gmd:spatialRepresentationInfo>
  <gmd:referenceSystemInfo>{0,unbounded}</gmd:referenceSystemInfo>
  <gmd:metadataExtensionInfo>{0,unbounded}</gmd:metadataExtensionInfo>
  <gmd:identificationInfo>{1,unbounded}</gmd:identificationInfo>
  <gmd:contentInfo>{0,unbounded}</gmd:contentInfo>
  <gmd:distributionInfo>{0,1}</gmd:distributionInfo>
  <gmd:dataQualityInfo>{0,unbounded}</gmd:dataQualityInfo>
  <gmd:portrayalCatalogueInfo>{0,unbounded}</gmd:portrayalCatalogueInfo>
  <gmd:metadataConstraints>{0,unbounded}</gmd:metadataConstraints>
  <gmd:applicationSchemaInfo>{0,unbounded}</gmd:applicationSchemaInfo>
  <gmd:metadataMaintenance>{0,1}</gmd:metadataMaintenance>
  <gmd:series>{0,unbounded}</gmd:series>
  <gmd:describes>{0,unbounded}</gmd:describes>
  <gmd:propertyType>{0,unbounded}</gmd:propertyType>
  <gmd:featureType>{0,unbounded}</gmd:featureType>
  <gmd:featureAttribute>{0,unbounded}</gmd:featureAttribute>
</gmd:MD_Metadata>


Core Metadata

This data dictionary describes the characteristics of the metadata defined in ISO 19115. The dictionary is specified in a hierarchy to establish relationships and an organization for the information.

Note:

  • "Obligation / Condition" is a descriptor indicating whether a metadata entity or metadata element shall always be documented in the metadata or sometimes be documented (i.e. contains value(s)). This descriptor may have the following values: M (mandatory), C (conditional), or O (optional).
  • "Maximum occurrence" specifies the maximum number of instances the metadata entity or the metadata element may have. Single occurrences are shown by “1”; repeating occurrences are represented by “N”. Fixed number occurrences other than one are allowed, and will be represented by the corresponding number (i.e. “2”, “3”...etc).


Name Definition Max occurrence Domain
Metadata information (MD_Metadata) root entity which defines metadata about a resource or resources 1 Lines 1-9


1 fileIdentifier (M) unique identifier for this metadata file 1 Free text
2 language (M) language used for documenting metadata 1 Free text
3 characterSet (C) full name of the character coding standard used for the metadata set 1 MD_CharacterSetCode <<CodeList>>
4 hierarchyLevel (M) scope to which the metadata applies N MD_ScopeCode<<CodeList>>
5 contact (O) individualName (O) name of the responsible person- surname, given name, title separated by a delimiter 1 Free text
organisationName (O) name of the responsible organization 1 Free text
positionName (O) role or position of the responsible person 1 Free text
role (O) function performed by the responsible party 1 CI_RoleCode
contactInfo (O) phone (C) telephone numbers at which the organization or individual may be contacted 1 CI_Telephone
address (C) physical and email address at which the organization or individual may be contacted 1 CI_Address
onlineResource (C) online information that can be used to contact the individual or organization 1 CI_OnlineResource
6 dateStamp (O) date that the metadata was created 1 Date
7 metadataStandardName (O) name of the metadata standard (including profile name) used 1 FreeText
8 metadataStandardVersion (O) version (profile) of the metadata standard used 1 FreeText
9 spatialRepresentationInfo (O) digital representation of spatial and temporal references systems used in the dataset N MD_SpatialRepresentation
MD_Identification - MD_DataIdentification basic information required to uniquely identify a resource or resources 1 Lines 10-20
10 title (M) name by which the cited resource is known 1 Free text
date date (M) reference date for the cited resource N Date
dateType (M) event used for reference date 1 CI_DateTypeCode
edition version of the cited resource 1 Free text
presentationForm mode in which the resource is represented 1 CI_PresentationFormCode <<CodeList>>
11 abstract (M) brief narrative summary of the content of the resource(s) 1 Free text
12 purpose (M) summary of the intentions with which the resource(s) was developed 1 Free text
13 resourceMaintenance (O) maintenanceAndUpdateFrequency provieds information about the frequency of resources updates, and the scope of those updates N MD_MaintenanceInformation
14 graphicOverview (O) filename (M) URL of the file that contains a graphic that provides an illustration of the dataset 1 Free text
fileDescription (O) text description of the illustration 1 Free text
fileType (O) format in which the illustration is encoded. Examples: CGM, EPS, GIF, JPEG, PBM, PS, TIFF, XWD 1 Free text
15 descriptiveKeywords (M) keyword commonly used word(s) or formalised word(s) or phrase(s) used to describe the subject N Free text
type (O) subject matter used to group similiar keywords 1 MD_KeywordTypeCode <<CodeList>>
thesaurusName (O) name of the formally registered thesaurus or a similar authoritative source of keywords 1 CI_Citation <<DataType>>
16 language (M) language(s) used within the dataset N ISO 639-2, other parts may be used
17 characterSet (C) full name of the character coding standard used for the dataset N MD_CharacterSetCode <<CodeList>>
18 topicCatergory (O) main theme(s) of the dataset N MD_TopicCategoryCode
19 extent (O) westBoundLongitude (M) western-most coordinate of the limit of the dataset extent, expressed in longitude in decimal degrees (positive east) 1 Angle
eastBoundLongitude (M) eastern-most coordinate of the limit of the dataset extent, expressed in longitude in decimal degrees (positive east) 1 Angle
southBoundLongitude (M) southern-most coordinate of the limit of the dataset extent, expressed in latitude in decimal degrees (positive north) 1 Angle
northBoundLongitude (M) northern-most, coordinate of the limit of the dataset extent expressed in latitude in decimal degrees (positive north) 1 Angle
20 supplementalinfo (O) any other descriptive information about the dataset 1 Free text
MD_Constraints provieds restrictions on the access and use of metada N Lines 21-23
21 useLimitation (M) limitation affecting the fitness for use of the resource or metadata. Example, “not to be used for navigation” N Free text
22 accessConstraints (O) access constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the resource or metadata N MD_RestrictionCode
23 useConstraints (O) constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations or warnings on using the resource or metadata N MD_RestrictionCode
MD_Distribution provides information about the distributor of and options for obtaining the resource(s) 1 Lines 24
24 transferOptions (O) provides information about technical means and media by which a resource is obtained from the distributor N MD_DigitalTransferOptions
DQ_DataQuality quality information for the data specified by a data quality scope 1 Lines 25-26
25 scope (M) the specific data to which the data quality information applies. 1 DQ_Scope
26 lineage (O) statement non-quantitative quality information about the lineage of the data specified in the scope 1 LI_Lineage

Metadata package data dictionaries

CI_Citation

Name Definition Obligation / Condition Max occurrence Data type Domain
27 CI_Citation standardized resource reference Use obligation from referencing object Use maximum occurrence from referencing object Class <<DataType>> Lines 27-31
28 title name by which the cited resource is known M 1 CharacterString Free text
29 date reference date for the cited resource M N Class CI_Date <<DataType>>
30 edition version of the cited resource O 1 CharacterString Free text
31 presentationForm mode in which the resource is represented O 1 CharacterString CI_PresentationFormCode <<CodeList>>


MD_DigitalTransferOptions

Name Definition Obligation / Condition Max occurrence Data type Domain
32 MD_DigitalTransferOptions technical means and media by which a resource is obtained from the distributor Use obligation/condition from referencing object Use maximum occurrence from referencing object Aggregated Class (MD_Distribution and MD_Distributor) Lines 33
33 online information about online sources from which the resource can be obtained O N Class CI_OnlineResource


CI_OnlineResource

Name Definition Obligation / Condition Max occurrence Data type Domain
34 CI_OnlineResource information about online sources from which the dataset, specification, or community profile name and extended metadata elements can be obtained Use obligation/condition from referencing object Use maximum occurrence from referencing object Class <<DataType>> Lines 34-38
35 linkage location (address) from on-line access using a Uniform Resource Locator address or similar addressing scheme M 1 Class URL
36 protocol connection protocol to be used O 1 CharacterString Free text
37 name name of the online resource O 1 CharacterString Free text
38 description detailed text description of what the online resource is/does O 1 CharacterString Free text


CI_Telephone

Name Definition Obligation / Condition Max occurrence Data type Domain
39 CI_Telephone telephone numbers for contacting the responsible individual or organization Use obligation/condition from referencing object Use maximum occurrence from referencing object Class <<DataType>> Lines 40-41
40 voice telephone number by which individuals can speak to the responsible organization or individual O N CharacterString Free text
41 facsimile telephone number of a facsimile machine for the responsible organization or individual O N CharacterString Free text


CI_Address

Name Definition Obligation / Condition Max occurrence Data type Domain
42 CI_Address location of the responsible individual or organization Use obligation/condition from referencing object Use maximum occurrence from referencing object Class <<DataType>> Lines 43-48
43 deliveryPoint address line for the location (as described in ISO 11180) O N CharacterString Free text
44 city city of the location O 1 CharacterString Free text
45 administrativeArea state, province of the location O 1 CharacterString Free text
46 postalCode ZIP or postal code O 1 CharacterString Free text
47 country country of the physical address O 1 CharacterString ISO 3166-3, other parts may be used
48 electronicMailAddress address of the electronic mailbox of the responsible organization or individual O N CharacterString Free text


MD_GeometricObject

Name Definition Obligation / Condition Max occurrence Data type Domain
49 MD_GeometricObject number of objects, listed by geometric object type, used in the dataset Use obligation/condition from referencing object Use maximum occurrence from referencing object Class <<DataType>> Lines 50-51
50 geometricObjectType name of point or vector objects used to locate zero-, one-, two-, or three-dimensional spatial locations in the dataset M 1 Class MD_GeometricObjectTypeCode<<CodeList>>
51 geometricObjectCount total number of the point or vector object type occurring in the dataset O 1 Integer > 0


DQ_Scope

Name Definition Obligation / Condition Max occurrence Data type Domain
52 DQ_Scope extent of characteristics of the data for which the quality information is reported Use obligation/condition from referencing object Use maximum occurrence from referencing object Class <<DataType>> Lines 53
53 level hierarchical level of the data specified by the scope. M 1 Class MD_ScopeCode


LI_Lineage

Name Definition Obligation / Condition Max occurrence Data type Domain
54 LI_Lineage extent of characteristics of the data for which the quality information is reported Use obligation/condition from referencing object Use maximum occurrence from referencing object Class <<DataType>> Lines 55-57
55 statement general explanation of the data producer’s knowledge about the lineage of a dataset C 1 CharacterString Free text
56 processStep information about events in the life of a dataset specified by the scope C N Association LI_ProcessStep
57 source information about the source data used in creating the data specified by the scope C N Association LI_Source


CI_DateTypeCode

Name Definition
creation date identifies when the resource was brought into existence
publication date identifies when the resource was issued
revision date identifies when the resource was examined or re-examined and improved or amended


CI_RoleCode

Name Definition
resourceProvider party that supplies the resource
custodian party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource
owner party that owns the resource
dataset information applies to the dataset
user party who uses the resource
distributor party who distributes the resource
originator party who created the resource
pointOfContact party who can be contacted for acquiring knowledge about or acquisition of the resource
principalInvestigator key party responsible for gathering information and conducting research
processor information applies to a property type
publisher party who published the resource
author party who authored the resource


MD_TopologyLevelCode

Name Definition
geometryOnly geometry objects without any additional structure which describes topology
topology1D 1-dimensional topological complex – commonly called “chain-node” topology
planarGraph 1-dimensional topological complex that is planar. (A planar graph is a graph that can be drawn in a plane in such a way that no two edges intersect except at a vertex.)
fullPlanarGraph 2-dimensional topological complex that is planar. (A 2-dimensional topological complex is commonly called “full topology” in a cartographic 2D environment.)
surfaceGraph 1-dimensional topological complex that is isomorphic to a subset of a surface. (A geometric complex is isomorphic to a topological complex if their elements are in a one-to-one, dimensional-and boundry-preserving correspondence to one another.)
fullSurfaceGraph 2-dimensional topological complex that is isomorphic to a subset of a surface
topology3D 3-dimensional topological complex. (A topological complex is a collection of topological primitives that are closed under the boundary operations.)
fullTopology3D complete coverage of a 3D Euclidean coordinate space
abstract topological complex without any specified geometric realisation


MD_CharacterSetCode

Values:

big5, ebcdic, eucJP, eucKR, jis, shiftJIS, ucs2, ucs4, usAscii, utf16, utf7, utf8, 
_8859part1, _8859part11, _8859part14, _8859part15, _8859part2, _8859part3, _8859part4, _8859part5, _8859part6, _8859part7, _8859part8, _8859part9.


MD_ScopeCode

Name Definition
attributeType information applies to the characteristic of a feature
collectionHardware information applies to the collection hardware class
collectionSession information applies to the collection session
dataset information applies to the dataset
series information applies to the series
nonGeographicDataset information applies to non-geographic data
dimensionGroup information applies to a dimension group
feature information applies to a feature
featureType information applies to a feature type
propertyType information applies to a property type
fieldSession information applies to a field session
software information applies to a computer program or routine
service information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case
model information applies to a copy or imitation of an existing or hypothetical object
tile information applies to a tile, a spatial subset of geographic data


MD_TopicCategoryCode

Name Definition
farming rearing of animals and/or cultivation of plants

Examples: agriculture, irrigation, aquaculture, plantations, herding, pests and diseases affecting crops and livestock

biota flora and/or fauna in natural environment

Examples: wildlife, vegetation, biological sciences, ecology, wilderness, sealife, wetlands, habitat

boundaries legal land descriptions

Examples: political and administrative boundaries

climatologyMeteorologyAt mosphere processes and phenomena of the atmosphere

Examples: cloud cover, weather, climate, atmospheric conditions, climate change, recipitation economic activities, conditions and employment

economy processes and phenomena of the atmosphere

Examples: production, labour, revenue, commerce, industry, tourism and ecotourism, orestry, fisheries, commercial or subsistence hunting, exploration and exploitation of resources such as minerals, oil and gas

elevation height above or below sea level

Examples: altitude, bathymetry, digital elevation models, slope, derived products

environment environmental resources, protection and conservation

Examples: environmental pollution, waste storage and treatment, environmental impact assessment, monitoring environmental risk, nature reserves, landscape

geoscientificInformation information pertaining to earth sciences

Examples: geophysical features and processes, geology, minerals, sciences dealing with the composition, structure and origin of the earth’s rocks, risks of earthquakes, volcanic activity, landslides, gravity information, soils, permafrost, hydrogeology, erosion

health health, health services, human ecology, and safety

Examples: disease and illness, factors affecting health, hygiene, substance abuse, mental and physical health, health services

imageryBaseMapsEarthCover base maps

Examples: land cover, topographic maps, imagery, unclassified images, annotations

intelligenceMilitary military bases, structures, activities

Examples: barracks, training grounds, military transportation, information collection

inlandWaters inland water features, drainage systems and their characteristics

Examples: rivers and glaciers, salt lakes, water utilization plans, dams, currents, floods, water quality, hydrographic charts

location positional information and services

Examples: addresses, geodetic networks, control points, postal zones and services, place names

oceans features and characteristics of salt water bodies (excluding inland waters)

Examples: tides, tidal waves, coastal information, reefs

planningCadastre information used for appropriate actions for future use of the land

Examples: land use maps, zoning maps, cadastral surveys, land ownership

society characteristics of society and cultures

Examples: settlements, anthropology, archaeology, education, traditional beliefs, manners and customs, demographic data, recreational areas and activities, social impact assessments, crime and justice, census information

structure man-made construction

Examples: buildings, museums, churches, factories, housing, monuments, shops, towers

transportation means and aids for conveying persons and/or goods

Examples: roads, airports/airstrips, shipping routes, tunnels, nautical charts, vehicle or vessel location, aeronautical charts, railways 20.

utilitiesCommunication energy, water and waste systems and communications infrastructure and services

Examples: hydroelectricity, geothermal, solar and nuclear sources of energy, water purification and distribution, sewage collection and disposal, electricity and gas distribution, data communication, telecommunication, radio, communication networks


CI_PresentationFormCode

Name Definition
documentDigital digital representation of a primarily textual item (can contain illustrations also)
documentHardcopy representation of a primarily textual item (can contain illustrations also) on paper, photographic material, or other media
imageDigital likeness of natural or man-made features, objects, and activities acquired through the sensing of visual or any other segment of the electromagnetic spectrum by sensors, such as thermal infrared, and high resolution radar and stored in digital format
imageHardcopy likeness of natural or man-made features, objects, and activities acquired through the sensing of visual or any other segment of the electromagnetic spectrum by sensors, such as thermal infrared, and high resolution radar and reproduced on paper, photographic material, or other media for use directly by the human user
mapDigital map represented in raster or vector form
mapHardcopy map printed on paper, photographic material, or other media for use directly by the human user
modelDigital multi-dimensional digital representation of a feature, process, etc.
modelHardcopy 3-dimensional, physical model
profileDigital vertical cross-section in digital form
profileHardcopy vertical cross-section printed on paper, etc.
tableDigital digital representation of facts or figures systematically displayed, especially in columns
tableHardcopy digital representation of facts or figures systematically displayed, especially in columns
videoDigital digital video recording
videoHardcopy video recording on film


MD_KeywordTypeCode

Name Definition
discipline keyword identifies a branch of instruction or specialized learning
place keyword identifies a location
stratum keyword identifies the layer(s) of any deposited substance
temporal keyword identifies a time period related to the dataset
theme keyword identifies a particular subject or topic


MD_ReferenceSystem

This package contains the description of the spatial and temporal reference system(s) used in a dataset. MD_ReferenceSystem contains an element to identify the reference system used. MD_ReferenceSystem may be subclassed as MD_CRS, which is an aggregate of MD_ProjectionParameters and MD_EllipsoidParameters. MD_ProjectionParameters is an aggregate of MD_ObliqueLineAzimuth and MD_ObliqueLinePoint.


MD_Constraints

This package contains information concerning the restrictions placed on data. The MD_Constraints entity is optional and may be specified as MD_LegalConstraints and/or MD_SecurityConstraints. The otherConstraint element of MD_LegalConstraints shall be non-zero (used) only if accessConstraints and/or useConstraints elements have a value of “otherRestrictions”, which is found in the MD_RestrictionCode codelist.


MD_MaintenanceInformation

This package contains information about the scope and frequency of updating data. MD_MaintenanceInformation entity is optional and contains mandatory and optional metadata elements.


Examples

MD_MetaData

<fileIdentifier>
	<gco:CharacterString>33462e78-e5ab-11c3-737d-b3a61366d028</gco:CharacterString>
</fileIdentifier>
<language>
	<gco:CharacterString>eng</gco:CharacterString>
</language>
<hierarchyLevel>
	<MD_ScopeCode codeList="http://metadata.dgiwg.org/codelistRegistry?MD_ScopeCode" codeListValue="dataset"/>
</hierarchyLevel>
<contact>
	<CI_ResponsibleParty>
		<individualName>
			<gco:CharacterString>Mario Rossi</gco:CharacterString>
		</individualName>
		<organisationName>
			<gco:CharacterString>ISTI-CNR</gco:CharacterString>
		</organisationName>
		<contactInfo>
			<CI_Contact>
				<address>
					<CI_Address>
						<electronicMailAddress>
						<gco:CharacterString>rossi@isti.cnr.it</gco:CharacterString>
						</electronicMailAddress>
					</CI_Address>
				</address>
			</CI_Contact>
		</contactInfo>
		<role>
			<CI_RoleCode codeList="http://www.isotc211.org/2005/resources/codeList.xml#CI_RoleCode" codeListValue="pointOfContact">pointOfContact</CI_RoleCode>
		</role>
	</CI_ResponsibleParty>
</contact>
<dateStamp>
	<gco:Date>2013-03-09</gco:Date>
</dateStamp>
<metadataStandardName>
	<gco:CharacterString>ISO19119</gco:CharacterString>
</metadataStandardName>
<metadataStandardVersion>
	<gco:CharacterString>2005/PDAM 1</gco:CharacterString>
</metadataStandardVersion>

DQ_DataQuality

<dataQualityInfo>
	<DQ_DataQuality>
		<scope>
			<DQ_Scope>
				<level>
					<MD_ScopeCode codeList="http://www.isotc211.org/2005/resources/codeList.xml#MD_ScopeCode" codeListValue="dataset">dataset</MD_ScopeCode>
				</level>
			</DQ_Scope>
		</scope>
		<lineage>
			<LI_Lineage>
				<statement>
					<gco:CharacterString>
                                        	Source Data History: Exploration License boundaries were sourced from the official Mining Register license documents. 
                                                License boundaries are legally defined to follow lines of latitude and longitude. 
                                                The register has existed since 1930. Processing Steps: Coordinates entered by keyboard from license documents. 
                                                Linework cleaned to remove duplicate arcs. Data adjusted for accurate state border and coastline. 
                                                Where appropriate, cadastral parcels removed from license polygons. 
                                                Associated attribute data also captured from license documents. 
					</gco:CharacterString>
				</statement>
			</LI_Lineage>
		</lineage>
	</DQ_DataQuality>
</dataQualityInfo>