<?xml version="1.0" encoding="UTF-8"?><metadata>
<idinfo>
<citation>
<citeinfo>
<geoform Sync="TRUE">SDE raster digital data</geoform>
<pubinfo>
<pubplace>Washington, DC</pubplace>
<publish>District of Columbia Office of the Chief Technology Officer (OCTO)</publish>
</pubinfo>
<ftname Sync="TRUE">IMAGE.ORTHO2009</ftname>
<origin>Pictometry Inc</origin>
<title Sync="TRUE">IMAGE.ORTHO2009</title>
<pubdate>20090824</pubdate>
<onlink Sync="FALSE">withheld</onlink>
</citeinfo>
</citation>
<descript>
<langdata Sync="TRUE">en</langdata>
<purpose>This data is used for the planning and management of Washington, D.C. by local government agencies.</purpose>
<supplinf>GSD: Pixels have a 1 foot GSD.
Coverage: Coverage is 1 square mile.
Overlap: Zero overlap, tiles have contiguous edges.
Feathering: Component images are feathered together using a 20-pixel feather region.
Cut-Lines: Cut lines are selected based on distance from nadir and do not take ground features into account.
Radiometric Balancing: Images are color balanced, however some radiometric differences may be seen across flat fields such as water or grassy planes.
Building Lean: Building lean is minimized by utilizing N5 orthogonal input images when available, however no other building lean corrections are performed.
Elevation Data: 1995 1 meter contours.</supplinf>
<abstract>2009 Aerial Photography (1 foot resolution) - Sector Tiles Pictometry provided as part of the 2009 photo capture were exported to tiff and provided as a raster catalog. An Ortho Sector Tile is typically a 1 foot GSD ortho mosaic tile covering a 1-square mile area that is created by deresolving the best available orthogonal images captured. Images are not radiometrically balanced, may have observable cut lines and could consist of imagery taken over a period of several days.
Note - Print at your own risk, the images have seamlines between some tiles and the Pictometry logo is in the southeast corner of every tile.
All DC GIS data is stored and exported in Maryland State Plane coordinates NAD 83 meters.
METADATA CONTENT IS IN PROCESS OF VALIDATION AND SUBJECT TO CHANGE.</abstract>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>20090111</caldate>
</sngdate>
</timeinfo>
<current>ground condition</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>Unknown</update>
</status>
<spdom>
<bounding>
<westbc Sync="TRUE">-77.121424</westbc>
<eastbc Sync="TRUE">-76.896993</eastbc>
<northbc Sync="TRUE">38.994810</northbc>
<southbc Sync="TRUE">38.791782</southbc>
</bounding>
<lboundng>
<leftbc Sync="TRUE">389481.534155</leftbc>
<rightbc Sync="TRUE">408923.545864</rightbc>
<bottombc Sync="TRUE">124899.060167</bottombc>
<topbc Sync="TRUE">149037.744475</topbc>
</lboundng>
</spdom>
<keywords>
<theme>
<themekt>None</themekt>
<themekey>Aerial Photography</themekey>
<themekey> Planning</themekey>
<themekey> Imagery</themekey>
<themekey> Orthos</themekey>
<themekey> Orthophotography</themekey>
<themekey> imageryBaseMapsEarthCover</themekey>
</theme>
<place>
<placekt>Geographic Names Information System</placekt>
<placekey>United States of America (USA)</placekey>
<placekey>Washington, D.C.</placekey>
<placekey>District of Columbia</placekey>
<placekey>D.C.</placekey>
</place>
</keywords>
<useconst>Acknowledgment of the DC Geographic Information Systems Program (DC GIS). The District of Columbia Government makes no claims as to the completeness, accuracy or content of any data contained hereon, and makes no representation of any kind, including, but not limited to, the warranty of the accuracy or fitness for a particular use, nor are any such warranties to be implied or inferred with respect to the information or data furnished herein.</useconst>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>D.C. Office of the Chief Technology Officer</cntorg>
</cntorgp>
<cntpos>GIS Data Coordinator</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>441 4th St NW, Suite 930 South</address>
<city>Washington</city>
<state>D.C.</state>
<postal>20001</postal>
</cntaddr>
<cntfax>(202)727-5660</cntfax>
<cntemail>dcgis@dc.gov</cntemail>
<hours>8:30 AM - 5:00 PM</hours>
</cntinfo>
</ptcontac>
<datacred>D.C. Office of the Chief of Technology Officer (OCTO)
Pictometry Inc
7320 Executive Way
Frederick, MD 21704
(301)948-8550</datacred>
<native Sync="FALSE">ESRI ArcCatalog 9.2.6.1500</native>
<natvform Sync="FALSE">Raster Dataset</natvform>
</idinfo>
<dataqual>
<posacc>
<horizpa>
<horizpar>Pixel placement accuracy is based on the accuracy of the component imagery. N5 orthogonal images are used when available to maximize accuracy, however Pictometry does not warrant any pixel placement accuracy. The most significant source of error is generally the error introduced by the elevation data.
Pictometry's orthogonal images provide the coordinate accuracy fulfilling most planemetric requirements, however, Pictometry data is not intended for authoritative definitive mapping or surveying replacement. If there is a need for authoritative mapping products, additional work is required by licensed individuals in order to certify Pictometry's orthogonal imagery. Alternatively, a separate, authoritative orthogonal image capture can be done and those orthogonal images used inside of Pictometry. Our oblique images are unique to Pictometry and are intended to provide data not available elsewhere and lateral views with more visual information, such as building stock analysis. In Pictometry the orthogonal and oblique images are linked for your convenience and additional study. With a few clicks you can find the revealing lateral views, height measurements, and other information afforded by the oblique images while using the coordinate accuracy afforded by the orthogonal images.</horizpar>
</horizpa>
<vertacc>
<vertaccr>N/A</vertaccr>
</vertacc>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>Pictometry Inc.</origin>
<pubdate>20070406</pubdate>
<title>Aerial Photography of Washington, D.C.</title>
<geoform>remote-sensing image</geoform>
<onlink>http://www.pictometry.com</onlink>
</citeinfo>
</srccite>
<typesrc>digital camera</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>20050404</caldate>
</sngdate>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>Pictometry</srccitea>
</srcinfo>
<procstep>
<procdesc>Sensor Size	Pixels: 4008 x 2672 (or 3208 x 2672 for some Community level imagery) in a Landscape orientation.
Image Format	Industry-standard image format with proprietary image trailer, including JFIF (JPEG), TIFF, and BMP.
Image Quality	Images will have an unobstructed view of the ground. In controlled airspace around airports, etc., and in areas of rapid elevation changes, the image footprint sizes and resolutions may vary. There may be varying degrees of ground illumination and color variations due to lighting and cloud shadows.
Measurement Accuracy	0.5% measurement error, excluding user pixel selection error
Pixel Placement Accuracy	Pictometry provides a visualization system and therefore does not certify image accuracy. However, some Pictometry customers have done their own certification on the Pictometry data after delivery and have shared their results. On average, customers have been seeing better than 1.0-meter RMS error at a 95% confidence level (NMAS 1:1200) for orthogonal imagery over relatively flat terrain or in areas with accurate elevation data, and 2.0-meter RMS error at a 95% confidence level (NMAS 1:2400) for more varied terrain or in areas with poor elevation data. However, Pictometry does not guarantee these accuracies and your results may vary.
Sensor Orientation	Pictometry utilizes an IMU (Inertial Measurement Unit), ground station post-corrected differential GPS, and Kalman filtering to achieve a high degree of positional and directional accuracy.
Sensor Positional Accuracy	mean 15cm absolute
Sensor Directional Accuracy	0.015 degrees absolute (roll/pitch)
0.035 degrees absolute (heading)
Ortho-Rectification	The images are ortho-rectified to back out the optical deviations of the capture system and the variations due to elevation changes (utilizing the best DEM data available, including customer provided DEM data), resulting in geographically square pixels aligned to a rectilinear grid. This grid can be one of any number of coordinate systems, including Latitude/Longitude, State Plane, UTM, and more. The desired coordinate system should be specified in the contract, or a default coordinate system will be used.
Image Export	J
FIF (JPEG), TIFF, BMP
EFS software can be utilized to export the images into any of the above industry-standard formats. The orthogonal images can optionally be re-projected during this export process, and an associated geography file can be created as well for use in importing the images into GIS mapping software.
Image Tiling	Individual orthogonal images are edge-feathered and mosaiced to produce orthogonal image tiles with tile sizes selected to balance single image coverage as well as manageability of open images. These orthogonal tiles provide continuous coverage across the area of interest. While some color balancing is done, these orthogonal tiles are not fully radiometrically balanced or edge-matched.
</procdesc>
<procdate>20070406</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Pictometry Inc</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>100 Town Centre Drive, Suite A</address>
<city>Rochester</city>
<state>NY</state>
<postal>14623-4260</postal>
<country>USA</country>
</cntaddr>
<cntvoice>888-771-9714</cntvoice>
<cntfax>585-486-0098</cntfax>
<cntemail>info@pictometry.com</cntemail>
<hours>8:30 Am - 5:00 p,</hours>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc Sync="TRUE">Metadata imported.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20091115</date>
<time Sync="TRUE">00571500</time>
</procstep>
</lineage>
<attracc>
<attraccr>N/A</attraccr>
</attracc>
</dataqual>
<spref>
<vertdef>
<altsys>
<altdatum>North American Vertical Datum of 1988</altdatum>
<altres Sync="TRUE">1.000000</altres>
<altunits>Meters</altunits>
<altenc Sync="TRUE">Explicit elevation coordinate included with horizontal coordinates</altenc>
</altsys>
</vertdef>
<horizsys>
<planar>
<planci>
<plance Sync="TRUE">row and column</plance>
<coordrep>
<absres Sync="TRUE">0.304801</absres>
<ordres Sync="TRUE">0.304801</ordres>
</coordrep>
<plandu Sync="TRUE">meters</plandu>
</planci>
</planar>
<cordsysn>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<projcsn Sync="TRUE">NAD_1983_StatePlane_Maryland_FIPS_1900</projcsn>
</cordsysn>
<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>
</horizsys>
</spref>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>D.C. Office of the Chief Technology</cntorg>
</cntorgp>
<cntpos>GIS Data Coordinator</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>
441 4th Street NW
Suite 930 South
</address>
<city>Washington</city>
<state>D.C.</state>
<postal>20001</postal>
<country>USA</country>
</cntaddr>
<cntfax>(202)727-5660</cntfax>
<cntemail>dcgis@dc.gov</cntemail>
<hours>8:30 am - 5:30 pm</hours>
</cntinfo>
</distrib>
<stdorder>
<digform>
<digtinfo>
<formname>TIFF</formname>
<filedec>No compression applied</filedec>
<transize Sync="TRUE">0.000</transize>
<dssize Sync="TRUE">0.000</dssize>
</digtinfo>
<digtopt>
<onlinopt>
<computer>
<networka>
<networkr>http://dcgis.dc.gov</networkr>
</networka>
</computer>
</onlinopt>
</digtopt>
</digform>
<fees>None</fees>
<ordering>See OCTO.</ordering>
</stdorder>
<resdesc Sync="TRUE">Downloadable Data</resdesc>
<distliab>Acknowledgment of the DC Geographic Information Systems Program (DC GIS). The District of Columbia Government makes no claims as to the completeness, accuracy or content of any data contained hereon, and makes no representation of any kind, including, but not limited to, the warranty of the accuracy or fitness for a particular use, nor are any such warranties to be implied or inferred with respect to the information or data furnished herein.</distliab>
</distinfo>
<metainfo>
<metd Sync="TRUE">20091115</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>D.C. Office of the Chief Technology</cntorg>
</cntorgp>
<cntpos>GIS Data Coordinator</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>
441 4th Street NW
Suite 930
</address>
<city>Washington</city>
<state>D.C.</state>
<postal>20001</postal>
</cntaddr>
<cntvoice>N/A</cntvoice>
<cntfax>(202)727-5660</cntfax>
<cntemail>dcgis@dc.gov</cntemail>
<hours>8:30 am - 5:00 pm</hours>
</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>
<metrd>07/24/07</metrd>
</metainfo>
<Esri>
<CreaDate>20091115</CreaDate>
<CreaTime>00571500</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20261014</SyncDate>
<SyncTime>11113000</SyncTime>
<ModDate>20261014</ModDate>
<ModTime>16152000</ModTime>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">Ortho2009.tif</itemName>
<nativeExtBox>
<westBL Sync="TRUE">389481.534155</westBL>
<eastBL Sync="TRUE">408923.545864</eastBL>
<southBL Sync="TRUE">124899.060167</southBL>
<northBL Sync="TRUE">149037.744475</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<imsContentType Sync="TRUE">002</imsContentType>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Meter (1.000000)</csUnits>
<projcsn Sync="TRUE">NAD_1983_StatePlane_Maryland_FIPS_1900</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.5.0'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_StatePlane_Maryland_FIPS_1900&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;Lambert_Conformal_Conic&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,400000.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-77.0],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,38.3],PARAMETER[&amp;quot;Standard_Parallel_2&amp;quot;,39.45],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,37.66666666666666],UNIT[&amp;quot;Meter&amp;quot;,1.0],AUTHORITY[&amp;quot;EPSG&amp;quot;,26985]]&lt;/WKT&gt;&lt;XOrigin&gt;-36747100&lt;/XOrigin&gt;&lt;YOrigin&gt;-29091500&lt;/YOrigin&gt;&lt;XYScale&gt;121236910.21292362&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.001&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;26985&lt;/WKID&gt;&lt;LatestWKID&gt;26985&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
<RasterProperties>
<General>
<PixelDepth Sync="TRUE">8</PixelDepth>
<HasColormap Sync="TRUE">FALSE</HasColormap>
<CompressionType Sync="TRUE">LZW</CompressionType>
<NumBands Sync="TRUE">3</NumBands>
<Format Sync="TRUE">TIFF</Format>
<HasPyramids Sync="TRUE">TRUE</HasPyramids>
<SourceType Sync="TRUE">continuous</SourceType>
<PixelType Sync="TRUE">unsigned integer</PixelType>
<NoDataValue Sync="TRUE">256</NoDataValue>
</General>
</RasterProperties>
</DataProperties>
<MetaID>{7B3A35D4-8919-47AC-8974-908B2A6455C9}</MetaID>
<ArcGISFormat>1.0</ArcGISFormat>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<ArcGISProfile>FGDC</ArcGISProfile>
</Esri>
<spdoinfo>
<direct Sync="TRUE">Raster</direct>
<rastinfo>
<rasttype Sync="TRUE">Pixel</rasttype>
<rowcount Sync="TRUE">79195</rowcount>
<colcount Sync="TRUE">63786</colcount>
<rastxsz Sync="TRUE">0.304801</rastxsz>
<rastysz Sync="TRUE">0.304801</rastysz>
<rastbpp Sync="TRUE">8</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">3</rastband>
<rastdtyp Sync="TRUE">pixel codes</rastdtyp>
<rastplyr Sync="TRUE">TRUE</rastplyr>
<rastifor Sync="TRUE">SDR</rastifor>
</rastinfo>
</spdoinfo>
<eainfo>
<detailed Name="IMAGE.Ortho2009">
<attr>
<attrlabl Sync="TRUE">ObjectID</attrlabl>
<attalias Sync="TRUE">ObjectID</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">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">NAME</attrlabl>
<attalias Sync="TRUE">NAME</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">256</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">RASTER</attrlabl>
<attalias Sync="TRUE">Raster</attalias>
<attrtype Sync="TRUE">0</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<enttyp>
<enttypl Sync="TRUE">IMAGE.Ortho2009</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">93</enttypc>
</enttyp>
<attr>
<attrlabl Sync="TRUE">SHAPE.AREA</attrlabl>
<attalias Sync="TRUE">SHAPE.AREA</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</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>
<detailed Name="Band_2">
<enttyp>
<enttypl Sync="TRUE">Band_2</enttypl>
<enttypt Sync="TRUE">Table</enttypt>
<enttypc Sync="TRUE">256</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">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">0</attwidth>
<atprecis Sync="TRUE">0</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">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
</detailed>
<detailed Name="Band_3">
<enttyp>
<enttypl Sync="TRUE">Band_3</enttypl>
<enttypt Sync="TRUE">Table</enttypt>
<enttypc Sync="TRUE">256</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">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">0</attwidth>
<atprecis Sync="TRUE">0</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">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
</detailed>
</eainfo>
<mdLang>
<languageCode value="eng">
</languageCode>
<countryCode Sync="TRUE" value="USA">
</countryCode>
</mdLang>
<mdChar>
<CharSetCd value="004">
</CharSetCd>
</mdChar>
<mdHrLv>
<ScopeCd value="005">
</ScopeCd>
</mdHrLv>
<mdContact>
<rpOrgName>D.C. Office of the Chief Technology</rpOrgName>
<rpPosName>GIS Data Coordinator</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>N/A</voiceNum>
<faxNum>(202)727-5660</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>441 4th Street NW Suite 930</delPoint>
<city>Washington</city>
<adminArea>D.C.</adminArea>
<postCode>20001</postCode>
<eMailAdd>dcgis@dc.gov</eMailAdd>
</cntAddress>
<cntHours>8:30 am - 5:00 pm</cntHours>
</rpCntInfo>
<role>
<RoleCd value="007">
</RoleCd>
</role>
</mdContact>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distributor>
<distorCont>
<rpOrgName>D.C. Office of the Chief Technology</rpOrgName>
<rpPosName>GIS Data Coordinator</rpPosName>
<rpCntInfo>
<cntPhone>
<faxNum>(202)727-5660</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>441 4th Street NW Suite 930 South</delPoint>
<city>Washington</city>
<adminArea>D.C.</adminArea>
<postCode>20001</postCode>
<country>US</country>
<eMailAdd>dcgis@dc.gov</eMailAdd>
</cntAddress>
<cntHours>8:30 am - 5:30 pm</cntHours>
</rpCntInfo>
<role>
<RoleCd value="005">
</RoleCd>
</role>
</distorCont>
<distorOrdPrc>
<resFees>None</resFees>
<ordInstr>See OCTO.</ordInstr>
</distorOrdPrc>
<distorFormat>
<formatName>TIFF</formatName>
<fileDecmTech>No compression applied</fileDecmTech>
</distorFormat>
<distorTran>
<onLineSrc>
<linkage>http://dcgis.dc.gov</linkage>
</onLineSrc>
</distorTran>
</distributor>
<distFormat>
<formatName Sync="TRUE">Raster Dataset</formatName>
</distFormat>
</distInfo>
<dataIdInfo>
<idCitation>
<date>
<pubDate>2009-08-24</pubDate>
</date>
<citRespParty>
<rpOrgName>District of Columbia Office of the Chief Technology Officer (OCTO)</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Washington, DC</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010">
</RoleCd>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Pictometry Inc</rpOrgName>
<role>
<RoleCd value="006">
</RoleCd>
</role>
</citRespParty>
<presForm>
<PresFormCd Sync="TRUE" value="005">
</PresFormCd>
</presForm>
<resTitle Sync="FALSE">Aerial Photography (Orthophoto) - 2009</resTitle>
</idCitation>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;2009 Aerial Photography (1 foot resolution) - Sector Tiles Pictometry provided as part of the 2009 photo capture were exported to tiff and provided as a raster catalog. An Ortho Sector Tile is typically a 1 foot GSD ortho mosaic tile covering a 1-square mile area that is created by deresolving the best available orthogonal images captured. Images are not radiometrically balanced, may have observable cut lines and could consist of imagery taken over a period of several days. Note - Print at your own risk, the images have seamlines between some tiles and the Pictometry logo is in the southeast corner of every tile. All DC GIS data is stored and exported in Maryland State Plane coordinates NAD 83 meters.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idPurp>This data is used for the planning and management of Washington, D.C. by local government agencies.</idPurp>
<idCredit>Office of the Chief of Technology Officer </idCredit>
<idStatus>
<ProgCd value="001">
</ProgCd>
</idStatus>
<idPoC>
<rpOrgName>D.C. Office of the Chief Technology Officer</rpOrgName>
<rpPosName>GIS Data Coordinator</rpPosName>
<rpCntInfo>
<cntPhone>
<faxNum>(202)727-5660</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>441 4th St NW, Suite 930 South</delPoint>
<city>Washington</city>
<adminArea>D.C.</adminArea>
<postCode>20001</postCode>
<eMailAdd>dcgis@dc.gov</eMailAdd>
</cntAddress>
<cntHours>8:30 AM - 5:00 PM</cntHours>
</rpCntInfo>
<role>
<RoleCd value="007">
</RoleCd>
</role>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="012">
</MaintFreqCd>
</maintFreq>
</resMaint>
<placeKeys>
<thesaName>
<resTitle>Geographic Names Information System</resTitle>
</thesaName>
<keyword>Washington</keyword>
<keyword>D.C.</keyword>
<keyword>D.C.</keyword>
<keyword>United States of America (USA)</keyword>
<keyword>District of Columbia</keyword>
</placeKeys>
<themeKeys>
<keyword>imageryBaseMapsEarthCover</keyword>
<keyword>Orthos</keyword>
<keyword>Orthophotography</keyword>
<keyword>Planning</keyword>
<keyword>Aerial Photography</keyword>
<keyword>Imagery</keyword>
</themeKeys>
<searchKeys>
<keyword>tiff</keyword>
<keyword>aerial photography</keyword>
<keyword>orthophoto</keyword>
<keyword>Washington DC</keyword>
<keyword>District of Columbia</keyword>
<keyword>Orthophoto 2005</keyword>
<keyword>DC</keyword>
<keyword>historic</keyword>
<keyword>imagery</keyword>
</searchKeys>
<resConst>
<LegConsts>
<useLimit>Acknowledgment of the DC Geographic Information Systems Program (DC GIS). The District of Columbia Government makes no claims as to the completeness, accuracy or content of any data contained hereon, and makes no representation of any kind, including, but not limited to, the warranty of the accuracy or fitness for a particular use, nor are any such warranties to be implied or inferred with respect to the information or data furnished herein.</useLimit>
</LegConsts>
</resConst>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;This work is licensed under a &lt;/SPAN&gt;&lt;A href="https://creativecommons.org/licenses/by/4.0" target="_blank" STYLE="text-decoration:underline;"&gt;&lt;SPAN&gt;&lt;SPAN STYLE="text-decoration:underline;"&gt;Creative Commons Attribution 4.0 International License&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN&gt;. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Acknowledgment of the DC Geographic Information Systems Program (DC GIS). The District of Columbia Government makes no claims as to the completeness, accuracy or content of any data contained hereon, and makes no representation of any kind, including, but not limited to, the warranty of the accuracy or fitness for a particular use, nor are any such warranties to be implied or inferred with respect to the information or data furnished herein.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<dataLang>
<languageCode value="eng">
</languageCode>
<countryCode Sync="TRUE" value="USA">
</countryCode>
</dataLang>
<dataExt>
<exDesc>ground condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2009-01-11</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<suppInfo>GSD: Pixels have a 1 foot GSD. Coverage: Coverage is 1 square mile. Overlap: Zero overlap, tiles have contiguous edges. Feathering: Component images are feathered together using a 20-pixel feather region. Cut-Lines: Cut lines are selected based on distance from nadir and do not take ground features into account. Radiometric Balancing: Images are color balanced, however some radiometric differences may be seen across flat fields such as water or grassy planes. Building Lean: Building lean is minimized by utilizing N5 orthogonal input images when available, however no other building lean corrections are performed. Elevation Data: 1995 1 meter contours.</suppInfo>
<envirDesc Sync="FALSE">Esri ArcGIS 13.5.5.57366</envirDesc>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="002">
</SpatRepTypCd>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-77.121445</westBL>
<eastBL Sync="TRUE">-76.896970</eastBL>
<northBL Sync="TRUE">39.009292</northBL>
<southBL Sync="TRUE">38.791780</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<tpCat>
<TopicCatCd value="010">
</TopicCatCd>
</tpCat>
<tpCat>
<TopicCatCd value="015">
</TopicCatCd>
</tpCat>
</dataIdInfo>
<mdMaint>
<maintFreq>
<MaintFreqCd value="012">
</MaintFreqCd>
</maintFreq>
<maintNote>Last metadata review date: 07/24/07</maintNote>
</mdMaint>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005">
</ScopeCd>
</scpLvl>
</dqScope>
<report type="DQQuanAttAcc">
<measDesc>N/A</measDesc>
</report>
<report dimension="horizontal" type="DQAbsExtPosAcc">
<measDesc>Pixel placement accuracy is based on the accuracy of the component imagery. N5 orthogonal images are used when available to maximize accuracy, however Pictometry does not warrant any pixel placement accuracy. The most significant source of error is generally the error introduced by the elevation data. Pictometry's orthogonal images provide the coordinate accuracy fulfilling most planemetric requirements, however, Pictometry data is not intended for authoritative definitive mapping or surveying replacement. If there is a need for authoritative mapping products, additional work is required by licensed individuals in order to certify Pictometry's orthogonal imagery. Alternatively, a separate, authoritative orthogonal image capture can be done and those orthogonal images used inside of Pictometry. Our oblique images are unique to Pictometry and are intended to provide data not available elsewhere and lateral views with more visual information, such as building stock analysis. In Pictometry the orthogonal and oblique images are linked for your convenience and additional study. With a few clicks you can find the revealing lateral views, height measurements, and other information afforded by the oblique images while using the coordinate accuracy afforded by the orthogonal images.</measDesc>
</report>
<report dimension="vertical" type="DQAbsExtPosAcc">
<measDesc>N/A</measDesc>
</report>
<dataLineage>
<dataSource>
<srcCitatn>
<resTitle>Aerial Photography of Washington, D.C.</resTitle>
<resAltTitle>Pictometry</resAltTitle>
<date>
<pubDate>2007-04-06</pubDate>
</date>
<citRespParty>
<rpOrgName>Pictometry Inc.</rpOrgName>
<role>
<RoleCd value="006">
</RoleCd>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005">
</PresFormCd>
</presForm>
<presForm>
<fgdcGeoform>remote-sensing image</fgdcGeoform>
</presForm>
<citOnlineRes>
<linkage>http://www.pictometry.com</linkage>
</citOnlineRes>
</srcCitatn>
<srcExt>
<exDesc>ground condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2005-04-04</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<prcStep>
<stepDesc>Sensor Size Pixels: 4008 x 2672 (or 3208 x 2672 for some Community level imagery) in a Landscape orientation. Image Format Industry-standard image format with proprietary image trailer, including JFIF (JPEG), TIFF, and BMP. Image Quality Images will have an unobstructed view of the ground. In controlled airspace around airports, etc., and in areas of rapid elevation changes, the image footprint sizes and resolutions may vary. There may be varying degrees of ground illumination and color variations due to lighting and cloud shadows. Measurement Accuracy 0.5% measurement error, excluding user pixel selection error Pixel Placement Accuracy Pictometry provides a visualization system and therefore does not certify image accuracy. However, some Pictometry customers have done their own certification on the Pictometry data after delivery and have shared their results. On average, customers have been seeing better than 1.0-meter RMS error at a 95% confidence level (NMAS 1:1200) for orthogonal imagery over relatively flat terrain or in areas with accurate elevation data, and 2.0-meter RMS error at a 95% confidence level (NMAS 1:2400) for more varied terrain or in areas with poor elevation data. However, Pictometry does not guarantee these accuracies and your results may vary. Sensor Orientation Pictometry utilizes an IMU (Inertial Measurement Unit), ground station post-corrected differential GPS, and Kalman filtering to achieve a high degree of positional and directional accuracy. Sensor Positional Accuracy mean 15cm absolute Sensor Directional Accuracy 0.015 degrees absolute (roll/pitch) 0.035 degrees absolute (heading) Ortho-Rectification The images are ortho-rectified to back out the optical deviations of the capture system and the variations due to elevation changes (utilizing the best DEM data available, including customer provided DEM data), resulting in geographically square pixels aligned to a rectilinear grid. This grid can be one of any number of coordinate systems, including Latitude/Longitude, State Plane, UTM, and more. The desired coordinate system should be specified in the contract, or a default coordinate system will be used. Image Export J FIF (JPEG), TIFF, BMP EFS software can be utilized to export the images into any of the above industry-standard formats. The orthogonal images can optionally be re-projected during this export process, and an associated geography file can be created as well for use in importing the images into GIS mapping software. Image Tiling Individual orthogonal images are edge-feathered and mosaiced to produce orthogonal image tiles with tile sizes selected to balance single image coverage as well as manageability of open images. These orthogonal tiles provide continuous coverage across the area of interest. While some color balancing is done, these orthogonal tiles are not fully radiometrically balanced or edge-matched.</stepDesc>
<stepDateTm>2007-04-06</stepDateTm>
<stepProc>
<rpOrgName>Pictometry Inc</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum>888-771-9714</voiceNum>
<faxNum>585-486-0098</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>100 Town Centre Drive, Suite A</delPoint>
<city>Rochester</city>
<adminArea>NY</adminArea>
<postCode>14623-4260</postCode>
<country>US</country>
<eMailAdd>info@pictometry.com</eMailAdd>
</cntAddress>
<cntHours>8:30 Am - 5:00 p,</cntHours>
</rpCntInfo>
<role>
<RoleCd value="009">
</RoleCd>
</role>
</stepProc>
<stepSrc type="produced">
<srcCitatn>
<resAltTitle>Analytical Aerotriangulation</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
</dataLineage>
</dqInfo>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="26985">
</identCode>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">4.5(3.0.1)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<mdDateSt Sync="TRUE">20261014</mdDateSt>
<spatRepInfo>
<Georect>
<cellGeo>
<CellGeoCd Sync="TRUE" value="002">
</CellGeoCd>
</cellGeo>
<numDims Sync="TRUE">2</numDims>
<tranParaAv Sync="TRUE">1</tranParaAv>
<chkPtAv Sync="TRUE">0</chkPtAv>
<cornerPts>
<pos Sync="TRUE">389481.534155 124899.060167</pos>
</cornerPts>
<cornerPts>
<pos Sync="TRUE">389481.534155 149037.744475</pos>
</cornerPts>
<cornerPts>
<pos Sync="TRUE">408923.545864 149037.744475</pos>
</cornerPts>
<cornerPts>
<pos Sync="TRUE">408923.545864 124899.060167</pos>
</cornerPts>
<centerPt>
<pos Sync="TRUE">399202.540009 136968.402321</pos>
</centerPt>
<axisDimension type="002">
<dimSize Sync="TRUE">63786</dimSize>
<dimResol>
<value Sync="TRUE" uom="m">0.304801</value>
</dimResol>
</axisDimension>
<axisDimension type="001">
<dimSize Sync="TRUE">79195</dimSize>
<dimResol>
<value Sync="TRUE" uom="m">0.304801</value>
</dimResol>
</axisDimension>
<ptInPixel>
<PixOrientCd Sync="TRUE" value="001">
</PixOrientCd>
</ptInPixel>
</Georect>
</spatRepInfo>
<contInfo>
<ImgDesc>
<contentTyp>
<ContentTypCd Sync="TRUE" value="001">
</ContentTypCd>
</contentTyp>
<covDim>
<Band>
<dimDescrp Sync="TRUE">Band_1</dimDescrp>
<bitsPerVal Sync="TRUE">8</bitsPerVal>
<valUnit>
<UOM type="length">
</UOM>
</valUnit>
</Band>
<Band>
<dimDescrp Sync="TRUE">Band_2</dimDescrp>
<bitsPerVal Sync="TRUE">8</bitsPerVal>
<valUnit>
<UOM type="length">
</UOM>
</valUnit>
</Band>
<Band>
<dimDescrp Sync="TRUE">Band_3</dimDescrp>
<bitsPerVal Sync="TRUE">8</bitsPerVal>
<valUnit>
<UOM type="length">
</UOM>
</valUnit>
</Band>
</covDim>
</ImgDesc>
</contInfo>
</metadata>
