I would create a materialized view in PostGIS that randomizes the locations a bit - and then publish that.
There are some geoserver functions for generating attract fill patterns Fills with randomized symbols — GeoServer 2.24.x User Manual <https://docs.geoserver.org/latest/en/user/styling/sld/extensions/randomized.html> and then make a circle in the area, and let the random fill drop in a symbol or two as appropriate. Turn off GetFeatureInfo or folks can just query to get the raw original data anyways. You could also do something fun like make a GeoServer SQL View (pretty much a query)... But it would be hard to keep the result stable as users pan and zoom around; or during tile generation. I would make a table of random values; and then index into the table based on the FID of the row in order to get some offsets to apply to the point locations. Materialized view in PostGIS would be easiest. -- Jody Garnett On Wed, Apr 19, 2023 at 8:24 PM Phil Scadden <p.scad...@gns.cri.nz> wrote: > I have survey point data (soil geochemistry) that is representative for an > area but on display, I need to jitter the point location so the actual > location cannot be discovered. For users point of view, you can click on > points and view data, but every time you refresh (or preferably every time > zoom) the point location will change within a certain parameters. > > > > An example https://iupui-earth-science.shinyapps.io/MME_Global/ > > > > > > Any idea of how I might achieve this with geoserver? Anyone done similar?? > > > > All I can think of is to draw from a very custom WFS source that is doing > the jitter. > > > > ________________________________________________ > > Ngā mihi, Nā Phil Scadden > > Te Raraunga me te Tātaritanga Mokowā Aronuku (Geospatial Data and > Analysis) > > *GNS Science* *Te Pῡ Ao* > > 764 Cumberland St, Private Bag 1930, > > Dunedin, New Zealand Ph +64 3 4799663, 027 3463185 > > > > “Whāia te iti kahurangi ki te tūohu koe me he maunga teitei” > > > Notice: This email and any attachments are confidential and may not be > used, published or redistributed without the prior written consent of the > Institute of Geological and Nuclear Sciences Limited (GNS Science). If > received in error please destroy and immediately notify GNS Science. Do not > copy or disclose the contents. > _______________________________________________ > 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 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
