ISO Metadata
Standards
David Danko, ESRI
ISO TC 211 Metadata Project Leader
UC 2007 Tech Sessions 1
Communicating geographic knowledge
Encapsulating the real world
Providing one’s “universe of discourse” to another
UC 2007 Tech Sessions 2
GIS Abstracts Geography into a Modern Information
Technology Framework
…Abstracting Geographic Knowledge
GeoVisualization
Data Management Decision Support
Encapsulating Analysis
Real World
Knowledge
Models
Maps
GIS
Metadata
Data
Models
Geodata Geodatabase
Sets
… an Information System for Geography
UC 2007 Tech Sessions 3
GIS Abstracts Geography Into Five Basic
Elements
Data Models
Geodata Sets
Process and Workflow Models
Maps and Globes
Metadata
. . . Together They Represent the Building
Blocks of Geographic Knowledge UC 2007 Tech Sessions 4
Metadata
Key building block abstracting geographic
knowledge
• Data about data
–Geographic area covered
–Currency
–Rules of use
–Positional accuracy
–Data dictionary
–Means of encoding
–Datum
–Map projection
• A Key interoperability technology:
–Producers explain their product
–Users learn about products
• Non standard products can be understood
UC 2007 Tech Sessions 5
Metadata Applications
Understanding the right data for the right purpose
• Locate • Extract
–Find
–Order
–Discover
–Download
–Structured searches vs.
unstructured
• Evaluate • Employ
–Define, Pleasantville
–Restrictions Pleasantville
–Apply,
–Quality
–Use,
–Reputation Pleasantville
– & Understand
geographic
knowledge
UC 2007 Tech Sessions 6
ISO 19115:2003
UC 2007 Tech Sessions 7
ISO 19115:2003
Scope
• ...the schema required for describing geographic
information and services.
• ...information about the identification, the extent, the
quality, the spatial and temporal schema, spatial
reference, and distribution of digital geographic data.
• ...applicable to the cataloguing of datasets,
clearinghouse activities, and the full description of
datasets for a wide range of geographic applications.
• …applicable to geographic datasets, dataset series, and
individual geographic features and attributes
• ...may be used for other forms of geographic data such
as map, charts, textual documents
UC 2007 Tech Sessions 8
19115:2003 Geographic Information – Metadata
•Defines metadata elements;
–Provides a schema (UML);
–Establishes a common set of metadata
terminology, definitions (data dictionary);
UC 2007 Tech Sessions 9
Metadata UML Packages
Data Quality Constraint
Identification
Information Information
Information
Locate 19113,14
Metadata
Maintenance
Extension
Information Evaluate Information
Metadata
Content
Distribution
Information
19110, 21, 23, 24 Extract Information
Spatial 19107
Representation Portrayal ApplicationEmployReference
Information Catalogue Schema 19109 System
Information Information Information
19108, 11, 12
UC 2007 Tech Sessions 10
ISO 19115:2003 Annex A
Metadata packages
> MD_ReferenceSystem
MD_SpatialRepresentation (from Reference system information)
(from Spatial representation information) 0..* +referenceSystemInfo
+spatialRepresentationInfo 0..*
MD_MetadataExtensionInformation
(from Metadata extension information)
0..*
DQ_DataQuality +metadataExtensionInfo
(from Data quality information)
+dataQualityInfo 0..*
MD_MaintenanceInformation
(from Maintenance information)
+metadataMaintenance +resourceMaintenance
0..1
+distributionInfo
MD_Metadata 0..*
MD_Distribution + fileIdentifier [0..1] : CharacterString
+ language [0..1] : CharacterString
(from Distribution information) + characterSet [0..1] : MD_CharacterSetCode = "utf8"
0..1 + parentIdentifier [0..1] : CharacterString >
+ hierarchyLevel [0..*] : MD_ScopeCode = "dataset"
+ hierarchyLevelName [0..*] : CharacterString 1..* MD_Identification
+ contact : CI_ResponsibleParty (from Identification information)
+ dateStamp : Date
+contentInfo 0..* + metadataStandardName [0..1] : CharacterString +identificationInfo +resourceConstraints
+ metadataStandardVersion [0..1] : CharacterString
MD_ContentInformation
(from Content information)
0..* 0..*
+portrayalCatalogueInfo MD_Constraints
0..* +metadataConstraints
from Constraint information)
MD_PortrayalCatalogueReference (
(from Portrayal catalogue information)
+applicationSchemaInfo Conditional statements:
0..* language: documented if not defined by the encoding
standard
MD_ApplicationSchemaInformation characterSet: documented if ISO 10646-1 not used
and not defined by the encoding standard
(from Application schema information) hierarchyLevel: documented if hierarchyLevel not
equal to "dataset"?
hierarchyLevelName: documented if hierarchyLevel
not equal to "dataset"? UC 2007 Tech Sessions 11
Metadata is composed Content Information
of information chapters Distribution information
(packages) Data quality information
Spatial representation info
Maintenance information
Reference system information
Constraint information
Identification information
Metadata
fileIdentifier: 3A2234641211B12
language: en
characterSet: (default = "utf8“)
parentIdentifier: National Map TopoSeries 864 9
hierarchyLevel: (default = "dataset“)
hierarchyLevelName: (not needed) 8
contact : CI_ResponsibleParty 7
dateStamp : 20060417 6
metadataStandardName: ISO 19115:2003
metadataStandardVersion: (not needed) or 5
metadataStandardVersion: North American Profile
1.0
4
3
2
Chapter 1 UC 2007 Tech Sessions 12
ISO 19115:2003 Annex B
Metadata data dictionary
Name/Role Short Definition Obligation/ Maximum Data type Domain
Name Name Condition occurrence
29 MD_Identific ident basic Use Use Aggregated Lines 30-41
ation information obligation maximum Class
require d to from occurrence (MD_Metadata)
uniquely identify referencing for >
a resource object referencing
object
30 citation idCitation citation data for M 1 Class CI_Citation
the resource >
(B3.2)
31 abstract idAbs brief narratiave M 1 CharacterString Free text
summary
32 purpose idPurp summary of the O 1 CharacterString Free text
intentions with
which the
resource was
developed
33 credit idCredit recognition of O 1 CharacterString Free text
those who
contributed to
the resource
34 statusCode idStatCode status of O N Class MD_ProgressCode
resource >
(B.6.26)
UC 2007 Tech Sessions 13
DataIdentification details
characterSet: documented if ISO 10646-1
is not used
{MD_Metadata.hierarchyLevel = "dataset"
implies count (extent.geographicElement.
MD_DataIdentification EX_GeographicBoundingBox) + count
(extent.geographicElement.EX_GeographicDe
scription >=1}
+ abstract : CharacterString
{MD_Metadata.hierarchyLevel notEqual
+ citation : CI_Citation
“dataset” or “series” implies topicCatagory
+ credit [0..*] : CharacterString is not mandatory}
+ purpose [0..1] : CharacterString
+ pointOfContact [0..*] : CI_ResponsibleParty
+ status [0..*] : MD_ProgressCode
+ spatialRepresentationType [0..*] : MD_SpatialRepresentationTypeCode
+ spatialResolution [0..*] : MD_Resolution EX_GeographicDescription
+ geographicIdentifier : MD_Identifier
+ language [1..*] : CharacterString
+ topicCategory [1..*] : MD_TopicCategoryCode
+ characterSet [0..1] : MD_CharacterSetCode = "utf8"
or both
EX_GeographicBoundingBox
+ geographicDescription [0..*] : EX_GeographicDescription
+ westBoundLongitude : Decimal
+ geographicBox [0..*] : EX_GeographicBoundingBox
+ eastBoundLongitude : Decimal
+ environmentDescription [0..1] : CharacterString
+ extent [0..*] : EX_Extent + southBoundLatitude : Decimal
+ supplementalInformation [0..1] : CharacterString + northBoundLatitude : Decimal
UC 2007 Tech Sessions 14
ISO 19115:2003 Annex A
Extent data types
>
EX_Extent
+ description[0..1] : CharacterString
count(description +
+geographicElement geographicElement +
temporalElement +
0..* verticalElement) >0
>
EX_GeographicExtent +temporalElement
+ extentTypeCode [0..1] : Boolean = "1"
0..*
EX_TemporalExtent
+spatialExtent + extent : TM_Primitive
1..*
+verticalElement
0..*
EX_VerticalExtent
+ minimumValue : Real
+ maximumValue : Real
EX_BoundingPolygon
+ polygon[1..*] : GM_Object
EX_SpatialTemporalExtent
EX_GeographicBoundingBox +verticalCRS
+ westBoundLongitude : Decimal
1
+ eastBoundLongitude : Decimal EX_GeographicDescription
+ southBoundLatitude : Decimal + geographicIdentifier : MD_Identifier >
+ northBoundLatitude : Decimal
SC_CRS
(from Spatial Referencing by Coordinates)
UC 2007 Tech Sessions 15
DataIdentification details characterSet: documented if ISO 10646-1
is not used
{MD_Metadata.hierarchyLevel = "dataset"
implies count (extent.geographicElement.
EX_GeographicBoundingBox) + count
(extent.geographicElement.EX_GeographicDe
scription >=1}
MD_DataIdentification {MD_Metadata.hierarchyLevel notEqual
“dataset” or “series” implies topicCatagory
is not mandatory}
+ abstract : CharacterString
>
+ citation : CI_Citation
+ credit [0..*] : CharacterString
MD_TopicCategoryCode
+ farming
+ purpose [0..1] : CharacterString
+ biota
+ pointOfContact [0..*] : CI_ResponsibleParty + boundaries
+ status [0..*] : MD_ProgressCode + climatologyMeterologyAtmosphere
+ spatialRepresentationType [0..*] : MD_SpatialRepresentationTypeCode + economy
+ elevation
+ spatialResolution [0..*] : MD_Resolution + environment
+ language [1..*] : CharacterString + geoscientificInformation
+ topicCategory [1..*] : MD_TopicCategoryCode + health
+ characterSet [0..1] : MD_CharacterSetCode = "utf8" + imageryBaseMapsEarthCover
+ intelligenceMilitary
+ geographicDescription [0..*] : EX_GeographicDescription + inlandWaters
+ geographicBox [0..*] : EX_GeographicBoundingBox + location
+ environmentDescription [0..1] : CharacterString + oceans
+ extent [0..*] : EX_Extent
+ planningCadastre
+ society
+ supplementalInformation [0..1] : CharacterString + structure
+ transportation
+ utilitiesCommunications
UC 2007 Tech Sessions 16
MD_TopicCategoryCode
1. farming 10. imageryBaseMapsEarth
2. biota Cover
3. boundaries 11. intelligenceMilitary
4. climatologyMeteorology 12. inlandWaters
Atmosphere 13. location
5. economy 14. oceans
6. elevation 15. planningCadastre
7. environment 16. society
8. geoscientificInformation 17. structure
9. health 18. transportation
19. utilitiesCommunication
UC 2007 Tech Sessions 17
climatologyMeteorology 004 processes and phenomena of the atmosphere
Atmosphere Examples: cloud cover, weather, climate, atmospheric
conditions, climate change, precipitation
economy 005 economic activities, conditions and employment
Examples: production, labour, revenue, commerce,
industry, tourism and ecotourism, forestry, fisheries,
commercial or subsistence hunting, exploration and
exploitation of resources such as minerals, oil and gas
elevation 006 height above or below sea level
Examples: altitude, bathymetry, digital elevation models,
slope, derived products
environment 007 environmental resources, protection and conservation
Examples: environmental pollution, waste storage and
treatment, environmental impact assessment, monitoring
environmental risk, nature reserves, landscape
geoscientificInformation 008 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 009 health, health services, human ecology, and safety
Examples: disease and illness, factors affecting health,
hygiene, substance abuse, mental and physical health,
health services
imageryBaseMapsEarth 010 base maps UC 2007 Tech Sessions 18
ISO 19115:2003
Metadata applications
GF_FeatureType
DS_DataSet 0..*
MD_Metadata FE_Feature
1..* 0..*
1..* 0..*
1..*
0..* 0..* GF_PropertyType
0..* 0..*
>
DS_Aggregate
FE_FeatureAttribute
0..*
0..*
DS_Series DS_Initiative
DS_Platform DS_Sensor DS_ProductionSeries
UC 2007 Tech Sessions 19
ISO 19115:2003
Metadata applications
Dataset
GF_FeatureType
Metadata 0..*
0..* FE_Feature
1..* 1..* 0..*
1..*
0..* 0..*
0..* 0..*
GF_PropertyType
>
DS_Aggregate 0..*
0..*
FE_FeatureAttribute
DS_Series or
DS_Initiative
or DS_Sensor or
DS_ProductionSeries XYZ Points
DS_Platform 3-D Features
Contours
DTM‟s
LIDAR UC 2007 Tech Sessions 20
ISO 19115:2003
Metadata applications
Dataset
GF_FeatureType
Metadata 0..*
0..* FE_Feature
1..* 1..* 0..*
1..*
0..* 0..*
0..* 0..*
GF_PropertyType
>
DS_Aggregate 0..*
0..*
FE_FeatureAttribute
DS_Series or Study,
DS_Initiative
or Collection…
DS_Sensor or
DS_ProductionSeries XYZ Points
DS_Platform 3-D Features
Contours
DTM‟s
LIDAR UC 2007 Tech Sessions 21
ISO 19115 recommended core
This list contains metadata elements answering the following questions:
“Does a dataset on a specific topic exist („what‟)?”, “For a specific place
(„where‟)?”, “For a specific date or period („when‟)?” and “A point of
contact to learn more about or order the dataset („who‟)?”.
Dataset title – Additional extent information
Dataset reference date (vertical and temporal)
─ Dataset responsible party – Spatial representation type
Geographic location of the – Reference system
dataset (by four coordinates or – Lineage statement
by geographic identifiers) – On-line resource
Dataset language – Metadata file identifier
Dataset character set – Metadata standard name
Dataset topic category – Metadata standard version
– Spatial Resolution Metadata language
Abstract describing the Metadata character set
dataset Metadata point of contact
– Distribution format Metadata time stamp
Mandatory Automated UC 2007 Tech Sessions 22
Dublin Core elements
1. Title
2. Creator
3. Subject (and keywords/topic)
4. Description (abstract)
5. Publisher (responsible for making resource available
6. Contributor
7. Date (date of event in life cycle - creation, availability)
8. Type (nature or genre) dataset, image, event…
9. Format
10.Identifier
11.Source
12.Language
13.Relation
14.Coverage
15.Rights “All optional”
UC 2007 Tech Sessions 23
Dublin Core / ISO 19115 Core Compared
Dataset title
─ Dataset responsible party (originator)
Dataset topic category
Abstract describing the dataset From ISO 19115
─ Dataset responsible party (publisher) outside core
Contributor Credit
Dataset reference date
– Spatial representation type
– Distribution format
Identifier DataSetURI/On-lineResource
– Lineage statement
Dataset language
Relation AggregateInfo
Geographic location of the dataset (by four coordinates or by
geographic identifiers)
Rights MD_Contraints
UC 2007 Tech Sessions 24
Remaining ISO 19115 Core
–Spatial Resolution
–Additional extent information (vertical and
temporal)
–Reference system
–Metadata standard name
–Metadata standard version
Metadata language
Metadata character set
Metadata point of contact
UC 2007 Tech Sessions 25
ESRI Metadata
Metadata elements not typically included within
dataset/services metadata records
Metadata element Example
Published Document ID {C52B9923-6D4F-D123-
9F70-F511E2452AA9}
–Metadata file identifier
Input Source 0
Where the metadata came
Modification Date 20060901
from – harvested, on-line,
Modification Time 01092800
etc
(issecured) false Metadata time stamp
(resourceType) 005
MD_Constraints
On-lineResource.description
UC 2007 Tech Sessions 26
ESRI Metadata
Metadata elements not typically included within
dataset/services metadata records
Publication Source
0 Harvester
1 Resource Type
Geography Network
Metadata element Example
001 2 Live Data and Maps (service)
GeoCommunicatior
002 3 Downloadable Data
ArcCatalog
Published Document ID {C52B9923-6D4F-D123-
003 4 Offline Data
On-line Form
9F70-F511E2452AA9}
004 5 Static Map Images
XML Upload
005 Document, Other Documents
006 Applications
Input Source 0
007 Geographic Services
Modification Date 20060901 008 Clearinghouses
009 Map Files
Modification Time 01092800
010 Geographic Activities
(issecured) false
(resourceType) 005
UC 2007 Tech Sessions 27
ISO 19115:2003
• Designed:
–to support geographic information;
–to work with wider information technology standards and
practices;
–to support locate, evaluate, extract, employ
–to support datasets, series, features, attributes…
–to serve the global community, in a multi-national, multi-
language environment;
–based on a foundation of national, regional, and special
information community standards and experiences
• Developed through a rigorous, consensus ISO process
• Provides a foundation for national, regional, and global
interoperability
Semantic Interoperability UC 2007 Tech Sessions 28
News flash
+
http://www.iso.org/iso/en/CatalogueListPage.CatalogueList
UC 2007 Tech Sessions 29
Corrigendum summary
• Corrects numerous spelling mistakes
• Clarifies language (sentences)
• Removes CRS and projection parameter
information (use new ISO 19111)
RS_Identifier still used to identify CRS used
by a dataset
• Corrects Bounding Box coordinates datatype
(from “angle” to “decimal”)
• Suggestion: redline your copy of original ISO
19115:2003
UC 2007 Tech Sessions 30
XML Implementation ISO 19139
UC 2007 Tech Sessions 31
ISO 19139
Geographic Information - Metadata
XML Schema Implementation
• Defines geographic metadata XML encoding (gmd)
• Uses ISO 19118 rules to produce ISO 19139 XML from ISO
19115 UML Schema
• Identification of additional 19100 entities
– 19103, 7, 8, 9, 18
• gmd XML encoding rules
• Takes advantage of GML and other XML encodings
• Clauses defining
– Cultural and linguistic support
• multiple languages, etc
– Metadata for transfer
– Dataset and Aggregate dataset metadata
– Codelists
Technical Interoperability UC 2007 Tech Sessions 32
Multi-lingual support
Encoding semantic interoperability
Enhancing free text information
Use Limitations: (a free text field)
Language: eng
Country: United Kingdom
Character Set: ISO/IEC 8859-1
Text: Weight restriction on bridges Lorries exceeding five
metric tonnes gross weight are not permitted on bridges
Language: fra
Country: Canada
Character set: ISO/IEC 8859-15
Text: Limitation de poids sur les ponts: Les camions dont
le poids total excède 5 tonnes métriques ne sont pas
autorisés à circuler sur les ponts.
UC 2007 Tech Sessions 33
Controlled vocabulary
using code lists
administrative area:
lang: (sp) Metrapltona (free text, miss-spelled)
lang: (en) Metropolitan
administrative area:
Better yet Codelist: http://mycodeLists.cl/adminAreas
CodelistValue: Metropolitana
CodeAlternativeExpression: 6
Administrative area Code List
1. Región de Tarapacá
2. Región de Antofagasta
3. Región de Atacama
http://mycodeList.cl/adminAreas 4. Región de Coquimbo
5. Región de Valparaiso
6. Región de Metropolitana
7. …
UC 2007 Tech Sessions 34
Originator Date Location
Altitude
Obliqueness
Identifiers
Time
Focal length
Aerial Photos
UC 2007 Tech Sessions 35
Other ISO TC 211 Standards of interest to ESIP
ISO 19130
Imagery sensor models for
geopositioning* ISO 19115:2003
Platform and Metadata
Sensor Description
Part 2
Extensions for imagery
ISO 19129 Framework and gridded data
Framework for imagery Requirements
and gridded data ISO Geospatial Metadata
Life-cycle
ISO 19101-2
Description
Imagery reference
model
UC 2007 Tech Sessions 36
ISO 19115-2 Geographic Information – Metadata – Part 2 Extensions for
Imagery and Gridded Data
• Scope
–This International Standard extends ISO 19115:2003
Geographic Information – Metadata
• defining the schema and additional metadata required for imagery and
gridded data
• Objective
– Augment existing ISO 19115:2003 standard - define the content and structure
required to:
• Describe geographic imagery and gridded data
• Support the collection of natural and synthetic imagery and gridded data
• Support exploitation of imagery and gridded data
UC 2007 Tech Sessions 37
Extended UML for imagery and gridded data
If(count(source) + count(processStep) =0) and
DQ_DataQuality
(DQ_DataQuality.scope.level = 'dataset' or 'series') then
(f rom Data quality inf ormation)
statement is mandatory
+ scope : DQ_Scope
"source" role is mandatory if
LI_Lineage.statement and "processStep"
+lineage role are not documented
0..1
LI_Lineage "processStep" role is mandatory if
(f rom Data quality inf ormation)
LI_Lineage.statement and "source" role are
+ statement[0..1] : CharacterString not documented
+processStep
+source 0..*
0..*
LI_Source
(f rom Data quality inf ormation) LI_ProcessStep
+ description[0..1] : CharacterString (f rom Data quality inf ormation)
+source
+ scaleDenominator[0..1] : MD_RepresentativeFraction + description : CharacterString
0..*
+ sourceReferenceSystem[0..1] : MD_ReferenceSystem + rationale[0..1] : CharacterString
+ sourceCitation[0..1] : CI_Citation 0..* + dateTime[0..1] : DateTime
+ sourceExtent[0..*] : EX_Extent +sourceStep + processor[0..*] : CI_ResponsibleParty
LE_Processing
+ identifier : MD_Identifier
+ softwareReference [0..*] : CI_Citation
"description" is mandatory if "sourceExtent" is not
documented +processingInformation + procedureDescription[0..1] : CharacterString
LE_ProcessStep + documentation[0..*] : CI_Citation
+ runTimeParameters[0..1] : CharacterString
"sourceExtent" is mandatory if "description" is not 0..1
documented
LE_Source +output
+ processedLevel[0..1] : MD_Identifier
+ resolution[0..1] : LE_NominalResolution 0..*
+report
+algorithm
0..*
0..*
If "LE_NominalResolution.scanningResolution" is used
LE_ProcessStepReport LE_Algorithm
then "LE_Source.scaleDenominator" is required
+ name : CharacterString + citation : CI_Citation
+ description[0..1] : CharacterString + description : CharacterString
> + fileType[0..1] : CharacterString
LE_NominalResolution
+ scanningResolution : Distance
+ groundResolution : Distance
UC 2007 Tech Sessions 38
Acquisition Information Package
MI_Platform
MI_Metadata MI_Plan
+ citation[0..1] : CI_Citation (from Metadata Entity Set - Imagery)
+ type[0..1] : MI_GeometryTypeCode
+ identifier : MD_Identifier
+ status : MD_ProgressCode
+ description : CharacterString
+ citation : CI_Citation
+ sponsor[0..*] : CI_ResponsibleParty
+acquisitionPlan
+platform
0..*
0..*
+acquisitionInformation
0..*
MI_AcquisitionInformation
+instrument +operation
0..*
0..*
MI_Operation
MI_Instrument
+ description[0..1] : CharacterString
+ citation : CI_Citation
+ citation : CI_Citation
+ type : MI_SensorTypeCode
+ status : MD_ProgressCode
+ description [0..1] : CharacterString
+acquisitionRequirement
0..*
+objective MI_Requirement
0..* + citation : CI_Citation
+ identifier : MD_Identifier
MI_Objective + requestor [1..*] : CI_ResponsibleParty
+ identifier : MD_Identifier + recipient [1..*] : CI_ResponsibleParty
+ priority[0..1] : CharacterString + priority : MI_PriorityCode
+ type[0..*] : MI_ObjectiveTypeCode + requestedDate : MI_RequestedDate
+ function[0..*] : CharacterString + expiryDate : DateTime
+ extent[0..*] : EX_Extent
UC 2007 Tech Sessions 40
Acquisition Information Package details
MI_Requirement
> >
+ citation : CI_Citation
MI_RequestedDate MI_TriggerCode
+ identifier : MD_Identifier
+ requestor [1..*] : CI_ResponsibleParty + requestedDateOfCollection : DateTime + automatic
+ recipient [1..*] : CI_ResponsibleParty + latestAcceptableDate : DateTime + manual
+ priority : MI_PriorityCode + preProgrammed
+ requestedDate : MI_RequestedDate
+ expiryDate : DateTime
>
+satisfiedRequirement MD_ProgressCode
0..* (f rom Identif ication inf ormation) >
> MI_ContextCode
+ completed
MI_PriorityCode > + historicalArchive + acquisition
+ critical +satisfiedPlan MI_GeometryTypeCode + obsolete + pass
+ highImportance 0..* + point + onGoing + wayPoint
+ mediumImportance + linear + planned
MI_Plan
+ lowImportance + areal + required
+ type[0..1] : MI_GeometryTypeCode
+ strip + underDevelopment
+ status : MD_ProgressCode
+ citation : CI_Citation
>
+plan MI_SequenceCode
>
0..1 + start
MI_OperationTypeCode
+ end
+ real + instantaneous
+childOperation + simulated
+ synthetic
0..* +operation MI_Event
0..* + identifier : MD_Identifier
MI_Operation +significantEvent + trigger : MI_TriggerCode
+parentOperation + context : MI_ContextCode
+ description[0..1] : CharacterString +objectiveOccurence
1 + citation : CI_Citation 0..* + sequence : MI_SequenceCode
+ status : MD_ProgressCode + time : DateTime 1..*
+ type [0..1] : MI_OperationTypeCode
> +relatedEvent
MI_SensorTypeCode
0..*
+ framing
+ lineScan
+ pushBroom
>
+ panFrame
MI_ObjectiveTypeCode +relatedPass
+ stepFrame
+ instantaneousCollection 0..1
+ radar
+ virtualRadar + persistentView MI_PlatformPass
+ mti + survey
+ identifier : MD_Identifier
+ multiModeRadar + extent [0..1] : GM_Object
+platform
0..* +pass
+objective
0..*
MI_Platform 0..*
+ citation[0..1] : CI_Citation
+ identifier : MD_Identifier MI_Objective
+ description : CharacterString + identifier [1..*] : MD_Identifier
+ sponsor[0..*] : CI_ResponsibleParty + priority[0..1] : CharacterString
+ type[0..*] : MI_ObjectiveTypeCode
+ function[0..*] : CharacterString +expectedObjective
+mountedOn
0..1 + extent[0..*] : EX_Extent
0..*
+instrument
1..* +sensingInstrument
MI_Instrument
+ citation : CI_Citation 0..*
+ type : MI_SensorTypeCode +relatedSensor
+ description [0..1] : CharacterString
0..*
UC 2007 Tech Sessions 41
ISO 15115-2
Schedule
• Working Draft: 2003-09
• Committee Draft 2004-08
• CD2: 2005-11
• Approved to move to DIS: 2007-04
• Draft International Standard: 2007-08
• FDIS: 2008-06
• IS 2008-12
UC 2007 Tech Sessions 42
ISO 19130 Image sensor models for
geopositioning*
• Defines the geolocation information that the data provider must supply
in order for the user to be able to find the geographical location of the
data using a physical sensor model, true replacement model, or
functional fit methodology.
• Provides detailed sensor models and associated uncertainties for the
following types of passive electro-optical (EO)/ infrared (IR) sensors:
– frame,
– pushbroom
– whiskbroom.
– A set of components from which sensor models can be constructed for
other sensors.
• Defines the metadata to be distributed with the observation data to
enable user determination of geopositions from the observations,
*New name
UC 2007 Tech Sessions 43
Camera geometries
Sensor perspective centre
x
(L) y
s y
z s
Calibrated focal s
z a x
length
Positive image
PP
plane
A
ZL
Z
Y A Pushbroom collection geometry
X Z
XL Y
YL
X ys
xs
Instantaneous Perspective zs Image Vector
To Ground
Frame sensor image, Center (L),
Also Sensor Coordinate Point
Positive Image f a (A)
projection centre and exterior System (SCS)
Plane Z
orientation L
Z A
Y
ZGround Swath
X imaged at time
X Y t
L
Y
X
L
UC 2007 Tech Sessions 44
Camera coordinate systems
zs
SCS
ys
y Lens (optical) axis L
(perpendicular to the page)
CCS
x0 0 column (sample)
1
0 2…
Perspective centre
1 (x,y,z)s=(0,0,-f)
(xs,ys,zs)
2
x .
. t=3
row (line).
y0 (ℓ(t),s(t)) = (2,4)
Ny = 9
xs
Principal point
Frame camera
coordinate Pushbroom
system coordinate
system
UC 2007 Tech Sessions 45
Platform coordinate systems
North,
N
Heading,
H Xa
Pitch axis - XP
Z East, E East,
E
Ya
Yaw axis - ZP
Roll, R
Y
Center of Za Down,
Y Velocity vector
Navigation
a Xa
D
X Roll axis - YP Pitch,
P North,
N
Za
Down,
D
Satellite Platform Platform coordinate
coordinate system with reference system and local
respect to ECEF (NED) frame
UC 2007 Tech Sessions 46
Earth coordinate systems and orbit geometries
Z = Zi
Z
North
+t Pole
Up, ULocal ENU
Y
t=0 Coordinate
Z X Ellipsoid North, East, E
Frame
Y N
A
X
Earth
f
GreenwicCenter Y
Ω h
Meridian l
ωet Equator f Latitu
Yi
l de
Longitu
Satellite Ground Track de
X
Xi
Satellite Orbit
Global, Earth-centered and
local coordinate system
Keplerian Orbit
UC 2007 Tech Sessions 47
Sensor metadata
UC 2007 Tech Sessions 48
Location model
UC 2007 Tech Sessions 49
ISO 19130
Schedule
• NWIP approval: 2007-09
• Working Draft or Committee Draft?: 2007-12
• CD or DIS: 2008-06
• IS: 2009-01
UC 2007 Tech Sessions 50
North American Profile (NAP) ISO 19115 -
Metadata
The situation today:
Canada and USA
•Directory Information Describing
Digital Geo-referenced Data Sets,
Canadian General Standards Board,
July 1994, Ottawa.
•Content Standard for Digital
Geospatial Metadata, Federal
Geographic Data Committee, June 8,
1994, Washington DC.
UC 2007 Tech Sessions 51
The goal
CAN/CGSB 171.3-95 North American
Profile
Geospatial
Metadata
Based on ISO
USA CSDGM 19115/19139
UC 2007 Tech Sessions 52
Co-located Meetings
Parallel Development
North MOU between North
American American
Profile of Canada and Profile of
ISO 19115 the USA ISO 19115
Metadata Metadata
UC 2007 Tech Sessions 53
Participants
Canada USA
• Natural Resources • Federal Geographic
Canada Data Committee
• Ontario Ministry of –NPS, USGS (BRD,
Geography, Geology),
Natural Resources NJ, BLM, Nature
• CGSB-CoG Serve, NOAA
–members • INCITS-L1
–members
NAP Metadata
Working Group Potential Mexican
involvement
UC 2007 Tech Sessions 54
Approach
• Requirements analysis
–Past experience with metadata standards
implementation
• Cross-table development (FGDC-ISO 19115)
• Modified UML
• Add capabilities provided by ISO/TS 19139
UC 2007 Tech Sessions 55
North American Profile of ISO 19115:2003 Metadata (NAP - Metadata)
• Selection of items from ISO19115:2003
• Promotion of optional fields to mandatory
• Extension of code lists
–Addition of values to existing code lists
–Addition of code lists
• Introduction of a multilingual register
–Compliant to ISO19135:2005 on registers
–English and/et Français (and potentially Spanish)
–Metadata items
–Code lists
• Register will be accessible on the Web
–XML document
–Web Services
–Web Browser
UC 2007 Tech Sessions 56
Metadata profile content
Title: NAP – Metadata
1. Preface (Introduction)
1.1. About Metadata
1.2. Using Metadata
2. Scope
3. Normative References
4. Terms and Definitions
5. Symbols and Abbreviated Terms
6. Metadata Content
6.1. Best Practices
7. Cultural and Linguistic Adaptability
8. Code Lists
9. NAP Metadata Registry
Annexes
Data Types
Metadata schemas Differences/UML
(normative)
Conformance Clauses
Metadata implementation
FGDC to NAP Metadata
UC 2007 Tech Sessions 57
NAP Definitions
6.2.1.1 citation (M)
Type: CI_Citation (see 6.13)
+ citation (M) Identification Information
Description: Citation for the dataset. + abstract ( M)
MD_ Identification
+ purpose (O)
BP: The attribute citedResponsibleParty in + credit ( O, *)
AT T RI B UTE S
CI_Citation must be reported at least once. +
+
status ( M, *)
pointOfContact(O, *)
Contact information (see 6.14.4) of the cited + (
spatialRepresentationTypeO, *) Data Identification Service Identification
+ (
spatialResolution O, *) MD_DataIdentification and/or SV_ServiceIdentification
responsible party shall be provided even if it + language( M, *)
is an optional attribute in +
+
characterSet( M, *)
topicCategory(M, *)
CI_ResponsibleParty. + (
environmentDescriptionO)
+ extent (O, *) EX_ Extent
The date of the resource reported in the + (
supplementalInformationO, *)
citation (i.e. citation date, see 6.13.3)
corresponds to its last update version
according to its update frequency (see 6.5.1) (O
Resource Maintenance Information , *) (
Resource ConstraintsO, *)
and the date of next update (see 6.5.2) of its MD_ MaintenanceInformation MD_ Constraints
previous version.
6.2.1.2 abstract (M) (
Graphic Overview O, *)
MD_ BrowseGraphic
Legal Constraints
MD_ LegalConstraints
Type: free text
Description: Brief narrative summary of the (
Descriptive KeywordsO, *) Security Constraints
dataset’s contents. MD_ Keywords MD_ SecurityConstraints
BP: Abstract narrative should include (O
Resource Specific Usage , *) (
Aggregation InformationO, *)
information on general content and features; MD_ Usage MD_ AggregateInformation
dataset application: GIS, CAD, image, Dbase;
geographic coverage: county/city name; time
period of content: begin and end date or
single date; and special data characteristics
or limitations.
UC 2007 Tech Sessions 58
Schedule
• Initial draft document – Nov 2006
• Expert review – March 2007
• Submit to standards bodies – July 2007
• Approval late fall 2007
UC 2007 Tech Sessions 61
Summary
• Metadata is a basic element used to abstract reality
• Metadata completes the “picture” allowing us to fully understand the
information
• Metadata provides a handle used for discovery
• ISO 19115 provides internationally standardized metadata elements
and a schema – semantic interoperability
• ISO 19139 provides an XML Schema encoding for metadata –
technical interoperability
• ISO 19115-2 will extend the schema for imagery and gridded data
• ISO 19130 standardizes sensor model descriptions, provides imagery
metadata supporting geopositioning
• North American Profile of ISO 19115 will soon replace the FGDC
Metadata standard providing international interoperability tailored for
North America
UC 2007 Tech Sessions 62