<?xml version="1.0" encoding="UTF-8"?><metadata>
<idinfo>
<citation>
<citeinfo>
<origin>EarthData International</origin>
<pubdate>20050308</pubdate>
<title Sync="FALSE">Contours2004</title>
<geoform Sync="TRUE">vector digital data</geoform>
<ftname Sync="FALSE">Contours2004</ftname>
<onlink Sync="FALSE">withheld</onlink>
</citeinfo>
</citation>
<descript>
<abstract>
This metadata record describes the development of a
bare earth digital terrain model and contours from lidar of
Rutherford County.
</abstract>
<purpose>
Rutherford County has contracted the production of digital
terrain models and contours from LIDAR data to support
land-use planning, risk-assessment and emergency
response agencies.
</purpose>
<langdata Sync="TRUE">en</langdata>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>20050308</caldate>
</sngdate>
</timeinfo>
<current>Publication Date</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>Unknown</update>
</status>
<spdom>
<bounding>
<westbc Sync="TRUE">-86.703807</westbc>
<eastbc Sync="TRUE">-86.141303</eastbc>
<northbc Sync="TRUE">36.102035</northbc>
<southbc Sync="TRUE">35.616926</southbc>
</bounding>
<lboundng>
<leftbc Sync="TRUE">1760579.136488</leftbc>
<rightbc Sync="TRUE">1926502.531478</rightbc>
<bottombc Sync="TRUE">467977.625389</bottombc>
<topbc Sync="TRUE">643850.639793</topbc>
</lboundng>
</spdom>
<keywords>
<theme>
<themekt>EDI Thesaurus</themekt>
<themekey>LIDAR</themekey>
<themekey>Digital Elevation Model</themekey>
<themekey>Reflective Surface</themekey>
<themekey>Digital Terrain Model</themekey>
<themekey>Bare Earth</themekey>
<themekey>Breaklines</themekey>
<themekey>Contours</themekey>
</theme>
<place>
<placekt>Geographic Names Information System</placekt>
<placekey>Rutherford County</placekey>
<placekey>Tennessee</placekey>
</place>
</keywords>
<accconst>None</accconst>
<useconst>None</useconst>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>Earth Data International</cntorg>
<cntper>Raquel Charrois</cntper>
</cntorgp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>7320 Executive Way</address>
<city>Frederick</city>
<state>Maryland</state>
<postal>21704</postal>
<country>USA</country>
</cntaddr>
<cntvoice>(301)948-8550</cntvoice>
<hours>Mon - Fri 9:00 am to 5:00 pm</hours>
</cntinfo>
</ptcontac>
<native Sync="FALSE">ESRI ArcCatalog 9.2.2.1350</native>
<natvform Sync="FALSE">Feature Class</natvform>
</idinfo>
<dataqual>
<attracc>
<attraccr>
This data has been produced to be fully compliant with
National Map Accuracy Standards for mapping at a scale
of 1 to 1,200.
</attraccr>
</attracc>
<logic>
Compliance with the accuracy standard was ensured by
the placement of GPS ground control prior to the
acquisition of aerial photography. The following checks
were performed.
1. The ground control and airborne GPS/IMU data stream
were validated through a "bore site" calibration sensor
overflight.
2. The lidar was checked against the
project control. The technician visited and confirmed the
accuracy of the points during initial processing.
</logic>
<complete>
The following methods are used to assure imagery
accuracy.
1. Use of IMU and ground control network utilizing GPS
techniques.
The following software was used for the validation.
1. Bentley - Microstation
2. Terrasolid - Terrascan
3. Trimble - Terramodeler
4. ESRI - ArcInfo
6. EarthData Proprietary software
Ensuring the National Standard for Spatial Data Accuracy
(NSSDA) published by the Federal Geographic Data
Committee (FGDC) in 1998 standards are met.
</complete>
<posacc>
<horizpa>
<horizpar>
The LIDAR data fully complies with National Map
Accuracy Standards for production of 2 foot contours.
</horizpar>
</horizpa>
<vertacc>
<vertaccr>
The LIDAR data fully complies with National Map
Accuracy Standards for production of 2 foot contours.
</vertaccr>
</vertacc>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>BWSC</origin>
<pubdate>20060406</pubdate>
<title>GPS Ground Control</title>
<geoform>model</geoform>
</citeinfo>
</srccite>
<srcscale>1200</srcscale>
<typesrc>electronic mail system</typesrc>
<srctime>
<timeinfo>
<rngdates>
<begdate>20040224</begdate>
<enddate>20040226</enddate>
</rngdates>
</timeinfo>
<srccurr>Ground Condition</srccurr>
</srctime>
<srccitea>Ground Control</srccitea>
<srccontr>
BWSC, under contract to EarthData International of
Maryland targeted 50 locations prior to aerial imagery
acquisition. The points were surveyed using GPS for both
vertical and horizontal coordinate values. Ground control
references Tennessee State Plane NAD83, NAVD88 both
in US Survey Feet.
</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>EarthData Aviations</origin>
<pubdate>20040412</pubdate>
<title>Rutherford County LIDAR Acquisition</title>
<geoform>profile</geoform>
</citeinfo>
</srccite>
<srcscale>1200</srcscale>
<typesrc>firewire</typesrc>
<srctime>
<timeinfo>
<rngdates>
<begdate>20040311</begdate>
<enddate>20040322</enddate>
</rngdates>
</timeinfo>
<srccurr>Ground Condition</srccurr>
</srctime>
<srccitea>Acquisition</srccitea>
<srccontr>
The LIDAR acquisition for Rutherford County was
flown to support the creation of 2 inch pixel. The LIDAR
data was acquired in three sorties at 6000 feet AMT using
the Leica ALS40 sensor.
</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 aboveground
structures. The algorithms for filtering data were utilized
within EarthData'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, the
technician performs calibrations on the data set.
2. Using the lidar data set provided by EarthData, 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'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.
3. Systematic distortions highlighted in step 2 were
removed and the data was 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.
4. The lidar data for each flight line was trimmed in batch
for the removal of the overlap areas between flight lines.
The data was 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.
5. 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.
6. The operator interactively processed the data
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 5. 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. 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 by
reflective objects such as buildings and vegetation. The
final DEM was written to an ASCII XYZ format.
7. The reflective surface data were also delivered in ASCII
Grid format.
</procdesc>
<srcused>withheld</srcused>
<procdate>20040624</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>EarthData International</cntorg>
<cntper>Raquel Charrois</cntper>
</cntorgp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>7320 Executive Way</address>
<city>Frederick</city>
<state>MD</state>
<postal>21704</postal>
<country>USA</country>
</cntaddr>
<cntvoice>(301)948-8550</cntvoice>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>
This process describes the method used to compile
breaklines to support the lidar digital elevation model data.
Around the perimeter of the lidar data set to
complete the surface model all breaklines
were photogrammetrically derived . The following
step-by-step procedures were utilized for breakline
development. The breakline file contains three
dimensional accurate line strings describing topographical
features. The relationship of lidar points to breaklines will
vary depending on the complexity and severity of the
terrain. Breaklines are collected where necessary to
support the final product. Examples of some such locations
include along the edges of roads, stream banks and
centerlines, ridges, and other features where the slope of
the terrain changes.
1. Using the ADS40 imagery provided by EarthData
Aviations the technician loaded the data into the ISTAR
processing system. Aerotriangulation is perfumed and
stereo pairs created.
2. Stereo pairs are then imported in to the ZI SSK softcopy
mapping system.
3. Breakline data was captured in the MicroStation
environment, which allowed the photogrammetrist to see
graphically where each lidar X, Y, and Z point and any
breaklines fall in relation to each other. This unique
approach allowed for interactive editing of the breakline
by the photogrammetrist. The technician generated a set of
temporary contours for the stereo model in the ZI work
environment to provide further guidance on the breakline
placement. The technician added and/or repositioned
breaklines to improve the accuracy as required. Once
these processes were completed, the temporary guidance
contours were deleted, and the data was passed to the
editing department for quality control and formatting.
4. The breakline data set was then put into an ESRI shape
file format.
</procdesc>
<srcused>withheld</srcused>
<procdate>20040705</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>EarthData International</cntorg>
<cntper>Raquel Charrois</cntper>
</cntorgp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>7320 Executive Way</address>
<city>Frederick</city>
<state>MD</state>
<postal>21704</postal>
<country>USA</country>
</cntaddr>
<cntvoice>(301) 948-8550</cntvoice>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>
EarthData International generated 2 foot contours from the
Lidar Bare Earth DEM and supplemental breaklines by
using the following methodology.
The contours were generated and edited using the
following software packages.
1. MicroStation V8
2. TerraScan 4.14
3. TerraSolid 4.008
Using TerraScan the Lidar points were edited, thinned,
merged with the breaklines and smoothed. Terramodel
was used to generate the contours. Elevation and Index
were the attribute fields which represent each contour line.
The contours were cut into sheets and delivered in shape
file format.
</procdesc>
<srcused>withheld</srcused>
<procdate>20040903</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>EarthData International</cntorg>
<cntper>Raquel Charrois</cntper>
</cntorgp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>7320 Executive Way</address>
<city>Frederick</city>
<state>MD</state>
<postal>21701</postal>
</cntaddr>
<cntvoice>(301) 948-8550</cntvoice>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc Sync="TRUE">Metadata imported.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20070810</date>
<time Sync="TRUE">12185700</time>
</procstep>
<procstep>
<procdesc Sync="TRUE">Dataset copied.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20080626</date>
<time Sync="TRUE">23382300</time>
</procstep>
<procstep>
<procdesc Sync="TRUE">Dataset copied.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20080627</date>
<time Sync="TRUE">12093000</time>
</procstep>
<procstep>
<procdesc Sync="TRUE">Dataset copied.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20080627</date>
<time Sync="TRUE">13550000</time>
</procstep>
</lineage>
<cloud>0</cloud>
</dataqual>
<spdoinfo>
<direct Sync="TRUE">Vector</direct>
<ptvctinf>
<esriterm Name="Contours2004">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE">Polyline</efeageom>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">1146885</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">TRUE</linrefer>
</esriterm>
<sdtsterm Name="Contours2004">
<sdtstype Sync="TRUE">String</sdtstype>
<ptvctcnt Sync="TRUE">1146885</ptvctcnt>
</sdtsterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<planar>
<planci>
<plance Sync="TRUE">coordinate pair</plance>
<coordrep>
<absres Sync="TRUE">0.000118</absres>
<ordres Sync="TRUE">0.000118</ordres>
</coordrep>
<plandu Sync="TRUE">survey feet</plandu>
</planci>
<mapproj>
<mapprojn Sync="TRUE">Lambert Conformal Conic</mapprojn>
<lambertc>
<stdparll Sync="TRUE">35.250000</stdparll>
<stdparll Sync="TRUE">36.416667</stdparll>
<longcm Sync="TRUE">-86.000000</longcm>
<latprjo Sync="TRUE">34.333333</latprjo>
<feast Sync="TRUE">1968500.000000</feast>
<fnorth Sync="TRUE">0.000000</fnorth>
</lambertc>
</mapproj>
</planar>
<geodetic>
<horizdn Sync="TRUE">North American Datum of 1983</horizdn>
<ellips Sync="TRUE">Geodetic Reference System 80</ellips>
<semiaxis Sync="TRUE">6378137.000000</semiaxis>
<denflat Sync="TRUE">298.257222</denflat>
</geodetic>
<cordsysn>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<projcsn Sync="TRUE">NAD_1983_StatePlane_Tennessee_FIPS_4100_Feet</projcsn>
</cordsysn>
</horizsys>
<vertdef>
<altsys>
<altdatum>North American Vertical Datum of 1988</altdatum>
<altres Sync="TRUE">0.250000</altres>
<altunits>Meters</altunits>
<altenc Sync="TRUE">Explicit elevation coordinate included with horizontal coordinates</altenc>
</altsys>
</vertdef>
</spref>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>Rutherford County</cntorg>
<cntper>Barbara Seivers</cntper>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>104 Rutherford County Courthouse</address>
<city>Murfreesboro</city>
<state>TN</state>
<postal>TN</postal>
</cntaddr>
<cntvoice>(615) 907-3155</cntvoice>
</cntinfo>
</distrib>
<distliab>None</distliab>
<resdesc Sync="TRUE">Downloadable Data</resdesc>
</distinfo>
<metainfo>
<metd Sync="TRUE">20070813</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>EarthData International</cntorg>
<cntper>Raquel Charrois</cntper>
</cntorgp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>7320 Executive Way</address>
<city>Frederick</city>
<state>MD</state>
<postal>21701</postal>
</cntaddr>
<cntvoice>(301) 948-8550</cntvoice>
</cntinfo>
</metc>
<metstdn Sync="TRUE">FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv Sync="TRUE">FGDC-STD-001-1998</metstdv>
<langmeta Sync="TRUE">en</langmeta>
<mettc Sync="TRUE">local time</mettc>
<metextns>
<onlink Sync="TRUE">http://www.esri.com/metadata/esriprof80.html</onlink>
<metprof Sync="TRUE">ESRI Metadata Profile</metprof>
</metextns>
</metainfo>
Rutherford County LIDAR
<Esri>
<CreaDate>20121211</CreaDate>
<CreaTime>17001000</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20070813</SyncDate>
<SyncTime>08463900</SyncTime>
<ModDate>20070813</ModDate>
<ModTime>08463900</ModTime>
<ArcGISFormat>1.0</ArcGISFormat>
<DataProperties>
<itemProps/>
</DataProperties>
</Esri>
<dataIdInfo>
<envirDesc Sync="FALSE">ESRI ArcCatalog 9.2.2.1350</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="en"/>
</dataLang>
<idCitation>
<resTitle Sync="FALSE">Contours2004</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="native">
<westBL Sync="TRUE">1760579.136488</westBL>
<eastBL Sync="TRUE">1926502.531478</eastBL>
<northBL Sync="TRUE">643850.639793</northBL>
<southBL Sync="TRUE">467977.625389</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<geoBox esriExtentType="decdegrees">
<westBL Sync="TRUE">-86.703807</westBL>
<eastBL Sync="TRUE">-86.141303</eastBL>
<northBL Sync="TRUE">36.102035</northBL>
<southBL Sync="TRUE">35.616926</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</geoBox>
</dataIdInfo>
<mdLang>
<languageCode Sync="TRUE" value="en"/>
</mdLang>
<mdStanName Sync="TRUE">ISO 19115 Geographic Information - Metadata</mdStanName>
<mdStanVer Sync="TRUE">DIS_ESRI1.0</mdStanVer>
<mdChar>
<CharSetCd Sync="TRUE" value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd Sync="TRUE" value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<distInfo>
<distributor>
<distorTran>
<onLineSrc>
<orDesc Sync="TRUE">002</orDesc>
<linkage Sync="FALSE">withheld</linkage>
<protocol Sync="TRUE">Local Area Network</protocol>
</onLineSrc>
</distorTran>
<distorFormat>
<formatName Sync="FALSE">Feature Class</formatName>
</distorFormat>
</distributor>
</distInfo>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE">NAD_1983_StatePlane_Tennessee_FIPS_4100_Feet</identCode>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
<geometObjs Name="Contours2004">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="001"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">1146885</geoObjCnt>
</geometObjs>
</VectSpatRep>
</spatRepInfo>
<eainfo>
<detailed Name="Contours2004">
<enttyp>
<enttypl Sync="FALSE">Contours2004</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">1146885</enttypc>
</enttyp>
<attr>
<attrlabl Sync="TRUE">OBJECTID</attrlabl>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Internal feature number.</attrdef>
<attrdefs Sync="TRUE">ESRI</attrdefs>
<attrdomv>
<udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">ELEV</attrlabl>
<attalias Sync="TRUE">ELEV</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">11</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">TYPE</attrlabl>
<attalias Sync="TRUE">TYPE</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">12</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">SHAPE</attrlabl>
<attalias Sync="TRUE">SHAPE</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Feature geometry.</attrdef>
<attrdefs Sync="TRUE">ESRI</attrdefs>
<attrdomv>
<udom Sync="TRUE">Coordinates defining the features.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">SHAPE.len</attrlabl>
<attalias Sync="TRUE">SHAPE.len</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
</detailed>
</eainfo>
<mdDateSt Sync="TRUE">20070813</mdDateSt>
</metadata>
