Hi Ioan,
re:
> All the best in 2018.
Same to you!
re:
> I'll get straight to business...I have the feeling the ADDE ABIN server
> has a bug
>
> I am making 5 req for the image header
>
> 2018-01-12 17:18:53,617 [INFO] client.py -- RTGOESR FD 0 0 TRACE=0 BAND=2
> VERSION=1 AUX=YES
> 2018-01-12 17:18:53,617 [INFO] client.py -- RTGOESR FD 0 0 TRACE=0 BAND=5
> VERSION=1 AUX=YES
> 2018-01-12 17:18:53,617 [INFO] client.py -- RTGOESR FD 0 0 TRACE=0 BAND=7
> VERSION=1 AUX=YES
> 2018-01-12 17:18:53,618 [INFO] client.py -- RTGOESR FD 0 0 TRACE=0 BAND=13
> VERSION=1 AUX=YES
> 2018-01-12 17:18:53,619 [INFO] client.py -- RTGOESR FD 0 0 TRACE=0 BAND=15
> VERSION=1 AUX=YES
> 2018-01-12 17:18:54,079 [INFO] adde_downloader.core -- Area Directory
> 2018-01-12 16:00:41
> Source instrument: ABIN
> Calibration type: RAW
> Bands: [2]
> Y resolution: 1
> X resolution: 1
> Size (21696, 21696)
> Data width: 2
>
> 2018-01-12 17:18:54,096 [INFO] adde_downloader.core -- Area Directory
> 2018-01-12 16:00:41
> Source instrument: ABIN
> Calibration type: RAW
> Bands: [15]
> Y resolution: 4
> X resolution: 4
> Size (5424, 5424)
> Data width: 2
>
> 2018-01-12 17:18:54,114 [INFO] adde_downloader.core -- Area Directory
> 2018-01-12 16:00:41
> Source instrument: ABIN
> Calibration type: RAW
> Bands: [13]
> Y resolution: 4
> X resolution: 4
> Size (5424, 5424)
> Data width: 2
>
> 2018-01-12 17:18:54,128 [INFO] adde_downloader.core -- Area Directory
> 2018-01-12 16:00:41
> Source instrument: ABIN
> Calibration type: RAW
> Bands: [5]
> Y resolution: 2
> X resolution: 2
> Size (10848, 10848)
> Data width: 2
>
> 2018-01-12 17:18:54,150 [INFO] adde_downloader.core -- Area Directory
> 2018-01-12 16:00:41
> Source instrument: ABIN
> Calibration type: RAW
> Bands: [7]
> Y resolution: 4
> X resolution: 4
> Size (5424, 5424)
> Data width: 2
Your output agrees with what the ADDE server shows for the bands specified
(but your Area Directory output is not in the same order your
'client.py -- RTGOESR FD 0 0 TRACE=0 BAND=' listings). Here is what
the ADDE server says for all bands for one time:
Resolution Factors (base=1): Line= 4.0 Element= 4.0
279 G-16 IMG 12 JAN 18012 15:45:41 0 75
Band: 1 0.47 um VIS aerosol-over-land 1.00 1.00 10848 x10848
Band: 2 0.64 um VIS clouds fog, insol, winds 0.50 0.50 21696 x21696
Band: 3 0.86 um Near IR veg/burn scar,aerosol, w 1.00 1.00 10848 x10848
Band: 4 1.37 um Near IR cirrus cloud 2.00 2.00 5424 x 5424
Band: 5 1.61 um Near IR cloud phase, snow 1.00 1.00 10848 x10848
Band: 6 2.24 um Near IR land/cloud, vege, snow 2.00 2.00 5424 x 5424
Band: 7 3.89 um IR Sfc, cloud, fog, fire, winds 2.00 2.00 5424 x 5424
Band: 8 6.17 um IR High-level WV, winds, rainfal 2.00 2.00 5424 x 5424
Band: 9 6.93 um IR Mid-level WV, winds, rainfall 2.00 2.00 5424 x 5424
Band: 10 7.34 um IR Lower-level WV, winds & SO2 2.00 2.00 5424 x 5424
Band: 11 8.44 um IR Total WV cloud phase, dust 2.00 2.00 5424 x 5424
Band: 12 9.61 um IR Total ozone,turbulence,wind 2.00 2.00 5424 x 5424
Band: 13 10.3 um IR Surface & cloud 2.00 2.00 5424 x 5424
Band: 14 11.2 um IR Imagery,SST,clouds,rainfall 2.00 2.00 5424 x 5424
Band: 15 12.3 um IR Total water, ash, and SST 2.00 2.00 5424 x 5424
Band: 16 13.3 um IR Air temp, cloud hgt and amt 2.00 2.00 5424 x 5424
proj: 0 created: 2018012 154541 memo: GOES-R Full Disk
type:ABIN cal type:RAW
offsets: data= 1280 navigation= 256 calibration= 768 auxiliary= 0
doc length: 0 cal length: 0 lev length: 0 PREFIX= 0
valcod: 0 zcor: 0 avg-smp: A
lcor: 1 ecor: 1 bytes per pixel: 2 ss:186
Resolution Factors (base=1): Line= 4.0 Element= 4.0
re:
> From GOESR PDU
> ------------------------------------------------------------------------------
> Horizontal Spatial Resolution | Full Disk
> ------------------------------------------------------------------------------
> km (nadir) | microradians | N/S (y-axis) | E/W (x-axis)
> ------------------------------------------------------------------------------
> 0.5 | 14 | 21696 | 21696
> ------------------------------------------------------------------------
> 1 | 28 | 10848 | 10848
> ------------------------------------------------------------------------
> 2 | 56 | 5424 | 5424
> ------------------------------------------------------------------------
> 4 | 112 | 2712 | 2712
> ------------------------------------------------------------------------
This listing matches the ADDE server output for the entries that have 0.5, 1
and 2 km resolutions. There do not appear to be any Full Disk GRB images
that have 4 km resolutions.
re:
> My feeling is that the resolution of the data is set wrong in the area
> directory or they set it to double the real resolution because of some
> limitations.
I disagree. The only thing that I see that doesn't match is the entry
for images that have 4 km resolutions at nadir. 'ncdump's on images
received in the GRB do not show any images that have 4 km resolution at nadir.
'ncdump's of each band you are accessing to get the image size also agree
with the ADDE server listing:
Band 2
netcdf
OR_ABI-L1b-RadF-M3C02_G16_s20180121545417_e20180121556184_c20180121556221 {
dimensions:
y = 21696 ;
x = 21696 ;
Band 5
netcdf
OR_ABI-L1b-RadF-M3C05_G16_s20180121545417_e20180121556184_c20180121556229 {
dimensions:
y = 10848 ;
x = 10848 ;
Band 7
netcdf
OR_ABI-L1b-RadF-M3C07_G16_s20180121600417_e20180121611196_c20180121611232 {
dimensions:
y = 5424 ;
x = 5424 ;
Band 13
netcdf
OR_ABI-L1b-RadF-M3C13_G16_s20180121600417_e20180121611196_c20180121611254 {
dimensions:
y = 5424 ;
x = 5424 ;
Band 15
netcdf
OR_ABI-L1b-RadF-M3C15_G16_s20180121600417_e20180121611190_c20180121611253 {
dimensions:
y = 5424 ;
x = 5424 ;
Which band(s) are you expecting to have 4 km resolution at nadir? Or is there
something else that I am missing?
Cheers,
Tom
--
****************************************************************************
Unidata User Support UCAR Unidata Program
(303) 497-8642 P.O. Box 3000
address@hidden Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage http://www.unidata.ucar.edu
****************************************************************************
Ticket Details
===================
Ticket ID: MOI-385613
Department: Support McIDAS
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata
inquiry tracking system and then made publicly available through the web. If
you do not want to have your interactions made available in this way, you must
let us know in each email you send to us.
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.