<metadata>
  <idinfo>
    <citation>
      <citeinfo>
        <origin>DTM Consulting, Inc.; Bozeman, MT</origin>
        <pubdate>20100216</pubdate>
        <title>Yellowstone River Historic Physical Features 1950-2005</title>
        <geoform>vector digital data</geoform>
        <pubinfo>
          <pubplace>Helena, Montana</pubplace>
          <publish>Montana State Library</publish>
        </pubinfo>
        <onlink>https://ftpgeoinfo.msl.mt.gov/Data/Spatial/NonMSDI/Collections/Yellowstone_River_Clearinghouse/Geodatabases/Yellowstone_Historic_Features.zip</onlink>
        <lworkcit>
          <citeinfo>
            <title>Yellowstone River Clearinghouse GIS Layers</title>
            <onlink>https://mslservices.mt.gov/Geographic_Information/Data/DataList/datalist_Details.aspx?did={17daa910-aba0-11e3-a5e2-0800200c9a66}</onlink>
          </citeinfo>
        </lworkcit>
      </citeinfo>
    </citation>
    <descript>
      <abstract>This data consists of polylines representing mapped physical features of the Yellowstone River for Stillwater, Yellowstone and Dawson counties.  These data were digitized from georeferenced imagery for six different periods -- 1948 to 1951, 1976, 1995, 2001, 2004 and 2005.
 
Polylines are attributed as being either present or absent for each time period.  Additionally, each feature is attributed as to whether it functionally impacts natural river processes for each time period.

This is a complex dataset representing detailed photo interpretation.  To understand what the attributes represent, and to use these data properly, one should read the accompanying report, "Yellowstone River Human Impacts Timeline - Final Report November 6, 2008"  (https://ftpgeoinfo.msl.mt.gov/Documents/Projects/Yellowstone_River_Clearinghouse/HumanImpactsTimeline_Final_Report_110608.pdf).</abstract>
      <purpose>Data was developed to support the Yellowstone River Cumulative Effects Study.  Linework represents conditions in the photography.</purpose>
    </descript>
    <timeperd>
      <timeinfo>
        <mdattim>
          <sngdate>
            <caldate>1950</caldate>
          </sngdate>
          <sngdate>
            <caldate>1976</caldate>
          </sngdate>
          <sngdate>
            <caldate>1995</caldate>
          </sngdate>
          <sngdate>
            <caldate>2005</caldate>
          </sngdate>
        </mdattim>
      </timeinfo>
      <current>ground condition</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
    </status>
    <spdom>
      <bounding>
        <westbc>-109.547108</westbc>
        <eastbc>-104.461074</eastbc>
        <northbc>47.436912</northbc>
        <southbc>45.479409</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>ISO 19115 Topic Category</themekt>
        <themekey>inlandWaters</themekey>
      </theme>
      <theme>
        <themekey>Stream channels</themekey>
        <themekey>Flow lines</themekey>
        <themekey>Yellowstone River</themekey>
      </theme>
      <place>
        <placekey>Yellowstone River</placekey>
        <placekey>Montana</placekey>
      </place>
    </keywords>
    <accconst>None</accconst>
    <useconst>Linework and attributes represent the conditions noted in the photography.  No interpretation of the photography was made to adjust for flow conditons.  Linework was digitized at 1:6000, and up to 1:3000 in detailed areas.

The Montana State Library provides this product/service for informational purposes only. The Library did not produce it for, nor is it suitable for legal, engineering, or surveying purposes. Consumers of this information should review or consult the primary data and information sources to ascertain the viability of the information for their purposes. The Library provides these data in good faith but does not represent or warrant its accuracy, adequacy, or completeness. In no event shall the Library be liable for any incorrect results or analysis; any direct, indirect, special, or consequential damages to any party; or any lost profits arising out of or in connection with the use or the inability to use the data or the services provided. The Library makes these data and services available as a convenience to the public, and for no other purpose. The Library reserves the right to change or revise published data and/or services at any time.</useconst>
    <ptcontac>
      <cntinfo>
        <cntperp>
          <cntper>Jim Robinson</cntper>
          <cntorg>Montana DNRC</cntorg>
        </cntperp>
        <cntaddr>
          <addrtype>mailing address</addrtype>
          <address>PO Box 201601</address>
          <city>Helena</city>
          <state>MT</state>
          <postal>59620-1601</postal>
        </cntaddr>
        <cntvoice>406-444-4247</cntvoice>
        <cntemail>jrobinson@state.mt.us</cntemail>
      </cntinfo>
    </ptcontac>
    <datacred>Data was prepared by DTM Consulting, Inc. for the Yellowstone River Conservation District Council.</datacred>
  </idinfo>
  <dataqual>
    <lineage>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>U.S. Geological Survey</origin>
            <title>Circa 1950 Aerial Photos</title>
            <pubinfo>
              <pubplace>Sioux Falls, SD</pubplace>
              <publish>U.S. Geological Survey
Earth Resources Observation Systems (EROS) Data Center</publish>
            </pubinfo>
            <onlink>http://edc.usgs.gov/products/aerial.html</onlink>
          </citeinfo>
        </srccite>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>1948</begdate>
              <enddate>1951</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccontr>This is the source of the circa 1950 data for Sweet Grass, Stillwater, and western Yellowstone counties.

The EROS Data Center has archived thousands of rolls of film containing several million frames of historical aerial and satellite photographs dating back to the 1930's gathered from various Federal agencies. This archive includes the rather well known, often utilized NHAP and NAPP film, but the largest portion of this archive consists of original film acquired in support of the USGS 1:24,000 topographic quadrangle map series, taken during the 1940s through the 1970s. Most of this photography is reasonably large scale to support the production of the quadrangle maps. USGS EROS has implemented a medium-resolution digital product. The medium-resolution files are created at approximately 600 dpi with an output image size of around five inches square.</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>U.S. National Archives and Records Administration (NARA)</origin>
            <title>Circa 1950 Aerial Photos</title>
            <pubinfo>
              <pubplace>Washington, DC</pubplace>
              <publish>U.S. National Archives and Records Administration (NARA)</publish>
            </pubinfo>
            <onlink>http://www.archives.gov/research/formats/cartographic.html</onlink>
          </citeinfo>
        </srccite>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>1948</begdate>
              <enddate>1951</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccontr>This is the source of the circa 1950 data for Treasure, Rosebud, Custer, Prairie, Dawson, Richland, McKenzie, and eastern Yellowstone counties.</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>U.S. Army Corps of Engineers</origin>
            <title>1976 Aerial Photos</title>
          </citeinfo>
        </srccite>
        <srctime>
          <timeinfo>
            <sngdate>
              <caldate>1976</caldate>
            </sngdate>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccontr>The 1976 data were digitized from this source.</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>U.S. Geological Survey</origin>
            <title>1995 Aerial Photos</title>
            <pubinfo>
              <pubplace>Helena, MT</pubplace>
              <publish>Montana State Library</publish>
            </pubinfo>
            <onlink>http://mslapps.mt.gov/Geographic_Information/Data/Aerial_Photos/doqq1.aspx</onlink>
          </citeinfo>
        </srccite>
        <srctime>
          <timeinfo>
            <sngdate>
              <caldate>1995</caldate>
            </sngdate>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccontr>The 1995 data were digitized from this source.</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>U.S. Department of Agriculture
Natural Resources Conservation Service</origin>
            <title>2001 Aerial Photos</title>
            <pubinfo>
              <pubplace>Helena, MT</pubplace>
              <publish>Montana State Library</publish>
            </pubinfo>
            <onlink>https://ftpgeoinfo.msl.mt.gov/Data/Spatial/NonMSDI/Collections/Yellowstone_River_Clearinghouse/Imagery/2001_IR/</onlink>
          </citeinfo>
        </srccite>
        <srctime>
          <timeinfo>
            <sngdate>
              <caldate>2001</caldate>
            </sngdate>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccontr>The 2001 data were digitized from this source.</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>Much of the initial physical feature data compilation was performed by Jim Robinson (DNRC). All available data GIS sources defining physical features for Stillwater, Yellowstone and Dawson counties were integrated into a single data set. These included:
 Physical Features Inventory from the Rapid Aerial Assessment,
 NRCS field mapping, and
 Feature mapping from 2004 LiDAR/high-resolution digital photography.

To provide the most complete mapping available, as well as to assist in assessing the features in the core data sets, the imagery from 2001 (color infrared) and 2005 (color NAIP) were also assessed. Additionally, shaded relief LiDAR (2004) data was referenced to help identify hidden or subtle features. By using the complete suite of available imagery there were more clues available to assess the existence, functionality, extent, and timing of each feature.

To detect temporal changes in the distribution of physical features, the digitizing process involved examining each suite of imagery and assessing each length of riverbank for the presence or absence of physical features. To ensure mapping consistency, features were mapped forwards through time, starting with the 2004 high-resolution orthophotos as a baseline, and moving to successively newer photography. The general workflow sequence is as follows:
 1) Assess the 2004 imagery.
 - a. Review each feature in the current dataset and confirm its existence using visual clues.
 - b. Remove or flag suspect features.
 - c. Add additional features that were missing in the dataset.
 - d. Assign the appropriate attributes to each feature.
2) Review the LiDAR shaded relief to identify any hidden or incorrectly mapped features.
 - a. Add any missing features.
 - b. Remove or flag suspect features.
 - c. Assign the appropriate attributes.
3) Review the 1950 imagery.
 - a. Assess whether the mapped features are present. Attribute each feature as necessary to reflect the presence or absence of the feature in the 1950 imagery.
 - b. Split existing feature lines to reflect the extent of feature in 1950. For example, a section of bank protection may be shorter in 1950 than it was in 2004. Here the 2004 line is split. One piece shows presence in both 2004 and 1950, while the other piece only shows existence in 2004.
 - c. Add any missing features.
 - d. Assign the appropriate attributes.
4) Repeat Step 3 for the remaining imagery (1976, 1995, 2001 and 2005).</procdesc>
        <proccont>
          <cntinfo>
            <cntorgp>
              <cntorg>DTM Consulting, Inc.</cntorg>
              <cntper>Tony Thatcher</cntper>
            </cntorgp>
            <cntaddr>
              <addrtype>mailing and physical address</addrtype>
              <address>211 N Grand Suite J</address>
              <city>Bozeman</city>
              <state>MT</state>
              <postal>59715</postal>
            </cntaddr>
            <cntvoice>406-585-5322</cntvoice>
            <cntemail>tony@dtmgis.com</cntemail>
          </cntinfo>
        </proccont>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>String</sdtstype>
        <ptvctcnt>754</ptvctcnt>
      </sdtsterm>
    </ptvctinf>
  </spdoinfo>
  <spref>
    <horizsys>
      <planar>
        <gridsys>
          <gridsysn>State Plane Coordinate System</gridsysn>
          <spcs>
            <spcszone>2500</spcszone>
            <lambertc>
              <stdparll>45.000000</stdparll>
              <stdparll>49.000000</stdparll>
              <longcm>-109.500000</longcm>
              <latprjo>44.250000</latprjo>
              <feast>600000.000000</feast>
              <fnorth>0.000000</fnorth>
            </lambertc>
          </spcs>
        </gridsys>
        <planci>
          <plandu>meters</plandu>
        </planci>
      </planar>
      <geodetic>
        <horizdn>North American Datum of 1983</horizdn>
        <ellips>Geodetic Reference System 80</ellips>
        <semiaxis>6378137.000000</semiaxis>
        <denflat>298.257222</denflat>
      </geodetic>
    </horizsys>
    <vertdef>
      <altsys>
        <altres>0.000003</altres>
        <altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
      </altsys>
    </vertdef>
  </spref>
  <eainfo>
    <detailed>
      <enttyp>
        <enttypl>phys_feat_lines_allyrs_SW_YE_DA</enttypl>
      </enttyp>
      <attr>
        <attrlabl>OBJECTID</attrlabl>
        <attrdef>Internal feature number.</attrdef>
      </attr>
      <attr>
        <attrlabl>Shape</attrlabl>
        <attrdef>Feature geometry.</attrdef>
      </attr>
      <attr>
        <attrlabl>Origin</attrlabl>
        <attrdef>Originator</attrdef>
        <attrdomv>
          <edom>
            <edomv>DTM</edomv>
            <edomvd>Feature identified from aerial photography by DTM Consulting</edomvd>
          </edom>
          <edom>
            <edomv>JVR</edomv>
            <edomvd>Feature identified by James Robinson, Montana DNRC</edomvd>
          </edom>
          <edom>
            <edomv>Merrick</edomv>
            <edomvd>Feature copied from photogrammetric GIS layer</edomvd>
          </edom>
          <edom>
            <edomv>NRCS</edomv>
            <edomvd>NRCS 2001 Physical Features Inventory</edomvd>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>COUNTY</attrlabl>
        <attrdef>County that the feature is in</attrdef>
      </attr>
      <attr>
        <attrlabl>FEATURECLA</attrlabl>
        <attrdef>Feature general classification</attrdef>
        <attrdomv>
          <edom>
            <edomv>Irrigation</edomv>
            <edomvd>Dikes, levees and other features associated with irrigation infrastructure -- ditches, canal levees, and pump station protection</edomvd>
          </edom>
          <edom>
            <edomv>Stream Stabilization</edomv>
            <edomvd>A feature that stops bank erosion and provents lateral channel migration.  These features include riprap, car bodies, flow deflectors, and riverbank levees</edomvd>
          </edom>
          <edom>
            <edomv>Transportation Encroachment</edomv>
            <edomvd>Any feature associated with tranportation -- county road, railroad, interstate, bridge approach, and other roads</edomvd>
          </edom>
          <edom>
            <edomv>Other Off Channel</edomv>
            <edomvd>Dikes, levees, and other features that are off channel -- field edges, random push-up berms behind other features, power line tower stands</edomvd>
          </edom>
          <edom>
            <edomv>Other</edomv>
            <edomvd>Any other feature such as sewage plants and refineries</edomvd>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>FEATURETYP</attrlabl>
        <attrdef>Specific Feature Type</attrdef>
        <attrdomv>
          <edom>
            <edomv>Bridge approach</edomv>
            <edomvd>Any road or railroad, existing or historic, that ramps up to a bridge crossing</edomvd>
          </edom>
          <edom>
            <edomv>Car Bodies</edomv>
            <edomvd>Car bodies are usually not identifiable in the GIS.  These features have been identified in the NRCS Physical Features Inventory</edomvd>
          </edom>
          <edom>
            <edomv>Concrete Riprap</edomv>
            <edomvd>It is generally impossible to indentify the type of riprap in any photography. Any riprap that is noted as concrete or rock was likely mapped in the field by the NRCS and no further field investigation has been undertaken to verify this mapping. If additional NRCS-mapped features were extended, they generally were attributed as the same type (concrete or rock) as the original feature. Note: For riprap features digitized by DTM, it was impossible to determine the actual type of material used. In this case, the feature took on the attributes of adjacent bank protection, or it was assumed to be rock.</edomvd>
          </edom>
          <edom>
            <edomv>Rock Riprap</edomv>
            <edomvd>It is generally impossible to indentify the type of riprap in any photography. Any riprap that is noted as concrete or rock was likely mapped in the field by the NRCS and no further field investigation has been undertaken to verify this mapping. If additional NRCS-mapped features were extended, they generally were attributed as the same type (concrete or rock) as the original feature. Note: For riprap features digitized by DTM, it was impossible to determine the actual type of material used. In this case, the feature took on the attributes of adjacent bank protection, or it was assumed to be rock.</edomvd>
          </edom>
          <edom>
            <edomv>County Road</edomv>
            <edomvd>County road features consist of any road other than the Interstate that has, or appears to have, a sizeable road prism. This includes both paved and dirt roads. In many cases a dirt road may convert to a paved road over time, and no additional attributing was made to note the change. Minor roads, driveways, and temporary features are generally mapped as "Other".</edomvd>
          </edom>
          <edom>
            <edomv>Floodplain Dike/Levee</edomv>
            <edomvd>Any Dike or Levee.  These features include canal dikes, streambank protections, field berms, etc.</edomvd>
          </edom>
          <edom>
            <edomv>Flow Deflector</edomv>
            <edomvd>Flow deflectors consist of erosion control features such as barbs.  Although these are typically point features, they were digitized as linear features comprising the entire series of deflectors. Where the flow deflectors are in association with other bank protections such as riprap or levees, they are attributed as flow deflectors.</edomvd>
          </edom>
          <edom>
            <edomv>In-Channel Diversion</edomv>
            <edomvd>An in-channel diversion is any features that extends across a stream channel. This includes permanent dams, rock diversions, and semi-permanent diversions such as maintained gravel berms</edomvd>
          </edom>
          <edom>
            <edomv>Interstate</edomv>
            <edomvd>Embankments assiciated with I-90 or I-94</edomvd>
          </edom>
          <edom>
            <edomv>Other</edomv>
            <edomvd>Minor roads, driveways, or other features that do not appear to have a road prism and thus do not impact the river corridor or floodplain</edomvd>
          </edom>
          <edom>
            <edomv>Railroad</edomv>
            <edomvd>The railroad grade commonly encroaches into the stream corridor.  These linear embankments are specifically identified as rail lines</edomvd>
          </edom>
          <edom>
            <edomv>Steel Retaining Wall</edomv>
            <edomvd>A single retaining wall occurrence just below Billings</edomvd>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Notes</attrlabl>
        <attrdef>Additional explanation or description of the feature</attrdef>
      </attr>
      <attr>
        <attrlabl>SUBREACH</attrlabl>
        <attrdef>2004 Geomorphic Reconnaissance study reach that the feature is in</attrdef>
      </attr>
      <attr>
        <attrlabl>Bank</attrlabl>
        <attrdef>Feature location, right bank or left bank</attrdef>
      </attr>
      <attr>
        <attrlabl>HI_Reliability</attrlabl>
        <attrdef>Mapping reliability evaluation</attrdef>
        <attrdomv>
          <edom>
            <edomv>High</edomv>
            <edomvd>Feature is clearly visible in aerial photos</edomvd>
          </edom>
          <edom>
            <edomv>Medium</edomv>
            <edomvd>Feature is inferred from other information</edomvd>
          </edom>
          <edom>
            <edomv>Low</edomv>
            <edomvd>Feature is not visible on aerial photos, but was noted from other sources</edomvd>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>HI_Source</attrlabl>
        <attrdef>Source of Human Impact Reliability evaluation</attrdef>
        <attrdomv>
          <edom>
            <edomv>DTM</edomv>
            <edomvd>DTM Consulting</edomvd>
          </edom>
          <edom>
            <edomv>JR</edomv>
            <edomvd>James Robinson, Montana DNRC</edomvd>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>HI_Notes</attrlabl>
        <attrdef>Additional notes about impact of the feature</attrdef>
      </attr>
      <attr>
        <attrlabl>HI_2005</attrlabl>
        <attrdef>Feature presence, 2005</attrdef>
        <attrdomv>
          <edom>
            <edomv>Feature is present</edomv>
          </edom>
          <edom>
            <edomv>Feature is NOT present</edomv>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>HI_2004</attrlabl>
        <attrdef>Feature presence, 2004</attrdef>
      </attr>
      <attr>
        <attrlabl>HI_2001</attrlabl>
        <attrdef>Feature presence, 2001</attrdef>
      </attr>
      <attr>
        <attrlabl>HI_1995</attrlabl>
        <attrdef>Feature presence, 1995</attrdef>
      </attr>
      <attr>
        <attrlabl>HI_1976</attrlabl>
        <attrdef>Feature presence, 1976</attrdef>
      </attr>
      <attr>
        <attrlabl>HI_1950</attrlabl>
        <attrdef>Feature presence, 1950</attrdef>
      </attr>
      <attr>
        <attrlabl>Shape_Length</attrlabl>
        <attrdef>Length of feature in meters</attrdef>
      </attr>
      <attr>
        <attrlabl>HI_2005_fx</attrlabl>
        <attrdef>Functionality, 2005
The functionality of a feature refers to its relative level of influence on the active river channel at the time of photography. Some interpretation is used here to flag features that have the potential to influence processes such as lateral channel migration.  In general, it is fairly straightforward to identify the functionality of bank armor, as that functionality is dictated by position relative to an active channel bankline. In contrast, the functionality of dikes and levees that are located out of the active channel corridor is difficult to discern without information regarding their hydraulic impacts on floodwaters. Dikes and levees were attributed in terms of apparent functionality with respect to either their impacts on channel migration, side channel access, or overbank flow patterns. However, due to inherent uncertainties in that attribution, the data for these features are summarized as total length of the mapped features, with no assumption regarding their overall impacts on flooding extents.

In the mapping effort, attempts have been made to avoid duplicating the function of features that run parallel to each other. For example, if a road is behind a riprapped bank, then the riprap would have a Yes for Function, while the road would be No.</attrdef>
        <attrdomv>
          <edom>
            <edomv>Yes</edomv>
            <edomvd>The feature is clearly influencing, or has the potential to restrict the lateral migration of the river.</edomvd>
          </edom>
          <edom>
            <edomv>Maybe</edomv>
            <edomvd>These tended to be major features that were a moderate distance from the active channel, but still have the potential to restrict the flow of water, or the lateral migration of the channel in flood events.</edomvd>
          </edom>
          <edom>
            <edomv>No</edomv>
            <edomvd>The feature is usually a great distance from the channel, is behind other bank protection features, or is along a non-alluvial boundary.</edomvd>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>HI_2004_fx</attrlabl>
        <attrdef>Functionality, 2004</attrdef>
      </attr>
      <attr>
        <attrlabl>HI_2001_fx</attrlabl>
        <attrdef>Functionality, 2001</attrdef>
      </attr>
      <attr>
        <attrlabl>HI_1995_fx</attrlabl>
        <attrdef>Functionality, 1995</attrdef>
      </attr>
      <attr>
        <attrlabl>HI_1976_fx</attrlabl>
        <attrdef>Functionality, 1976</attrdef>
      </attr>
      <attr>
        <attrlabl>HI_1950_fx</attrlabl>
        <attrdef>Functionality, 1950</attrdef>
      </attr>
    </detailed>
  </eainfo>
  <distinfo>
    <distrib>
      <cntinfo>
        <cntorgp>
          <cntorg>Montana State Library</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing address</addrtype>
          <address>PO Box 201800</address>
          <city>Helena</city>
          <state>MT</state>
          <postal>59620-1800</postal>
        </cntaddr>
        <cntvoice>406-444-5354</cntvoice>
        <cntvoice>406-444-5354</cntvoice>
        <cnttdd>Montana Relay 711</cnttdd>
        <cntfax>406-444-0266</cntfax>
        <cntemail>geoinfo@mt.gov</cntemail>
        <cntemail>geoinfo@mt.gov</cntemail>
      </cntinfo>
    </distrib>
    <resdesc>Downloadable Data</resdesc>
    <distliab>The Montana State Library provides this product/service for informational purposes only. The Library did not produce it for, nor is it suitable for legal, engineering, or surveying purposes. Consumers of this information should review or consult the primary data and information sources to ascertain the viability of the information for their purposes. The Library provides these data in good faith but does not represent or warrant its accuracy, adequacy, or completeness. In no event shall the Library be liable for any incorrect results or analysis; any direct, indirect, special, or consequential damages to any party; or any lost profits arising out of or in connection with the use or the inability to use the data or the services provided. The Library makes these data and services available as a convenience to the public, and for no other purpose. The Library reserves the right to change or revise published data and/or services at any time.</distliab>
    <stdorder>
      <digform>
        <digtinfo>
          <formname>ESRI Personal Geodatabase</formname>
        </digtinfo>
        <digtopt>
          <onlinopt>
            <computer>
              <networka>
                <networkr>https://ftpgeoinfo.msl.mt.gov/Data/Spatial/NonMSDI/Collections/Yellowstone_River_Clearinghouse/Geodatabases/Yellowstone_Historic_Features.zip</networkr>
              </networka>
            </computer>
          </onlinopt>
        </digtopt>
      </digform>
    </stdorder>
  </distinfo>
  <metainfo>
    <metd>20131115</metd>
    <metrd>20100212</metrd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>DTM Consulting, Inc.</cntorg>
          <cntper>Tony Thatcher</cntper>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical address</addrtype>
          <address>211 N Grand Suite J</address>
          <city>Bozeman</city>
          <state>MT</state>
          <postal>59715</postal>
        </cntaddr>
        <cntvoice>406-585-5322</cntvoice>
        <cntemail>tony@dtmgis.com</cntemail>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
  </metainfo>
  <Esri>
    <PublishedDocID>{74C0848B-31FB-41E4-B9CE-5726886AE62A}</PublishedDocID>
  </Esri>
</metadata>