<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<metadata xml:lang="en">
<Esri>
<CreaDate>20200219</CreaDate>
<CreaTime>13012200</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<ArcGISstyle>FGDC CSDGM Metadata</ArcGISstyle>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">Orthophotos_2019</itemName>
<itemLocation>
<linkage Sync="TRUE">file://\\OCTO-5GS23W2\E$\ProductionFiles\Ortho_2019\Orthophotos_2019.gdb</linkage>
<protocol Sync="TRUE">Local Area Network</protocol>
</itemLocation>
<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/10.8'&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">4</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"/>
</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">None</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>
<AllowedFields Sync="TRUE">Name,MinPS,MaxPS,LowPS,HighPS,Tag,GroupName,ProductName,CenterX,CenterY,ZOrder,Shape_Length,Shape_Area</AllowedFields>
<MaxCellSize Sync="TRUE">8748</MaxCellSize>
<LowCellSize Sync="TRUE">0.08</LowCellSize>
<HighCellSize Sync="TRUE">174.96</HighCellSize>
<ApplyColorCorrection Sync="TRUE">0</ApplyColorCorrection>
<TimeStamp.RemoveItems Sync="TRUE">44028.7512819676</TimeStamp.RemoveItems>
<TimeStamp.UpdateExtent Sync="TRUE">44028.8467769907</TimeStamp.UpdateExtent>
<_docversion_ Sync="TRUE">9</_docversion_>
</Properties>
<Functions Sync="TRUE">
<Function Description="Performs on-the-fly mosaic on a raster catalog." Name="Mosaic Function"/>
</Functions>
</RasterProperties>
</DataProperties>
<SyncDate>20231002</SyncDate>
<SyncTime>12450900</SyncTime>
<ModDate>20231002</ModDate>
<ModTime>13442200</ModTime>
<ArcGISProfile>FGDC</ArcGISProfile>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
</Esri>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdContact>
<rpIndName>GIS Data Coordinator</rpIndName>
<rpOrgName>D.C. Office of the Chief Technology Officer</rpOrgName>
<rpCntInfo>
<cntPhone>
<faxNum>(202) 727-5660</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>200 I Street SE, 5th Floor</delPoint>
<city>Washington</city>
<adminArea>DC</adminArea>
<postCode>20003</postCode>
<country>US</country>
<eMailAdd>dcgis@dc.gov</eMailAdd>
</cntAddress>
<cntHours>8:30 am - 5 pm</cntHours>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdDateSt Sync="TRUE">20231002</mdDateSt>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distributor>
<distorCont>
<rpIndName>GIS Data Coordinator</rpIndName>
<rpOrgName>D.C. Office of the Chief Technology Officer</rpOrgName>
<rpCntInfo>
<cntPhone>
<faxNum>(202) 727-5660</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>200 I Street SE, 5th Floor</delPoint>
<city>Washington</city>
<adminArea>DC</adminArea>
<postCode>20003</postCode>
<country>US</country>
<eMailAdd>dcgis@dc.gov</eMailAdd>
</cntAddress>
<cntHours>8:30 am - 5 pm</cntHours>
</rpCntInfo>
<role>
<RoleCd value="005"/>
</role>
</distorCont>
<distorOrdPrc>
<ordInstr>DC datasets can be downloaded from "http://opendata.dc.gov".</ordInstr>
</distorOrdPrc>
<distorFormat>
<formatName>Image Service</formatName>
</distorFormat>
</distributor>
</distInfo>
<dataIdInfo>
<idCitation>
<resTitle>Ortho_2019</resTitle>
<date>
<pubDate>2020-02-13</pubDate>
</date>
<citRespParty>
<rpOrgName>DC GIS</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>200 I Street SE, 5th floor, Washington, DC, 20003, US</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</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;2019 Orthophoto - 3 inch resolution: This document describes the processes used to create the orthoimagery data produced for the District of Columbia from 2019 digital aerial photography. It was flown on April 23, 2019. The aerial imagery acquisition was flown to support the creation of 4-band digital orthophotography with a 3 inch/0.08 meter pixel resolution over the full project area covering the District of Columbia which is approximately 69 square miles. The contractor received waivers to fly in the Flight Restricted Zone (FRZ) and P-56 areas. The ortho imagery was submitted to DC OCTO in GeoTiff/TFW format tiles following the tile scheme provided by OCTO. MrSID and JPEG2000 compressed mosaics were delivered as well using a 50:1 compression ratio.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>This data is used for the planning and management of Washington, D.C. by local government agencies.</idPurp>
<idCredit>http://dcgis.dc.gov</idCredit>
<idStatus>
<ProgCd value="001"/>
</idStatus>
<idPoC>
<rpIndName>GIS Data Coordinator</rpIndName>
<rpOrgName>D.C. Office of the Chief Technology Officer</rpOrgName>
<rpCntInfo>
<cntPhone>
<faxNum>(202) 727-5660</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>200 I Street SE, 5th Floor</delPoint>
<city>Washington</city>
<adminArea>DC</adminArea>
<postCode>20003</postCode>
<country>US</country>
<eMailAdd>dcgis@dc.gov</eMailAdd>
</cntAddress>
<cntHours>8:30 am - 5 pm</cntHours>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="009"/>
</maintFreq>
</resMaint>
<placeKeys>
<thesaName>
<resTitle>Geographic Names Information System</resTitle>
</thesaName>
<keyword>D.C.</keyword>
<keyword>Washington</keyword>
<keyword>D.C.</keyword>
<keyword>District of Columbia</keyword>
<keyword>United States of America (USA)</keyword>
</placeKeys>
<themeKeys>
<keyword>Orthophotography</keyword>
<keyword>Planning</keyword>
<keyword>Imagery</keyword>
<keyword>Orthos</keyword>
<keyword>Aerial Photography</keyword>
<keyword>imageryBaseMapsEarthCover</keyword>
</themeKeys>
<themeKeys>
<thesaName>
<resTitle>ISO 19115 Topic Categories</resTitle>
</thesaName>
<keyword>imageryBaseMapsEarthCover</keyword>
</themeKeys>
<searchKeys>
<keyword>Orthophotography</keyword>
<keyword>Planning</keyword>
<keyword>Imagery</keyword>
<keyword>Orthos</keyword>
<keyword>Aerial Photography</keyword>
<keyword>imageryBaseMapsEarthCover</keyword>
<keyword>imageryBaseMapsEarthCover</keyword>
<keyword>D.C.</keyword>
<keyword>Washington</keyword>
<keyword>D.C.</keyword>
<keyword>District of Columbia</keyword>
<keyword>United States of America (USA)</keyword>
</searchKeys>
<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 Creative Commons Attribution 4.0 International License.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<resConst>
<LegConsts>
<useLimit>See access and use constraints information.</useLimit>
</LegConsts>
</resConst>
<spatRpType>
<SpatRepTypCd value="002"/>
</spatRpType>
<envirDesc> Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.0.10450</envirDesc>
<dataExt>
<geoEle>
<GeoBndBox>
<exTypeCode>true</exTypeCode>
<westBL>-77.122373</westBL>
<eastBL>-76.900716</eastBL>
<northBL>39.001746</northBL>
<southBL>38.785481</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<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"/>
</tpCat>
<tpCat>
<TopicCatCd value="015"/>
</tpCat>
</dataIdInfo>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<report type="DQConcConsis">
<measDesc>Quality control procedures were implemented and documented at each step of the project to ensure that all services required by the contract are completed to specification; they include visual (manual) inspections, automated routines, and technical reviews.</measDesc>
</report>
<report type="DQConcConsis">
<measDesc>Aerial Data Acquisition QA/QC: 1. Flight Planning - The flight plan was based on the scope of work (SOW), DC OCTO provided boudnary, and flight restrictions.
2. Ground GPS Acquisition - The GPS equipment was assembled on a monument or a temporary established point and data was recorded. The data was then checked to ensure the PDOP is less than 3.0.
3. Data Acquisition
Prior to full flight, the following steps was peformed: - Inspect storage and system components to ensure all units are operational and there is sufficient storage space
- Select and confirm the lever arm coordinates
- Load navigation system and perform system check
- Perform 5 minute static alignment and record PDOP, GPS, and UTC start time
- Ensure IMU is operational
- Ensure all channels are operational, as applicable.
After the pre-flight checks, the crew began flight line data recording: observe video display, POS status and mass memory screens; record UTC start/stop times, GPS data, ground speed, altitude, comments/concerns, lines, waypoints and times on the flight log. When the flight mission was completed, a 5 minute static alignment was performed followed by a systematic shutdown of the system. All collected data was downloaded for QC.</measDesc>
</report>
<report type="DQConcConsis">
<measDesc>Ground Control QA/QC:
The Ground Control QA/QC strategy is based on reviewing the criteria described below:
- Incidences of High PDOP
- Poor network closure
- Inadequate point location
- Missing or omitted points
- Damaged or missing panels
The evaluation of the ground control is done through the following steps:
- All planning, reconnaissance, field observations, post-processing, adjustments, and final report development will be performed under the direct supervision of a highly-experienced land surveyor.
- Fixed height tripods will be used during the GPS survey to eliminate antenna height measurement error.
- The field crews will perform processing and closure analysis of the data to eliminate field blunders and determine baselines, which do not fit the network or project tolerances and must be re-observed.
- The final adjustment and processing of target locations will be coordinated, directed and completed by a single surveyor to ensure the overall consistency and integrity of the control network required to accurately map an area of this size. These efforts will also facilitate a smoother aerial triangulation process.</measDesc>
</report>
<report type="DQConcConsis">
<measDesc>IMU/GPS Processing QA/QC:
Airborne GPS control is accomplished through the simultaneous observation of five or more satellites in the GPS constellation using the on-board receiver and one or more ground receivers (base stations) located over known control points that are in the vicinity of the project area.
If accessible to non-airport personnel, the GPS occupation of a primary airport control station (PACS) is established prior to any airborne GPS collection. A GPS receiver is placed on a temporary marker using PK nails to define the location. The GPS station records at a one second interval for the duration of the airborne collection. Coordinates for this base station point is adjusted by the project surveyor and is tied into the project control network. Airborne GPS and IMU data is immediately processed using the airport GPS base station data. When necessary, combination of CORS stations and surveyor established GPS stations are used to ensure that a base station is operating within range of the aircraft at all times. If this occurs, it is included in the pre-planning. Once a decision has been made to fly, any GPS stations established for the project area is activated at a one second interval for the duration of the airborne collection.</measDesc>
</report>
<report type="DQConcConsis">
<measDesc>Aerotriangulation QA/QC:
The Aerotriangulation QA/QC strategy is based on the criteria described in the table below:
- Missing or corrupt ground control information
- Camera calibration
- GPS and IMU data integrity
An initial bundle/block adjustment is developed for each data sortie. The accuracy of each bundle/block is confirmed through an RMSE evaluation against the project ground control. The accuracy is verified through an iterative process where the adjustment is repeatedly run, while progressively increasing the constraints on the ground control.
After the accuracy is verified, the technician applies the bundle adjustment result to the images of each AT block (consisting of multiple lifts or sorties). The results of the adjustment are verified through the generation of the full-resolution panchromatic orthophoto chips over the ground control points for the data sortie. The orthophoto chips are inspected by the photogrammetric technician to identify any errors in the adjustment to ensure the accuracy meets project specification. The technician also generates and visually reviews that orthophoto strips cover across all flight lines to ensure edge matching between flight lines.
The adjustment/inspection process is repeated as bundle/block adjustment for adjoining sorties are complete and these small blocks are adjusted to build the overall bundle adjustment. Throughout the process, the accuracy of each adjustment is checked against the GPS ground control points.</measDesc>
</report>
<report type="DQConcConsis">
<measDesc>Imagery and Orthophoto QA/QC:
The Orthophoto Rectification QA/QC strategy is based on the criteria described below:
- Edge matching
- Fit to ground control
- Radiometric consistency
- Insufficient coverage
- Correct color band rendition
Preliminary field data is reviewed to ensure that there are no gaps between flight lines before the flight crew leaves the project site. Data will be inspected for turbulence, and if it is present and affects the data quality, the line is rejected.
A full visual review is conducted in the office to ensure that it is complete, uncorrupted, and that the entire project area has been covered without gaps between flight lines. The technician performs visual inspection of raw images on selected bands of each collected flight lines for completeness, this step also ensures proper sensor function of the sensor. The flight line trajectory files are reviewed to ensure completeness of acquisition for project flight lines, calibration lines, and cross flight lines.
The raw RGB images for each collected flight lines are rectified using the DEM data and the GPS/IMU solution in Fugro proprietary software. The technician visually reviews all rectified images to ensure completeness of acquisition for all flight lines. The technician also uses these images to identify any gaps, clouds, shadows and any un-predicted issues in project area.
The orthophoto production process incorporates the ability to develop a completed digital orthophoto mosaic of all or part of a data sortie at a greatly reduced resolution. “Quick look” generation permits the quick assessment of iterative adjustments to finalize the parameters that are applied to the data for radiometric corrections to the orthophoto while data limiting computer resources by only processing the imagery at full resolution once. Quick looks also enable the technician to assess the accuracy of the processed imagery as well as identifying areas of distortion that would necessitate regeneration of the DEM or aerotriangulation data.
The imagery is visually checked for accuracy on the workstation screen, and its absolute accuracy is verified by overlaying and comparing the locations of the control that are visible on the image against a CAD file containing the point locations in vector form.
The edge matching of adjacent strips of imagery is accomplished using a single color band from adjoining strips of imagery displaying each strip in alternating colors of red and cyan. In areas where the overlapping images are coincident, the imagery appears in a gray scale rendition while any offset is colored red or cyan. Any offsets are measured to confirm that the offset falls within the accuracy specification for the project.
Using the parameters developed from the quick look, the finishing department radiometrically corrects the orthophotos prior to completing the mosaicking and clipping of the final tiles, then the files are returned to digital orthophoto production for mosaicking. The finishing department performs a 100% final visual check for orthophoto image quality prior to outputting the approach data to the designated media. </measDesc>
</report>
<report type="DQConcConsis">
<measDesc>True Orthophotography:
Areas designated for true ortho capture photo capture are planned with a minimum 80 percent "endlap" between frames and 80 percent "sidelap" between flight lines. PCI Geomatics GXL and Focus tools are used in conjunction with internal proprietary techniques, and solutions to offer a comprehensive True Ortho product. The process utilizes a DSM extracted at the same resolution of the imagery to generate orthorectified imagery. With this approach, True Orthos are generated without voids, and the buildings are displayed without lean. The workflow is executed to produce the final products: • DSM Extraction • DSM Orthorectification • Mosaic Prep/Generation • Post Mosaic Editing GXL’s DEM Extraction workflow automatically scans an input directory for all valid stereo pairs, computes the epipolarized images and extracts the Digital Surface Model (DSM) for each stereo pair. Elevation values in a DSM are determined by matching points in a left and right epipolar input image using image correlation. After all DSMs in the batch are extracted, the GXL automatically merges them together to create a seamless multiview DSM. A “Pattern Suppression” algorithm helps to reduce or eliminate blunders in the output digital surface model,
The DSM Orthorectification operation orthorectifies the aerial imagery using the derived DSM. Occlusion zones that are created during the ortho process are detected for each ortho image and filled by retrieving optimal visible pixels from the adjacent overlapping ortho images. A Mosaic Preparation processing module automatically normalizes the images, calculating color balancing and generating the seamlines (cutlines). Building footprints are used as a “cutline mask” forcing the mosaicker to avoid buildings, eliminating an extreme majority of known buildings. A Mosaic tool is used to adjust cutlines and perform color balancing. PCI Geomatica and internal proprietary tools and techniques, are used to conduct a comprehensive QA/QC while simultaneously editing the imagery for DSM, seamline, or mosaicking errors.
</measDesc>
</report>
</dqInfo>
<spatRepInfo>
<Georect>
<numDims>3</numDims>
<axisDimension type="001">
<dimSize>300000</dimSize>
<dimResol>
<value Sync="TRUE" uom="m">0.080000</value>
</dimResol>
</axisDimension>
<axisDimension type="002">
<dimSize>240000</dimSize>
<dimResol>
<value Sync="TRUE" uom="m">0.080000</value>
</dimResol>
</axisDimension>
<axisDimension type="003">
<dimSize>1</dimSize>
</axisDimension>
<cellGeo>
<CellGeoCd Sync="TRUE" value="002"/>
</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"/>
</ptInPixel>
</Georect>
</spatRepInfo>
<mdLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="26985"/>
<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"/>
</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"/>
</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"/>
</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"/>
</valUnit>
</Band>
<Band>
<dimDescrp Sync="TRUE">Band_4</dimDescrp>
<maxVal Sync="TRUE">255.000000</maxVal>
<minVal Sync="TRUE">0.000000</minVal>
<bitsPerVal Sync="TRUE">8</bitsPerVal>
<valUnit>
<UOM type="length"/>
</valUnit>
</Band>
</covDim>
</ImgDesc>
</contInfo>
</metadata>
