Re: [Geoserver-devel] Request to backport to 2.16..x [GEOS-9380] Option for cascaded WMS Layer to respect Bounding Box of remote WMS Layer

2020-01-15 Thread Jody Garnett
The additional parameter option you added will be visible in both the user
interface and the rest api.

The rest api is here:
-
https://github.com/geoserver/geoserver/blob/master/doc/en/api/1.0.0/wmtsstores.yaml
-
https://github.com/geoserver/geoserver/blob/master/doc/en/api/1.0.0/wmslayers.yaml

There are some examples to update, and the definition of WMSStoreLayerInfo

(to document new parameter).
--
Jody Garnett


On Wed, 15 Jan 2020 at 00:12, Imran Rajjad  wrote:

> Hi Jody,
>
> I will add more detail to the documentation for the said feature.
>
> As for the REST API, I am not the author of that part of documentation,
> hence I am not really aware of the context.
>
> On Tue, Jan 14, 2020 at 11:27 PM Jody Garnett 
> wrote:
>
>> -1 this option is not yet documented.
>>
>> The provided text for the rest api:
>>
>> * **Optimization**. It is possible to ignore remote WMS calls if
>> requested map area is completely outside the native bounds as advertised by
>> remote WMS layer. These settings are available under **Publishing** Tab.
>>
>> The documentation for the publishing tab should be updated, for the REST
>> API we are using Open API connection parameter map / example.
>>
>> Please address before 2.17-RC
>> --
>> Jody Garnett
>>
>>
>> On Mon, 13 Jan 2020 at 05:46, Imran Rajjad  wrote:
>>
>>>
>>>
>>> *Dear List,I would like to ask backport permission for an improvement
>>> that optimized external GetMap requests for Cascaded WMS. This optimization
>>> when enabled, does not issue remote GetMap requests if requested area is
>>> completely outside of the advertised bounds on remote WMS Layer. More
>>> details at https://osgeo-org.atlassian.net/browse/GEOS-9380
>>> regards,Imran*
>>> --
>>> I.R
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>
>
> --
> I.R
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel


Re: [Geoserver-devel] Request to backport to 2.16..x [GEOS-9380] Option for cascaded WMS Layer to respect Bounding Box of remote WMS Layer

2020-01-15 Thread Imran Rajjad
Hi Jody,

I will add more detail to the documentation for the said feature.

As for the REST API, I am not the author of that part of documentation,
hence I am not really aware of the context.

On Tue, Jan 14, 2020 at 11:27 PM Jody Garnett 
wrote:

> -1 this option is not yet documented.
>
> The provided text for the rest api:
>
> * **Optimization**. It is possible to ignore remote WMS calls if requested
> map area is completely outside the native bounds as advertised by remote
> WMS layer. These settings are available under **Publishing** Tab.
>
> The documentation for the publishing tab should be updated, for the REST
> API we are using Open API connection parameter map / example.
>
> Please address before 2.17-RC
> --
> Jody Garnett
>
>
> On Mon, 13 Jan 2020 at 05:46, Imran Rajjad  wrote:
>
>>
>>
>> *Dear List,I would like to ask backport permission for an improvement
>> that optimized external GetMap requests for Cascaded WMS. This optimization
>> when enabled, does not issue remote GetMap requests if requested area is
>> completely outside of the advertised bounds on remote WMS Layer. More
>> details at https://osgeo-org.atlassian.net/browse/GEOS-9380
>> regards,Imran*
>> --
>> I.R
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>

-- 
I.R
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel


Re: [Geoserver-devel] Request to backport to 2.16..x [GEOS-9380] Option for cascaded WMS Layer to respect Bounding Box of remote WMS Layer

2020-01-14 Thread Jody Garnett
-1 this option is not yet documented.

The provided text for the rest api:

* **Optimization**. It is possible to ignore remote WMS calls if requested
map area is completely outside the native bounds as advertised by remote
WMS layer. These settings are available under **Publishing** Tab.

The documentation for the publishing tab should be updated, for the REST
API we are using Open API connection parameter map / example.

Please address before 2.17-RC
--
Jody Garnett


On Mon, 13 Jan 2020 at 05:46, Imran Rajjad  wrote:

>
>
> *Dear List,I would like to ask backport permission for an improvement that
> optimized external GetMap requests for Cascaded WMS. This optimization when
> enabled, does not issue remote GetMap requests if requested area is
> completely outside of the advertised bounds on remote WMS Layer. More
> details at https://osgeo-org.atlassian.net/browse/GEOS-9380
> regards,Imran*
> --
> I.R
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel