# Presentation: 580321

## The ISO/TC 211Geographic information/GeomaticsMetadata StandardsStatus Report

*... **building the foundation of the geospatial infrastructure, brick by brick ...*

## The goal of ISO/TC 211...

- ... is to develop a family of international standards that will
- support the understanding and usage of geographic information
- increase the availability, access, integration, and sharing of geographic information, enable inter-operability of geospatially enabled computer systems
- contribute to a unified approach to addressing global ecological and humanitarian problems
- ease the establishment of geospatial infrastructures on local, regional and global level
- contribute to sustainable development

## Scope of ISO/TC 211

- Standardization in the field of digital geographic information.
- This work aims to establish a structured set of standards for information concerning objects or phenomena that are directly or indirectly associated with a location relative to the Earth.
- These standards may specify, for geographic information, methods, tools and services for data management (including definition and description), acquiring,  processing, analyzing, accessing, presenting and transferring such data in digital/electronic form between different users, systems and locations.
- This work shall link to appropriate standards for information technology and data where possible, and provide a framework for the development of sector-specific applications using geographic data.

## Color legend:DIS, FDIS, IS

**ISO 19101:2002 - Reference model**
- ISO 19102 – Overview - **deleted**
- ISO/TS 19103 - Conceptual schema language
- ISO 19104 - Terminology
**ISO 19105:2000 - Conformance and testing**
- ISO 19106 - Profiles
**ISO 19107:2003 - Spatial schema**
**ISO 19108:2002 - Temporal schema**
- ISO 19109 - Rules for application schema
**ISO 19110 – Methodology for feature cataloguing**
**ISO 19111:2003 - Spatial referencing by coordinates**
**ISO 19112 - Spatial referencing by geographic ****	****	****identifiers**
**ISO 19113:2002 - Quality principles**
**ISO 19114 - Quality evaluation procedures**
**ISO 19115:2003 – Metadata**
**ISO 19115-2 – Metadata – Part 2: Extensions for Imagery and Gridded Data**
- ISO 19116 - Positioning services
- ISO 19117 – Portrayal
- ISO 19118 - Encoding
- ISO 19119 - Services
**ISO/TR 19120:2001 - Functional standards**
- ISO/TR 19120/Amd. 1 – Functional standards – Amendment 1

**ISO/TR 19121:2000 Imagery and gridded data**
- ISO/TR 19122 - Qualifications and certification 		of personnel
- ISO 19123 - Schema for coverage geometry and 		functions
**ISO/RS 19124 - Imagery and gridded data ****	****	****	****components**
- ISO 19125 - Simple feature access – Part 1-3
- ISO 19126 - Profile - FACC Data Dictionary
- ISO 19127 - Geodetic codes and parameters
- ISO 19128 - Web Map Server Interface
- ISO 19129 - Imagery, gridded and coverage data		framework
- ISO 19130 - Sensor and data model for imagery		and gridded data
- ISO 19131 - Data product specification
- ISO 19132 - Location based services possible		standards
- ISO 19133 - Location based services tracking		and navigation
- ISO 19134 - Multimodal location based services		for routing and navigation
- ISO 19135 - Procedures for registration of		geographic information items
- ISO 19136 – Geography Markup Language (GML)
- ISO 19137 -  Generally used profiles of the spatial schema and of similar important other schemas
- ISO 19138 – Data quality measures
- ISO 19139 – Metadata – Implementation specification
- ISO 19140 – Technical amendment to the ISO 191** Geographic information series of standards for harmonization and enhancements

- Color legend:DIS, **FDIS, ****IS**

## What is metadata used for?

- Locate: Find or Discover
- Evaluate: Restrictions, Quality, and Reputation
- Extract: Order or Download
- Employ: Apply and Use

## Major Metadata StandardsUsed in the Initial Development of ISO 19115

- Content Standards for Digital Geospatial Metadata, FGDC, June 1994
- Application Profile for the Government Information Locator Service (GILS), FIPS PUB 192, December 1994
- Proposed Framework for Core Metadata Elements (ANZLIC), Australia and New Zealand, November 1995
- Directory Information Describing Digital Geo-Referenced Data Sets, Canada, July 1994
- Geographic Information - Data Description - Metadata, (CEN 287), European Committee, January 1996
- IHO Transfer Standard for Digital Hydrographic Data (IHO S-57), October 1995
- The Digital Geographic Information Exchange Standard (DIGEST), January 1994
- ASTM Section D18.01.05, various dates, Spatial metadata content Standards for geographic information systems, catalogs, and data exchange
- Dublin Metadata Core and Z39.50, February 1998
- Spatial Data Transfer Standard (SDTS), FIPS 173, 1992
- US Machine Readable Cataloging (MARC)

**Notes:**
The ISO 19115 is the new metadata standard for the geospatial and imagery domain.  Many previous metadata standards, including the FGDC metadata standard, went into the development of 19115.  The major ones are listed here.

## What is ISO 19115:2003?

- “ Identifies the metadata required to describe digital geographic data. Metadata is applicable to independent datasets, aggregations of datasets, individual geographic features, and the various classes of objects that compose a feature. Metadata shall be provided for geographic datasets and may, optionally, be provided for aggregations of datasets, features, and attributes of features.”

## How is ISO 19115:2003 Organized?

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

## 19115:2003 Organization – Metadata Entity Set 

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

-  The language used to specify the metadata
-  The character set used to specify the metadata
-  The level of data to which the metadata applies
-  A point of contact for the metadata
-  A date the metadata was produced
-  The metadata standard that is used, including version information
-  A unique identifier by which this data can be referenced

## 19115:2003 Organization – Identification

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

-  An abstract that provides a narrative summary of the content
-  A purpose statement that describes the intentions for the development of the resource
-  The current status of the resource
-  A point of contact for the resource
-  The spatial representation type (e.g., vector, grid, tin, video)
-  The spatial resolution of the dataset (e.g., 1:50K)
- The language and character set of the data
- The topic category of the data (e.g., transportation, hydrography, farming)

## 19115:2003 Organization – Extent

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

-  The spatial extent of the dataset as a:
- Box
- More advanced spatial object
- Geographic Identifier
- The temporal extent of the dataset
- The vertical extent of the dataset

## 19115:2003 Organization – Reference System

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

- Reference System Identifiers
- Projection Identifiers and Parameters
- Ellipsoid Identifiers and Parameters
- Datum Identifiers

## 19115:2003 Organization – Spatial Representation

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

-  Vector Spatial Representation Information:
- Topology Level
- Geometric Object descriptions and counts (e.g. curves, points, surfaces, solids)
- Grid Spatial Representation Information:
- Number of dimensions
- Cell Geometry (point or area)
- Georectified Information
- Check Point Descriptions
- Corner Points
- Transformation Dimension Description
- Pixel Orientation (center, lower left, lower right, etc)
- Georeferenceable  Information
- Control Point Information
- Orientation Parameters
- Georeferenced Parameters

## 19115:2003 Organization – Data Quality

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

-  The scope to which the data quality information applies
- Lineage information
- Source information
- Process information
- Quality information
- Positional Accuracy
- Temporal Accuracy
- Thematic Accuracy
- Completeness
- Logical Consistency

## 19115:2003 Organization – Application Schema

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

-  The name of the application schema used
- The schema language used
- The constraint language used in the application schema
- The application schema provided as an ASCII file
- The application schema provided as a graphics file
- The application schema provided as a software development file

## 19115:2003 Organization – Maintenance

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

-  Maintenance and update frequency (e.g., continual, daily, weekly, asNeeded, irregular)
- Date of next update
- Update scope  (e.g., attribute, dataset, software, tile, series, feature)
- Contact
- User defined maintenance frequency

## 19115:2003 Organization – Portrayal Catalogue

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

-  Portrayal Catalogue Citation

## 19115:2003 Organization – Constraint

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

- Use Limitations
- Legal Constraints
-  Access
-  Use
-  Other
- Security Constraints
-  Classification
-  Classification System
-  Notes
-  Handling Description

## 19115:2003 Organization – Content

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

-  Feature Catalogue Description
- Language
- Feature Types
- Coverage Description
- Image Description
- Illumination Elevation Angle
- Image Condition (e.g., cloud, fog, blurred, shadow)
- Image Quality
- Processing Level
- Range Dimension
- Band
- maxValue
- minValue
- Tone Gradation
- Scale Factor

## 19115:2003 Organization – Citation and Responsible Party

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

-  Citation
- Title
- Date
- Edition
- Identifier
- ISBN
- Presentation form (e.g., imageDigital, mapDigital, documentHardcopy)
- Responsible Party
- Contact
- Online Resource
- Address
- Series
- Date

## 19115:2003 Organization – Distribution

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

-  Format
- Name
- Version
- Specification
- File Decompression Technique
- Digital Transfer Options
- Distributor
- Standard Order Process
- Fees
- Turnaround
- Ordering instructions

## 19115:2003 Organization – Metadata Extension

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

-  Extended Element information
- Name
- shortName
- domainCode
- Definition
- Obligation
- Condition
- dataType
- Max Occurrence
- Parent entity
- Rule
- Rationale
- source

## ISO 19115:2003 Real World Example 1

- Metadata about a **dataset**:
-  When the dataset was produced – 1997 May 23
-  The geographic location of the dataset – Middle East
-  A text description of the dataset - 1:4,500,000 Middle East Graphic
-  The distribution format of the dataset - Hi-Res .JPG (300dpi)
-  A point of contact if you have questions about the dataset – feedback@nima.mil

## ISO 19115:2003 Real WorldExample 2

- * Image generated with ESRI’s ArcGIS using the GreenValley sample project provided in the Getting Started section of version 8.2

- Metadata about **particular features**:
-  High-level geographic data thematic classification -  farming
-  Revision date if these features were modified on a date different than the dataset to which they belong – 1998 Sept 23
-  Data completeness of this particular feature layer – 80%

## ISO 19115:2003 Real WorldExample 3

- Metadata related to a **coordinate reference system**:
-  Ellipsoid Parameters
-  Semi-Major Axis = 63781370.0
-  Axis Units = meters
- Flattening Ratio = 1/298.257223563
- Code Space =  WGS 84

## What is ISO 19115 Part 2?

- Title: Geographic Information - Metadata - Part2: 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

## How is ISO 19115 Part 2 Organized?

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

## 19115 Part 2 Organization – Imagery Data Quality

- Data quality  information - Imagery

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

-  Processing Information:
- Run History/ Processing History/ Processing Information
- Software Reference
- Procedure Description
- Processing Documentation
- Command Line Parameters
- Algorithm Information
- Description
- Change History
- Peer Review
- Source Information
- Input Level
- Input Dataset

## 19115 Part 2 Organization – Imagery Spatial Representation

- Spatial representation information  -Imagery

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

-  Georeferencing Description
-  Instrument Parameters
- Position
- Rotation sequence
- Reference to Sensor Orientation
- Control Point Information
- Type
- Origin
- Accuracy
- Use
-  Cell Description
- groundShape
- corssTrackMotion

## 19115 Part 2 Organization – Imagery Identification

- Identification information  - Imagery

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

-  Acquisition Information
-  Instrument Identification
- Name
- Identifier
- Platform Identification
- Identifier
- Description
- Sponsor
- Reference to Platform Information
- Mission Identification
- Name
- Start date
- End date
-  description

## 19115 Part 2 Organization – Imagery Extent Information

- Extent information - Imagery

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

-  Vertical Extent Location
- Minimum Location
- Maximum Location

## 19115 Part 2 Organization – Imagery Content Information

- Content information - Imagery

- Metadata entity set

- Identification

- Constraint

- Maintenance

- Spatial representation

- Reference system

- Content

- Distribution

- Metadata extension

- Application schema

- Portrayal catalogue

- Data quality

- Extent

- Citation and responsible party

- Units of Measure

-  Sensor
- Collector Type (frame, pushbroom, panoramic, radar, etc.)
- Description
- Reference
- Sensor Type
- Frame Camera
- Scan
- Band
- Boundary definition
- Quality
- Spectral resolution
- Scaling
- Polarization characteristics
- Image
- Aerotriangulation reference
- Local elevation angle
- Local azimuth angle
- nadir

## ISO 19115 Part 2 Real WorldExample 1

- Platform Information
- identifier - to be defined by user community
- description - Unmanned Aerial Vehicle
- name - Global Hawk UAV
- shortName – Global Hawk
- serialIdentifier - Air Vehicle No. 4
- sponsor – US Air Force
- Mission Information
- identifier – to be defined by user community
- name - Linked Seas 00
- description - Provided direct support to amphibious operations in a joint-force environment involving air, sea, sub-surface and land-based assets
- startDate – 1 May 2000
- completionDate – 12 May 2000

## ISO 19115 Part 2 Real WorldExample 2

- The format for specifying the exacting details of the platform are defined in ISO 19130 and included by reference in the metadata:
- Flight Protocol information
- Flying Height
- GPS information
- Aircraft Orientation
- Roll
- Pitch
- Yaw
- Heave
- Surge
- Sway
- Heading
- Velocity in x, y and z
- Position information in x, y and z

## ISO 19115 Part 2 Real WorldExample 3

- ISO 19115 Part 2 Real World*Example 3*

- Processing Information:
- Software Reference - VICAR
- Procedure Description - Topographic shading derived from the SRTM elevation model was added to the Landsat image, with a false sun illumination from the left (southwest).
- Processing Documentation - http://www-mipl.jpl.nasa.gov/vicar/vicar290/html/index.html
- Command Line Parameters - F2 |RUNTYPE=BATCH| A.DAT B.DAT (1,1,100,100) FUNCTION="2*IN1" 'HALF

**Notes:**
Santa Barbara Coastline 

## What is ISO 19139?

- “*“**Given the abstract nature of the ISO 19115 specification, the actual execution of geographic information metadata could vary based on the interpretation of the metadata producers.  In an attempt to facilitate the standardization of implementations, this comprehensive **dataset** **metadata implementation specification provides **single UML interpretation** and **XML schema** for carrying out the ISO 19115 metadata standard.  This specification is meant to enhance interoperability by providing a common specification for describing, validating and exchanging metadata about **geographic datasets**.”*

## What is ISO 19139?

**Exact implementation specification** for creating an XML Instance document for a **dataset** that is 19115 compliant

- * Image generated with ESRI’s ArcGIS using the GreenValley sample project provided in the Getting Started section of version 8.2

## Organization of ISO 19139

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

**Notes:**
creating a latitude element that is -90> latitude > 90 instead of just using a real or decimal
creating a non-null string type that forces the length of the string to be greater than 0

## Other uses for ISO 19139

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

## Points of Contact

-  John Eller, NIMA_[ellerj@nima.mil](mailto:ellerj@nima.mil)_
- Dave Danko, ESRI
- 	_[ddanko@esri.com](mailto:ddanko@esri.com)_
- Lara Bordick, NGIT_[lara.bordick@ngc.com](mailto:lara.bordick@ngc.com)_
- _[http://metadata.](http://metadata.dgiwg.org/)__[dgiwg](http://metadata.dgiwg.org/)__[.org](http://metadata.dgiwg.org/)_

## Thank you !

***Questions?***

## Backup Slides

## What does ISO 19115:2003 include?

- Introduction
- References
- Terms (not defined elsewhere in the ISO 191** series)
- UML models – *including codelists*
- Core metadata list
- Data Dictionary
- Descriptions of *extensions* and *profiles*
- Abstract test suite
- Dataset Metadata application profile
- Extension methodology (informative only)
- Metadata implementation (informative only)
- Hierarchical levels of metadata (informative only)
- Implementation examples (informative only)
- Multilingual support for free text metadata elements (informative only)

## ISO 19115 Part 2Who’s doing it?

- US
- National Imagery and Mapping Agency (NIMA)
- NASA
- Joint Interoperability Test Command (JITC)
- ESRI
- Lockheed Martin Corporation
- Environmental Protection Agency (EPA)
- Canada -*Natural Resources Canada, Conseil du Trésor du Québec*
- Saudi Arabia - *King Abdulaziz City for Science and Technology*
- South Africa - *National Spatial Information Framework*
- Thailand - *Geo-Informatics and Space Technology Development Agency** *
- UK - *BP Exploration*
- DGIWG (L)
- CEOS/WGISS (L)
- ICAO (L)

## ISO Documents used in the Development of 19115

- ISO 639 (all parts), *Code for the representation of names of languages*
- ISO 690:1996, *Documentation — Bibliographic references — Content, form and structure*
- ISO 3166 (all parts), *Codes for the representation of names of countries and their subdivisions*
- ISO 4217:1995, *Codes for the representation of currencies and funds*
- ISO 8601:1987, *Data elements and interchange formats — Information interchange — Representation of dates and times*
- ISO 8859 (parts 1 to 15), *Information technology ― 8 bit single byte coded graphic character sets*
- ISO 8879, *Information processing ― Text and office systems ― Standard Generalized Markup Language (SGML)*
- ISO/IEC 10646-1, *Information technology ― Universal Multiple-Octet Coded Character Set (UCS) ― Part 1: Architecture and Basic Multilingual Plane*
- ISO/IEC 11179 (all parts), *Information technology ― Specification and standardization of data elements*
- ISO 23950:1998, *Information and documentation — Information retrieval (Z39.50) — Application service definition and protocol specification*

**Notes:**
The ISO 19115 is the new metadata standard for the geospatial and imagery domain.  Many previous metadata standards, including the FGDC metadata standard, went into the development of 19115.  The major ones are listed here.

## The Strategy“Shrink-wrapping the “After-Next””

- On the international front...**Participate in the development of international standards, and use standards adopted or adapted from internationally accepted standards to the greatest extent possible.**
- On the coalition, DoD and IC front** ... Adopt and **_[profile](slide31.xml)__ international standards to a level consistent with the need to share data._
- On the national front** ... Adopt and profile international standards to meet National objectives and protect current investments in existing data.**
- At the NIMA level** ... Adopt and profile the National & coalition level standards to meet NIMA objectives that protect investments in existing data and systems and achieves a high degree of interoperability and flexibility for future requirements.**

**Notes:**
NIMA’s strategy for migrating from proprietary government and military standards to International consensus based standards

         Any user community (not just NIMA or coalition forces) can use GML (also known as ISO 19136) to encode spatial data in XML.  Essentially this standard defines the geometries, topologies, etc. for describing spatial objects. 
         Any user community can use ISO 19139 to encode their geospatial metadata.  This is distinctly different then GML although GML expects to have a metadata schema (usually ISO 19139) included in an application schema.  This means that when a geospatial dataset is transferred in XML format all the “data” will comply to GML and all the “metadata” will comply to ISO 19139
         Specific user community’s needs will not all be met by these two standards.  These user communities will need to build “profiles” of the standards.  It is my understanding that this is where the IC Metadata Working Group comes into the picture.  Obviously NIMA has security and legal marking restrictions that aren’t of concern to ISO and OGC so we look to the IC Metadata Working Group to help us capture the XML encoding to properly support NIMA and coalition needs in this area.
This “extra” information is then added to the XML schemas of ISO 19139
to make the DGIWG or NIMA profiles.  The mechanism by which this
“extending” is done is illustrated in Annex G of the latest draft of ISO
19139
So essentially, when all is said and done, there will be a DGIWG profile or NIMA profile for the XML encoding of a dataset (to include spatial objects, metadata and community specific information).  It will comply with the guidelines developed by all the groups that you list and will result in encoded data that is understandable to COTS products but still supports the unique requirements of our user community. 

## Creating the dataset profile

- Create Constrained Types
- Create External types
- Replacing ISO 19115 classes with other ISO 19100 Series classes
- Converting Sequences to Implementation Types
- Renaming Abstract types
- Altering Association Types
- Replacing Associations
- Isolate the ISO 19115 package of the Abstract UML Model
- Removal of classes and elements not relevant for dataset implementations
- Add domain codes to the codelist and enumerations

## Exceptions in the automation to XML

- Labeling some items “SimpleType”
- Number, Integer, Decimal, Vector, Real, Character, CharacterString, Date, Time, DateTime, Boolean
- Allowing references to Citation classes
- Using XML Schema Temporal implementations
- Utilizing GML for spatial Objects
- Removing Binary Elements
- Reproducible Ordering

## How do we build ISO 19139

- Harmonized ISO Model

- Implementation
- UML Model
- (ISO 19139)

- Intermediate
- XML Description

- Transformation with Rational Rose Scripts

- Metadata
- XML Schema (s)

- XSLT
- Transformation
- Stylesheet

- Create Implementation Model
- of Dataset Profile
-  with Rational Rose Scripts

## The rules for the transformation(Based on ISO 19118)

- Class: All classes are transformed into an *xs:complexType* with a *name* attribute equal to the class name in the UML.  All classes contain an *xs:sequence* element that contains the XML implementations of its attributes and associations.
-    Additionally all classes are transformed into an *xs:element* with a *name* attribute equal to the class name and the *type* attribute equal to the *xs:complexType name* attribute described above.  The *type* attribute for this *xs:element* contains the proper namespace reference notation.

## The rules for the transformation(Based on ISO 19118)

- The rules for the transformation*(Based on ISO 19118)*

- Class:

## The rules for the transformation(Based on ISO 19118)

- Attributes of classes: All attributes of classes are transformed, as described in section A.5.3.1 of ISO 19118, into an xs:element with a name attribute equal to the attribute name in the UML.  The type attribute of the xs:element is equal to the type of the element in the UML as its class is transformed per the previously described rule.  The xs:element resides within the xs:sequence of the containing class as described in the previous rule.
-    The maxOccurs and minOccurs attributes of the xs:element are set based on the multiplicity stated for the attributes in the UML profile

## The rules for the transformation(Based on ISO 19118)

- The rules for the transformation*(Based on ISO 19118)*

- Attributes of classes:

## The rules for the transformation(Based on ISO 19118)

- Unions: All classes with the Stereotype Union are transformed into an xs:complexType with a name attribute equal to the class name in the UML.  All classes contain an xs:choice element that contains the XML implementations of its attributes in an identical manner to attributes in regular classes except for being located within the xs:choice tag instead of the xs:sequence tag.
-    Additionally all classes with the Stereotype Union are transformed into an xs:element with a name attribute equal to the class name and the type attribute equal to the xs:complexType name attribute described above.  The type attribute for this xs:element contains the proper namespace reference notation

## The rules for the transformation(Based on ISO 19118)

- Unions:

## The rules for the transformation(Based on ISO 19118)

- Enumerations: All classes with the Stereotype Enumeration are transformed into an xs:simpleType with a name attribute equal to the class name in the UML.  All classes contain an xs:union element that contains two xs:simpleType elements.  The first xs:simpleType element has an xs:restriction element with a base attribute equal to an iso19103:CharacterString.  Each xs:restriction element contains a series of xs:enumeration elements whose value equals the attribute values shown in the ISO 19115 UML diagram for the enumeration.  The second xs:simpleType element also has an xs:restriction element.  Its base attribute is an xs:positiveInteger.  It contains an xs:maxInclusive element whose value is set to the properly formatted equivalent of the number of attributes contained in the class stereotyped as Enumeration.   The propely formatted equivalent is defined by the second element in the xs:restricition element which is always an xs:pattern element with the value attribute set to "\d{3}".  This pattern forces the domain codes to be three digits.
-     Additionally all classes with the Stereotype Enumeration are transformed into an xs:element with a name attribute equal to the class name and the type attribute equal to the xs:simpleType name attribute described above.  The type attribute for this xs:element contains the proper namespace reference notation

## The rules for the transformation(Based on ISO 19118)

- Enumerations:

## The rules for the transformation(Based on ISO 19118)

- Code Lists: All classes with the Stereotype Codelist are transformed into an xs:complexType with an xs:simpleContent element. The xs:simpleContent element contains an xs:extension element with a base attribute  that is an iso19103:CharacterString. The xs:extension element contains an xs:attribute element with a name attribute equal to "codeSpace" and a value attribute equal to iso19115:URI. This xs:attribute is used to specify the codespace in which the codelist value is defined and has a default attribute that provides the reference to the data dictionary that contains the codelist values as described in ISO 19118 A.5.2.4.
-    For each class with the Stereotype Codelist, an xs:element with a name attribute equal to the class name and the type attribute equal to the xs:complexType name attribute described above.  The type attribute for this xs:element contains the proper namespace reference notation

## The rules for the transformation(Based on ISO 19118)

- The rules for the transformation*(Based on ISO 19118)*

- Code Lists:

## The rules for the transformation(Based on ISO 19118)

- Associations and corresponding roles: The treatment of associations is based on the assumption that all associations are one-way byValue per Section 6.1.1.6.  All associations are transformed into xs:element elements within the xs:sequence of the composite class.  The name attribute of the xs:element is set to the value of the role and the minOccurs attribute of the xs:element is set based on the multiplicity of the association, depending on whether the role is optional/conditional (0) or mandatory (1).  The xs:element contains an xs:complexType element which in turn contains an xs:sequence element.  Within the xs:sequence element there is an  xs:element that contains a ref attribute that is set to the class name equal to the xs:complexType name attribute of the part class as described in the class transformation above.  This ref attribute contains the proper namespace reference notation.  The maxOccurs attribute of this xs:element is set based on the multiplicity of the association

## The rules for the transformation(Based on ISO 19118)

- The rules for the transformation*(Based on ISO 19118)*

- Associations and corresponding roles:

## The rules for the transformation(Based on ISO 19118)

- Generalizations: Sub-classes in generalizations are treated like regular classes except that the xs:sequence element is contained within an xs:extension element whose base attribute is set to the value of the generalization class with proper namespace reference notation.  Additionally the xs:extension element is contained within an xs:complexContent element that is contained in the xs:ComplexType element created for all classes.
-    Just like with regular classes all Sub-classes in generalizations are transformed into an xs:element with a name attribute equal to the class name and the type attribute equal to the xs:complexType name attribute described above.  The type attribute for this xs:element contains the proper namespace reference notation.  Within this xs:element there is also a substitutionGroup attribute whose value is set to the generalization class with proper namespace notation

## The rules for the transformation(Based on ISO 19118)

- Generalizations:

## Application Schema – What is it?

- Any description of reality is always an abstraction, always partial, and always just one of many possible “views“, depending on the application field.
- The widespread application of computers and geographic information systems (GIS) has lead to an increased use of geographic data within multiple disciplines. With current technology as an enabler, society’s reliance on such data is growing.  Geographic datasets are increasingly being shared and exchanged. They are also used for purposes other than those for which they were produced.
- To ensure that data will be understood by both computer systems and users, the data structures for data access and exchange must be fully documented. The interfaces between systems therefore need to be defined with respect to data and operations, using the methods standardized in this International Standard. For the construction of internal software and data storage within proprietary systems any method may be used that enables the standardized interfaces to be supported.
- An application schema provides the formal description of the data structure and content required by one or more applications. An application schema contains the full description of a certain dataset and may contain descriptions of both geographic data and other related data.  A fundamental concept of geographic data is the feature. A feature is an abstraction of real world phenomena, about which data are collected, maintained, and disseminated

## Supports the Standardized Extension of Metadata

## Schedules