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

[IDV #YMI-196568]: Relative path in xidv file



Hi David-

> Thanks for your help with the issue bellow - I have just updated my build 
> from SVN and have run into a typing problem on the compile - can you please 
> advise on how to fix this?

Did you update local-visad.jar in the lib directory?  That has the updated
UniverseBuilderJ3D.   If you update now, you'll get a new local-visad.jar
and a new visad.jar.

Don Murray
> [javac] ----------
> [javac] 2641. ERROR in 
> /usr/local/src/idv/trunk/ucar/unidata/idv/IntegratedDataViewer.java (at line 
> 349)
> [javac]     
> visad.java3d.UniverseBuilderJ3D.setMinimumFrameCycleTime(minFrameCycleTime);
> [javac]                                     ^^^^^^^^^^^^^^^^^^^^^^^^
> [javac] The method setMinimumFrameCycleTime(long) is undefined for the type 
> UniverseBuilderJ3D
> [javac] ----------
> 
> 
> 
> -----Original Message-----
> From: Unidata IDV Support [mailto:address@hidden]
> Sent: Mon 6/15/2009 12:25 PM
> To: David Stuebe
> Cc: address@hidden
> Subject: [IDV #YMI-196568]: Relative path in xidv file
> 
> Hi David,
> 
> >
> > I was wondering if you can help me put a relative path in my XIDV file?
> > I have an NCML file which collects data in a particular way from a TDS
> > server - eventually I would like to put it on the server, but for
> > testing it would be helpful to have the plugin install with the NCML
> > file and have the XIDV session file grab that local NCML in the plugin
> > jar file. Using the relative path inside the jar does not work
> > /ucar/unidata/apps/asa_nmfs/TDS_AGG.ncml ? I can seem to get idv to find
> > a file by relative path though - are the IDVHOME env variables available
> > in and xidv file?
> >
> 
> The problem is that the java/netcdf code that we use is the one that opens up 
> the ncml file. It would not pick it up from the plugin jar. If the IDV was 
> the one to do this then we look at the plugin jars when opening any resource 
> path.
> 
> This might not help but...
> If your NCML file is applicable to a number of data files (i.e., you're not 
> adding, oh, say a time field to a particular file) then one way to do this is 
> to include a ncml file template and a specification of this new data source 
> type.  Then when your user selects a file or opendap link in a catalog they 
> can specify that that file or link is of a certain type. The IDV will 
> automatically instantiate the ncml file from the template in the plugin. See 
> attached for an example. It contains a template ncml file and a data source 
> definition xml file.
> 
> -Jeff
> 
> 
> Ticket Details
> ===================
> Ticket ID: YMI-196568
> Department: Support IDV
> Priority: Normal
> Status: Closed
> 
> 
> 


Ticket Details
===================
Ticket ID: YMI-196568
Department: Support IDV
Priority: Normal
Status: Open