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.
>From: "Stonie R. Cooper" <address@hidden> >Organization: Planetary Data, Inc. >Keywords: 200305231906.h4NJ6NLd025054 >Steve, > >Doing a little filtering here . . . one of RAP's customers, the US Army, uses >Garp quite a bit. Anyway, they put up profiler data, and then set autoupdate >on. > >You and I know that autoupdate is only for imagery . . . but unlike nmap, garp > >doesn't disallow autoupdating for non-imagery data. > >Are you . . . or anyone else at UNIDATA/COMET . . . doing any garp >development? If so, I'll point a request at you/them. Thanks! >-- >Stonie R. Cooper >Planetary Data, Inc. (PDI) >(402) 782-6611 [866-475-3733] > Stonie, There is nobody left at COMET that did the Garp development, so that avenue is basically closed. I try to fix bugs (and re-port the code when the gemlib functions change with new releases). Is your solution a gray-ing out (desensitizing) of the auto-update for specific data types? I'm mired under working on NEXRAD II displays at the moment, so I'm not in the Garp code diving mode at present. Steve Chiswell