I’ve gone back through this and read it again to try to familiarize myself with
the situation.
Is there a reason why GeoServer currently does it in the order it does it? For
instance, if I were to make the alternative — would it open up additional
issues that were prevented it from doing it
On Mon, Aug 27, 2018 at 6:47 PM Tyler Youschak
wrote:
> For the layer thats been acting up, I went ahead and turned off bilinear
> interpolation, and switched it back to nearest neighbor. This did fix my
> issue, but lost all of the nice smoothing, which is not ideal.
>
> Is there a way to “fix”
I haven't heard anything since... anyone able to take a look? Thanks!
Tyler Youschak
On Mon, Aug 27th, 2018 at 11:41 AM, Tyler Youschak
wrote:
>
>
> I’ve been doing some more digging during my free time.
>
>
> For the layer thats been acting up, I went ahead and turned off bilinear
>
I’ve been doing some more digging during my free time.
For the layer thats been acting up, I went ahead and turned off bilinear
interpolation, and switched it back to nearest neighbor. This did fix my issue,
but lost all of the nice smoothing, which is not ideal.
Is there a way to “fix” this
Hello,
(Forgot to reply all...)
Thanks for the quick reply!
I went ahead and fixed that and also made a few changes to the color table
in addition to that and I am getting the same outcome.
Updated example (of what I'm trying to fix):
Perhaps the
line is confusing it. I’d try making the quantity increase at each interval.
Brad
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
