<div dir="ltr"><div><div><div>A few comments:<br><br></div><div>[1]<br>The example file is netCDF-3 ("classic" netCDF)<br></div><div><br></div>%> <b>ncdump -k</b> <a href="http://goes11.2010.003.200014.BAND_01.nc">goes11.2010.003.200014.BAND_01.nc</a> <br>classic <=== response<br>===<br><br></div>[2] Golden rule of data processing: Look at ypur data file(s)<br><br></div>The example file overview can be seen via:<br><div><div><br>%> <b>ncdump -h</b> <a href="http://goes11.2010.003.200014.BAND_01.nc">goes11.2010.003.200014.BAND_01.nc</a><br></div><div>or<br></div><div>%> <b>ncl_filedump</b> <a href="http://goes11.2010.003.200014.BAND_01.nc">goes11.2010.003.200014.BAND_01.nc</a></div><div><br></div><div>The output is attached. An extract is:<br><br>netcdf goes11.2010.003.200014.BAND_01 {<br>dimensions:<br> lines = 871 ;<br> elems = 1912 ;<br> bands = 1 ;o<br></div><div>[wnip]<br></div><div><br> float <b>data</b>(bands, lines, elems) ;<br> data :long_name = "data" ;<br> data :type = "GVAR" ;<br> data :units = "unitless" ;<br> float latitude(lines, elems) ;<br> latitude:long_name = "latitude" ;<br> latitude:units = "degrees" ;<br> float longitude(lines, elems) ;<br> longitude:long_name = "longitude" ;<br> longitude:units = "degrees" ;<br><br>===<br></div><div>Hence, NCL is reading the variables 'data, latitude and longitude' <b>which are in the file</b>.<br><br><pre> diri = "./"
fili = "<a href="http://goes11.2010.003.200014.BAND_01.nc">goes11.2010.003.200014.BAND_01.nc</a>"
f = addfile(diri+fili,"r")
d = f-><b>data</b> ; data(bands, lines, elems)
; data@type = "GVAR"
d@lat2d = f-><b>latitude </b> ; (lines, elems)
d@lon2d = f-><b>longitude</b> <br><br>===<br></pre><pre>[3] The GOES16 file is netCDF-4 <br><br>%> ncdump -k <a href="http://goes16.nc">goes16.nc</a><br>netCDF-4 <=== response<br> <br></pre></div><div>%> ncdump -h <a href="http://goes15.nc">goes15.nc</a> [ ncdump -h <a href="http://goes16.nc">goes16.nc</a> > ncdump_h.goes16 ]<br><br></div><div>As you can see from the file dumps, they are VERY different both in contents and structure. Some of the variables are 'packed' (type short with scale_factor and add_offset attributes.<br><br>dimensions:<br> y = 500 ;<br> x = 500 ;<br> number_of_time_bounds = 2 ;<br> band = 1 ;<br> number_of_image_bounds = 2 ;<br> num_star_looks = 24 ;<br>variables:<br> <b>short</b> Rad(y, x) ;<br> Rad:_FillValue = 1023s ;<br> Rad:long_name = "ABI L1b Radiances" ;<br> Rad:standard_name = "toa_outgoing_radiance_per_unit_wavenumber" ;<br> Rad:_Unsigned = "true" ;<br> Rad:sensor_band_bit_depth = 10b ;<br> Rad:valid_range = 0s, 1022s ;<br> Rad:<b>scale_factor = 0.1760585f ;</b><br> Rad:<b>add_offset = -5.2392f </b>;<br> Rad:units = "mW m-2 sr-1 (cm-1)-1" ;<br> Rad:resolution = "y: 0.000056 rad x: 0.000056 rad" ;<br> Rad:coordinates = "band_id band_wavelength t y x" ;<br> Rad:grid_mapping = "goes_imager_projection" ;<br> Rad:cell_methods = "t: point area: point" ;<br> Rad:ancillary_variables = "DQF" ;<br></div><div>[SNIP]<br></div><div><br></div><div>If you want the variable 'Rad', it must be unpacked prior to usage:<br><br></div><div> data = short2flt( f->Rad ) ; read/import and unpack ... on the 'fly'<br></div><div> printVarSummary(data)<br></div><div> printMinMax(data,0)<br><br></div><div>Further, there are no explicit, lat/lon variables. Rather, georeferences are provided.<br><br>geospatial_lat_lon_extent<br> geospatial_lat_lon_extent:geospatial_westbound_longitude = -81.80251f ;<br> geospatial_lat_lon_extent:geospatial_northbound_latitude = 46.0514f ;<br> geospatial_lat_lon_extent:geospatial_eastbound_longitude = -65.13806f ;<br> geospatial_lat_lon_extent:geospatial_southbound_latitude = 32.08946f ;<br> geospatial_lat_lon_extent:geospatial_lat_center = 38.44252f ;<br> geospatial_lat_lon_extent:geospatial_lon_center = -74.89199f ;<br> geospatial_lat_lon_extent:geospatial_lat_nadir = 0.f ;<br> geospatial_lat_lon_extent:geospatial_lon_nadir = -89.5f ;<br> geospatial_lat_lon_extent:geospatial_lat_units = "degrees_north" ;<br> geospatial_lat_lon_extent:geospatial_lon_units = "degrees_east" ;<br> geospatial_lat_lon_extent:long_name = "geospatial latitude and longitude references" ;<br><br>====<br></div><div><b>Someone else will have to do the graphics stuff. </b><br><br></div><div>Good Luck<br></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 13, 2017 at 12:02 PM, Tim Risner <span dir="ltr"><<a href="mailto:trisner@awis.com" target="_blank">trisner@awis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">thanks Rick, others. <div>version is 6.4.0</div><div>running on Linux Amazon EC2 instance. x86_64 x86_64 x86_64 GNU/Linux</div><div>testing GOES16 file attached. <br></div><div>I obtained such file from the Amazon AWS bucket system that is now publicly accessible by the gov't/Amazon.</div><div>Information on file lists it as a GOES16 netcdf file. </div><div><br></div><div>I assumed I could simply replace the file in the example for GOES 11 example here: <a href="http://www.ncl.ucar.edu/Applications/Scripts/goes_1.ncl" target="_blank">http://www.ncl.ucar.edu/<wbr>Applications/Scripts/goes_1.<wbr>ncl</a></div><div>and all would work if the files and datasets were exchangeable. </div><div>Assumptions are likely my problem. </div><div><br></div><div>Error output: </div><div><br></div><div><div>fatal:["Execute.c":132]:<wbr>variable (data) is not in file (/var/NCL/INPUT/GOES16.nc)</div><div>fatal:["Execute.c":6381]:<wbr>variable (data) is not in file (f)</div><div>fatal:["Execute.c":8640]:<wbr>Execute: Error occurred at or near line 4 in file /var/NCL/CODE/<a href="http://testgoes.nc" target="_blank">testgoes.nc</a></div></div><div><br></div><div><br></div></div><div class="gmail_extra"><span class=""><br clear="all"><div><div class="m_-1552245507070405686gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div><font size="4"><b><span style="font-family:georgia,serif"><span></span><span></span><br>Tim Risner</span></b></font><br></div><i>Operational Meteorologist</i><br> </div><span><i><a href="tel:(888)%20798-9955" value="+18887989955" target="_blank">(888) 798-9955 ext 1006</a></i><br><br></span><div><a href="http://www.awis.com" target="_blank"><img alt="" src="https://pbs.twimg.com/profile_images/524275730171969536/n2Ev5bg8.jpeg" width="47" height="47"></a><a href="https://www.facebook.com/AWISWeatherServices/" target="_blank"><img alt="https://www.facebook.com/AWISWeatherServices/" src="https://upload.wikimedia.org/wikipedia/commons/thumb/1/1b/Facebook_icon.svg/2000px-Facebook_icon.svg.png" width="47" height="47"></a><a href="https://twitter.com/awisweather" target="_blank"><span><img src="https://lh3.ggpht.com/lSLM0xhCA1RZOwaQcjhlwmsvaIQYaP3c5qbDKCgLALhydrgExnaSKZdGa8S3YtRuVA=w300" width="48" height="48"></span></a><br></div></div></div></div></div></div></div></div></div></div></div></div>
<br></span><div><div class="h5"><div class="gmail_quote">On Wed, Dec 13, 2017 at 9:02 AM, Rick Brownrigg <span dir="ltr"><<a href="mailto:brownrig@ucar.edu" target="_blank">brownrig@ucar.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hi Tim,<br><br></div>Do you have a dataset you could share? I download some data from this site:<br><br><a href="https://www.goes-r.gov" target="_blank">https://www.goes-r.gov</a><br><br></div>but not knowing what I'm really looking for, I could not ascertain that it was specifically GOES16. NCL was able to read it.<br><br></div><div>I should also ask what version of NCL are you working with?<br></div><div><br></div>If your dataset is too large to email, you can post it to our FTP site:<br><br><a href="http://ncl.ucar.edu/ftp_files.shtml" target="_blank">http://ncl.ucar.edu/ftp_files.<wbr>shtml</a><span class="m_-1552245507070405686HOEnZb"><font color="#888888"><br><br></font></span></div><span class="m_-1552245507070405686HOEnZb"><font color="#888888">Rick<br></font></span></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_-1552245507070405686h5">On Wed, Dec 13, 2017 at 7:35 AM, Tim Risner <span dir="ltr"><<a href="mailto:trisner@awis.com" target="_blank">trisner@awis.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_-1552245507070405686h5"><div dir="ltr"><span style="font-size:12.8px">Hello All, </span><div style="font-size:12.8px">I am curious as to what the GOES16 netCDF plan is for NCL. </div><div style="font-size:12.8px">I've attempted to ingest the new GOES16 netCDF into generic GOES code found on the examples pages, but am getting a variables not found error when attempting to produce an image. Variable not found is "data". I assume this is due to the differences between the GOES16 netCDF files and the older GOES products? or is it just operator error and GOES16 netcdf files should work? <br><br>Thanks!!!</div><div><br></div><div><div class="m_-1552245507070405686m_6293265420076554199m_-5623333301813600442gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div><font size="4"><b><span style="font-family:georgia,serif"><span></span><span></span><br>Tim Risner</span></b></font><br></div><i>Operational Meteorologist</i><br> </div><span><i><a href="tel:(888)%20798-9955" value="+18887989955" target="_blank">(888) 798-9955 ext 1006</a></i><br><br></span><div><a href="http://www.awis.com" target="_blank"><img alt="" src="https://pbs.twimg.com/profile_images/524275730171969536/n2Ev5bg8.jpeg" width="47" height="47"></a><a href="https://www.facebook.com/AWISWeatherServices/" target="_blank"><img alt="https://www.facebook.com/AWISWeatherServices/" src="https://upload.wikimedia.org/wikipedia/commons/thumb/1/1b/Facebook_icon.svg/2000px-Facebook_icon.svg.png" width="47" height="47"></a><a href="https://twitter.com/awisweather" target="_blank"><span><img src="https://lh3.ggpht.com/lSLM0xhCA1RZOwaQcjhlwmsvaIQYaP3c5qbDKCgLALhydrgExnaSKZdGa8S3YtRuVA=w300" width="48" height="48"></span></a><br></div></div></div></div></div></div></div></div></div></div></div></div>
</div>
<br></div></div><span>______________________________<wbr>_________________<br>
ncl-talk mailing list<br>
<a href="mailto:ncl-talk@ucar.edu" target="_blank">ncl-talk@ucar.edu</a><br>
List instructions, subscriber options, unsubscribe:<br>
<a href="http://mailman.ucar.edu/mailman/listinfo/ncl-talk" rel="noreferrer" target="_blank">http://mailman.ucar.edu/mailma<wbr>n/listinfo/ncl-talk</a><br>
<br></span></blockquote></div><br></div>
</blockquote></div><br></div></div></div>
<br>______________________________<wbr>_________________<br>
ncl-talk mailing list<br>
<a href="mailto:ncl-talk@ucar.edu">ncl-talk@ucar.edu</a><br>
List instructions, subscriber options, unsubscribe:<br>
<a href="http://mailman.ucar.edu/mailman/listinfo/ncl-talk" rel="noreferrer" target="_blank">http://mailman.ucar.edu/<wbr>mailman/listinfo/ncl-talk</a><br>
<br></blockquote></div><br></div>