For the sake of completeness :
Le 20/09/2018 à 14:46, Arnaud L. a écrit :
The layer was based on an SQL query with UNIONs.
It "should" have been OK since these features where not real duplicates,
but as I just found out the operator used for DISTINCT queries on
geometries is the "=" operator, and this operator is not a real equality
as is "st_equals".
Replacing UNION with UNION ALL fixed the problem.
As per the blog post by Paul Ramsey
(http://blog.cleverelephant.ca/2017/09/postgis-operators.html), this was
true only in PostGIS up to version 2.3.
Starting with PostGIS 2.4, "=" is a real ST_Equals, and this should not
occur anymore.
Regards
--
Arnaud
_______________________________________________
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
