Re: feature: ability to set a layer group as root layer

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: feature: ability to set a layer group as root layer

Paul van Genuchten
This issue dates back to januari 2017 and part of it is discussed in https://osgeo-org.atlassian.net/browse/GEOS-7990
We have a use case of many layers in a service that are annual snapshots. the order how these layers are advertised in capabilities is important (this is the order in which they are shown when you open the capabilities document in qgis/arcgis). Geoserver instead uses an alphabetic order which is not optimal here. 

The improvement proposal in 2017 (https://github.com/PascalLike/geoserver/tree/GEOS-7990) was a start to set up a UI to set up ordering for layers (similar to how layers are ordered in layergroups), but for various reasons never made it to core.

In stead I want to propose a more simple approach as a start in which a setting on wms-service-level is introduced that deactivates the alphabetical order, on which geoserver will fall back to an order based on order of addition. 

What do people think? Or would it be better to make order more explicit?


_______________________________________________
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


[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Reply | Threaded
Open this post in threaded view
|

Re: feature: ability to set a layer group as root layer

geowolf
On Thu, Jan 31, 2019 at 4:54 PM Paul van Genuchten <[hidden email]> wrote:
This issue dates back to januari 2017 and part of it is discussed in https://osgeo-org.atlassian.net/browse/GEOS-7990
We have a use case of many layers in a service that are annual snapshots. the order how these layers are advertised in capabilities is important (this is the order in which they are shown when you open the capabilities document in qgis/arcgis). Geoserver instead uses an alphabetic order which is not optimal here. 

The improvement proposal in 2017 (https://github.com/PascalLike/geoserver/tree/GEOS-7990) was a start to set up a UI to set up ordering for layers (similar to how layers are ordered in layergroups), but for various reasons never made it to core.

In stead I want to propose a more simple approach as a start in which a setting on wms-service-level is introduced that deactivates the alphabetical order, on which geoserver will fall back to an order based on order of addition. 

I don't think it's going to work, the order you'd get is at best mimicking the order that the file system returns file on (which is not predictable across
operating systems), and what's more GeoServer now loads layers at startup with a multithreaded approach, meaning even that order won't be respected

Cheers
Andrea

==

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it 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-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


[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users