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
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”:
bicubic
The WMS setting is in the layer.xml and is one of “Nearest”, “Bilinear” and “Bicubic”:
Bicubic
Steve Ikeoka
···
From: Tyler Youschak tyleryouschak@anonymised.com
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
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” Steve.Ikeoka@anonymised.com 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”:
bicubic
The WMS setting is in the layer.xml and is one of “Nearest”, “Bilinear” and “Bicubic”:
Bicubic
Steve Ikeoka
From: Tyler Youschak <tyleryouschak@anonymised.com>
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
We welcome documentation fixes - https://docs.geoserver.org/latest/en/docguide/quickfix.html
Ian
···
On Thu, May 9th, 2019 at 10:52 AM, “Ikeoka, Steve” <Steve.Ikeoka@anonymised.com> 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”:
bicubic
The WMS setting is in the layer.xml and is one of “Nearest”, “Bilinear” and “Bicubic”:
Bicubic
Steve Ikeoka
From: Tyler Youschak <tyleryouschak@anonymised.com>
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
Ian Turton
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 ijturton@anonymised.com wrote:
We welcome documentation fixes - https://docs.geoserver.org/latest/en/docguide/quickfix.html
Ian
On Thu, 9 May 2019 at 16:11, Tyler Youschak <tyleryouschak@anonymised.com> 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” <Steve.Ikeoka@anonymised.com> 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”:
bicubic
The WMS setting is in the layer.xml and is one of “Nearest”, “Bilinear” and “Bicubic”:
Bicubic
Steve Ikeoka
From: Tyler Youschak <tyleryouschak@anonymised.com>
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:
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
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
–
Ian Turton