GeoTools

Add a CRS authority factory for the "urn:ogc:def:...:EPSG" name space

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.3.M0
  • Fix Version/s: 2.4-M0
  • Component/s: referencing
  • Labels:
    None

Description

In addition of the "EPSG:xxxx" authority code (which is ambiguious, see GEOT-858), OGC defines a namespace of the kind "urn:ogc:def". Examples:

urn:ogc:def:crs:EPSG:6.0:4277
urn:ogc:def:cs:EPSG:6.0:6402
urn:ogc:def:axis:EPSG:6.0:9901
urn:ogc:def:datum:EPSG:6.0:6277
urn:ogc:def:meridian:EPSG:6.0:8901
urn:ogc:def:ellipsoid:EPSG:6.0:7001

Note that this naming scheme include the kind of object ("crs", "axis", etc.) as well as the database version ("6.0" in the above examples).

  1. Text File
    GEOT-859.patch
    24/Nov/06 2:33 AM
    4 kB
    Justin Deoliveira

Issue Links

depends upon

Improvement - An improvement or enhancement to an existing feature or task. GEOT-1100 Deprecate the AbstractFactory.priority field

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Open - The issue is open and ready for the assignee to start work on it.
is related to

Bug - A problem which impairs or prevents the functions of the product. GEOT-1659 urn:ogc:def:crs:EPSG:4326 parsing won't work if forcexy is activated

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. GEOT-1388 EPSG codes in URN form do not respect global axis orientation setting

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. GEOT-1710 urn:ogc:def:crs:OGC:1.3:CRS84 is not recognized by the referencing subsystem

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Improvement - An improvement or enhancement to an existing feature or task. GEOT-858 Allow users to force CRS creation with (longitude,latitude) axis order

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. GEOT-1563 Cannot decode http://www.opengis.net/gml/srs/epsg.xml#XXXX when XXXX is a custom projection

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Task - A task that needs to be done. GEOS-1548 get story straight about urn style srsName

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Justin Deoliveira added a comment -
Hi Martin,

I have applied hte patch to trunk.

-Justin
Show
Justin Deoliveira added a comment - Hi Martin, I have applied hte patch to trunk. -Justin
Hide
Permalink
Martin Desruisseaux added a comment -
I have an issue with the patch. It wraps explicitly the (to be deprecated) EPSGCRSAuthorityFactory, which is the WKT-based factory assuming (x,y) axis order. I though that the "URN" syntax was created exactly in order to avoid the axis order ambiguity, and that the specification said that axis order should be as specified by the authority, which means (latitude,longitude) in EPSG case...

I would also like to know if there is a difference between urn:ogc... and urn:x-ogc...
Show
Martin Desruisseaux added a comment - I have an issue with the patch. It wraps explicitly the (to be deprecated) EPSGCRSAuthorityFactory, which is the WKT-based factory assuming (x,y) axis order. I though that the "URN" syntax was created exactly in order to avoid the axis order ambiguity, and that the specification said that axis order should be as specified by the authority, which means (latitude,longitude) in EPSG case... I would also like to know if there is a difference between urn:ogc... and urn:x-ogc...
Hide
Permalink
Martin Desruisseaux added a comment -
Depends upon GEOT-1100 if we want to take version in account.
Show
Martin Desruisseaux added a comment - Depends upon GEOT-1100 if we want to take version in account.
Hide
Permalink
Martin Desruisseaux added a comment -
Implemented as a URN_AuthorityFactory class on trunk.
Show
Martin Desruisseaux added a comment - Implemented as a URN_AuthorityFactory class on trunk.

People

  • Assignee:
    Martin Desruisseaux
    Reporter:
    Martin Desruisseaux
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: