Exception in thread "main" org.opengis.referencing.NoSuchAuthorityCodeException:
Authority "URN" is unknown or doesn't match the supplied hints.
Maybe it is defined in an unreachable JAR file?
at org.geotools.referencing.factory.ManyAuthoritiesFactory.noSuchAuthority(ManyAuthoritiesFactory.java:488)
at org.geotools.referencing.factory.ManyAuthoritiesFactory.getAuthorityFactory(ManyAuthoritiesFactory.java:466)
at org.geotools.referencing.factory.ManyAuthoritiesFactory.getCRSAuthorityFactory(ManyAuthoritiesFactory.java:547)
at org.geotools.referencing.factory.AuthorityFactoryAdapter.createCoordinateReferenceSystem(AuthorityFactoryAdapter.java:753)
at org.geotools.referencing.factory.ThreadedAuthorityFactory.createCoordinateReferenceSystem(ThreadedAuthorityFactory.java:728)
at org.geotools.referencing.CRS.decode(CRS.java:419)
at org.geotools.referencing.CRS.decode(CRS.java:353)
at org.geotools.referencing.ForcedLonFailure.main(ForcedLonFailure.java:12)

This makes the wfs 1.1 and wcs 1.1 protocols unusable (they suggest the usage of the urn syntax).

Issue Links

is depended upon by

GEOT-1685remove hack introduced for the parser to recognize CRS's from a GML 3.1.1 document when GEOT-1659 is fixed

relates to

GEOT-1388EPSG codes in URN form do not respect global axis orientation setting

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

Activity

Correction, wfs 1.1 is apparently usable... but I have no idea why... the simple test above keeps on failing for me even when using the urn syntax adopted by the wfs 1.1 tests: "urn:x-ogc:def:crs:EPSG:6.11.2:4326". (and I'm running the above tests from the epsg-hsql module, so any geoserver interference should be out of question)

Andrea Aime
added a comment - 09/Jan/08 9:53 AM - edited Correction, wfs 1.1 is apparently usable... but I have no idea why... the simple test above keeps on failing for me even when using the urn syntax adopted by the wfs 1.1 tests: "urn:x-ogc:def:crs:EPSG:6.11.2:4326". (and I'm running the above tests from the epsg-hsql module, so any geoserver interference should be out of question)

Martin Desruisseaux
added a comment - 28/Jan/08 5:09 AM Hopefully fixed on trunk as of revision 28977. However we are still lacking good test coverage, so any feedback from GeoServer would be appreciated.

Merged on the 2.4 branch as of revision 29058. Flag this issue as "resolved", waiting for confirmation that it works for GeoServer. Please close this issue if it produces the expected results with GeoServer.

Martin Desruisseaux
added a comment - 03/Feb/08 11:50 AM Merged on the 2.4 branch as of revision 29058. Flag this issue as "resolved", waiting for confirmation that it works for GeoServer. Please close this issue if it produces the expected results with GeoServer.

Andrea Aime
added a comment - 04/Feb/08 9:55 AM I can confirm this one is fixed, but unfortunately another referencing issue is blocking the geoserver release now... don't know if it's a side effect of this fix or not thought