using GOES-16 data as local area data

Errors and unexpected results
Post Reply
User avatar
joleenf
Posts: 1120
Joined: Mon Jan 19, 2009 7:16 pm

using GOES-16 data as local area data

Post by joleenf »

Hi,

I have GOES-16 data locally, that are copied via an ADDE IMGCOPY. It seems that these two UNIT parameters work:

ir_temperature = loadADDEImage(band=14, unit='Temperature', **loadADDE)
and
ir_temp = loadADDEImage(band=14, unit='TEMP', **loadADDE)

but only this works for visible
vis_alb = loadADDEImage(band=2, unit='ALB', mag=(1, 1), **loadADDE)


This does not work
vis_temperature = loadADDEImage(band=2, unit='Albedo', mag=(1, 1), **loadADDE)

The unit of 'Albedo' does work for remote access to ADDE data. I have not tested for netCDF data that I might point to as GOES-16 ABI data.

Joleen
User avatar
jayh
Posts: 415
Joined: Thu Jan 15, 2009 10:34 pm

Re: using GOES-16 data as local area data

Post by jayh »

Hi Joleen-

I was able to replicate your issue using GOES-13 and GOES-16 AREA files. I've written up inq. 2589 for evaluation to get ALB/Albedo to behave the same way TEMP/Temperature do in loadADDEImage calls.

I found this error in my log file:
__main__.AddeJythonInvalidUnitError: Unit not found in band. (error code: -11007)

Thanks for reporting this problem!

-Jay
Post Reply