Metadata for Elevation Data, ESRI Generate Files, Yellowstone River Corridor, Stillwater, Yellowstone, and Dawson Counties, Montana, 2004

Identification Information
Data Quality Information
Spatial Data Organization Information
Spatial Reference Information
Distribution Information
Metadata Reference Information

Download full XML Metadata

Identification Information:

Citation:

Originator: Merrick & Company

Publication date: 08/22/2005

Title:

Elevation Data, ESRI Generate Files, Yellowstone River Corridor, Stillwater, Yellowstone, and Dawson Counties, Montana, 2004

Publication place: Helena, MT
Publisher: Montana State Library

Online linkage: ftp://ftp.geoinfo.msl.mt.gov/Data/Spatial/NonMSDI/Collections/Yellowstone_River_Clearinghouse/Elevation/Generate

Larger Work Citation:

Originator: Merrick & Company
Originator: Woolpert, Inc.
Publication date: 2009
Title: Yellowstone River Floodplain Elevation Data, 2004 and 2007
Online linkage: http://apps.msl.mt.gov/Geographic_Information/Data/DataList/datalist_Details.aspx?did={197c8cad-2e4e-4965-8009-109451d68f84}

Abstract:

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.

Purpose:

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.

Supplemental information:

These data are also available in DEM format and as ESRI TIN datasets at http://geoinfo.montanastatelibrary.org/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.

Time period of content:

Beginning date: 05/01/2004
Ending date: 05/02/2004
Currentness reference: ground condition

Status:

Progress: Complete
Maintenance and update frequency: As needed

Access constraints: None

Use constraints:

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.

Point of contact:

Stan Danielsen
Project Coordinator
Yellowstone River Conservation District Council (YRCDC)
1371 Rimtop Drive
Billings, Montana 59105
Telephone: (406) 247-4414
Fax: (406) 247-4429
E-Mail: sdanielsen@mt.gov

Data Quality Information:

Attribute accuracy report:

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.

Completeness report:

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).

Quantitative horizontal positional accuracy assessment:

Horizontal positional accuracy value: 0.5 meters
Horizontal positional accuracy explanation:: Horizontal accuracy was tested by comparing the raw contours from each flightline against adjoining flightlines at specific points.

Vertical positional accuracy report:

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.

Quantitative vertical positional accuracy assessment:

Vertical positional accuracy value: 0.2 meters
Vertical positional accuracy explanation:: The vertical positional accuracy of the data is verified by a control report that matches known ground control points against LIDAR acquired points.

Lineage:

Source information:

Originator: Aerial Surveys International, LLC
Publication date: Unpublished material
Title: Color Photography
Source scale denominator: 15840
Type of source media: filmstrip
Source contribution: Film supplied for scanning.
Calendar date: 05/01/2004
Calendar date: 05/02/2004

Source information:

Originator: Merrick & Company
Publication date: 09/01/2004
Title: Fully Digital Analytical Aerotriangulation Report (FDAAT)
Source contribution:: Control network result with camera calibration information
Calendar date: 09/01/2004

Source information:

Originator: U.S. Geological Survey
Publication date: 02/11/2002
Title:: Report of Calibration of Aerial Mapping Camera; USGS Report No. OSL/2825
Source contribution: Camera calibration parameters
Calendar date: 01/17/2003

Source information:

Originator: Merrick & Company
Publication date: 08/05/2004
Title: Ground Control
Source contribution: Survey data for aerotriangulation and data quality control.
Calendar date: 08/05/2004

Source information:

Originator: Merrick & Company
Title: Digital Terrain Model (DTM)
Type of source media: online
Source contribution:: 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.

Source information:

Originator: Merrick & Company
Title: LIDAR (Light Detection and Ranging)
Source contribution: LIDAR points form the basis of the DTM surface.
Beginning date: 09/08/2004
Ending date: 09/11/2004

Process step:

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.

Process date: 02/17/2005

Process contact:

Doug Jacoby
Senior Project Manager

2450 South Peoria Street
Aurora, CO 80014
Telephone: 303-353-3903
Fax: 303-745-0964
E-Mail: doug.jacoby@merrick.com
Contact instructions: Call or email during business hours

Spatial Data Organization Information:

Spatial Reference Information:

Horizontal coordinate system definition:

Grid coordinate system name: State Plane Coordinate System

SPCS zone identifier: 2500

Lambert conformal conic:

Standard parallel: 45
Standard parallel: 49
Longitude of central meridian: -109.5
Latitude of projection origin: 44.25
False easting: 600000
False northing: 0

Planar distance units: meters

Geodetic model:

Horizontal datum name: North American Datum of 1983
Ellipsoid name: Geodetic Reference System 80
Semi-major axis: 6378137.000000
Denominator of flattening ratio: 298.257222

Altitude system definition:

Altitude datum name: North American Vertical Datum of 1988
Altitude resolution: .001
Altitude distance units: meters
Altitude encoding method:: Explicit elevation coordinate included with horizontal coordinates

Distribution Information:

Distributor:

Montana State Library
P.O. Box 201800
Helena, MT 59620-1800
Telephone: 406-444-5354
E-Mail: geoinfo@mt.gov

Resource description: Downloadable data

Distribution liability:

Standard order process:

Digital form:

Format name: Plain-text ESRI Generate Files
Online option:

Metadata Reference Information:

Metadata date: 11/07/2013

Metadata review date: 05/13/2005

Metadata contact:

Andy Morris
ArcGIS Services Manager
Merrick & Company
2450 South Peoria Street
Aurora, CO 80014
Telephone: 303-353-3929
Telephone: 303-751-0741
Fax: 303-745-0964
E-Mail: andy.morris@merrick.com
Contact instructions: Call or email during business hours