<?xml version="1.0" encoding="ISO-8859-1"?>
<metadata>
<idinfo>
<citation>
<citeinfo>
<origin>EarthData International of Maryland, LLC</origin>
<pubdate>20020900</pubdate>
<pubtime>Unknown</pubtime>
<title>Digital Land Base Mapping of the City of Sturgeon Bay, Door County, WI</title>
<edition>1st Edition</edition>
<geoform>map</geoform>
</citeinfo>
</citation>
<descript>
<abstract>
This metadata document describes the collection and
processing of Light Detection and Ranging (LIDAR) data
of the City of Sturgeon Bay in Door County, Wisconsin.
The resulting data are a bare ground elevation model
generated from LIDAR data and topographic mapping with
a 2&apos; contour interval produced for the United States
Army Corps of Engineers.
</abstract>
<purpose>
This dataset is intended for use by the United States Army
Corps of Engineers for base mapping.
</purpose>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>20020900</caldate>
</sngdate>
</timeinfo>
<current>Publication Date</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>None planned</update>
</status>
<spdom>
<bounding>
<westbc>-087.436039</westbc>
<eastbc>-087.293591</eastbc>
<northbc>44.871042</northbc>
<southbc>44.792001</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>None</themekt>
<themekey>Digital Land Base Mapping</themekey>
<themekey>Light Detection and Ranging (LIDAR)</themekey>
<themekey>Topographic Map</themekey>
</theme>
<place>
<placekt>None</placekt>
<placekey>United States of America (USA)</placekey>
<placekey>Wisconsin (WI)</placekey>
<placekey>Door County (55029)</placekey>
<placekey>City of Sturgeon Bay</placekey>
</place>
</keywords>
<accconst>None</accconst>
<useconst>None</useconst>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>EarthData International of Maryland</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>45 West Watkins Mill Rd</address>
<city>Gaithersburg</city>
<state>MD</state>
<postal>20878</postal>
<country>USA</country>
</cntaddr>
<cntvoice>301-948-8550</cntvoice>
<cntfax>301-963-2064</cntfax>
<cntemail>metadata@earthdata.com</cntemail>
<hours>9:00-5:00 M-F</hours>
</cntinfo>
</ptcontac>
</idinfo>
<dataqual>
<logic>
Height values between individual LIDAR points within a 3.5
meter radius were differentiated against surveyed control
points.  A statistical result was determined and indicated
that the vertical RMSE was +/- 0.15 meters (1 sigma) over the
project area.
The resultant map products are fully compliant with National
Map Accuracy Standards.
</logic>
<complete>
Differences between individual LIDAR points within a 3.5
meter radius were calculated against surveyed control
points.  A statistical result was determined and indicated
that the vertical RMSE was +/- 0.15 meters (1 sigma) for the
entire project.
The following software was used for the validation.
1. Bentley - Microstation
2. Terrasolid - Terrscan
3. Trimble - Terramodel
4. Esri - ArcInfo
5. EarthData Proprietary software
</complete>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>Towill</origin>
<pubdate>20020400</pubdate>
<pubtime>Unknown</pubtime>
<title>Ground Control Survey of Door County, WI</title>
<geoform>model</geoform>
<pubinfo>
<pubplace>Towill, Inc, San Francisco, CA</pubplace>
<publish>Towill</publish>
</pubinfo>
</citeinfo>
</srccite>
<srcscale>14,400</srcscale>
<typesrc>electronic mail system</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>20020400</caldate>
</sngdate>
</timeinfo>
<srccurr>Publication Date</srccurr>
</srctime>
<srccitea>GPS Ground Control</srccitea>
<srccontr>
Ground control was established prior to the acquisition of
aerial data acquisition.The ground control points were
established using GPS for vertical and horizontal
coordinate values. Ground control references the
Wisconsin Central State Plane NAD83, NAVD29, US
Survey Feet.
</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>EarthData Aviation</origin>
<pubdate>20020417</pubdate>
<pubtime>Unknown</pubtime>
<title>LIDAR Coverage of Door County, WI</title>
<geoform>model</geoform>
<pubinfo>
<pubplace>Hagerstown, MD</pubplace>
<publish>EarthData Aviation</publish>
</pubinfo>
</citeinfo>
</srccite>
<typesrc>CD-ROM</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>20020300</caldate>
<time>Unknown</time>
</sngdate>
</timeinfo>
<srccurr>Publication Date</srccurr>
</srctime>
<srccitea>Earthdata Aviation</srccitea>
<srccontr>
The project area was flown using EarthData Aviation&apos;s
Navajo Chieftain aircraft equipped with an AeroScan
LIDAR system, an Inertial Measurement Unit (IMU), and
dual frequency GPS receiver and antennae. The position
and orientation (omega, phi, and kappa) of the aircraft were
determined using a GPS receiver located at an existing
NGS control point.
The LIDAR, IMU, and GPS data were correlated using
GPS time and processed using LIDAR post-processing
software to determine the coordinate of each point on the
ground.  A reflective surface DEM of the project area
was delivered with a relative accuracy of +/- 0.15 meters.
</srccontr>
</srcinfo>
<procstep>
<procdesc>
EarthData has developed a unique method for processing
LIDAR data to identify and remove elevation points falling
on vegetation, buildings, and other above-ground
structures.  The algorithms for filtering data were utilized
within EarthData&apos;s proprietary software and commercial
software written by TerraSolid.  This software suite of tools
provides efficient processing for small to large-scale
projects and has been incorporated into ISO 9001
compliant production work flows.  The following is a
step-by-step breakdown of the process.
1. Using the LIDAR data set provided by EarthData
Aviation, the technician performed a visual inspection of
the data to verify that the flight lines overlap correctly.
The technician also verified that there were no voids, and
that the data covered the project limits. The technician then
selected a series of areas from the dataset and inspected
them where adjacent flight lines overlapped. These
overlapping areas were merged and a process which
utilizes 3-D Analyst and EarthData&apos;s proprietary software
was run to detect and color code the differences in
elevation values and profiles.  The technician reviewed
these plots and located the areas that contained
systematic errors or distortions that were introduced by the
LIDAR sensor.
2. Systematic distortions highlighted in step 1 were
removed and the data were re-inspected.  Corrections
and adjustments can involve the application of angular
deflection or compensation for curvature of the ground
surface that can be introduced by crossing from one type
of land cover to another.
3.The LIDAR data for each flight line were trimmed in batch
for the removal of the overlap areas between flight lines.
The data were checked against a control network to
ensure that vertical requirements were maintained.
Conversion to the client-specified datum and projections
were then completed. The LIDAR flight line data sets were
then segmented into adjoining tiles for batch processing
and data management.
4. The initial batch-processing run removed 95% of points
falling on vegetation.  The algorithm also removed the
points that fell on the edge of hard features such as
structures, elevated roadways and bridges. In addition,
points not classified as ground are coded as
intermediate canopy, top of canopy, building, etc.  Thus
the LIDAR data was classified into thematic layers that
can be analyzed separately or together.
5. The data were processed interactively by the operator
using LIDAR editing tools.  During this final phase the
operator generated a TIN based on a desired thematic
layers to evaluate the automated classification performed in
step 4. This allowed the operator to quickly re-classify
points from one layer to another and recreate the TIN
surface to see the effects of edits.  The use of
geo-referenced images were toggled on or off to aid the
operator in identifying problem areas. The data was also
examined with an automated profiling tool to aid the
operator in the reclassification.
6.The data were separated into a bare-earth DEM.  A grid
fill program was used to fill data voids caused from
reflective objects such as buildings and vegetation. The
final DEM was written as an ASCII file (comma &amp; space
delimited), ESRI Shape file, and an ESRI TIN file to a
CDROM.
</procdesc>
<srcused>EarthData International</srcused>
<procdate>20020900</procdate>
<proccont>
<cntinfo>
<cntperp>
<cntper>Raquel Charrois</cntper>
<cntorg>EarthData International</cntorg>
</cntperp>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>45 West Walkins Mill Road</address>
<city>Gaithersburg</city>
<state>Maryland</state>
<postal>20878</postal>
<country>USA</country>
</cntaddr>
<cntvoice>1-301-948-8550</cntvoice>
<cntfax>1-301-963-2064</cntfax>
<cntemail>international-md@earthdata.com</cntemail>
<hours>9 AM - 5 PM Mon. - Fri.</hours>
</cntinfo>
</proccont>
</procstep>
</lineage>
<cloud>0</cloud>
</dataqual>
<spref>
<horizsys>
<planar>
<gridsys>
<gridsysn>State Plane Coordinate System 1983</gridsysn>
<spcs>
<spcszone>Wisconsin Central (4802)</spcszone>
<lambertc>
<stdparll>44 15 0.0</stdparll>
<stdparll>45 30 0.0</stdparll>
<longcm>-090.000000</longcm>
<latprjo>+43.833333</latprjo>
<feast>600000.0</feast>
<fnorth>0.0</fnorth>
</lambertc>
</spcs>
</gridsys>
<planci>
<plance>coordinate pair</plance>
<coordrep>
<absres>2</absres>
<ordres>2</ordres>
</coordrep>
<plandu>Survey Feet</plandu>
</planci>
</planar>
</horizsys>
<vertdef>
<altsys>
<altdatum>National Geodetic Vertical Datum of 1929</altdatum>
<altres>0.15</altres>
<altunits>Meters</altunits>
<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
</altsys>
</vertdef>
</spref>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>United States Army Corps of Engineers - Detroit District</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>477 Michigan Avenue</address>
<city>Detroit</city>
<state>MI</state>
<postal>48226</postal>
<country>USA</country>
</cntaddr>
<cntvoice>313-226-6751</cntvoice>
</cntinfo>
</distrib>
<distliab>None.</distliab>
</distinfo>
<metainfo>
<metd>20021000</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>EarthData International of Maryland, LLC</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>45 West Watkins Mill Road</address>
<city>Gaithersburg</city>
<state>MD</state>
<postal>20878</postal>
<country>USA</country>
</cntaddr>
<cntvoice>301-948-8550</cntvoice>
<cntfax>301-963-2064</cntfax>
<cntemail>metadata@earthdata.com</cntemail>
<hours>9:00 AM - 5:00 PM (ET) M-F</hours>
</cntinfo>
</metc>
<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
</metainfo>
</metadata>

