Hi Ian an Andrea,
thanks for your input, I really appreciate it.
your answers helped, thanks.
In my case I only need to change the MinScaleDenoms inside the SLD to
make the styleing-rule available for another zoom-scale. So no need to
recreate the whole bunch of tiles, only seed another additional scale.
My SLDs currently have the MinScaleDnoms fitting to the used
tiling-scheme-scale-breaks though.
As a workarround I will mount an empty tile-storage-volume, do my
changes inside the SLDs, let geoserver delete all (non-existant) tiles
and remount the storage with the seeded tiles back in, and start seeding
the additional scale-level. This is untested though, hope this will
do...
I hoped there was somewhere a hidden variable to set to stop the
cache-truncation.
Anyway, thanks for your help!
Best
Stephan
Am 22.6.2023 09:17, schrieb Andrea Aime:
On Wed, Jun 21, 2023 at 4:44 PM Ian Turton <ijtur...@gmail.com> wrote:
Again GeoServer has no way of knowing (without a lot of work) which
tiles are invalid with a style change so it needs to redraw all of
them
A comparison of two SLD trees would be possible, figuring out if the
edits changed the tiles, but as you say,
it's going to be complicated. Having the automatic tile drop automation
admin controllable (on/off) is certainly easier.
There are some classes of edits that could be identified, which do not
affect, or just partially affect, the tiles:
* Changes rule names, titles and the like
* Changes in a rule that is active only in a given scale range (just
drop tiles in such range)
* Changes in a rule that matches only certain features (attribute
filter), figure out their bbox if there is a quick way to do so, only
drop in the bbox
As said, far away from trivial... a parallel scan of the two SLD object
trees would have to be implemented, which goes
hunt for certain types of differences.
Cheers
Andrea
==
GeoServer Professional Services from the experts!
Visit http://bit.ly/gs-services-us [1] 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/ [2]
http://twitter.com/geosolutions_it [3]
-------------------------------------------------------
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
Links:
------
[1] http://bit.ly/gs-services-us
[2] https://www.geosolutionsgroup.com/
[3] http://twitter.com/geosolutions_it
_______________________________________________
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
