We had a similar problem with another process, and our interpretation
was that for some reason the GeoJSON parser has been changed/updated and
it's now more strict following the GeoJSON specification.
The GeoJSON RFC [1] says the following:
/The coordinate reference system for all GeoJSON coordinates is a
geographic coordinate reference system, using the World Geodetic System
1984 (WGS 84) [WGS84] datum, with longitude and latitude units of
decimal degrees. /
/The use of alternative coordinate reference systems was specified in
[GJ2008], but it has been removed from this version of the specification
because the use of different coordinate reference systems -- especially
in the manner specified in [GJ2008] -- has proven to have
interoperability issues. In general, GeoJSON processing software is not
expected to have access to coordinate reference system databases or to
have network access to coordinate reference system transformation
parameters. However, _where all involved parties have a prior
arrangement, alternative coordinate reference systems can be used
_without risk of data being misinterpreted./
Maybe that could be the source of the trouble?
Bingen
[1] https://www.rfc-editor.org/rfc/rfc7946
22/10/26 09:38(e)an, Daniele Maggiolo via Geoserver-users igorleak
idatzi zuen:
Hi,
I noticed that in GeoServer version 2.21.1 the WPS ReprojectGeometry
does not work as it should.
In version 2.18.2, if I passed a geometry in application/json format
with coordinate system 3857 and transformed it into coordinate system
3003, everything worked fine.
In version 2.21.1, I get the error "Failed to retrieve value for input
geometry" instead.
The entered parameters are:
Input Geometry (TEXT / application/json):
{"coordinates": [1262204.6480731154,5710619.937814053], "type": "Point"}
sourceCRS:
EPSG: 3857
targetCRS:
EPSG: 3003
result (Checked Generate):
application/json
This is the request payload xml:
<?xml version="1.0" encoding="UTF-8"?><wps:Execute version="1.0.0"
service="WPS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns="http://www.opengis.net/wps/1.0.0";
xmlns:wfs="http://www.opengis.net/wfs";
xmlns:wps="http://www.opengis.net/wps/1.0.0";
xmlns:ows="http://www.opengis.net/ows/1.1";
xmlns:gml="http://www.opengis.net/gml";
xmlns:ogc="http://www.opengis.net/ogc";
xmlns:wcs="http://www.opengis.net/wcs/1.1.1";
xmlns:xlink="http://www.w3.org/1999/xlink";
xsi:schemaLocation="http://www.opengis.net/wps/1.0.0
http://schemas.opengis.net/wps/1.0.0/wpsAll.xsd";>
<ows:Identifier>gs:ReprojectGeometry</ows:Identifier>
<wps:DataInputs>
<wps:Input>
<ows:Identifier>geometry</ows:Identifier>
<wps:Data>
<wps:ComplexData
mimeType="application/json"><![CDATA[{"coordinates":[1262204.6480731154,5710619.937814053],"type":"Point"}]]></wps:ComplexData>
</wps:Data>
</wps:Input>
<wps:Input>
<ows:Identifier>sourceCRS</ows:Identifier>
<wps:Data>
<wps:LiteralData>EPSG:3857</wps:LiteralData>
</wps:Data>
</wps:Input>
<wps:Input>
<ows:Identifier>targetCRS</ows:Identifier>
<wps:Data>
<wps:LiteralData>EPSG:3003</wps:LiteralData>
</wps:Data>
</wps:Input>
</wps:DataInputs>
<wps:ResponseForm>
<wps:RawDataOutput mimeType="application/json">
<ows:Identifier>result</ows:Identifier>
</wps:RawDataOutput>
</wps:ResponseForm>
</wps:Execute>
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian
Turton:http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting
guidelines:http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see
this:https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
