[Geoserver-users] [Geoserver 1.6.4] WFS reprojection version 1.0.0 ?

GeoServer GeoServer User
1

Hi,

I'm currently having troubles with 1.0.0 WFS GET requests BBOX reprojection.
So here are my questions :

1) In WFS 1.0.0 is it possible to make WFS GET requests with a BBOX in a
different SRS than the one from the native database SRS ? (BBOX in EPSG:2154
and database in EPSG:27572 for example)

2) If it is, can you tell me where the BBOX reprojection is supposed to
happen precisely ? For now i'm quite confused with what happens in
GetFeature.java and GeoserverFeatureSource.java => It seems the
toDataQuery() method puts a CoordinateSystemReproject attribute into the
query instance but the adaptQuery() method erases it just after...

Thanx in advance

Manu

--
View this message in context: http://www.nabble.com/-Geoserver-1.6.4--WFS-reprojection-version-1.0.0---tp18940994p18940994.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

2

Hi,

WFS 1.0.0 is serving data in one projection only, which is advertised in the getCapabilities document. For Geoserver data do not need to be in that projection in the backend database. You can configure Geoserver to reproject it into some other projection which is then used in getCapabilities and in the output. BBOX in request must use this same advertised projection. Use WFS 1.1.0 if you want to deliver data in several projections.

-Jukka Rahkonen-

-----Alkuperäinen viesti-----
Lähettäjä: geoserver-users-bounces@lists.sourceforge.net
[mailto:geoserver-users-bounces@lists.sourceforge.net]
Puolesta Emmanuel Séguin
Lähetetty: 12. elokuuta 2008 12:53
Vastaanottaja: geoserver-users@lists.sourceforge.net
Aihe: [Geoserver-users] [Geoserver 1.6.4] WFS reprojection
version 1.0.0 ?

Hi,

I'm currently having troubles with 1.0.0 WFS GET requests
BBOX reprojection.
So here are my questions :

1) In WFS 1.0.0 is it possible to make WFS GET requests with
a BBOX in a different SRS than the one from the native
database SRS ? (BBOX in EPSG:2154 and database in EPSG:27572
for example)

2) If it is, can you tell me where the BBOX reprojection is
supposed to happen precisely ? For now i'm quite confused
with what happens in GetFeature.java and
GeoserverFeatureSource.java => It seems the
toDataQuery() method puts a CoordinateSystemReproject
attribute into the query instance but the adaptQuery() method
erases it just after...

Thanx in advance

Manu

--
View this message in context:
http://www.nabble.com/-Geoserver-1.6.4--WFS-reprojection-versi
on-1.0.0---tp18940994p18940994.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

--------------------------------------------------------------
-----------
This SF.Net email is sponsored by the Moblin Your Move
Developer's challenge
Build the coolest Linux based applications with Moblin SDK &
win great prizes
Grand prize is a trip for two to an Open Source event
anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

3

Hi,

Ok so from what you said :

1) In WFS 1.0.0 if my data are in EPSG:27572, and if the feature type is
declared with the same projection i will have to make requests to Geoserver
with a BBOX also defined in EPSG:27572.
2) In WFS 1.1.0 I should be able to make request with a BBOX defined in
EPSG:2154 on my feature defined in EPSG:27572

I've just tried making a request to my feature in EPSG:27572 like this :

http://localhost/geoserver/wfs?
request=GetFeature&
SERVICE=WFS&
BBOX=568518.46,6270011.33,569235.85,6270716.86&
TYPENAME=topp:commune&
srsName=EPSG:2154&
version=1.0.0

But when i look in the Geoserver logs here is what i see :wink:

2 Aug 13:30:15 DEBUG [data.jdbc] - sql is SELECT "layerid", "gid",
"layerid", "gid", "sourcede", "nom", "code_ins", "statut", "canton",
"arrondis", "departem", "region", "populati", "multi_ca",
encode(asBinary(force_2d("the_geom"),'XDR'),'base64') FROM
"public"."commune" WHERE "the_geom" && GeometryFromText('POLYGON ((568518.46
6270011.33, 568518.46 6270716.86, 569235.85 6270716.86, 569235.85
6270011.33, 568518.46 6270011.33))', 27572) LIMIT 1000000

The BBOX should be reprojected and it seems it's not ... Where should i look
to fix it ?

Thanx for your help

Manu

Rahkonen Jukka wrote:

Hi,

WFS 1.0.0 is serving data in one projection only, which is advertised in
the getCapabilities document. For Geoserver data do not need to be in
that projection in the backend database. You can configure Geoserver to
reproject it into some other projection which is then used in
getCapabilities and in the output. BBOX in request must use this same
advertised projection. Use WFS 1.1.0 if you want to deliver data in
several projections.

-Jukka Rahkonen-

-----Alkuperäinen viesti-----
Lähettäjä: geoserver-users-bounces@lists.sourceforge.net
[mailto:geoserver-users-bounces@lists.sourceforge.net]
Puolesta Emmanuel Séguin
Lähetetty: 12. elokuuta 2008 12:53
Vastaanottaja: geoserver-users@lists.sourceforge.net
Aihe: [Geoserver-users] [Geoserver 1.6.4] WFS reprojection
version 1.0.0 ?

Hi,

I'm currently having troubles with 1.0.0 WFS GET requests
BBOX reprojection.
So here are my questions :

1) In WFS 1.0.0 is it possible to make WFS GET requests with
a BBOX in a different SRS than the one from the native
database SRS ? (BBOX in EPSG:2154 and database in EPSG:27572
for example)

2) If it is, can you tell me where the BBOX reprojection is
supposed to happen precisely ? For now i'm quite confused
with what happens in GetFeature.java and
GeoserverFeatureSource.java => It seems the
toDataQuery() method puts a CoordinateSystemReproject
attribute into the query instance but the adaptQuery() method
erases it just after...

Thanx in advance

Manu

--
View this message in context:
http://www.nabble.com/-Geoserver-1.6.4--WFS-reprojection-versi
on-1.0.0---tp18940994p18940994.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

--------------------------------------------------------------
-----------
This SF.Net email is sponsored by the Moblin Your Move
Developer's challenge
Build the coolest Linux based applications with Moblin SDK &
win great prizes
Grand prize is a trip for two to an Open Source event
anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
View this message in context: http://www.nabble.com/-Geoserver-1.6.4--WFS-reprojection-version-1.0.0---tp18940994p18942630.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

4

Bad copy paste :blush:

http://localhost/geoserver/wfs?
request=GetFeature&
SERVICE=WFS&
BBOX=568518.46,6270011.33,569235.85,6270716.86&
TYPENAME=topp:commune&
srsName=EPSG:2154&
version=1.1.0

Emmanuel Séguin wrote:

Hi,

Ok so from what you said :

1) In WFS 1.0.0 if my data are in EPSG:27572, and if the feature type is
declared with the same projection i will have to make requests to
Geoserver with a BBOX also defined in EPSG:27572.
2) In WFS 1.1.0 I should be able to make request with a BBOX defined in
EPSG:2154 on my feature defined in EPSG:27572

I've just tried making a request to my feature in EPSG:27572 like this :

http://localhost/geoserver/wfs?
request=GetFeature&
SERVICE=WFS&
BBOX=568518.46,6270011.33,569235.85,6270716.86&
TYPENAME=topp:commune&
srsName=EPSG:2154&
version=1.1.0

But when i look in the Geoserver logs here is what i see :wink:

2 Aug 13:30:15 DEBUG [data.jdbc] - sql is SELECT "layerid", "gid",
"layerid", "gid", "sourcede", "nom", "code_ins", "statut", "canton",
"arrondis", "departem", "region", "populati", "multi_ca",
encode(asBinary(force_2d("the_geom"),'XDR'),'base64') FROM
"public"."commune" WHERE "the_geom" && GeometryFromText('POLYGON
((568518.46 6270011.33, 568518.46 6270716.86, 569235.85 6270716.86,
569235.85 6270011.33, 568518.46 6270011.33))', 27572) LIMIT 1000000

The BBOX should be reprojected and it seems it's not ... Where should i
look to fix it ?

Thanx for your help

Manu

Rahkonen Jukka wrote:

Hi,

WFS 1.0.0 is serving data in one projection only, which is advertised in
the getCapabilities document. For Geoserver data do not need to be in
that projection in the backend database. You can configure Geoserver to
reproject it into some other projection which is then used in
getCapabilities and in the output. BBOX in request must use this same
advertised projection. Use WFS 1.1.0 if you want to deliver data in
several projections.

-Jukka Rahkonen-

-----Alkuperäinen viesti-----
Lähettäjä: geoserver-users-bounces@lists.sourceforge.net
[mailto:geoserver-users-bounces@lists.sourceforge.net]
Puolesta Emmanuel Séguin
Lähetetty: 12. elokuuta 2008 12:53
Vastaanottaja: geoserver-users@lists.sourceforge.net
Aihe: [Geoserver-users] [Geoserver 1.6.4] WFS reprojection
version 1.0.0 ?

Hi,

I'm currently having troubles with 1.0.0 WFS GET requests
BBOX reprojection.
So here are my questions :

1) In WFS 1.0.0 is it possible to make WFS GET requests with
a BBOX in a different SRS than the one from the native
database SRS ? (BBOX in EPSG:2154 and database in EPSG:27572
for example)

2) If it is, can you tell me where the BBOX reprojection is
supposed to happen precisely ? For now i'm quite confused
with what happens in GetFeature.java and
GeoserverFeatureSource.java => It seems the
toDataQuery() method puts a CoordinateSystemReproject
attribute into the query instance but the adaptQuery() method
erases it just after...

Thanx in advance

Manu

--
View this message in context:
http://www.nabble.com/-Geoserver-1.6.4--WFS-reprojection-versi
on-1.0.0---tp18940994p18940994.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

--------------------------------------------------------------
-----------
This SF.Net email is sponsored by the Moblin Your Move
Developer's challenge
Build the coolest Linux based applications with Moblin SDK &
win great prizes
Grand prize is a trip for two to an Open Source event
anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
View this message in context: http://www.nabble.com/-Geoserver-1.6.4--WFS-reprojection-version-1.0.0---tp18940994p18942711.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

5

Rahkonen Jukka ha scritto:

Hi,

WFS 1.0.0 is serving data in one projection only, which is advertised
in the getCapabilities document. For Geoserver data do not need to
be in that projection in the backend database. You can configure
Geoserver to reproject it into some other projection which is then
used in getCapabilities and in the output. BBOX in request must use
this same advertised projection. Use WFS 1.1.0 if you want to
deliver data in several projections.

Standard wise I believe you're correct, implementation wise things
are different. We actually implemented reprojection in WFS 1.0 too,
in a way that allows filters with geometries and bboxes in other
SRS, and that allows also for reprojection of the output.
This has been made so that OL can do WFS-T with a Google Maps background, regardless of the native SRS of the data (and
considering that reimplementing WFS support to deal with WFS 1.1
in OL was simply too much work).

So, the reprojection should occurr, but there is an issue
in Emmanuel query that I'll detail in a separate mail.
Cheers
Andrea

6

Emmanuel Séguin ha scritto:

Bad copy paste :blush:

http://localhost/geoserver/wfs?
request=GetFeature&
SERVICE=WFS&
BBOX=568518.46,6270011.33,569235.85,6270716.86&
TYPENAME=topp:commune&
srsName=EPSG:2154&
version=1.1.0

The srsName parameter talks only about the output, it says
the output should be reprojected to 2154. To express the
srs of the bbox you have to add the srs specification as the
fifth element of the bbox definition:
BBOX=568518.46,6270011.33,569235.85,6270716.86,EPSG:2154
should work (haven't actually tried, so the syntax might
not be correct, look into the WFS 1.1 standard for the
exact one).
Once you get the proper syntax, the above GetFeature should
work with wfs 1.0 as well (only in our implementation, mind,
it's not part of the standard unless you use 1.1).

Cheers
Andrea

7

Thanx a lot. Still learning :wink:

Straight from the horse's mouth :

BBOX=lcc1,lcc2,...,lccN,ucc1,ucc2,...,uccN[,crsuri]

where lcc means Lower Corner Coordinate, ucc means Upper Corner Coordinate
and crsuri means the URI reference to the coordinate system being used. This
encoding allows N coordinates for each corner listed in the order of the
optional crsuri. If the crsuri is not specified then the 2-D coordinates
shall be specified using decimal decimal degrees and WGS84.

Wondering why there are such differences between WMS and WFS though.

Cheers

Manu

Andrea Aime-4 wrote:

Rahkonen Jukka ha scritto:

Hi,

WFS 1.0.0 is serving data in one projection only, which is advertised
in the getCapabilities document. For Geoserver data do not need to
be in that projection in the backend database. You can configure
Geoserver to reproject it into some other projection which is then
used in getCapabilities and in the output. BBOX in request must use
this same advertised projection. Use WFS 1.1.0 if you want to
deliver data in several projections.

Standard wise I believe you're correct, implementation wise things
are different. We actually implemented reprojection in WFS 1.0 too,
in a way that allows filters with geometries and bboxes in other
SRS, and that allows also for reprojection of the output.
This has been made so that OL can do WFS-T with a Google Maps
background, regardless of the native SRS of the data (and
considering that reimplementing WFS support to deal with WFS 1.1
in OL was simply too much work).

So, the reprojection should occurr, but there is an issue
in Emmanuel query that I'll detail in a separate mail.
Cheers
Andrea

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
View this message in context: http://www.nabble.com/-Geoserver-1.6.4--WFS-reprojection-version-1.0.0---tp18940994p18943953.html
Sent from the GeoServer - User mailing list archive at Nabble.com.