Report for Oblique and Orthogonal Imagery Obtained between the dates of Friday, January 24, Sunday, March 09, 2014

Transcription

1 Report for Oblique and Orthogonal Imagery Obtained between the dates of Friday, January 24, Sunday, March 09, 2014 Prepared for: Lee, Florida Prepared by: Pictometry International Corp. 100 Town Centre Drive, Suite A Rochester, NY Phone# Fax# Pictometry Business License No. LB7771 Michael J. Zoltek Professional Surveyor & Mapper /25/2014 This report is not valid without the signature and the original raised seal of a Florida licensed Surveyor and Mapper. Page 1 of 193

2 Table of Contents Type of Report... 3 Source Data... 3 Name of Company... 3 Responsible Surveyor... 3 Project Area... 4 Map Reference... 4 Equipment and Software... 4 Collection procedures... 4 Ground Control Surveying... 7 Summary of Specifications for Orthophotography... 7 Fully Analytical Aerial Triangulation... 8 Production of Orthomosaics... 8 Acronyms and Definitions Standard Product Absolute Horizontal Accuracies Background Summary Standard Product Relative Measurement Accuracies Relative Measurement Accuracies References Project Summary Summary of Project Absolute Horizontal Accuracies Summary of Project Relative Measurement Accuracies Appendix A: Sector Map Flight Plan Map(s) Appendix B: Sensor Data Camera serial Numbers Tail Number Serial Number Camera Orientation Mount Orientations Camera Calibration Reports Appendix C: Applanix data Base Station GPS Observables Conversion Logs Smartbase QC Logs Appendix D: Tie-point Statistics Appendix E: NGS Data Sheets Appendix F: Sectors Containing Imagery Frames Appendix G: Aerotriangulation Statistics Initial Control Point Residuals from Unconstrained Adjustment Block A Block B Block C Block Isand Block Island Final Constrained Adjustment Results Block A Block B Block C Block Isand Block Island Block Island Appendix H: Control Point Summary Appendix I: AccuPlus Tile List Page 2 of 193

3 Type of Report This Report pertains to the Photogrammetric Mapping, Digital Aerial Color Orthophotography and Oblique Photography processing performed to produce the georeferenced Orthogonal and Oblique imagery as delivered to the client. Source Data 3-inch (7.5 cm) and 4-inch (10 cm) Ground Sample Distance (GSD) source imagery is intended to be represented at a map scale of 1:800, 6-inch (15 cm) GSD source imagery is intended to be represented at a map scale of 1:1200 and any 9-inch (22.5 cm) or 12-inch (30 cm) GSD imagery is intended to be represented at a map scale of 1:2400. Note: The image capture date is recorded as the last 6 digits of each individual image file name. The file creation date is the date when the image was captured and the modified date is when the imaged was processed. Name of Company Pictometry International Corp. 100 Town Centre Drive, Suite A Rochester, NY Phone# Fax# Responsible Surveyor Michael J. Zoltek, CP, LS, GISP ASPRS CP #1523 Alabama PLS #25291 Arizona RLS #53351 California PLS #8878 Connecticut LS #70378 Florida PSM #5751 Georgia RLS #2976 Idaho PS #14353 Louisiana PLS #4994 Mississippi PS #3088 Nevada PLS #21183 New Mexico PS #20558 New York LS #50883 North Dakota LS #6646 Oregon RPP #88009RPP South Carolina PS #27462 South Dakota LS #10187 Tennessee LS #2836 Texas RPLS #6221 US Virgin Islands LS #1181LS Washington PLS #50992 West Virginia PS #2219 Wisconsin LS # Page 3 of 193

4 Project Area The project area for this report encompasses approximately 1063 square miles within Lee, Florida. Map Reference There are no hardcopy map sheets for this project. Equipment and Software Camera System Pictometry s Pentaview camera system is based on an architecture designed and patented by Pictometry. The Pentaview is a multi-camera system comprised of five digital camera modules and an acquisition computer (with sensor control hardware and software). Key components of the Pentaview system are manufactured and assembled by qualified suppliers under contract to Pictometry. Individual subsystems of the Pentaview system are integrated and tested at Pictometry s facilities in Rochester, NY. The finished camera system is calibrated and tested in the laboratory at Pictometry s facilities in Rochester, NY. Pictometry s 16-megapixel Pentaview imaging system carries the United States Geological Survey (USGS) Camera Type Certification and comprises five custom designed cameras and an Applanix Position and Orientation System (POS) which includes both a Global Positioning System (GPS) antenna and an Inertial Measurement Unit (IMU). The five cameras are aimed with one looking nadir and four looking in each of the four cardinal oblique directions. Pictometry s 29-megapixel Pentaview imaging system is constructed on the USGS approved platform and incorporates upgraded 29-megapixel sensors. Calibration Prior to image collection, as part of the manufacture, the individual cameras are put through a rigorous calibration process developed by Pictometry and licensed to the USGS. The calibration is performed through the capture of a series of images from prescribed locations and at varied orientations of a stationary target cage. Targets are identified in the images collected via a semi-automatic process and a free-network bundle adjustment is performed to solve for camera interior orientation, including precise focal length, principal point location, and radial distortion coefficients. These parameters are then incorporated into the camera model used during subsequent image processing operations. Each camera is also put through a color calibration process designed by Pictometry in order to generate a consistent response, ensuring consistent representation of ground features. Specific information pertaining to the sensors used for this project can be found in Appendix B. Collection procedures System Alignment In advance of capturing the data, an additional aerial boresight calibration is performed on each of the systems involved in the project. An adjustment then is computed to solve for the alignment between the optical axis of the camera and the internal coordinate axes of the Inertial Measurement Unit (IMU). This adjustment is then applied to the imagery captured throughout the project. Each system completes a boresight flight at regular intervals to ensure that the sensors have stayed in alignment. Page 4 of 193

5 Once the cameras are calibrated and the system is aligned, data capture can begin. Throughout each of the capture missions, GPS/IMU data is logged on the aircraft, the GPS data is recorded at a minimum rate of 2Hz and the IMU data is logged at a minimum rate of 200Hz. Concurrently, multiple GPS reference stations are logging data on the ground. These reference stations may be either part of the NGS CORS network, or a base station set up and run by Pictometry or a licensed surveyor sub-consultant. The imagery is nominally captured with a PDOP value of less than 8.0 and within 60 kilometers of an operating GPS reference station. Due to the small format of Pictometry s camera, and automatic aerial triangulation techniques available, Pictometry limits its sensor to 6 degrees of pitch and yaw; this limit can be utilized due to the narrow field of view of Pictometry s cameras which, by design, limits the off-nadir distance of features at the edge of the frame. Imagery is captured at 36-bit (12-bits per channel) and resampled to 24-bit RGB color for processing, with a planned forward lap of 60% and a side lap of 30%. During the capture process, Pictometry s Flight Management System performs real time checks of a variety of parameters, including but not limited to: rapid histogram analysis to detect exposure errors, camera orientation (i.e. roll, pitch, yaw) to ensure perspective, and camera position to ensure coverage. Upon completion of collection, the data is transferred to Pictometry's processing facility in Rochester, NY. GPS/INS Post-Processing Upon receipt in Rochester, the data is immediately backed up and post-processing begins. Applanix POSPac software is utilized to post process the GPS/IMU data utilizing the SmartBase (IN-fusion). The SmartBase technology uses a centralized filter approach to combine the GPS receiver s raw observables (pseudorange and phase observables) with the IMU data (tightly coupled solution). The Applanix SmartBase engine processes the raw observables (phase and pseudorange to each tracked satellite) from a minimum of four to a maximum of 50 continuously-working GPS reference stations surrounding the trajectory. The computed ionospheric, tropospheric, satellite clock, and orbital errors at all the reference stations are used to correct for the errors at the location of the remote receiver. The SmartBase Quality Check tool is utilized to perform a network adjustment on all the base-lines and reference stations in the network. Quality checks are also performed on the individual reference station observation files before the Applanix SmartBase is computed. The result of this process is that the integrity of the reference station s data and coordinates are known before the data is Page 5 of 193 Post-processed SBET

6 processed. The single base technology is different as only one dedicated base station is used as a reference station and atmospheric delay and other correction data are only retrieved at the dedicated master station. The final smoothed best estimated trajectory (SBET) is computed from the GPS track (including Kalman Filtering). Once the final trajectory has been generated, it is applied to the imagery on the basis of the individual time stamps associated with each frame. The location (X, Y, Z) and orientation (Roll, Pitch, Yaw) values derived from the SBET and assigned to each frame serve and would serve as the initial exterior orientation (EO) values should the imagery proceed to aerial triangulation. Specific information pertaining to the Applanix methodology used for this project can be found in Appendix C. Applying Trajectory Information The next step in the production of Pictometry s Oblique Imagery data is the application of the post-processed trajectory data with the oblique imagery. Each image is assigned a new camera center and orientation (exterior orientation or EO) based on the post-processed trajectory. This EO serves as the origin point for all measurements and calculations. Concurrent with the GPS/INS processing, the imagery in RAW format is developed to uncompressed TIFF format. During the capture process, Pictometry s Flight Management System performs real time checks of a variety of parameters, including but not limited to: rapid histogram analysis to detect exposure errors, camera orientation (i.e. roll, pitch, yaw) to ensure perspective, and camera position to ensure coverage. After the development process, the imagery is put through a rigorous QA/QC process whereby images of low quality, due to either improper exposure or sensor artifact, are identified and marked for recapture. Pictometry uses both automated software it has created (proprietary) and human examination when considering whether to reject an image or pass it for production. Pictometry s Image Processing Department checks for any of dozens of possible defects while assessing the quality of the imagery. Applying DEM Data In order to ensure accurate measurements on single frame images, (i.e. rather than using stereo pairs) it is necessary to incorporate surface data into the imagery. Pictometry applies DEM data to both its oblique and orthogonal frame images and does so using two different techniques. In orthogonal frames, the raw image data is warped and rewritten as a regular rectangular grid. For oblique frames, the original image is left unperturbed in order to preserve the natural perspective; the data behind the image is warped to match the image. Orthogonal Frames Pictometry s Standard Product (i.e. non-orthomosaiced) individual orthogonal frames are ortho rectified using the directly geo-registered EOs, the calibrated camera model parameters, and the best available digital elevation model (DEM). The orthorectification process will be used to remove horizontal displacement caused by terrain height variation, earth curvature, and camera based distortions. The process requires a resampling of the imagery; a cubic-convolution method is utilized to perform this resampling. Oblique Frames Pictometry incorporates DEM data into oblique images using a patented process called a Tessellated Ground Plane (TGP). The TGP can be thought of as a grid of elevation values, each creating a triangular facet similar to a triangular irregular network (TIN), yet not irregular. The TGP is appended to the image in a trailer; the Page 6 of 193

7 density of the TGP can be modified to suit customer needs. A very dense grid will provide the highest degree of accuracy, while a less dense grid will provide for smaller files. The final approved imagery is then put through a verification process wherein common points are compared in the images (tie-points). The calculated coordinates for each tie-point are then checked against those from the other tie-points of the same point in different images. Any anomalous points are investigated to ensure the tiepoint is valid and the image data is reprocessed if necessary. A summary of the results for each of the missions is attached in Appendix D. At the conclusion of the data processing, coordinate points may be collected across the project area, in accordance with specifications set forth in FGDC-STD If collected, the surveyed points are then compared against the coordinates measured in the imagery captured and produced by Pictometry and a final accuracy statement is then prepared. Ground Control Surveying Based upon Pictometry s surveying experience utilizing the National Geodetic Survey (NGS) published control network and CORS stations, the existing NGS published control network is considered adequate to support the absolute horizontal accuracies specified below. No additional high order geodetic surveying networks or additional Ground Control Points (GCPs) were established for purposes of this project unless otherwise noted herein. Published control points utilized for this project are listed in Appendix E. Summary of Specifications for Orthophotography Overview Pictometry s AccuPlus certified orthomosaic is a high accuracy orthomosaic generated from the vertical imagery captured by Pictometry s PentaView Capture System. The imagery is auto correlated, surveyed ground control points are measured, and a bundle adjustment performed to ensure the high level of absolute accuracy. The triangulated frames are then orthorectified to a terrain surface either derived from LiDAR or based on an automated surface extraction directly from the imagery. The resulting ortho frames are then mosaicked using an automated seamline generating algorithm followed by a manual correction process. Bridge decks and elevated roadways are corrected so as to be positioned properly; any instances of severe building lean are also corrected to ensure visibility of ground level transportation features. The photogrammetric mapping control utilized is adequate to support the identified accuracy specifications. This report documents the procedures and accuracies, aircraft positing systems and aerial triangulation statistics of the photogrammetric mapping project. The horizontal and vertical control are based on direct ties to National Geodetic Survey control stations, National Spatial Reference System (NSRS), unless otherwise noted. The horizontal and vertical control used for this project shown. The orthophotography meets the horizontal accuracy of specifications of the contract and are reported at the 95% confidence level as specified in the FGDC Geospatial Positioning Accuracy Standards, Part 3: National Standard for Spatial Data Accuracy ( Page 7 of 193

8 Fully Analytical Aerial Triangulation The digital AGPS/INS aerial photography will be processed with MATCH-AT Automatic Aerial Triangulation software to constrain the digital aerial imagery to the Applanix POSPAC software computed X, Y, Z, omega, phi, and kappa photo center parameters and the photogrammetric mapping survey control points. Bundle adjustments consisting of APGS/INS controlled photo center exposures are constrained to ground control points to compute the following values: 1. RMS automatic points in photo 2. RMS control and manual points in photo 3. RMS control points with default standard deviation set 4. RMS IMU observations 5. RMS GNSS observations 6. Average (weighted) sigma naught A summary of the Aerotriangulation results is attached in Appendix G. Production of Orthomosaics Auto-Correlation Automatic aerial triangulation (AAT) was performed on all imagery for use in the production of ortho mosaics. The AAT process makes use of the directly observed exterior orientation (EO) of each exposure, i.e. the position and orientation of each exposure derived from the GPS and INS data in conjunction with ground control points. Pictometry used Inpho s Match-AT software for the final bundle adjustment. Pictometry reviewed all residuals between control points and tie points, and compared the calculated coordinates of any available check points values to actual control. Pictometry reviewed a statistical analysis of the error propagation and theoretical accuracy. If any control points were not within range or statistical analysis indicated weak ties between images, new manual tie points were added to increase the strength of the solution. Control points on the photography were checked against control actually used to ensure that all available control was observed. An initial post process was performed with all control points set to check (an unconstrained adjustment) to verify the internal mathematical solution prior to the introduction of the control point values. Control and tie point residuals from the final bundle adjustment were examined and checked against project specifications. The bundle adjustment was also performed with a portion of the GCPs set as check points to verify the accuracy of the aerial triangulation adjustment. The RMSE error of the calculated point coordinates as compared to the surveyed point coordinates are reported. Following the aerial triangulation phase, the nadir imagery was passed into the ortho imagery production phase. This includes orthorectification and mosaicking of individual frames to create a single area-wide image which was be tiled for delivery. Ortho Imagery Production Orthorectified natural color (RGB) images are delivered by Pictometry. Digital Orthorectified images are referenced to the appropriated project datum. Unless otherwise specified, the orthorectified images are Page 8 of 193

9 submitted in uncompressed, untiled, ArcGIS readable, GeoTIFF file format with no internal tiling or overviews. Data was compressed during ANY PHASE of the production process. GeoTIFF files shall include the following GeoTIFF tags and keys: ModelTiepointTag ModelPixelScaleTag GTModelTypeGeoKey GTRasterTypeGeoKey ProjectedCSTypeGeoKey PCSCitationGeoKey ProjLinearUnitsGeoKey Orthorectification To perform the orthorectification, Pictometry utilized the triangulated EOs, the calibrated camera model parameters, and the digital elevation model (DEM). The orthorectification process was used to remove horizontal displacement caused by terrain height variation, earth curvature, and camera based distortions. The orthorectification process required a resampling of the imagery; a cubic-convolution method was utilized to perform this resampling. After ortho rectification, each frame containing a control point measurement was checked against the surveyed coordinates to ensure proper rectification. Color Balancing Consistent radiometry/photometry is recognized as an important characteristic of an ortho mosaic. Pictometry has developed techniques at every step of the process in order to ensure this consistency in its final ortho mosaics. First, Pictometry's PentaView Sensor System is put through a color calibration prior to deployment in order to ensure a consistent response from each sensor in Pictometry's fleet. Next each exposure is carefully monitored and data pertaining to that exposure stored for use during subsequent processing. Prior to ortho rectification, Pictometry applies its proprietary brightness equalization and color balancing software techniques. Both low and high spatial frequency adjustments are applied. Though infrequently the case, following orthorectification, Pictometry has the option to utilize Inpho's Ortho Vista during the mosaicking process if any further correction is deemed desirable. During the review process, final local adjustments of brightness values, color, and contrast based on image content can be performed as necessary Mosaicking The imagery was be aero-triangulated, ortho-rectified, and mosaicked to produce a single seamless ortho-mosaic. The mosaicking portion of the project consisted of two major steps: radiometric balancing and seamline selection. Pictometry utilized both its proprietary software and Inpho s OrthoVista software package to perform the radiometric balancing. Additionally, local adjustments of brightness values, color, and contrast were performed as necessary. Following radiometric balancing, the OrthoVista software package was utilized to generate automatic seamlines between source frames. The automatically generated seamlines were manually edited to eliminate feature misalignment due to seamlines which pass through features located above the DEM. Pictometry minimized seamlines through buildings and performed manual corrections where seamlines through buildings are unavoidable. Page 9 of 193

10 In addition to editing for geometric considerations, Pictometry also edited seam line placement for aesthetic purposes, including elimination of split vehicles and shadows where possible. During the seam editing process, Pictometry verified that feature alignment across seamlines is 3 pixels or less. Building Correction Features which are elevated with respect to the DEM are subject to scale increase and radial displacement (e.g. building lean). Due to the narrow field of view of Pictometry s small format camera, building lean is minimized in most cases. Building tilt shall be reduced so that all roads are visible. To the extent possible utilizing the frames available, Pictometry manually corrected buildings which obstruct transportation features due to either scale increase or building lean. Bridge Correction As with buildings and other elevated features, bridges are subject to the effects of scale increase and radial displacement. Pictometry manually corrected bridges as necessary in order to ensure proper planimetric placement and to eliminate distortion due to variances in the DEM below the bridge deck Pictometry has manually corrected bridges as necessary in order to ensure proper planimetric placement and to eliminate distortion due to variances in the DEM below the bridge deck.. Water Bodies In order to preserve uniformity of appearance, Pictometry utilized the seam editing process to attempt to source inland water bodies from a single frame where possible. In areas where this was not possible, Pictometry manually smoothed differences in the color of water bodies and/or apply a single color to said water bodies. Tiling Upon completion of the area wide mosaic Pictometry tiled the imagery. Orthorectified GeoTIFF files represent tiles cut at even intervals (e.g feet X 2500 feet) and cut at even foot grid lines with no overedge. Tiles are accompanied by an index sheet and shape file suitable for loading into ArcGIS. The index sheet shall include tile boundary and filename. Tiles split by the project boundary are completed to their full extent. File Naming Convention Unless otherwise specified by the client, the ortho tile file names are derived from the southwest corner of each tile and shall be based on the U.S. National Grid. File names will include Grid Zone Designation (GZD), block designator and X and Y grid coordinates truncated to an appropriate value. Metadata Project and File (tile) level metadata describing the ortho imagery production process shall be submitted as a deliverable. Unless otherwise specified by the client, one (1) Project Level Metadata file shall be delivered for each product type with corresponding names. One (1) Tile (File) Level Metadata file shall be delivered for each file (tile) with corresponding names. Page 10 of 193

11 Acronyms and Definitions Accuracy r Horizontal (radial) accuracy at the 95% confidence level, defined by the NSSDA Accuracy z Vertical accuracy at the 95% confidence level, defined by the NSSDA AGPS/INS Airborne GPS/Inertial Navigation System ASFPM Association of State Floodplain Managers ASPRS American Society for Photogrammetry and Remote Sensing CMAS Circular Map Accuracy Standard, defined by the NMAS CP Certified Photogrammetrist (ASPRS) CVA Consolidated Vertical Accuracy, defined by the NDEP and ASPRS DEM Digital Elevation Model (gridded DTM) DTM Digital Terrain Model (mass points and breaklines to map the bare earth terrain) DSM Digital Surface Model (top reflective surface, includes treetops and rooftops) E East FDEM Florida Division of Emergency Management FEMA Federal Emergency Management Agency FGDC Federal Geographic Data Committee FOV Field of View FVA Fundamental Vertical Accuracy, defined by the NDEP and ASPRS LAS LiDAR data format as defined by ASPRS LiDAR Light Detection and Ranging H Height HARN High Accuracy Reference Network (NAD 83/2007) N North NAD 83 North American Datum of 1983 NAVD 88 North American Vertical Datum of 1988 NDEP National Digital Elevation Program NGS National Geodetic Survey NMAS National Map Accuracy Standard NOAA National Oceanic and Atmospheric Administration NSSDA National Standard for Spatial Data Accuracy NSRS National Spatial Reference System OPUS Online Positioning Service Pt-id Photo- control point identifier PID Permanent IDentifier (six character alpha/numeric) PS Photogrammetric Surveyor QA/QC Quality Assurance/Quality Control RMS Root Mean Square RMSE r Horizontal (radial) RMS Error (RMSE) computed from RMSEx and RMSEy RMSE x Horizontal RMS Error (RMSE) in the x-dimension (Easting) RMSE y Horizontal RMS Error (RMSE) in the y-dimension (Northing) RMSE z Vertical RMS Error (RMSE) in the z-dimension (Elevation) RTK Real Time Kinematic Std. Dev Standard Deviation SVA Supplemental Vertical Accuracy, defined by the NDEP and ASPRS TIN Triangulated Irregular Network VMAS Vertical Map Accuracy Standard, defined by the NMAS Page 11 of 193

12 Standard Product Absolute Horizontal Accuracies Background The absolute horizontal accuracy (of features) within a particular frame of Pictometry orthogonal imagery depends on a number of factors. Among these are the accuracy of point location within the image, the accuracy of the ground surface (DEM) used for rectification, and the accuracy of the exposure station coordinates and orientation of the sensor at the time of the exposure (Exterior orientation Parameters). The Position and Orientation System (POS) data provides the Exterior Orientation Parameters of the sensor at the time of exposure in a ground coordinate system. These parameters (commonly referred to as EOs) are primarily derived from the post-processed POS solution, the accuracy of which in turn depends upon the accuracy of the GPS reference station coordinates and the solved vector to the capture system. The absolute horizontal accuracy of individual pixels as measured within individual orthogonal frames is dependent primarily upon the accuracy of the POS solution. In orthogonal imagery, the DEM used for rectification is generally of less significance than the POS solution and the error introduced by the DEM increases as we move away from the nadir point. At the nadir point, the contribution to the horizontal error from the DEM is zero and at the edge of the field of view (FOV) the contribution is at its maximum. For standard Pictometry orthogonal imagery, the maximum horizontal error introduced at the edge of the FOV, due to feature distances from the nadir point, is calculated to be approximately 0.32 times the error in the ground surface. Summary Conditions that may affect actual accuracies achieved include specific project site conditions, accuracy of the DEM utilized in imagery rectification, GPS and IMU errors, and variability in control station (e.g. CORS network) availability, accuracies and geometry. The areas tested in support of this document are areas with DEMs having nominal vertical accuracy of 1 meter. Therefore, Pictometry's Standard Product Individual Orthogonal Image Frames, orthorectified utilizing a DEM with a nominal vertical accuracy of 1 meter are compiled to meet: 2.5 feet / 0.76 m horizontal accuracy at a 95% confidence interval (3 inches /7.5 cm GSD 1 ) 2.8 feet / 0.85 m horizontal accuracy at a 95% confidence interval (4 inches /10 cm GSD 2 ) 3.2 feet / 0.98 m horizontal accuracy at a 95% confidence interval (6 inches /15 cm GSD 2 ) 4.0 feet / 1.22 m horizontal accuracy at a 95% confidence interval (9 inches /22.5 cm GSD 3 ) 4.8 feet / 1.46 m horizontal accuracy at a 95% confidence interval (12 inches /30 cm GSD 3 ) 1 : (Estimated) meets or exceeds NMAS & ASPRS Class 1 at 1 =100 (1:1200) 2 : meets or exceeds NMAS & ASPRS Class 2 at 1 =100 (1:1200) 3 : meets or exceeds NMAS & ASPRS Class 1 at 1 =200 (1:2400) Due to the impact of DEM error stated previously ( approximately 0.32 times the error in the ground surface ) the following additional absolute horizontal errors may exist in the imagery created utilizing DEMs of the accuracy listed below: Page 12 of 193

13 Assumed Source DEM Error Equivalent Contour Interval of Source DEM Additional Possible Horizontal Error from Source DEM NSSDA 2.98 feet* 5-foot contour 0 NSSDA 5.96 feet 10-foot contour interval 1.9 feet / 0.58 m NSSDA feet 20-foot contour interval 3.8 feet / 1.16 m NSSDA feet 30-foot contour interval 5.7 feet / 1.74 m *Nominal 1-meter DEM Error as utilized in testing. Standard Product Relative Measurement Accuracies The relative (measurement) accuracy within individual imagery frames is generally independent of the accuracy of an acceptable POS solution as the error in X, Y, and Z position only causes the shift of the image and will not propagate a significant error in ground measured distances within individual image frames. For oblique imagery an error in the X, Y, and Z position creates an error in the distance measurement due to the projection of the field of view across a ground surface that contains some errors. Therefore the accuracy of DEM plays a very important role in determining the accuracy of distance measurement on Pictometry s oblique imagery. For Pictometry s 6-inch GSD oblique imagery, the error of distance measurement caused by DEM error is calculated to be approximately 10 feet for a measured distance of 1000 feet when DEM accuracy is ±7m feet (±1.0% of distance measured) while it is 3 feet when DEM accuracy is ±1m (±0.3% of distance measured), assuming that both start and end points have same DEM error and terrain is flat. There is also an error created by the picking of the desired points (on each end of the line measured) within the actually imagery frame. Relative Measurement Accuracies The relative measurement accuracies which can be achieved, when carefully measuring well-defined features within Pictometry s individually captured orthogonal and oblique frame imagery, can be expressed in a simplified format as follows: ± (1.4 x GSD + 0.3% of distance measured) This equates to the following relative measurement accuracies for a DEM having an estimated error of ±1m: 3 inches /7.5cm GSD Imagery = ± (0.35 feet /11 cm + 0.3% of distance measured) 4 inches /10 cm GSD Imagery = ± (0.47 feet /14 cm + 0.3% of distance measured) 6 inches /15 cm GSD Imagery = ± (0.70 feet /21 cm + 0.3% of distance measured) 9 inches /22.5 cm GSD Imagery = ± (1.05 feet /32 cm + 0.3% of distance measured) 12 inches /30 cm GSD Imagery = ± (1.40 feet /43 cm + 0.3% of distance measured) Page 13 of 193

14 References ASPRS, 2007, Digital Elevation Model Technologies and Applications: The DEM User s Manual, 2nd edition, American Society for Photogrammetry and Remote Sensing, Bethesda, MD. ASPRS, 2004, ASPRS Guidelines, Vertical Accuracy Reporting for LiDAR Data, American Society for Photogrammetry and Remote Sensing, Bethesda, MD, May 24, 2004, ata.pdf. Bureau of the Budget, 1947, National Map Accuracy Standards, Office of Management and Budget, Washington, D.C. FDEM, 2006, Florida GIS, Baseline Specifications for Orthophotography and LiDAR, Appendix B, Terrestrial LiDAR Specifications, Florida Division of Emergency Management, Tallahassee, FL, October, FEMA, 2004, Appendix A, Guidance for Aerial Mapping and Surveying, to Guidelines and Specifications for Flood Hazard Mapping Partners, Federal Emergency Management Agency, Washington, D.C. FGCC, 1984, Standards and Specifications for Geodetic Control Networks, Federal Geodetic Control Committee, Silver Spring, MD, reprinted August FGCC, 1988, Geometric Geodetic Accuracy Standards and Specifications for Using GPS Relative Positioning Techniques, Federal Geodetic Control Committee, Silver Spring, MD, reprinted with corrections, August, FGDC, 1998a, Geospatial Positioning Accuracy Standards, Part I: Reporting Methodology, Federal Geographic Data Committee, c/o USGS, Reston, VA FGDC, 1998b, Geospatial Positioning Accuracy Standards, Part 2, Standards for Geodetic Networks, Federal Geographic Data Committee, c/o USGS, Reston, VA, FGDC, 1998b, Geospatial Positioning Accuracy Standards, Part 3, National Standard for Spatial Data Accuracy, Federal Geographic Data Committee, c/o USGS, Reston, VA, FGDC, 1998d, Content Standard for Digital Geospatial Metadata (CSDGM), Federal Geographic Data Committee, c/o USGS, Reston, VA, NDEP, 2004, Guidelines for Digital Elevation Data, Version 1.0, National Digital Elevation Program, May 10, 2004, NOAA, 1997, Guidelines for Establishing GPS-Derived Ellipsoid Heights (Standards: 2 cm and 5 cm), NOAA Technical Memorandum NOS NGS-58, November, NRC, 2007, Elevation Data for Floodplain Mapping, National Research Council, Washington, D.C. Page 14 of 193

15 Project Summary This report is incomplete without the external hard drives containing the digital orthophotography and oblique photography imagery frame mapping data. A listing of sectors containing imagery frames for this project is in Appendix F. Deliverable Information: Sector type Sector GSD (average) Sector Count Community Neighborhood INCH Image Type Oblique PSI Ortho PMI OrthoX PMI Image Count Capture Window: Friday, January 24, Sunday, March 09, 2014 Tile Projection(s): System Datum Zone Units US State Plane 1983 North American Datum 1983 Florida Western Zone US Survey Feet Source DEM(s): Custom Elevation files were used. Page 15 of 193

16 Summary of Project Absolute Horizontal Accuracies For this project, based upon the testing and in consideration of potential variables due to specific project site conditions, variability in CORS network availability, accuracies and geometry, it can be stated that: Pictometry's 4 inch [10 cm] GSD orthogonal imagery frames are compiled to meet 2.8 feet [85 cm] horizontal accuracy at a 95% confidence interval, which meets or exceeds NMAS & ASPRS Class 2 at 1"=100'. Summary of Project Relative Measurement Accuracies For this project, the relative measurement accuracies which can be achieved, when carefully measuring welldefined features within Pictometry s individually captured orthogonal and oblique frame imagery, can be expressed in a simplified format as follows: ± (1.4 x GSD + 0.3% of distance measured) This equates to the following relative measurement accuracies for a DEM having an estimated error of ±1m: 3 inch GSD Imagery = ± (0.35 feet + 0.3% of distance measured) 4 inch GSD Imagery = ± (0.47 feet + 0.3% of distance measured) 6 inch GSD Imagery = ± (0.7 feet + 0.3% of distance measured) 9 inch GSD Imagery = ± (1.05 feet + 0.3% of distance measured) 12 inch GSD Imagery = ± (1.4 feet + 0.3% of distance measured) Page 16 of 193

17 Appendix A: Sector Map Page 17 of 193

18 Flight Plan Map(s) Page 18 of 193

19 Appendix B: Sensor Data Camera serial Numbers Camera Count: 24 Tail Number Serial Number Camera Orientation N5238K SN20146 Nadir N5238K SN20201 Oblique N5238K SN20092 Oblique N5238K SN20190 Oblique N5238K SN20659 Oblique N51577 SN21087 Nadir N51577 SN20157 Oblique N51577 SN20081 Oblique N51577 SN20150 Oblique N51577 SN20102 Oblique N897LP SN20183 Nadir N897LP SN20189 Oblique N897LP SN20639 Oblique N897LP SN20195 Oblique N897LP SN20105 Oblique N5140D SN20104 Nadir N5140D SN21005 Oblique N5140D SN20148 Oblique N5140D SN20086 Oblique N725SP SN20632 Nadir N725SP SN20193 Oblique N725SP SN20083 Oblique N725SP SN20309 Oblique N725SP SN20281 Oblique Page 19 of 193

20 Mount Orientations Count: 6 Mount Configuration File: \\Xavier\pictometry\Processing Files - Penta\N5238K\N5238K_140112\N5238K_Penta_N5_65mm_ txt # This is a mount configuration file TAIL_NUMBER N5238K MOUNT_ORIENTATION PENTA MENU_NAME RIGHT CAMERA_ORIENTATION LANDSCAPE # These are our angles HEADING_OFFSET_ANGLE ROLL_OFFSET_ANGLE PITCH_OFFSET_ANGLE # Lever arms REF_TO_IMU_XYZ IMU_WRT_REF_RPY REF_TO_GPS_XYZ REF_WRT_CRAFT_RPY # Distances from imu to penta cameras in frame of aircraft (m) IMU_TO_CAM0_XYZ IMU_TO_CAM1_XYZ IMU_TO_CAM2_XYZ IMU_TO_CAM3_XYZ IMU_TO_CAM4_XYZ IMU_TO_CAM5_XYZ # Orientations of penta cameras (degrees) IMU_WRT_CAM0_RPY IMU_WRT_CAM1_RPY IMU_WRT_CAM2_RPY IMU_WRT_CAM3_RPY IMU_WRT_CAM4_RPY IMU_WRT_CAM5_RPY # Camera Rotations CAMERA_ROTATION[0] 0 CAMERA_ROTATION[1] 0 CAMERA_ROTATION[2] 0 CAMERA_ROTATION[3] 0 CAMERA_ROTATION[4] 0 CAMERA_ROTATION[5] 0 # Camera Orientations and Aims CAMERA_AIM[0] CENTER CAMERA_AIM[1] RIGHT CAMERA_AIM[2] LEFT CAMERA_AIM[3] FORWARD CAMERA_AIM[4] BACKWARD # Yaw Compensation YAW_COMPENSATION 0 # Authorization ## Camera0 Focal Length = mm Capture Date = Published by RJM Published Tuesday, January 21, :08:21 Workspace = \\beast\processing\!alignment Projects\Raw Control Fields\38K\!2013\38K_A_140112\Camera 0.pcw ## Camera1 Focal Length = mm Capture Date = Published by RJM Published Tuesday, January 21, :09:08 Workspace = \\beast\processing\!alignment Projects\Raw Control Fields\38K\!2013\38K_A_140112\Camera 1.pcw Page 20 of 193

21 ## Camera2 Focal Length = mm Capture Date = Published by RJM Published Tuesday, January 21, :09:39 Workspace = \\beast\processing\!alignment Projects\Raw Control Fields\38K\!2013\38K_A_140112\Camera 2.pcw ## Camera3 Focal Length = mm Capture Date = Published by RJM Published Tuesday, January 21, :10:09 Workspace = \\beast\processing\!alignment Projects\Raw Control Fields\38K\!2013\38K_A_140112\Camera 3.pcw ## Camera4 Focal Length = mm Capture Date = Published by RJM Published Tuesday, January 21, :10:41 Workspace = \\beast\processing\!alignment Projects\Raw Control Fields\38K\!2013\38K_A_140112\Camera 4.pcw Mount Configuration File: \\xavier\pictometry\processing Files - Penta\N51577\N51577_140108\N51577_Penta_N5_65mm_ txt # This is a mount configuration file TAIL_NUMBER N51577 MOUNT_ORIENTATION PENTA MENU_NAME RIGHT CAMERA_ORIENTATION LANDSCAPE # These are our angles HEADING_OFFSET_ANGLE ROLL_OFFSET_ANGLE PITCH_OFFSET_ANGLE # Lever arms REF_TO_IMU_XYZ IMU_WRT_REF_RPY REF_TO_GPS_XYZ REF_WRT_CRAFT_RPY # Distances from imu to penta cameras in frame of aircraft (m) IMU_TO_CAM0_XYZ IMU_TO_CAM1_XYZ IMU_TO_CAM2_XYZ IMU_TO_CAM3_XYZ IMU_TO_CAM4_XYZ IMU_TO_CAM5_XYZ # Orientations of penta cameras (degrees) IMU_WRT_CAM0_RPY IMU_WRT_CAM1_RPY IMU_WRT_CAM2_RPY IMU_WRT_CAM3_RPY IMU_WRT_CAM4_RPY IMU_WRT_CAM5_RPY # Camera Rotations CAMERA_ROTATION[0] 0 CAMERA_ROTATION[1] 0 CAMERA_ROTATION[2] 0 CAMERA_ROTATION[3] 0 CAMERA_ROTATION[4] 0 CAMERA_ROTATION[5] 0 # Camera Orientations and Aims CAMERA_AIM[0] CENTER CAMERA_AIM[1] RIGHT CAMERA_AIM[2] LEFT CAMERA_AIM[3] FORWARD CAMERA_AIM[4] BACKWARD # Yaw Compensation YAW_COMPENSATION 0 # Authorization ## Camera0 Focal Length = mm Capture Date = Published by ANG Published Wednesday, January 15, :15:34 Workspace = \\beast\processing\!alignment Projects\Raw Control Fields\577\!2013\577_F_140108\Camera 0.pcw Page 21 of 193

22 ## Camera1 Focal Length = mm Capture Date = Published by ANG Published Wednesday, January 15, :16:08 Workspace = \\beast\processing\!alignment Projects\Raw Control Fields\577\!2013\577_F_140108\Camera 1.pcw ## Camera2 Focal Length = mm Capture Date = Published by ANG Published Wednesday, January 15, :16:53 Workspace = \\beast\processing\!alignment Projects\Raw Control Fields\577\!2013\577_F_140108\Camera 2.pcw ## Camera3 Focal Length = mm Capture Date = Published by ANG Published Wednesday, January 15, :17:30 Workspace = \\beast\processing\!alignment Projects\Raw Control Fields\577\!2013\577_F_140108\Camera 3.pcw ## Camera4 Focal Length = mm Capture Date = Published by ANG Published Wednesday, January 15, :18:17 Workspace = \\beast\processing\!alignment Projects\Raw Control Fields\577\!2013\577_F_140108\Camera 4.pcw Mount Configuration File: \\xavier\pictometry\processing Files - Penta\N897LP\N897LP_140115\N897LP_Penta_N5_65mm_ txt # This is a mount configuration file TAIL_NUMBER N897LB MOUNT_ORIENTATION PENTA MENU_NAME RIGHT CAMERA_ORIENTATION LANDSCAPE # These are our angles HEADING_OFFSET_ANGLE ROLL_OFFSET_ANGLE PITCH_OFFSET_ANGLE # Lever arms REF_TO_IMU_XYZ IMU_WRT_REF_RPY REF_TO_GPS_XYZ REF_WRT_CRAFT_RPY # Distances from imu to penta cameras in frame of aircraft (m) IMU_TO_CAM0_XYZ IMU_TO_CAM1_XYZ IMU_TO_CAM2_XYZ IMU_TO_CAM3_XYZ IMU_TO_CAM4_XYZ IMU_TO_CAM5_XYZ # Orientations of penta cameras (degrees) IMU_WRT_CAM0_RPY IMU_WRT_CAM1_RPY IMU_WRT_CAM2_RPY IMU_WRT_CAM3_RPY IMU_WRT_CAM4_RPY IMU_WRT_CAM5_RPY # Camera Rotations CAMERA_ROTATION[0] 0 CAMERA_ROTATION[1] 0 CAMERA_ROTATION[2] 0 CAMERA_ROTATION[3] 0 CAMERA_ROTATION[4] 0 CAMERA_ROTATION[5] 0 # Camera Orientations and Aims # Yaw Compensation YAW_COMPENSATION 0 # Authorization ## Camera0 Focal Length = mm Capture Date = Published by ANG Published Tuesday, January 21, :17:24 Workspace = \\beast\processing\!alignment Projects\Daily Control Field Projects\7LP\!2014\FLCAPE_PENTA_7LP_B_140115_ANGLES\Camera 0.pcw ## Camera1 Focal Length = mm Capture Date = Published by ANG Published Tuesday, January 21, :18:06 Workspace = \\beast\processing\!alignment Projects\Daily Control Field Projects\7LP\!2014\FLCAPE_PENTA_7LP_B_140115_ANGLES\Camera 1.pcw Page 22 of 193

23 ## Camera2 Focal Length = mm Capture Date = Published by ANG Published Tuesday, January 21, :18:31 Workspace = \\beast\processing\!alignment Projects\Daily Control Field Projects\7LP\!2014\FLCAPE_PENTA_7LP_B_140115_ANGLES\Camera 2.pcw ## Camera3 Focal Length = mm Capture Date = Published by ANG Published Tuesday, January 21, :18:58 Workspace = \\beast\processing\!alignment Projects\Daily Control Field Projects\7LP\!2014\FLCAPE_PENTA_7LP_B_140115_ANGLES\Camera 3.pcw ## Camera4 Focal Length = mm Capture Date = Published by ANG Published Tuesday, January 21, :19:24 Workspace = \\beast\processing\!alignment Projects\Daily Control Field Projects\7LP\!2014\FLCAPE_PENTA_7LP_B_140115_ANGLES\Camera 4.pcw Mount Configuration File: \\xavier\pictometry\processing Files - Penta\N5140D\N5140D_140210\N5140D_Penta_N5_65mm_ txt # This is a mount configuration file TAIL_NUMBER N5140D MOUNT_ORIENTATION PENTA MENU_NAME RIGHT CAMERA_ORIENTATION LANDSCAPE # These are our angles HEADING_OFFSET_ANGLE ROLL_OFFSET_ANGLE PITCH_OFFSET_ANGLE # Lever arms REF_TO_IMU_XYZ IMU_WRT_REF_RPY REF_TO_GPS_XYZ REF_WRT_CRAFT_RPY # Distances from imu to penta cameras in frame of aircraft (m) IMU_TO_CAM0_XYZ IMU_TO_CAM1_XYZ IMU_TO_CAM2_XYZ IMU_TO_CAM3_XYZ IMU_TO_CAM4_XYZ IMU_TO_CAM5_XYZ # Orientations of penta cameras (degrees) IMU_WRT_CAM0_RPY IMU_WRT_CAM1_RPY IMU_WRT_CAM2_RPY IMU_WRT_CAM3_RPY IMU_WRT_CAM4_RPY IMU_WRT_CAM5_RPY # Camera Rotations CAMERA_ROTATION[0] 0 CAMERA_ROTATION[1] 0 CAMERA_ROTATION[2] 0 CAMERA_ROTATION[3] 0 CAMERA_ROTATION[4] 0 CAMERA_ROTATION[5] 0 # Camera Orientations and Aims CAMERA_AIM[0] CENTER CAMERA_AIM[1] RIGHT CAMERA_AIM[2] LEFT CAMERA_AIM[3] FORWARD CAMERA_AIM[4] BACKWARD # Yaw Compensation YAW_COMPENSATION 0 # Authorization ## Camera0 Focal Length = mm Capture Date = Published by SEZ Published Thursday, February 13, :10:43 Workspace = \\beast\processing\!alignment Projects\Daily Control Field Projects\40D\!2014\FLCAPE_Penta_40D_C_140210_Angles\Camera 0.pcw Page 23 of 193

24 ## Camera1 Focal Length = mm Capture Date = Published by SEZ Published Thursday, February 13, :11:31 Workspace = \\beast\processing\!alignment Projects\Daily Control Field Projects\40D\!2014\FLCAPE_Penta_40D_C_140210_Angles\Camera 1.pcw ## Camera2 Focal Length = mm Capture Date = Published by SEZ Published Thursday, February 13, :12:12 Workspace = \\beast\processing\!alignment Projects\Daily Control Field Projects\40D\!2014\FLCAPE_Penta_40D_C_140210_Angles\Camera 2.pcw ## Camera3 Focal Length = mm Capture Date = Published by SEZ Published Thursday, February 13, :12:49 Workspace = \\beast\processing\!alignment Projects\Daily Control Field Projects\40D\!2014\FLCAPE_Penta_40D_C_140210_Angles\Camera 3.pcw ## Camera4 Focal Length = mm Capture Date = Published by SEZ Published Thursday, February 13, :13:25 Workspace = \\beast\processing\!alignment Projects\Daily Control Field Projects\40D\!2014\FLCAPE_Penta_40D_C_140210_Angles\Camera 4.pcw Mount Configuration File: \\Xavier\pictometry\Processing Files - Penta\N725SP\N725SP_131227\N725SP_Penta_N5_65mm_ txt # This is a mount configuration file TAIL_NUMBER N725SP MOUNT_ORIENTATION PENTA MENU_NAME RIGHT CAMERA_ORIENTATION LANDSCAPE # These are our angles HEADING_OFFSET_ANGLE ROLL_OFFSET_ANGLE PITCH_OFFSET_ANGLE # Lever arms REF_TO_IMU_XYZ IMU_WRT_REF_RPY REF_TO_GPS_XYZ REF_WRT_CRAFT_RPY # Distances from imu to penta cameras in frame of aircraft (m) IMU_TO_CAM0_XYZ IMU_TO_CAM1_XYZ IMU_TO_CAM2_XYZ IMU_TO_CAM3_XYZ IMU_TO_CAM4_XYZ IMU_TO_CAM5_XYZ # Orientations of penta cameras (degrees) IMU_WRT_CAM0_RPY IMU_WRT_CAM1_RPY IMU_WRT_CAM2_RPY IMU_WRT_CAM3_RPY IMU_WRT_CAM4_RPY IMU_WRT_CAM5_RPY # Camera Rotations CAMERA_ROTATION[0] 0 CAMERA_ROTATION[1] 0 CAMERA_ROTATION[2] 0 CAMERA_ROTATION[3] 0 CAMERA_ROTATION[4] 0 CAMERA_ROTATION[5] 0 # Camera Orientations and Aims CAMERA_AIM[0] CENTER CAMERA_AIM[1] RIGHT CAMERA_AIM[2] LEFT CAMERA_AIM[3] FORWARD CAMERA_AIM[4] BACKWARD # Yaw Compensation YAW_COMPENSATION 0 # Authorization Page 24 of 193