[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

19990719: GDBIINT Program

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 19990719: GDBIINT Program
  • Date: Thu, 22 Jul 1999 09:49:09 -0600
>From: Brett Newkirk <address@hidden>
>Organization: .
>Keywords: 199907220036.SAA07036

>Hi Steve:
>
>I looked at the interpolation problem a bit more and I ensured that the
>warning regarding the output grid having points outside the input grid did
>not appear and I still get the same results. I believe that I have all
>parts of the thinned grid. In looking at the code, it looks as if you do
>account for data outside by giving it RMISSD in gdinterp.f. I am not sure
>why this result happens with that in mind.
>I will continue to look at this by trying other grids as well.
>Thanks,
>Brett
>> 
>> Brett,
>> 
>> I'll have to look at how the missing values are handled. I'll look at
>> interpolating the AVN thinned to the CED grid you mention. I know I had the 
> program
>> issue a warning if the output grid had points outside the original domain- w
> hich
>> would be possible with the ETA, but the AVN is global...assuming all 8 parts
>> of the grid have been received, so this should not be a problem unless there
>> is a seaming problem. 
>> 
>> Steve Chiswell
>

Brett,

It might be that I'm averaging a -9999 point with data and coming up
with some garbage results. I'll check into this...I'm preparing the
Gempak workshop for next week so have to budget time accordingly.

Steve Chiswell