McIDAS-V Support Forums

Support and discussion of the McIDAS-V software package
Forum HomeMcIDAS-V Home
It is currently 04 Aug 2020, 02:50

All times are UTC




Post new topic Reply to topic  [ 2 posts ] 
Author Message
 Post subject: using GOES-16 data as local area data
PostPosted: 11 Oct 2017, 16:27 
User avatar

Joined: 19 Jan 2009, 19:16
Posts: 1119
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


Top
 Profile  
 
 Post subject: Re: using GOES-16 data as local area data
PostPosted: 11 Oct 2017, 22:09 
User avatar

Joined: 15 Jan 2009, 22:34
Posts: 408
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


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 2 posts ] 

All times are UTC


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group