Merrick and Company 20050822 vector digital data Helena, MT Montana State Library https://ftpgeoinfo.msl.mt.gov/Data/Spatial/NonMSDI/Collections/Yellowstone_River_Clearinghouse/Elevation/Generate http://mslapps.mt.gov/Geographic_Information/Data/DataList/datalist_Details.aspx?did={197c8cad-2e4e-4965-8009-109451d68f84} The data consists of pairs of ESRI Generate files storing elevation data that may be converted to TIN (triangulated irregular network) data sets. Each pair of files covers a 1200mX1200m grid tile, and there are 813 tiles in the first phase of the mapping project. These data were created as part of a joint Yellowstone River Conservation District Council and U.S. Army Corps of Engineers, Omaha District cumulative impacts study of the Yellowstone River channel and floodplain. The multi-agency interdisciplinary planning study extends 477 river miles from Sweetgrass County, Montana to the Missouri River confluence in McKenzie County, North Dakota. These data are specifically intended to provide an accurate digital surface model (topographic and bathymetric) with which to analyze the hydraulic conditions of the Yellowstone River channel and floodplain. The TINs were created to operate within the ArcGIS software environment. In addition, they are intended to serve as a base for the project GIS and also to support a wide variety of analyses including planimetric data extraction (e.g., infrastructure, riverine geomorphology, land cover, habitat and vegetation), and to monitor long-term river channel changes. The first phase of the mapping focused on Stillwater, Yellowstone and Dawson Counties in Montana and included approximately 295 square miles of floodplain, together with 130 river miles of channel bathymetry. These data are also available in DEM format and as ESRI TIN datasets at http://geoinfo.msl.mt.gov/Home/data/yellowstone_river_corridor_resource_clearinghouse/elevation_data, along with data (from 2007) for the remaining counties of the Yellowstone River corridor. There are two data files for each grid tile. One file has a .pnt extension. Each line in the .pnt file has four columns. The first column contains an ID number and is needed if the file is to be imported with the Arc/Info Generate tool. The second and third columns are the x and y coordinates of the point and the fourth column is the elevation of the point in meters. The other file has a .lin extension and contains the coordinates of hard breaklines used in developing the TIN. The information for each line segment in these files spans several records. The first record contains an ID number that is needed for the Arc/Info Generate tool. This is followed by at least two records of three columns each that contain the x, y, and elevation of a vertex along the line. Each line segment is terminated by a record that consists of the word END. This is the procedure to create a TIN from a pair of these files with ArcMap and ArcToolbox. The procedure requires that Arc/Info Workstation and 3D Analyst be installed. 1 - Use the Generate tool in the Coverage Tools-Conversion-To Coverage toolset to convert the .pnt file to a point coverage and the .lin file to a line coverage. 2 - Use the Create TIN tool in the 3D Analyst Tools-TIN Creation toolset to create a new empty TIN. 3 - Open the Edit TIN tool in the 3D Analyst Tools-TIN Creation toolset and add the two coverages you just made to the empty TIN. 4 - Set the height_field of the point coverage to $ANGLE and make sure its SF_type is masspoint. 5 - Make sure the SF_type of the line coverage is hardline. 6 - push the OK button. 20040501 20040502 ground condition Complete As needed -109.5654 -104.3925 47.3556 45.5775 ISO 19115 Topic Category elevation TIN triangulated irregular network DTM elevation model Yellowstone Yellowstone River Yellowstone River Conservation District Council Stillwater Dawson Montana USA None 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. Stan Danielsen Yellowstone River Conservation District Council (YRCDC) Project Coordinator mailing and physical address

1371 Rimtop Drive

Billings Montana 59105 406-247-4414 406-247-4429 sdanielsen@mt.gov Verification of attribute accuracy of LIDAR points involves the use of filtering techniques. Auto-filtering uses algorithms to reclassify data in the point cloud. Hand-filtering involves the use of a technician working in a graphic environment to reclassify the erroneous points that may remain in the LIDAR point cloud after auto filter. The Arc/Info CREATETIN command was used with a proximal tolerance of 0.33m and a weed tolerance of 0.01m. CREATETIN produces a TIN from the DTM export files (model keypoints, bathymetric points, and breaklines). 0.5 meters Horizontal accuracy was tested by comparing the raw contours from each flightline against adjoining flightlines at specific points. LIDAR points were tested for vertical accuracy by comparing their values to known control points. Ground GPS techniques were used to establish the control locations. Survey control points were used to validate the accuracy of the LIDAR surface model and effects of filtering algorithms for vegetation removal. This "ground truth survey" was conducted in unique land cover and land use areas. Contour lines were generated and were verified for accuracy against surveyed spot elevations. Supplemental breaklines were added to more accurately model certain features. This essential validation proves the accuracy of the contours relative to the adjustment of the LIDAR data. 0.2 meters The vertical positional accuracy of the data is verified by a control report that matches known ground control points against LIDAR acquired points. Aerial Surveys International, LLC Unpublished material remote-sensing image Watkins, CO Aerial Surveys International, LLC 15840 filmstrip 20040501 20040502 ground condition Photography Film supplied for scanning. Merrick and Company 20040901 document Aurora, CO Merrick and Company 20040901 publication date FDAAT Control network result with camera calibration information U.S. Geological Survey 20020211 document Reston, VA U.S. Geological Survey 20030117 publication date Camera_Input Camera calibration parameters Merrick and Company 20040805 document Aurora, CO Merrick and Company 20040805 publication date Ground_Control Survey data for aerotriangulation and data quality control. Merrick and Company Aurora, CO Merrick and Company online ground condition DTM The digital terrain model (DTM) was created from LIDAR data and from supplemental data compiled from aerial photography. The DTM meets National Map Accuracy Standards for one meter contours. Merrick and Company point digital data Aurora, CO Merrick and Company 20040908 20040911 ground condition LIDAR LIDAR points form the basis of the DTM surface. LIDAR data was collected using Merrick's ALS40 sensor. The data was field-verified for complete coverage of the project area. Raw data files were parsed into manageable client-specific tiles. These tiles were then processed through automated filtering that separates the data into different classification groups: error points, ground points, and canopy-building points. The data was next taken into a graphic environment to reclassify the erroneous points that may remain in the LIDAR point cloud after auto filter. The surface was then normalized into a digital surface model (DSM). Final data extraction for the client's keypoint (statistically significant points) and canopy-building files were then generated. Using orthophotography, planimetric features were compiled as breaklines to supplement the LIDAR data. The LIDAR digital surface model was then processed with the breaklines. ASCII lines and points files were generated from the LIDAR data. A process is run in Arc/Info that removes points from the proximity of specified features, resulting in a cleaner data set. The Arc/Info CREATETIN command then outputs the TIN files from the lines and points files. Photography FDAAT Camera_Input Ground_Control DTM LIDAR 20050217 Doug Jacoby Senior Project Manager mailing and physical address

2450 South Peoria Street

Aurora CO 80014 303-353-3903 303-745-0964 doug.jacoby@merrick.com State Plane Coordinate System 2500 45 49 -109.5 44.25 600000 0 meters North American Datum of 1983 Geodetic Reference System 80 6378137.000000 298.257222 North American Vertical Datum of 1988 .001 meters Explicit elevation coordinate included with horizontal coordinates Montana State Library mailing address

P.O. Box 201800

Helena MT 59620-1800 406-444-5354 406-444-5354 Montana Relay 711 406-444-0266 geoinfo@mt.gov geoinfo@mt.gov Downloadable data 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. Plain-text ESRI Generate Files https://ftpgeoinfo.msl.mt.gov/Data/Spatial/NonMSDI/Collections/Yellowstone_River_Clearinghouse/Elevation/Generate 20131107 20050513 Andy Morris Merrick and Company ArcGIS Services Manager mailing and physical address

2450 South Peoria Street

Aurora CO 80014 303-353-3929 303-751-0741 303-745-0964 andy.morris@merrick.com FGDC Content Standard for Digital Geospatial Metadata FGDC-STD-001-1998 {9d44b178-4731-11e3-86ae-ce3f5508acd9}