Hi Andrea
Le 20/09/2018 à 14:04, Andrea Aime a écrit :
did you install the Marlin renderer? Or are you using the Windows installer?
You can check in the status page if it's there (otherwise you'll get
names like PiscesRenderer
or DuctusRenderer):
Selezione_387.png
If you are using Marlin, one thing to try out is to disable it (how,
depends on how you're running GeoServer).
I just found the problem !
Contrary to what I thought, not all the features where in the result
set. 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.
This also explains why I had all the geometries in pgAdmin : I added the
id field to identify the problematic geometries (stupid...).
BTW, I am running in Windows but I already had the Marlin renderer
installed.
Thanks for your help !
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
