Metadata Workshop. David Danko Work Item 15, 39 - Project Leader Senior Consultant - GIS Standards

Transcription

1 Metadata Workshop David Danko Work Item 15, 39 - Project Leader Senior Consultant - GIS Standards ddanko@esri.com

2 Interoperability Where does metadata fit? Metadata? Geospatial metadata Not just for catalogs Metadata Standards Dublin Core FGDC Agenda An introduction to ISO Implementing geospatial metadata ISO Profiles Discovery metadata - Portals

3 GIS GIS has has always always required required Interoperability Interoperability Features Social Factors Geographic analysis Multiple sources, multiple organizations Roads/Infrastructure Distributed within a community Merging diverse information types Surveys Signal Intelligence and continues to Land Use/Land Cover Enterprise GIS CAD GIS evolving beyond isolated communities Imagery GIS merging with broader IT infrastructures Environment Tables GIS Web Services BaseWeb Maps Services Networks Enabled by distributed networks Loosely coupled Models Government Policy EU Directives US E-government Act Imagery GIS Services Geography is a Key an integrating technology

4 Interoperability the ability of two or more systems or components to exchange information and to use the information that has been exchanged (1) Be able to: find what you need; access it; understand and employ it; have goods and services responsive to the needs of consumers (2) (1) IEEE (2) ISO TC211

5 Interoperability Enablers Authorization Copyright Business Agreements Policy Framework Incentives to cooperate Business Models Infrastructure Networks Support for multiple Languages Customs Views Data Formats Projections Datums Metadata Shared Best Practices Standards

6 Varieties of Interoperability Technical Technical (machine to machine, software module interaction, API, format ) Semantic (understanding concepts, terms ) Inter-disciplinary (special vocabularies) Political/Human Political/Human (government policy, training ) Legal (ownership, responsibility )

7 Technical Interoperability Standards ISO Metadata XML Schema WMS GML

8 Semantic Interoperability Standards Standards which define terms, concepts, and information schemas ISO Metadata Title = name by which the resource is known Common Alerting Protocol-CAP msgtype = the code denoting the nature of the alert message. <element name = "msgtype"> <simpletype name = "msgtype" > <restriction base = "string"> <enumeration value = "Alert"/> <enumeration value = "Update"/> <enumeration value = "Cancel"/> <enumeration value = "Ack"/> <enumeration value = "Error"/> </restriction> </simpletype> </element> FGDC Framework data models

9 GIS - Abstracts Geography into a Modern Information Technology Framework Abstracting Geographic Knowledge Encapsulating Real World Knowledge Data Management Analysis GeoVisualization Decision Support Maps GIS Models Metadata Data Models Geodata Sets Geodatabase an Information System for Geography

10 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

11 Metadata Data about Data (official definition) Information that describes an information resource (data) so it can be understood Insures we find and use the right data for the right purpose And used correctly

12 What IS Metadata? title supplemental information abstract time period author sources (file) size

13 More Metadata features attributes

14 Metadata Data about Data Geospatial data has a long history using Metadata Map catalogs Maps and Charts Imagery Digital data files

15 Identification Paper Maps Symbols Date Warnings Sources Producer Navigation notices Accuracy Reference system Title Scale Location

16 Originator Date Location Altitude Identifiers Obliqueness Focal length Time Aerial Photos

17 Map catalogs Format Size Series name Scale Location Area coverage Characteristics Distribution information

18 Digital data packaging Identifier Date Format Location Originator Contact information

19 Metadata - Supporting Geographic Data and Services Life Cycle Archive Query, Discover 1. Create Content 2. Catalog 3. Publish End User Publish Services Catalog Portal 4. Discover Metadata 5. Use/Access Create Data and 6. Archive Services Catalog

20 The metadata environment A p p li c a t i o n Catalog Processing Support Historical Record Understand Data Locate X X X Evaluate X X X Extract X X Environment Employ X X

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

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

23 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

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

25 Metadata Leading the way to semantic interoperability 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 products Users learn about products Non standard products can be understood

26 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

27 Metadata standards Dublin core FGDC ISO 19115

28 Dublin Core Metadata Semantic Interoperability ISO Simple element set for describing a wide range of networked resources Designed for search and retrieval (locate & some non-geographic evaluation) Common semantic building block of Web metadata 15 terms (broad categories) Used in catalog and web environments Widely implemented throughout the world Metadata Harvesting

29 Dublin Core Metadata continued (from continued (from (from a "small language for making a particular class of statements about resources - elements (nouns) and qualifiers (adjectives) -- which can be arranged into a simple pattern of statements Dublin Core can be seen as a "metadata pidgin for digital tourists": easily grasped, but not necessarily up to the task of expressing complex relationships or concepts The linkage between a metadata record and the resource it describes may take one of two forms: elements may be contained in a record separate from the item, as in the case of the library's catalog record; or the metadata may be embedded in the resource itself. Most communities need additional semantics to fully describe their resources

30 Content Standard for Digital Geospatial Metadata aka - FGDC Metadata Standard

31 ISO Development Process

32 Standards Development Standards make life easy - once they are implemented Developing standards is a lot of work Many organizations involved Take time to develop Complicated 20% technical 80% political

33 The ISO Process All work performed in technical committees (TC) Formal Process Refined over 50 years Stages and timelines fully defined Consensus based Drafts considered until consensus reached through voting process by P-P members

34 Preliminary Stage Proposal Stage Preparatory Stage Committee Stage Enquiry Stage Approval Stage Publication Stage ISO Development Stages

35 Standards Development Compares to Product Development Must fill a need Requirements Analysis Why is it needed Where will it be used How will it be used Well designed Fit for purpose Easy to use Easy to maintain Well integrated Marketed Maintained (kept up to date) Compete in the marketplace Widely Supported

36 ISO design considerations Must fill a need Requirements Analysis Why is it needed Where will it be used How will it be used Well designed Fit for purpose Easy to use Easy to maintain Well integrated Marketed Maintained (kept up to date) Compete in the marketplace Widely Supported

37 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

38 Primary participants Australia Austria Canada China Czech Republic Finland France Germany Japan Korea Malaysia Netherlands Norway Saudi Arabia South Africa Spain Sweden Switzerland Thailand United Kingdom United States DGIWG ICA IHB OGC

39 ISO Document Review/Comment Process Comments must be officially received from MB - DIN, ANSI, etc through ISO TC211 Secretariat Must fully identify and state problem/issue Must recommend solution Secretariat must compile and circulate comments to the entire TC within 4 weeks of closing Editing committee (CD), Editor/Secretariat (DIS) must officially adjudicate comments Must address every comment Must accept solution or fully document alternative

40 Official Comments MB 1 Clause No./ Subclau se No./ Annex (e.g. 3.1) Paragraph/ Figure/Tab le/note (e.g. Table 1) Typ e of com - men t 2 Comment (justification for change) by the MB JP te This definition is not harmonized with ISO 19123, SE E The definition is not harmonized with ISO Proposed change by the MB Harmonize both definitions consistently Harmonize Secretariat observations Accepted. The definition for grid will be changed to: network composed of two or more sets of curves in which the member of each set intersect the members of the other sets in an algorithmic way Accepted, in principle. The definition of 'metadata element' in will be harmonized to the 19115's, as per the Editing Committee. Se and 4.7 E As NOTE1 in 4.6 and NOTE2 in 4.7 both discusses UML, they should both be named NOTE2 Change order of NOTES for 4.6 Accepted. JP te There is no note like 4.6 and 4.7. The note "Equivalent to a package in UML terminology." should be added. SE E The definition is not harmonized with ISO Harmonize Accepted. Accepted. Action: Replace model definition with s definition as follows: abstraction of some aspects of a universe of discourse

41 ISO Development Cycles Working Drafts Version March FGDC/CEN/etc Version October 1996 Version December 1996 Version January IDEF1X-ER ER model, Full Imagery md Version June 1997 Version September Remove Full Imagery metadata Version December 1997 Version February 1998 Committee Drafts Version July Levels of conformance (962 comments) Version November UML Object Model (1422 comments) Version June Single comprehensive profile (676 com) Draft International Standard Version September XML DTD Final Draft International Standard Mar 2003 Removed DTD, initiate TS International Standard May 2003 Actual metadata elements have remained generally consistent since WD 1.0

42 ISO TC211 Development goals to to support the global exploitation of of data Requires Interoperable Metadata to ensure: Common understanding of data Standardized metadata elements The right data for the right purpose Metadata elements to support a wide range of applications

43 Common understanding of data Standardized Metadata Elements Project team consensus Selection Names and identifiers Definitions Schema Utilization

44 Metadata Applications Understanding the right data for the right purpose Locate Find Discover Evaluate Restrictions Quality Reputation Extract Order Download Employ Apply Use Pleasantville Understand Pleasantville Pleasantville

45 Metadata UML Packages Identification Information Locate Data Quality Information 19113,14 Constraint Information Metadata Extension Information Content Information 19110, 21, 23, 24 Evaluate Metadata Distribution Extract Information Extract Maintenance Information Spatial Representation Information Employ Portrayal Catalogue Information Application Schema Information Reference System Information 19108, 11, 12

46 DataTypes and CodeLists <<DataType>> Ex_Extent + description <<DataType>> CI_Citation + title + alternatetitle + date + edition + editiondate + identifier + identifiertype + citedresponsibleparty + presentationform + seriesname + issueidentification + othercitationdetails + collectivetitle + page + ISBN + ISSN <<CodeList 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...

47 ISO 19115:2003

48 ISO 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

49 19115:2003 Geographic Information Metadata Defines metadata elements; Provides a schema (UML); Establishes a common set of metadata terminology, definitions (data dictionary); Provides extension procedures

50 ISO ISO 19115: :2003 Requirements clauses Metadata application UML model defining how metadata applies to datasets, aggregate datasets, features and attributes Metadata packages Metadata package and entity relationship Metadata datatypes Extent, citation, and responsible party information Recommended core metadata for geographic datasets Simple natural language short list of recommended metadata elements

51 ISO ISO 19115: :2003 Annexes Normative A. Metadata schemas Abstract Object Model (UML) B. Data dictionary and code lists C. Extensions and profiles D. Abstract test suite E. Comprehensive dataset metadata application profile Informative F. Metadata Extension Methodology G. Metadata Implementation H. Hierarchical Levels of Metadata I. Implementation Examples J. Multilingual support for free text

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

53 Dataset 1..* ISO ISO 19115: :2003 Metadata applications 1..* Metadata FE_Feature GF_FeatureType or DS_Platform <<Abstract>> DS_Aggregate DS_Series or 1..* GF_PropertyType or DS_Sensor DS_ProductionSeries FE_FeatureAttribute XYZ Points 3-D D Features Contours DTM s LIDAR DS_Initiative

54 Dataset 1..* ISO ISO 19115: :2003 Metadata applications 1..* Metadata GF_FeatureType FE_Feature or DS_Platform <<Abstract>> DS_Aggregate DS_Series DS_Sensor or 1..* GF_PropertyType or DS_ProductionSeries FE_FeatureAttribute Study, DS_Initiative Collection XYZ Points 3-D D Features Contours DTM s LIDAR

55 <<Abstract>> MD_SpatialRepresentation (from Spatial representation information) +spatialrepresentationinfo DQ_DataQuality (from Data quality information) +dataqualityinfo +distributioninfo MD_Distribution (from Distribution information) contentinfo MD_ContentInformation (from Content information) +portrayalcatalogueinfo MD_PortrayalCatalogueReference (from Portrayal catalogue information) ISO ISO 19115: :2003 Annex Annex A Metadata packages MD_ReferenceSystem (from Reference system information) +referencesysteminfo MD_Metadata + fileidentifier [0..1] : CharacterString + language [0..1] : CharacterString + characterset [0..1] : MD_CharacterSetCode = "utf8" + parentidentifier [0..1] : CharacterString + hierarchylevel [] : MD_ScopeCode = "dataset" + hierarchylevelname [] : CharacterString + contact : CI_ResponsibleParty + datestamp : Date + metadatastandardname [0..1] : CharacterString + metadatastandardversion [0..1] : CharacterString +applicationschemainfo MD_ApplicationSchemaInformation (from Application schema information) MD_MetadataExtensionInformation (from Metadata extension information) +metadataextensioninfo +metadatamaintenance metadataconstraints MD_MaintenanceInformation (from Maintenance information) +resourcemaintenance <<Abstract>> MD_Identification 1..* (from Identification information) +identificationinfo +resourceconstraints MD_Constraints (from Constraint information) Conditional statements: language: documented if not defined by the encoding standard characterset: documented if ISO not used and not defined by the encoding standard hierarchylevel: documented if hierarchylevel not equal to "dataset"? hierarchylevelname: documented if hierarchylevel not equal to "dataset"?

56 ISO 19115:2003 Annex B Metadata data dictionary Name/Role Name Short Name Definition Obligation/ Condition Maximum occurrence Data type Domain 29 MD_Identific ation ident basic information required to uniquely identify a resource 30 citation idcitation citation data for the resource 31 abstract idabs brief narratiave summary 32 purpose idpurp summary of the intentions with which the resource was developed 33 credit idcredit recognition of those who contributed to the resource 34 statuscode idstatcode status of resource Use obligation from referencing object Use maximum occurrence for referencing object Aggregated Class (MD_Metadata) <<Abstract>> Lines M 1 Class CI_Citation <<DataType>> (B3.2) M 1 CharacterString Free text O 1 CharacterString Free text O 1 CharacterString Free text O N Class MD_ProgressCode <<CodeList>> (B.6.26)

57 <<Abstract>> MD_SpatialRepresentation (from Spatial representation information) +spatialrepresentationinfo DQ_DataQuality (from Data quality information) +dataqualityinfo +distributioninfo MD_Distribution (from Distribution information) contentinfo MD_ContentInformation (from Content information) +portrayalcatalogueinfo MD_PortrayalCatalogueReference (from Portrayal catalogue information) ISO ISO 19115: :2003 Annex Annex A Metadata packages MD_ReferenceSystem (from Reference system information) +referencesysteminfo MD_Metadata + fileidentifier [0..1] : CharacterString + language [0..1] : CharacterString + characterset [0..1] : MD_CharacterSetCode = "utf8" + parentidentifier [0..1] : CharacterString + hierarchylevel [] : MD_ScopeCode = "dataset" + hierarchylevelname [] : CharacterString + contact : CI_ResponsibleParty + datestamp : Date + metadatastandardname [0..1] : CharacterString + metadatastandardversion [0..1] : CharacterString +applicationschemainfo MD_ApplicationSchemaInformation (from Application schema information) MD_MetadataExtensionInformation (from Metadata extension information) +metadataextensioninfo +metadatamaintenance metadataconstraints MD_MaintenanceInformation (from Maintenance information) +resourcemaintenance <<Abstract>> MD_Identification 1..* (from Identification information) +identificationinfo +resourceconstraints MD_Constraints (from Constraint information) Conditional statements: language: documented if not defined by the encoding standard characterset: documented if ISO not used and not defined by the encoding standard hierarchylevel: documented if hierarchylevel not equal to "dataset"? hierarchylevelname: documented if hierarchylevel not equal to "dataset"?

58 Metadata is is composed of of information chapters (packages) Content Information Distribution information Data quality information Spatial representation info Maintenance information Reference system information Constraint information Identification information Metadata fileidentifier: 3A B12 language: en characterset: (default = "utf8 ) parentidentifier: National Map TopoSeries 864 hierarchylevel: (default = "dataset ) hierarchylevelname: (not needed) contact : CI_ResponsibleParty datestamp : metadatastandardname: ISO 19115:2003 metadatastandardversion: (not needed) or metadatastandardversion: North American Profile 1.0 Page

59 <<Abstract>> MD_SpatialRepresentation (from Spatial representation information) +spatialrepresentationinfo DQ_DataQuality (from Data quality information) +dataqualityinfo +distributioninfo MD_Distribution (from Distribution information) contentinfo MD_ContentInformation (from Content information) +portrayalcatalogueinfo MD_PortrayalCatalogueReference (from Portrayal catalogue information) ISO ISO 19115: :2003 Annex Annex A Metadata packages MD_ReferenceSystem (from Reference system information) +referencesysteminfo MD_Metadata + fileidentifier [0..1] : CharacterString + language [0..1] : CharacterString + characterset [0..1] : MD_CharacterSetCode = "utf8" + parentidentifier [0..1] : CharacterString + hierarchylevel [] : MD_ScopeCode = "dataset" + hierarchylevelname [] : CharacterString + contact : CI_ResponsibleParty + datestamp : Date + metadatastandardname [0..1] : CharacterString + metadatastandardversion [0..1] : CharacterString +applicationschemainfo MD_ApplicationSchemaInformation (from Application schema information) MD_MetadataExtensionInformation (from Metadata extension information) +metadataextensioninfo +metadatamaintenance metadataconstraints MD_MaintenanceInformation (from Maintenance information) +resourcemaintenance <<Abstract>> MD_Identification 1..* (from Identification information) +identificationinfo +resourceconstraints MD_Constraints (from Constraint information) Conditional statements: language: documented if not defined by the encoding standard characterset: documented if ISO not used and not defined by the encoding standard hierarchylevel: documented if hierarchylevel not equal to "dataset"? hierarchylevelname: documented if hierarchylevel not equal to "dataset"?

60 ISO 19115:2003 Annex A Metadata schema object models Identification Information MD_Usage + specificusage : CharacterString + usagedatetime[0..1] : DateTime + userdeterminedlimitations[0..1] : CharacterString + usercontactinfo [1..*] : CI_ResponsibleParty +resourcespecificusage MD_BrowseGraphic +graphicoverview + filename : CharacterString + filedescription[0..1] : CharacterString + filetype[0..1] : CharacterString MD_Metadata (from Metadata entity set information) +identificationinfo 1..* <<Abstract>> MD_Identification + citation : CI_Citation + abstract : CharacterString + purpose [0..1] : CharacterString + credit [] : CharacterString + status [] : MD_ProgressCode + pointofcontact [] : CI_ResponsibleParty MD_Constraints (from Constraint information) +resourceconstraints <<CodeList>> MD_TopicCategoryCode + farming + biota + boundaries + climatologymeterologyatmosphere + economy + elevation + environment + geoscientificinformation + health + imagerybasemapsearthcover + intelligencemilitary + inlandwaters + location + oceans + planningcadastre + society + structure + transportation + utilitiescommunications MD_Format (from Distribution information) <<CodeList>> MD_KeywordTypeCode + discipline + place + stratum + temporal + theme +resourceformat characterset: documented if ISO is not used {MD_Metadata.hierarchyLevelCode = "dataset" implies count (geographicbox) + count (geographicdescription) >=1} +descriptivekeywords MD_Keywords + keyword[1..*] : CharacterString + type [0..1] : MD_KeywordTypeCode + thesaurusname[0..1] : CI_Citation +resourcemaintenance MD_MaintenanceInformation (from Maintenance information) MD_DataIdentification + spatialrepresentationtype [] : MD_SpatialRepresentationTypeCode + spatialresolution [] : MD_Resolution + language [1..*] : CharacterString + characterset [0..1] : MD_CharacterSetCode = "utf8" + topiccategory [1..*] : MD_TopicCategoryCode + geographicbox [] : EX_GeographicBoundingBox + geographicdescription [] : EX_GeographicDescription + environmentdescription [0..1] : CharacterString + extent [] : EX_Extent + supplementalinformation [0..1] : CharacterString <<Union>> MD_Resolution + equivalentscale : MD_RepresentativeFraction + distance : Distance <<CodeList>> MD_CharacterSetCode + ucs2 + ucs4 + utf8 + utf16 + isoiec8859oneto15 + jis + shiftjis + eucjp SV_ServiceIdentification See ISO <<CodeList>> MD_ProgressCode + completed + historicalarchive + obsolete + ongoing + planned + required + underdevelopment Scale (from Units of Measure) /Scale <<DataType>> MD_RepresentativeFraction /+ denominator : Integer <<CodeList>> MD_SpatialRepresentationTypeCode + vector + grid + texttable + TIN + stereomodel + video Where MD_Representative Fraction.denominator = 1/Scale.measure And Scale.targetUnits = Scale.sourceUnits

61 ISO 19115:2003 Annex A Metadata schema object models Identification Information MD_Usage + specificusage : CharacterString + usagedatetime[0..1] : DateTime + userdeterminedlimitations[0..1] : CharacterString + usercontactinfo [1..*] : CI_ResponsibleParty +resourcespecificusage MD_BrowseGraphic +graphicoverview + filename : CharacterString + filedescription[0..1] : CharacterString + filetype[0..1] : CharacterString MD_Metadata (from Metadata entity set information) +identificationinfo 1..* <<Abstract>> MD_Identification + citation : CI_Citation + abstract : CharacterString + purpose [0..1] : CharacterString + credit [] : CharacterString + status [] : MD_ProgressCode + pointofcontact [] : CI_ResponsibleParty MD_Constraints (from Constraint information) +resourceconstraints <<CodeList>> MD_TopicCategoryCode + farming + biota + boundaries + climatologymeterologyatmosphere + economy + elevation + environment + geoscientificinformation + health + imagerybasemapsearthcover + intelligencemilitary + inlandwaters + location + oceans + planningcadastre + society + structure + transportation + utilitiescommunications MD_Format (from Distribution information) <<CodeList>> MD_KeywordTypeCode + discipline + place + stratum + temporal + theme +resourceformat characterset: documented if ISO is not used {MD_Metadata.hierarchyLevelCode = "dataset" implies count (geographicbox) + count (geographicdescription) >=1} +descriptivekeywords MD_Keywords + keyword[1..*] : CharacterString + type [0..1] : MD_KeywordTypeCode + thesaurusname[0..1] : CI_Citation +resourcemaintenance MD_MaintenanceInformation (from Maintenance information) MD_DataIdentification + spatialrepresentationtype [] : MD_SpatialRepresentationTypeCode + spatialresolution [] : MD_Resolution + language [1..*] : CharacterString + characterset [0..1] : MD_CharacterSetCode = "utf8" + topiccategory [1..*] : MD_TopicCategoryCode + geographicbox [] : EX_GeographicBoundingBox + geographicdescription [] : EX_GeographicDescription + environmentdescription [0..1] : CharacterString + extent [] : EX_Extent + supplementalinformation [0..1] : CharacterString <<Union>> MD_Resolution + equivalentscale : MD_RepresentativeFraction + distance : Distance <<CodeList>> MD_CharacterSetCode + ucs2 + ucs4 + utf8 + utf16 + isoiec8859oneto15 + jis + shiftjis + eucjp SV_ServiceIdentification See ISO <<CodeList>> MD_ProgressCode + completed + historicalarchive + obsolete + ongoing + planned + required + underdevelopment Scale (from Units of Measure) /Scale <<DataType>> MD_RepresentativeFraction /+ denominator : Integer <<CodeList>> MD_SpatialRepresentationTypeCode + vector + grid + texttable + TIN + stereomodel + video Where MD_Representative Fraction.denominator = 1/Scale.measure And Scale.targetUnits = Scale.sourceUnits

62 ISO 19115:2003 Annex A Metadata schema object models Identification Information MD_Usage + specificusage : CharacterString + usagedatetime[0..1] : DateTime + userdeterminedlimitations[0..1] : CharacterString + usercontactinfo [1..*] : CI_ResponsibleParty +resourcespecificusage MD_BrowseGraphic +graphicoverview + filename : CharacterString + filedescription[0..1] : CharacterString + filetype[0..1] : CharacterString MD_Metadata (from Metadata entity set information) +identificationinfo 1..* <<Abstract>> MD_Identification + citation : CI_Citation + abstract : CharacterString + purpose [0..1] : CharacterString + credit [] : CharacterString + status [] : MD_ProgressCode + pointofcontact [] : CI_ResponsibleParty MD_Constraints (from Constraint information) +resourceconstraints <<CodeList>> MD_TopicCategoryCode + farming + biota + boundaries + climatologymeterologyatmosphere + economy + elevation + environment + geoscientificinformation + health + imagerybasemapsearthcover + intelligencemilitary + inlandwaters + location + oceans + planningcadastre + society + structure + transportation + utilitiescommunications MD_Format (from Distribution information) <<CodeList>> MD_KeywordTypeCode + discipline + place + stratum + temporal + theme +resourceformat characterset: documented if ISO is not used {MD_Metadata.hierarchyLevelCode = "dataset" implies count (geographicbox) + count (geographicdescription) >=1} or +descriptivekeywords MD_Keywords + keyword[1..*] : CharacterString + type [0..1] : MD_KeywordTypeCode + thesaurusname[0..1] : CI_Citation +resourcemaintenance MD_MaintenanceInformation (from Maintenance information) MD_DataIdentification + spatialrepresentationtype [] : MD_SpatialRepresentationTypeCode + spatialresolution [] : MD_Resolution + language [1..*] : CharacterString + characterset [0..1] : MD_CharacterSetCode = "utf8" + topiccategory [1..*] : MD_TopicCategoryCode + geographicbox [] : EX_GeographicBoundingBox + geographicdescription [] : EX_GeographicDescription + environmentdescription [0..1] : CharacterString + extent [] : EX_Extent + supplementalinformation [0..1] : CharacterString <<Union>> MD_Resolution + equivalentscale : MD_RepresentativeFraction + distance : Distance <<CodeList>> MD_CharacterSetCode + ucs2 + ucs4 + utf8 + utf16 + isoiec8859oneto15 + jis + shiftjis + eucjp SV_ServiceIdentification See ISO <<CodeList>> MD_ProgressCode + completed + historicalarchive + obsolete + ongoing + planned + required + underdevelopment Scale (from Units of Measure) /Scale <<DataType>> MD_RepresentativeFraction /+ denominator : Integer <<CodeList>> MD_SpatialRepresentationTypeCode + vector + grid + texttable + TIN + stereomodel + video Where MD_Representative Fraction.denominator = 1/Scale.measure And Scale.targetUnits = Scale.sourceUnits

63 Mandatory Good idea ISO 19115:2003 Annex A Citation data types <<DataType>> CI_Citation + title : CharacterString + alternatetitle [] : CharacterString + date [1..*] : CI_Date + edition [0..1] : CharacterString + editiondate [0..1] : Date + identifier [] : CharacterString + identifiertype [] : CharacterString + citedresponsibleparty [] : CI_ResponsibleParty + presentationform [] : CI_PresentationFormCode + series [0..1] : CI_Series + othercitationdetails [0..1] : CharacterString + collectivetitle[0..1] : CharacterString + ISBN[0..1] : CharacterString + ISSN[0..1] : CharacterString <<DataType>> count of (individualname + organisationname + position Name) > 0 CI_ResponsibleParty + individualname[0..1] : CharacterString + organisationname[0..1] : CharacterString + positionname[0..1] : CharacterString + contactinfo [0..1] : CI_Contact + role : CI_RoleCode <<DataType>> 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 <<CodeList>> CI_RoleCode + resourceprovider + custodian + owner + user + distributor + originator + pointofcontact + principalinvestigator + processor + publisher <<DataType>> CI_Series + name [0..1] : CharacterString + issueidentification [0..1] : CharacterString + page [0..1] : CharacterString <<DataType>> CI_Date + date : Date + datetype : CI_DateTypeCode <<CodeList>> CI_DateTypeCode + creation + publication + revision <<CodeList>> CI_PresentationFormCode + documentdigital + documenthardcopy + imagedigital + mapdigital + maphardcopy + modeldigital + modelhardcopy + profiledigital + profilehardcopy + tabledigital + tablehardcopy + videodigital + videohardcopy <<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_Address + deliverypoint [] : CharacterString + city [0..1] : CharacterString + administrativearea [0..1] : CharacterString + postalcode [0..1] : CharacterString + country [0..1] : CharacterString + electronicmailaddress[] : CharacterString <<CodeList>> CI_OnLineFunctionCode + download + information + offlineaccess + order + search URL <<DataType>> CI_Telephone + voice [] : CharacterString + facsimile [] : CharacterString

64 Responsible Party Data type Example CI_ResponsibleParty organisationname: Department of Primary Industries and Resources SA positionname: GIS Coordinator contactinfo: CI_Contact phone: CI_Telephone voice: facsimile: address: CI_Address deliverypoint: GPO Box 167 city: Adelaide administrativearea: South Australia postalcode: 5001 country: Australia electronicmailaddress: pirsa.spatial@saugov.sa.gov.au onlineresource: CI_OnlineResource linkage: role: 007

65 DataIdentification details MD_DataIdentification + abstract : CharacterString + citation : CI_Citation + credit [] : CharacterString + purpose [0..1] : CharacterString + pointofcontact [] : CI_ResponsibleParty + status [] : MD_ProgressCode + spatialrepresentationtype [] : MD_SpatialRepresentationTypeCode + spatialresolution [] : MD_Resolution + language [1..*] : CharacterString + topiccategory [1..*] : MD_TopicCategoryCode + characterset [0..1] : MD_CharacterSetCode = "utf8" + geographicdescription [] : EX_GeographicDescription + geographicbox [] : EX_GeographicBoundingBox + environmentdescription [0..1] : CharacterString + extent [] : EX_Extent + supplementalinformation [0..1] : CharacterString Inherited from MD_Identification characterset: documented if ISO is not used {MD_Metadata.hierarchyLevel = "dataset" implies count (extent.geographicelement. EX_GeographicBoundingBox) + count (extent.geographicelement.ex_geographicde scription >=1} {MD_Metadata.hierarchyLevel notequal dataset or series implies topiccatagory is not mandatory} EX_GeographicDescription + geographicidentifier : MD_Identifier or both EX_GeographicBoundingBox + westboundlongitude : Decimal + eastboundlongitude : Decimal + southboundlatitude : Decimal + northboundlatitude : Decimal

66 ISO 19115:2003 Annex A Extent data types +geographicelement <<Abstract>> EX_GeographicExtent + extenttypecode [0..1] : Boolean = "1" +spatialextent 1..* <<DataType>> EX_Extent + description[0..1] : CharacterString +temporalelement EX_TemporalExtent + extent : TM_Primitive count(description + geographicelement + temporalelement + verticalelement) >0 +verticalelement EX_VerticalExtent + minimumvalue : Real + maximumvalue : Real EX_BoundingPolygon + polygon[1..*] : GM_Object EX_GeographicBoundingBox + westboundlongitude : Decimal + eastboundlongitude : Decimal + southboundlatitude : Decimal + northboundlatitude : Decimal EX_SpatialTemporalExtent +verticalcrs EX_GeographicDescription 1 + geographicidentifier : MD_Identifier <<Abstract>> SC_CRS (from Spatial Referencing by Coordinates)

67 DataIdentification details characterset: documented if ISO is not used MD_DataIdentification + abstract : CharacterString + citation : CI_Citation + credit [] : CharacterString + purpose [0..1] : CharacterString + pointofcontact [] : CI_ResponsibleParty + status [] : MD_ProgressCode + spatialrepresentationtype [] : MD_SpatialRepresentationTypeCode + spatialresolution [] : MD_Resolution + language [1..*] : CharacterString + topiccategory [1..*] : MD_TopicCategoryCode + characterset [0..1] : MD_CharacterSetCode = "utf8" + geographicdescription [] : EX_GeographicDescription + geographicbox [] : EX_GeographicBoundingBox + environmentdescription [0..1] : CharacterString + extent [] : EX_Extent + supplementalinformation [0..1] : CharacterString {MD_Metadata.hierarchyLevel = "dataset" implies count (extent.geographicelement. EX_GeographicBoundingBox) + count (extent.geographicelement.ex_geographicde scription >=1} {MD_Metadata.hierarchyLevel notequal dataset or series implies topiccatagory is not mandatory} <<Enumeration>> MD_TopicCategoryCode + farming + biota + boundaries + climatologymeterologyatmosphere + economy + elevation + environment + geoscientificinformation + health + imagerybasemapsearthcover + intelligencemilitary + inlandwaters + location + oceans + planningcadastre + society + structure + transportation + utilitiescommunications

68 MD_TopicCategoryCode 1. farming 2. biota 3. boundaries 4. climatologymeteor ologyatmosphere 5. economy 6. elevation 7. environment 8. geoscientificinform ation 9. health 10. imagerybasemapsearth Cover 11. intelligencemilitary 12. inlandwaters 13. location 14. oceans 15. planningcadastre 16. society 17. structure 18. transportation 19. utilitiescommunication

69 MD_TopicCate gorycode farming biota boundaries climatologymeteorolo gyatmosphere economy elevation environment geoscientificinformat ion TopicCat Cd high-level geographic data thematic classification to assist in the grouping and search of available geographic data sets. Can be used to group keywords as well. Listed examples are not exhaustive. NOTE It is understood there are overlaps between general categories and the user is encouraged to select the one most appropriate. rearing of animals and/or cultivation of plants Examples: agriculture, irrigation, aquaculture, plantations, herding, pests and diseases affecting crops and livestock flora and/or fauna in natural environment Examples: wildlife, vegetation, biological sciences, ecology, wilderness, sealife, wetlands, habitat legal land descriptions Examples: political and administrative boundaries processes and phenomena of the atmosphere Examples: cloud cover, weather, climate, atmospheric conditions, climate change, precipitation 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 height above or below sea level Examples: altitude, bathymetry, digital elevation models, slope, derived products environmental resources, protection and conservation Examples: environmental pollution, waste storage and treatment, environmental impact assessment, monitoring environmental risk, nature reserves, landscape 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,

70 Recommended core metadata for geographic datasets 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 Mandatory

71 ISO 19115:2003 Semantic Interoperability 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

72 News flash +

73 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

74 ISO 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

75 ISO Objectives 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 Describe the process used to produce the data from the raw data

76 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 Part 2 Augments ISO Allows incorporation of new elements Permits current standard to stand alone

77 Relationship to other WG6 Imagery and Gridded Data Standards ISO Sensor and data models for imagery and gridded data Platform and Sensor Description ISO Framework for imagery and gridded data Framework Requirements ISO 19115:2003 Metadata Part 2 Extensions for imagery and gridded data ISO Geospatial Metadata ISO Imagery reference model Life-cycle Description

78 Extended UML for imagery and gridded data DQ_DataQuality (from Data quality information) + scope : DQ_Scope If(count(source) + count(processstep) =0) and (DQ_DataQuality.scope.level = 'dataset' or 'series') then statement is mandatory "description" is mandatory if "sourceextent" is not documented "sourceextent" is mandatory if "description" is not documented +lineage 0..1 LI_Lineage (from Data quality information) + statement[0..1] : CharacterString "source" role is mandatory if LI_Lineage.statement and "processstep" role are not documented "processstep" role is mandatory if LI_Lineage.statement and "source" role are not documented +source LI_Source (from Data quality information) + description[0..1] : CharacterString + scaledenominator[0..1] : MD_RepresentativeFraction + sourcereferencesystem[0..1] : MD_ReferenceSystem + sourcecitation[0..1] : CI_Citation + sourceextent[] : EX_Extent +processstep LI_ProcessStep (from Data quality information) +source + description : CharacterString + rationale[0..1] : CharacterString + datetime[0..1] : DateTime +sourcestep + processor[] : CI_ResponsibleParty inputdataset is mandatory if inputlevel.exists LE_Source + inputlevel [0..1] : MD_Identifier + inputdataset [] : MD_Identifier + resolution [0..1] : Distance +output LE_ProcessStep +runhistory +processinghistory LE_SourceSensor + instrumentidentification[1..*] : MI_InstrumentInformation + platformidentification[0..1] : MI_PlatformInformation + missionidentificaiton[0..1] : MI_MissionInformation 1..* commandlineparameter is mandatory if parameters to control operations are entered at run-time <<Union>> LE_AlgorithmHistory + description : LI_ProcessStep + reference : CI_Citation +algorithm 0..1 LE_Algorithm + identifier : CI_Citation + description : LE_AlgorithmDescription + changehistory [1..*] : LE_AlgorithmHistory + peerreview [] : LE_AlgorithmHistory +processinginformation 0..1 LE_Processing + identifier : CI_Citation + softwarereference : CI_Citation + proceduredescription [0..1] : CharacterString + processingdocumentation [] : CE_Citation + commandlineparameter [0..1] : CharacterString <<Union>> LE_AlgorithmDescription + textdescription : CharacterString + reference : CI_Citation

79 Acquisition Information Package MI_Platform + citation[0..1] : CI_Citation + identifier : MD_Identifier + description : CharacterString + sponsor[] : CI_ResponsibleParty MI_Metadata (from Metadata Entity Set - Imagery) MI_Plan + type[0..1] : MI_GeometryTypeCode + status : MD_ProgressCode + citation : CI_Citation +platform +acquisitionplan +acquisitioninformation MI_AcquisitionInformation MI_Instrument +instrument + citation : CI_Citation + type : MI_SensorTypeCode + description [0..1] : CharacterString +operation MI_Operation + description[0..1] : CharacterString + citation : CI_Citation + status : MD_ProgressCode MI_Objective +objective + identifier : MD_Identifier + priority[0..1] : CharacterString + type[] : MI_ObjectiveTypeCode + function[] : CharacterString + extent[] : EX_Extent +acquisitionrequirement MI_Requirement + citation : CI_Citation + identifier : MD_Identifier + requestor [1..*] : CI_ResponsibleParty + recipient [1..*] : CI_ResponsibleParty + priority : MI_PriorityCode + requesteddate : MI_RequestedDate + expirydate : DateTime

80 Acquisition details <<CodeList>> MI_PriorityCode + critical + highimportance + mediumimportance + lowimportance MI_Requirement + citation : CI_Citation + identifier : MD_Identifier + requestor [1..*] : CI_ResponsibleParty + recipient [1..*] : CI_ResponsibleParty + priority : MI_PriorityCode + requesteddate : MI_RequestedDate + expirydate : DateTime +satisfiedrequirement MI_Plan +satisifiedplan + type[0..1] : MI_GeometryTypeCode + status : MD_ProgressCode + citation : CI_Citation <<CodeList>> MI_GeometryTypeCode + point + linear + areal + strip <<DataType>> MI_RequestedDate + requesteddateofcollection : DateTime + latestacceptabledate : DateTime <<CodeList>> MI_ContextCode + acquisition + pass + waypoint <<CodeList>> MI_TriggerCode + automatic + manual + preprogrammed <<CodeList>> MI_SequenceCode + start + end + instantaneous +plan parentoperation 1 +childoperation +operation MI_Operation + description[0..1] : CharacterString + citation : CI_Citation + status : MD_ProgressCode MI_Event + identifier : MD_Identifier +significantevent+ trigger : MI_TriggerCode + context : MI_ContextCode + sequence : MI_SequenceCode + time : DateTime +relatedevent +objectiveoccurance 1..* MI_Platform + citation[0..1] : CI_Citation + identifier : MD_Identifier + description : CharacterString + sponsor[] : CI_ResponsibleParty +mountedon platform <<CodeList>> MI_ObjectiveTypeCode + instantaneouscollection + persistentview + survey +objective MI_Objective + identifier : MD_Identifier + priority[0..1] : CharacterString + type[] : MI_ObjectiveTypeCode + function[] : CharacterString + extent[] : EX_Extent MI_PlatformPass +relatedpass identifier : MD_Identifier + extent [0..1] : GM_Object +pass +expectedobjective MI_Instrument +instrument 1..* + citation : CI_Citation + type : MI_SensorTypeCode + description [0..1] : CharacterString +sensinginstrument +relatedsensor

81 ISO Schedule Working Draft: Committee Draft: CD2: Draft International Standard: Final DIS: IS:

82 Implementing Geospatial Metadata XML implementation Hierarchical metadata Multi-lingual lingual metadata

83 XML Implementation ISO 19139

84 ISODTS Geographic Information - Metadata XML Schema Implementation Defines geographic metadata ata XML encoding (gmdxml( gmdxml) Uses ISO rules to produce ISO XML from ISO UML Schema Identification of additional entities Namespace gmd XML Schema of gss ISO Spatial Schema realized by ISO GML gts ISO Temporal XML Schema gsr ISO Spatial Referencing realized by ISO GML gco ISO Encoding gmx extended geographic metadata XML schemas for codelists,, etc Takes advantage of GML and other XML encodings basic types realized by XML Schema and GML, example: xs: : string, gml UOM dictionaries Clauses defining Cultural and linguistic support multiple languages, etc Metadata for transfer Dataset and Aggregate dataset metadata Codelists Technical Interoperability

85 ISO Geographic Dataset Metadata Implementation Specification Schemas available at and (future) User community profile community requirements Should always test against ISO schemas Develop user conformance testing requirements and corresponding test scripts/schematron schematron Test for your profile s content, conditionality, cardinality, codelist values, etc

86 Hierarchical Metadata Example Metadata for: National topographic series of 1:50,000 basic framework features Individual datasets within the series Dataset series: collection of datasets sharing the same product specification

87 SI-19-I-c-2 Dataset 1 metadata Hierarchical metadata Annex G -- ISO Metadata Standard Serie Topográfica de Chile Escala 1:50,000 Series metadata SI-19-I-c-3 Dataset 2 metadata SI-19-I-c-1 SI-19-I-c-1 Dataset 3 metadata

88 Series Metadata MD_Metadata: hierarchylevel: MD_ScopeCode = series hierarchylevelname: Serie Topográfica de Chile Escala 1: MD_DataIdentification: Citation: Title: Serie Topográfica de Chile Escala 1: Responsible party: IGM SpatialResolution: 1: Dataset topiccatagory: ImagerybaseMapsEarthCover Distribution format: mapa impreso Metadata about the series covers all the datasets in the series

89 Dataset 1 Metadata MD_Metadata: ParentIdentifier: Serie Topográfica de Chile Escala 1: hierarchylevel [] : MD_ScopeCode = dataset MD_DataIdentification: Citation: Title: SI-19-I-c3 Date: 2001 DateType: publicación Metadata about Extent: westboundinglongitude: the individual eastboundinglongitude: dataset only southboundinglatitude: the metadata northboundinglatitiude: unique to dataset

90 Multi-lingual lingual support Encoding semantic interoperability Enhancing free text information Use Limitations: Language: eng Country: United Kingdom Character Set: ISO/IEC 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 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.

91 Better yet Controlled vocabulary using codelists administrative area: lang: : (sp) Metrapltona (free text, miss-spelled) lang: (en) Metopolitan administrative area: Codelist: CodelistValue: Metropolitana CodeAlternativeExpression: 6 Administrative area Code List 1. Región de Tarapacá 2. Región de Antofagasta 3. Región de Atacama 4. Región de Coquimbo 5. Región de Valparaiso 6. Región de Metropolitana 7.

92 Section Summary Metadata is essential for all aspects of spatial data handling Locate Evaluate Extract Employ Dublin Core Easily grasped, General purpose discovery metadata Not up to describing complex concepts (geo?) Content Standard for Digital Geospatial (FGDC) Metadata Executive order Provided real world experience Widely implemented ISO 19115:2003 Using UML and data dictionaries to provide 11 packages of metadata Providing a comprehensive set of metadata to help enable the abstraction of the real world, discovery, and all aspects of spatial data handling Corrigendum Part 2 for Imagery ISO Technical (Implementation) Specification XML encoding for ISO metadata Tailored toward the web environment Provides for Multi-lingual lingual support Hierarchical metadata Controlled vocabularies

93 Profiles

94 Profiles Point No Latitude Longitude Elevation Characteristic Person 1 Person Height 168cm 196cm Weight 56kg 85kg Hair color Blond Black Gender Female Male Level of Education... Phd Masters Degree

95 Community Profile Characteristics Police Profile Academic Profile Alias X Height Weight X X Reasearch Speciality GPA X X X

96 ISO Standardized Profiles...set of one or more base standards or sub-sets sets of base standards that are necessary for accomplishing a particular function. Conformance to profile = conformance with base standard(s) (Conformance Level 1, Strict Conformance) Registered Profiles Internationally Registered (ISP) Nationally Registered Published Profiles Formally within Community Informally within Organization

97 Profile A standard tailored for a Community Standard Broad/complex Generic Optional Undefined domains Profile Narrow focus/often simpler Specific Mandatory Explicit Domains codelists Easier implementation

98 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 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...

99 Regional, national, & organizational profiles Communities with a common need for metadata ISO Standard Geographic Information - Metadata State Profile ANZLIC Profile NATO Profile EO Profile Navigation Profile European Profile North American Profile Perfil Latinoamericano de Metadata Profiles Enable Interoperability Between Communities

100 ISO Technical Specification Implementation DCW.xml Recommended Core Metadata Lake Okeechobee Soundings.xml only 12 mandatory metadata elements Lake Okeechobee Environmental Impact data.xml Full comprehensive metadata comprised of over 300 metadata elements NMA Specific.xsd TopoMap1-FL.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

101 Regional, National, Organization Profiles Regional/National ANZLIC North American European Asia/Pacific Latin American Information Community Earth observation NATO Hydrographic Aeronautical Geology Biology Specialty data providers

102 Extensions ISO provides metadata for a general variety of digital geographic data and generic applications Because of the wide variety of data and applications it may not be sufficient Extensions may be needed to add metadata elements, entities, and code- lists

103 Extension examples Attribute extension change attribute to class, add attributes Standard Fee: $100 (characterstring) Code list extension add East Timor Package extension Extension Fee: Currency type: MXP Amount: 500 add Biological Taxonomy section

104 Incorporating extensions via the standards development cycle

105 Profiles with extensions Standards balance needs of interoperability with needs that exceed requirements of the standard Higher interoperability = lower functionality Higher functionality = lower interoperability Extensions lower interoperability outside the community Extensions are out of scope with respect to base standard ISO Conformance level 2 conforming

106 Extensions and conformance

107 Profile selection and metadata creation exercise

108 Metadata element selection process This exercise is not to replace your national or community metadata profile development This is to provide an example of the thought process involved Your national/community profile should be based on a community wide user/requirement review process and balanced assessment of what s practical Look at previous work World Spatial Metadata Standards,, Edited by H. Moellering Part V. Cross-table of National and International Spatial Metadata Standards and Associated Characteristics.

109 How much metadata is enough? Only discovery metadata? Discovery and response metadata? (for search refinement/high level evaluation) Discovery, response, moderate evaluation, & access? Comprehensive metadata? Ask for just Discovery metadata and you end up revisiting data to collect additional metadata Don t fall into the Dublin Core trap Ask for too much and you turn off data producers Address the majority of users Minimum metadata is minimally useful 1 1 Creating and Publishing Metadata in Support of Geospatial One-Stop and the NSDI

110 For this exercise we ll look at 3 working metadata standards ISO Dublin Core ESRI metadata (application specific)

111 ISO 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 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 Mandatory

112 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

113 Dublin Core / ISO Core Compared Dataset title Dataset responsible party (originator) Dataset topic category Abstract describing the dataset From ISO 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

114 ESRI Metadata Metadata elements not typically included within dataset/services metadata records Metadata element Published Document ID Input Source Modification Date Modification Time (issecured) (resourcetype) Example {C52B9923-6D4F-D123 D123-9F70- F511E2452AA9} false 005 Can be added by metadata maintenance organization Metadata file identifier Where the metadata came from harvested, on-line, etc Metadata time stamp MD_Constraints On-lineResource.description

115 ESRI Metadata Metadata elements not typically included within dataset/services metadata records Metadata element Published Document ID Input Source Modification Date Modification Time (issecured) (resourcetype) Example {C52B9923-6D4F-D123 D123-9F70- F511E2452AA9} false 005 Publication Source 0 Harvester Resource Type 0011 Live Geography Data and Network Maps 0022 Downloadable GeoCommunicatior Data 0033 Offline ArcCatalog Data 0044 Static On-line Map Form Images Metadata file identifier Can be added by metadata 0055 Document, XML Upload Other Documents maintenance organization 006 Applications 007 Geographic Services Metadata time stamp 008 Clearinghouses 009 Map Files MD_Constraints 010 Geographic Activities On-lineResource.description

116 ESRI Codelists What you get when you go to the link Resource Type 001 Live Data and Maps 002 Downloadable Data 003 Offline Data 004 Static Map Images 005 Document, Other Documents 006 Applications 007 Geographic Services 008 Clearinghouses 009 Map Files 010 Geographic Activities Where the metadata came from Publication Source 0 Harvester 1 Geography Network 2 GeoCommunicatior 3 ArcCatalog 4 On-line Form 5 XML Upload

117 Remaining ISO 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

118 New combined core 1. Dataset title 2. Dataset responsible party (originator, publisher) 3. Dataset topic category 4. Abstract describing the dataset 5. Dataset reference date (published) 6. Spatial representation type 7. Distribution format (use controlled vocabulary- code list) 8. DataSetURI 9. Lineage statement 10. Dataset language 11. Geographic location of the dataset (by four coordinates or by geographic identifiers) 12. MD_Contraints 13. Spatial Resolution 14. Additional extent information (vertical and temporal) 15. Reference system 16. Metadata language 17. Metadata character set 18. Metadata point of contact 19. Metadata file identifier 20. Metadata time stamp (include time) 21. On-line resource type

119 User requirement analysis Locate, evaluate, extract, employ Identification information Keywords may help refine search criteria in many situations Data quality information Is positional, temporal, or attribute accuracy; completeness, or consistency important in your user community? Content information Number of bands, features and attributes? Maintenance information Is update information important to your user community; for instance Navigation community Distribution information Will your community be using different distributors, formats, pricing fees?

120 New profile 1. Dataset title 2. Dataset responsible party (originator, publisher) 3. Dataset topic category 4. Abstract describing the dataset 5. Dataset reference date (published) 6. Spatial representation type 7. Distribution format (use controlled vocabulary- code list) 8. DataSetURI 9. Lineage statement 10. Dataset language 11. Geographic location of the dataset (by four coordinates or by geographic identifiers) 12. MD_Contraints 13. Spatial Resolution 14. Additional extent information (vertical and temporal) 15. Reference system 16. Metadata character set 17. Metadata point of contact 18. Metadata file identifier 19. Metadata language 20. Metadata time stamp (include time) 21. Keywords 1. Thesaurus name 22. Positional accuracy 23. Thematic accuracy 24. Coverage description/features and attribute reference 25. Maintenance and update frequency 26. Transfer size 27. Fees 28. On-line resource type

121 Title Metadata creation hints Title as descriptive as possible - should include as much information as possible! Topic, place, time, etc Topic Category select all topics covered by dataset a controlled keyword list producers and users can use Keywords support users in finding your data - broad enough narrow enough Keywords

122 Keywords Plasma, waves, flares mean different things to different people (sound waves, coastal waves, earthquake waves) Think broadly hydrology, water bodies, watercourses Think narrowly water quality, flow dynamics, sediment, etc

123 Title Metadata creation hints Title as descriptive as possible - should include as much information as possible! Topic, place, time, etc Topic Category select all topics covered by dataset like a controlled keyword list producers and users can use Keywords support users in finding your data - broad enough narrow enough terms Abstract as descriptive as possible remember some may extract keywords and use them in context Keywords Abstract Temporal extent don t confuse with publication or release date Geographic location use both bounding box coordinates and geographic identifiers

124 Profiles Section summary slide subset strict conformance Most interoperable with extensions conforming Less interoperable How much metadata is enough? Moderation is the best policy Developing your profile Review what others have done Address user requirements Be pragmatic Collecting metadata Be descriptive Be consistent Can a stranger find and understand your dataset/service?

125 Discovery Metadata and Portals

126 Metadata Portals Portal gateway, place of entry Producers Advertise, expose products Share information about holdings Provide an understanding of data and services Users Perform efficient searches by requirements Discover data and services Determine fitness for use Acquire access information A Web "supersite" that provides a variety of services including Web searching, news, white and yellow pages directories, discussion groups, online shopping and links to other sites. TechWeb Encyclopedia

127 GIS Portal Enables Faster discovery Direct access and use Collaboration for new data collection Improvement of data quality and coverage Organizes a Spatial Data Infrastructure

128 The Concept W3C Service Oriented Architecture* Service Service Requester Requester Client Find Find Bind Bind Interact Interact Service Description Service Service Broker Broker Publish Service Service Provider Provider Service Service Description *From Web Service Architecture, 14 Nov. 2002

129 Metadata Portal Service Architecture OGC Catalog Services (Z39.50 CS-W) Search Search Catalog Catalog and and Find Find Users Connect Connect and and Use Use Download Download and and use use OGC WMS, WFS, WCS, other services, data download, order, etc Portal OAI Protocol for Metadata Harvesting Publish GIS data and services Document in catalog ISO Metadata/ ISO Metadata XML Schema Implementation GIS Web Services Providers FTP GIS Data GIS Data GIS Data Providers GIS Data

130 GIS Portal Spatial Search & Navigation View Users Supporting Data Sets Gazetteer Thesaurus Portal Categories Category Data Index Map Partners (Service broker) Metadata Publishers- Data & Service Providers

131 Portal Architecture FGDC ISO IBM WebSphere Portal Single Sign-on and Personalization Publish Search Other JSR-168 Portlets Map Viewer JSR-168 WMS WFS/GML WCS ArcIMS WMC Open LS Gazetteer Apps CS-W Z39.50 WAF / XML OAI-PMH Metadata Harvester Natural Language Search Catalog Service GIS Portal Toolkit ESRI-Google Spatial Extender Google Search Appliance ArcIMS Open LS Gazetteer CS-W Z39.50 Google http OAI Metadata Catalog ArcSDE - RDBMS COTS & Standards Based ( Programmatic Connection )

132 New Enabling Technologies Portal Technology What s New Search Engine- Google JSR Spatial Toolkits Communities Marketplace New interoperability New standard Portlet building blocks GIS Centric Specialized Search Uniform View What this Means Web Standard Google-like like Personalized

133 Metadata fuels the GIS Portal Catalog Services Metadata Data Models Maps Data Sets Metadata documents describe content and relationships