[Geoserver-users] R: ReprojectGeometry WPS problem from 2.22.0 GeoServer version using application/json input

[Daniele Maggiolo via Geoserver-users]

HI,
will this bug be fixed in future versions of GeoServer?

Daniele Maggiolo

Da: Ikeoka, Steve via Geoserver-users 
Inviato: mercoledì 1 novembre 2023 16:17
A: Roar Brænden ; Jody Garnett 

Cc: geoserver-users@lists.sourceforge.net
Oggetto: Re: [Geoserver-users] ReprojectGeometry WPS problem from 2.22.0 
GeoServer version using application/json input

This is a regression from the following commit that got missed because the bug 
wasn't covered by existing unit tests:
https://github.com/geoserver/geoserver/commit/587768dfcbe166bbf7972d172f454f1b3f17a043#diff-cb964c0310e4da804603b89cac17d51824cc66e2f626c4af6902610c8a8e9329

Getting rid of the JsonParser/JsonFactory stuff and just calling 
MAPPER.readValue(input, Geometry.class); should work.

Steve Ikeoka

From: Roar Brænden mailto:roar.brenden...@gmail.com>>
Sent: Wednesday, November 1, 2023 7:09 AM
To: Jody Garnett mailto:jody.garn...@gmail.com>>
Cc: 
geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.sourceforge.net>
 
mailto:geoserver-users@lists.sourceforge.net>>
Subject: Re: [Geoserver-users] ReprojectGeometry WPS problem from 2.22.0 
GeoServer version using application/json input

Hi, Jody, that code has been copied into GeoTools codebase in the module 
gt-geojson-core. https: //github. 
com/geotools/geotools/blob/main/modules/unsupported/geojson-core/src/main/java/com/bedatadriven/jackson/datatype/jts/serialization/GeometryDeserializer.
 javaAnd,
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
If you think this is a phishing email report it using the report phish button. 
For additional assistance go to OneGDIT Service Center KB0030624

ZjQcmQRYFpfptBannerEnd
Hi,

Jody, that code has been copied into GeoTools codebase in the module 
gt-geojson-core.

https://github.com/geotools/geotools/blob/main/modules/unsupported/geojson-core/src/main/java/com/bedatadriven/jackson/datatype/jts/serialization/GeometryDeserializer.java<https://urldefense.us/v3/__https:/github.com/geotools/geotools/blob/main/modules/unsupported/geojson-core/src/main/java/com/bedatadriven/jackson/datatype/jts/serialization/GeometryDeserializer.java__;!!JRQnnSFuzw7wjAKq6ti6!waRT-HUsgXcJEg3ALCJmXmJtfMs6nxH56GWmlojRNdIWR-CI-lBT4m5Qk_Z7YEKMBuVB7daUH4bQZvyk3fBMQ889R1U$>

And, the lines 44-45 were the error occurs is as follows:


ObjectCodec
oc = jsonParser.getCodec();

JsonNode
root = oc.readTree(jsonParser);


Here oc is the troublemaker being null, but according to the docs of getCodec() 
that could be the case so it should be handled in a way or the other. I'm 
afraid I haven't really looked into this module, so I can't really say how it 
should be handled.

Regards,
Roar Brænden



31. okt. 2023 kl. 21:55 skrev Jody Garnett 
mailto:jody.garn...@gmail.com>>:

I am a bit confused, checking GeometryDeserializer.java line 45:


  *   
https://github.com/bedatadriven/jackson-datatype-jts/blob/master/src/main/java/com/bedatadriven/jackson/datatype/jts/serialization/GeometryDeserializer.java<https://urldefense.us/v3/__https:/github.com/bedatadriven/jackson-datatype-jts/blob/master/src/main/java/com/bedatadriven/jackson/datatype/jts/serialization/GeometryDeserializer.java__;!!JRQnnSFuzw7wjAKq6ti6!waRT-HUsgXcJEg3ALCJmXmJtfMs6nxH56GWmlojRNdIWR-CI-lBT4m5Qk_Z7YEKMBuVB7daUH4bQZvyk3fBMEW3S0vg$>

And line 45 does not exist ... huh.

I looked online for a bit and did not find 
com.bedatadriven.jackson.datatype.jts.serialization.GeometryDeserializer yet 
(maybe someone else can help?)


I assume it is trying to parse GeoJSON when the failure occurs, perhaps look at 
the json output for anything odd or missing?
--
Jody Garnett


On Oct 31, 2023 at 1:53:06 AM, Daniele Maggiolo via Geoserver-users 
mailto:geoserver-users@lists.sourceforge.net>>
 wrote:

Hi,

I noticed that from version 2.22.0 of GeoServe, running the WPS process 
“gs:RepojectGeometry” with application/json input no longer works correctly 
while, for example, with version 2.18.2 everything worked correctly.

I tried with several recent versions, up to 2.23.1.

The Java version used in the latest versions is 11 as recommended by the 
minimum requirements of GeoServer (in version 2.18.2 I used version 8).

If I test the process with WKT input, everything works fine, while if I use 
application/json, I get the following error:


31 Oct 09:48:28 ERROR  [wps.executor] - Process execution failed

org.geoserver.wps.WPSException: Failed to retrieve value for input geometry

   at 
org.geoserver.wps.executor.LazyInputMap.parseInputs(LazyInputMap.java:98)

   at 
org.geoserver.wps.executor.LazyInputMap.get(LazyInputMap.java:50)

   at 
org.geotools.process.factory.AnnotationDrivenProcessFactory$InvokeMethodProcess.buildProcessArguments(AnnotationDrivenProcessFactory.java:748)

   at 
org.geotools.process.factory.Annotation

[Geoserver-users] R: Problems adding Grid Shift Transform files

[Daniele Maggiolo via Geoserver-users]

HI,
I found the solution.
To make everything work, you also need to write the parameters of the 2 systems 
you want to convert using grid shift (in the epsg_operations.properties file) 
before and after including the gsb file.

This is an example:

3003,3857=CONCAT_MT[INVERSE_MT[PARAM_MT["Transverse_Mercator",\
   PARAMETER["semi_major", 6378388.0],\
   PARAMETER["semi_minor", 6356911.9461279465],\
   PARAMETER["central_meridian", 9.0],\
   PARAMETER["latitude_of_origin", 0.0],\
   PARAMETER["scale_factor", 0.9996],\
   PARAMETER["false_easting", 150.0],\
   PARAMETER["false_northing", 0.0]]],\
PARAM_MT["NTv2", PARAMETER["Latitude and longitude difference file", 
"NadRoma40.gsb"]],\
PARAM_MT["Popular Visualisation Pseudo Mercator",\
PARAMETER["semi_major", 6378137.0],\
PARAMETER["semi_minor", 6378137.0],\
PARAMETER["latitude_of_origin", 0.0],\
PARAMETER["central_meridian", 0.0],\
PARAMETER["scale_factor", 1.0],\
PARAMETER["false_easting", 0.0],\
PARAMETER["false_northing", 0.0]]]

Daniele Maggiolo


Da: Daniele Maggiolo via Geoserver-users 
Inviato: giovedì 2 novembre 2023 14:49
A: geoserver-users@lists.sourceforge.net
Oggetto: [Geoserver-users] Problems adding Grid Shift Transform files

HI,
I tried to configure a grid shift as explained in this guide:

https://docs.geoserver.org/latest/en/user/configuration/crshandling/coordtransforms.html#examples

using a gsb file.

In the epsg_operations.properties file (inside user_projection) I wrote the 
following line:

3857,3003=PARAM_MT["NTv2",PARAMETER["Latitude and longitude difference file", 
"NadRoma40.gsb"]]

and I put the NadRoma40.gsb file inside the same folder (file verified with 
other applications and working correctly).

Now when I try to reproject from 3857 to 3003 if I click on "Show 
transformation details" I see that GeoServer has implemented my configuration 
(it shows me exactly what I wrote in the epsg_operation file), but the 
conversion does not work correctly.
The log tells me "Point (1306188.4848936629, 5743812.429289647) is not covered 
by 'NadRoma40.gsb' NTv2 grid, it will not be moved." but I am sure that the 
point is contained by the grid.

I also tried using the gsd file described in your guide and trying the 
coordinates system in your guide, but nothing with that either.

I'm currently testing everything on a GeoServer version 2.23.1

Daniele Maggiolo
___
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] Problems adding Grid Shift Transform files

[Daniele Maggiolo via Geoserver-users]

HI,
I tried to configure a grid shift as explained in this guide:

https://docs.geoserver.org/latest/en/user/configuration/crshandling/coordtransforms.html#examples

using a gsb file.

In the epsg_operations.properties file (inside user_projection) I wrote the 
following line:

3857,3003=PARAM_MT["NTv2",PARAMETER["Latitude and longitude difference file", 
"NadRoma40.gsb"]]

and I put the NadRoma40.gsb file inside the same folder (file verified with 
other applications and working correctly).

Now when I try to reproject from 3857 to 3003 if I click on "Show 
transformation details" I see that GeoServer has implemented my configuration 
(it shows me exactly what I wrote in the epsg_operation file), but the 
conversion does not work correctly.
The log tells me "Point (1306188.4848936629, 5743812.429289647) is not covered 
by 'NadRoma40.gsb' NTv2 grid, it will not be moved." but I am sure that the 
point is contained by the grid.

I also tried using the gsd file described in your guide and trying the 
coordinates system in your guide, but nothing with that either.

I'm currently testing everything on a GeoServer version 2.23.1

Daniele Maggiolo
___
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] ReprojectGeometry WPS problem from 2.22.0 GeoServer version using application/json input

[Daniele Maggiolo via Geoserver-users]

Hi,
I noticed that from version 2.22.0 of GeoServe, running the WPS process 
"gs:RepojectGeometry" with application/json input no longer works correctly 
while, for example, with version 2.18.2 everything worked correctly.
I tried with several recent versions, up to 2.23.1.
The Java version used in the latest versions is 11 as recommended by the 
minimum requirements of GeoServer (in version 2.18.2 I used version 8).
If I test the process with WKT input, everything works fine, while if I use 
application/json, I get the following error:

31 Oct 09:48:28 ERROR  [wps.executor] - Process execution failed
org.geoserver.wps.WPSException: Failed to retrieve value for input geometry
   at 
org.geoserver.wps.executor.LazyInputMap.parseInputs(LazyInputMap.java:98)
   at 
org.geoserver.wps.executor.LazyInputMap.get(LazyInputMap.java:50)
   at 
org.geotools.process.factory.AnnotationDrivenProcessFactory$InvokeMethodProcess.buildProcessArguments(AnnotationDrivenProcessFactory.java:748)
   at 
org.geotools.process.factory.AnnotationDrivenProcessFactory$InvokeMethodProcess.execute(AnnotationDrivenProcessFactory.java:628)
   at 
org.geoserver.wps.executor.ProcessStartupFilter$ProcessStartupWrapper.execute(ProcessStartupFilter.java:50)
   at 
org.geoserver.wps.executor.DefaultProcessManager$ProcessCallable.call(DefaultProcessManager.java:222)
   at 
org.geoserver.wps.executor.DefaultProcessManager$ProcessCallable.call(DefaultProcessManager.java:191)
   at 
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
   at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
   at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
   at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.NullPointerException
   at 
com.bedatadriven.jackson.datatype.jts.serialization.GeometryDeserializer.deserialize(GeometryDeserializer.java:45)
   at 
com.bedatadriven.jackson.datatype.jts.serialization.GeometryDeserializer.deserialize(GeometryDeserializer.java:33)
   at 
com.fasterxml.jackson.databind.deser.DefaultDeserializationContext.readRootValue(DefaultDeserializationContext.java:323)
   at 
com.fasterxml.jackson.databind.ObjectMapper._readValue(ObjectMapper.java:4650)
   at 
com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2831)
   at 
org.geoserver.wps.ppio.GeoJSONPPIO$Geometries.decode(GeoJSONPPIO.java:134)
   at org.geoserver.wps.ppio.CDataPPIO.decode(CDataPPIO.java:21)
   at 
org.geoserver.wps.executor.SimpleInputProvider.getValueInternal(SimpleInputProvider.java:81)
   at 
org.geoserver.wps.executor.AbstractInputProvider.getValue(AbstractInputProvider.java:103)
   at 
org.geoserver.wps.executor.LazyInputMap.parseInputs(LazyInputMap.java:90)

The XML to test the functionality is as follows:

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;>
  gs:ReprojectGeometry
  

  geometry
  

  


  sourceCRS
  
EPSG:3857
  


  targetCRS
  
EPSG:3003
  

  
  

  result

  



Daniele Maggiolo
Settore Tecnico

[signature_3331596089]

Via Roma, 5 - 36026, Pojana Maggiore (VI)
Tel. 0444 794127 - www.abitat.it

La presente e-mail ha carattere esclusivamente aziendale. Personale incaricato 
della ditta Abitat SIT srl potrà accedere al contenuto della e-mail e a 
eventuali risposte. Non è consentita la diffusione, distribuzione e copia della 
e-mail da parte di persona diversa dal destinatario. Non permettendo Internet 
di assicurare l'integrità del presente messaggio si declina ogni responsabilità 
nell'ipotesi in cui esso venga modificato. Se avete ricevuto questa e-mail per 
errore vi preghiamo di eliminarla e darne comunicazione al mittente. Grazie per 
la Vostra collaborazione.

___
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: 

[Geoserver-users] R: Styled marks shape dot does not work in geoserver version 2.23.1

[Daniele Maggiolo via Geoserver-users]

Hi, the result I get is a polygon without filling with dots.
If I use shape://slash it works like it always did in all versions (showing me 
the lines as a fill of the polygon). The only one I can't get to work anymore 
is shape://dot (in 2.23.1 version).

Daniele


Da: Ian Turton 
Inviato: martedì 20 giugno 2023 18:11
A: Daniele Maggiolo 
Cc: geoserver-users@lists.sourceforge.net
Oggetto: Re: [Geoserver-users] Styled marks shape dot does not work in 
geoserver version 2.23.1

can you give us any clues as to what doesn't work? is nothing drawn? does the 
program crash? is a penguin produced?

What does the log file show any interesting information? what if you turn 
logging up to GeoTools-dev level and try again?

Ian

On Tue, 20 Jun 2023 at 16:05, Daniele Maggiolo via Geoserver-users 
mailto:geoserver-users@lists.sourceforge.net>>
 wrote:
Hi,
I noticed that the styled mark shape://dot doesn't work in GeoServer version 
2.23.1.
I've tried both creating a style with CSS and SLD. In version 2.22.2 everything 
worked fine.
Below is an example of a style created using CSS.


@mode 'Auto';
@styleTitle 'Test';
@styleAbstract 'Test';

/* @title Test
* @abstract Test
*/
*{
  stroke: #a0a0f5;
  stroke-width: 1;
  fill: symbol("shape://dot");
:fill {
size: 5;
stroke: #a0a0f5;
stroke-width: 1;
  fill: #a0a0f5;
}
}

___
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

[Geoserver-users] Styled marks shape dot does not work in geoserver version 2.23.1

[Daniele Maggiolo via Geoserver-users]

Hi,
I noticed that the styled mark shape://dot doesn't work in GeoServer version 
2.23.1.
I've tried both creating a style with CSS and SLD. In version 2.22.2 everything 
worked fine.
Below is an example of a style created using CSS.


@mode 'Auto';
@styleTitle 'Test';
@styleAbstract 'Test';

/* @title Test
* @abstract Test
*/
*{
  stroke: #a0a0f5;
  stroke-width: 1;
  fill: symbol("shape://dot");
:fill {
size: 5;
stroke: #a0a0f5;
stroke-width: 1;
  fill: #a0a0f5;
}
}

___
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] WPS Process gs:ReprojectGeometry doesn't work in version 2.21.1

[Daniele Maggiolo via Geoserver-users]

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:

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;>
  gs:ReprojectGeometry
  

  geometry
  

  


  sourceCRS
  
EPSG:3857
  


  targetCRS
  
EPSG:3003
  
   
  
  

  result

  

___
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] R: WPS Process SRS Output blocked to EPSG:4326

[Daniele Maggiolo via Geoserver-users]

I have also seen that the areaB parameter that returns from the gs: 
IntersectionFeatureCollection process is not correct.
Making an intersection between layers with the same coordinates system and the 
same geometries, in the property areaB there are wrong values.


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

Da: Daniele Maggiolo
Inviato: venerdì 23 settembre 2022 17:55
A: Ian Turton 
Cc: geoserver-users@lists.sourceforge.net
Oggetto: R: [Geoserver-users] WPS Process SRS Output blocked to EPSG:4326

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@01D8D1BD.BE52EF40]
Thank you,
Daniele

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

Da: Ian Turton mailto:ijtur...@gmail.com>>
Inviato: venerdì 23 settembre 2022 17:37
A: Daniele Maggiolo 
mailto:daniele.maggi...@abitat.it>>
Cc: 
geoserver-users@lists.sourceforge.net<mailto: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 
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

[Geoserver-users] R: WPS Process SRS Output blocked to EPSG:4326

[Daniele Maggiolo via Geoserver-users]

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 
Inviato: venerdì 23 settembre 2022 17:37
A: Daniele Maggiolo 
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 
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

[Geoserver-users] WPS Process SRS Output blocked to EPSG:4326

[Daniele Maggiolo via Geoserver-users]

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