<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<metadata xml:lang="en">
<Esri>
<CreaDate>20201217</CreaDate>
<CreaTime>13334800</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<lineage>
<Process Date="20201217" Time="133348" ToolSource="c:\program files (x86)\arcgis\desktop10.7\ArcToolbox\Toolboxes\Data Management Tools.tbx\CreateMosaicDataset">CreateMosaicDataset \\gisfs1q\Orthos\Orthos_2005\Orthos2005TC.gdb Mosaic2005 "PROJCS['NAD_1983_StatePlane_Michigan_South_FIPS_2113_Feet_Intl',GEOGCS['GCS_North_American_1983',DATUM['D_North_American_1983',SPHEROID['GRS_1980',6378137.0,298.257222101]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]],PROJECTION['Lambert_Conformal_Conic'],PARAMETER['False_Easting',13123359.58005249],PARAMETER['False_Northing',0.0],PARAMETER['Central_Meridian',-84.36666666666666],PARAMETER['Standard_Parallel_1',42.1],PARAMETER['Standard_Parallel_2',43.66666666666666],PARAMETER['Latitude_Of_Origin',41.5],UNIT['Foot',0.3048]];-107138600 -97193800 3048;-100000 10000;-100000 10000;3.28083989501312E-03;0.001;0.001;IsHighPrecision" # # NONE #</Process>
<Process Date="20201217" Time="133936" ToolSource="c:\program files (x86)\arcgis\desktop10.7\ArcToolbox\Toolboxes\Data Management Tools.tbx\DefineOverviews">DefineOverviews \\gisfs1q\Orthos\Orthos_2005\Orthos2005TC.gdb\Mosaic2005 \\gisfs1q\Orthos\Orthos_2005\Orthos2005TC.Overviews\Mosaic2005.Overviews # "13301997.8572835 334000.47047244 13472997.6354987 511999.738188976" # # 5120 5120 3 NO_FORCE_OVERVIEW_TILES BILINEAR JPEG 80</Process>
<Process Date="20201217" Time="151812" ToolSource="c:\program files (x86)\arcgis\desktop10.7\ArcToolbox\Toolboxes\Data Management Tools.tbx\BuildOverviews">BuildOverviews \\gisfs1q\Orthos\Orthos_2005\Orthos2005TC.gdb\Mosaic2005 # DEFINE_MISSING_TILES GENERATE_OVERVIEWS GENERATE_MISSING_IMAGES REGENERATE_STALE_IMAGES</Process>
</lineage>
<itemProps>
<itemName Sync="TRUE">Mosaic2005</itemName>
<itemLocation>
<linkage Sync="TRUE">file://\\gisfs1p\Orthos\Orthos_2005\Orthos2005TC.gdb</linkage>
<protocol Sync="TRUE">Local Area Network</protocol>
</itemLocation>
<nativeExtBox>
<westBL Sync="TRUE">13301997.463500</westBL>
<eastBL Sync="TRUE">13472997.963500</eastBL>
<southBL Sync="TRUE">334000.189900</southBL>
<northBL Sync="TRUE">511999.689900</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Foot (0.304800)</csUnits>
<projcsn Sync="TRUE">NAD_1983_StatePlane_Michigan_South_FIPS_2113_Feet_Intl</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.7'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_StatePlane_Michigan_South_FIPS_2113_Feet_Intl&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;,13123359.58005249],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-84.36666666666666],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,42.1],PARAMETER[&amp;quot;Standard_Parallel_2&amp;quot;,43.66666666666666],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,41.5],UNIT[&amp;quot;Foot&amp;quot;,0.3048],AUTHORITY[&amp;quot;EPSG&amp;quot;,2253]]&lt;/WKT&gt;&lt;XOrigin&gt;-107138600&lt;/XOrigin&gt;&lt;YOrigin&gt;-97193800&lt;/YOrigin&gt;&lt;XYScale&gt;37448250.484633707&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.0032808398950131233&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;2253&lt;/WKID&gt;&lt;LatestWKID&gt;2253&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"/>
</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>
<_docversion_ Sync="TRUE">10</_docversion_>
<AllowedFields Sync="TRUE">Name,MinPS,MaxPS,LowPS,HighPS,Tag,GroupName,ProductName,CenterX,CenterY,ZOrder,Shape_Length,Shape_Area,Year</AllowedFields>
<MaxCellSize Sync="TRUE">36450</MaxCellSize>
<LowCellSize Sync="TRUE">0.5</LowCellSize>
<HighCellSize Sync="TRUE">729</HighCellSize>
</Properties>
<Functions Sync="TRUE">
<Function Description="Performs on-the-fly mosaic on a raster catalog." Name="Mosaic Function"/>
</Functions>
</RasterProperties>
</DataProperties>
<scaleRange>
<minScale>1200</minScale>
<maxScale>1200</maxScale>
</scaleRange>
<SyncDate>20210312</SyncDate>
<SyncTime>15014100</SyncTime>
<ModDate>20210312</ModDate>
<ModTime>15014100</ModTime>
</Esri>
<mdLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdContact>
<rpIndName>Raquel Charrois</rpIndName>
<rpOrgName>EarthData International</rpOrgName>
<rpPosName>Project Manager</rpPosName>
<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>21701</postCode>
<country>US</country>
<eMailAdd>rcharrois@earthdata.com</eMailAdd>
</cntAddress>
<cntHours>Mon to Fri 9:00 am to 5:00 pm</cntHours>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distributor>
<distorCont>
<rpIndName>Erick Phillips</rpIndName>
<rpOrgName>Oakland County One Stop Shop</rpOrgName>
<rpPosName>Supervisor</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>248.858.4070</voiceNum>
<faxNum>248.858.1080</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>2100 Pontiac Lake Rd. Bldg. 41W</delPoint>
<city>Waterford</city>
<adminArea>MI</adminArea>
<postCode>48328-0412</postCode>
<country>US</country>
<eMailAdd>phillipse@oakgov.com</eMailAdd>
</cntAddress>
<cntHours>9:00 a.m. to 4:00 p.m.</cntHours>
</rpCntInfo>
<role>
<RoleCd value="005"/>
</role>
</distorCont>
<distorOrdPrc>
<resFees>Varies by data type and agent.</resFees>
<ordInstr>Contact Erick Phillips of the One Stop Shop by phone.</ordInstr>
<ordTurn>24 hrs.</ordTurn>
</distorOrdPrc>
<distorFormat>
<formatName>Shapefiles, .tiff and MrSID</formatName>
</distorFormat>
<distorTran>
<offLineMed>
<medName>
<MedNameCd value="001"/>
</medName>
</offLineMed>
</distorTran>
<distorTran>
<onLineSrc>
<orDesc>Offline data</orDesc>
</onLineSrc>
</distorTran>
</distributor>
</distInfo>
<dataIdInfo>
<idCitation>
<resEd>1</resEd>
<citRespParty>
<rpOrgName>Oakland County</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>remote-sensing image</fgdcGeoform>
</presForm>
<resTitle Sync="TRUE">EnterpriseOrthoTC2005ImageService</resTitle>
</idCitation>
<idAbs>Oakland County participated in the Southeast Michigan Regional Orthoimagery project encompassing approximately 5000 square miles, which includes an additional ½ mile buffer beyond the boundary of the seven county region. This extends approximately 500 feet into Canada. The orthoimagery is true color with a base pixel resolution of 6 inches for the County-only imagery, and 2' for the region-wide imagery. Orthoimagery tiles were delivered in Tiff format with Tiff world files representing ground dimensions of 2000' x 3000'. Tile naming convention includes the county code, the third and fourth digit of the lower left X and the first three digits of the lowerY coordinate and the year flown. For example 161 2005, tile name would be 1612932405). Countywide and community mosaics are saved in the MrSID format. Community MrSID files are compressed at 20 to 1 using the 6 inch pixel imagery and countywide MrSIDs are compressed at 50 to 1 using the 2 foot pixel imagery. All control was based on the following -Michigan State Plane (South) -Horizontal datum -North American Datum (NAD 83) international feet second-order class I. -Vertical datum - North American Vertical Datum 1988 (NAVD88) international feet, third-order class I. All imagery was taken in the spring of 2005. Acquisition was attempted when the ground was not obscured by haze, smoke, dust, clouds or cloud shadows, and snow or ice. Flights were scheduled when solar angle was at least 30 degrees or more above the horizon Orthoimagery complies with the American Society for Photogrammetry and Remote Sensing Accuracy Standards for Class 1 mapping requirements.</idAbs>
<idPurp>Oakland County participated in the Southeast Michigan Regional Orthoimagery project encompassing approximately 5000 square miles, which includes an additional ½ mile buffer beyond the boundary of the seven county region. This extends approximately 500 feet into Canada. The orthoimagery is true color with a base pixel resolution of 6 inches for the County-only imagery, and 2' for the region-wide imagery. Orthoimagery tiles were delivered in Tiff format with Tiff world files representing ground dimensions of 2000' x 3000'. Tile naming convention includes the county code, the third and fourth digit of the lower left X and the first three digits of the lowerY coordinate and the year flown. For example 161 2005, tile name would be 1612932405). Countywide and community mosaics are saved in the MrSID format. Community MrSID files are compressed at 20 to 1 using the 6 inch pixel imagery and countywide MrSIDs are compressed at 50 to 1 using the 2 foot pixel imagery. All control was based on the following -Michigan State Plane (South) -Horizontal datum -North American Datum (NAD 83) international feet second-order class I. -Vertical datum - North American Vertical Datum 1988 (NAVD88) international feet, third-order class I. All imagery was taken in the spring of 2005. Acquisition was attempted when the ground was not obscured by haze, smoke, dust, clouds or cloud shadows, and snow or ice. Flights were scheduled when solar angle was at least 30 degrees or more above the horizon Orthoimagery complies with the American Society for Photogrammetry and Remote Sensing Accuracy Standards for Class 1 mapping requirements.</idPurp>
<idStatus>
<ProgCd value="001"/>
</idStatus>
<idPoC>
<rpIndName>Anita Campbell</rpIndName>
<rpOrgName>Oakland County Application Services</rpOrgName>
<rpPosName>GIS Data Services Supervisor</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>248.858.2388</voiceNum>
<faxNum>248.452.9128</faxNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>1200 N Telegraph Rd, Bldg 49W</delPoint>
<city>Pontiac</city>
<adminArea>MI</adminArea>
<postCode>48341</postCode>
<country>US</country>
<eMailAdd>campbella@oakgov.com</eMailAdd>
</cntAddress>
<cntHours>8:30 a.m. to 5:00 p.m.</cntHours>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="011"/>
</maintFreq>
</resMaint>
<placeKeys>
<keyword>Southeast Michigan</keyword>
</placeKeys>
<themeKeys>
<keyword>DEM</keyword>
<keyword>Digital Elevation Model</keyword>
<keyword>Aerial photography</keyword>
<keyword>Imagery</keyword>
<keyword>GPro</keyword>
<keyword>Air photos</keyword>
<keyword>Aerotriangulation</keyword>
<keyword>ADS40</keyword>
<keyword>DSM</keyword>
<keyword>Orthophotography</keyword>
<keyword>Digital Surface Model</keyword>
<keyword>Digital Orthos</keyword>
</themeKeys>
<searchKeys>
<keyword>DEM</keyword>
<keyword>Digital Elevation Model</keyword>
<keyword>Aerial photography</keyword>
<keyword>Imagery</keyword>
<keyword>GPro</keyword>
<keyword>Air photos</keyword>
<keyword>Aerotriangulation</keyword>
<keyword>ADS40</keyword>
<keyword>DSM</keyword>
<keyword>Orthophotography</keyword>
<keyword>Digital Surface Model</keyword>
<keyword>Southeast Michigan</keyword>
<keyword>Digital Orthos</keyword>
</searchKeys>
<resConst>
<LegConsts>
<othConsts>http://www.oakgov.com/it/gis/Documents/EnhancedAccessPolicy.pdf</othConsts>
</LegConsts>
</resConst>
<resConst>
<Consts>
<useLimit>http://www.oakgov.com/it/gis/Documents/GISDataPolicies.pdf</useLimit>
</Consts>
</resConst>
<dataLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<tpCat>
<TopicCatCd value="006"/>
</tpCat>
<tpCat>
<TopicCatCd value="010"/>
</tpCat>
<dataExt>
<geoEle>
<GeoBndBox>
<westBL>-84.173891</westBL>
<eastBL>-82.392011</eastBL>
<southBL>41.697475</southBL>
<northBL>43.195625</northBL>
</GeoBndBox>
</geoEle>
</dataExt>
<dataExt>
<exDesc>ground condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin date="April 12, 2005"/>
<tmEnd date="fMay 5, 2005"/>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
<geoEle/>
</dataExt>
<suppInfo>Most of the imagery was acquired on April 12, 2005. Some parts of the County were flown at a later date, the latest date being May 5, 2005.</suppInfo>
<envirDesc Sync="TRUE"> Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595</envirDesc>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="002"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-83.705118</westBL>
<eastBL Sync="TRUE">-83.061712</eastBL>
<northBL Sync="TRUE">42.903002</northBL>
<southBL Sync="TRUE">42.409128</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<idCredit/>
</dataIdInfo>
<mdMaint>
<maintFreq>
<MaintFreqCd value="012"/>
</maintFreq>
<maintNote>Last metadata review date: 20060516</maintNote>
</mdMaint>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<report type="DQConcConsis">
<measDesc>Compliance with the accuracy standard was ensured by the collection of photo identifiable GPS ground control after the acquisition of aerial imagery. The following checks were performed. 1. The ground control and airborne GPS data stream were validated through a fully analytical bundle aerotriangulation adjustment. The RMSE is less than 1, 10,000th of the flying height. 2. The DSM (for True Ortho areas) or DEM (for ground ortho areas) data was checked against the project control. The technician visited and confirmed the accuracy of the points during initial processing 3. Digital orthophotography was validated through an inspection of edge matching and visual inspection for image quality.</measDesc>
</report>
<report type="DQCompOm">
<measDesc>The following methods are used to assure imagery accuracy. 1. Use of IMU (inertial measurment unit) and ground control network utilizing GPS techniques. 2. Use of airborne GPS (global positioning system) in conjunction with the acquisition of imagery. The following software is used for validation of the imagery and surface modeling 1. Aerotriangulation - GPro and ISTAR 2. DSM and DEM data - GPro and ISTAR 3. Digital Orthophotography - ISTAR 4. Bentley - MicroStation 5. GPro 6. ISTAR 7. ESRI - ArcInfo 8. ERDAS Imagine 9. Terrascan 10. EarthData proprietary software 11. Adobe - Photoshop 12. Socetset 13. Horizons proprietary software</measDesc>
</report>
<report type="DQQuanAttAcc">
<measDesc>This data has been produced to be fully compliant with the American Society for Photogrammetry and Remote Sensing Accuracy Standards for Class 1 mapping requirements.</measDesc>
</report>
<report dimension="horizontal" type="DQAbsExtPosAcc">
<measDesc>This data has been produced to be fully compliant with the American Society for Photogrammetry and Remote Sensing Accuracy Standards for Class 1 mapping requirements. +/- 1 foot at 68.3 percent accuracy.</measDesc>
</report>
<report dimension="vertical" type="DQAbsExtPosAcc">
<measDesc>The surface model meets and accuracy of 2 meters or 7 feet RMSE.</measDesc>
</report>
<dataLineage>
<prcStep>
<stepDesc>The digital orthophotography is comprised of a natural color 6-inch pixel resolution ground orthos for the counties of Livingston, Macomb, Monroe, Oakland, St. Clair, Washtenaw and Wayne. True Ortho imagery was generated in downtown Detroit (Wayne County). Oakland County received their imagery in NAD83 (86). Livingston, Macomb, Monroe, St. Clair, Washtenaw and Wayne received their imagery in NAD83 (HARN). Two separate work flows were used to complete the orthophoto production. ISTAR was used in the True Ortho area (Detroit City) and Leica GPro was used for the Ground Ortho areas (the remainder of the project). This process describes the True Ortho production. The initial radiometric adjustments were performed on the imagery for each flight line attempting to reach the best possible histogram. The rectification process was then run using the processed DSM surface and the radiometrically balanced imagery on each flight line. The quicklook (reduced resolution rectification) of each flight line exported out of ISTAR. A second set of radiometric adjustments were made using EarthData proprietary tools. The radiometrically balanced imagery was then re-imported into the ISTAR system and the histogram from the quicklook was applied to the full resolution imagery. Mosaic lines were placed, joining the ADS40 imagery strips. In initial QA/QC was performed by the technician to ensure that the mosaic lines were appropriately placed and that there was appropriate imagery coverage. The final imagery data set is removed from the ISTAR environment in a process called "packaging" where the individual tiles are created. All data processing in the ISTAR system is performed in UTM meters; it is during packaging that final datum and projection are defined. The created tiles are reviewed again for anomalies and interactive radiometric adjustment applied where needed. QA/QC was performed looking for anomalies, smears and other indications of problems within the digital Orthophoto creation process, interactive radiometric adjustment applied where needed. Two additional radiometric adjustments are applied to the completed orthos in Adobe Photoshop. The first is a sharpening mask filter; this filter is used to help increase sharpness of a digital image. The basis for this filter is to locate pixels that differ in value from surrounding pixels by the threshold specified. It then increases the pixels' contrast by the value identified. For neighboring pixels specified by the threshold, the lighter pixels get even lighter and the darker pixels get even darker based on the specified amount. The changes made maintained the integrity of the original histogram curve. The settings used were, Filter Sharpen Unsharp Mask Amount 250% Radius 1.0 Pixels Threshold 0 Levels Image Adjustments Color Balance. -12 Green Midtones Image Adjustments Brightness/Contrast. +15 The final digital ortho product was TIFF with TFW. This process describes the Ground Ortho production. Ortho-rectification is performed in GPro for the entire image strip at once, which is more efficient that managing many frame images. GPro resamples the original Level-0 image with the refined orientation produced by aerotriangulation and the requisite DEM. After the creation of the Orthophotos using GPro, the images are run through a proprietary program that adjusts the gradient across each image to improve the tone balance of the images. This program also breaks the ADS40 orthophoto strip into more manageable overlapping tiles. These orthophotos are then imported into ORTHOVISTA where radiometric and color corrections are made on multiple flight lines at once. Upon completion the images are imported into horizons' proprietary image software. Images are mosaicked together using a "path of least resistance" algorithm to generate seam lines. When the initial database is generated, the technician overlays the DEM to check for correct orientations and obvious image errors. The technician then systematically goes through the database looking at every seam. If a seam is noticeable and can be lessened or be made "invisible" by moving the seam; the Technician will evaluate the overlapping image tiles to choose the "best fit" and mosaic the "new" seam line into the image database. Once all of the seam lines have been checked and corrected ortho tiles are then clipped from the image database and put through a thorough Q/C process. Any discrepancies found are marked and corrected inside of the image database. Once this process is complete the final ortho tiles are clipped from the database. Two additional radiometric adjustments are applied to the completed orthos in Adobe Photoshop. The first is a sharpening mask filter; this filter is used to help increase sharpness of a digital image. The basis for this filter is to locate pixels that differ in value from surrounding pixels by the threshold specified. It then increases the pixels' contrast by the value identified. For neighboring pixels specified by the threshold, the lighter pixels get even lighter and the darker pixels get even darker based on the specified amount. The changes made maintained the integrity of the original histogram curve. The settings used were, Filter Sharpen Unsharp Mask Amount 250% Radius 1.0 Pixels Threshold 0 Levels Image Adjustments Color Balance. -12 Green Midtones Image Adjustments Brightness/Contrast. +15 The final digital ortho product was TIFF with TFW. Additional Ortho products are identified below. 1. 6 inch natural color county, community and township MrSID mosaics. These products are created using MrSID software. Community and township MrSID files are created with a compression ratio of 20 to 1. Countywide MrSID files 1. The original individual 6 inch natural color orthos involved in the area of interest are isolated and identified as input for the MrSID software. The desired output ratio identified and the result is one mosaiced image with the desired compression ratio. 2. Natural color resampled orthos at 1 foot and 2 foot. These files are created using EarthData proprietary software. The original 6 inch natural color orthos are input into the software with the desired pixel out put specified. 3. Black and white 6 inch orthos. These files are created using EarthData proprietary software. The original 6 inch natural color orthos are input into the software with the desired outcome of black and white specified. The program translates the red, green and blue bands into gradients of black and white resulting in a black and white rendition . All data are delivered on firewire drive or DVD.</stepDesc>
<stepDateTm>2006-05-16</stepDateTm>
<stepProc>
<rpIndName>Raquel Charrois</rpIndName>
<rpOrgName>EarthData International</rpOrgName>
<rpPosName>Project Manager</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>301-948-8550</voiceNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>7320 Executive Way</delPoint>
<city>Frederick</city>
<adminArea>MD</adminArea>
<postCode>21704</postCode>
<country>US</country>
<eMailAdd>rcharrois@earthdata.com</eMailAdd>
</cntAddress>
<cntHours>Mon - Fri 9:00 am to 5:00 pm</cntHours>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>Digital Orthophotos</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc type="produced">
<srcCitatn>
<resAltTitle>Digital Orthos</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>Two separate work flows were used to complete the aerotriangulation on the project. ISTAR was used in the True Ortho area (Detroit City) and Leica GPro was used for the Ground Ortho areas (the remainder of the project). For both work flows the airborne GPS data were processed and integrated with the inertial measurement unit (IMU). For the True Ortho areas the results were imported into the ISTAR system for use in the aerotriangulation. The ADS40 imagery was downloaded onto the EarthData server and brought over to the UNIX based ISTAR system. The ground control was used in conjunction with the processed airborne global positioning system (ABGPS) results for the aerotriangulation. The ground control points were read in all available imagery and tie points between flight lines were selected. A fully analytical bundle adjustment was run. The properly formatted ISTAR results were used for subsequent processing. For the Ground Ortho area the results were imported into the GPro system for use in the aerotriangulation. Aerotriangulation of ADS40 imagery were performed using, the Socet Set Automatic Point Measurement (APM) tool to select the pass point between the selected bands and ORIMA to perform the analytical aerotriangulation bundle adjustment of the measurements recorded. Aerotriangulation was performed using three bands; the backward viewing pan band, the green band at nadir view and the green forward viewing band. The ground control points were read in all available imagery and tie points between flight lines were selected. A fully analytical bundle adjustment was run. The properly formated results were used for subsequent processing.</stepDesc>
<stepDateTm>2006-03-15</stepDateTm>
<stepProc>
<rpIndName>Raquel Charrois</rpIndName>
<rpOrgName>EarthData International</rpOrgName>
<rpPosName>Project Manager</rpPosName>
<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>US</country>
<eMailAdd>rcharrois@earthdata.com</eMailAdd>
</cntAddress>
<cntHours>Mon - Fri 9:00am to 5:00pm</cntHours>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>Aerotriangulation</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc type="produced">
<srcCitatn>
<resAltTitle>AT</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>Two separate work flows were used to complete the surface model on the project. ISTAR was used in the True Ortho area (Detroit City) and Leica GPro was used for the Ground Ortho areas (the remainder of the project). This process describes the ISTAR surface modeling for the True Ortho area. ISTAR digital surface modeling is based on an auto correlated pixel-matching system within the ISTAR software. The auto correlated digital surface model (DSM) surface represents the initial surface model. The post spacing was generated at 2 meters. The following is a step-by-step breakdown of the process. 1. Using the DSM ISTAR data set created, the technician performed a visual inspection of the data to verify that the flight lines met correctly. The technician also verified that there were no voids, and that the data covered the project limits. The technician then selected a series of areas from the dataset and inspected them where adjacent flight lines met. 2. This DSM surface is used in the rectification of True Ortho imagery. This process describes the surface modeling for the Ground Ortho areas. Socet Set digital surface modeling is based on an auto correlated pixel-matching system. Using the ADS40 Level-1 imagery and the Socet Set Automatic Terrain Extraction (ATE) tool, a DEM surface with a 2 meter post spacing was autocorrelated. ATE and ITE (Interactive Terrain Edit) are both tools in Socet Set that were used to generate and edit the DTM data. With ATE, a terrain adaptive image correlation strategy is used to create a DTM regular grid with specified post spacing. DTM grid files are created for each flight line. In ITE, buildings, trees, and all other areas that ATE could not correctly correlate were manually removed. The edited DTM data was directly used in GPro to rectify the Level-2 ortho strips. The following is a step-by-step breakdown of the process. 1. Using the DEM data set created, the technician performed a visual inspection of the data to verify that the flight lines met correctly. The technician also verified that there were no voids, and that the data covered the project limits. The technician then selected a series of areas from the dataset and inspected them where adjacent flight lines met. A process, which utilizes ITE was run to detect the differences in elevation values and profiles. The technician reviewed the results and located the areas that contained systematic errors or distortions that were introduced by the auto correlation. 2. Systematic distortions highlighted in step 1 were removed and the data were re-inspected. Corrections and adjustments can involve the application of angular deflection or compensation for curvature of the ground surface that can be introduced by crossing from one type of land cover to another. 3.The data was checked against the control network to ensure that vertical requirements were maintained. 4. Data was merged into countywide data sets, reprojected from HARN to 86 adjustment and converted to ESRI float grid format.</stepDesc>
<stepDateTm>2006-03-30</stepDateTm>
<stepProc>
<rpIndName>Raquel Charrois</rpIndName>
<rpOrgName>EarthData International</rpOrgName>
<rpPosName>Project Manager</rpPosName>
<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>US</country>
<eMailAdd>rcharrois@earthdata.com</eMailAdd>
</cntAddress>
<cntHours>Mon - Fri 9:00 am to 5:00 pm</cntHours>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>Digital Surface Model</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>Digital Elevation Model</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc type="produced">
<srcCitatn>
<resAltTitle>DSM and DEM</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<dataSource>
<srcDesc>Wade Trim was contracted by EarthData to acquire 60 photo identifiable ground control points after the acquisition of aerial imagery. The ground control points were established using GPS for vertical and horizontal coordinate values. NAD 83 (86) NAVD 88 International Feet</srcDesc>
<srcScale>
<rfDenom>1200</rfDenom>
</srcScale>
<srcCitatn>
<resTitle>Ground Control</resTitle>
<resAltTitle>Ground Control</resAltTitle>
<date>
<pubDate>2005-05-27</pubDate>
</date>
<resEd>1</resEd>
<citRespParty>
<rpOrgName>Wade Trim</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="008"/>
</presForm>
<presForm>
<fgdcGeoform>model</fgdcGeoform>
</presForm>
</srcCitatn>
<srcExt>
<exDesc>Ground Condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2005-05-05</tmBegin>
<tmEnd>2005-05-27</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>The aerial imagery acquisition for Southeast Michigan was flown to support the creation of digital orthophotography with a 6-inch pixel. The imagery was acquired in thirty-two sorties, the sorties were varying in size. The imagery were flown at 5,300 feet AMT. Imagery was flown with a 30% overlap between flight lines except in the areas of downtown Detroit where the imagery was flown with a 60-80% overlap to support the generation of True Ortho imagery. All imagery was collected using the Leica ADS40 digital pushbroom sensor.</srcDesc>
<srcScale>
<rfDenom>1200</rfDenom>
</srcScale>
<srcCitatn>
<resTitle>Aerial Imagery Acquisition</resTitle>
<resAltTitle>Aerial Acquisition</resAltTitle>
<date>
<pubDate>2005-05-20</pubDate>
</date>
<resEd>1</resEd>
<citRespParty>
<rpOrgName>EarthData Aviations</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>remote-sensing image</fgdcGeoform>
</presForm>
</srcCitatn>
<srcExt>
<exDesc>ground condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2005-04-12</tmBegin>
<tmEnd>2005-05-20</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
</dataLineage>
</dqInfo>
<spatRepInfo>
<Georect>
<numDims Sync="TRUE">2</numDims>
<cellGeo>
<CellGeoCd Sync="TRUE" value="002"/>
</cellGeo>
<tranParaAv Sync="TRUE">1</tranParaAv>
<chkPtAv Sync="TRUE">0</chkPtAv>
<cornerPts>
<pos Sync="TRUE">13301997.463500 334000.189900</pos>
</cornerPts>
<cornerPts>
<pos Sync="TRUE">13301997.463500 511999.689900</pos>
</cornerPts>
<cornerPts>
<pos Sync="TRUE">13472997.963500 511999.689900</pos>
</cornerPts>
<cornerPts>
<pos Sync="TRUE">13472997.963500 334000.189900</pos>
</cornerPts>
<centerPt>
<pos Sync="TRUE">13387497.713500 422999.939900</pos>
</centerPt>
<axisDimension type="002">
<dimSize Sync="TRUE">342001</dimSize>
<dimResol>
<value Sync="TRUE" uom="ft">0.500000</value>
</dimResol>
</axisDimension>
<axisDimension type="001">
<dimSize Sync="TRUE">355999</dimSize>
<dimResol>
<value Sync="TRUE" uom="ft">0.500000</value>
</dimResol>
</axisDimension>
<ptInPixel>
<PixOrientCd Sync="TRUE" value="001"/>
</ptInPixel>
</Georect>
</spatRepInfo>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="2253"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">5.3(9.0.0)</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">20.000000</minVal>
<bitsPerVal Sync="TRUE">8</bitsPerVal>
<valUnit>
<UOM type="length"/>
</valUnit>
</Band>
</covDim>
</ImgDesc>
</contInfo>
<mdDateSt Sync="TRUE">20210312</mdDateSt>
</metadata>
