Hello,
We have a very large number of files that we would like to serve with
WMS. Is there a way to configure Geoserver so that the data can be
organized into groups associated with several different WMS
getCapabilities responses -- to avoid overwhelming the user with a
single giant getCapabilities response?
Thank you so much,
Barbara
Hi Barbara,
This is something we are planning to implement for 2.0 but don't currently have. Basically be able to call service=wms&request=getCapabilities&map=mymap
Similar to how you can specify a specific mapfile with MapServer and only get a subset of layers.
Something people have done in the past as a workaround is generate a WMS getCaps doc with all the layers, save the file somewhere web accessible and then manually delete the unwanted layers from the file. Then have the client make the wms getCaps request to static file rather than the live service.
The downside of such an approach is of course it is not dynamic.
-Justin
Barbara O'Barr wrote:
Hello,
We have a very large number of files that we would like to serve with
WMS. Is there a way to configure Geoserver so that the data can be
organized into groups associated with several different WMS
getCapabilities responses -- to avoid overwhelming the user with a
single giant getCapabilities response?
Thank you so much,
Barbara------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
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.
Hi to the GeoServer community:
I have some questions regarding WMS Capabilities and WMS layers.
I would like to modify the WMS Capabilities document, because I need to offer only the Layer-Groups when doing the GetCapabilities request. But looking at the document generated, I see that information about styles are only associated to the layers I do not want to show.
Anyway, the main problem I have found is that, when using a GIS client, layers and layers group consisting of those ones appear, which can be very confusing to the users. How can we hide these layers to the users? Is it possible?
According to the mail attached, in order to change the Capabilities document, should I save the document somewhere and modify it? How can I do to show this static file?
Thanks in advance,
José Miguel
P.D.: Some weeks ago I left a question from Justin without response regarding GetFeatureInfo templates. I was very busy and I could not reproduce the error I got. However, I suppose I will have time to spend on it in the future!
José Miguel Rubio Iglesias
Subdirección General de Aplicaciones Geográficas
Instituto Geográfico Nacional
C/General Ibáñez de Ibero, 3 28003 MADRID
Despacho: A 0002 Teléfono: 91 597 97 51
E-mail: jmrubio@anonymised.com
-----Mensaje original-----
De: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Enviado el: martes, 13 de enero de 2009 21:51
Para: Barbara O’Barr
CC: geoserver-users@lists.sourceforge.net
Asunto: Re: [Geoserver-users] WMS configuration - multiple getCapabilities responses
Hi Barbara,
This is something we are planning to implement for 2.0 but don’t
currently have. Basically be able to call
service=wms&request=getCapabilities&map=mymap
Similar to how you can specify a specific mapfile with MapServer and
only get a subset of layers.
Something people have done in the past as a workaround is generate a WMS
getCaps doc with all the layers, save the file somewhere web accessible
and then manually delete the unwanted layers from the file. Then have
the client make the wms getCaps request to static file rather than the
live service.
The downside of such an approach is of course it is not dynamic.
-Justin
Barbara O’Barr wrote:
Hello,
We have a very large number of files that we would like to serve with
WMS. Is there a way to configure Geoserver so that the data can be
organized into groups associated with several different WMS
getCapabilities responses – to avoid overwhelming the user with a
single giant getCapabilities response?
Thank you so much,
Barbara
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
Geoserver-users mailing list
https://lists.sourceforge.net/lists/listinfo/geoserver-users
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Hi,
Well the static file can be served by any web server, like apache. You can also place it in the geoserver www (under the root of the data directory) which can be used to serve static files.
However, as of 1.7.3 there is an alternative for filtering the capabilities document. You can specify only the layers which come from a particular namespace by appending the "namespace=<ns>" parameter to the capabilities request. However layer groups do not belong to a namespace so they show up regardless of the namespace filter.
So a possible workaround is to place all of your layers in a particular namespace (ns1), and then create a second empty namespace (ns2). Create all the layer groups you need, and then if you request the wms caps doc filtered by ns2 you should only see the layer groups.
Hope that helps.
-Justin
Rubio Iglesias José Miguel wrote:
Hi to the GeoServer community:
I have some questions regarding WMS Capabilities and WMS layers.
I would like to modify the WMS Capabilities document, because I need to offer only the Layer-Groups when doing the GetCapabilities request. But looking at the document generated, I see that information about styles are only associated to the layers I do not want to show.
Anyway, the main problem I have found is that, when using a GIS client, layers and layers group consisting of those ones appear, which can be very confusing to the users. How can we hide these layers to the users? Is it possible?
According to the mail attached, in order to change the Capabilities document, should I save the document somewhere and modify it? How can I do to show this static file?
Thanks in advance,
José Miguel
P.D.: Some weeks ago I left a question from Justin without response regarding GetFeatureInfo templates. I was very busy and I could not reproduce the error I got. However, I suppose I will have time to spend on it in the future!
------------------------------------------------------------------------------
*/José Miguel Rubio Iglesias/*
*/Subdirección General de Aplicaciones Geográficas/*
*/Instituto Geográfico Nacional/*
*/C/General Ibáñez de Ibero, 3 28003 MADRID/*
*/Despacho: A 0002 Teléfono: 91 597 97 51/*
*/E-mail: jmrubio@anonymised.com <mailto:jmrubio@anonymised.com> /*
-----Mensaje original-----
De: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Enviado el: martes, 13 de enero de 2009 21:51
Para: Barbara O'Barr
CC: geoserver-users@lists.sourceforge.net
Asunto: Re: [Geoserver-users] WMS configuration - multiple getCapabilities responsesHi Barbara,
This is something we are planning to implement for 2.0 but don't
currently have. Basically be able to call
service=wms&request=getCapabilities&map=mymap
Similar to how you can specify a specific mapfile with MapServer and
only get a subset of layers.
Something people have done in the past as a workaround is generate a WMS
getCaps doc with all the layers, save the file somewhere web accessible
and then manually delete the unwanted layers from the file. Then have
the client make the wms getCaps request to static file rather than the
live service.
The downside of such an approach is of course it is not dynamic.
-Justin
Barbara O'Barr wrote:
Hello,
We have a very large number of files that we would like to serve with
WMS. Is there a way to configure Geoserver so that the data can be
organized into groups associated with several different WMS
getCapabilities responses -- to avoid overwhelming the user with a
single giant getCapabilities response?
Thank you so much,
Barbara
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
_______________________________________________
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.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
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.
Hi again,
Thanks for your help, Justin.
So you say I can place a static file in \\GeoServer_Data_Dir\www? How can I do to show that document when doing a GetCapabilities request? I am trying to do it, but I am a bit confused. I would be pleased if you could help me on that.
On the other hand, I have been investigated and it is possible to change localhost:port in the Capabilities document using the option Proxy Base URL. However, I need to change the complete path of the WMS shown in the document (I previously changed the WMS URL using Apache). Is it possible to do it without using a static file?
Thanks in advance.
Regards,
José Miguel
-----Mensaje original-----
De: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Enviado el: lunes, 13 de abril de 2009 15:29
Para: Rubio Iglesias José Miguel
CC: geoserver users
Asunto: Re: [Geoserver-users] WMS configuration - Capabilities document configuration
Hi,
Well the static file can be served by any web server, like apache. You
can also place it in the geoserver www (under the root of the data
directory) which can be used to serve static files.
However, as of 1.7.3 there is an alternative for filtering the
capabilities document. You can specify only the layers which come from a
particular namespace by appending the "namespace=<ns>" parameter to the
capabilities request. However layer groups do not belong to a namespace
so they show up regardless of the namespace filter.
So a possible workaround is to place all of your layers in a particular
namespace (ns1), and then create a second empty namespace (ns2). Create
all the layer groups you need, and then if you request the wms caps doc
filtered by ns2 you should only see the layer groups.
Hope that helps.
-Justin
Rubio Iglesias José Miguel wrote:
Hi to the GeoServer community:
I have some questions regarding WMS Capabilities and WMS layers.
I would like to modify the WMS Capabilities document, because I need to
offer only the Layer-Groups when doing the GetCapabilities request. But
looking at the document generated, I see that information about styles
are only associated to the layers I do not want to show.
Anyway, the main problem I have found is that, when using a GIS client,
layers and layers group consisting of those ones appear, which can be
very confusing to the users. How can we hide these layers to the users?
Is it possible?
According to the mail attached, in order to change the Capabilities
document, should I save the document somewhere and modify it? How can I
do to show this static file?
Thanks in advance,
José Miguel
P.D.: Some weeks ago I left a question from Justin without response
regarding GetFeatureInfo templates. I was very busy and I could not
reproduce the error I got. However, I suppose I will have time to spend
on it in the future!
------------------------------------------------------------------------------
*/José Miguel Rubio Iglesias/*
*/Subdirección General de Aplicaciones Geográficas/*
*/Instituto Geográfico Nacional/*
*/C/General Ibáñez de Ibero, 3 28003 MADRID/*
*/Despacho: A 0002 Teléfono: 91 597 97 51/*
*/E-mail: jmrubio@anonymised.com <mailto:jmrubio@anonymised.com> /*
-----Mensaje original-----
De: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Enviado el: martes, 13 de enero de 2009 21:51
Para: Barbara O'Barr
CC: geoserver-users@lists.sourceforge.net
Asunto: Re: [Geoserver-users] WMS configuration - multiple
getCapabilities responses
Hi Barbara,
This is something we are planning to implement for 2.0 but don't
currently have. Basically be able to call
service=wms&request=getCapabilities&map=mymap
Similar to how you can specify a specific mapfile with MapServer and
only get a subset of layers.
Something people have done in the past as a workaround is generate a WMS
getCaps doc with all the layers, save the file somewhere web accessible
and then manually delete the unwanted layers from the file. Then have
the client make the wms getCaps request to static file rather than the
live service.
The downside of such an approach is of course it is not dynamic.
-Justin
Barbara O'Barr wrote:
Hello,
We have a very large number of files that we would like to serve with
WMS. Is there a way to configure Geoserver so that the data can be
organized into groups associated with several different WMS
getCapabilities responses -- to avoid overwhelming the user with a
single giant getCapabilities response?
Thank you so much,
Barbara
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
_______________________________________________
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.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
_______________________________________________
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.
Hi Rubio,
the getcapabilities document does not normally have to come from /geoserver/wms , you should just tell your client to use http://youserver.org/geoserver/www/modified_document.xml instead of http://youserver.org/geoserver/wms?service=wms&request=getcapabilities&version=1.1.0
Since you are already using Apache, you could also use mod_rewrite to intercept the request transparently:
RewriteEngine On
RewriteCond ${QUERY_STRING} ^(.*)request=getcapabilities(.*)$ [NC]
RewriteRule ^/yourpath/wms$ modified_document.xml [L]
I think you are right that PROXY_BASE_URL will not change the context path ( /geoserver ), feel free to file a feature request in JIRA.
-Arne
Rubio Iglesias José Miguel wrote:
Hi again,
Thanks for your help, Justin.
So you say I can place a static file in \\*GeoServer_Data_Dir\www*? How can I do to show that document when doing a GetCapabilities request? I am trying to do it, but I am a bit confused. I would be pleased if you could help me on that.
On the other hand, I have been investigated and it is possible to change */localhost:port/* in the Capabilities document using the option *Proxy Base URL. *However, I need to change the complete path of the WMS shown in the document (I previously changed the WMS URL using Apache). Is it possible to do it without using a static file?
Thanks in advance.
Regards,
José Miguel
-----Mensaje original-----
De: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Enviado el: lunes, 13 de abril de 2009 15:29
Para: Rubio Iglesias José Miguel
CC: geoserver users
Asunto: Re: [Geoserver-users] WMS configuration - Capabilities document configurationHi,
Well the static file can be served by any web server, like apache. You
can also place it in the geoserver www (under the root of the data
directory) which can be used to serve static files.
However, as of 1.7.3 there is an alternative for filtering the
capabilities document. You can specify only the layers which come from a
particular namespace by appending the "namespace=<ns>" parameter to the
capabilities request. However layer groups do not belong to a namespace
so they show up regardless of the namespace filter.
So a possible workaround is to place all of your layers in a particular
namespace (ns1), and then create a second empty namespace (ns2). Create
all the layer groups you need, and then if you request the wms caps doc
filtered by ns2 you should only see the layer groups.
Hope that helps.
-Justin
Rubio Iglesias José Miguel wrote:
> Hi to the GeoServer community:
>
>
>
> I have some questions regarding WMS Capabilities and WMS layers.
>
>
>
> I would like to modify the WMS Capabilities document, because I need to
> offer only the Layer-Groups when doing the GetCapabilities request. But
> looking at the document generated, I see that information about styles
> are only associated to the layers I do not want to show.
>
>
>
> Anyway, the main problem I have found is that, when using a GIS client,
> layers and layers group consisting of those ones appear, which can be
> very confusing to the users. How can we hide these layers to the users?
> Is it possible?
>
>
>
> According to the mail attached, in order to change the Capabilities
> document, should I save the document somewhere and modify it? How can I
> do to show this static file?
>
>
>
> Thanks in advance,
>
>
>
> José Miguel
>
>
>
>
>
> P.D.: Some weeks ago I left a question from Justin without response
> regarding GetFeatureInfo templates. I was very busy and I could not
> reproduce the error I got. However, I suppose I will have time to spend
> on it in the future!
>
>
>
> ------------------------------------------------------------------------------
>
> */José Miguel Rubio Iglesias/*
>
> */Subdirección General de Aplicaciones Geográficas/*
>
> */Instituto Geográfico Nacional/*
>
> */C/General Ibáñez de Ibero, 3 28003 MADRID/*
>
> */Despacho: A 0002 Teléfono: 91 597 97 51/*
>
> */E-mail: jmrubio@anonymised.com <mailto:jmrubio@anonymised.com> /*
>
>
>
>
>
>
>
> -----Mensaje original-----
> De: Justin Deoliveira [mailto:jdeolive@anonymised.com]
> Enviado el: martes, 13 de enero de 2009 21:51
> Para: Barbara O'Barr
> CC: geoserver-users@lists.sourceforge.net
> Asunto: Re: [Geoserver-users] WMS configuration - multiple
> getCapabilities responses
>
>
>
> Hi Barbara,
>
>
>
> This is something we are planning to implement for 2.0 but don't
>
> currently have. Basically be able to call
>
> service=wms&request=getCapabilities&map=mymap
>
>
>
> Similar to how you can specify a specific mapfile with MapServer and
>
> only get a subset of layers.
>
>
>
> Something people have done in the past as a workaround is generate a WMS
>
> getCaps doc with all the layers, save the file somewhere web accessible
>
> and then manually delete the unwanted layers from the file. Then have
>
> the client make the wms getCaps request to static file rather than the
>
> live service.
>
>
>
> The downside of such an approach is of course it is not dynamic.
>
>
>
> -Justin
>
>
>
> Barbara O'Barr wrote:
>
>> Hello,
>
>> We have a very large number of files that we would like to serve with
>
>> WMS. Is there a way to configure Geoserver so that the data can be
>
>> organized into groups associated with several different WMS
>
>> getCapabilities responses -- to avoid overwhelming the user with a
>
>> single giant getCapabilities response?
>
>> Thank you so much,
>
>> Barbara
>
>>
>
>>
> ------------------------------------------------------------------------------
>
>> This SF.net email is sponsored by:
>
>> SourcForge Community
>
>> SourceForge wants to tell your story.
>
>> http://p.sf.net/sfu/sf-spreadtheword
>
>> _______________________________________________
>
>> 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.
>
>
>
> ------------------------------------------------------------------------------
>
> This SF.net email is sponsored by:
>
> SourcForge Community
>
> SourceForge wants to tell your story.
>
> http://p.sf.net/sfu/sf-spreadtheword
>
> _______________________________________________
>
> 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.
------------------------------------------------------------------------
This body part will be downloaded on demand.
------------------------------------------------------------------------This body part will be downloaded on demand.
--
Arne Kepp
OpenGeo - http://opengeo.org
Expert service straight from the developers
Hi Arne,
I am reading Apache documentation, but I do not understand clearly what to write when you say "/yourpath/wms$. Is that the path of the new Capabilities document in the server -and it has to be placed compulsory in GeoServer_Data_Dir/www? Or the path of my wms?
Do I have to write always "wms$" at the end? Or you just wrote it as an example?
I suppose that QUERY_STRING is a variable, but I have not defined it. Do I have to do it?
I have written the lines you sent to me in the http.conf of Apache, in the Virtual Host created to change the URL of GeoServer, but it doesn't work yet, and maybe is due to a wrong definition of the path.
Thanks,
José Miguel
-----Mensaje original-----
De: Arne Kepp [mailto:ak@anonymised.com]
Enviado el: martes, 14 de abril de 2009 10:50
Para: Rubio Iglesias José Miguel
CC: geoserver users
Asunto: Re: [Geoserver-users] WMS configuration - Capabilities document configuration
Hi Rubio,
the getcapabilities document does not normally have to come from
/geoserver/wms , you should just tell your client to use
http://youserver.org/geoserver/www/modified_document.xml instead of
http://youserver.org/geoserver/wms?service=wms&request=getcapabilities&version=1.1.0
Since you are already using Apache, you could also use mod_rewrite to
intercept the request transparently:
RewriteEngine On
RewriteCond ${QUERY_STRING} ^(.*)request=getcapabilities(.*)$ [NC]
RewriteRule ^/yourpath/wms$ modified_document.xml [L]
I think you are right that PROXY_BASE_URL will not change the context
path ( /geoserver ), feel free to file a feature request in JIRA.
-Arne
Rubio Iglesias José Miguel wrote:
Hi again,
Thanks for your help, Justin.
So you say I can place a static file in \\*GeoServer_Data_Dir\www*?
How can I do to show that document when doing a GetCapabilities
request? I am trying to do it, but I am a bit confused. I would be
pleased if you could help me on that.
On the other hand, I have been investigated and it is possible to
change */localhost:port/* in the Capabilities document using the
option *Proxy Base URL. *However, I need to change the complete path
of the WMS shown in the document (I previously changed the WMS URL
using Apache). Is it possible to do it without using a static file?
Thanks in advance.
Regards,
José Miguel
-----Mensaje original-----
De: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Enviado el: lunes, 13 de abril de 2009 15:29
Para: Rubio Iglesias José Miguel
CC: geoserver users
Asunto: Re: [Geoserver-users] WMS configuration - Capabilities
document configuration
Hi,
Well the static file can be served by any web server, like apache. You
can also place it in the geoserver www (under the root of the data
directory) which can be used to serve static files.
However, as of 1.7.3 there is an alternative for filtering the
capabilities document. You can specify only the layers which come from a
particular namespace by appending the "namespace=<ns>" parameter to the
capabilities request. However layer groups do not belong to a namespace
so they show up regardless of the namespace filter.
So a possible workaround is to place all of your layers in a particular
namespace (ns1), and then create a second empty namespace (ns2). Create
all the layer groups you need, and then if you request the wms caps doc
filtered by ns2 you should only see the layer groups.
Hope that helps.
-Justin
Rubio Iglesias José Miguel wrote:
> Hi to the GeoServer community:
>
>
>
> I have some questions regarding WMS Capabilities and WMS layers.
>
>
>
> I would like to modify the WMS Capabilities document, because I need to
> offer only the Layer-Groups when doing the GetCapabilities request. But
> looking at the document generated, I see that information about styles
> are only associated to the layers I do not want to show.
>
>
>
> Anyway, the main problem I have found is that, when using a GIS client,
> layers and layers group consisting of those ones appear, which can be
> very confusing to the users. How can we hide these layers to the users?
> Is it possible?
>
>
>
> According to the mail attached, in order to change the Capabilities
> document, should I save the document somewhere and modify it? How can I
> do to show this static file?
>
>
>
> Thanks in advance,
>
>
>
> José Miguel
>
>
>
>
>
> P.D.: Some weeks ago I left a question from Justin without response
> regarding GetFeatureInfo templates. I was very busy and I could not
> reproduce the error I got. However, I suppose I will have time to spend
> on it in the future!
>
>
>
> ------------------------------------------------------------------------------
>
> */José Miguel Rubio Iglesias/*
>
> */Subdirección General de Aplicaciones Geográficas/*
>
> */Instituto Geográfico Nacional/*
>
> */C/General Ibáñez de Ibero, 3 28003 MADRID/*
>
> */Despacho: A 0002 Teléfono: 91 597 97 51/*
>
> */E-mail: jmrubio@anonymised.com <mailto:jmrubio@anonymised.com> /*
>
>
>
>
>
>
>
> -----Mensaje original-----
> De: Justin Deoliveira [mailto:jdeolive@anonymised.com]
> Enviado el: martes, 13 de enero de 2009 21:51
> Para: Barbara O'Barr
> CC: geoserver-users@lists.sourceforge.net
> Asunto: Re: [Geoserver-users] WMS configuration - multiple
> getCapabilities responses
>
>
>
> Hi Barbara,
>
>
>
> This is something we are planning to implement for 2.0 but don't
>
> currently have. Basically be able to call
>
> service=wms&request=getCapabilities&map=mymap
>
>
>
> Similar to how you can specify a specific mapfile with MapServer and
>
> only get a subset of layers.
>
>
>
> Something people have done in the past as a workaround is generate a WMS
>
> getCaps doc with all the layers, save the file somewhere web accessible
>
> and then manually delete the unwanted layers from the file. Then have
>
> the client make the wms getCaps request to static file rather than the
>
> live service.
>
>
>
> The downside of such an approach is of course it is not dynamic.
>
>
>
> -Justin
>
>
>
> Barbara O'Barr wrote:
>
>> Hello,
>
>> We have a very large number of files that we would like to serve with
>
>> WMS. Is there a way to configure Geoserver so that the data can be
>
>> organized into groups associated with several different WMS
>
>> getCapabilities responses -- to avoid overwhelming the user with a
>
>> single giant getCapabilities response?
>
>> Thank you so much,
>
>> Barbara
>
>>
>
>>
> ------------------------------------------------------------------------------
>
>> This SF.net email is sponsored by:
>
>> SourcForge Community
>
>> SourceForge wants to tell your story.
>
>
>> _______________________________________________
>
>> 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.
>
>
>
> ------------------------------------------------------------------------------
>
> This SF.net email is sponsored by:
>
> SourcForge Community
>
> SourceForge wants to tell your story.
>
>
> _______________________________________________
>
> 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.
------------------------------------------------------------------------
This body part will be downloaded on demand.
------------------------------------------------------------------------
This body part will be downloaded on demand.
--
Arne Kepp
OpenGeo - http://opengeo.org
Expert service straight from the developers
Hi Jose,
sorry about reading your name in the wrong order. My example should be regarded as pseudocode, you will have to find the exact strings yourself. The details depend on your Apache version and settings like RewriteBase.
- /yourpath/wms can be replaced with anything you like, you can drop the /wms too.
- modified_document.xml would normally refer to a document in the DocumentRoot of the Apache host. You can also provide a URL to an external document, but then you must replace [L] with [P].
- %{QUERY_STRING} is a variable that mod_rewrite extracts from the request, you do not define it.
Note that the GeoServer UI breaks when you do these things, the browser will not able to find CSS files etc, but the OGC services do not care about path (except for the capabilities documents), so it's fine.
-Arne
Rubio Iglesias José Miguel wrote:
Hi Arne,
I am reading Apache documentation, but I do not understand clearly what to write when you say "/*yourpath/wms*$. Is that the path of the new Capabilities document in the server –and it has to be placed compulsory in *GeoServer_Data_Dir/www*? Or the path of my *wms*?
Do I have to write always “*wms*$” at the end? Or you just wrote it as an example?
I suppose that QUERY_STRING is a variable, but I have not defined it. Do I have to do it?
I have written the lines you sent to me in the *http.conf* of Apache, in the Virtual Host created to change the URL of GeoServer, but it doesn’t work yet, and maybe is due to a wrong definition of the path.
Thanks,
José Miguel
-----Mensaje original-----
De: Arne Kepp [mailto:ak@anonymised.com]
Enviado el: martes, 14 de abril de 2009 10:50
Para: Rubio Iglesias José Miguel
CC: geoserver users
Asunto: Re: [Geoserver-users] WMS configuration - Capabilities document configurationHi Rubio,
the getcapabilities document does not normally have to come from
/geoserver/wms , you should just tell your client to use
http://youserver.org/geoserver/www/modified_document.xml instead of
http://youserver.org/geoserver/wms?service=wms&request=getcapabilities&version=1.1.0
Since you are already using Apache, you could also use mod_rewrite to
intercept the request transparently:
RewriteEngine On
RewriteCond ${QUERY_STRING} ^(.*)request=getcapabilities(.*)$ [NC]
RewriteRule ^/yourpath/wms$ modified_document.xml [L]
I think you are right that PROXY_BASE_URL will not change the context
path ( /geoserver ), feel free to file a feature request in JIRA.
-Arne
Rubio Iglesias José Miguel wrote:
>
> Hi again,
>
>
>
> Thanks for your help, Justin.
>
>
>
> So you say I can place a static file in \\*GeoServer_Data_Dir\www*?
> How can I do to show that document when doing a GetCapabilities
> request? I am trying to do it, but I am a bit confused. I would be
> pleased if you could help me on that.
>
>
>
> On the other hand, I have been investigated and it is possible to
> change */localhost:port/* in the Capabilities document using the
> option *Proxy Base URL. *However, I need to change the complete path
> of the WMS shown in the document (I previously changed the WMS URL
> using Apache). Is it possible to do it without using a static file?
>
>
>
> Thanks in advance.
>
>
>
> Regards,
>
>
>
> José Miguel
>
>
>
>
>
>
>
> -----Mensaje original-----
> De: Justin Deoliveira [mailto:jdeolive@anonymised.com]
> Enviado el: lunes, 13 de abril de 2009 15:29
> Para: Rubio Iglesias José Miguel
> CC: geoserver users
> Asunto: Re: [Geoserver-users] WMS configuration - Capabilities
> document configuration
>
>
>
> Hi,
>
>
>
> Well the static file can be served by any web server, like apache. You
>
> can also place it in the geoserver www (under the root of the data
>
> directory) which can be used to serve static files.
>
>
>
> However, as of 1.7.3 there is an alternative for filtering the
>
> capabilities document. You can specify only the layers which come from a
>
> particular namespace by appending the "namespace=<ns>" parameter to the
>
> capabilities request. However layer groups do not belong to a namespace
>
> so they show up regardless of the namespace filter.
>
>
>
> So a possible workaround is to place all of your layers in a particular
>
> namespace (ns1), and then create a second empty namespace (ns2). Create
>
> all the layer groups you need, and then if you request the wms caps doc
>
> filtered by ns2 you should only see the layer groups.
>
>
>
> Hope that helps.
>
>
>
> -Justin
>
>
>
> Rubio Iglesias José Miguel wrote:
>
> > Hi to the GeoServer community:
>
> >
>
> >
>
> >
>
> > I have some questions regarding WMS Capabilities and WMS layers.
>
> >
>
> >
>
> >
>
> > I would like to modify the WMS Capabilities document, because I need to
>
> > offer only the Layer-Groups when doing the GetCapabilities request. But
>
> > looking at the document generated, I see that information about styles
>
> > are only associated to the layers I do not want to show.
>
> >
>
> >
>
> >
>
> > Anyway, the main problem I have found is that, when using a GIS client,
>
> > layers and layers group consisting of those ones appear, which can be
>
> > very confusing to the users. How can we hide these layers to the users?
>
> > Is it possible?
>
> >
>
> >
>
> >
>
> > According to the mail attached, in order to change the Capabilities
>
> > document, should I save the document somewhere and modify it? How can I
>
> > do to show this static file?
>
> >
>
> >
>
> >
>
> > Thanks in advance,
>
> >
>
> >
>
> >
>
> > José Miguel
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > P.D.: Some weeks ago I left a question from Justin without response
>
> > regarding GetFeatureInfo templates. I was very busy and I could not
>
> > reproduce the error I got. However, I suppose I will have time to spend
>
> > on it in the future!
>
> >
>
> >
>
> >
>
> > ------------------------------------------------------------------------------
>
> >
>
> > */José Miguel Rubio Iglesias/*
>
> >
>
> > */Subdirección General de Aplicaciones Geográficas/*
>
> >
>
> > */Instituto Geográfico Nacional/*
>
> >
>
> > */C/General Ibáñez de Ibero, 3 28003 MADRID/*
>
> >
>
> > */Despacho: A 0002 Teléfono: 91 597 97 51/*
>
> >
>
> > */E-mail: jmrubio@anonymised.com <mailto:jmrubio@anonymised.com> /*
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > -----Mensaje original-----
>
> > De: Justin Deoliveira [mailto:jdeolive@anonymised.com]
>
> > Enviado el: martes, 13 de enero de 2009 21:51
>
> > Para: Barbara O'Barr
>
> > CC: geoserver-users@lists.sourceforge.net
>
> > Asunto: Re: [Geoserver-users] WMS configuration - multiple
>
> > getCapabilities responses
>
> >
>
> >
>
> >
>
> > Hi Barbara,
>
> >
>
> >
>
> >
>
> > This is something we are planning to implement for 2.0 but don't
>
> >
>
> > currently have. Basically be able to call
>
> >
>
> > service=wms&request=getCapabilities&map=mymap
>
> >
>
> >
>
> >
>
> > Similar to how you can specify a specific mapfile with MapServer and
>
> >
>
> > only get a subset of layers.
>
> >
>
> >
>
> >
>
> > Something people have done in the past as a workaround is generate a WMS
>
> >
>
> > getCaps doc with all the layers, save the file somewhere web accessible
>
> >
>
> > and then manually delete the unwanted layers from the file. Then have
>
> >
>
> > the client make the wms getCaps request to static file rather than the
>
> >
>
> > live service.
>
> >
>
> >
>
> >
>
> > The downside of such an approach is of course it is not dynamic.
>
> >
>
> >
>
> >
>
> > -Justin
>
> >
>
> >
>
> >
>
> > Barbara O'Barr wrote:
>
> >
>
> >> Hello,
>
> >
>
> >> We have a very large number of files that we would like to serve with
>
> >
>
> >> WMS. Is there a way to configure Geoserver so that the data can be
>
> >
>
> >> organized into groups associated with several different WMS
>
> >
>
> >> getCapabilities responses -- to avoid overwhelming the user with a
>
> >
>
> >> single giant getCapabilities response?
>
> >
>
> >> Thank you so much,
>
> >
>
> >> Barbara
>
> >
>
> >>
>
> >
>
> >>
>
> > ------------------------------------------------------------------------------
>
> >
>
> >> This SF.net email is sponsored by:
>
> >
>
> >> SourcForge Community
>
> >
>
> >> SourceForge wants to tell your story.
>
> >
>
> >> http://p.sf.net/sfu/sf-spreadtheword
>
> >
>
> >> _______________________________________________
>
> >
>
> >> 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.
>
> >
>
> >
>
> >
>
> > ------------------------------------------------------------------------------
>
> >
>
> > This SF.net email is sponsored by:
>
> >
>
> > SourcForge Community
>
> >
>
> > SourceForge wants to tell your story.
>
> >
>
> > http://p.sf.net/sfu/sf-spreadtheword
>
> >
>
> > _______________________________________________
>
> >
>
> > 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.
>
> ------------------------------------------------------------------------
>
> This body part will be downloaded on demand.
> ------------------------------------------------------------------------
>
> This body part will be downloaded on demand.
--
Arne Kepp
OpenGeo - http://opengeo.org
Expert service straight from the developers
--
Arne Kepp
OpenGeo - http://opengeo.org
Expert service straight from the developers