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.

Re: [thredds] NetCDF Tools UI


On Aug 24, 2010, at 11:53 AM, john caron wrote:


Hi nathan:
Im wondering what your case is. Is is that you want to use the jnlp file in Hyrax without creating a catalog? 


Exactly.



Or you are not making dataset ids for the fragment? or ???
There was an issue with dataset IDs in my code. I think I have it worked out now. I asked so that I might use a feature if it existed. 

Nathan





john

Ethan Davis wrote:

Hi Nathan,
Currently, the netCDF ToolsUI will accept a single argument which must 
be a URL to a THREDDS catalog. It opens that catalog in the "THREDDS"
tab. If the URL has a fragment identifier which is a valid dataset ID, 
that dataset is selected and displayed in the "THREDDS" tab.

It would be a nice addition to allow a "-dap <dapURL>" argument which
would open the OPeNDAP dataset in the "Viewer" tab. I've added this to 
our enhancements list.

Ethan

On 8/3/2010 3:23 PM, Nathan Potter wrote:


Greetings,
I have a question about the NetCDF Tools UI. I have been looking at the JNLP files that are used to "WebStart" the application and the arguments 
section looks like this:

/  <application-desc main-class="ucar.nc2.ui.ToolsUI">
  <argument>{catalog}#{dataset}</argument>
</application-desc>
/
And a typical URL to invoke it looks like this:

/http://motherlode.ucar.edu/thredds/view/ToolsUI.jnlp?catalog=http://motherlode.ucar.edu/thredds/catalog/fmrc/NCEP/GFS/Alaska_191km/runs/catalog.xml&dataset=fmrc/NCEP/GFS/Alaska_191km/runs/NCEP-GFS-Alaska_191km_RUN_2010-08-03T12:00:00Z
<http://motherlode.ucar.edu/thredds/view/ToolsUI.jnlp?catalog=http://motherlode.ucar.edu/thredds/catalog/fmrc/NCEP/GFS/Alaska_191km/runs/catalog.xml&dataset=fmrc/NCEP/GFS/Alaska_191km/runs/NCEP-GFS-Alaska_191km_RUN_2010-08-03T12:00:00Z > 
/
Which in turn returns a JNLP file with the argument element filled in: 

/  <application-desc main-class="ucar.nc2.ui.ToolsUI">
<argument>http://motherlode.ucar.edu/thredds/catalog/fmrc/NCEP/GFS/Alaska_191km/runs/catalog.xml#fmrc/ NCEP/GFS/Alaska_191km/runs/NCEP-GFS- Alaska_191km_RUN_2010-08-03T12:00:00Z</argument> 
</application-desc>
/

So I would deduce that it wants the catalog URL and the
thredds:dataset/@ID attribute separated by a "#" sign as it's argument. 

Does it accept different argument schemes?
Is there a way to simply pass it a DAP data access URL?

/http://motherlode.ucar.edu/thredds/dodsC/fmrc/NCEP/GFS/Alaska_191km/runs/NCEP-GFS-Alaska_191km_RUN_2010-08-03T12:00:00Z
/
Or even a URL that returns a netcdf file?

/http://motherlode.ucar.edu/thredds/dodsC/fmrc/NCEP/GFS/Alaska_191km/runs/NCEP-GFS-Alaska_191km_RUN_2010-08-03T12:00:00Z.nc
/
(This last example is really a fictitious URL but I hope you can
appreciate my point)


Or is it the case that it will only accept a THREDDS catalog and a
dataset ID as arguments?


Nathan




= = =
Nathan Potter                        ndp at opendap.org
OPeNDAP, Inc.                        +1.541.231.3317





_______________________________________________
thredds mailing list
thredds@xxxxxxxxxxxxxxxx
For list information or to unsubscribe,  visit: 
http://www.unidata.ucar.edu/mailing_lists/


_______________________________________________
thredds mailing list
thredds@xxxxxxxxxxxxxxxx
For list information or to unsubscribe,  visit: 
http://www.unidata.ucar.edu/mailing_lists/


_______________________________________________
thredds mailing list
thredds@xxxxxxxxxxxxxxxx
For list information or to unsubscribe,  visit: 
http://www.unidata.ucar.edu/mailing_lists/


= = =
Nathan Potter                        ndp at opendap.org
OPeNDAP, Inc.                        +1.541.231.3317
  • 2010 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the thredds archives: