<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<metadata xml:lang="en">
<Esri>
<CreaDate>20261008</CreaDate>
<CreaTime>12151800</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<imsContentType>002</imsContentType>
<itemName Sync="TRUE">Ortho_2005</itemName>
<nativeExtBox>
<westBL Sync="TRUE">389400.000000</westBL>
<eastBL Sync="TRUE">408600.000000</eastBL>
<southBL Sync="TRUE">124200.000000</southBL>
<northBL Sync="TRUE">148200.000000</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: 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">None</CompressionType>
<NumBands Sync="TRUE">3</NumBands>
<Format Sync="TRUE">AMD</Format>
<HasPyramids Sync="TRUE">TRUE</HasPyramids>
<SourceType Sync="TRUE">continuous</SourceType>
<PixelType Sync="TRUE">unsigned integer</PixelType>
<NoDataValue Sync="TRUE">
</NoDataValue>
</General>
<Properties>
<MaxImageHeight Sync="TRUE">4100</MaxImageHeight>
<MaxImageWidth Sync="TRUE">15000</MaxImageWidth>
<MaxRecordCount Sync="TRUE">1000</MaxRecordCount>
<MaxDownloadImageCount Sync="TRUE">20</MaxDownloadImageCount>
<MaxDownloadSizeLimit Sync="TRUE">2048</MaxDownloadSizeLimit>
<MaxMosaicImageCount Sync="TRUE">20</MaxMosaicImageCount>
<DefaultCompressionQuality Sync="TRUE">75</DefaultCompressionQuality>
<DefaultCompressionTolerance Sync="TRUE">0.01</DefaultCompressionTolerance>
<BlendWidth Sync="TRUE">10</BlendWidth>
<ViewpointSpacingX Sync="TRUE">600</ViewpointSpacingX>
<ViewpointSpacingY Sync="TRUE">300</ViewpointSpacingY>
<AllowedItemMetadata Sync="TRUE">Basic</AllowedItemMetadata>
<DefaultResamplingMethod Sync="TRUE">1</DefaultResamplingMethod>
<AllowedMosaicMethods Sync="TRUE">NorthWest,Center,LockRaster,ByAttribute,Nadir,Viewpoint,Seamline,None</AllowedMosaicMethods>
<AllowedCompressions Sync="TRUE">None,JPEG,LZ77,LERC</AllowedCompressions>
<AllowedMensurationCapabilities Sync="TRUE">Basic</AllowedMensurationCapabilities>
<AvailableMensurationCapabilities Sync="TRUE">None,Basic,Base-Top Height,Top-Top Shadow Height,Base-Top Shadow Height,3D</AvailableMensurationCapabilities>
<ClipToBoundary Sync="TRUE">-1</ClipToBoundary>
<FootprintMayContainNoData Sync="TRUE">-1</FootprintMayContainNoData>
<CellSizeTolerance Sync="TRUE">0.8</CellSizeTolerance>
<MinimumPixelContribution Sync="TRUE">1</MinimumPixelContribution>
<AvailableMosaicMethods Sync="TRUE">NorthWest,Center,LockRaster,ByAttribute,Nadir,Viewpoint,Seamline,None</AvailableMosaicMethods>
<AvailableCompressionMethods Sync="TRUE">None,JPEG,LZ77,LERC</AvailableCompressionMethods>
<AvailableItemMetadataLevels Sync="TRUE">None,Basic,Full</AvailableItemMetadataLevels>
<BandDefinitionKeyword Sync="TRUE">NONE</BandDefinitionKeyword>
<_docversion_ Sync="TRUE">10</_docversion_>
<AllowedFields Sync="TRUE">Name,MinPS,MaxPS,LowPS,HighPS,Tag,GroupName,ProductName,CenterX,CenterY,ZOrder,Shape_Length,Shape_Area</AllowedFields>
<MaxCellSize Sync="TRUE">4608</MaxCellSize>
<LowCellSize Sync="TRUE">0.16</LowCellSize>
<HighCellSize Sync="TRUE">10.24</HighCellSize>
<ClipToFootprint Sync="TRUE">-1</ClipToFootprint>
</Properties>
<Functions Sync="TRUE">
<Function Description="Performs on-the-fly mosaic on a raster catalog." Name="Mosaic Function">
</Function>
</Functions>
</RasterProperties>
</DataProperties>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<SyncDate>20261008</SyncDate>
<SyncTime>16104000</SyncTime>
<ModDate>20261008</ModDate>
<ModTime>16104000</ModTime>
</Esri>
<mdLang>
<languageCode value="eng">
</languageCode>
<countryCode Sync="TRUE" value="USA">
</countryCode>
</mdLang>
<mdChar>
<CharSetCd value="004">
</CharSetCd>
</mdChar>
<mdHrLv>
<ScopeCd value="005">
</ScopeCd>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<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>
<mdDateSt Sync="TRUE">20261008</mdDateSt>
<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>Most DC GIS datasets can be downloaded from "http//dcgis.dc.gov" on the data center page. Orders can also be made by contacting OCTO GIS at "dcgis@dc.gov", especially for datasets not available for download</ordInstr>
</distorOrdPrc>
<distorFormat>
<formatName>TIFF</formatName>
<fileDecmTech>No compression applied</fileDecmTech>
</distorFormat>
<distorTran>
<transSize>643.730</transSize>
<onLineSrc>
<linkage>http://dcgis.dc.gov</linkage>
</onLineSrc>
</distorTran>
</distributor>
<distTranOps>
<onLineSrc>
<linkage>withheld</linkage>
</onLineSrc>
</distTranOps>
<distFormat>
<formatName Sync="TRUE">Raster Dataset</formatName>
</distFormat>
</distInfo>
<dataIdInfo>
<idCitation>
<resTitle>Ortho_2005</resTitle>
<date>
<pubDate>2006-06-30</pubDate>
</date>
<citRespParty>
<rpOrgName>DC GIS</rpOrgName>
<role>
<RoleCd value="006">
</RoleCd>
</role>
</citRespParty>
<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>
<presForm>
<PresFormCd value="005">
</PresFormCd>
</presForm>
<presForm>
<fgdcGeoform>remote-sensing image</fgdcGeoform>
</presForm>
</idCitation>
<idAbs>&lt;div style='text-align:Left;'&gt;&lt;div&gt;&lt;div&gt;&lt;p&gt;&lt;span&gt;2005 Orthophoto - This document describes the processes used to update the planimetric and topographic data originally produced for the District of Columbia from the 2005 aerial photography. The project area covers the entire District of Columbia which is approximately 69 square miles. The digital imagery was used to create natural color digital orthophotography with 15cm pixel resolution. The final orthophotography deliverable products for this project consist of 328 ortho tiles at a scale of 1 to 2400. The tile dimensions are 800 meters by 800 meters. A corresponding MrSid image was created by mosaicking the 328 ortho tiles together and compressing the image using an 80 to 1 compression ration. 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.&lt;/span&gt;&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</idAbs>
<idPurp>Aerial Photography (Orthophoto) - 2005
This data is used for the planning and management of Washington, D.C. by local government agencies.</idPurp>
<idCredit>D.C. Office of the Chief of Technology Officer (OCTO)
EarthData International, Inc
7320 Executive Way
Frederick, MD 21704
(301)948-8550</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>United States of America (USA)</keyword>
<keyword>Washington</keyword>
<keyword>D.C.</keyword>
<keyword>District of Columbia</keyword>
<keyword>D.C.</keyword>
</placeKeys>
<themeKeys>
<keyword>Planimetric</keyword>
<keyword>Topographic</keyword>
<keyword>Aerial Photography</keyword>
<keyword>Planning</keyword>
<keyword>Imagery</keyword>
<keyword>Orthos</keyword>
<keyword>Orthophotography</keyword>
</themeKeys>
<searchKeys>
<keyword>Planimetric</keyword>
<keyword>Topographic</keyword>
<keyword>Aerial Photography</keyword>
<keyword>Planning</keyword>
<keyword>Imagery</keyword>
<keyword>Orthos</keyword>
<keyword>Orthophotography</keyword>
<keyword>United States of America (USA)</keyword>
<keyword>Washington</keyword>
<keyword>D.C.</keyword>
<keyword>District of Columbia</keyword>
<keyword>D.C.</keyword>
</searchKeys>
<resConst>
<Consts>
<useLimit>&lt;div style='text-align:Left;'&gt;&lt;div&gt;&lt;div&gt;&lt;p&gt;&lt;span&gt;Data cannot be redistributed in any manner without written authorization. OCTO makes no claims as to the completeness, accuracy or content of any data contained heron, 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>
<resConst>
<LegConsts>
<useLimit>OCTO 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. Subject to terms and conditions of the Memorandum of Agreement. Memorandum of Agreement must have authorized signature.</useLimit>
<accessConsts>
<RestrictCd value="008">
</RestrictCd>
</accessConsts>
<othConsts>Contact OCTO GIS. Any data obtained outside of OCTO GIS are unauthorized copies.</othConsts>
</LegConsts>
</resConst>
<spatRpType>
<SpatRepTypCd value="002">
</SpatRepTypCd>
</spatRpType>
<dataLang>
<languageCode value="eng">
</languageCode>
<countryCode Sync="TRUE" value="USA">
</countryCode>
</dataLang>
<envirDesc>ESRI ArcCatalog 9.1.0.722</envirDesc>
<dataExt>
<geoEle>
<GeoBndBox>
<exTypeCode>true</exTypeCode>
<westBL>-077.191347</westBL>
<eastBL>-076.831779</eastBL>
<northBL>+39.015550</northBL>
<southBL>+38.772940</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<dataExt>
<exDesc>ground condition</exDesc>
</dataExt>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-77.122373</westBL>
<eastBL Sync="TRUE">-76.900716</eastBL>
<northBL Sync="TRUE">39.001746</northBL>
<southBL Sync="TRUE">38.785481</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<tpCat>
<TopicCatCd value="010">
</TopicCatCd>
</tpCat>
<tpCat>
<TopicCatCd value="015">
</TopicCatCd>
</tpCat>
</dataIdInfo>
<mdMaint>
<maintFreq>
<MaintFreqCd value="012">
</MaintFreqCd>
</maintFreq>
</mdMaint>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005">
</ScopeCd>
</scpLvl>
</dqScope>
<report type="DQQuanAttAcc">
<measDesc>N/A</measDesc>
</report>
<report type="DQConcConsis">
<measDesc>Compliance with the accuracy standard was ensured by the placement of photo identifiable ground control points and the collection of airborne GPS data. The elevation data were generated by autocorrelation and manual processes. An RMSE value for each tile was calculated based on the photos utilized in the production of the tile by comparing the AT X and Y coordinates. This value represents an estimate of the accuracy of the horizontal coordinate measurements in the tile expressed in meters.</measDesc>
</report>
<report type="DQCompOm">
<measDesc>Compliance with the accuracy standard was ensured by the placement of photo identifiable ground control points
and the collection of airborne GPS data.</measDesc>
</report>
<report dimension="horizontal" type="DQAbsExtPosAcc">
<measDesc>The horizontal accuracy of the orthorectified images is mainly determined by the accuracy of the aerotriangulation and digital surface model (DSM). For each rectified image, an RMSE value for all of the standard errors of the tie/pass/control points located in that image and computed by the aerotriangulation solution was calculated. The DSM accuracy assessment was achieved by comparing the aerotriangulation-derived elevation with the elevation of the DSM. In addition, visual examination was employed to assess all tiles and its relative edge match. All results were examined for consistency and its compliance with the ASPRS Standards for Large Scale Mapping at 1 to 1200 which states that the orthos will meet 1 foot RMSE at the 95% confidence clevel.</measDesc>
</report>
<report dimension="vertical" type="DQAbsExtPosAcc">
<measDesc>N/A</measDesc>
</report>
<dataLineage>
<prcStep>
<stepDesc>Metadata imported.</stepDesc>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>withheld</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<dataSource>
<srcDesc>This aerial photography was composed of 24 flight lines and a total of 1023 exposures. Imagery was obtained at an altitude of 1,100 meters above mean terrain (AMT) 7200. The mission was flown with two Wild RC30 cameras serial no. 5368 with 153.743 mm lens serial number 13413 and serial no. 5324 with 153.247 mm lens serial number 13365 with ABGPS.</srcDesc>
<srcMedName>
<MedNameCd value="filmstrip">
</MedNameCd>
</srcMedName>
<srcCitatn>
<resTitle>Aerial Photography of Washington, D.C.</resTitle>
<resAltTitle>Aerial Photography</resAltTitle>
<date>
<pubDate>2006-06-30</pubDate>
</date>
<citRespParty>
<rpOrgName>EarthData International, Inc</rpOrgName>
<role>
<RoleCd value="006">
</RoleCd>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005">
</PresFormCd>
</presForm>
<presForm>
<fgdcGeoform>remote-sensing image</fgdcGeoform>
</presForm>
</srcCitatn>
<srcExt>
<exDesc>ground condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2005-04-04</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>TerraSurv established 30 photo identification control points to support the aerotriangulation process. Continuously Operating Reference Station (CORS) station USNO (PIDAI7403) was used as the control for this project. The horizontal datum was the North American Datum of 1983, CORS adjustment (NAD 1983 CORS). The vertical datum was the North American Vertical Datum of 1988
(NAVD 1988).</srcDesc>
<srcMedName>
<MedNameCd value="015">
</MedNameCd>
</srcMedName>
<srcCitatn>
<resTitle>Report of Survey Washington, DC Area</resTitle>
<resAltTitle>GPS ground control</resAltTitle>
<date>
<pubDate>2006-06-30</pubDate>
</date>
<citRespParty>
<rpOrgName>TerraSurv, Inc</rpOrgName>
<role>
<RoleCd value="006">
</RoleCd>
</role>
</citRespParty>
<presForm>
<PresFormCd value="008">
</PresFormCd>
</presForm>
<presForm>
<fgdcGeoform>model</fgdcGeoform>
</presForm>
</srcCitatn>
<srcExt>
<exDesc>Ground Condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2005-08-01</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<prcStep>
<stepDesc>Source photography - Wild RC-30 camera, natural color stable base.
Control - airborne GPS supplemented with photo identifiable field control.
Scanning - Z/I Imaging PhotoScan flatbed metric scanner.
Aerotriangulation - Photo-T.
Elevation Model - Lidar, autocorrelation and manual collection and update.
Radiometric Balancing - Proprietary and COTS Software (PhotoShop).
Orthorectification - Z/I Ortho Pro 4.0 software package.
Mosaic - Z/I Ortho Pro 4.0 software package.
Processed on Windows NT/2000 systems.
Analytical Aerotriangulation:
The ground control and airborne GPS data was integrated into a rigid network through the completion of a fully analytical bundle aerotriangulation adjustment.
1. The original aerial film was scanned at a resolution of 21 microns. The scans were produced using Z/I Imaging PhotoScan flatbed metric scanners.
2. The raster scans were given a preliminary visual check on the scanner workstation to ensure that the raster file size is correct and to verify that the tone and contrast were acceptable. A directory tree structure for the project was established on one of the workstations. This project was then accessed by other workstations through the network. The criteria used for establishment of the directory structure and file naming conventions accessed through the network avoids confusion or errors due to inconsistencies in digital data. The project area was defined using the relevant camera information that was obtained from the USGS camera calibration report for the aerial camera and the date of photography. The raster files were rotated to the correct orientation for mensuration on the softcopy workstation. The rotation of the raster files was necessary to accommodate different flight directions from one strip to the next. The technician verified that the datum and units of measurement for the supplied control were consistent with the project requirements.
3. The photogrammetric technician performed an automatic interior orientation for the frames in the project area. The softcopy systems that were used by the technicians have the ability to set up predefined fiducial templates for the aerial camera(s) used for the project. Using the template that was predefined in the interior orientation setup, the software identified and measured the eight fiducial positions for all the frames. Upon completion, the results were reviewed against the tolerance threshold. Any problems that occurred during the automatic interior orientation would cause the software to reject the frame and identify it as a potential problem. The operator then had the option to measure the fiducials manually.
4. The operator launched the point selection routine which automatically selected pass and tie points by an autocorrelation process. The correlation tool that is part of the routine identified the same point of contrast between multiple images in the Von Gruber locations. The interpolation tool can be adjusted by the operator
depending on the type of land cover in the triangulation block. Factors that influence the settings include the amount of contrast and the sharpness of features present on the photography. A preliminary adjustment was run to identify pass points that had high residuals. This process was accomplished for each flight line or partial flight line to ensure that the network has sufficient levels of accuracy. The points were visited and the cause for any inaccuracy was identified and rectified. This process also identified any gaps where the point selection routine failed to establish a point. The operator interactively set any missing points.
5. The control and pass point measurement data was run through a final adjustment on the Z/I SSK PhotoT workstations. The PhotoT program created a results file with the RMSE results for all points within the block and their relation to one another. The photogrammetrist performing the adjustments used their experience to determine what course of action to take for any point falling outside specifications.
6. The bundle adjustment was run through thePhotoT software several times. The photogrammetrist increased the accuracy parameters for each subsequent iteration so, when the final adjustment was run, the RMSE for the project met the accuracy of 1 part in 10,000 of the flying height for the horizontal position (X and Y) and 1 part in 9,000 or better of the flying height in elevation (Z). The errors were expressed as a natural ratio of the flying height utilizing a one-sigma (95%) confidence level.
7. The accuracy of the final solution was verified by running the final adjustment, placing no constraints on any quality control points. The RMSE values for these points must fall within the tolerances above for the solution to be acceptable.
8. The final adjustment generates three files. The .txt file has all the results from the adjustment with the RMSE values for each point measured. The .XYZ file contains the adjusted X, Y, Z,coordinates for all the measured points and the .PHT file contains the exterior orientation parameters of each exposure station.</stepDesc>
<stepDateTm>2006-06-30</stepDateTm>
<stepProc>
<rpOrgName>EarthData International, Inc</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum>(301)948-8550</voiceNum>
<faxNum>(301)963-2064</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>7320 Executive Way</delPoint>
<city>Frederick</city>
<adminArea>MD</adminArea>
<postCode>21704</postCode>
<eMailAdd>metadata@earthdata.com</eMailAdd>
</cntAddress>
<cntHours>8:30 Am - 5:00 PM Mon - Fri</cntHours>
</rpCntInfo>
<role>
<RoleCd value="009">
</RoleCd>
</role>
</stepProc>
<stepSrc type="produced">
<srcCitatn>
<resAltTitle>Analytical Aerotriangulation</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>Digital Elevation Model (DEM):
Both Lidar and previously produced DEM data was available to support the production process. Following an analysis of the data the previously produced DEM was selected for update and use.
The following provides a step-by-step outline of the production process.
1. The existing DEM which was comprised of both gridded mass points from 10 to 20 meters with spots, and vertices of contour lines was converted to dgn files for compilation. 2. The DEM was then merged together in MicroStation V8, and then split into 34 tiles, approximately 3077m X 3029m.
3. The compilation team updated the data with breaklines where needed, and collected 3D bridges. 3D bridges were collected to prevent smearing and warping, caused by the elevation difference between the bare earth and the elevated bridges. Proprietary MDLsfor Microstation were run to create a 10 to 15 meter buffer around the bridges and to clip the surrounding ground data.
4. The dgn files were then merged into four large areas for QC purposes. The files were imported into TerraSolid/TerraModler and a tin and a color relief was generated to search for any spikes or mismatches. This check in performed to fix any problems before going to the ortho stage. Large water areas were filled with elevation points.
5. Complex lines, shapes and arcs were dropped before delivering to the ortho epartment. A final level listing was run to ensure all the lines were dropped and the files wereclean. This listing was provided to the ortho team.</stepDesc>
<stepDateTm>2006-06-30</stepDateTm>
<stepProc>
<rpOrgName>EarthData International, Inc</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum>(301)948-8550</voiceNum>
<faxNum>(301)963-2064</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>7320 Executive Way</delPoint>
<city>Frederick</city>
<adminArea>MD</adminArea>
<postCode>21704</postCode>
<country>U.S.</country>
<eMailAdd>metadata@earthdata.com</eMailAdd>
</cntAddress>
<cntHours>8:30 Am - 5:00 PM Mon - Fri</cntHours>
</rpCntInfo>
<role>
<RoleCd value="009">
</RoleCd>
</role>
</stepProc>
<stepSrc type="produced">
<srcCitatn>
<resAltTitle>Digital Elevation Model (DEM)</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>Orthophotography:
The digital orthophotography was produced in natural color with a 0.15 meter pixel resolution. A step-by-step breakdown of the digital orthophoto production process follows:
1. A representative number of raster image files were visually checked for image quality on the workstation. 2. The digital image files were oriented on the digital orthophoto production workstation. The following information was then loaded onto the workstation. - The camera calibration parameters and flight line direction.
- Ground control and pass point locations.
- The exterior orientation parameters from the aerotriangulation process.
- ASCII file containing the corner coordinates of the orthophotos.
- The digital elevation model in a DGN format referenced to Maryland State Plane, NAD83, meters.
- Project-specific requirements such as final sheet size and resolution.
- Orientation parameters developed from the aerotriangulation solution.
3. A coordinate transformation based on the camera calibration fiducial coordinates was then undertaken. This transformation allowed the conversion of every measured element of the plates to a sample/line location. Each pixel in an image was then referenced by sample and line (its horizontal and vertical position) and matched to project control. The newly rectified image was visually checked for pixel drop-out and/or other artifacts that may degrade the final orthophoto image.
4. DEM data was imported and written to the correct subdirectory on disk. The final digital orthophotos were referenced to Maryland State Plane Coordinates system, NAD83, meters.
5. The DEM file was reinspected for missing or erroneous data points.
6. A complete differential rectification was carried out using an exponential algorithm that removed image displacement due to topographic relief, tip and tilt of the aircraft at the moment of exposure, and radial distortion within the camera. Each final orthophoto was produced at a 0.15 meter pixel resolution.
7. Each digital orthophoto image was visually checked for accuracy on the workstation screen. The digital orthophotos were then edge-matched using a module of the Ortho Pro software package.
8. Once the orthophotos were inspected and approved for accuracy, the files were copied to the network and downloaded by the orthophoto finishing department. This production unit was responsible for radiometrically correcting the orthophotos prior to completing the mosaicking and clipping of the final tiles. The final 800 X 800-meter tiles are clipped out and the imagery is output in GeoTIFF format.
9. The processed images were mosaicked using the Ortho Pro software. File names were assigned.
10. The finishing department performed final visual checks for orthophoto image quality. The images were inspected using Adobe Photoshop, which enabled the technician to remove dust and lint from the image files interactively.
11. The final orthophoto images were written out into Arc/Info readable, GeoTIFF format.
12. A corresponding MrSid image was created by mosaicking the 328 ortho tiles together and compressing the image using an 80 to 1 compression ratio.</stepDesc>
<stepDateTm>2006-06-30</stepDateTm>
<stepProc>
<rpOrgName>EarthData International, Inc</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum>(301)948-8550</voiceNum>
<faxNum>(301)963-2064</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>7320 Executive Way</delPoint>
<city>Frederick</city>
<adminArea>MD</adminArea>
<postCode>21704</postCode>
<country>U.S.</country>
<eMailAdd>metadata@earthdata.com</eMailAdd>
</cntAddress>
<cntHours>8:30 Am - 5:00 PM Mon - Fri</cntHours>
</rpCntInfo>
<role>
<RoleCd value="009">
</RoleCd>
</role>
</stepProc>
<stepSrc type="produced">
<srcCitatn>
<resAltTitle>Orthophotography</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
</dataLineage>
</dqInfo>
<spatRepInfo>
<Georect>
<numDims>3</numDims>
<axisDimension type="001">
<dimSize>150000</dimSize>
<dimResol>
<value Sync="TRUE" uom="m">0.160000</value>
</dimResol>
</axisDimension>
<axisDimension type="002">
<dimSize>120000</dimSize>
<dimResol>
<value Sync="TRUE" uom="m">0.160000</value>
</dimResol>
</axisDimension>
<axisDimension type="003">
<dimSize>1</dimSize>
</axisDimension>
<cellGeo>
<CellGeoCd Sync="TRUE" value="002">
</CellGeoCd>
</cellGeo>
<tranParaAv Sync="TRUE">1</tranParaAv>
<chkPtAv Sync="TRUE">0</chkPtAv>
<cornerPts>
<pos Sync="TRUE">389400.000000 124200.000000</pos>
</cornerPts>
<cornerPts>
<pos Sync="TRUE">389400.000000 148200.000000</pos>
</cornerPts>
<cornerPts>
<pos Sync="TRUE">408600.000000 148200.000000</pos>
</cornerPts>
<cornerPts>
<pos Sync="TRUE">408600.000000 124200.000000</pos>
</cornerPts>
<centerPt>
<pos Sync="TRUE">399000.000000 136200.000000</pos>
</centerPt>
<ptInPixel>
<PixOrientCd Sync="TRUE" value="001">
</PixOrientCd>
</ptInPixel>
</Georect>
</spatRepInfo>
<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>
<contInfo>
<ImgDesc>
<contentTyp>
<ContentTypCd Sync="TRUE" value="001">
</ContentTypCd>
</contentTyp>
<covDim>
<Band>
<dimDescrp Sync="TRUE">Band_1</dimDescrp>
<maxVal Sync="TRUE">255.000000</maxVal>
<minVal Sync="TRUE">0.000000</minVal>
<bitsPerVal Sync="TRUE">8</bitsPerVal>
<valUnit>
<UOM type="length">
</UOM>
</valUnit>
</Band>
<Band>
<dimDescrp Sync="TRUE">Band_2</dimDescrp>
<maxVal Sync="TRUE">255.000000</maxVal>
<minVal Sync="TRUE">0.000000</minVal>
<bitsPerVal Sync="TRUE">8</bitsPerVal>
<valUnit>
<UOM type="length">
</UOM>
</valUnit>
</Band>
<Band>
<dimDescrp Sync="TRUE">Band_3</dimDescrp>
<maxVal Sync="TRUE">255.000000</maxVal>
<minVal Sync="TRUE">0.000000</minVal>
<bitsPerVal Sync="TRUE">8</bitsPerVal>
<valUnit>
<UOM type="length">
</UOM>
</valUnit>
</Band>
</covDim>
</ImgDesc>
</contInfo>
<eainfo>
<detailed Name="OrthoMosaic05.sid.vat">
<enttyp>
<enttypl Sync="TRUE">OrthoMosaic05.sid.vat</enttypl>
<enttypt Sync="TRUE">Table</enttypt>
<enttypc Sync="TRUE">256</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">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="OrthoMosaic05.sid(Band_2).vat">
<enttyp>
<enttypl Sync="TRUE">OrthoMosaic05.sid(Band_2).vat</enttypl>
<enttypt Sync="TRUE">Table</enttypt>
<enttypc Sync="TRUE">256</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">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="OrthoMosaic05.sid(Band_3).vat">
<enttyp>
<enttypl Sync="TRUE">OrthoMosaic05.sid(Band_3).vat</enttypl>
<enttypt Sync="TRUE">Table</enttypt>
<enttypc Sync="TRUE">256</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">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>
</metadata>
