[FrontPage] [TitleIndex] [WordIndex

CRS Subsystem Development

Status: beta (2010-01-22)

Design and implementation documentation for the deegree3 CRS subsystem.

1. CRS ids

The codes for CRSs (and also any other identifiable OGC objects) are formally called URNs. There is a paper from the OGC that discusses the forms of URNs. (last visited 22/01/2010)

Currently, the CRS database contains the CRSs from the EPSG database plus a few custom CRSs (e.g. the CRS used by Google maps). There have been cases of different spellings/forms of the same EPSG crs ids ("EPSG" and the code number were always present though). Here are the forms for which the EPSG 4326 code (the code may have 4, 5 or 6 digits) can appear:

Also note:

  1. between the last two colons (::), there can appear the version of the code, e.g. URN:X-OGC:DEF:CRS:EPSG:6.11:4326. In the case of EPSG 4326, the CRS with this version (6.11) is actually different (the axes are switched); however this is not a rule.

  2. there are variants where the two colons (::) are replaced by one colon (:).

2. Component definitions

2.1. Ellipsoids

2.2. Geodetic datums

2.3. Prime Meridian

2.4. Axis

2.5. Coordinate systems

2.5.1. Geographic CRS

2.5.2. Compound CRS

2.5.3. Geocentric CRS

2.5.4. Projected CRS

2.6. Projections Definitions

2.6.1. defined Projections

2.6.2. LatLon

2.6.3. Projection

(with optional attribute class string)

2.6.4. TransverseMercator

2.6.5. StereographicAzimuthal

2.6.6. LambertConformalConicType

3. Modelling the Projection (discussion 03/03/09)

The Projection table currently stores a reference to the GeographicCRS. This is inefficient if more GeographicCRSs are used with the same projection parameters. Currently, there is no evidence of such a case (although the EPSG-registry appears to be modeling it independently) . The Java class model has the same configuration (e.g. the Projection constructor has a GeographicCRS parameter). In this case however a separation between Projection and GeographicCRS would lead to new conversion classes for each transformation and hence make the design difficult to understand.

A Projection (concrete instances: TransverseMercator, LambertConfomalConic, LambertAzimuthalEqualArea, StereographicAzimuthal, StereographicAlternative) applied to a GeographicCRS results in a ProjectedCRS. The Projection needs to access Ellipsoid-specific data through the Datum of the GeographicCRS.


2018-04-20 12:04