1 / 62

ISO/TC211 Geographic information/Geomatics Metadata

ISO/TC211 Geographic information/Geomatics Metadata. David Danko Work Item 15 - Project Leader ddanko@esri.com. Metadata Data about Data. Geospatial data has a long history using Metadata Map catalogs Maps and Charts Imagery Digital data files. Identification. Paper Maps. Symbols

christmas
Download Presentation

ISO/TC211 Geographic information/Geomatics Metadata

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ISO/TC211Geographic information/GeomaticsMetadata David Danko Work Item 15 - Project Leader ddanko@esri.com

  2. MetadataData about Data • Geospatial data has a long history using Metadata • Map catalogs • Maps and Charts • Imagery • Digital data files

  3. Identification Paper Maps Symbols (Feature Codes) Warnings Date Sources Producer Title Reference system Navigation notices Scale Accuracy Location

  4. Metadata perspectives • Why it’s more important now? • Expansion in the use of Geographic Information • Proliferation of data • Non-geographers using geospatial data • The producer is not the user • Geospatial data is imperfect • A model, a “point of view” • Assumptions, limitations, approximations, simplifications • Expensive • Reuse • Data management • Why should it be standardized? • Provide an understanding of data – around the Globe and across information communities

  5. Locate Find Discover Evaluate Restrictions Quality Reputation Extract Order Download Employ Apply Use Metadata ApplicationsTo understand the right data for the right purpose

  6. The metadata environment Application Environment

  7. Spatial Data Set Client Metadata ? State Agency ? Federal Agency ? Private Company ? ? ? Academic Non-Profit Agency Local Agency Cataloging datasets Locate Evaluate Extract • Index of Datasets • Product Catalog • Printed • On-line • Clearinghouse • Searching • Browsing • Data Warehouse • Management

  8. Understanding data Locate Evaluate Employ Pleasantville • Understand the Model • How features are represented • Connectivity • Understand the Content • Why features are included or excluded • Understand the Point-of-View • Business/Commercial • Environmental/Scientific • Military/Defense/Intel Pleasantville Pleasantville

  9. Processing support Extract Employ • Support user Decisions • Identify multiple datasets within an application • Know the good and bad areas • Merging data (which is the better data?) • Currentness • Quality • Support Computer Processing • Application software functions • Extraction/Creation (I/O) • Guide software through the data

  10. Historical records Locate Evaluate • Production Management • Storage/Archival • Coordinating production • Planning - setting priorities • Legal Records • Proper use • Document assumptions

  11. ISO 19115:2003 Metadata Stage date: 2003-05-08 http://www.iso.org/iso/en/prods-services/ISOstore/store.html

  12. ISO 19115:2003Scope • ...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

  13. The ISO Process • Formal Process • Refined over 50 years • Stages and timelines fully defined • Consensus based • Drafts considered until consensus reached through voting process by P- members

  14. ISO metadata foundation • Regional 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 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

  15. ISO 19115:2003 Metadata applications GF_FeatureType DS_DataSet 0..* 0..* 1..* MD_Metadata FE_Feature 1..* 0..* 1..* GF_PropertyType 0..* 0..* 0..* 0..* <<Abstract>> DS_Aggregate FE_FeatureAttribute 0..* 0..* DS_Series DS_Initiative DS_OtherAssociation DS_Platform DS_Sensor DS_ProductionSeries DS_StereoMate

  16. Identification Information Reference System Information Locate Distribution Information Data Quality Information 19108, 11, 12 Content Information Evaluate 19113,14 19110, 21, 23, 24 Extract Application Schema Information Metadata Extension Information Constraint Information 19107 Employ 19109 19117 Spatial Representation Information Portrayal Catalogue Information Maintenance Information Metadata packages Developed to fulfill primary metadata applications

  17. ISO 19115: 2003 Metadata schema object models <<CodeList>> MD_Metadata MD_Usage MD_TopicCategoryCode + farming + biota (from Metadata entity set information) + specificUsage : CharacterString + boundaries + usageDateTime[0..1] : DateTime MD_Constraints + climatologyMeterologyAtmosphere + userDeterminedLimitations[0..1] : CharacterString + economy + userContactInfo [1..*] : CI_ResponsibleParty + elevation (from Constraint information) + environment + geoscientificInformation 0..* 0..* +resourceConstraints 0..* 0..* + health +resourceSpecificUsage + imageryBaseMapsEarthCover +identificationInfo 1..* 1..* + intelligenceMilitary + inlandWaters MD_Identification <<Abstract>> MD_BrowseGraphic + location + oceans + citation : CI_Citation + planningCadastre +graphicOverview + abstract : CharacterString + fileName : CharacterString + society + purpose [0..1] : CharacterString + fileDescription[0..1] : CharacterString + structure 0..* 0..* + credit [0..*] : CharacterString + fileType[0..1] : CharacterString + transportation + status [0..*] : MD_ProgressCode + utilitiesCommunications + pointOfContact [0..*] : CI_ResponsibleParty +descriptiveKeywords +resourceFormat 0..* 0..* MD_Format MD_Keywords 0..* 0..* (from Distribution information) + keyword[1..*] : CharacterString + type [0..1] : MD_KeywordTypeCode + thesaurusName[0..1] : CI_Citation <<CodeList>> characterSet: documented if ISO MD_KeywordTypeCode 10646-1 is not used + discipline {MD_Metadata.hierarchyLevelCode = + place +resourceMaintenance "dataset" implies count (geographicBox) + stratum 0..* 0..* MD_MaintenanceInformation + count (geographicDescription) >=1} + temporal + theme (from Maintenance information) MD_ServiceIdentification MD_DataIdentification <<CodeList>> MD_SpatialRepresentationTypeCode + vector + spatialRepresentationType [0..*] : MD_SpatialRepresentationTypeCode + grid + spatialResolution [0..*] : MD_Resolution <<CodeList>> + textTable + language [1..*] : CharacterString <<CodeList>> MD_CharacterSetCode + TIN + characterSet [0..1] : MD_CharacterSetCode = "utf8" MD_ProgressCode + stereoModel Scale + ucs2 + topicCategory [1..*] : MD_TopicCategoryCode + completed + video + ucs4 + geographicBox [0..*] : EX_GeographicBoundingBox (from Units of Measure) + historicalArchive + utf8 + geographicDescription [0..*] : EX_GeographicDescription + obsolete + utf16 + environmentDescription [0..1] : CharacterString /Scale + onGoing Where MD_Representative + isoIec8859oneTo15 + extent [0..*] : EX_Extent + planned Fraction.denominator = + jis + supplementalInformation [0..1] : CharacterString <<DataType>> + required 1/Scale.measure And + shiftJIS MD_RepresentativeFraction + underDevelopment Scale.targetUnits = + eucJP /+ denominator : Integer Scale.sourceUnits <<Union>> MD_Resolution + equivalentScale : MD_RepresentativeFraction + distance : Distance

  18. count of (individualName + <<DataType>> <<DataType>> CI_Citation CI_ResponsibleParty organisationName + position Name) > 0 + title : CharacterString + individualName[0..1] : CharacterString + alternateTitle [0..*] : CharacterString + organisationName[0..1] : CharacterString + date [1..*] : CI_Date + positionName[0..1] : CharacterString <<CodeList>> + edition [0..1] : CharacterString + contactInfo [0..1] : CI_Contact CI_RoleCode + editionDate [0..1] : Date + role : CI_RoleCode + resourceProvider + identifier [0..*] : CharacterString + custodian + identifierType [0..*] : CharacterString + owner + citedResponsibleParty [0..*] : CI_ResponsibleParty <<DataType>> + user + presentationForm [0..*] : CI_PresentationFormCode CI_Contact + distributor + series [0..1] : CI_Series + phone [0..1] : CI_Telephone + originator + otherCitationDetails [0..1] : CharacterString + address [0..1] : CI_Address + pointOfContact + collectiveTitle[0..1] : CharacterString + onlineResource [0..1] : CI_OnlineResource + principalInvestigator + ISBN[0..1] : CharacterString + hoursOfService [0..1] : CharacterString + processor + ISSN[0..1] : CharacterString + contactInstructions [0..1] : CharacterString + publisher <<DataType>> CI_Series <<DataType>> <<CodeList>> CI_OnlineResource + name [0..1] : CharacterString CI_OnLineFunctionCode + issueIdentification [0..1] : CharacterString + linkage : URL + download + page [0..1] : CharacterString + protocol [0..1] : CharacterString + information + applicationProfile [0..1] : CharacterString + offlineAccess + name [0..1] : CharacterString + order + description [0..1] : CharacterString + search <<CodeList>> <<DataType>> + function [0..1] : CI_OnLineFunctionCode CI_Date CI_PresentationFormCode + documentDigital + date : Date + documentHardcopy URL + dateType : CI_DateTypeCode <<DataType>> + imageDigital CI_Address + mapDigital + deliveryPoint [0..*] : CharacterString + mapHardcopy <<CodeList>> + city [0..1] : CharacterString + modelDigital <<DataType>> CI_Telephone CI_DateTypeCode + administrativeArea [0..1] : CharacterString + modelHardcopy + postalCode [0..1] : CharacterString + creation + profileDigital + voice [0..*] : CharacterString + country [0..1] : CharacterString + publication + profileHardcopy + facsimile [0..*] : CharacterString + electronicMailAddress[0..*] : CharacterString + revision + tableDigital + tableHardcopy + videoDigital + videoHardcopy Citation data types

  19. <<DataType>> EX_Extent + description[0..1] : CharacterString count(description + geographicElement + +geographicElement temporalElement + verticalElement) >0 0..* 0..* <<Abstract>> EX_GeographicExtent +temporalElement + extentTypeCode [0..1] : Boolean = "1" 0..* 0..* EX_TemporalExtent + extent : TM_Primitive +spatialExtent 1..* 1..* +verticalElement 0..* 0..* EX_VerticalExtent + minimumValue : Real + maximumValue : Real + unitOfMeasure : UomLength EX_BoundingPolygon + polygon[1..*] : GM_Object EX_SpatialTemporalExtent EX_GeographicBoundingBox +verticalDatum + westBoundLongitude : Angle 1 1 EX_GeographicDescription + eastBoundLongitude : Angle + southBoundLatitude : Angle + geographicIdentifier : MD_Identifier SC_VerticalDatum + northBoundLatitude : Angle (from Spatial Referencing by Coordinates) Extent data types

  20. <<CodeList>> MD_ProgressCode completed historicalArchive obsolete onGoing planned required underDevelopment Name DomainCode Definition MD_ProgressCode ProgCode status of the resource completed 001 production has been completed historicalArchive 002 data has been stored offline obsolete 003 data is no longer relevant onGoing 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... CodeLists

  21. Why codelists • Suggested items (pick lists) • Searchable (common representation) • Registered definition (dictionary) • Multi-lingual

  22. ISO 19115: 2003 Metadata data dictionary

  23. Dataset title Dataset reference date Dataset responsible party Geographic location of the dataset (by four coordinates or by geographic identifiers) Dataset language Dataset character set Dataset topic category Spatial Resolution Abstract describing the dataset Distribution format Additional extent information (vertical and temporal) Spatial representation type Reference system Lineage statement On-line resource Metadata file identifier Metadata standard name Metadata standard version Metadata language Metadata character set Metadata point of contact Metadata time stamp Recommended core metadata for geographic datasets • Mandatory

  24. ISO 19115:2003 Annex EComprehensive dataset metadata application schema

  25. ISO 19115:2003 Annex EComprehensive datasetmetadata profile • Comprehensive metadata application schema (UML model) • Implementation profile • Applicable to a broad range of information communities • Complete range of metadata

  26. ISO 19115:2003 • Designed: • to support geographic information; • to work with wider information technology standards and practices; • 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

  27. Resolution 226 - Proceeding of ISO DIS 19115 Metadata • ISO/TC 211 resolves to delete the informative annex F, clause J.3 and any references to these, in ISO DIS 19115, as requirements for XML DTDs are replaced by requirements for XML schemas in 19118. •  ISO/TC 211 instructs the secretariat to process the corrections above and other editorial and minor technical improvements in accordance with the ISO Directives, and to forward ISO DIS 19115 to the ISO Central Secretariat for issuing as FDIS. •  ISO/TC 211 resolves that an implementation UML model and an XML Schema for metadata in compliance with ISO 19115 and 19118 will be a new work item proposal for a Technical Specification. Based on discussions at the 14th ISO/TC 211 plenary, the new work item proposal will be submitted for ballot by 2002-06-30.

  28. ISO Technical SpecificationGeographic Dataset Metadata Implementation • Separate from ISO 19115 • Based on Comprehensive Profile ISO 19115 • More easily evolve with changes in technology • Quickly establish implementation of ISO 19115 • XML Schema • More rigorous validation of compliance • More exacting representation of UML

  29. NMA Specific.xsdVMap 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 Technical Specification implementation ISO-Comprehensive Geographic Metadata.xsd DCW.xml Recommended Core Metadata Schiphol Environmental Impact data.xml Full comprehensive metadata comprised of over 300 metadata elements North Sea Soundings.xml only 12 mandatory metadata elements

  30. Profiles “A standard related to a community of interest”

  31. Metadata profiles The ISO Metadata standard is a list of possible metadata elements A Profile is a selection of those elements that fit an organization’s needs

  32. Regional, national, & organizational profiles ISO Standard 19115 Geographic Information - Metadata State Profile Navigation Profile ANZLIC Profile European Profile NATO Profile Canadian Profile EO Profile US Federal Profile Profiles Enable Interoperability Between Communities

  33. Building a Profile • Requirements Analysis • Scope • Community of interest • Applicable context • Functions that require support • Legacy systems • Life cycle (data)

  34. Life Cycle Request for Information Discovery/Retrieval of Information FAILURE Planning → Generate Task Tasking → Request for collection Acquisition → Collect Data SUCCESS Process/Exploit Data SUCCESS Dissemination/Archiving

  35. New Metadata Work Items • ISO/TS 19139 Geographic Information – Metadata – Dataset Implementation Specification • ISO 19115-2 Geographic Information – Metadata – Part 2 Extensions for Imagery and Gridded Data

  36. ISO/TS 19139 Scope This implementation specification is applicable to digital geographic datasets and can be used to describe many other forms of geographic data such as maps, charts, and textual documents. It provides information about the identification, the extent, the quality, the spatial and temporal reference, and the distribution of digital geographic data.More specifically, this specification provides an implementation UML model based on the ISO 19115 abstract UML model and defines an XML schema derived from the implementation UML model.

  37. Overview of ISO 19139 Draft • Composed of three essential parts in the Requirements Clause: • ISO 19139 expands Annex E of ISO 19115 to show all the metadata elements (Not XML Specific) • ISO 19139 also defines new constraint types to further refine the metadata elements for implementation (Not XML Specific) • ISO 19139 defines XML Schema for geographic information dataset metadata (XML Specific)

  38. XML Schema Implementation • Although the XML schema in ISO 19139 is to be used to provide metadata for digital geographic datasets, the schemas may also be applied to aggregations of datasets, feature types, individual features, attribute types, and individual attributes

  39. How We’re Building ISO 19139 Implementation UML Model (ISO 19139) Transformation with Rational Rose Scripts Intermediate XML Description Create Implementation Model of Dataset Profile with Rational Rose Scripts XSLT Transformation Stylesheet Harmonized ISO Model Metadata XML Schema (s)

  40. ISO 19139Schedule • Working Draft: 2003-09 • Preliminary Draft TS: 2004-02 • Draft TS: 2004-07 • Technical Specification: 2004-11 Work is just starting – get involved

  41. 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 by defining the schema and additional metadata required for imagery and gridded data

  42. ISO 19115-2 • Current ISO 19115 Metadata • Some geospatial imagery support exists • Detailed imagery metadata definition purposely deferred • Geospatial Imagery Metadata • User Requirements (same as regular geospatial user requirements): • Locate • Evaluate • Extract • Employ • Requirements: Reside in a variety of disciplines and communities

  43. Approach • Take Advantage of the TC211 Harmonized Model • Develop UML model of new elements • Leverage existing elements where possible and appropriate • Do not interfere with existing implementations • As ISO 19115 - Part 2 • Augments ISO 19115 • Allows incorporation of new elements • Permits current standard to stand alone

  44. Liaison Organizations and Related Work Commercial SPOT Consortium IEEE ISPRS WMO ISO 19115 - 2 Imagery Extensions FGDC Metadata Remote Sensing Extensions ISO 19115:2003 IHO S-57 Edition 4 SMPTE JTC1/SC24 ISO/IEC 12087-5 BIFF

  45. MD_DataIdentification Number_of_Thematic_Layers Mission_Completion Mission_Description Mission_Significant_Event Mission_Start_Date Platform_Information MD_Identification Platform_and_Instrument_Identification Data_Dictionary_Reference Science_Paper User's_Guide Proposed Extension Identification Information New Imagery Elements and Existing Classes

  46. Algorithm_Change_History Algorithm_Identifiers Algorithm_Peer_Review_Information Algorithm_Reference Algorithm_Text_Description Command_Line_Processing_Parameter Processing_Change_History Processing_Documentation Processing_Identifiers Processing_Procedure_Description Processing_Run_History Processing_Software_Reference Proposed ExtensionData Quality – Lineage New Imagery Elements and Existing Classes LI_ProcessStep

  47. ISO 15115-2Schedule • Working Draft: 2003-09 • Committee Draft: 2004-08 • CD2: 2005-03 • Draft International Standard: 2005-09 • Final DIS: 2006-05 • IS: 2006-08

  48. ImplementingISO 19115

  49. Geographic Data and Services Life Cycle Query, Discover Publish Services End User 1. Create Content Catalog Portal 2. Document (Metadata) 3. Catalog Metadata 4. Publish 5. Discover Catalog 6. Use Create Data and Services Document with Metadata Distributed GIS activities

  50. ArcCatalog • A tool for exploring and managing geographic data • File-based data on disk in many formats • Design and implement spatial databases in an enterprise RDBMS • Access vector, image, metadata services on ArcIMS Internet servers

More Related