[Geoserver-devel] WMS 'base map' option

Hi everyone

We have implemented a base-map option for WMS that allows the user to specify all of the default layers they want rendered when they use the layer name "basemap". For instance, if they list four layers to be the base map, then when they make a WMS request and specify "LAYERS=basmap" then they will get the four layers returned. This will be configurable from the web admin UI for WMS.

Right now this is just for WMS getMap requests, but we want to know if anyone thinks this will be useful for other services.
Thoughts?

--
Brent Owens
(The Open Planning Project)

Doesn't WMS support the idea of nested layers.. so a layer called '
infrastructure' would include the sub-layers roads, rail, paths etc..
wouldn't it be more useful to define the heiracies in the admin tool so
you could have a 'virtual layer' called 'base' but also other groups to
make it easier to control what type of info you get back. not sure how
many clients support this properly though.

-ivan

-----Original Message-----
From: geoserver-devel-bounces@lists.sourceforge.net
[mailto:geoserver-devel-bounces@lists.sourceforge.net] On Behalf Of
Brent Owens
Sent: Tuesday, 22 August 2006 5:35 AM
To: Geoserver-devel
Subject: [Geoserver-devel] WMS 'base map' option

Hi everyone

We have implemented a base-map option for WMS that allows the user to
specify all of the default layers they want rendered when they use the
layer name "basemap". For instance, if they list four layers to be the
base map, then when they make a WMS request and specify "LAYERS=basmap"
then they will get the four layers returned. This will be configurable
from the web admin UI for WMS.

Right now this is just for WMS getMap requests, but we want to know if
anyone thinks this will be useful for other services.
Thoughts?

--
Brent Owens
(The Open Planning Project)

------------------------------------------------------------------------
-
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Interesting, I didn't know that was the point of the nested layers in WMS. I think Alessio may have done some work on WCS branch to define hierarchies. If so we could add the concept of groups of layers there as well, if he hasn't already.

Chris

Ivan Price wrote:

Doesn't WMS support the idea of nested layers.. so a layer called '
infrastructure' would include the sub-layers roads, rail, paths etc..
wouldn't it be more useful to define the heiracies in the admin tool so
you could have a 'virtual layer' called 'base' but also other groups to
make it easier to control what type of info you get back. not sure how
many clients support this properly though.

-ivan

-----Original Message-----
From: geoserver-devel-bounces@lists.sourceforge.net
[mailto:geoserver-devel-bounces@lists.sourceforge.net] On Behalf Of
Brent Owens
Sent: Tuesday, 22 August 2006 5:35 AM
To: Geoserver-devel
Subject: [Geoserver-devel] WMS 'base map' option

Hi everyone

We have implemented a base-map option for WMS that allows the user to
specify all of the default layers they want rendered when they use the
layer name "basemap". For instance, if they list four layers to be the
base map, then when they make a WMS request and specify "LAYERS=basmap" then they will get the four layers returned. This will be configurable
from the web admin UI for WMS.

Right now this is just for WMS getMap requests, but we want to know if
anyone thinks this will be useful for other services.
Thoughts?

--
Brent Owens
(The Open Planning Project)

------------------------------------------------------------------------
-
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

!DSPAM:1003,44eea45b88821775926497!

--
Chris Holmes
The Open Planning Project
http://topp.openplans.org

Thanks Ivan, you beat me to the punch on this one :slight_smile:

The other nice thing to do with nesting is define:
- Roads
-- Roads at scale 1
-- Roads at scale 2
-- Roads at scale 3

So that users can ask for "Roads" and the WMS (combined with SLD for each layer) can choose level of detailed required for the picture, resulting in a much faster experience.
Jody

Doesn't WMS support the idea of nested layers.. so a layer called '
infrastructure' would include the sub-layers roads, rail, paths etc..
wouldn't it be more useful to define the heiracies in the admin tool so
you could have a 'virtual layer' called 'base' but also other groups to
make it easier to control what type of info you get back. not sure how
many clients support this properly though.

-ivan

-----Original Message-----
From: geoserver-devel-bounces@lists.sourceforge.net
[mailto:geoserver-devel-bounces@lists.sourceforge.net] On Behalf Of
Brent Owens
Sent: Tuesday, 22 August 2006 5:35 AM
To: Geoserver-devel
Subject: [Geoserver-devel] WMS 'base map' option

Hi everyone

We have implemented a base-map option for WMS that allows the user to
specify all of the default layers they want rendered when they use the
layer name "basemap". For instance, if they list four layers to be the
base map, then when they make a WMS request and specify "LAYERS=basmap" then they will get the four layers returned. This will be configurable
from the web admin UI for WMS.

Right now this is just for WMS getMap requests, but we want to know if
anyone thinks this will be useful for other services.
Thoughts?

--
Brent Owens
(The Open Planning Project)

------------------------------------------------------------------------
-
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
  

Le Vendredi 25 Août 2006 10:57, Jody Garnett a écrit :

Hi,

I don't know if it's worth writting this, but :

- We have several dabases representing objects at different ranges of scales;
- We have defined for each database/featureType an SLD that tries to render
the object taking into account the current scale (featureType nesting) ;
- We are using mapbuilder to define the base type (thematic featureType) as
follows :

   <Layer queryable="0" hidden="0">
      <Server service="wms" version="1.1.0" title="wms">
        <OnlineResource xlink:type="simple"
xlink:href="http://localhost:8080/geoserver/wms?&quot;/&gt;
      </Server>
      
<Name>contexte:egm_trans_l_lambe,contexte:erm_transl_l_lambe,bdcarto:tron_rou,bdtopo:tronrout,bdtopo:tronrout</Name>
      <Title xml:lang="fr">Routes</Title>
      <Title xml:lang="en">Roads</Title>
      <SRS>EPSG:27572</SRS>
      <FormatList>
        <Format current="1">image/png</Format>
      </FormatList>
      <StyleList>
        <Style
current="1"><Name>egm_road,erm_road,bdcarto_tron_rou,bdtopo_tronrout_secon,bdtopo_tronrout_princ</Name></Style>
      </StyleList>
    </Layer>

Hope this help,

didier

Thanks Ivan, you beat me to the punch on this one :slight_smile:

The other nice thing to do with nesting is define:
- Roads
-- Roads at scale 1
-- Roads at scale 2
-- Roads at scale 3

So that users can ask for "Roads" and the WMS (combined with SLD for
each layer) can choose level of detailed required for the picture,
resulting in a much faster experience.
Jody

> Doesn't WMS support the idea of nested layers.. so a layer called '
> infrastructure' would include the sub-layers roads, rail, paths etc..
> wouldn't it be more useful to define the heiracies in the admin tool so
> you could have a 'virtual layer' called 'base' but also other groups to
> make it easier to control what type of info you get back. not sure how
> many clients support this properly though.
>
> -ivan
>
>
> -----Original Message-----
> From: geoserver-devel-bounces@lists.sourceforge.net
> [mailto:geoserver-devel-bounces@lists.sourceforge.net] On Behalf Of
> Brent Owens
> Sent: Tuesday, 22 August 2006 5:35 AM
> To: Geoserver-devel
> Subject: [Geoserver-devel] WMS 'base map' option
>
> Hi everyone
>
> We have implemented a base-map option for WMS that allows the user to
> specify all of the default layers they want rendered when they use the
> layer name "basemap". For instance, if they list four layers to be the
> base map, then when they make a WMS request and specify "LAYERS=basmap"
> then they will get the four layers returned. This will be configurable
> from the web admin UI for WMS.
>
> Right now this is just for WMS getMap requests, but we want to know if
> anyone thinks this will be useful for other services.
> Thoughts?
>
> --
> Brent Owens
> (The Open Planning Project)
>
>
> ------------------------------------------------------------------------
> -
> Using Tomcat but need to do more? Need to support web services,
> security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache
> Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier Download IBM WebSphere Application Server v.1.0.1 based on Apache
> Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

That is interesting, the approach I describe is the usual one for WMS (because if a user just makes the "road" layer they do not have to know anything more in order to take advantage of different resolutions and so on).

You approach is very creative :slight_smile: And a similar idea would be interesting to allow WFS to serve up different qualities of data.
Jody

Le Vendredi 25 Août 2006 10:57, Jody Garnett a écrit :

Hi,

I don't know if it's worth writting this, but :

- We have several dabases representing objects at different ranges of scales;
- We have defined for each database/featureType an SLD that tries to render the object taking into account the current scale (featureType nesting) ;
- We are using mapbuilder to define the base type (thematic featureType) as follows :

   <Layer queryable="0" hidden="0">
      <Server service="wms" version="1.1.0" title="wms">
        <OnlineResource xlink:type="simple" xlink:href="http://localhost:8080/geoserver/wms?&quot;/&gt;
      </Server>
      <Name>contexte:egm_trans_l_lambe,contexte:erm_transl_l_lambe,bdcarto:tron_rou,bdtopo:tronrout,bdtopo:tronrout</Name>
      <Title xml:lang="fr">Routes</Title>
      <Title xml:lang="en">Roads</Title>
      <SRS>EPSG:27572</SRS>
      <FormatList>
        <Format current="1">image/png</Format>
      </FormatList>
      <StyleList>
        <Style current="1"><Name>egm_road,erm_road,bdcarto_tron_rou,bdtopo_tronrout_secon,bdtopo_tronrout_princ</Name></Style>
      </StyleList>
    </Layer>

Hope this help,

didier

Thanks Ivan, you beat me to the punch on this one :slight_smile:

The other nice thing to do with nesting is define:
- Roads
-- Roads at scale 1
-- Roads at scale 2
-- Roads at scale 3

So that users can ask for "Roads" and the WMS (combined with SLD for
each layer) can choose level of detailed required for the picture,
resulting in a much faster experience.
Jody

Doesn't WMS support the idea of nested layers.. so a layer called '
infrastructure' would include the sub-layers roads, rail, paths etc..
wouldn't it be more useful to define the heiracies in the admin tool so
you could have a 'virtual layer' called 'base' but also other groups to
make it easier to control what type of info you get back. not sure how
many clients support this properly though.

-ivan

-----Original Message-----
From: geoserver-devel-bounces@lists.sourceforge.net
[mailto:geoserver-devel-bounces@lists.sourceforge.net] On Behalf Of
Brent Owens
Sent: Tuesday, 22 August 2006 5:35 AM
To: Geoserver-devel
Subject: [Geoserver-devel] WMS 'base map' option

Hi everyone

We have implemented a base-map option for WMS that allows the user to
specify all of the default layers they want rendered when they use the
layer name "basemap". For instance, if they list four layers to be the
base map, then when they make a WMS request and specify "LAYERS=basmap"
then they will get the four layers returned. This will be configurable
from the web admin UI for WMS.

Right now this is just for WMS getMap requests, but we want to know if
anyone thinks this will be useful for other services.
Thoughts?

--
Brent Owens
(The Open Planning Project)

------------------------------------------------------------------------
-
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
      

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
    
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
  

Most clients support it well, servers less so.

ArcIMS doesnt support it at all (last version I looked at)
Mapserver supports a single configurable grouping (1 level of nesting)
Geoserver doesnt support at all.

Yes - it would be a really good thing.

One use for it would to to force "aliases" to make geoserver's internal naming scheme match an external requirement.

Rob A

Ivan Price wrote:

Doesn't WMS support the idea of nested layers.. so a layer called '
infrastructure' would include the sub-layers roads, rail, paths etc..
wouldn't it be more useful to define the heiracies in the admin tool so
you could have a 'virtual layer' called 'base' but also other groups to
make it easier to control what type of info you get back. not sure how
many clients support this properly though.

-ivan

-----Original Message-----
From: geoserver-devel-bounces@lists.sourceforge.net
[mailto:geoserver-devel-bounces@lists.sourceforge.net] On Behalf Of
Brent Owens
Sent: Tuesday, 22 August 2006 5:35 AM
To: Geoserver-devel
Subject: [Geoserver-devel] WMS 'base map' option

Hi everyone

We have implemented a base-map option for WMS that allows the user to
specify all of the default layers they want rendered when they use the
layer name "basemap". For instance, if they list four layers to be the
base map, then when they make a WMS request and specify "LAYERS=basmap" then they will get the four layers returned. This will be configurable
from the web admin UI for WMS.

Right now this is just for WMS getMap requests, but we want to know if
anyone thinks this will be useful for other services.
Thoughts?

--
Brent Owens
(The Open Planning Project)

------------------------------------------------------------------------
-
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel