When entering a WMS query, the list of the available layer appears below.
By adding a new remote layer, we could have more details if they were listed in a table.
We already show TITLE and NAME, and can add the ABSTRACT field.
Otherwise, using a checkbox would avoid the manipulations when adding multiple layers from the same WMS.
Adding an information to let know if a layer is already loaded would also minimize the back and forth when looking or testing layers
-> The category layers (ex: "PPRN_COMMUNE_GASPAR") have only a tag
-> The content layers (ex: "PPRN_COMMUNE_AVALANCHE_APPROUV") have a <layer queryable="1" [or "0"]> tag
This could help to make an automatized sorting of the datas, and to give the possibility for a GetFeatureInfo tool.
It could look like this :
<checkbox (checked and unchangeable if loaded)> TITLE 1 (category) | TITLE 2 (thematic) | NAME | ABSTRACT
When entering a WMS query, the list of the available layer appears below.
By adding a new remote layer, we could have more details if they were listed in a table. We already show TITLE and NAME, and can add the ABSTRACT field.
Otherwise, using a checkbox would avoid the manipulations when adding multiple layers from the same WMS.
Adding an information to let know if a layer is already loaded would also minimize the back and forth when looking or testing layers
Ordering the layers If you take the example of this WMS : https://www.georisques.gouv.fr/services?service=wms&request=getcapabilities The layers are categorized :
-> The category layers (ex: "PPRN_COMMUNE_GASPAR") have only a tag
-> The content layers (ex: "PPRN_COMMUNE_AVALANCHE_APPROUV") have a <layer queryable="1" [or "0"]> tag
This could help to make an automatized sorting of the datas, and to give the possibility for a GetFeatureInfo tool.
It could look like this :
<checkbox (checked and unchangeable if loaded)> TITLE 1 (category) | TITLE 2 (thematic) | NAME | ABSTRACT