PCGIAP Metadata Profile Survey & Resulting Draft ISO Metadata Profile for Asia and the Pacific ISO Metadata Profile for Asia and the Pacific Workshop 2008. 8.20 Kuala Lumpur, Malaysia Sang-Ki Hong Vice Chair, WG 2, PCGIAP Convenor,, WG10, ISO/TC211 1
About Metadata 2
What is Metadata? 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 3
Geographic Metadata Data about data Geographic area covered Currency Rules of use Positional accuracy Data dictionary Means of encoding Datum Map A Key interoperability technology Producer explain their product Users learn about products 4
Like this... actors title abstract Running time Regional code author Disc format rating language 5
Metadata in maps identification title scale Reference system producer date location symbols warning 6
Metadata Supporting Geographic Data and Services Life Cycle 7
Metadata Applications Locate Find Discover Structured searches vs. unstructured Evaluate Resolutions Quality Reputation Extract Order Download Employ Define Apply Use Understand geographic knowledge 8
Metadata UML Packages 9
Metadata Standard - 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 10
Metadata Standard - ISO 19115:2003 Contents Defines metadata elements; Provides a schema (UML); Establishes a common set of metadata terminology, definitions (data dictionary); Provides extension procedures 11
Metadata Standard - ISO 19115:2003 Recommended Core Metadata 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)? A point of contact to learn more about or order the dataset(who)? (M) Mandatory (M) Dataset title (M) Dataset reference date ( - ) Dataset responsible party (M) Geographic location of the dataset (by four coordinates or by geographic identifiers) (M) Dataset language (M) Dataset character set (M) 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 (M) Metadata language (M) Metadata character set (M) Metadata point of contact (M) Metadata date stamp 12
Metadata packages - ISO 19115:2003 13
Metadata data dictionary 14
15
DataIdentification details 16
About Profile 17
What is a Profile? Profile A standard tailored for a Community 18
Standardized Profiles - ISO 19106...set of one or more base standards or sub-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) Register Profiles Internationally Registered (ISP) Nationally Registered Published Profiles Formally within Community Informally within Organization 19
Profiles Regional, national & organizational Profiles Enable Interoperability Between Communities 20
Need for Asia Pacific Profile 8th PCGIAP(Permanent Committee on GIS Infrastructure for Asia and the pacific) meeting decided to implement the prototype of APSDI(Asia Pacific Spatial Data Infrastructure) clearinghouse. APSDI Clearinghouse is an environment that can facilitate access to geo-spatial data, products and services 21
History During 7 th PCGIAP Meeting, 2001-4,Tsukuba,Japana A task force for APSDI data node was formed Task: promoting the planning and implementation of APSDI spatial data clearinghouse. Started a pilot project Before 8 th PCGIAP Meeting, 2002-4,Brunei Darussalam Workshop on APSDI Clearinghouse (Hainan Islands, China, Nov. 2001); PCGIAP Metadata profile drafted; Guidelines for APSDI Clearinghouse Node Development drafted. 22
History (continued) Before 9 th PCGIAP meeting, 2003-7,Okinawa, Japan PCGIAP Metadata profile And a metadata entry tool named Mediator complying to this profile is developed and freely available. Guidelines for APSDI Clearinghouse Node Development finished and a reference prototype Implementation of APSDI Clearinghouse provided at http://nfgis.nsdi.gov.cn/apsdi Before 11 th PCGIAP Meeting, 2005-5,Bali, Indonesia Joint Workshop of WG1 and WG2,7-9 September 2004, Chengdu, China (Closed the pilot project and reinstituted the taskforce) ESRI GIS Portal Toolkit Workshop for PCGIAP, 6-8 April, 2005, Hong Kong, China (13 participants from 6 members; China, Indonesia, Japan, Korea, Nepal, Malaysia attended) 23
History (continued) 12 th PCGIAP & 17 th UNRCCAP, Tailand, 2006 Recommends PCGIAP encourage close collaboration between PCGIAP Working Group 2 with ISO/TC211 in the development of an ISO Metadata standard profile for Asia Pacific. 13th PCGIAP Meeting, June 2007 Seoul, Korea Metadata profile for AP Taskforce Coordinator: Prof. Sang-Ki Hong, Vice Chair of WG2 24
Recent Actions to make Asia Pacific Profile 13th PCGIAP Meeting, June 2007 Seoul, Korea Metadata profile for AP Taskforce (Coordinator: Prof. Sang-Ki Hong, Vice Chair of WG2) Use what has already been done by PCGIAP in the past Select latest ISO standards as the basis for this exercise Look at the profile already developed by the UN (UNGIWG) Connect the PCGIAP process with the one started by CODI and eventually PCIDEA Create a draft profile to be discussed among the members of PCGIAP Look at tools that could support the use of this profile Provide information and material to the members through the WG 2 web site Increase awareness through the organization of at least one workshop on metadata in the region Address the language issue (e.g.: glossary of terms, ISO) 25
Development of Asia Pacific Profile Selection of items from ISO19115:2003 Promotion of optional fields to mandatory Result of survey Other regional profile (NAP, LAMP, ANZLIC, INSPIRE & AFRICAN) Extension of code lists need to be worked Addition of values to existing code lists Addition of code lists 26
Development of Asia Pacific Profile Introduction of multilingual register need to be discussed Compliant to ISO19135:2005 on registers English and other languages Metadata items Code lists Register will be accessible on the Web - need to be worked XML document Web Services Web Browser 27
Survey Results 28
id name Obligation Ch+Vie+Mal+Hk VI I O 1 Metadata 1 - - File Identifier O 1 3 - Language C - 4 - Character Set C - 3 1 Parent Identifier - 2 2 Hierarchy Level - 2 2 Hierarchy Level Name - 2 2 contact M 2 2 - Date Stamp M 2 2 - Metadata Standard Name O 1 2 1 Metadata Standard Version O 1 2 1 Data Set URL 1 1 1 - - - Name - - - 2 Identification - 2 - citation M 2-2 abstract M 2 1 1 purpose 1 1 2 credit 1-2 status 1 2 1 Point Of Contact O 1 2 1 29
3 Data Identification - 2 - Spatial Representation Type O 2 2 - Spatial Resolution O 1 3 - language M 2 1 1 Character Set C - 2 2 Topic Category M 2 2 - Environment Description - 2 1 Extent 1 3 - Supplemental Information - - 3 - - - 4 Browse Graphic - 2 - File Name 1 1 2 File Description - 2 2 File Type - 1 3 - - - - - - 5 Keywords 1 1 - keyword O 3-1 Type 1 1 2 Thesaurus Name 1-2 - - - 30
Analysis of Existing Profiles 31
19115 African ANZLIC/ Core UNGIWG INSPIRE AP 1 Metadata point of contact M M M M M M 2 Metadata date stamp M M M M M M 3 Metadata language C C C C M C 4 Metadata character set C C C C C 5 Metadata file identifier O O M C M 6 Metadata standard name O C O C O 7 Metadata standard version O C O C O 8 Dataset title M M M M M M Abstract describing the 9 dataset M M M M M M 10 Dataset reference date M M M M M M 11 Dataset language M M M M C M 12 Dataset topic category M M M M M M 13 Dataset character set C C C M C 14 Geographic location of the dataset (by four coordinates or by geographic identifier) C M C M M M 15 Dataset responsible party O M O M M M 16 Spatial resolution of the dataset O O O O C O 32
17 Additional extent information for the dataset (vertical O O O N M O and temporal) 18 Spatial representation O M O O O type 19 Distribution format O M O N O 20 On-line resource O C O O M O 21 Lineage O O O O M O 22 Reference system O O O C O Additional Elements purpose (M) Metadata file parent identifier (C) Dataset Edition (O) Presentation Format (C) Purpose (O) Status (C) Keywords (O) Place Keyword (M) Browse Graphic FileName (O) Browse Graphic FileDescription (O) Browse Graphic FileType (C) Start Date (O) End Date (O) SupplementalInformation (O) Maintenance Frequency (C) Restrictions (C) Data quality scope code (O) Processing step description (O) Processing step date/time stamp (O) Data quality report result (O) Geometric ObjectType (C) Cell Geometry (O) Keyword (M) Conformity (M) Conditions applying to access and use (M) Limitations on public access (M) purpose (O) keywords (O) restrictions (O) contraints(o) Positional Accuracy (O) fees (O) 33
Draft AP Metadata Profile 34
Name Path Obligation 1 Metadata point of contact MD_Metadata.contact > CI_ResponsibleParty M 2 Metadata date stamp MD_Metadata.dateStamp M 3 Metadata language MD_Metadata.language C 4 Metadata character set MD_Metadata.characterSet C 5 Metadata file identifier MD_Metadata.fileIdentifier M 6 Metadata standard name MD_Metadata.metadataStandardName O 7 Metadata standard version MD_Metadata.metadataStandardVersion O 8 Dataset title MD_Metadata.identificationInfo > MD_DataIdentification.citation > CI_Citation.title M 9 Abstract describing the dataset MD_Metadata.identificationInfo > MD_DataIdentification.abstract M 10 Purpose MD_Metadata.identificationInfo > MD_DataIdentification.purpose O 35
11 Keywords 12 Dataset reference date MD_Metadata.identificationInfo > MD_DataIdentification > MD_Keywords MD_Metadata.identificationInfo > MD_DataIdentification.citation > CI_Citation.date O M 13 Dataset language MD_Metadata.identificationInfo > MD_DataIdentification.language M 14 Dataset topic category MD_Metadata.identificationInfo > MD_DataIdentification.topicCategory M 15 Dataset character set MD_Metadata.identificationInfo > MD_DataIdentification.characterSet C Geographic location of MD_Metadata.identificationInfo > MD_DataIdentification.extent > the dataset (by four 16 EX_Extent > EX_GeographicBoundingBox or coordinates or by EX_GeographicDescription.geographicIdentifier geographic identifier) M Dataset responsible 17 party MD_Metadata.identificationInfo > MD_DataIdentification.pointOfContact > CI_ResponsibleParty M Spatial resolution of 18 the dataset Additional extent 19 information for the dataset MD_Metadata.identificationInfo > MD_DataIdentification.spatialResolution > MD_Resolution.distance or MD_Resolution.equivalentScale MD_Metadata.identificationInfo > MD_DataIdentification.extent > EX_Extent.temporalElement > EX_TemporalExtent.extent O O Spatial representation 20 type MD_Metadata.identificationInfo > MD_DataIdentification.spatialRepresentationType O 36
21 Distribution format MD_Metadata.distributionInfo > MD_Distribution > MD_Format O 22 Fees MD_Metadata.distributionInfo > MD_Distribution > MD_StandardOrderProcess.fees O 23 On-line resource MD_Metadata.distributionInfo > MD_Distribution > MD_DigitalTransferOption.onLine > CI_OnlineResource O 24 Lineage MD_Metadata.dataQualityInfo > DQ_DataQuality.lineage > LI_Lineage O 25 Source MD_Metadata.dataQualityInfo > DQ_DataQuality.lineage > LI_Lineage.source > LI_Source or LI_Lineage.processStep > LI_prossStep O 26 Positional Accuracy MD_Metadata.dataQualityInfo > DQ_DataQuality.report > DQ_Element > DQ_Positional_Accuracy O 27 Reference system MD_Metadata.referenceSystemInfo > MD_ReferenceSystem.referenceSystemIdentifier > RS_Identifier O 28 Contraints MD_Metadata.metadataConstrants > MD_Constraints > MD_LegalConstraints O 37
Issues 38
What kind of metadata? Minimum metadata is minimally useful 39
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 fee? 40
Level of Constrain Elements Mandatory vs. Optional Should all data be at least optional? Don t eliminate any element from base standard. Does it against the idea of profile? ISO mandatory elements are constrained by the profiling rules. How many mandatory elements should we have? Absolutely minimum? or All elements that we think suitable? 41
Scope of AP profile Which type do we need? Wide range profile : minimum/core set + full regional profile? Narrow range profile just one profile (with or without minimum set)? Base Standard 42
Further works things to do Code lists Expansion Implementation issues Services metadata Multiple language Issues AP Profile Documentation We need a dedicated Project Team! 43
Thank you for your attention! Contact info: skhong@anyang.ac.kr 44