[Geoserver-users] How to configure nested layer structure in WMS capabilities

GeoServer GeoServer User
1

All,

Is there any way to configure GeoServer to generate nested/tree layer
structure in its WMS GetCapabilities response?

For example, I have base layers a,b,c,d,e and I would like to create
group-layer g1 (a,b,c) and g2 (d,e) in such a way that it looks like below
in WMS capabilities files:

geoserver
  |_g1
       |_a
       |_b
       |_c
  |_g2
       |_d
       |_e

In the doc I only see a way to create a new layer-group which can replace a
list of layer in WMS Getmap request but it's not reflecting the relationship
between those layers.

Thanks
--
View this message in context: http://www.nabble.com/How-to-configure-nested-layer-structure-in-WMS-capabilities-tp19518255p19518255.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

2

Hi,

You should be able to use the "wms path" (middle of the page) for this functionality. You can set it to sopmethign like "/g1/a" it should achieve the desired effect.

-Justin

AugustTown wrote:

All,

Is there any way to configure GeoServer to generate nested/tree layer
structure in its WMS GetCapabilities response?

For example, I have base layers a,b,c,d,e and I would like to create
group-layer g1 (a,b,c) and g2 (d,e) in such a way that it looks like below
in WMS capabilities files:

geoserver
  |_g1
       |_a
       |_b
       |_c
  |_g2
       |_d
       |_e

In the doc I only see a way to create a new layer-group which can replace a
list of layer in WMS Getmap request but it's not reflecting the relationship
between those layers.

Thanks

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for the open source geospatial stack.

3

Thanks Justin,

Another thing I noticed is that if I don't provide a "WMS Path" or give it
"/" then the layer will be directly under root layer. But whenever I restart
the GeoServer, WMS Path will be set to its feature type name automatically.

Is that an expected behavior?

Thanks

AugustTown wrote:

All,

Is there any way to configure GeoServer to generate nested/tree layer
structure in its WMS GetCapabilities response?

For example, I have base layers a,b,c,d,e and I would like to create
group-layer g1 (a,b,c) and g2 (d,e) in such a way that it looks like below
in WMS capabilities files:

geoserver
  |_g1
       |_a
       |_b
       |_c
  |_g2
       |_d
       |_e

In the doc I only see a way to create a new layer-group which can replace
a list of layer in WMS Getmap request but it's not reflecting the
relationship between those layers.

Thanks

--
View this message in context: http://www.nabble.com/How-to-configure-nested-layer-structure-in-WMS-capabilities-tp19518255p19538396.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

4

Justin,

I just found that whenever I restart the GeoServer, WMS path for each
feature type will be reset to its feature type name. Is it a bug?

Thanks

AugustTown wrote:

All,

Is there any way to configure GeoServer to generate nested/tree layer
structure in its WMS GetCapabilities response?

For example, I have base layers a,b,c,d,e and I would like to create
group-layer g1 (a,b,c) and g2 (d,e) in such a way that it looks like below
in WMS capabilities files:

geoserver
  |_g1
       |_a
       |_b
       |_c
  |_g2
       |_d
       |_e

In the doc I only see a way to create a new layer-group which can replace
a list of layer in WMS Getmap request but it's not reflecting the
relationship between those layers.

Thanks

--
View this message in context: http://www.nabble.com/How-to-configure-nested-layer-structure-in-WMS-capabilities-tp19518255p19538519.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

5

AugustTown escribió:

Justin,

I just found that whenever I restart the GeoServer, WMS path for each
feature type will be reset to its feature type name. Is it a bug?
  

Sounds likely. Which GeoServer version were you using? and just to get it clearer, you mean that if you set the wms path property it works, but once you restart the layers lose the wms path you set and defaults to its feature type name?
Please confirm that cause depending on the geoserver version it may be just a problem of the new config wrappers either not persisting or loading the property, which certainly will be an easy fix.

regards,
Gabriel

Thanks

AugustTown wrote:
  

All,

Is there any way to configure GeoServer to generate nested/tree layer
structure in its WMS GetCapabilities response?

For example, I have base layers a,b,c,d,e and I would like to create
group-layer g1 (a,b,c) and g2 (d,e) in such a way that it looks like below
in WMS capabilities files:

geoserver
  |_g1
       |_a
       |_b
       |_c
  |_g2
       |_d
       |_e

In the doc I only see a way to create a new layer-group which can replace
a list of layer in WMS Getmap request but it's not reflecting the
relationship between those layers.

Thanks

6

Gabriel,

I am using GeoServer 1.7.0 beta2 and yes I got exactly the problem you
described below.

If you set the wms path property it works, but
once you restart the layers lose the wms path you set and defaults to
its feature type name

Thanks

Gabriel Roldán-5 wrote:

AugustTown escribió:

Justin,

I just found that whenever I restart the GeoServer, WMS path for each
feature type will be reset to its feature type name. Is it a bug?
  

Sounds likely. Which GeoServer version were you using? and just to get
it clearer, you mean that if you set the wms path property it works, but
once you restart the layers lose the wms path you set and defaults to
its feature type name?
Please confirm that cause depending on the geoserver version it may be
just a problem of the new config wrappers either not persisting or
loading the property, which certainly will be an easy fix.

regards,
Gabriel

Thanks

AugustTown wrote:
  

All,

Is there any way to configure GeoServer to generate nested/tree layer
structure in its WMS GetCapabilities response?

For example, I have base layers a,b,c,d,e and I would like to create
group-layer g1 (a,b,c) and g2 (d,e) in such a way that it looks like
below
in WMS capabilities files:

geoserver
  |_g1
       |_a
       |_b
       |_c
  |_g2
       |_d
       |_e

In the doc I only see a way to create a new layer-group which can
replace
a list of layer in WMS Getmap request but it's not reflecting the
relationship between those layers.

Thanks

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
View this message in context: http://www.nabble.com/How-to-configure-nested-layer-structure-in-WMS-capabilities-tp19518255p19541627.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

7

Most likely an issue with the new configuration backend added on 1.7.x. I will schedule a jira for 1.7.0-RC3 to fix this.

http://jira.codehaus.org/browse/GEOS-2241

Thanks for the bug report.

Could you perhaps test it out on 1.6.5 and let us know if it works properly for you?

-Justin

AugustTown wrote:

Gabriel,

I am using GeoServer 1.7.0 beta2 and yes I got exactly the problem you
described below.

If you set the wms path property it works, but once you restart the layers lose the wms path you set and defaults to its feature type name

Thanks

Gabriel Roldán-5 wrote:

AugustTown escribió:

Justin,

I just found that whenever I restart the GeoServer, WMS path for each
feature type will be reset to its feature type name. Is it a bug?
  

Sounds likely. Which GeoServer version were you using? and just to get it clearer, you mean that if you set the wms path property it works, but once you restart the layers lose the wms path you set and defaults to its feature type name?
Please confirm that cause depending on the geoserver version it may be just a problem of the new config wrappers either not persisting or loading the property, which certainly will be an easy fix.

regards,
Gabriel

Thanks

AugustTown wrote:
  

All,

Is there any way to configure GeoServer to generate nested/tree layer
structure in its WMS GetCapabilities response?

For example, I have base layers a,b,c,d,e and I would like to create
group-layer g1 (a,b,c) and g2 (d,e) in such a way that it looks like
below
in WMS capabilities files:

geoserver
  |_g1
       |_a
       |_b
       |_c
  |_g2
       |_d
       |_e

In the doc I only see a way to create a new layer-group which can
replace
a list of layer in WMS Getmap request but it's not reflecting the
relationship between those layers.

Thanks

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.