[Geoserver-users] urn:x-ogc or urn:ogc ???

GeoServer GeoServer User
1

hi all,

could you explain why in a wfs 1.1 response, i have srsName="urn:x-ogc:def:crs:EPSG:6.11.2:4326" ??

why urn:x-ogc:def:crs:EPSG:6.11.2:4326 and not urn:ogc:def:crs:EPSG:6.11.2:4326 or urn:ogc:def:crs:EPSG:4326 ??

where can i find specification/information.. about this ?

thanks again and again..:wink:

Sébastien.

2

I am not exactly sure this is the reason by I believe x-ogc vs just ogc is meant to remove any ambiguity in axis order, so wether its long/lat or lat/long.

As for the version number 6.11.2, it is optional. And in recent version of the WFS compliance tests they made it optional so GeoServer should not be outputing a version of srsName's on trunk.

You can find the complete specification here:

http://portal.opengeospatial.org/files/?artifact_id=8339

-Justin

Sébastien Geindre wrote:

hi all,

could you explain why in a wfs 1.1 response, i have srsName="urn:x-ogc:def:crs:EPSG:6.11.2:4326" ??

why urn:x-ogc:def:crs:EPSG:6.11.2:4326 and not urn:ogc:def:crs:EPSG:6.11.2:4326 or urn:ogc:def:crs:EPSG:4326 ??

where can i find specification/information.. about this ?

thanks again and again..:wink:

Sébastien.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:4007,485281b916862092453641!

--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com

3

I also should have noted that you will get a much more complete answer if you send this question to wfs-dev@anonymised.com

-Justin

Justin Deoliveira wrote:

I am not exactly sure this is the reason by I believe x-ogc vs just ogc is meant to remove any ambiguity in axis order, so wether its long/lat or lat/long.

As for the version number 6.11.2, it is optional. And in recent version of the WFS compliance tests they made it optional so GeoServer should not be outputing a version of srsName's on trunk.

You can find the complete specification here:

http://portal.opengeospatial.org/files/?artifact_id=8339

-Justin

Sébastien Geindre wrote:

hi all,

could you explain why in a wfs 1.1 response, i have srsName="urn:x-ogc:def:crs:EPSG:6.11.2:4326" ??

why urn:x-ogc:def:crs:EPSG:6.11.2:4326 and not urn:ogc:def:crs:EPSG:6.11.2:4326 or urn:ogc:def:crs:EPSG:4326 ??

where can i find specification/information.. about this ?

thanks again and again..:wink:

Sébastien.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com

4

thanks Justin.
In fact, partnet of mine tell me that Ihe tried to import WFS reply into a commercial GIS (ESRI ARC GIS).

But srsName seems to be ignore..

The processus ended up with the following error message:

"urn:x-ogc:def:crs:EPSG: is not a valid key name.
No definition was found for coordinate system `urn:x-ogc:def:crs:EPSG:6.11.2:4326'"

Last question for today..
Geoserver 1.7-beta1 is build from the trunk ?

thanks.

Justin Deoliveira a écrit :

I am not exactly sure this is the reason by I believe x-ogc vs just ogc is meant to remove any ambiguity in axis order, so wether its long/lat or lat/long.

As for the version number 6.11.2, it is optional. And in recent version of the WFS compliance tests they made it optional so GeoServer should not be outputing a version of srsName's on trunk.

You can find the complete specification here:

http://portal.opengeospatial.org/files/?artifact_id=8339

-Justin

Sébastien Geindre wrote:

hi all,

could you explain why in a wfs 1.1 response, i have srsName="urn:x-ogc:def:crs:EPSG:6.11.2:4326" ??

why urn:x-ogc:def:crs:EPSG:6.11.2:4326 and not urn:ogc:def:crs:EPSG:6.11.2:4326 or urn:ogc:def:crs:EPSG:4326 ??

where can i find specification/information.. about this ?

thanks again and again..:wink:

Sébastien.

-------------------------------------------------------------------------

Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:4007,485281b916862092453641!

5

Sébastien Geindre ha scritto:

thanks Justin.
In fact, partnet of mine tell me that Ihe tried to import WFS reply into a commercial GIS (ESRI ARC GIS).

But srsName seems to be ignore..

The processus ended up with the following error message:

"urn:x-ogc:def:crs:EPSG: is not a valid key name.
No definition was found for coordinate system `urn:x-ogc:def:crs:EPSG:6.11.2:4326'"

Afaik ArcGIS is completely unable to make proper version negotiation,
it simply blindly assumes you're using WFS 1.0, it won't be able to
recognize the form even without the x-

You should try to force ArcGIS to hit the wfs 1.0 capabilities
instead of the WFS 1.1 ones afaik.

As for the reason for x-ogc vs ogc, the reason is that when the
WFS 1.1 spec was made ogc was not registered as an authority
at the... where was that.. the IANA? Don't exactly remember.
Anyways the x- means "temporary" or something like that, as
in, "non official".
For further details contact the ml Justin referred you to.

Last question for today..
Geoserver 1.7-beta1 is build from the trunk ?

Cheers
Andrea