Issue with rest API and per layer interpolation

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue with rest API and per layer interpolation

craytor
Hello all,

Currently through the rest api I make a post request to coverage stores to add my store. I thin make a post request to /workspaces/{name}/coverages that contain information. Additionally, I have these lines in there specifically:
"interpolationMethods" => [
"string" => [
"bilinear"
]
],
"defaultInterpolationMethod" => "bilinear",

I then make a put request to /layers/{name}:{layer_name} and my layer is enabled. The issue is that the layer is being interpolated by the "default WMS settings" even though I specifically said for it to use bilinear interpolation.
Is it possible to edit that "Default Interpolation Method" via the API so I can get it to be bilinear? 

For some reason Services > WMS > Raster Rendering Options > Default Interpolation of Nearest neighbor is overriding what I am selecting and it's making no sense.

I appreciate any help.

Thanks,
Tyler Youschak


_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:
- Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Reply | Threaded
Open this post in threaded view
|

Re: Issue with rest API and per layer interpolation

sikeoka

I haven't tested it through the REST API but there are separate default interpolation method settings for WCS and WMS.


The WCS setting is in the coverage.xml and is one of "nearest neighbor", "bilinear" and "bicubic":
<defaultInterpolationMethod>bicubic</defaultInterpolationMethod>

The WMS setting is in the layer.xml and is one of "Nearest", "Bilinear" and "Bicubic":
<defaultWMSInterpolationMethod>Bicubic</defaultWMSInterpolationMethod>

Steve Ikeoka



From: Tyler Youschak <[hidden email]>
Sent: Wednesday, May 8, 2019 10:03 PM
To: GeoServer Mailing List List
Subject: [Geoserver-users] Issue with rest API and per layer interpolation
 
Hello all,

Currently through the rest api I make a post request to coverage stores to add my store. I thin make a post request to /workspaces/{name}/coverages that contain information. Additionally, I have these lines in there specifically:
"interpolationMethods" => [
"string" => [
"bilinear"
]
],
"defaultInterpolationMethod" => "bilinear",

I then make a put request to /layers/{name}:{layer_name} and my layer is enabled. The issue is that the layer is being interpolated by the "default WMS settings" even though I specifically said for it to use bilinear interpolation.
Is it possible to edit that "Default Interpolation Method" via the API so I can get it to be bilinear? 

For some reason Services > WMS > Raster Rendering Options > Default Interpolation of Nearest neighbor is overriding what I am selecting and it's making no sense.

I appreciate any help.

Thanks,
Tyler Youschak


_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:
- Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Reply | Threaded
Open this post in threaded view
|

Re: Issue with rest API and per layer interpolation

craytor
Thank you a lot! That is exactly what I was looking for.

I feel like that should maybe be better documented, as I didn't find it anywhere in all of my searching.

Thanks again,
Tyler

Tyler Youschak

On Thu, May 9th, 2019 at 10:52 AM, "Ikeoka, Steve" <[hidden email]> wrote:

I haven't tested it through the REST API but there are separate default interpolation method settings for WCS and WMS.


The WCS setting is in the coverage.xml and is one of "nearest neighbor", "bilinear" and "bicubic":
<defaultInterpolationMethod>bicubic</defaultInterpolationMethod>

The WMS setting is in the layer.xml and is one of "Nearest", "Bilinear" and "Bicubic":
<defaultWMSInterpolationMethod>Bicubic</defaultWMSInterpolationMethod>

Steve Ikeoka



From: Tyler Youschak <[hidden email]>
Sent: Wednesday, May 8, 2019 10:03 PM
To: GeoServer Mailing List List
Subject: [Geoserver-users] Issue with rest API and per layer interpolation
 
Hello all,

Currently through the rest api I make a post request to coverage stores to add my store. I thin make a post request to /workspaces/{name}/coverages that contain information. Additionally, I have these lines in there specifically:
"interpolationMethods" => [
"string" => [
"bilinear"
]
],
"defaultInterpolationMethod" => "bilinear",

I then make a put request to /layers/{name}:{layer_name} and my layer is enabled. The issue is that the layer is being interpolated by the "default WMS settings" even though I specifically said for it to use bilinear interpolation.
Is it possible to edit that "Default Interpolation Method" via the API so I can get it to be bilinear? 

For some reason Services > WMS > Raster Rendering Options > Default Interpolation of Nearest neighbor is overriding what I am selecting and it's making no sense.

I appreciate any help.

Thanks,
Tyler Youschak



_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:
- Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Reply | Threaded
Open this post in threaded view
|

Re: Issue with rest API and per layer interpolation

Ian Turton

On Thu, 9 May 2019 at 16:11, Tyler Youschak <[hidden email]> wrote:
Thank you a lot! That is exactly what I was looking for.

I feel like that should maybe be better documented, as I didn't find it anywhere in all of my searching.

Thanks again,
Tyler

Tyler Youschak

On Thu, May 9th, 2019 at 10:52 AM, "Ikeoka, Steve" <[hidden email]> wrote:

I haven't tested it through the REST API but there are separate default interpolation method settings for WCS and WMS.


The WCS setting is in the coverage.xml and is one of "nearest neighbor", "bilinear" and "bicubic":
<defaultInterpolationMethod>bicubic</defaultInterpolationMethod>

The WMS setting is in the layer.xml and is one of "Nearest", "Bilinear" and "Bicubic":
<defaultWMSInterpolationMethod>Bicubic</defaultWMSInterpolationMethod>

Steve Ikeoka



From: Tyler Youschak <[hidden email]>
Sent: Wednesday, May 8, 2019 10:03 PM
To: GeoServer Mailing List List
Subject: [Geoserver-users] Issue with rest API and per layer interpolation
 
Hello all,

Currently through the rest api I make a post request to coverage stores to add my store. I thin make a post request to /workspaces/{name}/coverages that contain information. Additionally, I have these lines in there specifically:
"interpolationMethods" => [
"string" => [
"bilinear"
]
],
"defaultInterpolationMethod" => "bilinear",

I then make a put request to /layers/{name}:{layer_name} and my layer is enabled. The issue is that the layer is being interpolated by the "default WMS settings" even though I specifically said for it to use bilinear interpolation.
Is it possible to edit that "Default Interpolation Method" via the API so I can get it to be bilinear? 

For some reason Services > WMS > Raster Rendering Options > Default Interpolation of Nearest neighbor is overriding what I am selecting and it's making no sense.

I appreciate any help.

Thanks,
Tyler Youschak

_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:
- Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users


--
Ian Turton


_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:
- Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Reply | Threaded
Open this post in threaded view
|

Re: Issue with rest API and per layer interpolation

craytor
Ok sounds good. When I get some free time I'll contribute!

Tyler Youschak

On Thu, May 9th, 2019 at 11:37 AM, Ian Turton <[hidden email]> wrote:
On Thu, 9 May 2019 at 16:11, Tyler Youschak <[hidden email]> wrote:
Thank you a lot! That is exactly what I was looking for.

I feel like that should maybe be better documented, as I didn't find it anywhere in all of my searching.

Thanks again,
Tyler

Tyler Youschak

On Thu, May 9th, 2019 at 10:52 AM, "Ikeoka, Steve" <[hidden email]> wrote:

I haven't tested it through the REST API but there are separate default interpolation method settings for WCS and WMS.


The WCS setting is in the coverage.xml and is one of "nearest neighbor", "bilinear" and "bicubic":
<defaultInterpolationMethod>bicubic</defaultInterpolationMethod>

The WMS setting is in the layer.xml and is one of "Nearest", "Bilinear" and "Bicubic":
<defaultWMSInterpolationMethod>Bicubic</defaultWMSInterpolationMethod>

Steve Ikeoka



From: Tyler Youschak <[hidden email]>
Sent: Wednesday, May 8, 2019 10:03 PM
To: GeoServer Mailing List List
Subject: [Geoserver-users] Issue with rest API and per layer interpolation
 
Hello all,

Currently through the rest api I make a post request to coverage stores to add my store. I thin make a post request to /workspaces/{name}/coverages that contain information. Additionally, I have these lines in there specifically:
"interpolationMethods" => [
"string" => [
"bilinear"
]
],
"defaultInterpolationMethod" => "bilinear",

I then make a put request to /layers/{name}:{layer_name} and my layer is enabled. The issue is that the layer is being interpolated by the "default WMS settings" even though I specifically said for it to use bilinear interpolation.
Is it possible to edit that "Default Interpolation Method" via the API so I can get it to be bilinear? 

For some reason Services > WMS > Raster Rendering Options > Default Interpolation of Nearest neighbor is overriding what I am selecting and it's making no sense.

I appreciate any help.

Thanks,
Tyler Youschak

_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:
- Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users


--
Ian Turton



_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:
- Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-users