Ok, but if I use WFS service in GeoServer i can use srsName property for having 
coordinate with native system in JSON format. So why not give the possibility 
to use different systems also on wps processes?
Is not easy to use gs:IntersectionFeatureCollection because is rare that the 
first or the second features are in 4326. The result of the process will be 
empty if the feature was not reprojected before.

However, which option should I use to generate the GML format?

[cid:image001.png@01D8CF75.6096D2D0]
Thank you,
Daniele

Daniele Maggiolo | Abitat SIT
daniele.maggi...@abitat.it<mailto:daniele.maggi...@abitat.it>
0444 794127

Da: Ian Turton <ijtur...@gmail.com>
Inviato: venerdì 23 settembre 2022 17:37
A: Daniele Maggiolo <daniele.maggi...@abitat.it>
Cc: geoserver-users@lists.sourceforge.net
Oggetto: Re: [Geoserver-users] WPS Process SRS Output blocked to EPSG:4326

GeoJSON is required to be in 4326 by the specification, we have just come into 
conformance with that standard. I don't think there is any way to force it back 
to the old way.

A solution if you need to use a better projection is to ask for your output in 
GML instead

Ian

On Fri, 23 Sept 2022 at 16:29, Daniele Maggiolo via Geoserver-users 
<geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.sourceforge.net>>
 wrote:
Hi,
I just updated GeoServer from version 2.18.2 to 2.21.1 and I noticed that, in 
the latest version of GeoServer, using the WPS gs:Query and 
gs:IntersectionFeatureCollection processes the SRS of the output geometries is 
EPSG: 4326.
In version 2.18.2 that I used before, the coordinate system of the output 
geometry was instead that of the starting layer on which the process was 
performed, for example EPSG: 3003. Also, in the JSON of the output, in addition 
to the "features" property there was the "crs" property which contained the 
coordinate system information.
I would need to output the same coordinate system as the starting layer (as was 
the case in the previous version of GeoServer), is this possible? If not, is 
there any workaround? I specify that the starting layer can have different 
coordinate systems and therefore I cannot force it but it must be taken 
dynamically.

Thank you,
Daniele

_______________________________________________
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<mailto:Geoserver-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/geoserver-users


--
Ian Turton
_______________________________________________
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

Reply via email to