diff --git a/404.html b/404.html
index 2a6a68fa67..bcf399f9b4 100644
--- a/404.html
+++ b/404.html
@@ -331,8 +331,8 @@
 
 
   <li class="md-nav__item">
-    <a href="/awips2/cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="/awips2/cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/appendix/appendix-acronyms/index.html b/appendix/appendix-acronyms/index.html
index 38f81bb80a..1e8c712a50 100644
--- a/appendix/appendix-acronyms/index.html
+++ b/appendix/appendix-acronyms/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../../cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../../cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/appendix/appendix-cots/index.html b/appendix/appendix-cots/index.html
index 0899229b75..bd48e15035 100644
--- a/appendix/appendix-cots/index.html
+++ b/appendix/appendix-cots/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../../cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../../cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/appendix/appendix-grid-parameters/index.html b/appendix/appendix-grid-parameters/index.html
index 5b94fe3786..9802c5d93e 100644
--- a/appendix/appendix-grid-parameters/index.html
+++ b/appendix/appendix-grid-parameters/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../../cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../../cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/appendix/appendix-wsr88d/index.html b/appendix/appendix-wsr88d/index.html
index e6f9cfd680..20cd20f23c 100644
--- a/appendix/appendix-wsr88d/index.html
+++ b/appendix/appendix-wsr88d/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../../cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../../cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/bundles-and-procedures/index.html b/cave/bundles-and-procedures/index.html
index 9d38fb5101..31b502a088 100644
--- a/cave/bundles-and-procedures/index.html
+++ b/cave/bundles-and-procedures/index.html
@@ -380,8 +380,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/cave-keyboard-shortcuts/index.html b/cave/cave-keyboard-shortcuts/index.html
index 8cdece9f54..d4c59ac494 100644
--- a/cave/cave-keyboard-shortcuts/index.html
+++ b/cave/cave-keyboard-shortcuts/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/cave-localization/index.html b/cave/cave-localization/index.html
index 5cf677ffb8..e0ea73fec7 100644
--- a/cave/cave-localization/index.html
+++ b/cave/cave-localization/index.html
@@ -341,8 +341,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/d2d-edit-menus/index.html b/cave/d2d-edit-menus/index.html
index d68ad52cef..59b48fcaeb 100644
--- a/cave/d2d-edit-menus/index.html
+++ b/cave/d2d-edit-menus/index.html
@@ -341,8 +341,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/d2d-gis-shapefiles/index.html b/cave/d2d-gis-shapefiles/index.html
index e98ca0c67a..2c6725e030 100644
--- a/cave/d2d-gis-shapefiles/index.html
+++ b/cave/d2d-gis-shapefiles/index.html
@@ -341,8 +341,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/d2d-gridded-models/index.html b/cave/d2d-gridded-models/index.html
index 66d2ef90ad..25c15871f8 100644
--- a/cave/d2d-gridded-models/index.html
+++ b/cave/d2d-gridded-models/index.html
@@ -341,8 +341,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/d2d-grids/index.html b/cave/d2d-grids/index.html
index bf44d68d58..d4833e138d 100644
--- a/cave/d2d-grids/index.html
+++ b/cave/d2d-grids/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/d2d-hydro/index.html b/cave/d2d-hydro/index.html
index 2fdc0a1d97..26b6186e92 100644
--- a/cave/d2d-hydro/index.html
+++ b/cave/d2d-hydro/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/d2d-map-resources/index.html b/cave/d2d-map-resources/index.html
index 69269dc253..13b9ea7b6c 100644
--- a/cave/d2d-map-resources/index.html
+++ b/cave/d2d-map-resources/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/d2d-perspective/index.html b/cave/d2d-perspective/index.html
index 807da625a6..37380ca738 100644
--- a/cave/d2d-perspective/index.html
+++ b/cave/d2d-perspective/index.html
@@ -468,8 +468,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/d2d-pointdata-surface-obs/index.html b/cave/d2d-pointdata-surface-obs/index.html
index 7904cd255a..05ef33fa42 100644
--- a/cave/d2d-pointdata-surface-obs/index.html
+++ b/cave/d2d-pointdata-surface-obs/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/d2d-radar-tools/index.html b/cave/d2d-radar-tools/index.html
index 1882429011..fa94080b80 100644
--- a/cave/d2d-radar-tools/index.html
+++ b/cave/d2d-radar-tools/index.html
@@ -341,8 +341,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/d2d-radar/index.html b/cave/d2d-radar/index.html
index 8d4eeb742c..f8a965f960 100644
--- a/cave/d2d-radar/index.html
+++ b/cave/d2d-radar/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/d2d-satellite/index.html b/cave/d2d-satellite/index.html
index 6fceace8ed..51545c7fc1 100644
--- a/cave/d2d-satellite/index.html
+++ b/cave/d2d-satellite/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/d2d-tools/index.html b/cave/d2d-tools/index.html
index c7baa21471..f3d20197f0 100644
--- a/cave/d2d-tools/index.html
+++ b/cave/d2d-tools/index.html
@@ -341,8 +341,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/d2d-uair/index.html b/cave/d2d-uair/index.html
index 45cd05f9a3..99f21fc51c 100644
--- a/cave/d2d-uair/index.html
+++ b/cave/d2d-uair/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/goes-16-satellite/index.html b/cave/goes-16-satellite/index.html
index eebab69bef..d3ab914ec7 100644
--- a/cave/goes-16-satellite/index.html
+++ b/cave/goes-16-satellite/index.html
@@ -341,8 +341,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
@@ -1225,7 +1225,7 @@ drwxr-xr-x 18 awips fxalpha TMESO-2
     <div class="md-footer-nav">
       <nav class="md-footer-nav__inner md-grid">
         
-          <a href="../warngen/" title="WarnGen" class="md-flex md-footer-nav__link md-footer-nav__link--prev" rel="prev">
+          <a href="../warngen/" title="WarnGen Walkthrough" class="md-flex md-footer-nav__link md-footer-nav__link--prev" rel="prev">
             <div class="md-flex__cell md-flex__cell--shrink">
               <i class="md-icon md-icon--arrow-back md-footer-nav__button"></i>
             </div>
@@ -1234,7 +1234,7 @@ drwxr-xr-x 18 awips fxalpha TMESO-2
                 <span class="md-footer-nav__direction">
                   Previous
                 </span>
-                WarnGen
+                WarnGen Walkthrough
               </span>
             </div>
           </a>
diff --git a/cave/import-export/index.html b/cave/import-export/index.html
index 6b064f4bca..e2aefdc0c6 100644
--- a/cave/import-export/index.html
+++ b/cave/import-export/index.html
@@ -394,8 +394,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/localization-perspective/index.html b/cave/localization-perspective/index.html
index 3053b5aa3e..0dd01c3aba 100644
--- a/cave/localization-perspective/index.html
+++ b/cave/localization-perspective/index.html
@@ -394,8 +394,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/maps-views-projections/index.html b/cave/maps-views-projections/index.html
index 21c0218a09..d6116116c8 100644
--- a/cave/maps-views-projections/index.html
+++ b/cave/maps-views-projections/index.html
@@ -387,8 +387,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/ncp-perspective/index.html b/cave/ncp-perspective/index.html
index 7960ff6282..e97f58268b 100644
--- a/cave/ncp-perspective/index.html
+++ b/cave/ncp-perspective/index.html
@@ -440,8 +440,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/cave/nsharp/index.html b/cave/nsharp/index.html
index 76dd08317c..54bcb2944f 100644
--- a/cave/nsharp/index.html
+++ b/cave/nsharp/index.html
@@ -426,8 +426,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
@@ -1096,13 +1096,13 @@
           </a>
         
         
-          <a href="../warngen/" title="WarnGen" class="md-flex md-footer-nav__link md-footer-nav__link--next" rel="next">
+          <a href="../warngen/" title="WarnGen Walkthrough" class="md-flex md-footer-nav__link md-footer-nav__link--next" rel="next">
             <div class="md-flex__cell md-flex__cell--stretch md-footer-nav__title">
               <span class="md-flex__ellipsis">
                 <span class="md-footer-nav__direction">
                   Next
                 </span>
-                WarnGen
+                WarnGen Walkthrough
               </span>
             </div>
             <div class="md-flex__cell md-flex__cell--shrink">
diff --git a/cave/warngen/index.html b/cave/warngen/index.html
index 6c982bc65f..88549f2662 100644
--- a/cave/warngen/index.html
+++ b/cave/warngen/index.html
@@ -21,7 +21,7 @@
     
     
       
-        <title>WarnGen - Unidata AWIPS User Manual</title>
+        <title>WarnGen Walkthrough - Unidata AWIPS User Manual</title>
       
     
     
@@ -92,7 +92,7 @@
               
             
             
-              WarnGen
+              WarnGen Walkthrough
             
           
         </span>
@@ -346,30 +346,47 @@
     
     <input class="md-toggle md-nav__toggle" data-md-toggle="toc" type="checkbox" id="toc">
     
-      
-    
     
       <label class="md-nav__link md-nav__link--active" for="toc">
-        WarnGen
+        WarnGen Walkthrough
       </label>
     
-    <a href="./" title="WarnGen" class="md-nav__link md-nav__link--active">
-      WarnGen
+    <a href="./" title="WarnGen Walkthrough" class="md-nav__link md-nav__link--active">
+      WarnGen Walkthrough
     </a>
     
       
 <nav class="md-nav md-nav--secondary">
   
   
-    
-  
   
     <label class="md-nav__title" for="toc">Table of contents</label>
     <ul class="md-nav__list" data-md-scrollfix>
       
         <li class="md-nav__item">
-  <a href="#launching-warngen" title="Launching WarnGen" class="md-nav__link">
-    Launching WarnGen
+  <a href="#load-nexrad-level-3-display" title="Load NEXRAD level 3 display" class="md-nav__link">
+    Load NEXRAD level 3 display
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#select-site-localization" title="Select SITE Localization" class="md-nav__link">
+    Select SITE Localization
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#select-the-nearest-wsr-88d-location" title="Select the nearest WSR-88D location" class="md-nav__link">
+    Select the nearest WSR-88D location
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#launch-warngen" title="Launch WarnGen" class="md-nav__link">
+    Launch WarnGen
   </a>
   
 </li>
@@ -379,6 +396,13 @@
     Generate a Storm Motion Vector
   </a>
   
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#restart" title="Restart" class="md-nav__link">
+    Restart
+  </a>
+  
 </li>
       
         <li class="md-nav__item">
@@ -931,15 +955,34 @@
 <nav class="md-nav md-nav--secondary">
   
   
-    
-  
   
     <label class="md-nav__title" for="toc">Table of contents</label>
     <ul class="md-nav__list" data-md-scrollfix>
       
         <li class="md-nav__item">
-  <a href="#launching-warngen" title="Launching WarnGen" class="md-nav__link">
-    Launching WarnGen
+  <a href="#load-nexrad-level-3-display" title="Load NEXRAD level 3 display" class="md-nav__link">
+    Load NEXRAD level 3 display
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#select-site-localization" title="Select SITE Localization" class="md-nav__link">
+    Select SITE Localization
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#select-the-nearest-wsr-88d-location" title="Select the nearest WSR-88D location" class="md-nav__link">
+    Select the nearest WSR-88D location
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#launch-warngen" title="Launch WarnGen" class="md-nav__link">
+    Launch WarnGen
   </a>
   
 </li>
@@ -949,6 +992,13 @@
     Generate a Storm Motion Vector
   </a>
   
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#restart" title="Restart" class="md-nav__link">
+    Restart
+  </a>
+  
 </li>
       
         <li class="md-nav__item">
@@ -1010,11 +1060,38 @@
                   <a href="https://github.com/Unidata/awips2/edit/master/docs/cave/warngen.md" title="Edit this page" class="md-icon md-content__icon">edit</a>
                 
                 
-                <h1 id="warngen">WarnGEN<a class="headerlink" href="#warngen" title="Permanent link"></a></h1>
-<p>WarnGen is an AWIPS application for issuing short-term, text-based warnings by National Weather Service WFOs.  WarnGen is an operational tool, and is designed to create and issue warning products from CAVE to EDEX.  Unidata AWIPS is <em>non-operational</em>, and one of its limitations is that CAVE can not send or issue warning products.  Unidata developers have left the WarnGen tool accessible in CAVE for education and training purposes. </p>
-<h2 id="launching-warngen">Launching WarnGen<a class="headerlink" href="#launching-warngen" title="Permanent link"></a></h2>
-<p>Select the WarnGen application from the D2D toolbar button. When WarnGen is started, the storm centroid marker appears and the WarnGen GUI will pop up as a separate window. </p>
-<p>You will need to load one or more products (and maps) to observe severe weather (ideal products are radar reflectivity or velocity, or both).</p>
+                  <h1>WarnGen Walkthrough</h1>
+                
+                <p>WarnGen is an AWIPS graphics application for creating and issuing warnings as is done by National Weather Service offices.  In the Unidata AWIPS release it is a <em>non-operational</em> forecasting tool, meaning it allows users to experiment and simulate with the drawing and text-generation tools, but prevents you from transmitting a generated warning upstream. </p>
+<div class="admonition warning">
+<p class="admonition-title">In order to select a feature it must be within your <em>CAVE localization</em> coverage (load <strong>Maps</strong> &gt; <strong>County Warning Areas</strong> to see coverages)</p>
+</div>
+<p>Steps involved in using WarnGen in Unidata AWIPS CAVE 17.1.1</p>
+<ul>
+<li>Load NEXRAD Display from the Radar menu.</li>
+<li>Choose a WFO site with active severe weather (LKZ is used in the video).</li>
+<li>Re-localize to this site in the CAVE &gt; Preferences &gt; Localization menu.</li>
+<li>Load NEXRAD Display again and select a WSR-88D site to load a 2-panel display of 0.5 degree Reflectivity (N0Q) and Velocity (N0U).</li>
+<li>Click the WarnGen toolbar button or load from Tools &gt; WarnGen.</li>
+<li>Drag the storm marker to the center of a storm feature.</li>
+<li>Step through frames back and forth and adjust the marker to match the trajectory of the storm feature.</li>
+<li>From the WarnGen dialog select the type of warning to generate, the time range, the basis of the warning, and any threats to add (wind, hail, etc). </li>
+<li>Click "Create Text" at the bottom of the WarnGen dialog to generate a text warning product in a new window.</li>
+<li>Click "Reset" at the top of the WarnGen dialog to reset the storm marker at any time.</li>
+<li>Select "Line of Storms" to enable a two-pointed vector which is to be positioned parallel to a storm line.</li>
+</ul>
+<iframe width="700" height="450"
+src="https://www.youtube.com/embed/KSKmIMjkVCU?autoplay=1">
+</iframe>
+
+<h2 id="load-nexrad-level-3-display">Load NEXRAD level 3 display<a class="headerlink" href="#load-nexrad-level-3-display" title="Permanent link"></a></h2>
+<p>Select the menu <strong>Radar</strong> &gt; <strong>NEXRAD Display</strong> and note coverage areas of current severe weather.  We choose a WFO ID that contains some active severe weather (KLZK Little Rock, Arkansas, in this example).</p>
+<h2 id="select-site-localization">Select SITE Localization<a class="headerlink" href="#select-site-localization" title="Permanent link"></a></h2>
+<p>Open <strong>CAVE</strong> &gt; <strong>Preferences</strong> &gt; <strong>Localization</strong>, select the WFO ID (KLZK) for the coverage area you want to use, followed by <strong>Apply</strong> and then <strong>Restart</strong>.</p>
+<h2 id="select-the-nearest-wsr-88d-location">Select the nearest WSR-88D location<a class="headerlink" href="#select-the-nearest-wsr-88d-location" title="Permanent link"></a></h2>
+<p>Click on any NEXRAD Display station to load a two-pane Reflectivity/Velocity view.</p>
+<h2 id="launch-warngen">Launch WarnGen<a class="headerlink" href="#launch-warngen" title="Permanent link"></a></h2>
+<p>Select <strong>WarnGen</strong> from the D2D Toolbar or from the <strong>Tools</strong> menu.  When started, the storm centroid marker appears and the WarnGen GUI will pop up as a separate window. </p>
 <table>
 <thead>
 <tr>
@@ -1024,12 +1101,11 @@
 </thead>
 <tbody>
 <tr>
-<td align="center"><img alt="" src="../../images/warngen.png" /></td>
 <td align="center"><img alt="" src="../../images/Warngen_Basic.png" /></td>
+<td align="center"><img alt="" src="../../images/warngen.png" /></td>
 </tr>
 </tbody>
 </table>
-<p>In order to select a feature it must be within your <em>EDEX server</em> localization coverage (default BOU)</p>
 <h2 id="generate-a-storm-motion-vector">Generate a Storm Motion Vector<a class="headerlink" href="#generate-a-storm-motion-vector" title="Permanent link"></a></h2>
 <ol>
 <li>Click and drag <strong>Drag Me to Storm</strong> to the feature you want to track (WarnGen uses a dot to track a single storm and a line to track a line of storms).</li>
@@ -1037,7 +1113,8 @@
 <li>Drag the dot to the previous position of the feature you first marked.</li>
 <li>Review the product loop and make adjustments to ensure the vector is accurate.</li>
 </ol>
-<p>After determinng the storm motion you will want to redraw the polygon to fit the new storm track. The easiest way to do this task is to use one of the </p>
+<h2 id="restart">Restart<a class="headerlink" href="#restart" title="Permanent link"></a></h2>
+<p>Click the <strong>Reset</strong> button to clear all current polygons and vectors and reset the storm centroid marker.</p>
 <h2 id="redrawing-a-polygon">Redrawing a Polygon<a class="headerlink" href="#redrawing-a-polygon" title="Permanent link"></a></h2>
 <p>Select the <strong>Track</strong> button in the <strong>"Redraw Box on Screen"</strong> section to redraw a default warning polygon oriented along the storm motion track and containing the storm centroid dot for the most recent volume scan. The initial polygon may have unhatched areas that will be removed from the warning due to crossing CWAs or not meeting area thresholds in the county for inclusion. The Warned/Hatched Area button allow you to preview the polygon shape that will be issued, so you can make further edits.</p>
 <h2 id="moving-vertex-points">Moving Vertex Points<a class="headerlink" href="#moving-vertex-points" title="Permanent link"></a></h2>
@@ -1046,8 +1123,13 @@
 <p>When reshaping your warning polygon in this manner, the philosophy is to include all areas that are at risk of experiencing severe weather covered by that warning type. Effective polygons account for uncertainty over time and typically widen downstream. There will be a lot of training provided on Storm-Based Warning Fundamentals in RAC and in the workshop, and this lesson is more focused on the basic mechanics.</p>
 <h2 id="add-and-remove-vertex-points">Add and Remove Vertex Points<a class="headerlink" href="#add-and-remove-vertex-points" title="Permanent link"></a></h2>
 <p>There will be some occasions where you will want to add vertices to your warning polygon. Most often, these situations will involve line warnings with bowing segments or single storm warnings where you want to account for storm motion uncertainty or multiple threat areas that may have differing storm motions.</p>
-<p>New vertices are added to the warning polygon using a context relative menu accessed by selecting the warning polygon line segments with a Right Mouse Button “click and hold.” In the menu that appears, just select the “add vertex” option to add a new point to the warning polygon. Make sure, when using this feature, that you select the line segment in the warning where you want to add the additional vertex. After selecting this option, you will see a new vertex linked to the cursor. Just press your Left Mouse Button at the location you desire for the new vertex and the new point is located there. In addition, clicking with the middle mouse button (or scroll wheel) along an edge of the polygon will also place a vertex at that point.</p>
-<p>Vertex points are removed from the warning polygon using the same context relative menu. Instead of selecting a line segment, you select the vertex you wish to remove and then “click and hold” with the Right Mouse Button. In the menu that appears, select “remove vertex” to remove the point from the warning polygon. Generally speaking, you should always have at least four points in your warning polygon. So, you should only remove a vertex if you are at a point after you have already added one to your warning polygon.</p>
+<p>New vertices are added to the warning polygon using a context relative menu accessed by selecting the warning polygon line segments with a <strong>Right Mouse Button "click and hold"</strong>. </p>
+<ol>
+<li>Hold right-click and select <strong>add vertex</strong>.</li>
+<li>Click the left mouse button at the location you desire for the new vertex and the point is created there.</li>
+<li>Clicking the middle mouse button (or scroll wheel) along an edge of the polygon will also place a vertex at that point.</li>
+</ol>
+<p>Vertex points are removed from the warning polygon using the same context relative menu. Instead of selecting a line segment, you select the vertex you wish to remove and then <strong>click and hold</strong> with right mouse button.  Hold right-click and select <strong>remove vertex</strong>. </p>
 <h2 id="restoring-a-polygon">Restoring a Polygon<a class="headerlink" href="#restoring-a-polygon" title="Permanent link"></a></h2>
 <p>When you are customizing a polygon in WarnGen, speed is critical. Everyone, even veteran warning forecasters, will occasionally draw a warning polygon one way and then realize, prior to sending the warning, that they want to draw the warning boundaries differently. Depending on the complexity of the changes you make to a warning polygon, sometimes it’s faster to just start over from scratch. The easiest way to proceed, especially if you are still comfortable with the storm motion, is to select the “Track” button from the “Redraw Box on Screen from” section of the WarnGen GUI.</p>
 <h2 id="text-window">Text Window<a class="headerlink" href="#text-window" title="Permanent link"></a></h2>
diff --git a/dev/awips-development-environment/index.html b/dev/awips-development-environment/index.html
index 9b8d7ee3f8..5d513f69c3 100644
--- a/dev/awips-development-environment/index.html
+++ b/dev/awips-development-environment/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../../cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../../cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/dev/build-nsharp-macos/index.html b/dev/build-nsharp-macos/index.html
index e33cddfd97..b244de6dea 100644
--- a/dev/build-nsharp-macos/index.html
+++ b/dev/build-nsharp-macos/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../../cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../../cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/edex/data-distribution-files/index.html b/edex/data-distribution-files/index.html
index 8a6c0d9a81..3f0c362d38 100644
--- a/edex/data-distribution-files/index.html
+++ b/edex/data-distribution-files/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../../cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../../cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
@@ -1081,7 +1081,7 @@ dpa.xml           pirep.xml
 <p>Save the file and exit the editor. EDEX will automatically pick up the new distribution pattern.</p>
 </li>
 </ol>
-<p>Raw files are written to <strong>/data_store</strong>, and a message is sent via QPID to the EDEX distribution service from the LDM. When a regular expression match is found in a data distribution file, the raw data file is placed in a queue for the matching plugin to decode and process. The distribution files are used to match file headers as well as filenames, which is how files dropped into EDEX’s manual endpoint (<strong>/awips2/data_store/ingest</strong>) are processed.</p>
+<p>Raw files are written to <strong>/data_store</strong>, and a message is sent via QPID to the EDEX distribution service from the LDM. When a regular expression match is found in a data distribution file, the raw data file is placed in a queue for the matching plugin to decode and process. The distribution files are used to match file headers as well as filenames, which is how files dropped into EDEX's manual endpoint (<strong>/awips2/data_store/ingest</strong>) are processed.</p>
 <h2 id="editing-an-edex-data-distribution-file">Editing an EDEX Data Distribution File<a class="headerlink" href="#editing-an-edex-data-distribution-file" title="Permanent link"></a></h2>
 <p>Because these files are in the <strong>edex_static/</strong> directory, they have to be manually edited using a text editor. You should not edit the base files; rather, you should copy the base version to your site and then edit the site version. The regular expressions in the distribution files need to correspond with the regular expressions in the LDM <strong><em>pqact.conf</em></strong><strong> </strong>file.</p>
 <p>If patterns exist in <strong><em>pqact.conf</em></strong> but are not in the distribution files, then raw data files will be written to <strong>/data_store</strong> but will not be ingested and processed by EDEX. Entries for these non-ingested files would be written to the unrecognized files log in <strong>/awips/edex/logs</strong>.</p>
diff --git a/edex/data-plugins/index.html b/edex/data-plugins/index.html
index 7627bd658c..fa49ccd441 100644
--- a/edex/data-plugins/index.html
+++ b/edex/data-plugins/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../../cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../../cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/edex/data-purge/index.html b/edex/data-purge/index.html
index e50d3856fc..9134e5e922 100644
--- a/edex/data-purge/index.html
+++ b/edex/data-purge/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../../cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../../cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/edex/edex-users/index.html b/edex/edex-users/index.html
index 8f934435d0..13abc8bf6b 100644
--- a/edex/edex-users/index.html
+++ b/edex/edex-users/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../../cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../../cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/edex/ldm/index.html b/edex/ldm/index.html
index 9bdbfdbf61..d2e69341e9 100644
--- a/edex/ldm/index.html
+++ b/edex/ldm/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../../cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../../cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/edex/new-grid/index.html b/edex/new-grid/index.html
index c5e7920025..f26e65cc6d 100644
--- a/edex/new-grid/index.html
+++ b/edex/new-grid/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../../cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../../cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
@@ -984,10 +984,10 @@ cp wrf.grib /awips2/data_store/ingest/
 <p>Confirm that the grib file decodes in the grib log file:</p>
 <pre><code>edex log grib
 
-INFO [Ingest.GribDecode] /awips2/data_store/manual/grib/20141026/14/wrf.grib processed in: 0.1200 (sec) Latency: 21.8080 (sec)
-INFO [Ingest.GribDecode] /awips2/data_store/manual/grib/20141026/14/wrf.grib processed in: 0.1180 (sec) Latency: 21.8140 (sec)
-INFO [Ingest.GribDecode] /awips2/data_store/manual/grib/20141026/14/wrf.grib processed in: 0.4230 (sec) Latency: 21.8360 (sec)
-INFO [Ingest.GribDecode] /awips2/data_store/manual/grib/20141026/14/wrf.grib processed in: 0.2240 (sec) Latency: 21.9140 (sec)
+INFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.1200 (sec) Latency: 21.8080 (sec)
+INFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.1180 (sec) Latency: 21.8140 (sec)
+INFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.4230 (sec) Latency: 21.8360 (sec)
+INFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.2240 (sec) Latency: 21.9140 (sec)
 
 ...
 </code></pre>
diff --git a/images/cave.png b/images/cave.png
index 1be220e6c5..0f2550ce75 100644
Binary files a/images/cave.png and b/images/cave.png differ
diff --git a/images/warngen_nexrad_display.png b/images/warngen_nexrad_display.png
new file mode 100644
index 0000000000..f62b3df31f
Binary files /dev/null and b/images/warngen_nexrad_display.png differ
diff --git a/index.html b/index.html
index a9036327b2..7c4771e047 100644
--- a/index.html
+++ b/index.html
@@ -454,8 +454,8 @@
 
 
   <li class="md-nav__item">
-    <a href="cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/install/install-cave/index.html b/install/install-cave/index.html
index f2ba8dfc9e..d96cc3aff2 100644
--- a/install/install-cave/index.html
+++ b/install/install-cave/index.html
@@ -399,8 +399,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../../cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../../cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/install/install-edex/index.html b/install/install-edex/index.html
index de066a15cd..4376572d2b 100644
--- a/install/install-edex/index.html
+++ b/install/install-edex/index.html
@@ -440,8 +440,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../../cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../../cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
@@ -1264,11 +1264,14 @@ service qpidd start
 service edex_camel start
 </code></pre>
 <p>The fifth service, <strong>edex_ldm</strong>, does <strong>not run at boot</strong> to prevent filling up disk space if EDEX is not running. </p>
-<pre><code>service edex_ldm start
+<pre><code>ldmadmin start
 </code></pre>
 <p>To start <em>all services except the LDM</em> (good for troubleshooting):</p>
 <pre><code>edex start base
 </code></pre>
+<p>To restart EDEX</p>
+<pre><code>edex restart
+</code></pre>
 <hr />
 <h2 id="directories-to-know">Directories to know<a class="headerlink" href="#directories-to-know" title="Permanent link"></a></h2>
 <ul>
diff --git a/install/start-edex/index.html b/install/start-edex/index.html
index d2c6c59489..ba99214878 100644
--- a/install/start-edex/index.html
+++ b/install/start-edex/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../../cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../../cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/mkdocs/search_index.json b/mkdocs/search_index.json
index fcf7175e9e..313e777075 100644
--- a/mkdocs/search_index.json
+++ b/mkdocs/search_index.json
@@ -107,7 +107,7 @@
         }, 
         {
             "location": "/install/install-edex/", 
-            "text": "EDEX for Linux\n\uf0c1\n\n\ninstallEDEX.sh \n \n\n\nInstalls to subdirectories in \n/awips2\n\n\n\n\nSystem Requirements\n\n\n\n\n64-bit\n CentOS/RHEL 6 or 7\n\n\n8 CPU\n cores (16 recommended) \n\n\n16GB\n RAM (32+GB recommended for full IDD processing)\n\n\n500GB\n disk space, more if you build a data archive.\n\n\n\n\n\n\nAn \nSSD is an especially good idea\n, mounted to \n/awips2/edex/data/hdf5\n  to contain the decoded data files, or mounted to \n/awips2\n to contain the entire AWIPS software system.\n\n\nEDEX \ncan scale to any system\n, either by adjusting the incoming data feeds, or the resources allocated to each data type, but when selecting a server, \nmore is always better\n.\n\n\n64-bit CentOS/RHEL 6 and 7\n are the only supported Linux operating systems. You may have luck with Fedora Core 12 to 14 and Scientific Linux. EDEX is not developed, tested, or supported on Debian, Ubuntu, SUSE, Solaris, OS X, or Windows.\n\n\n\n\nLinux One-Time Setup\n\uf0c1\n\n\nAll of these command should be run as \nroot\n!\n\n\nUsers and Groups\n\uf0c1\n\n\nCreate user and group awips:fxalpha\n\n\ngroupadd fxalpha \n useradd -G fxalpha awips\n\n\n\nor if the awips account already exists:\n\n\ngroupadd fxalpha \n usermod -G fxalpha awips\n\n\n\n\n\niptables\n\uf0c1\n\n\nConfigure iptables to allow TCP connections on ports 5672, 9581 and 9582\n\n\n\n\n\n\nTo open ports to all connections\n\n\nvi /etc/sysconfig/iptables\n\n*filter\n:INPUT ACCEPT [0:0]\n:FORWARD ACCEPT [0:0]\n:OUTPUT ACCEPT [0:0]\n-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT\n-A INPUT -p icmp -j ACCEPT\n-A INPUT -i lo -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 5672 -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 9581 -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 9582 -j ACCEPT\n-A INPUT -j REJECT --reject-with icmp-host-prohibited\n-A FORWARD -j REJECT --reject-with icmp-host-prohibited\nCOMMIT\n\n\n\n\n\n\n\nTo open ports to specific IP addresses\n\n\nvi /etc/sysconfig/iptables\n\n*filter\n:INPUT DROP [0:0]\n:FORWARD DROP [0:0]\n:OUTPUT ACCEPT [0:0]\n:EXTERNAL - [0:0]\n:EDEX - [0:0]\n-A INPUT -i lo -j ACCEPT\n-A INPUT -p icmp --icmp-type any -j ACCEPT\n-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT\n-A INPUT -s 128.117.140.0/24 -j EDEX\n-A INPUT -s 128.117.156.0/24 -j EDEX\n-A INPUT -j EXTERNAL\n-A EXTERNAL -j REJECT\n-A EDEX -m state --state NEW -p tcp --dport 22 -j ACCEPT\n-A EDEX -m state --state NEW -p tcp --dport 5672 -j ACCEPT\n-A EDEX -m state --state NEW -p tcp --dport 9581 -j ACCEPT\n-A EDEX -m state --state NEW -p tcp --dport 9582 -j ACCEPT\n-A EDEX -j REJECT\nCOMMIT\n\n\n\n\n\n\n\n\n\nIn this example, the IP range \n128.117.140.0/24\n will match all 128.117.140.\n addresses, while \n128.117.156.0/24\n will match 128.117.156.\n.\n\n\n\n\nRestart iptables\n\n\nservice iptables restart\n\n\n\nFor CentOS 7 error \nRedirecting to /bin/systemctl restart  iptables.service\nFailed to restart iptables.service: Unit iptables.service failed to load: No such file or directory.\n\n\nThe solution is:\n\n\nyum install iptables-services\nsystemctl enable iptables\nservice iptables restart\n\n\n\n\n\nDisable SELinux\n\uf0c1\n\n\nvi /etc/sysconfig/selinux\n\n# This file controls the state of SELinux on the system.\n# SELINUX= can take one of these three values:\n#     enforcing - SELinux security policy is enforced.\n#     permissive - SELinux prints warnings instead of enforcing.\n#     disabled - No SELinux policy is loaded.\nSELINUX=disabled\n# SELINUXTYPE= can take one of these two values:\n#     targeted - Targeted processes are protected,\n#     mls - Multi Level Security protection.\nSELINUXTYPE=targeted\n\n\n\n\n\nRead more about selinux at \nredhat.com\n\n\n\n\nreboot if necessary\n, required if iptables was updated.\n\n\n\n\nSSD Mount\n\uf0c1\n\n\nThough a Solid State Drive is not required, it is \nstrongly encouraged\n in order to handle the amount of disk IO for real-time IDD feeds.  \n\n\nThe simplest configuration would be to mount an 500GB+ SSD to \n/awips2\n to contain both the installed software (approx. 20GB) and the real-time data (approx. 150GB per day).\n\n\nThe default \npurge rules\n are configured such that \n/awips2\n does not exceed 450GB. \n/awips2/data_store\n is scoured every hour and should not exceed 50GB. \n\n\nIf you want to increase EDEX data retention you should mount a large disk to \n/awips2/edex/data/hdf5\n since this will be where the archived processed data exists, and any case studies created.\n\n\n    Filesystem      Size  Used Avail Use% Mounted on\n    /dev/sda1        30G  2.5G   26G   9% /\n    tmpfs            28G     0   28G   0% /dev/shm\n    /dev/sdc1       788G   81G  667G  11% /awips2\n    /dev/sdb1       788G   41G  708G  10% /awips2/edex/data/hdf5\n\n\n\n\n\nyum install\n\uf0c1\n\n\nDownload the script \ninstallEDEX.sh\n to setup and run yum to install AWIPS packages:\n\n\nwget http://www.unidata.ucar.edu/software/awips2/installEDEX.sh\nchmod 755 ./installEDEX.sh\n./installEDEX.sh\n\n\n\n\n\nWhat does \ninstallEDEX.sh\n do?\n\n\n\n\nDownloads \nawips2.repo\n or \nel7.repo\n to \n/etc/yum.repos.d/awips2.repo\n\n\nRuns \nyum clean all\n\n\nRuns \nyum groupinstall awips2-server\n\n\n\n\n\n\n\n\nEDEX Setup\n\uf0c1\n\n\nThe command \nedex setup\n attempts to add the domain name of your server. \n\n\n\n\n\n\n/awips2/edex/bin/setup.env\n should contain the fully-qualified domain name, externally resolved, localhost will not work. \n\n\nexport AW_SITE_IDENTIFIER=OAX\nexport EDEX_SERVER=edex-cloud.unidata.ucar.edu\n\n\n\n\n\n\n\n/awips2/ldm/etc/ldmd.conf\n contains the upstream server (default \nidd.unidata.ucar.edu\n, which requires you connect form a .edu domain). This file also contains the \nedexBridge\n hostname (default \nlocalhost\n). \n\n\nEXEC    \"pqact -e\"\nEXEC    \"edexBridge -s localhost\"\n\n\n\n\n\n\n\n/etc/security/limits.conf\n defines the number of user processes and files (this step is automatically performed by \ninstallEDEX.sh\n). Without these definitions, Qpid is known to crash during periods of high ingest.\n\n\nawips soft nproc 65536\nawips soft nofile 65536\n\n\n\n\n\n\n\n\n\nLDM\n\uf0c1\n\n\nEDEX installs its own version of the LDM to the directory \n/awips2/ldm\n.  As with a the default LDM configuration, two files are used to control what IDD feeds are ingested:\n\n\n\n\n\n\n/awips2/ldm/etc/ldmd.conf\n - specifies an upstream LDM server to request data from, and what feeds to request:\n\n\nREQUEST NEXRAD3 \"./p(DHR|DPR|DSP|DTA|DAA|DVL|EET|HHC|N0Q|N0S|N0U|OHA|NVW|NTV|NST).\" idd.unidata.ucar.edu\nREQUEST FNEXRAD|IDS|DDPLUS|UNIWISC \".*\" idd.unidata.ucar.edu\nREQUEST NGRID \".*\" idd.unidata.ucar.edu\nREQUEST NOTHER \"^TIP... KNES.*\" idd.unidata.ucar.edu\n\n\n\n\n\nread more about ldmd.conf in the LDM User Manual\n\n\n\n\n\n\n\n\n/awips2/ldm/etc/pqact.conf\n - specifies the WMO headers and file pattern actions to request:\n\n\n# Redbook graphics\nANY     ^([PQ][A-Z0-9]{3,5}) (....) (..)(..)(..) !redbook [^/]*/([^/]*)/([^/]*)/([^/]*)/([0-9]{8})\n        FILE    -overwrite -close -edex /awips2/data_store/redbook/\\8/\\4\\5Z_\\8_\\7_\\6-\\1_\\2_(seq).rb.%Y%m%d%H\n# NOAAPORT GINI images\nNIMAGE  ^(sat[^/]*)/ch[0-9]/([^/]*)/([^/]*)/([^ ]*) ([^/]*)/([^/]*)/([^/]*)/ (T[^ ]*) ([^ ]*) (..)(..)(..)\n        FILE    -overwrite -close -edex /awips2/data_store/sat/\\(11)\\(12)Z_\\3_\\7_\\6-\\8_\\9_(seq).satz.%Y%m%d%H\n\n\n\n\n\nread more about pqact.conf in the LDM User Manual\n\n\n\n\n\n\nsee available AWIPS LDM feeds\n\n\n\n\n\n\n\n\n\n\nStart and Stop\n\uf0c1\n\n\nto start all EDEX services, including the LDM:\n\n\nedex start\n\nStarting EDEX PostgreSQL:                                  [  OK  ]\nStarting httpd:                                            [  OK  ]\nStarting QPID                                              [  OK  ]\nStarting EDEX Camel (request): \nStarting EDEX Camel (ingest): \nStarting EDEX Camel (ingestGrib): \nStarting AWIPS LDM:The product-queue is OK.\n\n\n\nto stop:\n\n\nedex stop\n\nStopping EDEX Camel (request): \nStopping EDEX Camel (ingest): \nStopping EDEX Camel (ingestGrib): \nStopping QPID                                              [  OK  ]\nStopping httpd:                                            [  OK  ]\nStopping EDEX PostgreSQL:                                  [  OK  ]\nStopping AWIPS LDM:Stopping the LDM server...\n\n\n\nTo manually start, stop, and restart:\n\n\nservice edex_postgres start\nservice httpd-pypies start\nservice qpidd start\nservice edex_camel start\n\n\n\nThe fifth service, \nedex_ldm\n, does \nnot run at boot\n to prevent filling up disk space if EDEX is not running. \n\n\nservice edex_ldm start\n\n\n\nTo start \nall services except the LDM\n (good for troubleshooting):\n\n\nedex start base\n\n\n\n\n\nDirectories to know\n\uf0c1\n\n\n\n\n/awips2\n - Contains all of the installed AWIPS software. \n\n\n/awips2/edex/logs\n - EDEX logs.\n\n\n/awips2/httpd_pypies/var/log/httpd\n - httpd-pypies logs.\n\n\n/awips2/data/pg_log\n - PostgreSQL logs.\n\n\n/awips2/qpid/log\n - Qpid logs.\n\n\n/awips2/edex/data/hdf5\n - HDF5 data store. \n\n\n/awips2/edex/data/utility\n - Localization store and configuration files. \n\n\n/awips2/ldm/etc\n - Location of \nldmd.conf\n and \npqact.conf\n\n\n/awips2/ldm/logs\n - LDM logs.\n\n\n/awips2/data_store\n - Raw data store.\n\n\n/awips2/data_store/ingest\n - Manual data ingest endpoint.", 
+            "text": "EDEX for Linux\n\uf0c1\n\n\ninstallEDEX.sh \n \n\n\nInstalls to subdirectories in \n/awips2\n\n\n\n\nSystem Requirements\n\n\n\n\n64-bit\n CentOS/RHEL 6 or 7\n\n\n8 CPU\n cores (16 recommended) \n\n\n16GB\n RAM (32+GB recommended for full IDD processing)\n\n\n500GB\n disk space, more if you build a data archive.\n\n\n\n\n\n\nAn \nSSD is an especially good idea\n, mounted to \n/awips2/edex/data/hdf5\n  to contain the decoded data files, or mounted to \n/awips2\n to contain the entire AWIPS software system.\n\n\nEDEX \ncan scale to any system\n, either by adjusting the incoming data feeds, or the resources allocated to each data type, but when selecting a server, \nmore is always better\n.\n\n\n64-bit CentOS/RHEL 6 and 7\n are the only supported Linux operating systems. You may have luck with Fedora Core 12 to 14 and Scientific Linux. EDEX is not developed, tested, or supported on Debian, Ubuntu, SUSE, Solaris, OS X, or Windows.\n\n\n\n\nLinux One-Time Setup\n\uf0c1\n\n\nAll of these command should be run as \nroot\n!\n\n\nUsers and Groups\n\uf0c1\n\n\nCreate user and group awips:fxalpha\n\n\ngroupadd fxalpha \n useradd -G fxalpha awips\n\n\n\nor if the awips account already exists:\n\n\ngroupadd fxalpha \n usermod -G fxalpha awips\n\n\n\n\n\niptables\n\uf0c1\n\n\nConfigure iptables to allow TCP connections on ports 5672, 9581 and 9582\n\n\n\n\n\n\nTo open ports to all connections\n\n\nvi /etc/sysconfig/iptables\n\n*filter\n:INPUT ACCEPT [0:0]\n:FORWARD ACCEPT [0:0]\n:OUTPUT ACCEPT [0:0]\n-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT\n-A INPUT -p icmp -j ACCEPT\n-A INPUT -i lo -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 5672 -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 9581 -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 9582 -j ACCEPT\n-A INPUT -j REJECT --reject-with icmp-host-prohibited\n-A FORWARD -j REJECT --reject-with icmp-host-prohibited\nCOMMIT\n\n\n\n\n\n\n\nTo open ports to specific IP addresses\n\n\nvi /etc/sysconfig/iptables\n\n*filter\n:INPUT DROP [0:0]\n:FORWARD DROP [0:0]\n:OUTPUT ACCEPT [0:0]\n:EXTERNAL - [0:0]\n:EDEX - [0:0]\n-A INPUT -i lo -j ACCEPT\n-A INPUT -p icmp --icmp-type any -j ACCEPT\n-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT\n-A INPUT -s 128.117.140.0/24 -j EDEX\n-A INPUT -s 128.117.156.0/24 -j EDEX\n-A INPUT -j EXTERNAL\n-A EXTERNAL -j REJECT\n-A EDEX -m state --state NEW -p tcp --dport 22 -j ACCEPT\n-A EDEX -m state --state NEW -p tcp --dport 5672 -j ACCEPT\n-A EDEX -m state --state NEW -p tcp --dport 9581 -j ACCEPT\n-A EDEX -m state --state NEW -p tcp --dport 9582 -j ACCEPT\n-A EDEX -j REJECT\nCOMMIT\n\n\n\n\n\n\n\n\n\nIn this example, the IP range \n128.117.140.0/24\n will match all 128.117.140.\n addresses, while \n128.117.156.0/24\n will match 128.117.156.\n.\n\n\n\n\nRestart iptables\n\n\nservice iptables restart\n\n\n\nFor CentOS 7 error \nRedirecting to /bin/systemctl restart  iptables.service\nFailed to restart iptables.service: Unit iptables.service failed to load: No such file or directory.\n\n\nThe solution is:\n\n\nyum install iptables-services\nsystemctl enable iptables\nservice iptables restart\n\n\n\n\n\nDisable SELinux\n\uf0c1\n\n\nvi /etc/sysconfig/selinux\n\n# This file controls the state of SELinux on the system.\n# SELINUX= can take one of these three values:\n#     enforcing - SELinux security policy is enforced.\n#     permissive - SELinux prints warnings instead of enforcing.\n#     disabled - No SELinux policy is loaded.\nSELINUX=disabled\n# SELINUXTYPE= can take one of these two values:\n#     targeted - Targeted processes are protected,\n#     mls - Multi Level Security protection.\nSELINUXTYPE=targeted\n\n\n\n\n\nRead more about selinux at \nredhat.com\n\n\n\n\nreboot if necessary\n, required if iptables was updated.\n\n\n\n\nSSD Mount\n\uf0c1\n\n\nThough a Solid State Drive is not required, it is \nstrongly encouraged\n in order to handle the amount of disk IO for real-time IDD feeds.  \n\n\nThe simplest configuration would be to mount an 500GB+ SSD to \n/awips2\n to contain both the installed software (approx. 20GB) and the real-time data (approx. 150GB per day).\n\n\nThe default \npurge rules\n are configured such that \n/awips2\n does not exceed 450GB. \n/awips2/data_store\n is scoured every hour and should not exceed 50GB. \n\n\nIf you want to increase EDEX data retention you should mount a large disk to \n/awips2/edex/data/hdf5\n since this will be where the archived processed data exists, and any case studies created.\n\n\n    Filesystem      Size  Used Avail Use% Mounted on\n    /dev/sda1        30G  2.5G   26G   9% /\n    tmpfs            28G     0   28G   0% /dev/shm\n    /dev/sdc1       788G   81G  667G  11% /awips2\n    /dev/sdb1       788G   41G  708G  10% /awips2/edex/data/hdf5\n\n\n\n\n\nyum install\n\uf0c1\n\n\nDownload the script \ninstallEDEX.sh\n to setup and run yum to install AWIPS packages:\n\n\nwget http://www.unidata.ucar.edu/software/awips2/installEDEX.sh\nchmod 755 ./installEDEX.sh\n./installEDEX.sh\n\n\n\n\n\nWhat does \ninstallEDEX.sh\n do?\n\n\n\n\nDownloads \nawips2.repo\n or \nel7.repo\n to \n/etc/yum.repos.d/awips2.repo\n\n\nRuns \nyum clean all\n\n\nRuns \nyum groupinstall awips2-server\n\n\n\n\n\n\n\n\nEDEX Setup\n\uf0c1\n\n\nThe command \nedex setup\n attempts to add the domain name of your server. \n\n\n\n\n\n\n/awips2/edex/bin/setup.env\n should contain the fully-qualified domain name, externally resolved, localhost will not work. \n\n\nexport AW_SITE_IDENTIFIER=OAX\nexport EDEX_SERVER=edex-cloud.unidata.ucar.edu\n\n\n\n\n\n\n\n/awips2/ldm/etc/ldmd.conf\n contains the upstream server (default \nidd.unidata.ucar.edu\n, which requires you connect form a .edu domain). This file also contains the \nedexBridge\n hostname (default \nlocalhost\n). \n\n\nEXEC    \"pqact -e\"\nEXEC    \"edexBridge -s localhost\"\n\n\n\n\n\n\n\n/etc/security/limits.conf\n defines the number of user processes and files (this step is automatically performed by \ninstallEDEX.sh\n). Without these definitions, Qpid is known to crash during periods of high ingest.\n\n\nawips soft nproc 65536\nawips soft nofile 65536\n\n\n\n\n\n\n\n\n\nLDM\n\uf0c1\n\n\nEDEX installs its own version of the LDM to the directory \n/awips2/ldm\n.  As with a the default LDM configuration, two files are used to control what IDD feeds are ingested:\n\n\n\n\n\n\n/awips2/ldm/etc/ldmd.conf\n - specifies an upstream LDM server to request data from, and what feeds to request:\n\n\nREQUEST NEXRAD3 \"./p(DHR|DPR|DSP|DTA|DAA|DVL|EET|HHC|N0Q|N0S|N0U|OHA|NVW|NTV|NST).\" idd.unidata.ucar.edu\nREQUEST FNEXRAD|IDS|DDPLUS|UNIWISC \".*\" idd.unidata.ucar.edu\nREQUEST NGRID \".*\" idd.unidata.ucar.edu\nREQUEST NOTHER \"^TIP... KNES.*\" idd.unidata.ucar.edu\n\n\n\n\n\nread more about ldmd.conf in the LDM User Manual\n\n\n\n\n\n\n\n\n/awips2/ldm/etc/pqact.conf\n - specifies the WMO headers and file pattern actions to request:\n\n\n# Redbook graphics\nANY     ^([PQ][A-Z0-9]{3,5}) (....) (..)(..)(..) !redbook [^/]*/([^/]*)/([^/]*)/([^/]*)/([0-9]{8})\n        FILE    -overwrite -close -edex /awips2/data_store/redbook/\\8/\\4\\5Z_\\8_\\7_\\6-\\1_\\2_(seq).rb.%Y%m%d%H\n# NOAAPORT GINI images\nNIMAGE  ^(sat[^/]*)/ch[0-9]/([^/]*)/([^/]*)/([^ ]*) ([^/]*)/([^/]*)/([^/]*)/ (T[^ ]*) ([^ ]*) (..)(..)(..)\n        FILE    -overwrite -close -edex /awips2/data_store/sat/\\(11)\\(12)Z_\\3_\\7_\\6-\\8_\\9_(seq).satz.%Y%m%d%H\n\n\n\n\n\nread more about pqact.conf in the LDM User Manual\n\n\n\n\n\n\nsee available AWIPS LDM feeds\n\n\n\n\n\n\n\n\n\n\nStart and Stop\n\uf0c1\n\n\nto start all EDEX services, including the LDM:\n\n\nedex start\n\nStarting EDEX PostgreSQL:                                  [  OK  ]\nStarting httpd:                                            [  OK  ]\nStarting QPID                                              [  OK  ]\nStarting EDEX Camel (request): \nStarting EDEX Camel (ingest): \nStarting EDEX Camel (ingestGrib): \nStarting AWIPS LDM:The product-queue is OK.\n\n\n\nto stop:\n\n\nedex stop\n\nStopping EDEX Camel (request): \nStopping EDEX Camel (ingest): \nStopping EDEX Camel (ingestGrib): \nStopping QPID                                              [  OK  ]\nStopping httpd:                                            [  OK  ]\nStopping EDEX PostgreSQL:                                  [  OK  ]\nStopping AWIPS LDM:Stopping the LDM server...\n\n\n\nTo manually start, stop, and restart:\n\n\nservice edex_postgres start\nservice httpd-pypies start\nservice qpidd start\nservice edex_camel start\n\n\n\nThe fifth service, \nedex_ldm\n, does \nnot run at boot\n to prevent filling up disk space if EDEX is not running. \n\n\nldmadmin start\n\n\n\nTo start \nall services except the LDM\n (good for troubleshooting):\n\n\nedex start base\n\n\n\nTo restart EDEX\n\n\nedex restart\n\n\n\n\n\nDirectories to know\n\uf0c1\n\n\n\n\n/awips2\n - Contains all of the installed AWIPS software. \n\n\n/awips2/edex/logs\n - EDEX logs.\n\n\n/awips2/httpd_pypies/var/log/httpd\n - httpd-pypies logs.\n\n\n/awips2/data/pg_log\n - PostgreSQL logs.\n\n\n/awips2/qpid/log\n - Qpid logs.\n\n\n/awips2/edex/data/hdf5\n - HDF5 data store. \n\n\n/awips2/edex/data/utility\n - Localization store and configuration files. \n\n\n/awips2/ldm/etc\n - Location of \nldmd.conf\n and \npqact.conf\n\n\n/awips2/ldm/logs\n - LDM logs.\n\n\n/awips2/data_store\n - Raw data store.\n\n\n/awips2/data_store/ingest\n - Manual data ingest endpoint.", 
             "title": "Install EDEX"
         }, 
         {
@@ -157,7 +157,7 @@
         }, 
         {
             "location": "/install/install-edex/#start-and-stop", 
-            "text": "to start all EDEX services, including the LDM:  edex start\n\nStarting EDEX PostgreSQL:                                  [  OK  ]\nStarting httpd:                                            [  OK  ]\nStarting QPID                                              [  OK  ]\nStarting EDEX Camel (request): \nStarting EDEX Camel (ingest): \nStarting EDEX Camel (ingestGrib): \nStarting AWIPS LDM:The product-queue is OK.  to stop:  edex stop\n\nStopping EDEX Camel (request): \nStopping EDEX Camel (ingest): \nStopping EDEX Camel (ingestGrib): \nStopping QPID                                              [  OK  ]\nStopping httpd:                                            [  OK  ]\nStopping EDEX PostgreSQL:                                  [  OK  ]\nStopping AWIPS LDM:Stopping the LDM server...  To manually start, stop, and restart:  service edex_postgres start\nservice httpd-pypies start\nservice qpidd start\nservice edex_camel start  The fifth service,  edex_ldm , does  not run at boot  to prevent filling up disk space if EDEX is not running.   service edex_ldm start  To start  all services except the LDM  (good for troubleshooting):  edex start base", 
+            "text": "to start all EDEX services, including the LDM:  edex start\n\nStarting EDEX PostgreSQL:                                  [  OK  ]\nStarting httpd:                                            [  OK  ]\nStarting QPID                                              [  OK  ]\nStarting EDEX Camel (request): \nStarting EDEX Camel (ingest): \nStarting EDEX Camel (ingestGrib): \nStarting AWIPS LDM:The product-queue is OK.  to stop:  edex stop\n\nStopping EDEX Camel (request): \nStopping EDEX Camel (ingest): \nStopping EDEX Camel (ingestGrib): \nStopping QPID                                              [  OK  ]\nStopping httpd:                                            [  OK  ]\nStopping EDEX PostgreSQL:                                  [  OK  ]\nStopping AWIPS LDM:Stopping the LDM server...  To manually start, stop, and restart:  service edex_postgres start\nservice httpd-pypies start\nservice qpidd start\nservice edex_camel start  The fifth service,  edex_ldm , does  not run at boot  to prevent filling up disk space if EDEX is not running.   ldmadmin start  To start  all services except the LDM  (good for troubleshooting):  edex start base  To restart EDEX  edex restart", 
             "title": "Start and Stop"
         }, 
         {
@@ -442,24 +442,39 @@
         }, 
         {
             "location": "/cave/warngen/", 
-            "text": "WarnGEN\n\uf0c1\n\n\nWarnGen is an AWIPS application for issuing short-term, text-based warnings by National Weather Service WFOs.  WarnGen is an operational tool, and is designed to create and issue warning products from CAVE to EDEX.  Unidata AWIPS is \nnon-operational\n, and one of its limitations is that CAVE can not send or issue warning products.  Unidata developers have left the WarnGen tool accessible in CAVE for education and training purposes. \n\n\nLaunching WarnGen\n\uf0c1\n\n\nSelect the WarnGen application from the D2D toolbar button. When WarnGen is started, the storm centroid marker appears and the WarnGen GUI will pop up as a separate window. \n\n\nYou will need to load one or more products (and maps) to observe severe weather (ideal products are radar reflectivity or velocity, or both).\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nIn order to select a feature it must be within your \nEDEX server\n localization coverage (default BOU)\n\n\nGenerate a Storm Motion Vector\n\uf0c1\n\n\n\n\nClick and drag \nDrag Me to Storm\n to the feature you want to track (WarnGen uses a dot to track a single storm and a line to track a line of storms).\n\n\nStep back 3 to 4 frames.\n\n\nDrag the dot to the previous position of the feature you first marked.\n\n\nReview the product loop and make adjustments to ensure the vector is accurate.\n\n\n\n\nAfter determinng the storm motion you will want to redraw the polygon to fit the new storm track. The easiest way to do this task is to use one of the \n\n\nRedrawing a Polygon\n\uf0c1\n\n\nSelect the \nTrack\n button in the \n\"Redraw Box on Screen\"\n section to redraw a default warning polygon oriented along the storm motion track and containing the storm centroid dot for the most recent volume scan. The initial polygon may have unhatched areas that will be removed from the warning due to crossing CWAs or not meeting area thresholds in the county for inclusion. The Warned/Hatched Area button allow you to preview the polygon shape that will be issued, so you can make further edits.\n\n\nMoving Vertex Points\n\uf0c1\n\n\nVertices can be moved by clicking and dragging with the mouse. The warning polygon, including stippling, will update automatically.\n\n\n\n\nWhen reshaping your warning polygon in this manner, the philosophy is to include all areas that are at risk of experiencing severe weather covered by that warning type. Effective polygons account for uncertainty over time and typically widen downstream. There will be a lot of training provided on Storm-Based Warning Fundamentals in RAC and in the workshop, and this lesson is more focused on the basic mechanics.\n\n\nAdd and Remove Vertex Points\n\uf0c1\n\n\nThere will be some occasions where you will want to add vertices to your warning polygon. Most often, these situations will involve line warnings with bowing segments or single storm warnings where you want to account for storm motion uncertainty or multiple threat areas that may have differing storm motions.\n\n\nNew vertices are added to the warning polygon using a context relative menu accessed by selecting the warning polygon line segments with a Right Mouse Button \u201cclick and hold.\u201d In the menu that appears, just select the \u201cadd vertex\u201d option to add a new point to the warning polygon. Make sure, when using this feature, that you select the line segment in the warning where you want to add the additional vertex. After selecting this option, you will see a new vertex linked to the cursor. Just press your Left Mouse Button at the location you desire for the new vertex and the new point is located there. In addition, clicking with the middle mouse button (or scroll wheel) along an edge of the polygon will also place a vertex at that point.\n\n\nVertex points are removed from the warning polygon using the same context relative menu. Instead of selecting a line segment, you select the vertex you wish to remove and then \u201cclick and hold\u201d with the Right Mouse Button. In the menu that appears, select \u201cremove vertex\u201d to remove the point from the warning polygon. Generally speaking, you should always have at least four points in your warning polygon. So, you should only remove a vertex if you are at a point after you have already added one to your warning polygon.\n\n\nRestoring a Polygon\n\uf0c1\n\n\nWhen you are customizing a polygon in WarnGen, speed is critical. Everyone, even veteran warning forecasters, will occasionally draw a warning polygon one way and then realize, prior to sending the warning, that they want to draw the warning boundaries differently. Depending on the complexity of the changes you make to a warning polygon, sometimes it\u2019s faster to just start over from scratch. The easiest way to proceed, especially if you are still comfortable with the storm motion, is to select the \u201cTrack\u201d button from the \u201cRedraw Box on Screen from\u201d section of the WarnGen GUI.\n\n\nText Window\n\uf0c1\n\n\nUsing the customized settings in the WarnGen GUI, WarnGen translates the information into a text product that is displayed in a text window on the Text Display. Initially the AWIPS Header Block window appears, and you will just click Enter to modify the text of the warning. The auto-generated text contains the storm speed and direction, the counties and cities affected by the warning/advisory, the valid times of the product, the warning/advisory body text (including any optional bullets selected in the GUI), and additional code to help our partners to efficiently process and disseminate the warning/advisory. The locked parts of the text are highlighted in blue and most of your text should not need to be edited if you configured your WarnGen window correctly.\n\n\nFor some products like Severe Weather Statements, there are parts of text that must be edited that have wild-card characters around them that need to be removed after modifying the text inside (e.g. !\n WEAKENED.MOVED OUT OF THE WARNED AREA. \n!). When you attempt to send a product, WarnGen will instruct you to modify this text if you have not. Once the text looks ready for submission you click the Send button, and, on a live system, the warning will be transmitted for public broadcast after you press the Go Ahead button on the final WarnGen check. WES-2 Bridge has been implemented in a way that cannot interact with the live AWIPS processes and communications, so warnings issued on the WES-2 Bridge will not be transmitted as live products.\n\n\nNOTE: Edits made to product text in the editor window should be limited to items such as forecaster name/initials, call-to-action text, etc. If changes are warranted for items such as storm motion, warned counties, or Latitude/Longitude points, close the editor window and make changes using the D-2D and WarnGen graphical tools, then recreate the polygon and/or the text.\n\n\n\"Issuing\" a Warning\n\uf0c1\n\n\nWith a tracked storm in WarnGen:\n\n\n\n\nSelect \nCAVE \n New \n Text Workstation\n\n\nSelect the \nTrack\n button to preview the polygon\n\n\nSelect the \nCreate Text\n button.\n\n\nSelect \nEnter\n on the AWIPS Header Block window to enter the text editor. \n\n\nBlue text is locked and uneditable. You should not need to edit most text, and you need to be careful not to make the hazards inconsistent with the locked intensity summary at the bottom of the warning.\n\n\nIf WarnGen has text you need to edit, there will be wildcards around the text, and WarnGen will not let you send the warning until you modify it.\n\n\n\n\n\n\nRead the text of the warning, identify your ETN number after the \u201cSV.W.\u201d (e.g. 0004) at the top of the warning, and make changes to the warning text if WarnGen tells you to.\n\n\nClick the \nSend\n button (will not actually send). Sending warnings on the WES-2 Bridge is safe because it is not connected to the live AWIPS communications route, and the transmission capabilities have been disabled, firewalled, and modified to prevent any risk of warnings going out.  Unidata AWIPS always disables the sending of warnings.", 
-            "title": "WarnGen"
+            "text": "WarnGen is an AWIPS graphics application for creating and issuing warnings as is done by National Weather Service offices.  In the Unidata AWIPS release it is a \nnon-operational\n forecasting tool, meaning it allows users to experiment and simulate with the drawing and text-generation tools, but prevents you from transmitting a generated warning upstream. \n\n\n\n\nIn order to select a feature it must be within your \nCAVE localization\n coverage (load \nMaps\n \n \nCounty Warning Areas\n to see coverages)\n\n\n\n\nSteps involved in using WarnGen in Unidata AWIPS CAVE 17.1.1\n\n\n\n\nLoad NEXRAD Display from the Radar menu.\n\n\nChoose a WFO site with active severe weather (LKZ is used in the video).\n\n\nRe-localize to this site in the CAVE \n Preferences \n Localization menu.\n\n\nLoad NEXRAD Display again and select a WSR-88D site to load a 2-panel display of 0.5 degree Reflectivity (N0Q) and Velocity (N0U).\n\n\nClick the WarnGen toolbar button or load from Tools \n WarnGen.\n\n\nDrag the storm marker to the center of a storm feature.\n\n\nStep through frames back and forth and adjust the marker to match the trajectory of the storm feature.\n\n\nFrom the WarnGen dialog select the type of warning to generate, the time range, the basis of the warning, and any threats to add (wind, hail, etc). \n\n\nClick \"Create Text\" at the bottom of the WarnGen dialog to generate a text warning product in a new window.\n\n\nClick \"Reset\" at the top of the WarnGen dialog to reset the storm marker at any time.\n\n\nSelect \"Line of Storms\" to enable a two-pointed vector which is to be positioned parallel to a storm line.\n\n\n\n\n\n\n\n\n\nLoad NEXRAD level 3 display\n\uf0c1\n\n\nSelect the menu \nRadar\n \n \nNEXRAD Display\n and note coverage areas of current severe weather.  We choose a WFO ID that contains some active severe weather (KLZK Little Rock, Arkansas, in this example).\n\n\nSelect SITE Localization\n\uf0c1\n\n\nOpen \nCAVE\n \n \nPreferences\n \n \nLocalization\n, select the WFO ID (KLZK) for the coverage area you want to use, followed by \nApply\n and then \nRestart\n.\n\n\nSelect the nearest WSR-88D location\n\uf0c1\n\n\nClick on any NEXRAD Display station to load a two-pane Reflectivity/Velocity view.\n\n\nLaunch WarnGen\n\uf0c1\n\n\nSelect \nWarnGen\n from the D2D Toolbar or from the \nTools\n menu.  When started, the storm centroid marker appears and the WarnGen GUI will pop up as a separate window. \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nGenerate a Storm Motion Vector\n\uf0c1\n\n\n\n\nClick and drag \nDrag Me to Storm\n to the feature you want to track (WarnGen uses a dot to track a single storm and a line to track a line of storms).\n\n\nStep back 3 to 4 frames.\n\n\nDrag the dot to the previous position of the feature you first marked.\n\n\nReview the product loop and make adjustments to ensure the vector is accurate.\n\n\n\n\nRestart\n\uf0c1\n\n\nClick the \nReset\n button to clear all current polygons and vectors and reset the storm centroid marker.\n\n\nRedrawing a Polygon\n\uf0c1\n\n\nSelect the \nTrack\n button in the \n\"Redraw Box on Screen\"\n section to redraw a default warning polygon oriented along the storm motion track and containing the storm centroid dot for the most recent volume scan. The initial polygon may have unhatched areas that will be removed from the warning due to crossing CWAs or not meeting area thresholds in the county for inclusion. The Warned/Hatched Area button allow you to preview the polygon shape that will be issued, so you can make further edits.\n\n\nMoving Vertex Points\n\uf0c1\n\n\nVertices can be moved by clicking and dragging with the mouse. The warning polygon, including stippling, will update automatically.\n\n\n\n\nWhen reshaping your warning polygon in this manner, the philosophy is to include all areas that are at risk of experiencing severe weather covered by that warning type. Effective polygons account for uncertainty over time and typically widen downstream. There will be a lot of training provided on Storm-Based Warning Fundamentals in RAC and in the workshop, and this lesson is more focused on the basic mechanics.\n\n\nAdd and Remove Vertex Points\n\uf0c1\n\n\nThere will be some occasions where you will want to add vertices to your warning polygon. Most often, these situations will involve line warnings with bowing segments or single storm warnings where you want to account for storm motion uncertainty or multiple threat areas that may have differing storm motions.\n\n\nNew vertices are added to the warning polygon using a context relative menu accessed by selecting the warning polygon line segments with a \nRight Mouse Button \"click and hold\"\n. \n\n\n\n\nHold right-click and select \nadd vertex\n.\n\n\nClick the left mouse button at the location you desire for the new vertex and the point is created there.\n\n\nClicking the middle mouse button (or scroll wheel) along an edge of the polygon will also place a vertex at that point.\n\n\n\n\nVertex points are removed from the warning polygon using the same context relative menu. Instead of selecting a line segment, you select the vertex you wish to remove and then \nclick and hold\n with right mouse button.  Hold right-click and select \nremove vertex\n. \n\n\nRestoring a Polygon\n\uf0c1\n\n\nWhen you are customizing a polygon in WarnGen, speed is critical. Everyone, even veteran warning forecasters, will occasionally draw a warning polygon one way and then realize, prior to sending the warning, that they want to draw the warning boundaries differently. Depending on the complexity of the changes you make to a warning polygon, sometimes it\u2019s faster to just start over from scratch. The easiest way to proceed, especially if you are still comfortable with the storm motion, is to select the \u201cTrack\u201d button from the \u201cRedraw Box on Screen from\u201d section of the WarnGen GUI.\n\n\nText Window\n\uf0c1\n\n\nUsing the customized settings in the WarnGen GUI, WarnGen translates the information into a text product that is displayed in a text window on the Text Display. Initially the AWIPS Header Block window appears, and you will just click Enter to modify the text of the warning. The auto-generated text contains the storm speed and direction, the counties and cities affected by the warning/advisory, the valid times of the product, the warning/advisory body text (including any optional bullets selected in the GUI), and additional code to help our partners to efficiently process and disseminate the warning/advisory. The locked parts of the text are highlighted in blue and most of your text should not need to be edited if you configured your WarnGen window correctly.\n\n\nFor some products like Severe Weather Statements, there are parts of text that must be edited that have wild-card characters around them that need to be removed after modifying the text inside (e.g. !\n WEAKENED.MOVED OUT OF THE WARNED AREA. \n!). When you attempt to send a product, WarnGen will instruct you to modify this text if you have not. Once the text looks ready for submission you click the Send button, and, on a live system, the warning will be transmitted for public broadcast after you press the Go Ahead button on the final WarnGen check. WES-2 Bridge has been implemented in a way that cannot interact with the live AWIPS processes and communications, so warnings issued on the WES-2 Bridge will not be transmitted as live products.\n\n\nNOTE: Edits made to product text in the editor window should be limited to items such as forecaster name/initials, call-to-action text, etc. If changes are warranted for items such as storm motion, warned counties, or Latitude/Longitude points, close the editor window and make changes using the D-2D and WarnGen graphical tools, then recreate the polygon and/or the text.\n\n\n\"Issuing\" a Warning\n\uf0c1\n\n\nWith a tracked storm in WarnGen:\n\n\n\n\nSelect \nCAVE \n New \n Text Workstation\n\n\nSelect the \nTrack\n button to preview the polygon\n\n\nSelect the \nCreate Text\n button.\n\n\nSelect \nEnter\n on the AWIPS Header Block window to enter the text editor. \n\n\nBlue text is locked and uneditable. You should not need to edit most text, and you need to be careful not to make the hazards inconsistent with the locked intensity summary at the bottom of the warning.\n\n\nIf WarnGen has text you need to edit, there will be wildcards around the text, and WarnGen will not let you send the warning until you modify it.\n\n\n\n\n\n\nRead the text of the warning, identify your ETN number after the \u201cSV.W.\u201d (e.g. 0004) at the top of the warning, and make changes to the warning text if WarnGen tells you to.\n\n\nClick the \nSend\n button (will not actually send). Sending warnings on the WES-2 Bridge is safe because it is not connected to the live AWIPS communications route, and the transmission capabilities have been disabled, firewalled, and modified to prevent any risk of warnings going out.  Unidata AWIPS always disables the sending of warnings.", 
+            "title": "WarnGen Walkthrough"
         }, 
         {
-            "location": "/cave/warngen/#warngen", 
-            "text": "WarnGen is an AWIPS application for issuing short-term, text-based warnings by National Weather Service WFOs.  WarnGen is an operational tool, and is designed to create and issue warning products from CAVE to EDEX.  Unidata AWIPS is  non-operational , and one of its limitations is that CAVE can not send or issue warning products.  Unidata developers have left the WarnGen tool accessible in CAVE for education and training purposes.", 
-            "title": "WarnGEN"
+            "location": "/cave/warngen/#load-nexrad-level-3-display", 
+            "text": "Select the menu  Radar     NEXRAD Display  and note coverage areas of current severe weather.  We choose a WFO ID that contains some active severe weather (KLZK Little Rock, Arkansas, in this example).", 
+            "title": "Load NEXRAD level 3 display"
         }, 
         {
-            "location": "/cave/warngen/#launching-warngen", 
-            "text": "Select the WarnGen application from the D2D toolbar button. When WarnGen is started, the storm centroid marker appears and the WarnGen GUI will pop up as a separate window.   You will need to load one or more products (and maps) to observe severe weather (ideal products are radar reflectivity or velocity, or both).                In order to select a feature it must be within your  EDEX server  localization coverage (default BOU)", 
-            "title": "Launching WarnGen"
+            "location": "/cave/warngen/#select-site-localization", 
+            "text": "Open  CAVE     Preferences     Localization , select the WFO ID (KLZK) for the coverage area you want to use, followed by  Apply  and then  Restart .", 
+            "title": "Select SITE Localization"
+        }, 
+        {
+            "location": "/cave/warngen/#select-the-nearest-wsr-88d-location", 
+            "text": "Click on any NEXRAD Display station to load a two-pane Reflectivity/Velocity view.", 
+            "title": "Select the nearest WSR-88D location"
+        }, 
+        {
+            "location": "/cave/warngen/#launch-warngen", 
+            "text": "Select  WarnGen  from the D2D Toolbar or from the  Tools  menu.  When started, the storm centroid marker appears and the WarnGen GUI will pop up as a separate window.", 
+            "title": "Launch WarnGen"
         }, 
         {
             "location": "/cave/warngen/#generate-a-storm-motion-vector", 
-            "text": "Click and drag  Drag Me to Storm  to the feature you want to track (WarnGen uses a dot to track a single storm and a line to track a line of storms).  Step back 3 to 4 frames.  Drag the dot to the previous position of the feature you first marked.  Review the product loop and make adjustments to ensure the vector is accurate.   After determinng the storm motion you will want to redraw the polygon to fit the new storm track. The easiest way to do this task is to use one of the", 
+            "text": "Click and drag  Drag Me to Storm  to the feature you want to track (WarnGen uses a dot to track a single storm and a line to track a line of storms).  Step back 3 to 4 frames.  Drag the dot to the previous position of the feature you first marked.  Review the product loop and make adjustments to ensure the vector is accurate.", 
             "title": "Generate a Storm Motion Vector"
         }, 
+        {
+            "location": "/cave/warngen/#restart", 
+            "text": "Click the  Reset  button to clear all current polygons and vectors and reset the storm centroid marker.", 
+            "title": "Restart"
+        }, 
         {
             "location": "/cave/warngen/#redrawing-a-polygon", 
             "text": "Select the  Track  button in the  \"Redraw Box on Screen\"  section to redraw a default warning polygon oriented along the storm motion track and containing the storm centroid dot for the most recent volume scan. The initial polygon may have unhatched areas that will be removed from the warning due to crossing CWAs or not meeting area thresholds in the county for inclusion. The Warned/Hatched Area button allow you to preview the polygon shape that will be issued, so you can make further edits.", 
@@ -472,7 +487,7 @@
         }, 
         {
             "location": "/cave/warngen/#add-and-remove-vertex-points", 
-            "text": "There will be some occasions where you will want to add vertices to your warning polygon. Most often, these situations will involve line warnings with bowing segments or single storm warnings where you want to account for storm motion uncertainty or multiple threat areas that may have differing storm motions.  New vertices are added to the warning polygon using a context relative menu accessed by selecting the warning polygon line segments with a Right Mouse Button \u201cclick and hold.\u201d In the menu that appears, just select the \u201cadd vertex\u201d option to add a new point to the warning polygon. Make sure, when using this feature, that you select the line segment in the warning where you want to add the additional vertex. After selecting this option, you will see a new vertex linked to the cursor. Just press your Left Mouse Button at the location you desire for the new vertex and the new point is located there. In addition, clicking with the middle mouse button (or scroll wheel) along an edge of the polygon will also place a vertex at that point.  Vertex points are removed from the warning polygon using the same context relative menu. Instead of selecting a line segment, you select the vertex you wish to remove and then \u201cclick and hold\u201d with the Right Mouse Button. In the menu that appears, select \u201cremove vertex\u201d to remove the point from the warning polygon. Generally speaking, you should always have at least four points in your warning polygon. So, you should only remove a vertex if you are at a point after you have already added one to your warning polygon.", 
+            "text": "There will be some occasions where you will want to add vertices to your warning polygon. Most often, these situations will involve line warnings with bowing segments or single storm warnings where you want to account for storm motion uncertainty or multiple threat areas that may have differing storm motions.  New vertices are added to the warning polygon using a context relative menu accessed by selecting the warning polygon line segments with a  Right Mouse Button \"click and hold\" .    Hold right-click and select  add vertex .  Click the left mouse button at the location you desire for the new vertex and the point is created there.  Clicking the middle mouse button (or scroll wheel) along an edge of the polygon will also place a vertex at that point.   Vertex points are removed from the warning polygon using the same context relative menu. Instead of selecting a line segment, you select the vertex you wish to remove and then  click and hold  with right mouse button.  Hold right-click and select  remove vertex .", 
             "title": "Add and Remove Vertex Points"
         }, 
         {
@@ -962,12 +977,12 @@
         }, 
         {
             "location": "/edex/data-distribution-files/", 
-            "text": "EDEX alerts the appropriate decoding plug-ins of new data by use of XML files that describe data based on regular expressions.  If the WMO header, or file name, matches a regular expression listed in a distribution XML, then EDEX will put a message into the QPID queue for the decoder which indicates that a piece of data is available. If a piece of data does not match any distribution XML, EDEX will:\n\n\n\n\n\n\nCreate an entry in \n/awips2/edex/logs/edex-ingest-unrecognized-files-yyyymmdd.log\n\n\n\n\n\n\nSkip processing of the unrecognized file.\n\n\n\n\n\n\nDistribution filters are stored in the \nedex_static\n branch of the Localization Store, and a list of available files can be found in the base-level directory.  \n\n\nFor each plug-in, the distribution file is named \ndata-type\n.xml\n; for example, the distribution file for satellite data is \nsatellite.xml\n. The distribution files follow the AWIPS base/site localization pattern: \n\n\n[root@edex]# cd /awips2/edex/data/utility/edex_static/base/distribution\n[root@edex distribution]# ls\nacars.xml         ffg.xml            poessounding.xml\nairep.xml         goessounding.xml   profiler.xml\nairmet.xml        grib.xml           q2.xml\natcf.xml          hpe.xml            radar.xml\naww.xml           idft.xml           recco.xml\nbinlightning.xml  intlsigmet.xml     redbook.xml\nbufrascat.xml     ldadhydro.xml      satellite.mcidas.xml\nbufrhdw.xml       ldadmanual.xml     satellite.xml\nbufrmos.xml       ldadmesonet.xml    sfcobs.xml\nbufrmthdw.xml     ldadprofiler.xml   shef.xml\nbufrncwf.xml      loctables.xml      svrwx.xml\nbufrquikscat.xml  lsr.xml            taf.xml\nbufrsgwhv.xml     mcidas.xml         tcg.xml\nbufrsgwh.xml      modelsounding.xml  tcm.xml\nbufrsigwx.xml     mosaic.xml         tcs.xml\nbufrssha.xml      ncccfp.xml         textlightning.xml\nbufrssmi.xml      ncgrib.xml         text.xml\nbufrua.xml        ncscat.xml         uair.xml\nccfp.xml          nctext.xml         vaa.xml\nconvsigmet.xml    nonconvsigmet.xml  warning.xml\ncwa.xml           obs.xml            wcp.xml\ndhr.xml           pafm.xml\ndpa.xml           pirep.xml\n\n\n\n\n\n\n\nbase files are located in \n/awips2/edex/data/utility/edex_static/base/distribution \n\n\n\n\n\n\nsite override distribution files are located in \n/awips2/edex/data/utility/edex_static/site/XXX/distribution\n, where \nXXX\n is the site identifier.\n\n\n\n\n\n\nNote that site-level files override the base files; as a result, local modifications to distribution files must be made as follows:\n\n\n\n\n\n\nThe base distribution file must be copied from \n/awips2/edex/data/utility/edex_static/base/distribution\n to \n/awips2/edex/data/utility/edex_static/site/XXX/distribution\n\n\n\n\n\n\nThe local modification must be made to the file in \n/awips2/edex/data/utility/edex_static/site/XXX/distribution\n\n\n\n\n\n\nThe basic structure of the distribution file is:\n\n\nrequestPatterns xmlns:ns2=\"group\"\n\n    \nregex\npattern\n/regex\n\n    \nregex\npattern\n/regex\n\n\n/requestPatterns\n\n\n\n\nIn each \n \ntag, \npattern\n is replaced with a regular expression that will match either the filename or the WMO header of the raw data. Only data that matches a pattern in the distribution file will be processed.\n\n\nThe contents of the base version of the radar distribution file:\n\n\n[root@edex]# cd /awips2/edex/data/utility/edex_static/base/distribution/\n[root@edex]# tail -4 radar.xml\n\n\nrequestPatterns xmlns:ns2=\"group\"\n\n    \nregex\n^SDUS[234578]. .*\n/regex\n\n    \nregex\n^RadarServer.*\n/regex\n\n\n/requestPatterns\n\n\n\n\nLooking at the base radar.xml distribution file in the previous example, there are two regular expressions.  The first regular expression matches the standard WMO ID of radar products.   Via the edexBridge the LDM will place a message in the external.dropbox QPID queue, indicating a radar product has arrived.  EDEX will then take the message containing the radar WMO ID and compare it against the regular expressions in radar.xml.  If a match is found, EDEX places a message in the QPID queue Ingest.radar.  The radar decoder will then consume the message and process the radar data accordingly. \n\n\nAdding a REGEX to the Satellite Data Distribution File\n\uf0c1\n\n\nAs a quick example, suppose we have a local data source for satellite imagery that does not have a WMO header; also suppose that the data source writes to files whose names start with \nLOCAL.sat\n.\n\n\nTo add this locally produced satellite data file to the EDEX distribution; perform the following steps.\n\n\n\n\n\n\nCopy the base version of \nsatellite.gini.xml\n from the base distribution directory \n/awips2/edex/data/utility/edex_static/base/distribution\n into the site distribution directory \n/awips2/edex/data/utility/edex_static/site/XXX/distribution\n\n\n\n\n\n\nEdit the site version of \nsatellite.xml\n, adding a new \nregex\n/regex\n tag immediately below the existing regular expression (\nregex\n/regex\n) tag. The contents of the tag will be \nLOCAL.sat\n. The final result will be:\n\n\nrequestPatterns xmlns:ns2=\"group\"\n\n    \nregex\nTI[CGT]... ....\n/regex\n\n    \nregex\n.*NEXRCOMP.*\n/regex\n\n    \nregex\n^LOCAL.sat.*\n/regex\n\n\n/requestPatterns\n\n\n\n\n\n\n\n\nSave the file and exit the editor. EDEX will automatically pick up the new distribution pattern.\n\n\n\n\n\n\nRaw files are written to \n/data_store\n, and a message is sent via QPID to the EDEX distribution service from the LDM. When a regular expression match is found in a data distribution file, the raw data file is placed in a queue for the matching plugin to decode and process. The distribution files are used to match file headers as well as filenames, which is how files dropped into EDEX\u00e2\u20ac\u2122s manual endpoint (\n/awips2/data_store/ingest\n) are processed.\n\n\nEditing an EDEX Data Distribution File\n\uf0c1\n\n\nBecause these files are in the \nedex_static/\n directory, they have to be manually edited using a text editor. You should not edit the base files; rather, you should copy the base version to your site and then edit the site version. The regular expressions in the distribution files need to correspond with the regular expressions in the LDM \npqact.conf\n \nfile.\n\n\nIf patterns exist in \npqact.conf\n but are not in the distribution files, then raw data files will be written to \n/data_store\n but will not be ingested and processed by EDEX. Entries for these non-ingested files would be written to the unrecognized files log in \n/awips/edex/logs\n.\n\n\nExamples\n\uf0c1\n\n\nSurface Obs\n\uf0c1\n\n\n/awips2/edex/data/utility/edex_static/base/distribution/obs.xml\n Processes any file header that starts with \nSA\n or \nSP\n, which should match any WMO header that contains METAR data (e.g.\nSAUS\n, \nSPUS\n, \nSACN\n, \nSAMX\n).\n\n\nrequestPatterns xmlns:ns2=\"group\"\n\n  \nregex\n^S[AP].*\n/regex\n\n\n/requestPatterns\n\n\n\n\nText Data\n\uf0c1\n\n\n/awips2/edex/data/utility/edex_static/base/distribution/text.xml\n Processes lots of WM patterns. The second pattern ^S[A-CEG-Z].* matches any header that starts with \nS\n except for \nSD\nor \nSF\n, so it also matches the \nSA\n and \nSP\n files that the \nobs.xml\n plugin matches. This means that METARs are processed by both plugins simultaneously.\n\n\nrequestPatterns\n\n  \nregex\n^[ACFNRUW][A-Z].*\n/regex\n\n  \nregex\n^S[ACEG-Z].*\n/regex\n\n  \nregex\n^T[BCX].*\n/regex\n\n  \nregex\n^SF[A-OQ-TVZ].*\n/regex\n\n  \nregex\n^SDUS1.*\n/regex\n\n  \nregex\n^SDUS4[1-6].*\n/regex\n\n  \nregex\n^SDUS9[^7].*\n/regex\n\n  \nregex\n^SFU[^S].*\n/regex\n\n  \nregex\n^SFUS4[^1].*\n/regex\n \n  \nregex\n^SFP[^A].*\n/regex\n\n  \nregex\n^SFPA[^4].*\n/regex\n \n  \nregex\n^SFPA4[^1].*\n/regex\n\n  \nregex\n^BMBB91.*\n/regex\n \n  \nregex\n^N.*\n/regex\n\n  \nregex\n^F[EHIJKLMQVWX].*\n/regex\n \n\n/requestPatterns\n\n\n\n\nGrib Data\n\uf0c1\n\n\n/awips2/edex/data/utility/edex_static/base/distribution/grib.xml\n The grib/grid decoder distribution file matches all numerical grids distributed over the IDD NGRID feed by matching WMO header, and from CONDUIT by matching the \n.grib\n file extension.\n\n\nrequestPatterns\n\n    \n!-- Super Set of all possible WMO grib patterns --\n\n    \nregex\n^[EHLMOYZ][A-Z]{3}\\d{2}\n/regex\n\n    \n!-- This to match Unidata CONDUIT products w/o standard headers --\n\n    \nregex\n.*grib.*\n/regex\n\n    \nregex\n^US058.*\n/regex\n\n    \nregex\n^CMC_reg.*\n/regex\n\n\n/requestPatterns\n\n\n\n\nImportant notes about regular expressions:\n\n\n\n\n\n\nAny time a new entry is placed in the \npqact.conf\n file on LDM, a corresponding entry needs to be added to the appropriate Data Distribution file in the data distribution directory, or the data file will be logged to \nedex-ingest-unrecognized-files-YYYYMMDD.log\n\n\n\n\n\n\nAny time an entry is removed from the \npqact.conf\n file, the corresponding entry should be removed from the appropriate Data Distribution file in the data distribution directory.", 
+            "text": "EDEX alerts the appropriate decoding plug-ins of new data by use of XML files that describe data based on regular expressions.  If the WMO header, or file name, matches a regular expression listed in a distribution XML, then EDEX will put a message into the QPID queue for the decoder which indicates that a piece of data is available. If a piece of data does not match any distribution XML, EDEX will:\n\n\n\n\n\n\nCreate an entry in \n/awips2/edex/logs/edex-ingest-unrecognized-files-yyyymmdd.log\n\n\n\n\n\n\nSkip processing of the unrecognized file.\n\n\n\n\n\n\nDistribution filters are stored in the \nedex_static\n branch of the Localization Store, and a list of available files can be found in the base-level directory.  \n\n\nFor each plug-in, the distribution file is named \ndata-type\n.xml\n; for example, the distribution file for satellite data is \nsatellite.xml\n. The distribution files follow the AWIPS base/site localization pattern: \n\n\n[root@edex]# cd /awips2/edex/data/utility/edex_static/base/distribution\n[root@edex distribution]# ls\nacars.xml         ffg.xml            poessounding.xml\nairep.xml         goessounding.xml   profiler.xml\nairmet.xml        grib.xml           q2.xml\natcf.xml          hpe.xml            radar.xml\naww.xml           idft.xml           recco.xml\nbinlightning.xml  intlsigmet.xml     redbook.xml\nbufrascat.xml     ldadhydro.xml      satellite.mcidas.xml\nbufrhdw.xml       ldadmanual.xml     satellite.xml\nbufrmos.xml       ldadmesonet.xml    sfcobs.xml\nbufrmthdw.xml     ldadprofiler.xml   shef.xml\nbufrncwf.xml      loctables.xml      svrwx.xml\nbufrquikscat.xml  lsr.xml            taf.xml\nbufrsgwhv.xml     mcidas.xml         tcg.xml\nbufrsgwh.xml      modelsounding.xml  tcm.xml\nbufrsigwx.xml     mosaic.xml         tcs.xml\nbufrssha.xml      ncccfp.xml         textlightning.xml\nbufrssmi.xml      ncgrib.xml         text.xml\nbufrua.xml        ncscat.xml         uair.xml\nccfp.xml          nctext.xml         vaa.xml\nconvsigmet.xml    nonconvsigmet.xml  warning.xml\ncwa.xml           obs.xml            wcp.xml\ndhr.xml           pafm.xml\ndpa.xml           pirep.xml\n\n\n\n\n\n\n\nbase files are located in \n/awips2/edex/data/utility/edex_static/base/distribution \n\n\n\n\n\n\nsite override distribution files are located in \n/awips2/edex/data/utility/edex_static/site/XXX/distribution\n, where \nXXX\n is the site identifier.\n\n\n\n\n\n\nNote that site-level files override the base files; as a result, local modifications to distribution files must be made as follows:\n\n\n\n\n\n\nThe base distribution file must be copied from \n/awips2/edex/data/utility/edex_static/base/distribution\n to \n/awips2/edex/data/utility/edex_static/site/XXX/distribution\n\n\n\n\n\n\nThe local modification must be made to the file in \n/awips2/edex/data/utility/edex_static/site/XXX/distribution\n\n\n\n\n\n\nThe basic structure of the distribution file is:\n\n\nrequestPatterns xmlns:ns2=\"group\"\n\n    \nregex\npattern\n/regex\n\n    \nregex\npattern\n/regex\n\n\n/requestPatterns\n\n\n\n\nIn each \n \ntag, \npattern\n is replaced with a regular expression that will match either the filename or the WMO header of the raw data. Only data that matches a pattern in the distribution file will be processed.\n\n\nThe contents of the base version of the radar distribution file:\n\n\n[root@edex]# cd /awips2/edex/data/utility/edex_static/base/distribution/\n[root@edex]# tail -4 radar.xml\n\n\nrequestPatterns xmlns:ns2=\"group\"\n\n    \nregex\n^SDUS[234578]. .*\n/regex\n\n    \nregex\n^RadarServer.*\n/regex\n\n\n/requestPatterns\n\n\n\n\nLooking at the base radar.xml distribution file in the previous example, there are two regular expressions.  The first regular expression matches the standard WMO ID of radar products.   Via the edexBridge the LDM will place a message in the external.dropbox QPID queue, indicating a radar product has arrived.  EDEX will then take the message containing the radar WMO ID and compare it against the regular expressions in radar.xml.  If a match is found, EDEX places a message in the QPID queue Ingest.radar.  The radar decoder will then consume the message and process the radar data accordingly. \n\n\nAdding a REGEX to the Satellite Data Distribution File\n\uf0c1\n\n\nAs a quick example, suppose we have a local data source for satellite imagery that does not have a WMO header; also suppose that the data source writes to files whose names start with \nLOCAL.sat\n.\n\n\nTo add this locally produced satellite data file to the EDEX distribution; perform the following steps.\n\n\n\n\n\n\nCopy the base version of \nsatellite.gini.xml\n from the base distribution directory \n/awips2/edex/data/utility/edex_static/base/distribution\n into the site distribution directory \n/awips2/edex/data/utility/edex_static/site/XXX/distribution\n\n\n\n\n\n\nEdit the site version of \nsatellite.xml\n, adding a new \nregex\n/regex\n tag immediately below the existing regular expression (\nregex\n/regex\n) tag. The contents of the tag will be \nLOCAL.sat\n. The final result will be:\n\n\nrequestPatterns xmlns:ns2=\"group\"\n\n    \nregex\nTI[CGT]... ....\n/regex\n\n    \nregex\n.*NEXRCOMP.*\n/regex\n\n    \nregex\n^LOCAL.sat.*\n/regex\n\n\n/requestPatterns\n\n\n\n\n\n\n\n\nSave the file and exit the editor. EDEX will automatically pick up the new distribution pattern.\n\n\n\n\n\n\nRaw files are written to \n/data_store\n, and a message is sent via QPID to the EDEX distribution service from the LDM. When a regular expression match is found in a data distribution file, the raw data file is placed in a queue for the matching plugin to decode and process. The distribution files are used to match file headers as well as filenames, which is how files dropped into EDEX's manual endpoint (\n/awips2/data_store/ingest\n) are processed.\n\n\nEditing an EDEX Data Distribution File\n\uf0c1\n\n\nBecause these files are in the \nedex_static/\n directory, they have to be manually edited using a text editor. You should not edit the base files; rather, you should copy the base version to your site and then edit the site version. The regular expressions in the distribution files need to correspond with the regular expressions in the LDM \npqact.conf\n \nfile.\n\n\nIf patterns exist in \npqact.conf\n but are not in the distribution files, then raw data files will be written to \n/data_store\n but will not be ingested and processed by EDEX. Entries for these non-ingested files would be written to the unrecognized files log in \n/awips/edex/logs\n.\n\n\nExamples\n\uf0c1\n\n\nSurface Obs\n\uf0c1\n\n\n/awips2/edex/data/utility/edex_static/base/distribution/obs.xml\n Processes any file header that starts with \nSA\n or \nSP\n, which should match any WMO header that contains METAR data (e.g.\nSAUS\n, \nSPUS\n, \nSACN\n, \nSAMX\n).\n\n\nrequestPatterns xmlns:ns2=\"group\"\n\n  \nregex\n^S[AP].*\n/regex\n\n\n/requestPatterns\n\n\n\n\nText Data\n\uf0c1\n\n\n/awips2/edex/data/utility/edex_static/base/distribution/text.xml\n Processes lots of WM patterns. The second pattern ^S[A-CEG-Z].* matches any header that starts with \nS\n except for \nSD\nor \nSF\n, so it also matches the \nSA\n and \nSP\n files that the \nobs.xml\n plugin matches. This means that METARs are processed by both plugins simultaneously.\n\n\nrequestPatterns\n\n  \nregex\n^[ACFNRUW][A-Z].*\n/regex\n\n  \nregex\n^S[ACEG-Z].*\n/regex\n\n  \nregex\n^T[BCX].*\n/regex\n\n  \nregex\n^SF[A-OQ-TVZ].*\n/regex\n\n  \nregex\n^SDUS1.*\n/regex\n\n  \nregex\n^SDUS4[1-6].*\n/regex\n\n  \nregex\n^SDUS9[^7].*\n/regex\n\n  \nregex\n^SFU[^S].*\n/regex\n\n  \nregex\n^SFUS4[^1].*\n/regex\n \n  \nregex\n^SFP[^A].*\n/regex\n\n  \nregex\n^SFPA[^4].*\n/regex\n \n  \nregex\n^SFPA4[^1].*\n/regex\n\n  \nregex\n^BMBB91.*\n/regex\n \n  \nregex\n^N.*\n/regex\n\n  \nregex\n^F[EHIJKLMQVWX].*\n/regex\n \n\n/requestPatterns\n\n\n\n\nGrib Data\n\uf0c1\n\n\n/awips2/edex/data/utility/edex_static/base/distribution/grib.xml\n The grib/grid decoder distribution file matches all numerical grids distributed over the IDD NGRID feed by matching WMO header, and from CONDUIT by matching the \n.grib\n file extension.\n\n\nrequestPatterns\n\n    \n!-- Super Set of all possible WMO grib patterns --\n\n    \nregex\n^[EHLMOYZ][A-Z]{3}\\d{2}\n/regex\n\n    \n!-- This to match Unidata CONDUIT products w/o standard headers --\n\n    \nregex\n.*grib.*\n/regex\n\n    \nregex\n^US058.*\n/regex\n\n    \nregex\n^CMC_reg.*\n/regex\n\n\n/requestPatterns\n\n\n\n\nImportant notes about regular expressions:\n\n\n\n\n\n\nAny time a new entry is placed in the \npqact.conf\n file on LDM, a corresponding entry needs to be added to the appropriate Data Distribution file in the data distribution directory, or the data file will be logged to \nedex-ingest-unrecognized-files-YYYYMMDD.log\n\n\n\n\n\n\nAny time an entry is removed from the \npqact.conf\n file, the corresponding entry should be removed from the appropriate Data Distribution file in the data distribution directory.", 
             "title": "Data Distribution Files"
         }, 
         {
             "location": "/edex/data-distribution-files/#adding-a-regex-to-the-satellite-data-distribution-file", 
-            "text": "As a quick example, suppose we have a local data source for satellite imagery that does not have a WMO header; also suppose that the data source writes to files whose names start with  LOCAL.sat .  To add this locally produced satellite data file to the EDEX distribution; perform the following steps.    Copy the base version of  satellite.gini.xml  from the base distribution directory  /awips2/edex/data/utility/edex_static/base/distribution  into the site distribution directory  /awips2/edex/data/utility/edex_static/site/XXX/distribution    Edit the site version of  satellite.xml , adding a new  regex /regex  tag immediately below the existing regular expression ( regex /regex ) tag. The contents of the tag will be  LOCAL.sat . The final result will be:  requestPatterns xmlns:ns2=\"group\" \n     regex TI[CGT]... .... /regex \n     regex .*NEXRCOMP.* /regex \n     regex ^LOCAL.sat.* /regex  /requestPatterns     Save the file and exit the editor. EDEX will automatically pick up the new distribution pattern.    Raw files are written to  /data_store , and a message is sent via QPID to the EDEX distribution service from the LDM. When a regular expression match is found in a data distribution file, the raw data file is placed in a queue for the matching plugin to decode and process. The distribution files are used to match file headers as well as filenames, which is how files dropped into EDEX\u00e2\u20ac\u2122s manual endpoint ( /awips2/data_store/ingest ) are processed.", 
+            "text": "As a quick example, suppose we have a local data source for satellite imagery that does not have a WMO header; also suppose that the data source writes to files whose names start with  LOCAL.sat .  To add this locally produced satellite data file to the EDEX distribution; perform the following steps.    Copy the base version of  satellite.gini.xml  from the base distribution directory  /awips2/edex/data/utility/edex_static/base/distribution  into the site distribution directory  /awips2/edex/data/utility/edex_static/site/XXX/distribution    Edit the site version of  satellite.xml , adding a new  regex /regex  tag immediately below the existing regular expression ( regex /regex ) tag. The contents of the tag will be  LOCAL.sat . The final result will be:  requestPatterns xmlns:ns2=\"group\" \n     regex TI[CGT]... .... /regex \n     regex .*NEXRCOMP.* /regex \n     regex ^LOCAL.sat.* /regex  /requestPatterns     Save the file and exit the editor. EDEX will automatically pick up the new distribution pattern.    Raw files are written to  /data_store , and a message is sent via QPID to the EDEX distribution service from the LDM. When a regular expression match is found in a data distribution file, the raw data file is placed in a queue for the matching plugin to decode and process. The distribution files are used to match file headers as well as filenames, which is how files dropped into EDEX's manual endpoint ( /awips2/data_store/ingest ) are processed.", 
             "title": "Adding a REGEX to the Satellite Data Distribution File"
         }, 
         {
@@ -997,12 +1012,12 @@
         }, 
         {
             "location": "/edex/new-grid/", 
-            "text": "Unrecognized grids can be decoded by EDEX simply by dropping \n*.grib\n or \n*.grib2\n files into \n/awips2/data_store/ingest/\n\n\nTo add support for a new grid, two edits must be made:\n\n\n\n\nGeospatial projection\n must be defined in a \ngrid navigation file\n\n\nGrid name\n, \ncenter\n, \nsubcenter\n, and \nprocess ID\n must be defined in a \nmodel definition file\n.\n\n\n\n\nIngest an Unsupported Grid\n\uf0c1\n\n\n\n\n\n\nDownload an example grib1 file and rename to a \n*.grib\n extension, then copy to the manual ingest point \n/awips2/data_store/ingest/\n \n\n\nwget http://www.unidata.ucar.edu/staff/mjames/14102318_nmm_d01.GrbF00600 -O wrf.grib\n\ncp wrf.grib /awips2/data_store/ingest/\n\n\n\nRemember that the data distribution file (\n/awips2/edex/data/utility/edex_static/base/distribution/grib.xml\n) will match filename which have the \n*.grib\n extension.\n\n\n\n\n\n\nConfirm that the grib file decodes in the grib log file:\n\n\nedex log grib\n\nINFO [Ingest.GribDecode] /awips2/data_store/manual/grib/20141026/14/wrf.grib processed in: 0.1200 (sec) Latency: 21.8080 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/manual/grib/20141026/14/wrf.grib processed in: 0.1180 (sec) Latency: 21.8140 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/manual/grib/20141026/14/wrf.grib processed in: 0.4230 (sec) Latency: 21.8360 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/manual/grib/20141026/14/wrf.grib processed in: 0.2240 (sec) Latency: 21.9140 (sec)\n\n...\n\n\n\n\n\n\n\nCheck that the hdf5 data directory exists for our unnamed grid\n\n\nls -latr /awips2/edex/data/hdf5/grid/GribModel:7:0:89\n\n\n\nThough the grib file has been decoded, it has been given a generic name with its center, subcenter, and process IDs (7, 0, 89, respectively). \n\n\n\n\n\n\nDetermine Grid Projection\n\uf0c1\n\n\nWhen the grid was ingested a record was added to the \ngrid_coverage\n table with its navigation information:\n\n\npsql metadata\n\nmetadata=# select nx,ny,dx,dy,majoraxis,minoraxis,la1,lo1,lov,latin1,latin2 from gridcoverage where id=(select distinct(location_id) from grid_info where datasetid='GribModel:7:0:89');\n nx  | ny  |        dx        |        dy        | majoraxis | minoraxis |       la1        |        lo1        |        lov        |      latin1      |      latin2      \n-----+-----+------------------+------------------+-----------+-----------+------------------+-------------------+-------------------+------------------+------------------\n 201 | 155 | 4.29699993133545 | 4.29699993133545 |   6378160 |   6356775 | 42.2830009460449 | -72.3610000610352 | -67.0770034790039 | 45.3680000305176 | 45.3680000305176\n(1 row)\n\n\n\nCompare with the projection info returned by wgrib on the original file:\n\n\nwgrib -V wrf.grib\n\nrec 799:27785754:date 2014102318 ALBDO kpds5=84 kpds6=1 kpds7=0 levels=(0,0) grid=255 sfc 6hr fcst: bitmap: 736 undef\n  ALBDO=Albedo [%]\n  timerange 0 P1 6 P2 0 TimeU 1  nx 201 ny 155 GDS grid 3 num_in_ave 0 missing 0\n  center 7 subcenter 0 process 89 Table 2 scan: WE:SN winds(grid) \n  Lambert Conf: Lat1 42.283000 Lon1 -72.361000 Lov -67.077000\n      Latin1 45.368000 Latin2 45.368000 LatSP 0.000000 LonSP 0.000000\n      North Pole (201 x 155) Dx 4.297000 Dy 4.297000 scan 64 mode 8\n  min/max data 5 21.9  num bits 8  BDS_Ref 50  DecScale 1 BinScale 0\n\n\n\nNotice that our grib1 file is a \nLambert Conformal\n projection.  We will need these values for the next step. Note that \nthere is a tolerance of +/- 0.1 degrees\n to keep in mind when defining your coverage area.\n\n\nCreate Grid Projection File\n\uf0c1\n\n\nGrid projection files are stored in \n/awips2/edex/data/utility/edex_static/base/grib/grids/\n and there are four grid coverage types available:\n\n\n\n\n\n\nlambertConformalGridCoverage\n example\n\n\nlambertConformalGridCoverage\n\n    \nname\n305\n/name\n\n    \ndescription\nRegional - CONUS (Lambert Conformal)\n/description\n\n    \nla1\n16.322\n/la1\n\n    \nlo1\n-125.955\n/lo1\n\n    \nfirstGridPointCorner\nLowerLeft\n/firstGridPointCorner\n\n    \nnx\n151\n/nx\n\n    \nny\n113\n/ny\n\n    \ndx\n40.63525\n/dx\n\n    \ndy\n40.63525\n/dy\n\n    \nspacingUnit\nkm\n/spacingUnit\n\n    \nminorAxis\n6356775.0\n/minorAxis\n\n    \nmajorAxis\n6378160.0\n/majorAxis\n\n    \nlov\n-95.0\n/lov\n\n    \nlatin1\n25.0\n/latin1\n\n    \nlatin2\n25.0\n/latin2\n\n\n/lambertConformalGridCoverage\n\n\n\n\n\n\n\n\npolarStereoGridCoverage\n example\n\n\npolarStereoGridCoverage\n\n    \nname\n405\n/name\n\n    \ndescription\nSea Ice south 690X710 13km grid\n/description\n\n    \nla1\n-36.866\n/la1\n\n    \nlo1\n139.806\n/lo1\n\n    \nfirstGridPointCorner\nLowerLeft\n/firstGridPointCorner\n\n    \nnx\n690\n/nx\n\n    \nny\n710\n/ny\n\n    \ndx\n12.7\n/dx\n\n    \ndy\n12.7\n/dy\n\n    \nspacingUnit\nkm\n/spacingUnit\n\n    \nminorAxis\n6371229.0\n/minorAxis\n\n    \nmajorAxis\n6371229.0\n/majorAxis\n\n    \nlov\n100.0\n/lov\n\n\n/polarStereoGridCoverage\n\n\n\n\n\n\n\n\nlatLonGridCoverage\n example\n\n\nlatLonGridCoverage\n\n    \nname\n864162002\n/name\n\n    \ndescription\nUKMet HiRes combined - Southern Hemisphere\n        Longitude range 71.25E - 70.416E \n/description\n\n    \nla1\n-89.721\n/la1\n\n    \nlo1\n71.25\n/lo1\n\n    \nfirstGridPointCorner\nLowerLeft\n/firstGridPointCorner\n\n    \nnx\n864\n/nx\n\n    \nny\n162\n/ny\n\n    \ndx\n0.833\n/dx\n\n    \ndy\n0.556\n/dy\n\n    \nspacingUnit\ndegree\n/spacingUnit\n\n    \nla2\n-0.278\n/la2\n\n    \nlo2\n70.416\n/lo2\n\n\n/latLonGridCoverage\n\n\n\n\n\n\n\n\nmercatorGridCoverage\n example\n\n\nmercatorGridCoverage\n\n    \nname\nNBM_PR\n/name\n\n    \ndescription\n National Blend Grid over Puerto Rico - (1.25 km)\n/description\n\n    \nla1\n16.9775\n/la1\n\n    \nlo1\n-68.0278\n/lo1\n\n    \nfirstGridPointCorner\nLowerLeft\n/firstGridPointCorner\n\n    \nnx\n339\n/nx\n\n    \nny\n225\n/ny\n\n    \ndx\n1.25\n/dx\n\n    \ndy\n1.25\n/dy\n\n    \nla2\n19.3750032477232\n/la2\n\n    \nlo2\n-63.984399999999994\n/lo2\n\n    \nlatin\n20\n/latin\n\n    \nspacingUnit\nkm\n/spacingUnit\n\n    \nminorAxis\n6371200\n/minorAxis\n\n    \nmajorAxis\n6371200\n/majorAxis\n\n\n/mercatorGridCoverage\n\n\n\n\n\n\n\n\nCopy an existing file file with the same grid projection type (in this case \nlambertConformalGridCoverage\n) to a new file \nwrf.xml\n\n\ncd /awips2/edex/data/utility/edex_static/base/grib/grids/\ncp RUCIcing.xml wrf.xml\n\n\n\nAnd edit the new \nwrf.xml\n to define the projection values (example provided):\n\n\nvi wrf.xml\n\n\nlambertConformalGridCoverage\n\n    \nname\n201155\n/name\n\n    \ndescription\nRegional - CONUS (Lambert Conformal)\n/description\n\n    \nla1\n42.2830009460449\n/la1\n\n    \nlo1\n-72.3610000610352\n/lo1\n\n    \nfirstGridPointCorner\nLowerLeft\n/firstGridPointCorner\n\n    \nnx\n201\n/nx\n\n    \nny\n155\n/ny\n\n    \ndx\n4.29699993133545\n/dx\n\n    \ndy\n4.29699993133545\n/dy\n\n    \nspacingUnit\nkm\n/spacingUnit\n\n    \nminorAxis\n6356775.0\n/minorAxis\n\n    \nmajorAxis\n6378160.0\n/majorAxis\n\n    \nlov\n-67.0770034790039\n/lov\n\n    \nlatin1\n45.3680000305176\n/latin1\n\n    \nlatin2\n45.3680000305176\n/latin2\n\n\n/lambertConformalGridCoverage\n\n\n\n\n\n\nNotice \nname\n201155\n/name\n defined from the number of grid points (201 x 155). This value will be matched against an entry in our models file (below) to set the name of the model (e.g. WRF).\n\n\n\n\nCreate Model Definition\n\uf0c1\n\n\nModel definition XML files are found in \n/awips2/edex/data/utility/edex_static/base/grid/models/\n. Since our grib1 file has a center ID of 7 (NCEP) we will edit the \ngribModels_NCEP-7.xml\n file.\n\n\ncd /awips2/edex/data/utility/edex_static/base/grib/models/\n\nvi gribModels_NCEP-7.xml\n\n\n\nin \ngribModelSet\n add an entry\n\n\n    \nmodel\n\n        \nname\nWRF\n/name\n\n        \ncenter\n7\n/center\n\n        \nsubcenter\n0\n/subcenter\n\n        \ngrid\n201155\n/grid\n\n        \nprocess\n\n            \nid\n89\n/id\n\n        \n/process\n\n    \n/model\n\n\n\n\nsave the file and restart EDEX for the changes to take effect.\n\n\nsudo service edex_camel restart\n\n\n\nNow copy the \nwrf.grib\n file \nagain\n to \n/awips2/data_store/ingest/\n.  If everything is correct we will not see any persistence errors since the grid is now named \nWRF\n and not \nGribModel:7:0:89\n.\n\n\ncp wrd.grib /awips2/data_store/ingest/\n\nedex log grib\n\n\n\nAfter you have confirmed that the grid was ingested with the given name, you can \nedit the D2D product menus to display the new grid\n.\n\n\nTroubleshooting Grib Ingest\n\uf0c1\n\n\nIf you ingest a piece of data and the parameter appears as unknown in the metadata database, ensure that the correct parameter tables are in place for the center/subcenter.\n\n\nMake sure the latitude and longitude entries in your coverage specification file match those of your ingested raw grib file. There is a tolerance of +/- 0.1 degree to keep in mind when defining your coverage area.\n\n\nIf some of the information is unknown, using a grib utility application such as \nwgrib\n and \nwgrib2\n (not delivered) can be useful in determining the information that must be added to correctly process a new grib file.", 
+            "text": "Unrecognized grids can be decoded by EDEX simply by dropping \n*.grib\n or \n*.grib2\n files into \n/awips2/data_store/ingest/\n\n\nTo add support for a new grid, two edits must be made:\n\n\n\n\nGeospatial projection\n must be defined in a \ngrid navigation file\n\n\nGrid name\n, \ncenter\n, \nsubcenter\n, and \nprocess ID\n must be defined in a \nmodel definition file\n.\n\n\n\n\nIngest an Unsupported Grid\n\uf0c1\n\n\n\n\n\n\nDownload an example grib1 file and rename to a \n*.grib\n extension, then copy to the manual ingest point \n/awips2/data_store/ingest/\n \n\n\nwget http://www.unidata.ucar.edu/staff/mjames/14102318_nmm_d01.GrbF00600 -O wrf.grib\n\ncp wrf.grib /awips2/data_store/ingest/\n\n\n\nRemember that the data distribution file (\n/awips2/edex/data/utility/edex_static/base/distribution/grib.xml\n) will match filename which have the \n*.grib\n extension.\n\n\n\n\n\n\nConfirm that the grib file decodes in the grib log file:\n\n\nedex log grib\n\nINFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.1200 (sec) Latency: 21.8080 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.1180 (sec) Latency: 21.8140 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.4230 (sec) Latency: 21.8360 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.2240 (sec) Latency: 21.9140 (sec)\n\n...\n\n\n\n\n\n\n\nCheck that the hdf5 data directory exists for our unnamed grid\n\n\nls -latr /awips2/edex/data/hdf5/grid/GribModel:7:0:89\n\n\n\nThough the grib file has been decoded, it has been given a generic name with its center, subcenter, and process IDs (7, 0, 89, respectively). \n\n\n\n\n\n\nDetermine Grid Projection\n\uf0c1\n\n\nWhen the grid was ingested a record was added to the \ngrid_coverage\n table with its navigation information:\n\n\npsql metadata\n\nmetadata=# select nx,ny,dx,dy,majoraxis,minoraxis,la1,lo1,lov,latin1,latin2 from gridcoverage where id=(select distinct(location_id) from grid_info where datasetid='GribModel:7:0:89');\n nx  | ny  |        dx        |        dy        | majoraxis | minoraxis |       la1        |        lo1        |        lov        |      latin1      |      latin2      \n-----+-----+------------------+------------------+-----------+-----------+------------------+-------------------+-------------------+------------------+------------------\n 201 | 155 | 4.29699993133545 | 4.29699993133545 |   6378160 |   6356775 | 42.2830009460449 | -72.3610000610352 | -67.0770034790039 | 45.3680000305176 | 45.3680000305176\n(1 row)\n\n\n\nCompare with the projection info returned by wgrib on the original file:\n\n\nwgrib -V wrf.grib\n\nrec 799:27785754:date 2014102318 ALBDO kpds5=84 kpds6=1 kpds7=0 levels=(0,0) grid=255 sfc 6hr fcst: bitmap: 736 undef\n  ALBDO=Albedo [%]\n  timerange 0 P1 6 P2 0 TimeU 1  nx 201 ny 155 GDS grid 3 num_in_ave 0 missing 0\n  center 7 subcenter 0 process 89 Table 2 scan: WE:SN winds(grid) \n  Lambert Conf: Lat1 42.283000 Lon1 -72.361000 Lov -67.077000\n      Latin1 45.368000 Latin2 45.368000 LatSP 0.000000 LonSP 0.000000\n      North Pole (201 x 155) Dx 4.297000 Dy 4.297000 scan 64 mode 8\n  min/max data 5 21.9  num bits 8  BDS_Ref 50  DecScale 1 BinScale 0\n\n\n\nNotice that our grib1 file is a \nLambert Conformal\n projection.  We will need these values for the next step. Note that \nthere is a tolerance of +/- 0.1 degrees\n to keep in mind when defining your coverage area.\n\n\nCreate Grid Projection File\n\uf0c1\n\n\nGrid projection files are stored in \n/awips2/edex/data/utility/edex_static/base/grib/grids/\n and there are four grid coverage types available:\n\n\n\n\n\n\nlambertConformalGridCoverage\n example\n\n\nlambertConformalGridCoverage\n\n    \nname\n305\n/name\n\n    \ndescription\nRegional - CONUS (Lambert Conformal)\n/description\n\n    \nla1\n16.322\n/la1\n\n    \nlo1\n-125.955\n/lo1\n\n    \nfirstGridPointCorner\nLowerLeft\n/firstGridPointCorner\n\n    \nnx\n151\n/nx\n\n    \nny\n113\n/ny\n\n    \ndx\n40.63525\n/dx\n\n    \ndy\n40.63525\n/dy\n\n    \nspacingUnit\nkm\n/spacingUnit\n\n    \nminorAxis\n6356775.0\n/minorAxis\n\n    \nmajorAxis\n6378160.0\n/majorAxis\n\n    \nlov\n-95.0\n/lov\n\n    \nlatin1\n25.0\n/latin1\n\n    \nlatin2\n25.0\n/latin2\n\n\n/lambertConformalGridCoverage\n\n\n\n\n\n\n\n\npolarStereoGridCoverage\n example\n\n\npolarStereoGridCoverage\n\n    \nname\n405\n/name\n\n    \ndescription\nSea Ice south 690X710 13km grid\n/description\n\n    \nla1\n-36.866\n/la1\n\n    \nlo1\n139.806\n/lo1\n\n    \nfirstGridPointCorner\nLowerLeft\n/firstGridPointCorner\n\n    \nnx\n690\n/nx\n\n    \nny\n710\n/ny\n\n    \ndx\n12.7\n/dx\n\n    \ndy\n12.7\n/dy\n\n    \nspacingUnit\nkm\n/spacingUnit\n\n    \nminorAxis\n6371229.0\n/minorAxis\n\n    \nmajorAxis\n6371229.0\n/majorAxis\n\n    \nlov\n100.0\n/lov\n\n\n/polarStereoGridCoverage\n\n\n\n\n\n\n\n\nlatLonGridCoverage\n example\n\n\nlatLonGridCoverage\n\n    \nname\n864162002\n/name\n\n    \ndescription\nUKMet HiRes combined - Southern Hemisphere\n        Longitude range 71.25E - 70.416E \n/description\n\n    \nla1\n-89.721\n/la1\n\n    \nlo1\n71.25\n/lo1\n\n    \nfirstGridPointCorner\nLowerLeft\n/firstGridPointCorner\n\n    \nnx\n864\n/nx\n\n    \nny\n162\n/ny\n\n    \ndx\n0.833\n/dx\n\n    \ndy\n0.556\n/dy\n\n    \nspacingUnit\ndegree\n/spacingUnit\n\n    \nla2\n-0.278\n/la2\n\n    \nlo2\n70.416\n/lo2\n\n\n/latLonGridCoverage\n\n\n\n\n\n\n\n\nmercatorGridCoverage\n example\n\n\nmercatorGridCoverage\n\n    \nname\nNBM_PR\n/name\n\n    \ndescription\n National Blend Grid over Puerto Rico - (1.25 km)\n/description\n\n    \nla1\n16.9775\n/la1\n\n    \nlo1\n-68.0278\n/lo1\n\n    \nfirstGridPointCorner\nLowerLeft\n/firstGridPointCorner\n\n    \nnx\n339\n/nx\n\n    \nny\n225\n/ny\n\n    \ndx\n1.25\n/dx\n\n    \ndy\n1.25\n/dy\n\n    \nla2\n19.3750032477232\n/la2\n\n    \nlo2\n-63.984399999999994\n/lo2\n\n    \nlatin\n20\n/latin\n\n    \nspacingUnit\nkm\n/spacingUnit\n\n    \nminorAxis\n6371200\n/minorAxis\n\n    \nmajorAxis\n6371200\n/majorAxis\n\n\n/mercatorGridCoverage\n\n\n\n\n\n\n\n\nCopy an existing file file with the same grid projection type (in this case \nlambertConformalGridCoverage\n) to a new file \nwrf.xml\n\n\ncd /awips2/edex/data/utility/edex_static/base/grib/grids/\ncp RUCIcing.xml wrf.xml\n\n\n\nAnd edit the new \nwrf.xml\n to define the projection values (example provided):\n\n\nvi wrf.xml\n\n\nlambertConformalGridCoverage\n\n    \nname\n201155\n/name\n\n    \ndescription\nRegional - CONUS (Lambert Conformal)\n/description\n\n    \nla1\n42.2830009460449\n/la1\n\n    \nlo1\n-72.3610000610352\n/lo1\n\n    \nfirstGridPointCorner\nLowerLeft\n/firstGridPointCorner\n\n    \nnx\n201\n/nx\n\n    \nny\n155\n/ny\n\n    \ndx\n4.29699993133545\n/dx\n\n    \ndy\n4.29699993133545\n/dy\n\n    \nspacingUnit\nkm\n/spacingUnit\n\n    \nminorAxis\n6356775.0\n/minorAxis\n\n    \nmajorAxis\n6378160.0\n/majorAxis\n\n    \nlov\n-67.0770034790039\n/lov\n\n    \nlatin1\n45.3680000305176\n/latin1\n\n    \nlatin2\n45.3680000305176\n/latin2\n\n\n/lambertConformalGridCoverage\n\n\n\n\n\n\nNotice \nname\n201155\n/name\n defined from the number of grid points (201 x 155). This value will be matched against an entry in our models file (below) to set the name of the model (e.g. WRF).\n\n\n\n\nCreate Model Definition\n\uf0c1\n\n\nModel definition XML files are found in \n/awips2/edex/data/utility/edex_static/base/grid/models/\n. Since our grib1 file has a center ID of 7 (NCEP) we will edit the \ngribModels_NCEP-7.xml\n file.\n\n\ncd /awips2/edex/data/utility/edex_static/base/grib/models/\n\nvi gribModels_NCEP-7.xml\n\n\n\nin \ngribModelSet\n add an entry\n\n\n    \nmodel\n\n        \nname\nWRF\n/name\n\n        \ncenter\n7\n/center\n\n        \nsubcenter\n0\n/subcenter\n\n        \ngrid\n201155\n/grid\n\n        \nprocess\n\n            \nid\n89\n/id\n\n        \n/process\n\n    \n/model\n\n\n\n\nsave the file and restart EDEX for the changes to take effect.\n\n\nsudo service edex_camel restart\n\n\n\nNow copy the \nwrf.grib\n file \nagain\n to \n/awips2/data_store/ingest/\n.  If everything is correct we will not see any persistence errors since the grid is now named \nWRF\n and not \nGribModel:7:0:89\n.\n\n\ncp wrd.grib /awips2/data_store/ingest/\n\nedex log grib\n\n\n\nAfter you have confirmed that the grid was ingested with the given name, you can \nedit the D2D product menus to display the new grid\n.\n\n\nTroubleshooting Grib Ingest\n\uf0c1\n\n\nIf you ingest a piece of data and the parameter appears as unknown in the metadata database, ensure that the correct parameter tables are in place for the center/subcenter.\n\n\nMake sure the latitude and longitude entries in your coverage specification file match those of your ingested raw grib file. There is a tolerance of +/- 0.1 degree to keep in mind when defining your coverage area.\n\n\nIf some of the information is unknown, using a grib utility application such as \nwgrib\n and \nwgrib2\n (not delivered) can be useful in determining the information that must be added to correctly process a new grib file.", 
             "title": "Ingest a New Grid"
         }, 
         {
             "location": "/edex/new-grid/#ingest-an-unsupported-grid", 
-            "text": "Download an example grib1 file and rename to a  *.grib  extension, then copy to the manual ingest point  /awips2/data_store/ingest/    wget http://www.unidata.ucar.edu/staff/mjames/14102318_nmm_d01.GrbF00600 -O wrf.grib\n\ncp wrf.grib /awips2/data_store/ingest/  Remember that the data distribution file ( /awips2/edex/data/utility/edex_static/base/distribution/grib.xml ) will match filename which have the  *.grib  extension.    Confirm that the grib file decodes in the grib log file:  edex log grib\n\nINFO [Ingest.GribDecode] /awips2/data_store/manual/grib/20141026/14/wrf.grib processed in: 0.1200 (sec) Latency: 21.8080 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/manual/grib/20141026/14/wrf.grib processed in: 0.1180 (sec) Latency: 21.8140 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/manual/grib/20141026/14/wrf.grib processed in: 0.4230 (sec) Latency: 21.8360 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/manual/grib/20141026/14/wrf.grib processed in: 0.2240 (sec) Latency: 21.9140 (sec)\n\n...    Check that the hdf5 data directory exists for our unnamed grid  ls -latr /awips2/edex/data/hdf5/grid/GribModel:7:0:89  Though the grib file has been decoded, it has been given a generic name with its center, subcenter, and process IDs (7, 0, 89, respectively).", 
+            "text": "Download an example grib1 file and rename to a  *.grib  extension, then copy to the manual ingest point  /awips2/data_store/ingest/    wget http://www.unidata.ucar.edu/staff/mjames/14102318_nmm_d01.GrbF00600 -O wrf.grib\n\ncp wrf.grib /awips2/data_store/ingest/  Remember that the data distribution file ( /awips2/edex/data/utility/edex_static/base/distribution/grib.xml ) will match filename which have the  *.grib  extension.    Confirm that the grib file decodes in the grib log file:  edex log grib\n\nINFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.1200 (sec) Latency: 21.8080 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.1180 (sec) Latency: 21.8140 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.4230 (sec) Latency: 21.8360 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.2240 (sec) Latency: 21.9140 (sec)\n\n...    Check that the hdf5 data directory exists for our unnamed grid  ls -latr /awips2/edex/data/hdf5/grid/GribModel:7:0:89  Though the grib file has been decoded, it has been given a generic name with its center, subcenter, and process IDs (7, 0, 89, respectively).", 
             "title": "Ingest an Unsupported Grid"
         }, 
         {
diff --git a/python/derived-parameters/index.html b/python/derived-parameters/index.html
index 707514ca4a..3f8bb9a32e 100644
--- a/python/derived-parameters/index.html
+++ b/python/derived-parameters/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../../cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../../cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/python/python-awips-data-access/index.html b/python/python-awips-data-access/index.html
index 1b51ed48d6..03078aff90 100644
--- a/python/python-awips-data-access/index.html
+++ b/python/python-awips-data-access/index.html
@@ -339,8 +339,8 @@
 
 
   <li class="md-nav__item">
-    <a href="../../cave/warngen/" title="WarnGen" class="md-nav__link">
-      WarnGen
+    <a href="../../cave/warngen/" title="WarnGen Walkthrough" class="md-nav__link">
+      WarnGen Walkthrough
     </a>
   </li>
 
diff --git a/sitemap.xml b/sitemap.xml
index bf44929529..42e9105df3 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -4,7 +4,7 @@
     
     <url>
      <loc>http://unidata.github.io/awips2/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -12,7 +12,7 @@
     
     <url>
      <loc>http://unidata.github.io/awips2/install/install-cave/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -20,7 +20,7 @@
     
     <url>
      <loc>http://unidata.github.io/awips2/install/install-edex/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -29,91 +29,91 @@
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-perspective/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/maps-views-projections/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/bundles-and-procedures/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/import-export/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/localization-perspective/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/ncp-perspective/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/nsharp/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/warngen/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/goes-16-satellite/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-gis-shapefiles/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-gridded-models/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-tools/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-radar-tools/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-edit-menus/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/cave-localization/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
@@ -123,43 +123,43 @@
         
     <url>
      <loc>http://unidata.github.io/awips2/install/start-edex/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/edex/ldm/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/edex/data-distribution-files/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/edex/new-grid/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/edex/data-purge/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/edex/edex-users/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/edex/data-plugins/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
@@ -169,43 +169,43 @@
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-grids/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-pointdata-surface-obs/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-satellite/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-radar/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-uair/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-hydro/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-map-resources/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
@@ -215,13 +215,13 @@
         
     <url>
      <loc>http://unidata.github.io/awips2/python/derived-parameters/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/python/python-awips-data-access/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
@@ -231,13 +231,13 @@
         
     <url>
      <loc>http://unidata.github.io/awips2/dev/awips-development-environment/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/dev/build-nsharp-macos/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
@@ -247,31 +247,31 @@
         
     <url>
      <loc>http://unidata.github.io/awips2/appendix/appendix-grid-parameters/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/appendix/appendix-acronyms/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/appendix/appendix-cots/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/appendix/appendix-wsr88d/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>http://unidata.github.io/awips2/cave/cave-keyboard-shortcuts/</loc>
-     <lastmod>2017-06-15</lastmod>
+     <lastmod>2017-06-30</lastmod>
      <changefreq>daily</changefreq>
     </url>