Camp Grafton, Devils Lake Topographic Half-Foot Contours 2013

File Geodatabase Feature Class

Tags
Elevation, Model, LiDAR, Terrain, North Dakota, Camp Grafton, US, Surface

Description

This data has been acquired and developed by the National Guard Bureau (NGB) to collect and deliver topographic elevation point data derived from multiple return light detection and ranging (LiDAR) measurements for the 31 sq. mile project area encompassing Camp Grafton, North Dakota. Fugro EarthData, Inc. acquired 36 flight lines in 1 lift on December 5, 2012. LiDAR data collection was performed with a Cessna 310 twin engine aircraft, utilizing a Leica ALS60 MPiA sensor; collecting multiple return x, y, and z as well as intensity data. The classified LiDAR point cloud data are delivered in LAS 1.3 format: 1 – unclassified, 2 – ground, 3 – low vegetation, 5 – high vegetation, 6 – buildings, 7 – low points, 8 – model keypoints, 9 – water, and 10 – reserved, 12 – overlap points. Specialized in-house and commercial software processes the native LiDAR data into 3-dimensional positions that can be imported into GIS software for visualization and further analysis. The horizontal datum for the data is geographic Coordinates, NAD83(2011) in meters and the vertical datum is the North American Vertical Datum of 1988 (NAVD88) in meters using GEIOD12A.


Summary

The purpose of the work is for land development, encroachment, unit training and installation planning. The data is to be acquired during leaf off conditions in the fall of 2012. The project consists of high accuracy classified LiDAR data in LAS format as well as a combination of raster digital elevation models and contours.

Credits

USACE, St. Louis District

Use limitations

Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations.

Scale Range

Metadata 

Topics and Keywords 

Themes or categories of the resource  elevation


*Content type  Downloadable Data

Place keywords  North Dakota, Camp Grafton, US

Thesaurus
Title Geographic Names Information System




Theme keywords  Elevation, Model, LiDAR, Terrain, Surface

Thesaurus
Title Keywords




Citation 

Title Camp Grafton, Devils Lake Topographic Half-Foot Contours 2013
Publication date 2013-05-02 00:00:00


Edition v.01


Presentation formats  hardcopy map
FGDC geospatial presentation format  map


Citation Contacts 

Responsible party
Organization's name Fugro EarthData, Inc.
Contact's role  publisher


Contact information
Address
Type
Delivery point Frederick, Maryland



Responsible party
Organization's name Fugro EarthData, Inc.
Contact's role  originator


Resource Details 

Dataset languages  English (UNITED STATES)
Dataset character set  utf8 - 8 bit UCS Transfer Format


Status  completed
Spatial representation type  vector


Supplemental information
*Processing environment Microsoft Windows 7 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS 10.3.1.4959


Credits
USACE, St. Louis District

*Name elevation_contour

Extents 

Extent
Geographic extent
Bounding rectangle
West longitude -98.969379
East longitude -98.601456
South latitude 487.647846
North latitude 48.112049

Vertical extent
*Minimum value -0.000023
*Maximum value 536.499977


Extent
Description
ground condition

Temporal extent
Date and time 2012-12-05 00:00:00

Vertical extent
*Minimum value -0.000023
*Maximum value 536.499977


Extent
Geographic extent
Bounding rectangle
Extent type  Extent used for searching
*West longitude -98.969379
*East longitude -98.601458
*North latitude 48.112048
*South latitude 47.647846
*Extent contains the resource Yes

Extent in the item's coordinate system
*West longitude 502299.670000
*East longitude 529665.350000
*South latitude 5277236.570000
*North latitude 5328754.500000
*Extent contains the resource Yes

Resource Points of Contact 

Point of contact
Organization's name USACE, St. Louis District
Contact's role  point of contact


Contact information
Phone
Voice 314-331-8389

Address
Type both
Delivery point 1222 Spruce Street
City St. Louis
Administrative area Missouri
Postal code 63103
Country US



Resource Maintenance 

Resource maintenance
Update frequency  as needed


Resource Constraints 

Legal constraints
Limitations of use
Any conclusions drawn from the analysis of this information are not the responsibility of the USACE, St. Louis District or its partners.

Security constraints
Classification  unclassified
Classification system None


Additional restrictions
N/A



Constraints
Limitations of use

Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations.


Spatial Reference 

ArcGIS coordinate system
*Type Projected
*Geographic coordinate reference GCS_NAD_1983_2011
*Projection NAD_1983_2011_UTM_Zone_14N
*Coordinate reference details
Projected coordinate system
Well-known identifier 102383
X origin -5120900
Y origin -9998100
XY scale 10000
Z origin -882.74182350000001
Z scale 10000
M origin -100000
M scale 10000
XY tolerance 0.001
Z tolerance 0.001
M tolerance 0.001
High precision true
Latest well-known identifier 6343
VCSWKID  5703
LatestVCSWKID  5703
Well-known text PROJCS["NAD_1983_2011_UTM_Zone_14N", GEOGCS["GCS_NAD_1983_2011", DATUM["D_NAD_1983_2011", SPHEROID["GRS_1980", 6378137.0, 298.257222101]], PRIMEM["Greenwich", 0.0], UNIT["Degree", 0.0174532925199433]], PROJECTION["Transverse_Mercator"], PARAMETER["False_Easting", 500000.0], PARAMETER["False_Northing", 0.0], PARAMETER["Central_Meridian", -99.0], PARAMETER["Scale_Factor", 0.9996], PARAMETER["Latitude_Of_Origin", 0.0], UNIT["Meter", 1.0], AUTHORITY["EPSG", 6343]], VERTCS["NAVD_1988", VDATUM["North_American_Vertical_Datum_1988"], PARAMETER["Vertical_Shift", 0.0], PARAMETER["Direction", 1.0], UNIT["Meter", 1.0], AUTHORITY["EPSG", 5703]]

Reference system identifier
*Value 6343
*Codespace EPSG
*Version 8.6.2


Spatial Data Properties 

Vector
*Level of topology for this dataset  geometry only


Geometric objects
Feature class name elevation_contour
*Object type  composite
*Object count 18518



ArcGIS Feature Class Properties
Feature class name elevation_contour
*Feature type Simple
*Geometry type Polyline
*Has topology FALSE
*Feature count 18518
*Spatial index TRUE
*Linear referencing TRUE



Data Quality 

Scope of quality information
Resource level  dataset




Data quality report - Conceptual consistency
Measure description
Compliance with the accuracy standard was ensured by the collection of ground control and the establishment of a GPS base station at the operation airport. The following checks were performed: 1) The LiDAR data accuracy was validated by performing a full boresight adjustment and then checking it against the ground control prior to generating a digital terrain model (DTM) or other products. 2) LiDAR elevation data was validated through an inspection of edge matching and visual inspection for quality (artifact removal).





Data quality report - Completeness omission
Measure description
The following methods are used to ensure LiDAR data accuracy: 1) Use of a ground control network utilizing GPS survey techniques; 2) Use of airborne GPS and IMU in conjunction with the acquisition of LiDAR; and 3) Measurement of quality control ground survey points within the finished product. The following software is used for the validation: 1) Terrascan and 2) Fugro EarthData, Inc. Proprietary Software.





Data quality report - Quantitative attribute accuracy
Measure description
During LiDAR data collection the airborne GPS receiver was collecting data at 2 Hz frequency and the Dilution of Precision (PDOP) was monitored. One GPS base station was also running at the operation airport and was recording data at 1 Hz. The airborne GPS data was post-processed in DGPS mode together with the base station data to provide high accuracy aircraft positions. The GPS trajectory then was combined with the IMU data using loosely coupled approach to yield high accuracy aircraft positions and attitude angles. Then the LiDAR data was processed using the aircraft trajectory and raw LiDAR data. After boresighting the LiDAR data, the ground control points were measured against the LiDAR data by technicians using TerraScan and proprietary software and the LiDAR data was adjusted vertically to the ground control. Independent ground control check points were used to ensure vertical accuracy of the data. The horizontal datum for the data is geographic Coordinates, NAD83(NA2011) in meters and the vertical datum is the North American Vertical Datum of 1988 (NAVD88) in meters. The vertical datum was realized through the use of the published/calculated ellipsoidal heights of the base station to process the aircraft trajectory and then later applying the GEOID12A model to the processed LiDAR data to obtain orthometric heights.





Data quality report - Absolute external positional accuracy
Dimension vertical


Measure description
Accuracyz = RMSEz X 1.9600 at the 95% confidence level. However the RMSE is only valid when the errors follow a normal distribution which may not always be the case with LiDAR data particularly in vegetated land cover categories. Therefore the data will also be tested using the ASPRS/NDEP method which acknowledges that vegetated land cover may not follow a normal error distribution. The ASPRS/NDEP methods mandate the use of Fundamental Vertical Accuracy (FVA) in open terrain and provides for the optional use of Supplemental Vertical Accuracy (SVA) in other individual land cover categories and Consolidated Vertical Accuracy (CVA) in all land cover categories combined. FVA is calculated at the 95th percent confidence level as a function of RMSEz. SVA and CVA are calculated at the 95th percentile, where 95% of elevations errors have elevation errors equal to or less that the 95th percentile. The test results for this project are as follows: Tested 0.05 meters fundamental vertical accuracy at 95% confidence level in open terrain using RMSEz X 1.9600. Tested 0.0.26 meters supplemental vertical accuracy at 95th percentile in High Vegetation. Tested 0.08 meters supplemental vertical accuracy at 95th percentile in Low Vegetation. Tested 0.23 meters consolidated vertical accuracy at 95th percentile in All Land Cover categories





Lineage 

Process step
When the process occurred 2013-04-28 00:00:00
Description
The following step-by-step procedure was utilized for DTM development and contour generation. The DTM file is composed of random data points (X,Y and Z) and three dimensional breaklines. The relationship of points to breaklines and the density and position of points will vary depending on the complexity and severity of the terrain. Breaklines are collected as needed along the edges of roads, stream banks and centerlines, ridges, and other features where the slope of the terrain changes and where necessary. 1) In editing, TerraSolid modules TerraScan and TerraModeler were used to automatically define and thin the points needed for any terrain change. 2) The cartographic editor performed an accuracy evaluation for each DSM and DTM file. This step was accomplished in Global Mapper by a visual inspection of the dataset in profile view to identify spikes or pits in the mass point information. The technician also verified that sufficient coverage exists for each file. 3) The filtered DSM and breaklines compiled along streams, ridge lines, roads, hydrographic features, bridges, and other areas of topographic significance were QCed in MicroStation before generating the contour deliverables. 4) Following the compilation of the breaklines a technician brings the LAS data and the breakline data into the TerraSolid software suite. A process within the TerraScan module known as Contour Keypoint is run. This process analyzes all available data (LAS and breaklines) and filters it leaving only those critical points and breaklines necessary to support the desired output, in this case 0.5 foot contours. The results are reviewed for quality and completeness and then a batch contour generation process is started. During this step contours are generated over the entire project area. A conversion from Microstation dgn format to an Arc GeoDatabase was than processed. 5) In an ESRI Arc environment the technician set the required project datum and projection and created a TIN (triangulated irregular network). Final edit work is done on the data to convert it to the desired GeoDataBase deliverable. The dataset was viewed over the orthos before the final conversion. The contours were then converted to Arc/Info where final QC ARC Topology was run to verify that no contours were crossing. The contours were delivered as a merged file in ArcGIS File-GeoDataBase.



Process contact
Individual's name Richard McClellan
Organization's name Fugro EarthData, Inc.
Contact's position Project Manager
Contact's role  processor


Contact information
Phone
Voice 301.948.8550
Fax 301.963.2064

Address
Type both
Delivery point 7320 Executive Way
City Frederick
Administrative area MD
Postal code 21704
Country US
e-mail addressrmcclellan@fugro.com

Hours of service
Mon-Fri 8:30am to 5:00pm



Source data
Relationship to the process step used


Source citation
Alternate titles  LiDAR, 3D Breaklines






Source data
Relationship to the process step produced


Source citation
Alternate titles  Contours








Source data
Description
Fugro EarthData utilized commercial software as well as proprietary software for automatic filtering. The parameters used in the process were customized for each terrain type to obtain optimum results. Once the automated filtering was completed, the files were run through a visual inspection to ensure that the filtering was not too aggressive or not aggressive enough. In cases where the filtering was too aggressive and important terrain features were filtered out, the data was either run through a different filter within local area or was corrected during the manual filtering process. Interactive editing was then completed in visualization software that provides manual and automatic point classification tools using commercial and proprietary software for the process. Vegetation and artifacts remaining after automatic data post-processing were reclassified manually through interactive editing. The hard edges of ground features that were automatically filtered out during the automatic filtering process were brought back into ground class during manual editing. The technician then reviewed the LiDAR points with color shaded TINs for anomalies in ground class during interactive filtering. Upon the completion of peer review and finalization of bare earth filtering, the classified LiDAR point cloud work tiles went through a water classification routine. Upon the completion of finalization of the classified LiDAR point cloud work tiles, the tiles were re-projected to UTM Zone 15 north; NAD83(2011), meters; NAVD88 (GEOID12A),meters. The data was also cut to the approved tile layout and clipped to the approved project boundary.



Source citation
Title Classified LiDAR Point Cloud Data
Alternate titles  Classified LiDAR Point Cloud
Publication date 2013-01-08


Responsible party
Organization's name Fugro EarthData, Inc.
Contact's role  originator




Extent of the source data
Description
Publication Date

Temporal extent
Date and time 2012-12-05



Source data
Description
The hydrographic features were collected as vector linework using classified LiDAR datasets, intensity images, shaded-relief TIN surfaces, and contours. The following is a step-by-step breakdown of the process: 1) The hydro features were collected as: a) Inland Ponds and Lakes: Edges of non-flowing (static) waterbodies, ~2 acres in area and b) Inland Streams and Rivers: Edges of flowing waterbodies, nominally wider than 100 feet. 2) After initial collection, linework was then checked for the following topological and attribution rules: a) Lines must be attributed with the correct feature code; and b) Lakes, ponds, and shore/bay must form closed polygons. 3) Hydro features were collected as vector linework using LiDAR and its derived products listed above. This linework is initially 2D, meaning that it does not have elevation values assigned to individual line vertices. Vertex elevation values were assigned using IDW (Inverse Distance Weighted) Interpolation. After the initial vertex elevation was assigned, the linework elevation values were further adjusted based on the following rules: a) Lake feature vertices were re-assigned (flattened) to lowest vertex elevation value; b) Stream connector line vertices were adjusted so that subsequent vertices are lower than previous ones based on line direction; and c) Double stream bankline vertices were re-assigned based on the vertices of the closest adjusted double stream connector line. 4) After assignment of 3D values, the stream network is checked to ensure the following does not exist: a) Large differences between initial assigned elevation and adjusted elevation values; b) Elevation differences between nodes; and c) Elevation values flowing in an 'downhill' direction. 5) The hydro breaklines were delivered to the terrain department for hydro-flattening of the DEM in ESRI GeoDataBase format.



Source citation
Title Hydro Breaklines
Alternate titles  Hydro Breaklines
Publication date 2013-02-07


Responsible party
Organization's name Fugro EarthData, Inc.
Contact's role  originator




Extent of the source data
Description
Publication Date

Temporal extent
Date and time 2012-12-05



Source data
Description
TerraSurv under contract to Fugro EarthData, Inc. successfully established ground control for Camp Grafton, ND. A total of 8 ground control points along with 73 check points; 31 in open terrain, 21 in low vegetation, and 21 in high vegetation were acquired. GPS was used to establish the control network. The horizontal datum was the North American Datum of 1983(2011). The vertical datum was the North American Vertical Datum of 1988 (NAVD88) using GEOID12A.



Source medium name  online link
Source citation
Title Report of Survey
Alternate titles  Ground Control
Publication date 2013-01-02


Responsible party
Organization's name TerraSurv
Contact's role  originator




Extent of the source data
Description
Ground Condition

Temporal extent
Beginning date 2012-10-22
Ending date 2012-10-24



Source data
Description
Fugro EarthData, Inc. collected ALS60-derived LiDAR over Camp Grafton, North Dakota with a 0.7 meter, nominal post spacing using a Cessna 310 twin engine aircraft. Data was collected when environmental conditions meet the criteria specified. To be specific, the following conditions existed prior to launch of the aircraft: 1) Streams and rivers were within their normal banks, 2) Snow free, 3) smoke free and fog-free, 4) Air traffic restrictions were accounted for (flight crews coordinated with air traffic controllers and the military facility prior to data collection), and 5) Leaf off. The collection for the entire project area was accomplished on December 5, 2012; 36 flight lines were acquired in 1 lift; The lines were flown at an average of 6100 feet altitude. The collection was performed using Leica ALS60 MPiA LiDAR systems, serial number 142.



Source citation
Title Aerial Acquisition
Alternate titles  Aerial LiDAR Acquisition
Publication date 2012-05-13


Responsible party
Organization's name Fugro EarthData, Inc.
Contact's role  originator




Extent of the source data
Description
ground condition

Temporal extent
Date and time 2012-12-05



Distribution 

Distributor
Contact information
Organization's name USACE, St. Louis District
Contact's role  distributor


Contact information
Phone
Voice 314-331-8389

Address
Type both
Delivery point 1222 Spruce Street
Delivery point USACE, St. Louis District
City St. Louis
Administrative area Missouri
Postal code 63103
Country US

Hours of service
Monday through Friday 8:00 AM to 4:00 PM (Central Time)

Contact instructions
The above is the contact information for USACE St. Lous District





Distribution format
*Name File Geodatabase Feature Class


Fields 

Details for object elevation_contour 
*Type Feature Class
*Row count 18518


Field OBJECTID
 
*Alias OBJECTID
*Data type OID
*Width 4
*Precision 0
*Scale 0
*Field description
Internal feature number.

*Description source
ESRI

*Description of values
Sequential unique whole numbers that are automatically generated.





Field Shape
 
*Alias Shape
*Data type Geometry
*Width 0
*Precision 0
*Scale 0
*Field description
Feature geometry.

*Description source
ESRI

*Description of values
Coordinates defining the features.





Field Handle
 
*Alias Handle
*Data type String
*Width 16
*Precision 0
*Scale 0




Field Elevation
 
*Alias Elevation
*Data type Double
*Width 8
*Precision 0
*Scale 0




Field DGN_LEVEL
 
*Alias Level
*Data type Integer
*Width 4
*Precision 0
*Scale 0




Field OBJECTID_1
 
*Alias OBJECTID
*Data type Integer
*Width 4
*Precision 0
*Scale 0




Field SUBTYPEID
 
*Alias SubType identifier
*Data type Integer
*Width 4
*Precision 0
*Scale 0


Subtype information
*Subtype name (Subtype code)
INDEX (200967)
200967
INTER (200970)
200967
INDEX_DEP (200964)
200967
INTER_DEP (200973)
200967



Field DATALINK
 
*Alias Unique Data Identifier
*Data type Integer
*Width 4
*Precision 0
*Scale 0




Field CONTOUR_ID
 
*Alias Primary Key Identifier
*Data type String
*Width 20
*Precision 0
*Scale 0




Field MAP_ID
 
*Alias FOREIGN KEY JOIN to cmgenmap
*Data type Integer
*Width 4
*Precision 0
*Scale 0




Field META_ID
 
*Alias FOREIGN KEY JOIN to cmgenmet
*Data type String
*Width 20
*Precision 0
*Scale 0




Field MEDIA_ID
 
*Alias FOREIGN KEY JOIN to cmmedmed
*Data type String
*Width 20
*Precision 0
*Scale 0




Field COORD_ID
 
*Alias FOREIGN KEY JOIN to cmgencrd
*Data type String
*Width 20
*Precision 0
*Scale 0




Field CNTR_TYP_D
 
*Alias Type Discriminator Code
*Data type String
*Width 16
*Precision 0
*Scale 0


Subtype information
*Subtype name (Subtype code)
INDEX (200967)
no default value
INTER (200970)
no default value
INDEX_DEP (200964)
no default value
INTER_DEP (200973)
no default value

*Domain name d_cnttyp
*Description discriminator - contour
*Type Coded Value
*Merge rule Default value
*Split rule Duplicate



Field ELEVATION_1
 
*Alias Elevation Dimension
*Data type Integer
*Width 4
*Precision 0
*Scale 0




Field ELEV_U_D
 
*Alias Elevation Unit of Measure Code
*Data type String
*Width 16
*Precision 0
*Scale 0


Subtype information
*Subtype name (Subtype code)
INDEX (200967)
no default value
INTER (200970)
no default value
INDEX_DEP (200964)
no default value
INTER_DEP (200973)
no default value

*Domain name d_uomdis
*Description unit of measure - distance
*Type Coded Value
*Merge rule Default value
*Split rule Duplicate



Field USER_FLAG
 
*Alias User Flag Text
*Data type String
*Width 20
*Precision 0
*Scale 0




Field INSTLN_ID
 
*Alias FOREIGN KEY JOIN to cddodins
*Data type String
*Width 20
*Precision 0
*Scale 0




Field INSTNAME
 
*Alias INSTNAME
*Data type String
*Width 30
*Precision 0
*Scale 0




Field FACIL_ID
 
*Alias FOREIGN KEY JOIN to cmgenfac
*Data type String
*Width 20
*Precision 0
*Scale 0




Field GRID_VALUE
 
*Alias Graphic Attribute Raster GValue
*Data type Double
*Width 8
*Precision 0
*Scale 0




Field COORD_X
 
*Alias X Coordinate
*Data type Double
*Width 8
*Precision 0
*Scale 0




Field COORD_Y
 
*Alias Y Coordinate
*Data type Double
*Width 8
*Precision 0
*Scale 0




Field COORD_Z
 
*Alias Z Coordinate
*Data type Double
*Width 8
*Precision 0
*Scale 0




Field FRCOORD_X
 
*Alias From X Coordinate
*Data type Double
*Width 8
*Precision 0
*Scale 0




Field FRCOORD_Y
 
*Alias From Y Coordinate
*Data type Double
*Width 8
*Precision 0
*Scale 0




Field FRCOORD_Z
 
*Alias From Z Coordinate
*Data type Double
*Width 8
*Precision 0
*Scale 0




Field TOCOORD_X
 
*Alias To X Coordinate
*Data type Double
*Width 8
*Precision 0
*Scale 0




Field TOCOORD_Y
 
*Alias To Y Coordinate
*Data type Double
*Width 8
*Precision 0
*Scale 0




Field TOCOORD_Z
 
*Alias To Z Coordinate
*Data type Double
*Width 8
*Precision 0
*Scale 0




Field FEAT_LEN
 
*Alias Feature Length Dimension
*Data type Double
*Width 8
*Precision 0
*Scale 0




Field FEAT_NAME
 
*Alias Feature Name
*Data type String
*Width 64
*Precision 0
*Scale 0




Field VERT_DAT_D
 
*Alias Vertical Datum Code
*Data type String
*Width 16
*Precision 0
*Scale 0


Subtype information
*Subtype name (Subtype code)
INDEX (200967)
no default value
INTER (200970)
no default value
INDEX_DEP (200964)
no default value
INTER_DEP (200973)
no default value

*Domain name d_metadn
*Description metadata - altitude datum name
*Type Coded Value
*Merge rule Default value
*Split rule Duplicate



Field LENGTH_U_D
 
*Alias Length Unit of Measure Code
*Data type String
*Width 16
*Precision 0
*Scale 0


Subtype information
*Subtype name (Subtype code)
INDEX (200967)
no default value
INTER (200970)
no default value
INDEX_DEP (200964)
no default value
INTER_DEP (200973)
no default value

*Domain name d_uomdis
*Description unit of measure - distance
*Type Coded Value
*Merge rule Default value
*Split rule Duplicate



Field STATE
 
*Alias STATE
*Data type String
*Width 30
*Precision 0
*Scale 0




Field SOURCETHM
 
*Alias SOURCETHM
*Data type String
*Width 30
*Precision 0
*Scale 0




Field cntr_typ_id
 
*Alias cntr_typ_id
*Data type String
*Width 50
*Precision 0
*Scale 0




Field SHAPE_Length_1
 
*Alias SHAPE_Length
*Data type Double
*Width 8
*Precision 0
*Scale 0




Field Shape_Length
 
*Alias Shape_Length
*Data type Double
*Width 8
*Precision 0
*Scale 0
*Field description
Length of feature in internal units.

*Description source
ESRI

*Description of values
Positive real numbers that are automatically generated.







Overview Description
Entity and Attribute Overview
Leica ALS60 MPiA sensor; 0.7m nominal post spacing



Entity and Attribute Detail Citation
see process steps within this record





Metadata Details 

Metadata language English (UNITED STATES)
Metadata character set  utf8 - 8 bit UCS Transfer Format


Scope of the data described by the metadata  dataset
Scope name* dataset


*Last update 2016-02-26


ArcGIS metadata properties
Metadata format ArcGIS 1.0
Metadata style FGDC CSDGM Metadata
Standard or profile used to edit metadata FGDC


Created in ArcGIS for the item 2013-12-06 09:47:50
Last modified in ArcGIS for the item 2016-02-26 11:44:08


Automatic updates
Have been performed Yes
Last update 2016-02-26 11:44:08


Metadata Contacts 

Metadata contact
Organization's name USACE, St. Louis District
Contact's role  point of contact


Contact information
Phone
Voice 314-331-8389

Address
Type both
Delivery point USACE, St. Louis District
Delivery point 1222 Spruce Street
City St. Louis
Administrative area Missouri
Postal code 63103
Country US

Hours of service
Monday through Friday 8:00 AM to 4:00 PM (Central Time)

Contact instructions
The above is the contact information for USACE St. Lous District



Metadata Maintenance 

Maintenance
Update frequency  unknown


Other maintenance requirements
Last metadata review date: 20130502