On Sun, Jan 1, 2023 at 8:47 AM Jody Garnett <jody.garn...@gmail.com> wrote:
> Andrea: > > I gave it a go; I do not completely like the result - but it is a starting > point. > - I drew this with the root layer turned on, just to establish the tree > structure better > A full tree cannot work, breaks support for pageability (ever seen a pageable tree? I did not). Similarly, we have to avoid the full actual WMS tree treatment, e.g., hiding from top level layers that are part of a group in tree mode. Generally speaking, the computation of the WMS capabilities document requires loading all of the layers in memory. A tree also breaks support for sorting layers by name or type (something I use daily and think it's important to many) What might be possible (but not easy to achieve in Wicket I believe) is to allow expanding elements below a layer group, when the group happens to be in tree mode. > - tree structure is represented by indenting the icon a little bit each > level, we should have lots of width to work with as only a small indent is > indeed to make the visual > - I experimented with just showing the title, and only showing the layer > name when more detail is shown. It provides lots of room :) > The title is often not filled properly, and it's not even mandatory, especially users that manage GeoServer by a REST API might have no use for it at all (GeoServer as a map server for a specific app, rather than open OGC service). To give you an idea, here I removed the title completely, no complaints from GeoServer: [image: image.png] > - I am onlys showing interactive previews above the break, with data > downloads below the break > Makes sense to some extent. I assume Leaflet and MapML are examples of what could be added by plugins. I'm not sure "Tiles" can be provided as a link, we don't have a single "tiles" preview.... we need the "tiled layers" drop down with the choice of what is actually cached (if anything is cached at all). I guess you'd like to choose one as the default, probably thinking web mercator (oh the horror), but unlike "openlayers", cached tiles can be configured by layer and might not have a common gridset or format. Even for the single layer, there is no way to choose which one should be the default for a given layer (e.g., the gridsets cannot be re-ordered easily, the formats cannot be sorted at all). > - more detail shows layer name, abstract, and keywords presented as > hashtags > Nice > - labed "Download Sample" to be clear it is not a complete download > Good idea. "sample" could be removed if the maximum number of elements for preview is configured to be 0 or negative? (it's a configurable setting in the WFS panel). I find repeating "details" over and over is visually annoying. A simple icon with a hover description should do. > - in order to have more space, the list shows all formats, and the filters > at the top filter the list > This cannot work, the same format can appear in two different protocols with different meanings (e.g., TIFF is available for both WMS and WCS, with different outputs). We can have a sort of choice at the top, but choice must be compulsory. > - the filter names are taken from GSIP-202 > <https://github.com/geoserver/geoserver/wiki/GSIP-202> data directory > titles (rather than just WMS > As said before, I want to retain the ability to filter on more than just workspace and layer name. The current preview supports filtering of a "full text search" (see GeoServerDataProvider.getFilter()). This is not to say we should not have workspace and layer filtering, but that the usual full text filter should also be there. Edit: I see you agree, below. > - I experimented with adding legend graphic but it was too busy and > confusing > Yup, plus legend graphic generation is poor in general. > > Advantages: > - There is a clear preview from each service, and each virtual service > - From global WMS navigate to layer preview page with ?formats=maps > - From ne worksapce WFS navigate to layer preview page with > ?workspace=ne&formats=vector > - From ne:coatlines layer Tiles navigate to layer preview page with > ?workspace=ne&layer=coastline&formats=tiles (this would navigate to the > layer preview page as shown listing ne workspace, with coastline layer > details expanded > "navigate to the layer preview page" from where? > > Drawbacks: > - I kind of want to see layer name, personally I would consider making a > configuration toggle, and show the title after the break > - The welcome page workspace and layer selection is not as freeform as the > previous generic search. I think the generic search should still be present > and should search everything (title, name, abstract, keywords) > > > Comment: > - The tree structure is good > Holy cow no it is not! 😂 > - The download sample format toggles are the same number of clicks as a > drop down select - and less annoying > - There is already a dropdown for "more detail", so having > separate dropdowns for selecting individual format seems overkill > I can go for it. > - Filtering with the tree structure is fine (some of the search result > content may show indented and that is okay) > - Should make the formats into blue links so it is obvious they are > clickable > Well they could be simply a <ul> with actual text rather than a list control at this point (and would allow to copy the links, that is actually something quite annoying about the existing "all formats" dropdown. It will use more space, but this design is already using a lot more vertical real estate than the one I originally suggested, when opened... I guess a div can also be given its low local scrolls, if we want to limit vertical size. > As for complete downloads not being available: I wonder if we could > present a page with links providing the download in multiple parts: > - Populated Places: Part 1 > - Populated Places: Part 2 > - Populated Places: Part 3 > Gosh no, some layers might have hundreds of parts. If you want a "full" download, it would be achievable by playing with the content disposition parameters <https://github.com/geoserver/geoserver/blob/707290a3308f2a0c880a47b077a8eff2a660e98a/src/ows/src/main/java/org/geoserver/ows/Dispatcher.java#L1047> , forcing file download. I say "full" in quotes because the WFS still has a configurable limit for maximum number of features returned, which simply cannot be dodged.... the default is large, 1,000,000, but taking a mid-sized dataset like OS Zoomstack has two layers (roads, woodland) that go beyond the limit. Bulk download from WFS, beyond small datasets, is in general a bad idea. Two working ways are: - WPS download with async request - Actual static file (with resumable download using HTTP range reads) Sidenote, I started this conversation out of a personal desire to make cache tiled views more evident (right now hidden in admin panels). However, the conversation is spinning scope towards a major undertaking... it's too big to fit on some hours on the odd saturday a month. Can it be made acceptable, while small and still useful? Otherwise I'll just give up, the conversation will still be useful for someone interested in funding it. 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 339 8844549 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 Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
