<div dir="ltr">Hi,<div><br></div><div>I just built GDAL 3.3.3 RC1 here on Windows with VS2019 and PROJ 8.1.1 and it built easily. </div><div><br></div><div>I retried the gdallocationinfo queries that I was having trouble with beforehand (with 3.3.1) and both the USGS National Map and my local WCS server queries now return the expected values. I know others had tested the fix Even mentioned but I wanted to try it myself.</div><div><br></div><div>Thanks again for the explanation and the fix,</div><div>carl</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 21, 2021 at 2:00 PM Carl Godkin <<a href="mailto:cgodkin@gmail.com">cgodkin@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Thanks, Even.<br><div><br></div><div>That makes sense. (Finally!) I can wait a little bit to come back to this so I'll either build 3.3 HEAD on my own or await the next release.</div><div><br></div><div>It's great that this isn't a random server load thing or something!</div><div><br></div><div>The weird result on my own WCS server also seemed to be caused by a bad "xmin" value which is how I started down this road.</div><div><br></div><div>Thanks again,</div><div><br></div><div>carl</div><div><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 21, 2021 at 1:49 PM Even Rouault <<a href="mailto:even.rouault@spatialys.com" target="_blank">even.rouault@spatialys.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p><br>
</p>
<div>Le 21/10/2021 à 22:32, Rahkonen Jukka
(MML) a écrit :<br>
</div>
<blockquote type="cite">
<div>
<p class="MsoNormal"><span>Hi
Even,<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">You are right, re-running the request -oo
clear_cache gives me the same error about 3 bands. Obviously
our server was configured right when I used it with GDAL
last time. Now gdallocationinfo does not work even for me
because I wiped the working configuration from my cache. We
will fix the service metadata when we go from beta to
official soon.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">The <a href="http://nationalmap.gov" target="_blank">nationalmap.gov</a> service does not still work
for me. I cleared the cache but I still get a 404 error from
the server. Subsets in the reques are these<br>
SUBSET=x(-20037507.0672000013,-13590403.131594259)&SUBSET=y(5303978.1067894027,5304490.1067842878)</span></p>
</div>
</blockquote>
<p>The xmin value in the request you get is obviously wrong. The
subset I get with GDAL master and head of 3.3 branch is:<br>
</p>
<p>SUBSET=x%(-13591427.131584032,-13590403.131594259)&SUBSET=y(5303978.1067894027,5304490.1067842878)</p>
<p>I suspect you might use a GDAL release version, that hasn't yet
received the following recent fix that is likely related to that
issue and will be in 3.3.3 and 3.4.0:<br>
</p>
<p><a href="https://github.com/OSGeo/gdal/commit/8af67b64371c275a3770e75da1bd0d4bb7329295" target="_blank">https://github.com/OSGeo/gdal/commit/8af67b64371c275a3770e75da1bd0d4bb7329295</a><br>
</p>
<p>(I get the same error as you with the 3.2 branch, so I strongly
suspect the above is indeed the fix for that)<br>
</p>
<p>Even</p>
<br>
<pre cols="72">--
<a href="http://www.spatialys.com" target="_blank">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
</div>
</blockquote></div>
</blockquote></div>