Re: [Geoserver-users] Output dimension must be 2 or 3

2022-12-06 Thread Hans Yperman
Hi, I just found out all the M values are identical, and some huge negative value (-1.797693134862316e+308) which seems to be the lowest value that fits in a Double . So I'll ask the business if I am allowed to just drop the M coordinate. I don't know enough GIS to answer this question: What

Re: [Geoserver-users] Output dimension must be 2 or 3

2022-12-06 Thread Jody Garnett
Interesting, well that may be your issue? 4326 is a two-dimensional SRS, please make use of a three dimensional SRS. What does the SRID number say in PostGIS? It should be baked into each geometry (and should not work if if set to 4326). I guess it could be that you have a two dimensional XY

Re: [Geoserver-users] Output dimension must be 2 or 3

2022-12-06 Thread Michael, Ursula (DEM)
UNOFFICIAL Hello Andrea & Geoserver team, I’ve seen a somewhat related WMS rendering error with our Oracle and App-Shema service when we switched from 2D GDA94 to the 3D GDA2020 EPSG 7843. 06 023 22:23:41 ERROR [geoserver.ows] - org.opengis.geometry.MismatchedDimensionException: Argument

Re: [Geoserver-users] Output dimension must be 2 or 3

2022-12-06 Thread Andrea Aime
Hi, looks like it's happening as the code is preparing to write a geometry literal for a filter in a prepared statement... and it does not work because the WKB writer for it does not know how to write geometries with 4 dimensions. Maybe it would be ok to lower the geometry used for the filter to 2

Re: [Geoserver-users] Output dimension must be 2 or 3

2022-12-06 Thread Hans Yperman
Thanks for your help, Jody The data is indeed XYZM, and the srid is 4326. For reference: This is the full constraint on the column: constraint enforce_dims_the_geom check (st_ndims(the_geom) = 4) constraint enforce_geotype_the_geom check ((geometrytype(the_geom) = 'MULTIPOLYGON'::text)