NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi Jeff, Thanks for your reply. The documentation is useful and I was able to specify the datasource to be loaded using datasource tag. But it's unclear how one would specify a certain kind of display, e.g If I want to load temperature data for a NAM datasource what exactly will go in the display tags? There are other kinds of displays like dew point, pressure etc. I am not sure how to load these using ISL files. The -b64isl argument will be helpful in the sense that I need not create a separate isl and pass it as a param to the jnlp. Thanks for your help. Happy Thanksgiving, Nilesh. On Wed, Nov 26, 2008 at 2:28 PM, Jeff McWhirter <jeffmc@xxxxxxxxxxxxxxxx>wrote: > Felix Terkhorn wrote: > >> Actually, we talked again with the project coordinator and we won't need >> to worry about the spatial subsetting. Again, thanks for your help here, >> Jeff & Don! >> >> >> > Hi, > I'm not sure on where we're at right now in all of this. > There is documentation on using the datasource and display tags in isl: > > http://www.unidata.ucar.edu/software/idv/release/nightly/docs/userguide/isl/DataAndDisplays.html#datasource > > > This allows you to explicitly load in data and create displays from ISL > without resorting to a bundle file. > > I am going to add a -b64isl command line argument that will allow one to > include the ISL script inline in a jnlp file > as a command line argument. (Kind of like the -b64bundle argument). > > -Jeff > >
idvdevelopers archives: