Thanks, Even. 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.
It's great that this isn't a random server load thing or something! 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. Thanks again, carl On Thu, Oct 21, 2021 at 1:49 PM Even Rouault <[email protected]> wrote: > > Le 21/10/2021 à 22:32, Rahkonen Jukka (MML) a écrit : > > Hi Even, > > > > 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. > > > > The nationalmap.gov 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 > > SUBSET=x(-20037507.0672000013,-13590403.131594259)&SUBSET=y(5303978.1067894027,5304490.1067842878) > > 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: > > > SUBSET=x%(-13591427.131584032,-13590403.131594259)&SUBSET=y(5303978.1067894027,5304490.1067842878) > > 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: > > > https://github.com/OSGeo/gdal/commit/8af67b64371c275a3770e75da1bd0d4bb7329295 > > (I get the same error as you with the 3.2 branch, so I strongly suspect > the above is indeed the fix for that) > > Even > > -- http://www.spatialys.com > My software is free, but my time generally not. > >
_______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
