The bundle tag lets you load in a new bundle and takes the form:

<bundle file="some_bundle_file.xidv"/>

<bundle file="some_bundle_file.xidv" clear="false"/>

The bbox attribute is a string of the form "north,west,south,east" and will relocate any gridded data to use these bounds.

The wait attribute, if true (the default), will essentially do a pause, waiting until all displays have been rendered.

The window attribute, if true and in offscreen mode, will generate idv window object, that is needed when saving to a zidv bundle.

The times attribute allows you to override the set of time indices that are used in the data sources in the bundle. Note: this overrides the times for all data sources in the bundle.

The value is a comma separated list of time specifiers where the specifier can be a single time, a time range or a time range with a step. The time indices are 0 based, e.g., the first time index is 0. The time range is of the form "firsttime:lasttime". To specify a step do: "firsttime:lasttime:step"

For example, we have:

   times="0"                    -- Just use the first time
   times="2"                    -- Just use the third time
   times="0,1,2"                -- Just use the first 3 times
   times="0:10"                 -- 0 through 10
   times="0:10:2"               -- 0,2,4,6,8,10
   times="0:10:2, 20:30"        -- 0,2,4,6,8,10 20-30
   times="1,2,3,5:11:2,20,30"   -- 1,2 3, 5,7,9,11, 20, 30

For example, we have:

   ensembles="0"                -- Just use the first ensemble members
   ensembles="0,1,2"            -- Just use the first 3 ensemble members
   ensembles="0:10:2"           -- ensemble members 0,2,4,6,8,10
   etc...

For example, we have:

<bundle file="some_bundle_file.xidv" bbox="50,-110,30,-100"/>

For example, we have:

<bundle file="some_bundle_file.xidv" timedriverstart="yyyy-MM-dd HH:mm:ss Z" timedriverend="yyyy-MM-dd HH:mm:ss Z"/>

The bundle tag can contain any number of "setfiles" tags. Each of these setfiles tags has a datasource attribute which is used to find the data source in the bundle by name. There is also a file attribute which defines a file to use for that data source.

e.g.:

<isl debug="true" offscreen="false">
    <bundle file="test.xidv">
         <setfiles datasource=".*" file="/upc/share/testdata/grid/netcdf/nuwg/ruc.nc"/>
     </bundle>
     <image file="test.png"/>
</isl>

datasource=".*" 

<isl debug="true" offscreen="false">
    <bundle file="test.xidv">
        <setfiles datasource="datasource1" file="file for first data source"/>
        <setfiles datasource="datasource2" file="file for 2nd data source"/>
    </bundle>
    <image file="test.png"/>
</isl>

<setfiles datasource="datasource1">
    <fileset file="some file"/>
    <fileset file="some other file"/>
     ...
</setfiles>

The datasource tag lets you create a new data source and takes the form. The url attribute is required and specifies the file or url to load. The type attribute is optional and defines the data source type from the datasources.xml file in the source release. For a text listing see Datasources.html. For now you can only specify a data source that takes a single url (or filename). This will change in the future. The times and ensembles attributes work the same as in the bundle tag above.

<isl>
  <datasource url="dods://motherlode.ucar.edu/cgi-bin/dods/DODS-3.2.1/nph-dods/dods/casestudies/idvtest/grids/small_ruc_grid.nc">
<!-- Set the name on the data source  -->
    <property
       name="name"
       value="the name"/>
  </datasource>
</isl>
datasource.isl

    stridex = the X skip factor (stride)
    stridey = the Y skip factor
    stridez = the Z skip factor
    bbox    = the geographic bounding box (N,W,S,E)

  <isl>
  <datasource
       url="dods://motherlode.ucar.edu:8080/thredds/dodsC/casestudies/idvtest/grids/small_ruc_grid.nc" stridex="2" stridey="3" stridez="2" bbox="40,-113,20,-98"/>
  </isl>

The display tag lets you create a display and can exist on its own:

<display type="somedisplaytype" param="some_parameter"/>

<isl>

<!-- Create   a datasource. Note: you can also have a template attribute
     that points to a bundle xidv file that was saved from a data source:
     bundle="${islpath}/datasource.xidv"
-->

  <datasource 
     url="dods://motherlode.ucar.edu:8080/thredds/dodsC/casestudies/idvtest/grids/small_ruc_grid.nc"
     id="datasource1">
<!-- Set the name on the data source  -->
    <property
       name="name"
       value="Example data source"/>
<!-- Create a display of RH. Here we load in the display from a template.  -->
<!--
    <display
       param="RH" template="${islpath}/template.xidv">
      <property
         name="id"
         value="display1"/>
      <property
         name="displayCategory"
         value="Category 1"/>
      <property
         name="legendLabelTemplate"
         value="%datasourcename% - %shortname%"/>
    </display>
-->


<!-- Create a display of T. Here we create the display from the type -->
    <display
	type="planviewcontour"
      param="T">
      <property
         name="displayCategory"
         value="Category 1"/>
<!--
        The contour info can be set with: interval;base;min;max
              <property name="contourInfoParams" value="10;40;-30;100"/>
         Or it can have names in it:
-->
      <property name="contourInfoParams" value="interval=10;base=40;min=-30;max=100;dashed=true;labels=false"/>

<!--
you can also specify irregular levels with levels=, e.g.:
      <property name="contourInfoParams" value="levels=10,20,30;dashed=true;labels=false"/>
-->

      <property
         name="legendLabelTemplate"
         value="%datasourcename% - %shortname%"/>

<!-- This sets the level to be 500 hectopascals -->
<!-- Note: this can also be of the form #<index>, eg. #4 will select the 5th level (this is zero based) -->

      <property
         name="dataSelectionLevel"
         value="500[hectopascals]"/>


    </display>
  </datasource>


<!-- Set the projection to the data projection  of the display we created above  -->
<!--
  <center
     display="display1"
     useprojection="true"/>
-->

</isl>
display.isl

The param attribute is not required. If specified it is the name of a parameter in either the containing datasource tag or in one of the currently loaded data sources. The display tag will evolve in time to provide a richer set of facilities for setting values on the display.

The property tags define various properties to apply to the display. See here for a listing.

The spatial subset attributes described in the datasource tag above can be used with each display to override the default.

This removes all current displays. If there is the display attribute set then it removes that display. (See below).

<removedisplays/>

<removeall/>

<reload/>

The center tag comes in a number of forms, depending on the attributes:

<isl>
    <bundle file="test.xidv"/>
    <pause/>

    <echo message="Set the projection to be the projection of the first display"/>
    <center/>
    <pause seconds="10"/>

    <echo message="Center at a point"/>
    <center lat="15" lon="-65"/>
    <pause seconds="10"/>

    <echo message="Set the projection to be the lat/lon box"/>
    <center north="40.0" south="30" east="-90" west="-100"/>
    <pause seconds="10"/>

    <echo message="Set the projection from the specified display"/>
    <center display="display1" useprojection="true"/>
    <pause seconds="10"/>

    <echo message="Center at the center of the given displays projection"/>
    <center display="display1" useprojection="false"/>
    <pause seconds="10"/>

</isl>
center.isl

display="some name"

display="class:ucar.unidata.idv.TrackControl"
or:
display="TrackControl"

<isl>
    <bundle file="test.xidv"/>
    <pause/>

    <echo message="Changing the projection defined in the bundle to be North America"/>
    <projection name="North America"/>
    <pause seconds="10"/>

</isl>
projection.isl

The viewpoint tag comes in a number of forms, depending on the attributes:

<?xml version="1.0" encoding="ISO-8859-1"?>
<isl debug="true" loop="1" offscreen="false" sleep="60.0minutes">
  <bundle clear="true" file="${islpath}/test.xidv" wait="true"/>
  <pause seconds="5"/>

<!-- Specify a rotation, translation and scale. These values are shown in the Aspect Ratio tab of the View Manager properties dialog  -->
  <viewpoint  rotx="75" roty="62" rotz="-3.3" scale="0.399" transx="0.0" transy="0.0" transz="0.0"/>
  <pause seconds="5"/>

<!-- You can also set the aspect ratio  -->
  <viewpoint  aspectx="2" aspecty="5" aspectz="10"/>
  <pause seconds="5"/>

<!-- You can also specify a tilt and azimuth. This is the same as you can do interactively in the viewpoint dialog -->
  <viewpoint  tilt="45" azimuth="180"/>
  <pause seconds="5"/>

</isl>
viewpoint.isl

<?xml version="1.0" encoding="ISO-8859-1"?>
<isl debug="true" loop="1" offscreen="true" sleep="60.0minutes">
  <bundle clear="true" file="${islpath}/test.xidv" wait="true"/>
  <export file="/tmp/test" what="csv, netcdf" display="class:ucar.unidata.idv.control.ObsListControl"/>
</isl>
export.isl

display="class:ucar.unidata.idv.control.ObsListControl"

<?xml version="1.0" encoding="ISO-8859-1"?>
<isl debug="true" loop="1" offscreen="true" sleep="60.0minutes">
  <bundle clear="true" file="${islpath}/test.xidv" wait="true"/>
  <displayproperties display="class:ucar.unidata.idv.control.ContourPlanViewControl">
      <property name="DisplayAreaSubset"  value="true"/>
  </displayproperties>
  <export file="/tmp/test/test.zidv" what="zidv" />
</isl>
exportZidv.isl

Unidata's Integrated Data Viewer > Miscellaneous > IDV Scripting