Hi,
Does anyone know if GeoServer 2.1.3 supports WFS reprojection on EPSG:3758?
WMS service obviously does. But, I have trouble to make it work on WFS. If I switch to epsg:4326, everything works just fine.
Thanks,
Guan
Hi,
Does anyone know if GeoServer 2.1.3 supports WFS reprojection on EPSG:3758?
WMS service obviously does. But, I have trouble to make it work on WFS. If I switch to epsg:4326, everything works just fine.
Thanks,
Guan
Hi,
This is probably a newer version but generally, yes.
The correct code is EPSG:3857. However, with all data reprojection into EPSG:3857 in not possible because the system is valid only between -85 - +85 degrees latitude.
-Jukka Rahkonen-
________________________________
Guan Wang wrote:
Hi,
Does anyone know if GeoServer 2.1.3 supports WFS reprojection on EPSG:3758?
WMS service obviously does. But, I have trouble to make it work on WFS. If I switch to epsg:4326, everything works just fine.
Thanks,
Guan
Hi Jukka,
Thank you for the quick reply! That's a typo error. I meant "epsg:3857".
Now I know I probably used the wrong term. "Reprojection" in WFS context
means the returning coordinates are in the projection specified by "srsName"
that is appending to the GET request.
What I try to accomplish is sending coordinates in "epsg:3857" to a layer
with the projection, say "epsg:4326". I wish GeoServer WFS could recognize
this and do the reprojection for incoming coordinates on the fly, which is
very common for WMS.
Is this even doable using WFS GET? Should I dig into WFS filter option or is
just another parameter name, i.e., 'SRS' or 'CRS', I missed?
Thanks a lot!
Guan
-----Original Message-----
From: Rahkonen Jukka [mailto:jukka.rahkonen@anonymised.com]
Sent: Friday, May 24, 2013 5:20 PM
To: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] GeoServer 2.1.X WFS Support on Google
Projection
Hi,
This is probably a newer version but generally, yes.
http://demo.opengeo.org/geoserver/wfs?service=wfs&version=1.1.0&request=getf
eature&typename=topp:states&srsname=EPSG:3857&maxfeatures=1
The correct code is EPSG:3857. However, with all data reprojection into
EPSG:3857 in not possible because the system is valid only between -85 - +85
degrees latitude.
-Jukka Rahkonen-
________________________________
Guan Wang wrote:
Hi,
Does anyone know if GeoServer 2.1.3 supports WFS reprojection on EPSG:3758?
WMS service obviously does. But, I have trouble to make it work on WFS. If I
switch to epsg:4326, everything works just fine.
Thanks,
Guan
----------------------------------------------------------------------------
--
Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only
SaaS-based application performance monitoring service that delivers powerful
full stack analytics. Optimize and monitor your browser, app, & servers with
just a few lines of code. Try New Relic and get this awesome Nerd Life
shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
On Fri, May 24, 2013 at 11:32 PM, Guan Wang <gwang@anonymised.com> wrote:
Hi Jukka,
Thank you for the quick reply! That's a typo error. I meant "epsg:3857".
Now I know I probably used the wrong term. "Reprojection" in WFS context
means the returning coordinates are in the projection specified by
"srsName"
that is appending to the GET request.What I try to accomplish is sending coordinates in "epsg:3857" to a layer
with the projection, say "epsg:4326". I wish GeoServer WFS could recognize
this and do the reprojection for incoming coordinates on the fly, which is
very common for WMS.
Yes, it should work (we have several automated tests for this behavior).
Is this even doable using WFS GET? Should I dig into WFS filter option or
is
just another parameter name, i.e., 'SRS' or 'CRS', I missed?
If it's just the bbox, you can specify the srs as the fifth element, if
it's a spatial
filter in an XML OGC filter, you set the srs on each geometry in it
Cheers
Andrea
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
Hi Andrea,
Thank you!
As for using bbox in WFS GET, by adding epsg as the fifth element of the bbox string, GeoServer recognizes the request for incoming coordinates conversion from the srs that is specified in bbox to the native coordinate system of the layer defined in typename.
The format is like (WFS 1.1.0): bbox=y1,x1,y2,x2,epsg:3857
However, this technique is not practical since it won't be a hurdle at all for the client to conduct conversion (2 pairs of coords) unless the native srs is unknown or the client is lack of means for this conversion. What really matters is the returning coordinates, it is a smart idea to ask GeoServer do it for you by specifying srsName parameter in the WFS GET. Well, OL can do it on the fly at the client side too though.
Have a great long weekend!
Guan
----- Original Message -----
From: "Andrea Aime" <andrea.aime@anonymised.com>
To: "Guan Wang" <gwang@anonymised.com>
Cc: "Rahkonen Jukka" <jukka.rahkonen@anonymised.com>, "GeoServer Mailing List List" <geoserver-users@lists.sourceforge.net>
Sent: Saturday, May 25, 2013 1:52:25 AM
Subject: Re: [Geoserver-users] GeoServer 2.1.X WFS Support on Google Projection
On Fri, May 24, 2013 at 11:32 PM, Guan Wang < gwang@anonymised.com > wrote:
Hi Jukka,
Thank you for the quick reply! That's a typo error. I meant "epsg:3857".
Now I know I probably used the wrong term. "Reprojection" in WFS context
means the returning coordinates are in the projection specified by "srsName"
that is appending to the GET request.
What I try to accomplish is sending coordinates in "epsg:3857" to a layer
with the projection, say "epsg:4326". I wish GeoServer WFS could recognize
this and do the reprojection for incoming coordinates on the fly, which is
very common for WMS.
Yes, it should work (we have several automated tests for this behavior).
Is this even doable using WFS GET? Should I dig into WFS filter option or is
just another parameter name, i.e., 'SRS' or 'CRS', I missed?
If it's just the bbox, you can specify the srs as the fifth element, if it's a spatial
filter in an XML OGC filter, you set the srs on each geometry in it
Cheers
Andrea
--
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------