1 / 33

Comprehensive Guide to AIXM Metadata Requirements and Models

Understand AIXM metadata, compliance with ISO standards, main sources like ISO 19115, and differences with AIXM metadata model. Learn about metadata layers and profiles, including new elements and constraint roles.

booherl
Télécharger la présentation

Comprehensive Guide to AIXM Metadata Requirements and Models

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. AIXM 5 Metadata

  2. Requirements for AIXM Metadata • AIXM Metadata Model • Examples

  3. Metadata • Metadata is structured information about data • It provides information about a particular dataset, which can be a message or a single feature • the origin of the data, the citation for the resources, an abstract, the purposes, credits, the status and points of contact

  4. AIXM Requirements • AIXM has two high-level requirements: • Compliance with the ISO 19100 series • Coverage for AIXM specific needs • CRC • Integrity

  5. Main Sources • International Standardization Organization (ISO) • 19115 (Geographic information – Metadata) and Corrigendum • 19139 (Geographic information – Metadata – XML Schema Implementation) • ISO 19139 = XML Schema based encoding for ISO 19115 metadata • Defines geographic metadata XML encoding (gmdXML)

  6. Main Sources • ISO 19115 UML model online: http://www.isotc211.org/ • ISO 19139 schema available at: http://www.isotc211.org/2005/

  7. Suitability of ISO 19115 • ISO 19115 defines over 400 metadata elements • Answers: • Does a dataset on a specific topic exist (‘what’)? • For a specific location (‘where’)? • For a specific date or period (‘when’)? • A point of contact to learn more about or order the dataset (‘who’)? • Describes metadata for catalogue services, rather than for recurrent messages (e.g. AIXM messages)

  8. Requirements for AIXM Metadata • AIXM Metadata Model • Examples

  9. AIXM Metadata Model • AIXM metadata model is based on ISO19115 • However, it is not intended to be a substitution for ISO 19115 • It does not completely conform to ISO19115

  10. Differences • The AIXM metadata model: • Does not include topic category as mandatory • Includes extended metadata elements required to describe aeronautical information exchange data

  11. Metadata Layers • The AIXM Metadata model provides Metadata at three levels: • For the entire dataset or package, i.e. AIXM message • For each feature within a message • For each timeslice within a feature

  12. Metadata Layers

  13. AIXM Metadata Profile • The profile has 6 models: • 1. Metadata for the AIXM message • 2. Metadata for an AIXM feature • 3. Metadata for an AIXM feature timeslice • 4. Constraint information • 5. Citation and Responsible Party information • 6. Data Quality information

  14. Metadata to Include with AIXM Message • The classes named using prefix MD or CI or DQ indicate inclusion of, or association with, ISO19115 classes

  15. New Metadata Elements • cyclicRedundancyCheckMessage is the value or string of alphanumeric characters usually generated by a cyclic redundancy check (CRC) algorithm. • Best practice recommends that the algorithm consider all tags and data elements within the feature data • When the data receiver applies the CRC algorithm to the feature data, a different CRC indicates that a tag or data element within the feature data has been changed since the sender generated the original CRC • noteCRCMessage provides the ability to relay information to the data receiver if necessary about the CRC calculation • Using this data element, the sender can document the tags and data elements considered in the cyclic redundancy check

  16. Modified Metadata Elements • The IdentificationMessage outlines the elements to include as it pertains to the data in the AIXM message • The relationships with MD_Identification is labelled restriction since the AIXM class is a subset of and/or includes varied attributes • IdentificationMessage and MessageMetadata are related to MD_Constraints

  17. Constraint Information Metadata

  18. New Constraint Roles • Constraints manage the rights to information including restrictions on access and use. • messageConstraintInfo describes the constraints • If any of the features within the message have attributes with classification codes such as restricted, confidential, top secret, etc., the classification code for the feature captures the highest classification code among the attributes • messageConstraintInfo captures the highest classification code among the features • metadataConstraintInfo describes any restrictions on the access and use of the metadata for the AIXM message • Classification code for this role is determined by the sender or data producer • Both are similar to the role metadataConstraints relating MD_Metadata to MD_Constraints in ISO19115

  19. Metadata to Include About an AIXM Feature • Similar to metadata on a Message: • cyclicRedundancyCheckFeature • noteCRCFeature

  20. Metadata to Include About an AIXM Feature Timeslice

  21. Metadata Elements • The FeatureTimeSliceMetadata class includes elements: • to reference the party responsible for the metadata information • the date on which the metadata was compiled. • FeatureTimeSliceMetadata contains five new metadata elements not defined in ISO19115: • measureClass • measEquipClass • dataIntegrity • horizontalResolution • verticalResolution

  22. Citation and Responsible Party Information Metadata

  23. Similar to ISO19115 • Describes authoritative reference information • ResponsibleParty is essentially the same as ISO19115 CI_ResponsibleParty • except two new data elements: • systemName as a place to describe the responsible system, i.e., database or repository • digitalCertificate, a field to capture an electronic signature authentication information • contactInfo is associated with Contact not CI_Contact • The Contact class differs from ISO19115 CI_Contact class. • address is the same as in ISO19115 which maps to the CI_Address class • phone maps to the class Telephone not to CI_Telephone

  24. Data Quality Information Metadata

  25. Description • Describes the quality of data within a feature timeslice. • The quality of data may vary by attribute or set of attributes. • ISO19115 data element attributes is used to list the attributes to which the report applies. • report maps to class DataQualityElement associated with DQ_Element which contains • ISO19115 elements evaluationMethodDescription and pass. • a new metadata element evaluationMethodName giving the name of the evaluation method used on the given attributes (AirMAT-AICM metadata harmonization)

  26. Requirements for AIXM Metadata • AIXM Metadata Model • Examples

  27. Optional • It is optional to include metadata within an AIXM message or feature timeslice • If it is included, it should conform to the profile • Metadata can be easily captured and it is highly recommended that it be sent with an AIXM message

  28. Mandatory Message Metadata <MessageMetadata> <dateStamp>2007-09-11T16:00:00Z</dateStamp> <contact> <individualName>ScottWilson</individualName> <positionName>AIXM Development Support</positionName> <role>distributor</role> </contact> <messageIdentificationInfo> <abstract>“baseline” timeslice valid 01 Jan 2008</abstract> <language>en</language> </messageIdentificationInfo> </MessageMetadata>

  29. Feature Timeslice Metadata <FeatureTimeSliceMetadata> <dateStamp>2007-09-11T16:00:00Z</dateStamp> <contact> <organizationName>EUROCONTROL</organizationName> <positionName>AIXM Development</positionName> <role>originator</role> </contact> <featureIdentificationInfo> <abstract>Donlon antenna</abstract> <citation> <title>Metadata study</title> <date>2007-09-10T17:00:00Z</date> <dateType>revision</dateType> </citation> </featureIdentificationInfo> </FeatureTimeSliceMetadata>

  30. Current Status • The AIXM Metadata Model has not been applied to the XML Schema in Release Candidate 2 • RC2 uses the ISO 19139 Schemas • Release Candidate 3 will consider the adoption of the profile

  31. Next Steps • The final AIXM 5 release will provide guidelines on how certain metadata fields shall be used • This will lead to harmonised encodings of certain information, such as • accountable source, • date when the information was issued, • contact details, etc.

  32. Metadata Forms • http://geonetwork-opensource.org/

  33. Thank you

More Related