<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Matt,</p>
<p>The output of gdalinfo that matters here was the one on the
subdataset you transform, so</p>
<p>gdalinfo <span style="font-size:11.0pt;color:black">
NETCDF:"./test.nc":analysed_sst</span></p>
<p><span style="font-size:11.0pt;color:black">I've a very poor
Internet connection for the next 10 days so can't download the
full .nc file yet, but from the .ncdump file you provided, I
believe I managed to reproduce your issue</span></p>
<p><span style="font-size:11.0pt;color:black">I've queued a fix in
<a class="moz-txt-link-freetext" href="https://github.com/OSGeo/gdal/pull/6129">https://github.com/OSGeo/gdal/pull/6129</a><br>
</span></p>
<p><span style="font-size:11.0pt;color:black">There's no much
workaround I can think of, apart removing the 'coordinates'
attribute on the sst_anomaly variable.<br>
</span></p>
<p><span style="font-size:11.0pt;color:black">Even<br>
</span></p>
<div class="moz-cite-prefix">Le 27/07/2022 à 21:19, Matthew Savoie a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CY1PR03MB2171361248F74155BEB41D00E8979@CY1PR03MB2171.namprd03.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas",serif;}span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}div.WordSection1
{page:WordSection1;}</style>
<div class="WordSection1">
<p class="MsoNormal">Hi Even, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">>
I have run this command with gdal 3.4.3 and gdal 3.5.1
and get different output files.<br>
<br>
Can you compare the output of the two versions of
gdalinfo ?<br>
This should determine whether the difference is when
reading or writing.<o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Good
idea, I did that and there is no difference in the
output of gdalinfo between 3.4.3 and 3.5.1 on the
test.nc file.<o:p></o:p></p>
</div>
</div>
</blockquote>
<p>Are you 100% sure about that ? It is highly unlikely that the
difference would be on the side of the output driver
(GeoTIFF), and much more likely on the reading side (netCDF).
There have been adjustments recently in the netCDF driver to
be a bit more restrictive regarding exposing geotransforms
(the driver could expose non relevant geotransforms), that
have had side effects on some files where they could be
legitimate.<o:p></o:p></p>
<p>You can likely workaround the issue by definining the
configuration option / environment variable
GDAL_NETCDF_IGNORE_XY_AXIS_NAME_CHECKS to YES (cf
<a
href="https://gdal.org/drivers/raster/netcdf.html#georeference"
moz-do-not-send="true" class="moz-txt-link-freetext">https://gdal.org/drivers/raster/netcdf.html#georeference</a>).
<o:p></o:p></p>
<pre><o:p> </o:p></pre>
<pre><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Yes, I rechecked the output of gdalinfo on the file. Here is a link to my shared drive.<o:p></o:p></span></pre>
<p class="MsoNormal"><a
href="https://o365coloradoedu-my.sharepoint.com/:f:/g/personal/savoie_colorado_edu/EjihTcOSuZdJiZiiJmXkEiABHpbXHPFab6MbnjSfyfDLfw?e=qhQYmF"
moz-do-not-send="true">gdal-test</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The files are the test.nc file (which is in
fact a copy of a dataset file
20210429090000-JPL-L4_GHRSST-SSTfnd-MUR-GLOB-v02.0-fv04.1.nc)<o:p></o:p></p>
<p class="MsoNormal">test.nc.dump which is the output of ncdump
-h on the file<o:p></o:p></p>
<p class="MsoNormal">gdal.3.4.3.out and gdal3.5.1.out which are
the result of two commands gdalinfo –version and gdalinfo
test.nc. You can see the only difference is the version.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I will look at the config option to see how
to get around this. Thanks.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Matt<o:p></o:p></p>
<pre><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></pre>
</div>
</blockquote>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.spatialys.com">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
</body>
</html>