<?xml version="1.0"?>

<nexradExportBatchOptions>

   <!-- Define Options for Level-II Command-Line Batch Export

   -->
   <level2options>

      <!-- moment value of 0 (REFLECTIVITY), 1 (VELOCITY) or 2 (SPECTRUM WIDTH) -->
      <moment> 0 </moment> 

      <!-- integer cut (not elevation angle) of radar file 
           - some cuts will not contain any information for the desired moment 
           - 0 & 2 generally only have Reflectivity data while 1 & 3 have Velocity/Spec. Width 
           - The remaining cuts usually have all moments in each cut although this may vary with
           - vcp 12 and 121. -->
      <cut> 0 </cut> 
     
      <!-- Classify polygon values into 5 dbZ (4 dbZ in Clear-Air Mode) intervals -->
      <classify> false </classify> 

      <!-- Export RF values for BVEL and SPEC moments -->
      <useRFvalues> true </useRFvalues>

      <!-- Export single cut in point shapefile -->
      <exportPoints> false </exportPoints> 

      <!-- Export entire moment in point shapefile (overrides exportPoints value 
        and any specified cut integer)-->
      <exportAllPoints> false </exportAllPoints> 

   </level2options>

   <level2filter>
     
      <!-- Range Filter units of kilometers -->
      <minRange> NONE </minRange>
      <maxRange> NONE </maxRange>
      <!-- Azimuth Filter units of decimal degrees -->
      <minAzimuth> NONE </minAzimuth>
      <maxAzimuth> NONE </maxAzimuth>
      <!-- Value Filter of int or floating point number -->
      <minValue> NONE </minValue>
      <maxValue> NONE </maxValue>
      
      <!-- All geographic extent fields must be specified for
           geographic filter to be engaged. -->
      <!-- Geographic Extent Filter units of decimal degrees -->
      <minLat> NONE </minLat>
      <maxLat> NONE </maxLat>
      <minLon> NONE </minLon>
      <maxLon> NONE </maxLon>
      <!-- Example geographic filter: 
           Uncomment and modify if desired 
           Because the 'min' or 'max' longitude value can be confusing, 
           it doesn't matter which has the 'true' min value.  This 
           will be calculated automatically in the program. -->
      <!--
      <minLat> 35.0 </minLat>
      <maxLat> 36.0 </maxLat>
      <minLon> -90.0 </minLon>  
      <maxLon> -91.0 </maxLon>
      -->
      
      
      <!-- Height Filter units of meters (relative to radar site) -->
      <minHeight> NONE </minHeight>
      <maxHeight> NONE </maxHeight>

   </level2filter>


   
   
   
   <level3options>

      <!-- Join equal value polygons - this greatly increases 
         processing time but reduces filesizes by ~35% -->
      <reducePolygons> false </reducePolygons> 

   </level3options>


   <level3filter>
     
      <!-- Range Filter units of kilometers - only applies to Radial products. -->
      <minRange> NONE </minRange>
      <maxRange> NONE </maxRange>
      <!--
      While most Level-III data is categorized, this software will calculate which
      categories should be included based on max and min filter values. 
      
      Multiple max-min ranges can be created for the value filter.  Use a comma-separated list of min values
        with a comma-separated list of max values.  For example, min values of '-200,30' and max values of '-30,200'
        creates 2 value ranges of -200 to -30 and 30 to 200.  This is useful for velocity products where the strongest
        winds are of most interest.
       -->
      <minValue> NONE </minValue>
      <maxValue> NONE </maxValue>
      
      <!--
      The Category Override allows non-numeric fields (such as 'RF' for range folding)
       to be included if desired.
      -->
      <categoryOverrides>RF</categoryOverrides>

      <!-- All geographic extent fields must be specified for
           geographic filter to be engaged. -->
      <!-- Geographic Extent Filter units of decimal degrees -->
      <minLat> NONE </minLat>
      <maxLat> NONE </maxLat>
      <minLon> NONE </minLon>
      <maxLon> NONE </maxLon>
      <!-- Example geographic filter: 
           Uncomment and modify if desired 
           Because the 'min' or 'max' longitude value can be confusing, 
           it doesn't matter which has the 'true' min value.  This 
           will be calculated automatically in the program. -->
      <!--
      <minLat> 35.0 </minLat>
      <maxLat> 36.0 </maxLat>
      <minLon> -90.0 </minLon>  
      <maxLon> -91.0 </maxLon>
      -->
   </level3filter>


   
   
   
   
   <exportRasterOptions>
      
      <!-- 'squareGridSize' represents the size for the 'long' side of 
           the raster grid.  The short side is dynamically calculated
           (always height because we are on a lat/lon grid).  The
           grid cell resolution is dynamically calculated.

           For example, if 1000 is used, the width will be 1000, but
           the height will probably be somewhere between 800 and 900
           depending on the latitude.  This is done to reduce filesize
           by minimizing the amount of 'noData' areas outside the 
           extent of the Radar site.

           If this value is '-1', the 'gridCellResolution' value 
           will be used and the raster size is dynamically generated.

      -->
      <squareGridSize> 1000 </squareGridSize>



      <!-- 'gridCellResolution' represents the grid cell resolution in decimal degrees.
           The actual size (height and width) of the raster is
           dynamically calculated based on this value and the 
           extent of the Radar (or extent of the data if 'autoResolution'
           flag is set to 'true')
      
           If this value is '-1', the 'squareGridSize' value will be
           used and the grid cell resolution is dynamically generated.

           ** This functionality implemented in version >= 1.5.1 **
      -->
      <gridCellResolution> -1 </gridCellResolution>

      <!-- 'noDataValue': Value for 'No Data' points in the grid -->
      <noDataValue> -999 </noDataValue>

      <!-- 'autoResolution':  Fit the grid size around the decoded features (Auto-Resolution)? 
           This option will determine the extent of the actual data 
           present (as opposed to the maximum extent of the Radar site, i.e.
           Radar coverage) and size the raster accordingly.  

           If the 'squareGridSize' option is used, the grid resolution 
           will change for each change in input data.

           If the 'gridCellResolution' option is used, the grid size
           will change for each change in input data.
      -->
      <autoResolution> false </autoResolution>

   </exportRasterOptions>

   
   
   
</nexradExportBatchOptions>
