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 or 3
dimensions but... not sure how PostGIS would
react to that.
Cheers
Andrea
On Mon, Dec 5, 2022 at 1:57 PM Hans Yperman <hans.yper...@vliz.be> wrote:
> Hello everybody,
>
>
>
> after upgrading from geoserver 2.11 to geoserver 2.22, we have a few
> postgis layers that refuse to render in the preview.
>
>
>
> Here is a simplified example, in postgis:
>
>
>
> create table testhy(
> geometry geometry constraint enforce_dims_the_geom check (*st_ndims*
> (geometry) = 4)
> );
>
>
>
> We get this exception:
>
> Caused by: java.lang.IllegalArgumentException: Output dimension must be 2
> or 3
>
> at org.locationtech.jts.io.WKBWriter.<init>(WKBWriter.java:291)
>
> at org.locationtech.jts.io.WKBWriter.<init>(WKBWriter.java:270)
>
> at org.locationtech.jts.io.WKBWriter.<init>(WKBWriter.java:240)
>
> at
> org.geotools.data.postgis.PostGISPSDialect.setGeometryValue(PostGISPSDialect.java:253)
>
> at
> org.geotools.jdbc.JDBCDataStore.setPreparedFilterValues(JDBCDataStore.java:3810)
>
> at
> org.geotools.jdbc.JDBCDataStore.selectSQLPS(JDBCDataStore.java:3728)
>
> at
> org.geotools.jdbc.JDBCFeatureSource.getReaderInternal(JDBCFeatureSource.java:609)
>
>
>
> I browsed the code. geoserver gets dimension 4 based on a variant of this
> query (PostGISDialect.java):
>
>
>
> *SELECT * FROM GEOMETRY_COLUMNS WHERE coord_dimension not in (2,3);*
>
>
>
> but the query generated by geoserver to fetch the data is :
>
> SELECT ST_AsBinary(ST_Force2D("geometry")) as "geometry" FROM
> "public"."testhy" WHERE […]
>
>
>
> Note the ST_Force2D that removes the Z and M dimension, so there are only
> 2 dimensions, not 4.
>
>
>
>
>
>
>
>
>
> *Hans Yperman*
>
> Department IT
>
> *Vlaams Instituut voor de Zee vzw*
>
> InnovOcean Campus, Jacobsenstraat 1
>
> 8400 Oostende, België
>
>
>
> ☎+32 (0) 59 33 61 13
>
> 📧 hans.yper...@vliz.be
>
> *www.vliz.be <http://www.vliz.be>*
>
>
>
>
> _______________________________________________
> 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
>
--
Regards,
Andrea Aime
==
GeoServer Professional Services from the experts!
Visit http://bit.ly/gs-services-us for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions Group
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
https://www.geosolutionsgroup.com/
http://twitter.com/geosolutions_it
-------------------------------------------------------
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail
_______________________________________________
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
