Overview of ISO 19100 Series ISO/TC211 ISO/TC211 Geographic information/Geomatics.
ISO/TC211 Geographic information/Geomatics Metadata David Danko Work Item 15 - Project Leader...
-
Upload
megan-mitchell -
Category
Documents
-
view
214 -
download
0
Transcript of ISO/TC211 Geographic information/Geomatics Metadata David Danko Work Item 15 - Project Leader...
ISO/TC211ISO/TC211Geographic information/GeomaticsGeographic information/Geomatics
MetadataMetadata
David DankoDavid Danko
Work Item 15 - Project LeaderWork Item 15 - Project Leader
[email protected]@esri.com
MetadataMetadataData about DataData about DataMetadataMetadata
Data about DataData about Data
• Geospatial data has a long Geospatial data has a long history using Metadatahistory using Metadata– Map catalogsMap catalogs
– Maps and ChartsMaps and Charts
– ImageryImagery
– Digital data filesDigital data files
Title
Symbols(Feature Codes)
Identification
Scale
Accuracy
Producer
Navigation notices Referencesystem
Sources
Warnings
Location
Date
Paper MapsPaper Maps
Metadata perspectivesMetadata perspectivesMetadata perspectivesMetadata perspectives• Why it’s more important now?Why it’s more important now?
– Expansion in the use of Geographic InformationExpansion in the use of Geographic Information– Proliferation of dataProliferation of data– Non-geographers using geospatial dataNon-geographers using geospatial data– The producer is not the userThe producer is not the user
– Geospatial data is imperfectGeospatial data is imperfect– A model, a “point of view”A model, a “point of view”– Assumptions, limitations, approximations, Assumptions, limitations, approximations,
simplificationssimplifications– Expensive Expensive
– ReuseReuse– Data managementData management
• Why should it be standardized?Why should it be standardized?– Provide an understanding of data – around the Globe Provide an understanding of data – around the Globe
and across information communitiesand across information communities
Metadata ApplicationsMetadata Applications To understand the right data for To understand the right data for
the right purposethe right purpose
Metadata ApplicationsMetadata Applications To understand the right data for To understand the right data for
the right purposethe right purpose • LocateLocate
– Find– Discover
• EvaluateEvaluate– Restrictions– Quality– Reputation
• ExtractExtract– Order
– Download
• EmployEmploy– Apply
– Use
The metadata The metadata environmentenvironment
The metadata The metadata environmentenvironment
Catalog Processing Support
Historical Record
Understand Data
Locate X X X
Evaluate X X X
Extract X X
Employ X X
EnvironmentApplication
Cataloging datasetsCataloging datasetsCataloging datasetsCataloging datasets
• Index of DatasetsIndex of Datasets• Product CatalogProduct Catalog
– PrintedPrinted– On-lineOn-line
• ClearinghouseClearinghouse– SearchingSearching– BrowsingBrowsing
• Data WarehouseData Warehouse– ManagementManagement
Locate Evaluate Extract
Federal Agency
Academic
State Agency
Local Agency
Private Company
Non-Profit Agency
?
?
?
?
?
?
ClientClient MetadataSpatialData Set
Pleasantville
Pleasantville
Pleasantville
Understanding dataUnderstanding dataUnderstanding dataUnderstanding data
• Understand the ModelUnderstand the Model– How features are representedHow features are represented– Connectivity Connectivity
• Understand the ContentUnderstand the Content– Why features are included or excludedWhy features are included or excluded
• Understand the Point-of-ViewUnderstand the Point-of-View– Business/CommercialBusiness/Commercial– Environmental/ScientificEnvironmental/Scientific– Military/Defense/IntelMilitary/Defense/Intel
Locate Evaluate Employ
Processing supportProcessing supportProcessing supportProcessing support
• Support user DecisionsSupport user Decisions– Identify multiple datasets within an Identify multiple datasets within an
applicationapplication– Know the good and bad areasKnow the good and bad areas– Merging data (which is the better data?)Merging data (which is the better data?)
– CurrentnessCurrentness– QualityQuality
• Support Computer ProcessingSupport Computer Processing– Application software functionsApplication software functions– Extraction/Creation (I/O)Extraction/Creation (I/O)– Guide software through the dataGuide software through the data
Extract Employ
Historical recordsHistorical recordsHistorical recordsHistorical records
• Production ManagementProduction Management– Storage/ArchivalStorage/Archival– Coordinating productionCoordinating production– Planning - setting prioritiesPlanning - setting priorities
• Legal RecordsLegal Records– Proper useProper use– Document assumptionsDocument assumptions
Locate Evaluate
ISO 19115:2003 MetadataISO 19115:2003 MetadataISO 19115:2003 MetadataISO 19115:2003 MetadataStage date: 2003-05-08
http://www.iso.org/iso/en/prods-services/ISOstore/store.html
ISO 19115:2003ISO 19115:2003
ScopeScope
ISO 19115:2003ISO 19115:2003
ScopeScope
• ...the ...the schema required for describing geographic informationschema required for describing geographic information and and servicesservices..
• ...information...information about the identification, the extent, the quality, the about the identification, the extent, the quality, the spatial and temporal schema, spatial reference, and distribution of spatial and temporal schema, spatial reference, and distribution of digital geographic datadigital geographic data..
• ...applicable...applicable to the to the cataloguingcataloguing of datasets, of datasets, clearinghouseclearinghouse activities, and the activities, and the full descriptionfull description of datasets for a of datasets for a wide range of wide range of geographic applicationsgeographic applications..
• ……applicableapplicable to geographic to geographic datasetsdatasets, dataset , dataset seriesseries, and , and individual individual geographicgeographic features features and and attributesattributes
• ......may be usedmay be used for other forms of geographic data such as for other forms of geographic data such as map, map, charts, textual documentscharts, textual documents
The ISO ProcessThe ISO ProcessThe ISO ProcessThe ISO Process• Formal ProcessFormal Process
–Refined over 50 yearsRefined over 50 years
–Stages and timelines fully definedStages and timelines fully defined
• Consensus basedConsensus based–Drafts considered until consensus Drafts considered until consensus
reached through voting process by reached through voting process by P- membersP- members
ISO metadata foundationISO metadata foundation• Regional metadata standardsRegional metadata standards
– ANZLIC Working Group on Metadata: Core Metadata Elements Guidelines Draft 7 , Australia and New Zealand Land Information Council, November 1995, Sydney.
– the Canadian Directory Information Describing Digital Geo-referenced Data Sets , Canadian General Standards Board, July 1994, Ottawa.
– Standard for Geographic Information - Metadata, European Committee for Standardisation (CEN), September 1996, Brussels.
– Content Standard for Geospatial Metadata Federal Geographic Data Committee, June 8, 1994, Washington DC
• Other influential documentsOther influential documents– Digital Geographic Information Exchange Standard (Digest), Version 1.2 . Digital Geographic
Information Working Group, January 1994, – IHO Transfer Standard for Digital Hydrographic Data, International Hydrographic Bureau, October
1995, Monaco– Spatial Data Transfer Standard (SDTS), US Department of Commerce, August 1992, Gaithersburg, MD– Application Profile for the Government Information Locator Service (GILS), US Department of
Commerce, December 1994, Gaithersburg, MD– Cartographic materials: A manual of interpretation for AACR2, Anglo-American Committee on
Cataloguing of Cartographic materials, 1982, Chicago– USMARC Format for Bibliographic Data, US Library of Congress, 1988, Washington, DC
ISO 19115:2003 ISO 19115:2003
Metadata applicationsMetadata applicationsISO 19115:2003 ISO 19115:2003
Metadata applicationsMetadata applications
MD_Metadata
<<Abstract>>DS_Aggregate
DS_DataSet
DS_OtherAssociation
DS_StereoMate
DS_Series DS_Initiative
GF_PropertyType
GF_FeatureType
FE_FeatureAttribute
FE_Feature
0..*
0..*
0..*
0..*
0..*
0..*
1..*
0..*
1..*
0..*
0..*
1..*
DS_Platform DS_Sensor DS_ProductionSeries
Metadata packagesMetadata packagesMetadata packagesMetadata packages
IdentificationInformationLocateLocate
Constraint Information
Maintenance Information
Data QualityInformation
19113,14
ContentInformation
19110, 21, 23, 24EvaluateEvaluate
DistributionInformation
ExtractExtractMetadataExtension
Information
ReferenceSystem
Information
19108, 11, 12
SpatialRepresentation
Information
19107
PortrayalCatalogue
Information
19117
ApplicationSchema
Information
19109EmployEmploy
Developed to fulfill primary metadata applications
ISO 19115: 2003 ISO 19115: 2003
Metadata schema object modelsMetadata schema object modelsISO 19115: 2003 ISO 19115: 2003
Metadata schema object modelsMetadata schema object models
MD_KeywordTypeCode
+ discipline+ place+ stratum+ temporal+ theme
<<CodeList>>
MD_TopicCategoryCode
+ farming+ biota+ boundaries+ climatologyMeterologyAtmosphere+ economy+ elevation+ environment+ geoscientificInformation+ health+ imageryBaseMapsEarthCover+ intelligenceMilitary+ inlandWaters+ location+ oceans+ planningCadastre+ society+ structure+ transportation+ utilitiesCommunications
<<CodeList>>
MD_ProgressCode
+ completed+ historicalArchive+ obsolete+ onGoing+ planned+ required+ underDevelopment
<<CodeList>>
MD_Format(from Distribution information)
MD_Usage+ specificUsage : CharacterString+ usageDateTime[0..1] : DateTime+ userDeterminedLimitations[0..1] : CharacterString+ userContactInfo [1..*] : CI_ResponsibleParty
MD_MaintenanceInformation(from Maintenance information)
MD_Metadata(from Metadata entity set information)
MD_Keywords+ keyword[1..*] : CharacterString+ type [0..1] : MD_KeywordTypeCode+ thesaurusName[0..1] : CI_Citation
MD_Constraints(from Constraint information)
MD_Identification+ citation : CI_Citation+ abstract : CharacterString+ purpose [0..1] : CharacterString+ credit [0..*] : CharacterString+ status [0..*] : MD_ProgressCode+ pointOfContact [0..*] : CI_ResponsibleParty
<<Abstract>>
0..*
+resourceFormat
0..*
0..*+resourceSpecificUsage
0..*
0..*+resourceMaintenance
0..*
1..*+identificationInfo
1..*
0..*
+descriptiveKeywords
0..*
0..*+resourceConstraints 0..*
MD_BrowseGraphic+ fileName : CharacterString+ fileDescription[0..1] : CharacterString+ fileType[0..1] : CharacterString 0..*
+graphicOverview
0..*
MD_Resolution
+ equivalentScale : MD_RepresentativeFraction+ distance : Distance
<<Union>>
MD_CharacterSetCode
+ ucs2+ ucs4+ utf8+ utf16+ isoIec8859oneTo15+ jis+ shiftJIS+ eucJP
<<CodeList>>
MD_DataIdentification+ spatialRepresentationType [0..*] : MD_SpatialRepresentationTypeCode+ spatialResolution [0..*] : MD_Resolution+ language [1..*] : CharacterString+ characterSet [0..1] : MD_CharacterSetCode = "utf8"+ topicCategory [1..*] : MD_TopicCategoryCode+ geographicBox [0..*] : EX_GeographicBoundingBox+ geographicDescription [0..*] : EX_GeographicDescription+ environmentDescription [0..1] : CharacterString+ extent [0..*] : EX_Extent+ supplementalInformation [0..1] : CharacterString
MD_ServiceIdentification
MD_RepresentativeFraction
/+ denominator : Integer
<<DataType>>
Scale(from Units of Measure)
/ScaleWhere MD_RepresentativeFraction.denominator = 1/Scale.measure And Scale.targetUnits = Scale.sourceUnits
characterSet: documented if ISO 10646-1 is not used
{MD_Metadata.hierarchyLevelCode = "dataset" implies count (geographicBox) + count (geographicDescription) >=1}
MD_SpatialRepresentationTypeCode
+ vector+ grid+ textTable+ TIN+ stereoModel+ video
<<CodeList>>
Citation data typesCitation data typesCitation data typesCitation data types
CI_Telephone+ voice [0..*] : CharacterString+ facsimile [0..*] : CharacterString
<<DataType>>
CI_Address+ deliveryPoint [0..*] : CharacterString+ city [0..1] : CharacterString+ administrativeArea [0..1] : CharacterString+ postalCode [0..1] : CharacterString+ country [0..1] : CharacterString+ electronicMailAddress[0..*] : CharacterString
<<DataType>>
CI_OnlineResource+ linkage : URL
+ protocol [0..1] : CharacterString+ applicationProfile [0..1] : CharacterString+ name [0..1] : CharacterString+ description [0..1] : CharacterString+ function [0..1] : CI_OnLineFunctionCode
<<DataType>>
CI_PresentationFormCode+ documentDigital+ documentHardcopy+ imageDigital+ mapDigital+ mapHardcopy+ modelDigital+ modelHardcopy+ profileDigital+ profileHardcopy+ tableDigital+ tableHardcopy+ videoDigital+ videoHardcopy
<<CodeList>>
CI_Citation+ title : CharacterString+ alternateTitle [0..*] : CharacterString+ date [1..*] : CI_Date
+ edition [0..1] : CharacterString+ editionDate [0..1] : Date+ identifier [0..*] : CharacterString+ identifierType [0..*] : CharacterString+ citedResponsibleParty [0..*] : CI_ResponsibleParty+ presentationForm [0..*] : CI_PresentationFormCode+ series [0..1] : CI_Series
+ otherCitationDetails [0..1] : CharacterString+ collectiveTitle[0..1] : CharacterString+ ISBN[0..1] : CharacterString+ ISSN[0..1] : CharacterString
<<DataType>>
CI_OnLineFunctionCode
+ download+ information
+ offlineAccess+ order+ search
<<CodeList>>
URL
CI_Contact+ phone [0..1] : CI_Telephone+ address [0..1] : CI_Address
+ onlineResource [0..1] : CI_OnlineResource+ hoursOfService [0..1] : CharacterString+ contactInstructions [0..1] : CharacterString
<<DataType>>
CI_RoleCode+ resourceProvider+ custodian+ owner+ user+ distributor+ originator+ pointOfContact+ principalInvestigator+ processor+ publisher
<<CodeList>>
CI_ResponsibleParty+ individualName[0..1] : CharacterString+ organisationName[0..1] : CharacterString+ positionName[0..1] : CharacterString+ contactInfo [0..1] : CI_Contact+ role : CI_RoleCode
<<DataType>> count of (individualName + organisationName + positionName) > 0
CI_Date+ date : Date
+ dateType : CI_DateTypeCode
<<DataType>>
CI_DateTypeCode+ creation+ publication+ revision
<<CodeList>>
CI_Series+ name [0..1] : CharacterString+ issueIdentification [0..1] : CharacterString+ page [0..1] : CharacterString
<<DataType>>
Extent data typesExtent data typesExtent data typesExtent data types
EX_BoundingPolygon+ polygon[1..*] : GM_Object
EX_GeographicBoundingBox+ westBoundLongitude : Angle+ eastBoundLongitude : Angle+ southBoundLatitude : Angle+ northBoundLatitude : Angle
count(description + geographicElement + temporalElement + verticalElement) >0
SC_VerticalDatum(from Spatial Referencing by Coordinates)
EX_TemporalExtent+ extent : TM_Primitive
EX_VerticalExtent+ minimumValue : Real+ maximumValue : Real+ unitOfMeasure : UomLength
1
+verticalDatum
1
EX_SpatialTemporalExtent
EX_Extent+ description[0..1] : CharacterString
<<DataType>>
0..*
+temporalElement
0..*
0..*
+verticalElement
0..*
EX_GeographicExtent+ extentTypeCode [0..1] : Boolean = "1"
<<Abstract>>
1..*
+spatialExtent
1..*
0..*
+geographicElement
0..*
EX_GeographicDescription+ geographicIdentifier : MD_Identifier
CodeListsCodeListsCodeListsCodeLists<<CodeList>><<CodeList>>
MD_ProgressCodeMD_ProgressCode+ completedcompleted+ historicalArchivehistoricalArchive+ obsoleteobsolete+ onGoingonGoing+ plannedplanned+ requiredrequired+ underDevelopmentunderDevelopment
Name DomainCode DefinitionMD_ProgressCode ProgCode status of the resourcecompleted 001 production has been completedhistoricalArchive 002 data has been stored offlineobsolete 003 data is no longer relevantonGoing 004 data is continuously being ...planned 005 fixed date has been established…required 006 data needs to be generated or ...underDevelopment 007 data is currently in the process...
Why codelistsWhy codelistsWhy codelistsWhy codelists
• Suggested items (pick lists)Suggested items (pick lists)
• Searchable (common Searchable (common representation)representation)
• Registered definition (dictionary)Registered definition (dictionary)
• Multi-lingualMulti-lingual
ISO 19115: 2003 ISO 19115: 2003
Metadata data dictionaryMetadata data dictionaryISO 19115: 2003 ISO 19115: 2003
Metadata data dictionaryMetadata data dictionaryName/RoleName
ShortName
Definition Obligation/Condition
Maximumoccurrence
Data type Domain
29 MD_Identification
ident basicinformationrequired touniquely identifya resource
Useobligation
fromreferencing
object
Usemaximumoccurrence
forreferencing
object
AggregatedClass(MD_Metadata)<<Abstract>>
Lines 30-41
30 citation idCitation citation data forthe resource
M 1 Class CI_Citation<<DataType>>(B3.2)
31 abstract idAbs brief narratiavesummary
M 1 CharacterString Free text
32 purpose idPurp summary of theintentions withwhich theresource wasdeveloped
O 1 CharacterString Free text
33 credit idCredit recognition ofthose whocontributed tothe resource
O 1 CharacterString Free text
34 statusCode idStatCode status ofresource
O N Class MD_ProgressCode<<CodeList>>(B.6.26)
Recommended core metadata for Recommended core metadata for geographic datasetsgeographic datasets
Recommended core metadata for Recommended core metadata for geographic datasetsgeographic datasets
Dataset titleDataset title Dataset reference dateDataset reference date Dataset responsible partyDataset responsible party Geographic location of Geographic location of
the dataset the dataset (by four (by four coordinates or by geographic coordinates or by geographic identifiers)identifiers)
Dataset languageDataset language Dataset character setDataset character set Dataset topic categoryDataset topic category– Spatial ResolutionSpatial Resolution Abstract describing the Abstract describing the
datasetdataset– Distribution formatDistribution format
– Additional extent information Additional extent information (vertical and temporal)(vertical and temporal)
– Spatial representation typeSpatial representation type– Reference systemReference system– Lineage statementLineage statement– On-line resourceOn-line resource– Metadata file identifierMetadata file identifier– Metadata standard nameMetadata standard name– Metadata standard versionMetadata standard version Metadata languageMetadata language Metadata character setMetadata character set Metadata point of contactMetadata point of contact Metadata time stampMetadata time stamp
Mandatory
ISO 19115:2003 Annex EISO 19115:2003 Annex EComprehensive dataset Comprehensive dataset
metadata application schemametadata application schema
ISO 19115:2003 Annex EISO 19115:2003 Annex EComprehensive dataset Comprehensive dataset
metadata application schemametadata application schema
MD_LegalConstraints(fr om Constraint informat ion)
MD_SecurityConstraints(fr om Const raint inf ormation)
MD_CRS(fr om Reference system inform ation)
MD_VectorSpatialRepresentation(from Spatial representation informat ion)
MD_RasterDescription(f rom Content inform ation)
MD_RasterSpatialRepresentation(from Spatial representation informat ion)
MD_FeatureCatalogueDescription(fr om Cont ent informat ion)
DS_DataSet(from M etadat a app licati on in fo rmati on )
MD_SpatialRepresentation(f rom Spatial r epr esent ation inf or mation)
<<Abstract>>
MD_ContentDescription(f rom Content infor mation)
MD_Distribution(from Distribution inf ormation)
MD_MetadataExtensionInformation(f rom Met adat a extension infor mation)
MD_ApplicationSchemaInfo(from Applicat ion schema infor mation)
MD_MaintenanceInformation(fr om Maintenance inf or mation)
MD_Constraints( from Constraint infor mation)
MD_PortrayalCatalogueReference( from Port rayal cat alogue informat ion)
DQ_DataQuality(f rom DataQualit y)
MD_DataIdentification(fr om Identification inf ormation)
MD_Metadata( from Metadata entity set inf ormation)
1..*
1..*
+has1..*
+applies
1..*
0 ..*+spatialRepresentationInfo
0..*
0..*+contentInformation0..*
0..1
+distributionInfo
0..1
0..*+metadataExtensionInfo 0..*
0..*
+applicationSchemaInfo
0..*
0..1
+metadataMaintenance
0..1
0..*
+metadataConstraints
0..*
0..*
+portrayalCatalogueInfo
0..*
0..*
+dataQualityInfo
0..*
1..*
+dataIdentificationInfo
1..*
MD_ReferenceSystem(fr om Ref erence system inform ation)
0..*+referenceSystemInfo 0..*
ISO 19115:2003 Annex EISO 19115:2003 Annex E
Comprehensive datasetComprehensive datasetmetadata profilemetadata profile
ISO 19115:2003 Annex EISO 19115:2003 Annex E
Comprehensive datasetComprehensive datasetmetadata profilemetadata profile
• Comprehensive metadata Comprehensive metadata application schema (UML model)application schema (UML model)
– Implementation profileImplementation profile
–Applicable to a broad range of Applicable to a broad range of information communitiesinformation communities
–Complete range of metadata Complete range of metadata
ISO 19115:2003ISO 19115:2003ISO 19115:2003ISO 19115:2003• Designed:Designed:
– to support geographic information;to support geographic information;– to work with wider information technology standards to work with wider information technology standards
and practices;and practices;– to serve the global community, in a multi-national, to serve the global community, in a multi-national,
multi-language environment;multi-language environment;– based on a foundation of national, regional, and based on a foundation of national, regional, and
special information community standards and special information community standards and experiencesexperiences
• Developed through a rigorous, consensus ISO processDeveloped through a rigorous, consensus ISO process
Resolution 226 - Proceeding of ISO DIS 19115 Metadata
Resolution 226 - Proceeding of ISO DIS 19115 Metadata
• ISO/TC 211 resolves to ISO/TC 211 resolves to delete delete the informative annex F, clause J.3 the informative annex F, clause J.3 and any references to these, in ISO DIS 19115, as requirements for and any references to these, in ISO DIS 19115, as requirements for XML XML DTDDTDs are replaced by requirements for XML schemas in s are replaced by requirements for XML schemas in 19118. 19118.
• ISO/TC 211 instructs the secretariat to process the corrections ISO/TC 211 instructs the secretariat to process the corrections above and other above and other editorial and minor technical improvementseditorial and minor technical improvements in in accordance with the ISO Directives, and to accordance with the ISO Directives, and to forward ISO DIS 19115forward ISO DIS 19115 to the ISO Central Secretariat for issuing to the ISO Central Secretariat for issuing as FDISas FDIS..
• ISO/TC 211 resolves that an implementation UML model and an ISO/TC 211 resolves that an implementation UML model and an XML Schema for metadata in compliance with ISO 19115 and 19118 XML Schema for metadata in compliance with ISO 19115 and 19118 will be a will be a new work item proposal for a Technical Specificationnew work item proposal for a Technical Specification. . Based on discussions at the 14Based on discussions at the 14thth ISO/TC 211 plenary, the new work ISO/TC 211 plenary, the new work item proposal will be submitted for ballot by item proposal will be submitted for ballot by 2002-06-302002-06-30..
ISO Technical SpecificationISO Technical Specification Geographic Dataset Metadata Geographic Dataset Metadata
ImplementationImplementation
ISO Technical SpecificationISO Technical Specification Geographic Dataset Metadata Geographic Dataset Metadata
ImplementationImplementation
• Separate from ISO 19115Separate from ISO 19115• Based on Comprehensive Profile ISO 19115Based on Comprehensive Profile ISO 19115• More easily evolve with changes in More easily evolve with changes in
technologytechnology• Quickly establish implementation of ISO Quickly establish implementation of ISO
1911519115• XML SchemaXML Schema
– More rigorous validation of complianceMore rigorous validation of compliance– More exacting representation of UML More exacting representation of UML
Technical Specification Technical Specification implementationimplementation
Technical Specification Technical Specification implementationimplementation
ISO-Comprehensive Geographic Metadata.xsd
DCW.xmlRecommended
CoreMetadata
Schiphol Environmental
Impact data.xmlFull comprehensive metadata comprised of over 300 metadata elements
NMA Specific.xsd VMap 1-NL.xml
NMA cataloging profile which may include ISO recommended core plus additional selected metadata elements. The NMA XSD will define NMA specific metadata and code lists
North Sea Soundings.xmlonly 12 mandatory metadata elements
ProfilesProfilesProfilesProfiles
““A standard related to a A standard related to a community of interest”community of interest”
Metadata profilesMetadata profilesMetadata profilesMetadata profiles
Metadata Elements NMA Profile Other Profile Title X X
Originator X X
Publication Date X X
Publication Place X
Series Name X
Progress X X
Production Status (ext) X
Access Restrictions X
Price X
. . .
The ISO Metadata standard is a list of possible metadata elementsA Profile is a selection of those elements that fit an organization’s needs
Regional, national, & Regional, national, & organizational profilesorganizational profilesRegional, national, & Regional, national, &
organizational profilesorganizational profiles
ANZLIC ProfileANZLIC Profile
Canadian ProfileCanadian Profile
EO ProfileEO Profile
European ProfileEuropean Profile
US Federal ProfileUS Federal Profile
NATO ProfileNATO Profile
Profiles Enable Interoperability Between Communities
ISO Standard 19115ISO Standard 19115Geographic Information - MetadataGeographic Information - Metadata
State ProfileState Profile Navigation ProfileNavigation Profile
Building a ProfileBuilding a ProfileBuilding a ProfileBuilding a Profile
• Requirements AnalysisRequirements Analysis
– ScopeScope
– Community of interestCommunity of interest
– Applicable contextApplicable context
– Functions that require supportFunctions that require support
– Legacy systemsLegacy systems
– Life cycle (data)Life cycle (data)
Life CycleLife CycleLife CycleLife Cycle
Discovery/Retrieval of InformationDiscovery/Retrieval of Information
Planning → Generate Task
Tasking Tasking → Request for collection Request for collection
Process/Exploit DataProcess/Exploit Data
Dissemination/ArchivingDissemination/Archiving
Acquisition Acquisition → Collect DataCollect Data
Request for InformationRequest for Information
SUCCESS
FAILURE
SUCCESS
New Metadata Work New Metadata Work ItemsItems
New Metadata Work New Metadata Work ItemsItems
• ISO/TS 19139 ISO/TS 19139 Geographic Geographic Information – MetadataInformation – Metadata – – Dataset Dataset Implementation SpecificationImplementation Specification
• ISO 19115-2 ISO 19115-2 Geographic Information Geographic Information – Metadata– Metadata – Part 2 – Part 2 Extensions for Extensions for Imagery and Gridded DataImagery and Gridded Data
ISO/TS 19139ISO/TS 19139ISO/TS 19139ISO/TS 19139
This This implementation specificationimplementation specification is applicable to digital is applicable to digital geographic datasetsgeographic datasets and can be used to describe many and can be used to describe many other forms of geographic data such as maps, charts, other forms of geographic data such as maps, charts, and textual documents. It provides information about and textual documents. It provides information about the identification, the extent, the quality, the spatial and the identification, the extent, the quality, the spatial and temporal reference, and the distribution of digital temporal reference, and the distribution of digital geographic data.geographic data.
More specifically, this specification provides an More specifically, this specification provides an implementation UML model implementation UML model based on the ISO 19115based on the ISO 19115 abstract UML model and defines an abstract UML model and defines an XML schemaXML schema derived from the implementation UML model.derived from the implementation UML model.
Scope
Overview of ISO 19139 DraftOverview of ISO 19139 DraftOverview of ISO 19139 DraftOverview of ISO 19139 Draft• Composed of three essential parts in the Composed of three essential parts in the
Requirements Clause:Requirements Clause:– ISO 19139 expands Annex E of ISO 19115 to ISO 19139 expands Annex E of ISO 19115 to
show all the metadata elements show all the metadata elements (Not XML (Not XML Specific)Specific)
– ISO 19139 also defines new constraint types to ISO 19139 also defines new constraint types to further refine the metadata elements for further refine the metadata elements for implementation implementation (Not XML Specific)(Not XML Specific)
– ISO 19139 defines ISO 19139 defines XML SchemaXML Schema for geographic for geographic information dataset metadata information dataset metadata (XML Specific)(XML Specific)
XML Schema ImplementationXML Schema ImplementationXML Schema ImplementationXML Schema Implementation
• Although the XML schema in ISO Although the XML schema in ISO 19139 is to be used to provide 19139 is to be used to provide metadata for digital geographic metadata for digital geographic datasets, the schemas may also be datasets, the schemas may also be applied to applied to aggregations of datasets, aggregations of datasets, feature types, individual features, feature types, individual features, attribute types, and individual attribute types, and individual attributesattributes
How We’re Building ISO How We’re Building ISO 1913919139
How We’re Building ISO How We’re Building ISO 1913919139
Harmonized ISO Model
ImplementationUML Model(ISO 19139)
IntermediateXML Description
Transformation with Rational Rose Scripts
MetadataXML Schema (s)
XSLTTransformation
Stylesheet
Create Implementation Model
of Dataset Profile with Rational Rose Scripts
ISO 19139ISO 19139
ScheduleScheduleISO 19139ISO 19139
ScheduleSchedule
• Working Draft:Working Draft: 2003-092003-09
• Preliminary Draft TS: Preliminary Draft TS: 2004-022004-02
• Draft TS:Draft TS: 2004-072004-07
• Technical Specification:Technical Specification: 2004-112004-11
Work is just starting – get involved
ISO 19115-2 ISO 19115-2 Geographic Geographic Information – MetadataInformation – Metadata – Part 2 – Part 2
Extensions for Imagery and Extensions for Imagery and Gridded DataGridded Data
ISO 19115-2 ISO 19115-2 Geographic Geographic Information – MetadataInformation – Metadata – Part 2 – Part 2
Extensions for Imagery and Extensions for Imagery and Gridded DataGridded Data
• ScopeScope
– This International Standard This International Standard extendsextends ISO ISO 19115:2003 Geographic Information – 19115:2003 Geographic Information – Metadata by Metadata by defining the schema and defining the schema and additional metadataadditional metadata required for imagery required for imagery and gridded dataand gridded data
ISO 19115-2ISO 19115-2ISO 19115-2ISO 19115-2• Current ISO 19115 MetadataCurrent ISO 19115 Metadata
– Some geospatial imagery support existsSome geospatial imagery support exists– Detailed imagery metadata definition purposely deferredDetailed imagery metadata definition purposely deferred
• Geospatial Imagery MetadataGeospatial Imagery Metadata– User Requirements (same as User Requirements (same as regularregular geospatial user geospatial user
requirements): requirements): – Locate Locate – EvaluateEvaluate– ExtractExtract– EmployEmploy
– Requirements: Reside in a variety of disciplines and Requirements: Reside in a variety of disciplines and communitiescommunities
ApproachApproachApproachApproach• Take Advantage of the TC211 Harmonized ModelTake Advantage of the TC211 Harmonized Model
– Develop UML model of new elementsDevelop UML model of new elements– Leverage existing elements where possible and Leverage existing elements where possible and
appropriateappropriate– Do not interfere with existing implementationsDo not interfere with existing implementations
• As ISO 19115 - Part 2As ISO 19115 - Part 2– Augments ISO 19115Augments ISO 19115– Allows incorporation of new elementsAllows incorporation of new elements– Permits current standard to stand alonePermits current standard to stand alone
Liaison Organizations and Related Work
Liaison Organizations and Related Work
ISO 19115:2003ISO 19115:2003
FGDCMetadata Remote Sensing Extensions
FGDCMetadata Remote Sensing Extensions
ISO19115 - 2 Imagery
Extensions
ISO19115 - 2 Imagery
Extensions
IHOS-57 Edition 4
IHOS-57 Edition 4
SMPTESMPTEJTC1/SC24ISO/IEC 12087-5 BIFF
JTC1/SC24ISO/IEC 12087-5 BIFF
CommercialSPOT
CommercialSPOT
ConsortiumIEEE
ISPRSWMO
ConsortiumIEEE
ISPRSWMO
Proposed ExtensionProposed Extension Identification InformationIdentification Information
Proposed ExtensionProposed Extension Identification InformationIdentification Information
MD_DataIdentification
MD_Identification
New Imagery Elements and Existing Classes
Number_of_Thematic_Layers
Mission_CompletionMission_Description
Mission_Significant_Event
Mission_Start_Date
Data_Dictionary_ReferenceScience_PaperUser's_Guide
Platform_Information
Platform_and_Instrument_Identification
Proposed ExtensionProposed Extension Data Quality – LineageData Quality – Lineage
Proposed ExtensionProposed Extension Data Quality – LineageData Quality – Lineage
LI_ProcessStep
Algorithm_Change_HistoryAlgorithm_Identifiers
Algorithm_Peer_Review_InformationAlgorithm_Reference
Algorithm_Text_Description
Command_Line_Processing_ParameterProcessing_Change_HistoryProcessing_Documentation
Processing_IdentifiersProcessing_Procedure_Description
Processing_Run_HistoryProcessing_Software_Reference
New Imagery Elements and Existing Classes
ISO 15115-2ISO 15115-2
ScheduleScheduleISO 15115-2ISO 15115-2
ScheduleSchedule
• Working Draft:Working Draft: 2003-092003-09• Committee Draft:Committee Draft: 2004-082004-08• CD2:CD2: 2005-032005-03• Draft International Standard: 2005-09Draft International Standard: 2005-09• Final DIS:Final DIS: 2006-052006-05• IS:IS: 2006-082006-08
ImplementingImplementingISO 19115ISO 19115
ImplementingImplementingISO 19115ISO 19115
Geographic Data and Services Life
Cycle End UserEnd User
6. Use6. Use
Distributed GIS activitiesDistributed GIS activitiesDistributed GIS activitiesDistributed GIS activities
Create Data andCreate Data andServicesServices
1. Create Content1. Create Content
Query, DiscoverQuery, Discover
5. Discover5. Discover
Document with MetadataDocument with Metadata
2. Document (Metadata)2. Document (Metadata)
MetadataMetadata
CatalogCatalog
3. Catalog3. Catalog
Publish ServicesPublish Services
4. Publish4. Publish
Catalog PortalCatalog Portal
ArcCatalogArcCatalogArcCatalogArcCatalog
• A tool for exploring and managing A tool for exploring and managing geographic datageographic data
– File-based data on disk in many File-based data on disk in many formatsformats
– Design and implement spatial Design and implement spatial databases in an enterprise RDBMSdatabases in an enterprise RDBMS
– Access vector, image, metadata Access vector, image, metadata services on ArcIMS Internet serversservices on ArcIMS Internet servers
Design goals for Design goals for metadata in ArcCatalogmetadata in ArcCatalog
Design goals for Design goals for metadata in ArcCatalogmetadata in ArcCatalog• Make it easy to create and use Make it easy to create and use
metadatametadata–Create editors that are easy to Create editors that are easy to
useuse–Create and update metadata Create and update metadata
automatically with a dataset’s automatically with a dataset’s current propertiescurrent properties
Design goals for Design goals for metadata in ArcCatalogmetadata in ArcCatalog
Design goals for Design goals for metadata in ArcCatalogmetadata in ArcCatalog
• Support ISO metadata content Support ISO metadata content standard out-of-the-boxstandard out-of-the-box
–Support other standards through Support other standards through customizationcustomization
• Support metadata for everythingSupport metadata for everything
–Geographic data, non-spatial Geographic data, non-spatial files, folders, databases, etc.files, folders, databases, etc.
Design goals for Design goals for metadata in ArcCatalogmetadata in ArcCatalog
Design goals for Design goals for metadata in ArcCatalogmetadata in ArcCatalog• Metadata is part of the dataMetadata is part of the data
– Travels with the data when copied, Travels with the data when copied, moved, renamed, or exportedmoved, renamed, or exported
– Doesn’t get lostDoesn’t get lost
• Achieve our goals using open, Achieve our goals using open, flexible, industry standard flexible, industry standard technologytechnology
– Metadata stored in XML formatMetadata stored in XML format
ISO metadata tools ISO metadata tools in ArcCatalog in ArcCatalog
ISO metadata tools ISO metadata tools in ArcCatalog in ArcCatalog
• Editor for typing informationEditor for typing information• Stylesheets for viewingStylesheets for viewing• Synchronizer for updating Synchronizer for updating
automaticallyautomatically• Importers and exportersImporters and exporters• Translator from one standard to Translator from one standard to
anotheranother
ISO metadata editorISO metadata editorISO metadata editorISO metadata editor• Wizard-based editor designed for Wizard-based editor designed for
the average personthe average person• Elements are introduced by plain Elements are introduced by plain
languagelanguage• Navigate with Next and Back Navigate with Next and Back
buttons or go directly to a page buttons or go directly to a page using the TOCusing the TOC
• Handles core elements as defined Handles core elements as defined by 19115by 19115
ISO SynchronizerISO SynchronizerISO SynchronizerISO Synchronizer• Automates much Automates much
of the work for of the work for metadata metadata collection and collection and maintenancemaintenance
• Vector and raster Vector and raster information, information, spatial reference, spatial reference, etc.etc.
ArcIMS ArcIMS ServicesServices
ArcIMS ArcIMS ServicesServices FilesFiles
Automatically senses and records properties Automatically senses and records properties Automatically senses and records properties
ArcCatalogArcCatalog
Internet
ArcIMSMetadata
Server
ArcIMSMetadata
Server
ArcSDE
AuthorAuthor
PublishPublish
DiscoverDiscover
ArcIMS 4.0 allows easier metadata publishingArcIMS 4.0 allows easier metadata publishing
Metadata ServerMetadata ServerMetadata ServerMetadata Server
Metadata Server GoalsMetadata Server GoalsMetadata Server GoalsMetadata Server Goals• DATA SHARING!!!DATA SHARING!!!
– Provide a central repository of Provide a central repository of metadata that can be accessed by metadata that can be accessed by everyone over the internet.everyone over the internet.
– A place for data producers to publish A place for data producers to publish their data and data consumers to find their data and data consumers to find the data.the data.
– Using ArcCatalog publishers can Using ArcCatalog publishers can publish to multiple metadata serverspublish to multiple metadata servers
Publishing MetadataPublishing MetadataPublishing MetadataPublishing Metadata• Publish metadata by Publish metadata by
copy/paste or drag/dropcopy/paste or drag/drop– Copy/drag the metadata Copy/drag the metadata
onto the onto the Metadata ServerMetadata Server folder to publishfolder to publish
• Metadata is “copied” to the Metadata is “copied” to the ServerServer– a new record is created in a new record is created in
the database for this the database for this metadata dataset.metadata dataset.
– Contents are indexed to Contents are indexed to optimize search and optimize search and retrieval.retrieval.
• Must have publishing Must have publishing privileges.privileges.
Searching for Searching for Geospatial Data Geospatial Data
Searching for Searching for Geospatial Data Geospatial Data
Metadata Metadata CatalogCatalog
Geography NetworkGeography NetworkGeography NetworkGeography NetworkArcCatalogArcCatalog
HTML or JavaHTML or Java
Clearinghouse Clearinghouse Z39.50Z39.50
Metadata ExplorerMetadata Explorer
Customizing Customizing Customizing Customizing • Metadata ExplorerMetadata Explorer
- GraphicsGraphics- TitleTitle- Search criteriaSearch criteria- Help instructionsHelp instructions- Display of results, Display of results,
details, map viewsdetails, map views• Metadata ServerMetadata Server
- Custom contentCustom content- Based on XML Based on XML
– ISOISO– FGDCFGDC– National profile National profile
•ISO 19115 development–based on a solid foundation of national, regional, and information community standards–has broad global participation–has gone through formal development cycles
• New ISO metadata work initiated– ISO 19139 Metadata
implementation Technical Specification
– Robust implementation / Validation
– ISO 19115-2 Imagery– Improved imagery metadata – Developed by imagery
experts from around the world
SummarySummaryISO MetadataISO MetadataSummarySummary
ISO MetadataISO Metadata• Metadata is absolutely
essential for all aspects of spatial data handling– Locate– Evaluate– Extract– Employ
the foundation for a Global Spatial Data Infrastructure
•ISO standard metadata–Allows expanded networks–Provides a common understanding–Global Interoperability