North American Profile for Geospatial Metadata status report

Transcription

1 North American Profile for Geospatial Metadata status report David Danko ESRI, Washington, DC Jean Brodeur Natural Resources Canada, Centre for Topographic Information, Sherbrooke

2 What is a profile? ISO Standardized Profiles...set of one or more base standards or sub-sets sets of base standards that 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

3 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

4 Regional, national, & organizational profiles Communities with a common need for metadata ISO19115:2003 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

5 The situation today Directory Information Describing Digital Geo-referenced Data Sets, Canadian General Standards Board, July 1994, Ottawa. Content Standard for Digital Geospatial Metadata, Federal Geographic Data Committee, June 8, 1994, Washington DC.

6 The goal CAN/CGSB USA CSDGM North American Profile Geospatial Metadata Based on ISO 19115/19139

7 Co-located Meetings Parallel Development North American Profile of ISO Metadata MOU between Canada and the USA North American Profile of ISO Metadata

8 Participants Canada Natural Resources Canada Ontario Ministry of Natural Resources CGSB-CoG CoG members USA Federal Geographic Data Committee NPS, USGS (BRD, Geography, Geology), NJ, BLM, Nature Serve, NOAA INCITS-L1 members NAP Metadata Working Group Potential Mexican involvement

9 Meetings & Schedule Sherbrooke,, QC Sept 2005 Columbus, OH Dec 2005 Vienna, VA March 2006 Denver, CO Sept 2006 Future meetings Initial draft document Sept 2006 Submit to standards bodies Dec 2006?

10 Requirements analysis Approach Past experience with metadata standards implementation Cross-table development (FGDC-ISO 19115) Modified UML Promote options to obligations Extended codelists Added codelists

11 Crosswalk FGDC name Identification Information (Section 1) 1.1 Citation 1.2 Description Abstract Purpose Supplemental Information 4.1 Horizontal Coordinate System Definition Geographic Latitude Resolution Longitude Resolution Geographic Coordinate Units Planar Dialup Instructions 6.5 Custom Order Process ISO name MD_Metadata.identificationInfo.MD_Identification MD_Metadata.identificationInfo.MD_Identification.citation --- MD_Metadata.identificationInfo.MD_Identification.abstract MD_Metadata.identificationInfo.MD_Identification.purpose MD_Metadata.identificationInfo.MD_DataIdentification.suppl ementalinformation --- MD_Metadata.referenceSystemInfo.MD_ReferenceSystem.ref erencesystemidentifier.rs_identifier.code ( = FGDC Geographic) NO MATCH NO MATCH NO MATCH --- Deprecate Comment Compound element, unnecessary mapping Compound element, no mapping necessary Compound element, no mapping necessary 7.7 Metadata Time Convention Address Type Deprecate Deprecate

12 Modified UML <<Abstract>> MD_SpatialRepresentation (from Spatial representation information) +spatialrepresentationinfo 0..* NAP-Metadata: { (identificationinfo.spatialrepresentationtype = "vector") or (identificationinfo.spatialrepresentationtype = "grid") or (identificationinfo.spatialrepresentationtype = "tin") implies count referencesysteminfo >= 1) } MD_ReferenceSystem (from Reference system information) MD_MetadataExtensionInformation (from Metadata extension information) 0..* +metadataextensioninfo DQ_DataQuality (from Data quality information) 0..* +referencesysteminfo 0..* MD_Distribution (from Distribution information) <<Abstract>> MD_ContentInformation (from Content information) +dataqualityinfo +distributioninfo contentinfo 0..* +portrayalcatalogueinfo MD_PortrayalCatalogueReference 0..* (from Portrayal catalogue information) MD_Metadata + fileidentifier[0..1] : CharacterString + language : CharacterString + characterset : MD_CharacterSetCode = "utf8" + parentidentifier[0..1] : CharacterString + hierarchylevel[1..*] : MD_ScopeCode = "dataset" + hierarchylevelname[1..*] : CharacterString + contact[1..*] : CI_ResponsibleParty + datestamp : Date + metadatastandardname : CharacterString = "NAP-Metadata" + metadatastandardversion[0..1] : CharacterString + dataseturi[0..1] : CharacterString + locale[1..*] : PT_Locale 0..1 MD_MaintenanceInformation (from Maintenance information) +metadatamaintenance +identificationinfo 1..* <<Abstract>> MD_Identification (from Identification information) 0..* +resourcemaintenance +applicationschemainfo 0..* MD_ApplicationSchemaInformation (from Application schema information) +metadataconstraints 0..* 0..* +resourceconstraints MD_Constraints (from Constraint information) NAP-Metadata: + language: mandatory, composed of a language code (ISO639-2/T) and a 3-digit numeric country code (ISO3166-1) + characterset: "utf8" mandatory + hierarchylevel: mandatory + hierarchylevelname: mandatory + metadatastandardname: "NAP-Metadata" mandatory + locale: mandatory Conditional statements: language: documented if not defined by the encoding standard characterset: documented if ISO not used and not defined by the encoding standard parentidentifier: documented if the hierarchy of a higher level exists

13 ISO Validation NAP Validator Afternoon NAP.xml Recommended Core Metadata Lake Okeechobee SoundingsNAP.xml only 12 mandatory metadata elements Lake Okeechobee Environmental Impact data- NAP.xml Full comprehensive metadata comprised of over 300 metadata elements

14 North American Profile of ISO Metadata North American Profile of ISO Metadata