Package org.geotools.data.crs

Provides support for the OGC Catalog Specification.

See: Description

Class Summary

Class	Description
ForceCoordinateSystemFeatureReader	ForceCoordinateSystemFeatureReader provides a CoordinateReferenceSystem for FeatureTypes.
ForceCoordinateSystemFeatureResults	ForceCoordinateSystemFeatureResults provides a CoordinateReferenceSystem for FeatureTypes.
ForceCoordinateSystemIterator	ForceCoordinateSystemFeatureReader provides a CoordinateReferenceSystem for FeatureTypes.
ReprojectFeatureIterator	ReprojectFeatureReader provides a reprojection for FeatureTypes.
ReprojectFeatureReader	ReprojectFeatureReader provides a reprojection for FeatureTypes.
ReprojectFeatureResults	ReprojectFeatureReader provides a reprojection for FeatureTypes.

Package org.geotools.data.crs Description

Provides support for the OGC Catalog Specification.

This package provides the base interfaces needed to support the concept of a catalog of catalog entries. Catalog access is granted by both an iterator, and a query method. The query language is not specified by this api, although the specification expects it to perform similarly to the Simple Feature.

NOTE:
The specification Catalog Services 1.1.1 does not specify the methods of the org.opengis.catalog.CatalogEntry interface. The methods in this interface were inferred from reading the abstract catalog specification: Catalog Services section 3.1.2.

Representation of Metadata

We could not decide on a unified approach for the representation of Metadata. The choices were between ISO 19115, ISO 19119 and the Dublin core. Our feedback for implementing ISO 19115 is described in the org.opengis.metadata package.

Our insight came when examining the Catalog Services 1.1.1 document - in the abstract catalog specification: CatalogServices section 3.1.2. By making real classes out of these definitions we have been able to programatically declare the api used by catalog services org.opengis.catalog.QueryDefinition to access metadata without being tied to a specific Metadata standard.

Specifically the following definitions:

• 4.6 Metadata dataset - Metadata describing a specific dataset [ISO 19101]
• 4.7 Metadata entity - Group of metadata elements and other metadata entities describing the same aspect of data.
  • NOTE 1: A metadata entity may contain one or more metadata entities.
  • NOTE 2: A metadata is equivalent to a class in UML terminology [ISO 19101].
• 4.8 Metadata schema - Conceptual schema describing metadata.
  • NOTE ISO 19115 describes a standard for a metadata schema [ISO 19101]

From these definitions we have formalized the following:

• org.opengis.catalog.MetadataEntity
• org.opengis.catalog.MetadataEntity.EntityType
• org.opengis.catalog.MetadataEntity.Element

This abstraction allows our implementation of ISO 19115 (org.opengis.metadata) to exist independently of org.opengis.catalog.Catalog, org.opengis.catalog.CatalogEntry, org.opengis.catalog.QueryDefinition and org.opengis.catalog.QueryResult.

Package Specification

This package is based on the following specifications:

• Topic 13 - Catalog Services version: 4 (Abstract Specification)
• OpenGIS� Catalogue Services Specification version: 1.1.1 (Implementation Specification)

Since the time of creation the following has been released:

• OpenGIS� Catalogue Services Specification version: 2.0 (Implementation Specification)

Q: Is practice of creating objects for MetadataEntity, Element and EntityType not in the spirit of the specification, if so can they recommend an alternative? One alternative would be to port the CORBA IDL from v2. Problem is InsertMetadata/UpdateMetadata using "any payload".

Q: Does the Catalog v2 section 10: HTTP protocol binding replace the Web Registry Service draft document? Or should we expect any progress on that front?

Related Documentation

• org.opengis.metadata - ISO 19115 (TC211) Metadata specification
• org.opengis.filter - defines a query language similar in scope to QueryDefinition