I was also thinking about the end-user - an opaque layer group is a good candidate to switch styles as it is then not shown to the user (in the get capabilities document) about the contents of the layer group.
Reading proposal now: The proposal describes this as a choice: *different LayerGroup named configurations, each comprising different sets of layers' styles and eventually layers, in addition to the default one.* For the "eventually layers" part of the proposal I think we would end up with: - single: no problem as no structure is generated - opaque container: no problem as no structure is generated - named tree: suggest listing all the layers from all the the named options (not sure what order to list in, perhaps does not matter?) - container tree: not applicable to have named options, disable styling completely - earth observation: probably watch to associate a different root layer with each "named configuration" Feedback: - "named configuration" - would like to just call this "style" if that is how this is going to be presented in the get capabilities document - the ui *option 1* matches the workflow on wps security and other security screens where we edit parts of a larger document - I like the ui *option 2* and think it would be a good experiment. Suggestion arranging the "Add Layer" " Add Layer Group" "Add Style Group" horizontally, recommend placing an empty "StyleName" heading with an empty label at the end of the list with "Add" at the end of the table (this would result in less scrolling up and down the page). -- Jody Garnett On Fri, 3 Sept 2021 at 00:57, Andrea Aime <[email protected]> wrote: > On Fri, Sep 3, 2021 at 7:32 AM Jody Garnett <[email protected]> > wrote: > >> Do keep in mind that layer groups are very simple right now and are >> pretty much unpacked into GetMap request parameters. I am not sure about >> swapping between different sets of layers (ie contents), as that starts to >> feel more like defining a new layer group mode, rather than a styling of >> its contents. >> > > You are thinking structure of the object here, we are proposing an > end-user functionality instead. When your car navigator switches from day > mode to night mode, is that the same map? > From the user POV, it is, the implementation requires having a layer group > with styles. In this case, the same layers, a different array of styles. > Another situation is switching between a map with lots of detail to one > that has less. To the user, that's still "OSM", but one is "OSM bright" > with all the details, while > the other is "light background", in this case, with different styles and > fewer layers (the high detail ones are omitted): same dataset, two > different styles. > I guess one could achieve the same using a fixed array of layers and using > styles that never display anything to take out the unwanted layers but... > that's really clumsy. > > Cheers > Andrea > > == > > 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 333 8128928 > > 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-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
