This issue dates back to januari 2017 and part of it is discussed in
https://osgeo-org.atlassian.net/browse/GEOS-7990
<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
<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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
