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

Re: CoordinateAxis.getBoundaryRef

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: CoordinateAxis.getBoundaryRef
  • Date: Tue, 07 Mar 2006 13:33:32 -0700


Robert B. Schmunk wrote:


On Mar 6, 2006, at 20:44, John Caron wrote:


Hi Robert:
The getBoundaryRef() are optional, and as you note, rarely (never?) implemented. One of those features I planned to implement but didnt get back to. Sorry for the cruft. 


Ah, and I was hoping it would be an automatic thing. Sort of a  convenience
method which would replace stringing together a

(((VariableDS)axis).findAttribute ("bounds").getStringValue ( );


A nice convenience method along those lines, for string valued attributes, is

NetcdfFile.findAttValueIgnoreCase(Variable v, java.lang.String attName, 
java.lang.String defaultValue)
Ill get the "all javadocs" back on line. Public is (sort of) the stable public interface, "all" is everything, includeing experimental classes and implementation classes.
Ah, if that's what "all" means, then I should probably stick to the "public" 
API. I've whined enough in the past about adjusting to API changes. :)


yes i would recommend it.







--
Robert B. Schmunk, address@hidden
NASA Goddard Institute for Space Studies, 2880 Broadway, New York, NY 10025