Got it,
https://github.com/OSGeo/gdal/commit/5eb8fa57c7730ae09b6ef0c7840c26283d84db0e
Thanks!!!
Idan
On Sat, 6 Jun 2020, 00:26 Even Rouault, wrote:
> > Should I open a bug report or am I missing something here?
>
>
>
> Was indeed a bug. Just fixed
>
>
>
> Even
>
>
>
> --
>
> Spatialys - Geospa
Even,
Thank you for your work and diligence. Perhaps what I meant by the warp
"working" was that in 3.1.0 it is no longer throwing an error about being
able to compute the bounds.
I can confirm that NWS's NBM v3.2 grib2 files are now translating to TIF
successfully when I try using the latest doc
> Should I open a bug report or am I missing something here?
Was indeed a bug. Just fixed
Even
--
Spatialys - Geospatial professional services
http://www.spatialys.com
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/
Thomas,
> A follow up with some more information. According to Zachary Flamig, there
> are no issues in GDAL 2.2.0. I encountered these issues in 3.0.4.
I've just pushed a fix for that regression. was an added security check that
was incorrectly
triggered when reading band 23.
> In 3.1.0,
> th
t; LENGTHUNIT["Metre",1]],
> AXIS["northing",north,
> ORDER[2],
> LENGTHUNIT["Metre",1]]]
> Data axis to CRS axis mapping: 1,2
> Origin = (-3272421.457337170839310,3790842.106035435572267)
> Pixel Size = (2539.702999
38d23'39.07"W, 53d 3'24.76"N)
Lower Left (-3272421.457, -265063.585) (126d17' 8.03"W, 19d12'55.22"N)
Upper Right ( 2683182.078, 3790842.106) ( 59d 1'17.54"W, 54d22'46.84"N)
Lower Right ( 2683182.078, -265063.585) ( 69d11'54.98"W, 2
Hi Thomas,
Looks like that is my best bet. Python docs are on there, so Wayback Machine
saves the day again!
Thanks,
Jon
From: Thomas Juntunen
Sent: 04 June 2020 15:12
To: Jon Morris
Cc: gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] Documentation for previous versions
Hi Jon,
Maybe the W
