{47A8C7BE-658E-4B12-B542-94268D8A78E8}2011040903525200FALSE20110409045729002011040911410400Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.0.1770enDigital Terrain Model in ESRI GRID formatThe purpose of this survey is to provide the Vicksburg District with bare earth and top surface elevation data for providing geometry input to USACE hydraulic modeling programs.USACE, Vicksburg DistrictUnpublished MaterialMSD3_DTM_GRIDraster digital dataground condition20091200201007In workAs needed-90.092421-88.82690334.98322333.6678272369875.7100002747898.5500001519327.1000001994875.850000GridBare-EarthDigital Terrain ModelDigital Elevation ModelMississippiData are to be used by U.S. Government personnel only unless a written request to the USACE, Vicksburg District POC has been approved.Users must abide by the terms of the non-disclosure agreement or the data sharing agreement under which the geospatial data were obtained.GRIDElijah C. HuntU.S. Army Corps of Engineers, Vicksburg Districtmailing and physical address

4155 East Clay St

VicksburgMS39183-3435USA(601) 631-7040elijah.c.hunt@us.army.milUnclassifiedMicrosoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.0.1770MSD3_DTM_GRID2369875.712747898.551994875.851519327.11-90.092421-88.82690334.98322333.6678271enFGDC Content Standards for Digital Geospatial MetadataFGDC-STD-001-1998local timeElijah C. HuntUSACE, Vicksburg Districtmailing and physical addressVicksburgMS39183-3435

4155 East Clay St

USA(601) 631-7040elijah.c.hunt@us.army.mil20110409Unclassifiedhttp://www.esri.com/metadata/esriprof80.htmlESRI Metadata ProfileISO 19115 Geographic Information - MetadataDIS_ESRI1.0datasetDownloadable DataGRIDU.S. Army Corps of Engineers, Vicksburg District002file://\\FLIGHT11\E$\Deliveries\MS_Delta\20471_MXD\SHAPES\MSD3_DTM_GRIDLocal Area Network0.185ShapefileRasterGrid Cell5 feet5 feetGCS_North_American_1983NAD_1983_StatePlane_Mississippi_West_FIPS_2302_Feetcoordinate pairsurvey feet0.0000000.000000Transverse Mercator0.999950-90.33333329.5000002296583.3333330.000000North American Datum of 1983Geodetic Reference System 806378137.000000298.257222North American Vertical Datum of 1988feetNAD_1983_StatePlane_Mississippi_West_FIPS_2302_Feet124720110409Aeroquest Optimal, Inc.Unpublished Materialvector digital data2009120020100700ground conditionChris JaegerAeroquest Optimal, Inc.Project Managermailing and physical address

4975 Bradford Dr. NW, Ste 100

HuntsvilleAL35805USA(256) 882-7788chris.jaeger@optimalgeo.comDATA ACQUISITION: - Ground Control Survey: A ground control survey was conducted for the purpose of establishing aerial targets to validate the accuracy of the LiDAR and imagery data. LiDAR test points were collected using RTK methods in accordance with FEMA guidelines and were used to validate the vertical accuracy of the LiDAR data. - LiDAR Acquisition: The LiDAR data was collected using a combination of three OPTECH ALTM sensores (3100, 3100EA, and Gemini). Planned acquisition altitudes of 1,000m for the 3100 and 3100EA and 1,800' for the Gemini were used to support the generation of elevation data capable of supporting 2' contours meeting ASPRS Class 1 vertical accuracy standards. The LiDAR collection was support by two ground base stations positioned so that the aircraft was no further than 20-miles from a base station at any given time during flight.20100700Chris JaegerAeroquest Optimal, Inc.Project Managermailing and physical address

4975 Bradford Dr NW, Ste 100

HuntsvilleAL35805USA(256) 882-7788chris.jaeger@optimalgeo.comLIDAR PROCESSING: - LiDAR Calibration: Initial processing of the GPS data was processed using POSPC MMS. The SBET was generated and DASHMap software was used to generate georeferenced laser returns which were then processed in strip form allowing for the QC of the overlap between strips (lines). The data from each line were combined and automated classification routines run to determine the initial surface model. This initial surface model was then verified to the LiDAR test points. - LiDAR Classification: The calibrated LiDAR data was run through automated classification routines and then manually checked. The data was classified int the following classes: ground, hydrography, unclassified. - Breakline Collection: LiDARgrammetry was used to collect hydro-enforced breaklines in stereo using synthetic stereo pairs generated in GeoCue using the LiDAR Intensity data. The data was collected in the MicroStation environment and then converted into 3D shapefile format for inclusion in the Digital Elevation Models. - Contour Generation: Two-foot contours were generated and checked using TerraModeler. The contours were then imported into Shapefile format and the topology validated. They were clipped to the tile boundaries for delivery.20110400Chris JaegerAeroquest Optimal, Inc.Project Managermailing and physical address

4975 Bradford Dr NW, Ste 100

HuntsvilleAL35805USA(256) 882-7788chris.jaeger@optimalgeo.comGRID CREATION: - Ground LiDAR LAS points were converted into multipoint format by tile with a 10 foot buffer using LP360. The breaklines were converted from DGN to ESRI 3D polyline format and then clipped using ETGeoWizard's Split by location tool to the tile index with a 10-foot buffer. The TINs were then generated using ESRI's ArcGIS 3D Analyst Create TIN tool using the bare-earth multipoint file as a mass point input, the breaklines as a hard line input with elevations obtained from the shapefile geometry. The index was also used as hard clip input to clip the TIN files neatly to the tile boundaries. - The TINs were then inspected for errors by converting them to hillshades and viewing them in ArcGIS for anomolies. Further inspection of the surfaces were conducted prior to TIN generation by visually inspecting the contours for anomolies (see metadata for contour generation). - The GRIDs were then generated for each tile using ESRI's 3D Analyst Tin to Raster tool.20110400Attribute value domains and ranges are verified against a set domain of values according to SDSFIE. Content is populated according to the Standard Operating Procedures for that layer. Specific value content is verified by and authority with site knowledge and access to other sources.Topological integrity of the data was validated using the validation tools in ESRI's ArcGIS 9.3.Complete data set.The expected horizontal accuacy of elevation products derived using the OPTECH 3100 LiDAR sensor as determined from system studies and other methods is 1/2000 of the flight height, which in the instance of this particular project was 1000m (3280.8 feet), giving a horizontal tolerance of less than 0.5m (1.64 survey feet).The DEMs for these survey areas are believed to be accurate. The inclusion of breaklines collected from the LiDAR data provides for a more accurate DEM around hydro edges than could be achieved with the LiDAR points alone. The data was processed in four separate acquisition areas and accuracy was reported by area (see LiDAR DEM Quality Report for details). The accuracy statements below are based on the area having the highest RMSE(z) for all four areas and therefore some areas are of higher quality than this. The following statements are derived in accordance with the ASPRS Guidelines for Vertical Accuracy Reporting for LiDAR Data (Flood, M., 2004). Tested 0.34 US Survey Foot fundamental vertical accuracy at the 95% confidence level in open terrain using RMSE(z) x 1.9600. Tested 0.56 US Survey Foot consolidated vertical accuracy at the 95% confidence level in open terrain, low & high grass, and treed areas using RMSE(z) x 1.9600.0%