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

Re: Registering convention handlers

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: Re: Registering convention handlers
  • Date: Wed, 14 Dec 2005 15:27:07 -0700

Don Murray wrote:

Jeff-

Jeff McWhirter wrote:


Don and John,
I just added the ability to specify netcdf convention handlers via idv properties. 
Don - this does indeed work with the jar files in the plugins directory.
Is there a test file and test convention handler around that I can test this with? 

John said he is going to work on this once he got the server
500 error fixed.  You could remove one of the existing conventions
from the JAR file and from the static registry in CoordSysBuilder
in the mean time and test that way.

What do you use for the name?  The name is supposed to be
the conventions string (e.g. CF-1.0)

either that or you implement

 /** return true if you think this is your file. */
 public static boolean isMine( NetcdfFile ncfile);

the conventions test is preferred, since its guareeteed to be a fast test.


Don
*************************************************************
Don Murray                               UCAR Unidata Program
address@hidden                        P.O. Box 3000
(303) 497-8628                              Boulder, CO 80307
http://www.unidata.ucar.edu/staff/donm
        "Time makes everyone interesting, even YOU!"
*************************************************************