<?xml version="1.0" encoding="UTF-8"?><metadata>
<idinfo>
<citation>
<citeinfo>
<origin>U.S. Geological Survey</origin>
<pubdate>Unknown</pubdate>
<pubtime>Unknown</pubtime>
<title>Digital Elevation Models (DEM) - New York State</title>
<pubinfo>
<pubplace>Reston, VA</pubplace>
<publish>U.S. Geological Survey</publish>
</pubinfo>
<onlink>http://cugir.mannlib.cornell.edu/datatheme.jsp?id=23</onlink>
</citeinfo>
</citation>
<descript>
<abstract>A Digital Elevation Model (DEM) contains a series of
elevations ordered from south to north with the order of the
columns from west to east. The DEM is formatted as one ASCII
header record (A-record), followed by a series of profile
records (B-records) each of which include a short B-record
header followed by a series of ASCII integer elevations per each
profile. The last physical record of the DEM is an accuracy
record (C-record). The 7.5-minute DEM (10- by 10-m data spacing,
elevations in decimeters) is cast on the Universal Transverse
Mercator (UTM) projection (the quads UTM zone can be found in
the header record (Record A)) in the North American Datum of
1927. It provides coverage in 7.5- by 7.5-minute blocks. Each
product provides the same coverage as a standard USGS 7.5-minute
quadrangle, but overedges are published as separate DEM files.
Coverage is available for all quads completely contained within
New York State, plus some additional ones falling along the
borders and containing significant area of the State's land.</abstract>
<purpose>DEMs can be used as source data for digital orthophotos and
as layers in geographic information systems for earth science
analysis. DEMs can also serve as tools for volumetric analysis,
for site location of towers, or for drainage basin delineation.
These data are collected as part of the National Mapping
Program.</purpose>
<supplinf>7.5-minute DEMs have rows and columns which vary in length
and are staggered. The UTM bounding coordinates form a
quadrilateral (no two sides are parallel to each other), rather
than a rectangle. The user will need to pad out the uneven rows
and columns with blanks or flagged data values, if a rectangle
is required for the user's application. Some software vendors
have incorporated this function into their software for input of
standard formatted USGS DEMs.</supplinf>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>unknown</caldate>
</sngdate>
</timeinfo>
<current>ground condition</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>Irregular</update>
</status>
<spdom>
<bounding>
<westbc>-79.77</westbc>
<eastbc>-71.85</eastbc>
<northbc>45.02</northbc>
<southbc>40.49</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>None</themekt>
<themekey>digital elevation model</themekey>
<themekey>digital terrain model</themekey>
<themekey>hypsography</themekey>
<themekey>altitude</themekey>
<themekey>height</themekey>
<themekey>landforms</themekey>
<themekey>relief</themekey>
<themekey>topography</themekey>
<themekey>raster</themekey>
<themekey>grid</themekey>
<themekey>cell</themekey>
</theme>
<theme>
<themekt>Library of Congress Subject Headings</themekt>
<themekey>Hydrography</themekey>
<themekey>Digital Mapping</themekey>
<themekey>Digital mapping -- Automation</themekey>
<themekey>Cartography -- Automation</themekey>
<themekey>New York (State) -- Dept. of Environmental
Conservation</themekey>
</theme>
<theme>
<themekt>ISO 19115 Topic Category</themekt>
<themekey>elevation</themekey>
<themekey>006</themekey>
</theme>
<place>
<placekt>Department of Commerce, 1987, Codes for the
Identification of the States, The District of Columbia and
the Outlying Areas of the U.S., and Associated Areas
(Federal Information Processing Standard 5-2): Washington,
Department of Commerce, National Institute of Standards and
Technology (http://www.itl.nist.gov/fipspubs/fip5-2.htm)</placekt>
<placekey>New York</placekey>
<placekey>36</placekey>
<placekey>NY</placekey>
</place>
<place>
<placekt>Library of Congress Subject Headings</placekt>
<placekey>New York (State)</placekey>
</place>
<place>
<placekt>Geographic Names Information System
http://geonames.usgs.gov/pls/gnispublic</placekt>
<placekey>New York State</placekey>
</place>
</keywords>
<accconst>None</accconst>
<useconst>1. The NYS DEC and the U.S. Geological Survey asks to be
credited in derived products. 2. Secondary Distribution of the data
is not allowed. 3. Any documentation provided is an integral part of
the data set. Failure to use the documentation in conjunction with
the digital data constitutes misuse of the data. 4. Although every
effort has been made to ensure the accuracy of information, errors
may be reflected in the data supplied. The user must be aware of
data conditions and bear responsibility for the appropriate use of
the information with respect to possible errors, original map scale,
collection methodology, currency of data, and other conditions.</useconst>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>New York State Department of Environmental
Conservation. Division of Water</cntorg>
</cntorgp>
<cntpos>Watershed Geographic Information Technologies Support
Group, Chief</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>625 Broadway</address>
<address>4th floor</address>
<city>Albany</city>
<state>New York</state>
<postal>12233-3500</postal>
</cntaddr>
<cntvoice>518-402-8259</cntvoice>
<cntemail>watergis@gw.dec.state.ny.us</cntemail>
<cntinst>All questions regarding metadata and/or data should go
through the internal DEC contact.</cntinst>
</cntinfo>
</ptcontac>
<native>24,000 scale hypsographic contour linework drawn by
photogrametric, plane table or other methods by USGS, US Army Corp
of Engineers, Tennessee Valley Authority or others. Linework copied
onto stable-base mylar. Raster image of linework created by USGS,
Reston, with Optronics drum scanner at an aperture of 20um, to give
an equivalent resolution of 1024 DPI. Raster data converted to
vector with line-center algorithm in LT4X v. 3.1, 11/11/93, by John
Dabritz of Infotec Development Inc. Grid elevations calculated with
8-profile weighted linear interpolation, with cubic smoothing of
slope at the contour line as per algorithm in above mentioned LT4X
v. - export in DEM format, UTM meters, - grid height and width of 10
mt, - clipping (overedge) coordinate in UTM mt, - input coord feet
or meters (depending on source material), output in
meters/decimeters, - DEM grid points which are on a profile section
longer than 80 mt are smoothed by passing the grid through a low
pass-filter twice. The filter size (see below) is of 9 cell
diameters (aprox 9 mt). The purpose here is to leave well-contoured
areas untouched while smoothing areas of less than 5-2.5% slope (to
lessen streaking in flat areas typical of multiple-profile DEM
derivation). - cubic smoothing of elevation profile across contours
to 35% of the distance between adjacent contours. These profiles
have a smaller, but still discontinuous change in slope at contour
intersection than if not rounded. - 9 cell diameter for smoothing
reach, - use all 8 directions (from grid point to N, S, E, W ,NE,
NW, SE, SW) for each cell, - no line feeds. export dem
&lt;contour data name&gt; 2 10.00 10.00 2 1 4 80 2 0.35 9 8
0</native>
<crossref>
<citeinfo>
<origin>US Geological Survey</origin>
<pubdate>unknown</pubdate>
<title>Digital Elevation Model (DEM)</title>
<onlink>http://eros.usgs.gov/guides/dem.html</onlink>
</citeinfo>
</crossref>
</idinfo>
<dataqual>
<attracc>
<attraccr>10 mt gridding cell spacing is the maximun that can be
meaningfully extracted from hypsography contour lines. This
allows very good hypsographic contour reproduction in all areas
except very flat ones. Elevation_resolution_ is 1 decimeter (0.1
meter). Elevation accuracy is 24,000 contour data, i.e.
plus/minus half the contour interval.</attraccr>
</attracc>
<logic>The fidelity of the relationships encoded in the data structure
of the DEM are automatically verified using a USGS software program
upon completion of the data production cycle. The test verifies full
compliance to the DEM specification.</logic>
<complete>DEM visually inspected using Delta3D version 2.0, 1995 by John
Dabritz and S. Phan of Infotec Development Inc. Checked for
completness and drainage characteristics matching the USGS
Hydrography Digital Line Graphs published at the same time as the
model. Further validation for logical consistency performed previous
to submission for archiving.</complete>
<posacc>
<horizpa>
<horizpar>The horizontal accuracy of the DEM is expressed as an
estimated root mean square error (RMSE). The estimate of the
RMSE is based upon horizontal accuracy tests of the DEM
source materials with equal to or less than intended
horizontal RMSE error of the DEM. The testing of horizontal
accuracy of the source materials is accomplished by
comparing the planimetric (X and Y) coordinates of
well-defined ground points with the coordinates of the same
points as determined from a source of higher accuracy.</horizpar>
<qhorizpa>
<horizpav>3 meters (estimated)</horizpav>
<horizpae>Digital elevation models meet horizontal National
Map Accuracy Standards (NMAS) accuracy
requirements.</horizpae>
</qhorizpa>
</horizpa>
<vertacc>
<vertaccr>A vertical RMSE of one-half of the contour interval of
the source map is the maximum permitted. Systematic errors
may not exceed the contour interval of the source graphic.
Level 2 DEMs have been processed or smoothed for consistency
and edited to remove identifiable systematic errors.</vertaccr>
<qvertpa>
<vertaccv>6 to 8 meters</vertaccv>
<vertacce>DEMs meet vertical National Map Accuracy Standards
(NMAS) accuracy requirements. Vertical Positional
Accuracy Vaue varies with each quad.</vertacce>
</qvertpa>
</vertacc>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>U.S. Geological Survey</origin>
<pubdate>Unknown</pubdate>
<pubtime>Unknown</pubtime>
<title>Albany</title>
<pubinfo>
<pubplace>EROS Data Center, SD</pubplace>
<publish>U.S. Geological Survey</publish>
</pubinfo>
</citeinfo>
</srccite>
<typesrc>mylar separate from original color separation plate</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>unknown</caldate>
</sngdate>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>CONTOUR1</srccitea>
<srccontr>elevation values for interpolation</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>U.S. Geological Survey or National Geodetic
Survey (NGS) (ed.)</origin>
<pubdate>Unknown</pubdate>
<pubtime>Unknown</pubtime>
<title>project control</title>
<pubinfo>
<pubplace>EROS Data Center, SD</pubplace>
<publish>U.S. Geological Survey</publish>
</pubinfo>
</citeinfo>
</srccite>
<typesrc>field notes</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>unknown</caldate>
</sngdate>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>CONTROL1</srccitea>
<srccontr>ground control points</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>U.S. Geological Survey (ed.)</origin>
<pubdate>Unknown</pubdate>
<pubtime>Unknown</pubtime>
<title>photo ID number</title>
<pubinfo>
<pubplace>EROS Data Center, SD</pubplace>
<publish>U.S. Geological Survey</publish>
</pubinfo>
</citeinfo>
</srccite>
<typesrc>transparency</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>unknown</caldate>
</sngdate>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>PHOTO1</srccitea>
<srccontr>elevation values from photogrametry</srccontr>
</srcinfo>
<procstep>
<procdesc>The process can be seen as divided into several tasks,
each with associated sub-processes. A. Original Data Source
Preparation: 1. The United States Geological Service (USGS)
office of Map Production (Mid Continent Mapping Center,
Rolla, MO) selects the most recent original printing plates
(1:24,000 or 1:25,000 scale) for each published quadrangle
map. These plates are archived under controlled
environmental conditions and are produced from the original
map scripting materials onto dimensionally stable material
(Mylar). A copy of the separate is made by contact methods
onto photosensitive, opaque, dimensionally stable material.
The separate plate copy is shipped to the USGS Mapping
Applications Center (Reston, VA). 2. The MAC scans the
separate plate with an Ektaprint (a.k.a. Optronics) drum
scanner with an aperture of 24um (corresponding to a linear
resolution of approx 1030 DPI) into a run-length encoded
(RLE) formatted raster file. Contours lines have typically a
thickness of 25 to 30 pixels. The file, typically between 10
and 20 Mb, would be checked for completeness and distortion.
If satisfactory MAC forwards both the raster file, the plate
separate and the corresponding published quadrangle to the
digitization workshop at the New York State Department of
Environmental Conservation Water GIS unit in Albany, NY. B.
Raster file batch processing 1. The raster file was loaded
into Line Tracer for X Windows (LT4X, Infotec Inc.,
Portland, Oregon) version 3.1. With it is georegistered and
trimmed of any excess margin. 2. The file is put through an
automated raster-to-vector batch process in which a vector
following the center of the raster line is created, with a
minimum vertex separation of 25 pixels. Once the vector has
been calculated and the topology of the resultant data
established, the resolution of the original raster was
reduced to 500 DPI, to allow faster processing in the
succeeding steps. C. Vector Contour Edit, Edge Matching and
Labeling. 1. The vectorized contours are edited carefully to
correct any line breaks, vector webbing (due to pen
thickness or lack of resolution of the original's drafting
process), labels and special line symbols (depressions, road
fills, etc). 2. The contours are labeled with their
corresponding elevations, as tagged in the original
material. 3. The eight adjoining maps' vector contours are
brought in and checked against those of the map being
edited. Vectors of matching labels are snapped together if
the gap is less than 3 line-thicknesses. Otherwise they are
tagged as "disagreement in the original" (see DLG standards
for hypsography layer). For each border only one of the maps
is edited. 4. An independent quality control check of
contour edits and labeling is carried out. 5. The Digital
Elevation Model is interpolated in a batch process (see
"Native Dataset Environment" above). D. DEM Edit and Quality
Control 1. The resultant DEM is loaded in Delta3D (Infotec
Inc., Portland, OR) v. 2.1, together with the corresponding
hydrography vectors. The DEM is checked for the presence of
irregular patterns, in which case it is returned to the
previous process; water body height (e.g. in large lakes) is
set for all grid cells within the water body; and drainage
along vector streams is enforced by lowering cells higher
than the upstream one along the stream. Water retention
areas (wetlands, marshes...) are not modified except for
stream entrance and exit. - Edge matching with the adjoining
eight DEMs. 2. From thirty to thirty-five height reference
markers are collected from the corresponding cultural
separate for the quadrangle. These are compared to heights
as read from the DEM and an statistical RMS is calculated,
this is recorded in the DEM's C record. 3. The quadrangle
record A is filled and checked for consistency. 4. A final
DEM-formatted elevation dataset for the quadrangle is
recorded. E. Final Quality Control and Databasing 1. The DEM
file is shipped to USGS's Rocky Mountain Mapping Center
(Boulder, CO). There it undergoes a separate quality control
process which essentially mimics D. 2. The corresponding
quality control flags are established. The DEM is
sub-sampled to 30 mt grid spacing and the resultant file is
forwarded to USGS's EROS Data Center, were it is catalogued
into the National Elevation database. The 10 mt grid spacing
file is returned to NYS DEC, from where it is forwarded to
Cornell University's Mann Library.</procdesc>
<procdate>Unknown</procdate>
</procstep>
</lineage>
</dataqual>
<spref>
<horizsys>
<planar>
<planci>
<plance>row and column</plance>
<coordrep>
<absres>10</absres>
<ordres>10</ordres>
</coordrep>
<plandu>Meters</plandu>
</planci>
</planar>
<geodetic>
<horizdn>North American Datum of 1927</horizdn>
<ellips>Clarke 1866</ellips>
<semiaxis>6378206.4</semiaxis>
<denflat>294.9787</denflat>
</geodetic>
</horizsys>
<vertdef>
<altsys>
<altdatum>National Geodetic Vertical Datum of 1929</altdatum>
<altres>1</altres>
<altunits>decimeters</altunits>
<altenc>Explicit elevation coordinate included with horizontal
coordinates</altenc>
</altsys>
</vertdef>
</spref>
<eainfo>
<overview>
<eaover>The digital elevation model is composed of an elevation
value linked to a grid cell location representing a gridded form
of a topographic map hypsography overlay. Each grid cell entity
contains an 8-character value between -32,767.0 and 32,768.0.</eaover>
<eadetcit>U.S. department of the Interior, U.S. Geological Survey,
1992, Standards for digital elevation models: Reston, VA, a
hypertext version of the Digital Elevation Model (DEM) is
available at: http://eros.usgs.gov/guides/dem.html (see Cross
Reference)</eadetcit>
</overview>
<detailed Name="Hillshade_USGS_CUGIR_Region.tif.vat">
<enttyp>
<enttypl Sync="TRUE">Hillshade_USGS_CUGIR_Region.tif.vat</enttypl>
<enttypt Sync="TRUE">Table</enttypt>
<enttypc Sync="TRUE">248</enttypc>
</enttyp>
<attr>
<attrlabl Sync="TRUE">OID</attrlabl>
<attalias Sync="TRUE">OID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</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">VALUE</attrlabl>
<attalias Sync="TRUE">VALUE</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">COUNT_</attrlabl>
<attalias Sync="TRUE">COUNT_</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
</detailed>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>Mann Library</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing</addrtype>
<address>Cornell University</address>
<city>Ithaca</city>
<state>NY</state>
<postal>14853</postal>
<country>USA</country>
</cntaddr>
<cntvoice>607-255-5406</cntvoice>
<cntemail>mann_ref@cornell.edu</cntemail>
</cntinfo>
</distrib>
<distliab>Although these data have been processed successfully on a
computer system at the U.S. Geological Survey, no warranty expressed
or implied is made regarding the accuracy or utility of the data on
any other system or for general or scientific purposes, nor shall
the act of distribution constitute any such warranty. This
disclaimer applies both to individual use of the data and aggregate
use with other data. It is strongly recommended that careful
attention be paid to the contents of the metadata file associated
with these data. Neither the U.S. Geologial Survey nor the New York
State Department of Environmental Conservation shall be held liable
for improper or incorrect use of the data described and/or contained
herein. Cornell University provides these geographic data "as is."
Cornell University makes no guarantee or warranty concerning the
accuracy of information contained in the geographic data. Cornell
University further makes no warranty either expressed or implied,
regarding the condition of the product or its fitness for any
particular purpose. The burden for determining fitness for use lies
entirely with the user. Although these files have been processed
successfully on computers at Cornell University, no warranty is made
by Cornell University regarding the use of these data on any other
system, nor does the fact of distribution constitute or imply any
such warranty.</distliab>
<stdorder>
<digform>
<digtinfo>
<formname>DEM</formname>
<filedec>zip</filedec>
</digtinfo>
<digtopt>
<onlinopt>
<computer>
<networka>
<networkr>http://cugir.mannlib.cornell.edu/datatheme.jsp?id=23</networkr>
</networka>
</computer>
</onlinopt>
</digtopt>
</digform>
<fees>None</fees>
</stdorder>
</distinfo>
<metainfo>
<metd>20080414</metd>
<metrd>20080414</metrd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>New York State Department of Environmental
Conservation</cntorg>
</cntorgp>
<cntpos>Division of Information Services; GIS Unit</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>625 Broadway</address>
<address>3rd floor</address>
<city>Albany</city>
<state>New York</state>
<postal>12233-2750</postal>
</cntaddr>
<cntvoice>518-402-9860</cntvoice>
<cntfax>518-402-9031</cntfax>
<cntemail>enterpriseGIS@gw.dec.state.ny.us</cntemail>
</cntinfo>
</metc>
<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
</metainfo>
<dataIdInfo>
<envirDesc Sync="FALSE">Esri ArcGIS 13.0.3.36057</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="TRUE">Hillshade_USGS_CUGIR_Region.tif</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="002"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-75.386459</westBL>
<eastBL Sync="TRUE">-73.744480</eastBL>
<northBL Sync="TRUE">42.384751</northBL>
<southBL Sync="TRUE">41.243050</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
</dataIdInfo>
<mdLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<Esri>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">Hillshade_USGS_CUGIR_Region.tif</itemName>
<imsContentType Sync="TRUE">002</imsContentType>
<nativeExtBox>
<westBL Sync="TRUE">252635.190869</westBL>
<eastBL Sync="TRUE">696236.665869</eastBL>
<southBL Sync="TRUE">878944.445810</southBL>
<northBL Sync="TRUE">1293740.204143</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Foot_US (0.304801)</csUnits>
<projcsn Sync="TRUE">NAD_1983_StatePlane_New_York_East_FIPS_3101_Feet</projcsn>
<peXml Sync="TRUE">&lt;ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.0.0'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_StatePlane_New_York_East_FIPS_3101_Feet&amp;quot;,GEOGCS[&amp;quot;GCS_North_American_1983&amp;quot;,DATUM[&amp;quot;D_North_American_1983&amp;quot;,SPHEROID[&amp;quot;GRS_1980&amp;quot;,6378137.0,298.257222101]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Transverse_Mercator&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,492125.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-74.5],PARAMETER[&amp;quot;Scale_Factor&amp;quot;,0.9999],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,38.83333333333334],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;EPSG&amp;quot;,2260]],VERTCS[&amp;quot;Unknown VCS from ArcInfo Workstation&amp;quot;,VDATUM[&amp;quot;Unknown&amp;quot;],PARAMETER[&amp;quot;Vertical_Shift&amp;quot;,0.0],PARAMETER[&amp;quot;Direction&amp;quot;,1.0],UNIT[&amp;quot;User_Defined_Unit&amp;quot;,0.3048]]&lt;/WKT&gt;&lt;XOrigin&gt;-17954600&lt;/XOrigin&gt;&lt;YOrigin&gt;-46918100&lt;/YOrigin&gt;&lt;XYScale&gt;137255069.87923574&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;10000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;10000&lt;/MScale&gt;&lt;XYTolerance&gt;0.0032808333333333331&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.001&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.001&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;102715&lt;/WKID&gt;&lt;LatestWKID&gt;2260&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
<RasterProperties>
<General>
<PixelDepth Sync="TRUE">16</PixelDepth>
<HasColormap Sync="TRUE">FALSE</HasColormap>
<CompressionType Sync="TRUE">LZW</CompressionType>
<NumBands Sync="TRUE">1</NumBands>
<Format Sync="TRUE">TIFF</Format>
<HasPyramids Sync="TRUE">TRUE</HasPyramids>
<SourceType Sync="TRUE">discrete</SourceType>
<PixelType Sync="TRUE">unsigned integer</PixelType>
<NoDataValue Sync="TRUE">32767</NoDataValue>
</General>
</RasterProperties>
</DataProperties>
<SyncDate>20221208</SyncDate>
<SyncTime>14452300</SyncTime>
<ModDate>20221208</ModDate>
<ModTime>14452300</ModTime>
<CreaDate>20230815</CreaDate>
<CreaTime>12061500</CreaTime>
<SyncOnce>TRUE</SyncOnce>
</Esri>
<distInfo>
<distFormat>
<formatName Sync="TRUE">Raster Dataset</formatName>
</distFormat>
</distInfo>
<mdHrLv>
<ScopeCd Sync="TRUE" value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="2260"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">5.3(9.0.0)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spdoinfo>
<rastinfo>
<rasttype Sync="TRUE">Pixel</rasttype>
<rowcount Sync="TRUE">12643</rowcount>
<colcount Sync="TRUE">13521</colcount>
<rastxsz Sync="TRUE">32.808333</rastxsz>
<rastysz Sync="TRUE">32.808333</rastysz>
<rastbpp Sync="TRUE">16</rastbpp>
<vrtcount Sync="TRUE">1</vrtcount>
<rastorig Sync="TRUE">Upper Left</rastorig>
<rastcmap Sync="TRUE">FALSE</rastcmap>
<rastcomp Sync="TRUE">LZ77</rastcomp>
<rastband Sync="TRUE">1</rastband>
<rastdtyp Sync="TRUE">pixel codes</rastdtyp>
<rastifor Sync="TRUE">SDR</rastifor>
<rastplyr Sync="TRUE">TRUE</rastplyr>
</rastinfo>
</spdoinfo>
<mdDateSt Sync="TRUE">20221208</mdDateSt>
<spatRepInfo>
<Georect>
<cellGeo>
<CellGeoCd Sync="TRUE" value="002"/>
</cellGeo>
<numDims Sync="TRUE">2</numDims>
<tranParaAv Sync="TRUE">1</tranParaAv>
<chkPtAv Sync="TRUE">0</chkPtAv>
<cornerPts>
<pos Sync="TRUE">252635.190869 878944.445810</pos>
</cornerPts>
<cornerPts>
<pos Sync="TRUE">252635.190869 1293740.204143</pos>
</cornerPts>
<cornerPts>
<pos Sync="TRUE">696236.665869 1293740.204143</pos>
</cornerPts>
<cornerPts>
<pos Sync="TRUE">696236.665869 878944.445810</pos>
</cornerPts>
<centerPt>
<pos Sync="TRUE">474435.928369 1086342.324976</pos>
</centerPt>
<axisDimension type="002">
<dimSize Sync="TRUE">13521</dimSize>
<dimResol>
<value Sync="TRUE" uom="ftUS">32.808333</value>
</dimResol>
</axisDimension>
<axisDimension type="001">
<dimSize Sync="TRUE">12643</dimSize>
<dimResol>
<value Sync="TRUE" uom="ftUS">32.808333</value>
</dimResol>
</axisDimension>
<ptInPixel>
<PixOrientCd Sync="TRUE" value="001"/>
</ptInPixel>
</Georect>
</spatRepInfo>
<contInfo>
<ImgDesc>
<contentTyp>
<ContentTypCd Sync="TRUE" value="002"/>
</contentTyp>
<covDim>
<Band>
<dimDescrp Sync="TRUE">Band_1</dimDescrp>
<maxVal Sync="TRUE">248.000000</maxVal>
<minVal Sync="TRUE">0.000000</minVal>
<bitsPerVal Sync="TRUE">16</bitsPerVal>
<valUnit>
<UOM type="length"/>
</valUnit>
</Band>
</covDim>
</ImgDesc>
</contInfo>
</metadata>
