DRAFT_RFP_2018_NAIP_single-year_contract.pdf

PART I – THE SCHEDULE

SECTION C – DESCRIPTION/SPECIFICATIONS/WORK STATEMENT DRAFT RFP

PART I - THE SCHEDULE

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

PERFORMANCE WORK STATEMENT

1.0 PURPOSE AND OBJECTIVES

The objective of this contract is to furnish orthorectified imagery in accordance with the requirements, specifications, terms, conditions, clauses, and provisions specified herein, effective for the periods stated in the schedule.

1.1 Background. National Agriculture Imagery Program (NAIP) imagery is intended to provide current information of agricultural conditions in support of U.S. Department of Agriculture (USDA) farm programs. For USDA Farm Service Agency (FSA), the imagery provides a base map for activities such as crop compliance, acreage reporting, environmental compliance, Conservation Reserve Program (CRP) compliance, and Farm Records maintenance. The NAIP imagery is generally acquired in projects covering full states in cooperation with partnering agencies, who use the imagery for a variety of purposes, including land use planning and natural resource assessment. NAIP imagery is also used for disaster response, often providing the most current pre-event imagery.

2.0 GENERAL REQUIREMENTS

The general scope of this contract is to procure vertical, high resolution, direct digital orthorectified imagery to support various Government geographic information system (GIS) programs.

2.1 Location of Work. The 2018 NAIP collection will acquire imagery for approximately one-third of the Continental United States. Please refer to Attachment 2, Project Item Requirements and Maps.

2.2 Imagery Delivery Schedule. Imagery shall be submitted in accordance with Paragraph F-3, Deliveries.

2.3 Importance of Image Quality. Any imagery submitted to the Government that does not meet the minimum quality requirements may impact the Government’s ability to properly use the imagery for its intended purpose and will be subject to a price reduction based on the diminished usability of the product.

3.0 TASKS AND CRITICAL SUBTASKS

The specific tasks of this contract are summarized as follows.

3.1 TASK 1: Flight Planning. The Contractor is required to provide the necessary project management, coordination, and supervision to conduct project planning, flight planning and acquisition, image processing, product delivery, and related technical and progress reports as required in the contract.

3.2 TASK 2: Imagery Acquisition. The Contractor shall obtain precise vertical aerial imagery using an approved digital sensor in accordance with the following technical requirements. For the purpose of this contract, imagery collected from satellite-based systems are considered vertical aerial imagery.

(a) Airspace Clearances. The project items may contain areas of controlled or restricted airspace. It is the responsibility of the Contractor to obtain all approvals necessary to assure that required clearances are achieved. (see H-3, Airspace Clearances)

(b) Acquisition Periods. The acquisition period for the individual project items are listed in

Attachment 2, Project Item Requirements and Maps. The Contractor shall acquire imagery only during that portion of the day when the sun angle exceeds the minimum thirty degrees (30°).

(c) Image Resolution. The Contractor shall collect raw imagery resolution at or better than the required Ground Sample Distance (GSD) specified in paragraph 3.3(b), Ground Sample Distance. Interpolation of the raw imagery to increase GSD is not permitted.

(d) Sensor Tilt (airborne platform only). It is desired that exposures be made when the optical axis of the camera is in a vertical position. The Contractor shall not acquire imagery when the tilt (departure from the vertical) of any exposure exceeds four degrees (4°) or relative tilt between any two successive exposures which exceed six degrees (6°). Tilt shall not average more than two degrees (2°) in any 16 km (10 mile) section of a flight line and shall not average more than one degree (1°) for the entire project.

(e) Off-Nadir Angle (satellite platform only). It is desired that exposures be made when the satellite is in true nadir position. The Contractor shall not acquire imagery when the off-nadir angle exceeds 20 degrees.

(f) Ground Conditions. Imagery shall be acquired when skies are clear, free from smoke or excessive haze, and well-defined images can be resolved. Image tiles with greater than ten percent (10%) cloud cover or cloud shadows per tile (including any required buffer) will not be accepted. The ground shall be free from snow below timberline, standing water (other than natural or man-made ponds and lakes), flood waters from streams which have overflowed their banks, and wet ground which obscures field, soil or crop boundary lines. The Contractor shall minimize specular reflections, especially in agriculture areas, by avoiding acquisition during periods of peak solar reflectivity, or by patching the area using imagery from other exposures.

(g) Digital Sensor. The Contractor shall only acquire imagery using a digital sensor system(s) that meet the requirements in Attachment 3, APFO Specification for Digital Camera Based Acquisition, and have been approved by the Contracting Officer.

(h) Priorities for Project Items. The Contracting Officer or Contracting Officer

Representative (COR) may direct, by written order, certain project items or regions within those items listed in the Schedule to be acquired in a priority order, weather and ground conditions permitting. All reasonable efforts will be directed toward providing a schedule of operations favorable to both the Government and Contractor

3.3 TASK 3: Orthorectification and Related Services. Contractor shall provide orthorectification services to produce digital orthorectified imagery. The image tiles shall be projected in the native UTM zone using the NAD83 Datum.

(a) Orthorectified Image Files (Deliverable). The Contractor shall color-correct the imagery so it radiometrically matches the ground at the time of exposure including, but not limited to, any dodging, histogram stretching, brightness adjustments, and/or color balancing. The Government’s preference is not to have the image tiles “radiometrically balanced” with other neighboring tiles. The tile shall not contain any borders, artifacts, or other non-image items. All tiles shall meet the image quality requirements specified in Attachment 4, USDA Digital Imagery Quality Specification.

(b) Ground Sample Distance. The GSD requirement for this project is a minimum of 60 cm.

(c) Image Buffer. The image tile shall cover the entire image area of one USGS standard quarter quadrangle (QQ), with a 300 (±30) pixel buffer on all four sides of the QQ.

(d) Ground Control. The Contractor shall be responsible for acquiring all ground control needed to meet the absolute horizontal accuracy specification noted in paragraph e.

(e) Horizontal Accuracy. All well-defined points tested on image tile shall fall within 4.0 meters of true ground at a 95% confidence level (see FGDC-STD-007.3-1998, page 3-10).

(f) Digital Elevation Model. The Contractor may use any Digital Elevation Model (DEM) for terrain-correcting the imagery required to meet horizontal accuracy specifications in paragraph d. The Contractor shall document the elevation dataset used during the orthoimagery production process including, but not limited to corrections made to an existing dataset, in the process description field of the metadata. The description should be at the project item level and not tailored to individual tiles unless unique conditions necessitate the additional detail.

(g) File Format. Image tiles will be delivered as an uncompressed, 4-band, 8-bit per band, tiled, georeferenced tagged image file format (GeoTIFF) in accordance with Attachment 5, TIFF/GeoTIFF Requirements. The band order shall be red, green, blue, and near infrared (RGBN).

(h) Naming Convention. Image tiles shall use the file naming specified in Attachment 6, File

Naming Convention. File names shall be in lower case only.

(i) Media Requirements. Image tiles and associated metadata files shall be delivered on industry standard hard drives as defined in the contract Section D-1(d)(1), Hard Drive Disks. No more than one project item may be placed on a drive.

(j) Metadata (Deliverable). The Contractor shall create a Federal Geographic Data

Committee (FGDC) compliant, per the FGDC-STD-001-1998 specification, metadata file for each image tile using the Government provided template. The file must parse cleanly through the current USGS metadata parser “mp” version 2.9.40 (or later version) without any errors. Metadata files shall use the Extensible Markup Language (XML) file format and use the same naming convention as the image tile but with an “xml” extension.

(k) Pre-production Sample (Deliverable). For each project item, the Contractor shall submit a single radiometrically corrected image tile for Government review. The sample shall be a TIFF (GeoTIFF preferred), and submitted on a standard CD or DVD. The Government will evaluate and provide an approval or disapproval letter with comments no later than five (5) business days, with a goal of 24 hours. Additional project item area samples may be submitted for review if approved by the Contracting Officer Representative (COR).

3.4 TASK 4: Seamline Shapefile (Deliverable). The Contractor shall create a project item based

Esri® compatible polygon shapefile index. The index shall be topologically correct and contain a polygon for each exposure used in the creation of the imagery. The polygons shall completely cover the entire area represented by the extents of the visible imagery and not have gaps (slivers) within the area. There shall be no overlapping or multiple-part polygons in the shapefile. The smallest area covered by a single polygon shall not be smaller than 40,470 square meters (approx. 10 acres). If any reflights or image reprocessing changes either the actual seamline polygon or one of the attributes, the Contractor shall resubmit a revised shapefile(s) with imagery resubmittal.

(a) Attributes. The shapefiles shall be attributed with the following data columns:

ATTRIBUTE COLUMN DATA

DESCRIPTION NAME TYPE EXAMPLE

Image acquisition date IDATE Char(10) 2012-07-23 Polygon start date/time1 SDATE Char(16) 07/23/2012 13:52 Polygon end date/time1 EDATE Char(16) 07/23/2012 13:53 Color Type2 BCON Char(3) M4B Camera type (Digital or film) CAM_TYPE Char(20) Digital Camera manufacturer CAM_MAN Char(50) Leica Geosystems Camera model CAM_MOD Char(25) ADS-80 Camera HW and FW version3 HARD_FIRM Char(50) camera F/W v2.14 Sensor or lens serial number SENSNUM Char(50) 30029 Aircraft type4,5 AC_TYPE Char(50) C441 Aircraft tail number5 ACTAILNUM Char(10) N12345R Polygon area (square meters) SHAPE_AREA Double(19)6 250000.0000 Red electromagnetic spectrum7 RED_RNGE Char(10) 604-664 Green electromagnetic spectrum7 GREEN_RNGE Char(10) 533-587

Blue electromagnetic spectrum7 BLUE_RNGE Char(10) 420-492 NIR electromagnetic spectrum7 NIR_RNGE Char(10) 683-920 1 Local 24-hour clock. The start/end time will be for the collection of the individual polygon (will be the same for frame-based systems) 2 Possible values are: NC (natural color), CIR (color infrared), and M4B (4-band) 3 Top level information specific to camera system. Other hardware information (i.e. GPS/IMU) is optional.

4 ICAO designator (i.e., use C441 for a Cessna 441 Conquest II) 5 Airborne platform only. Blank attribute for space-based systems 6 Double data type shall be length of 19 (18 precision, 11 scale) 7 Electromagnetic spectrum range in nanometers (no spaces allowed in free text)

The geometry of the shapefile shall conform to the extents of all QQs delivered in the project item (i.e., one shapefile for the whole state). Shapefiles shall use the GCS North American 1983 (NAD83) coordinate system and be delivered with QQs.

(b) File Format. Shapefile format compatible with Esri® ArcGIS 10.2 and newer version software.

(c) Naming Convention: Files shall use the file naming specified in Attachment 6, File

Naming Convention. File names shall be in lower case only.

(d) Shapefile Metadata (Deliverable). The Contractor shall create a FGDC compliant, per the FGDC-STD-001-1998 specification, metadata file using the Government provided template for each seamline shapefile generated. The metadata must parse cleanly through the USGS metadata parser “mp” version 2.9.40 (or later version) without any errors. The metadata shall use the XML file format and shall use the same file naming convention as the seamline shapefile but with an “xml” extension.

3.5 TASK 5: Project Management. The Contractor shall establish and maintain a project management system with a designated project manager for this effort. Project management consists of those activities required to plan, manage, administer, and control efforts to accomplish the objective of the contract. The project manager will serve as the primary point of contact for the Contractor’s activity with the Government. The project manager’s name and contact information shall be identified, in writing, to the Contracting Officer within 20 days of contract award.

(a) Progress Reports (Deliverable). Progress Reports indicating the progress made in imagery acquisition shall be submitted on a daily basis in accordance with instructions in Attachment 7, Progress Reports Convention. Reporting shall start when the Contractor receives the Notice to Proceed and continue until the area is completed or the acquisition period and any extension ends. Separate reports are required from each acquisition crew. On days that no imagery was collected, the body of the report should state “No progress.” Each progress report shall be sent by email transmission to the COR not later than the day following performance. In the event that day is a holiday or non-business day, the report shall be sent on the next business day.

(b) Subcontract Management (Deliverable). If the Contractor uses subcontractors in the performance of the contract, a plan and procedure will be established to manage its subcontractors. Contractor should give prior notification of any subcontracts in accordance with G-4, Subcontracts. The Contractor is encouraged to maximize its use of partnerships and subcontractors to accomplish the requirements of this contract.

However, the Contractor is solely responsible for the performance and cost control of its partnerships and subcontractors.

3.6 TASK 6: Quality Control. Quality control shall be exercised by the Contractor continuously throughout the performance of the contract. Procedures shall be established to assure that all contract materials are delivered in accordance with the delivery schedule and at the required level of accuracy and quality. The Contractor shall inspect and constantly monitor the image quality and coverage, and shall undertake immediate reflights of any imagery where the quality fails to meet minimum requirements of the contract specifications. Any marginal photography/imagery submitted for inspection which does not meet minimum requirements may be rejected. The marginal photography may be accepted, at the Government’s convenience, but shall be subject to a price reduction based on the diminished utility of the product. The nature and urgency of this project may require the Government to make equitable financial adjustments for materials deemed rejectable or where product use is adversely impacted. USDA inspection and acceptance procedures are described in Section E, Inspection and Acceptance.

3.7 Regional Settings. All digital files, including imagery and metadata, shall be created using standard ANSI English-US setting. For example, periods (“.”) shall be used to separate the whole number from the fractional portion when recording decimal numbers, and data representing a long date shall be recorded as “Wednesday, August 17, 2005 5:09:38 PM.”

4.0 OPTIONS

The Government is considering awarding the following optional tasks to include additional states and deliverables produced from the base imagery requirements. Optional deliverable items will not be awarded without the base item. Except when it is determined in accordance with FAR 17.206(b) not to be in the Government’s best interests, the Government will evaluate offers for award purposes by adding the total price for all options to the total price for the basic requirement.

Evaluation of options will not obligate the Government to exercise the option(s). The unit prices should be the delta cost for the individual options and not include the base imagery cost.

The Contracting Officer may exercise any of the following options upon contract award or mutual agreement until May 31, 2018.

4.1 Optional Task(s) – Additional States.

Non-priority states are considered optional tasks and may be exercised upon contract award or by mutual agreement following award. Any priority state that is not awarded initially due to lack of funds will be considered optional tasks and may be exercised by mutual agreement.

A non-priority state may be exercised even if all priority states are not awarded or exercised, based on funding and need.

4.2 Optional Task – County Mosaics.

(a) Compressed County Mosaic (Deliverable): The Contractor shall create a three-band mosaic for each county in the project item. The three-band mosaics may be processed to either natural color or infrared. Both natural color and infrared sets may be required.

(1) Image Quality. The Contractor shall tone balance the composite DOQQs to give the

Compressed County Mosaic (CCM) a consistent and uniform image quality appearance that eliminates a checkerboard effect. The resulting CCM should maintain as much of the original color and appearance of the color corrected tiles as practical.

(2) Horizontal Accuracy. The accuracy requirements from paragraph 3.3(e), Horizontal Accuracy, shall be preserved when creating the CCM using the imagery associated with the quarter quadrangle tiles

(3) File Format. The Contractor shall compress the mosaic using LizardTech MrSID® Generation Three (MG3) format in accordance with the requirements listed below.

• The target compression ratio shall be 1:40. All CCM compression shall be at the same ratio and settings ("region of interest" compressed at a different ratio will not be accepted).

• When encoding the CCM, the following settings shall be applied: compression block size of 64; both the transparency and background values set to an RGB value of 0,0,0 (black); and use the “maximum zoom level” applicable to the input image, for example: checking the “Use Maximum Zoom Levels for Image” button in the encoding options menu

• The image header shall contain correct Esri® compatible projection information for the mosaic.

• Standard MrSID® MG3 files generated by the LizardTech software (i.e., .sid, .sdw, and .txt) shall be included.

• The Contractor shall provide the text file created when generating the CCM. The file shall use the same naming convention as the CCM but with a “.txt” extension.

• The Contractor shall provide an “.aux” file containing Esri® projection information for each CCM. The auxiliary file shall contain the proper projection information for the mosaic and shall match the information in the CCM header.

The file shall use the same naming convention as the CCM but with an “.aux” extension.

(4) Naming Convention. The CCMs shall use the file naming specified in Attachment 6, File Naming Convention. File names shall be in lower case only.

(5) Mosaic Metadata (Deliverable). The Contractor shall create a FGDC compliant, per the FGDC-STD-001-1998 specification, metadata file using the Government provided template for each CCM generated. The metadata must parse cleanly through the USGS metadata parser “mp” version 2.9.40 (or later version) without any errors.

The metadata shall use the XML file format and shall use the same file naming convention as the seamline shapefile but with a “.met” extension.

(b) Mosaic Seamline Shapefile (Deliverable). The Contractor shall create a polygon seamline shapefile index using the same projection as the CCM and shall be delivered on the same media. The shapefile shall have the same attributes and requirements, including the metadata file, as stated in paragraph 3.4, TASK 4 – Seamline Shapefile, except the naming convention.

(1) File Format. Shapefile format compatible with Esri® ArcGIS 10.2 and newer version software.

(2) Naming Convention: The mosaic shapefiles shall use the same file naming convention as the CCM but with the standard shapefile file extensions (i.e., .shp, .shx, .dbf, and .prj).

(3) Seamline Shapefile Metadata (Deliverable). The Contractor shall create a metadata for the shapefile using the requirements stated in paragraph 3.4(c), Shapefile Metadata, with the exception of the file name. The metadata shall use the XML file format and shall use the same file naming convention as the seamline shapefile but with an “.xml” extension.

4.3 Optional Task – Stereo Imagery.

(a) Color-corrected Image Files (Deliverable). The contractor shall create epipolar (L1) resampled image tiles with external geo-referencing suitable for import into industry standard softcopy stereo workstations. All tiles shall meet the image quality requirements specified in Attachment 4, USDA Digital Imagery Quality Specification, expect for paragraphs 2.2, Specular Reflections, and 2.3, Image Mosaicking.

(1) Image Quality. The Contractor shall make necessary radiometric adjustments, including stretching, dodging, color correction, etc., to the acquired imagery in order to match ground conditions at the time of exposure and to ensure the best possible color balance for both natural color and color infrared. Image pixels shall not any contain 0 digital number (DN) values.

(2) Spatial Resolution: The imagery shall be submitted using the native collected resolution, unless prior approval from the Contracting Officer.

(3) Overlaps. The recommended end and sidelap for frame-based sensors is:

Endlap: Optimum 62%; Minimum 57%; Recommended Maximum 67% Sidelap: Optimum 30%; Minimum 20%; Recommended Maximum 45% The recommended sidelap for push broom sensors is:

Side lap: Optimum 30%; Minimum 27%; Recommended Maximum 45% Note: the recommended minimum overlaps above may not be adequate for stereo viewing in areas of high relief and the recommended maximum may need to be exceeded in order to provide this coverage.

(4) Coverage. Delivered imagery shall provide complete stereo coverage of the project item.

(5) Georeferenced Accuracy. The principal point shall have an accuracy not exceeding a 4 meter offset from true ground.

(6) File Format. Single point georeferenced, uncompressed, 4-band, 8-bit GeoTIFF file.

GeoTIFF files shall be properly georeferenced so that the image is oriented north up when viewed in GIS software including Esri® ArcGIS and ERDAS Imagine. Individual image files shall not exceed 2GB in size.

(7) Raster Support Files (Deliverable). The Contractor shall produce an AUX (Esri® and ERDAS compatible Auxilary statistic/projection file) and a RRD (Esri® and ERDAS compatible Reduced Resolution Dataset pyramid file) for each image file. Each AUX file shall have statistics calculated with the Skip Factor in the X and Y as 1, and Bin Type as Direct. In addition, the AUX file shall contain the proper projection information for the tile and shall match the information in the GeoTIFF header.

Each RRD file shall be created using a 3X3 kernel, Binomial Interpolation.

(8) Naming Convention. Image tiles shall use the file naming specified in Attachment 6, File Naming Convention. File names shall be in lower case only.

(9) Image Metadata (Deliverable). The Contractor shall create a FGDC compliant, per the FGDC-STD-001-1998 specification, metadata file using the Government provided template for each image file generated. The metadata must parse cleanly through the USGS metadata parser “mp” version 2.9.40 (or later version) without any errors.

The metadata shall use the XML file format and shall use the same file naming convention as the image file but with an “.xml” extension.

(b) Stereo Block Files (Deliverable). The Contractor shall create stereo block files so that digital image files created in Section C-4.2(a), Color-corrected Image Files, can be brought in and viewed in stereo-pairs with very minimal adjustment to the x or y parallax. Data fields in the stereo block file shall be populated with sensor specific data.

Each block file should include the average flying height for the area covered by that block file, rather than for the entire project item. The file shall be projected in the 1983 North American Datum (NAD83), 1988 North American Vertical Datum (NAVD) GEOID12A (or most recent), using the corresponding native majority UTM zone for the project item.

(1) Image Reference Structure: Stereo block files shall be produced in a mutually agreeable layout structure. Each block file should be rectangular in area with a minimum of 200 referenced images.

(2) File Format. The stereo block files shall be Leica Photogrammetry Suite (LPS) compatible and shall be readable in Stereo Analyst extensions for ERDAS IMAGINE 2011 and Esri® ArcGIS 10.2 and newer. The Government prefers the use of .blk files.

See Exhibit 2 for naming convention. The files shall be stored on a hard drive (See Section C-9) according to the Hard Drive Directory Structure Template, Exhibit 10.

(3) Naming Convention. Block files shall use the file naming specified in Attachment 6, File Naming Convention. File names shall be in lower case only.

(4) Block File Metadata (Deliverable). The Contractor shall create a FGDC compliant, per the FGDC-STD-001-1998 specification, metadata file using the Government provided template for each block file generated. The metadata must parse cleanly through the USGS metadata parser “mp” version 2.9.40 (or later version) without any errors. The metadata shall use the XML file format and shall use the same file naming convention as the image file but with an “.xml” extension.

(c) Project Geodatabase (Deliverable). The Contractor shall produce a file Geodatabase, compatible with Esri® ArcGIS® 10.2 and newer versions, for each project item. The feature dataset shall be projected in the corresponding native majority UTM zone for the project item. The photo-center location, UTM coordinates, shall be corrected to reflect the physical ground location and shall be accurate within 4 meters of true ground. The coordinates shall be expressed in meters and formatted to the same datum and projection required for the GeoTIFF image files. The project geodatabase shall be resubmitted with corrections reflecting any image corrections, reflights, or completion of additional flights after original submission. The geodatabase shall contain a feature dataset that contains following three classes:

(1) Photo Center Point Feature Class. The Contractor shall create a point feature class named “Image_Centers” for each image tile center (tiles segmented from a pushbroom sensor may need to be calculated) with the following attributes:

Flight Line number1 FLTLN Char(4) 0027 Exposure number1 EXPNUM Char(4) 0001 Date of exposur3 IDATE Char(10) 2015-08-27 Image file name NAME Char(50) see Attachment 6 Point Acquisition date/time4 DATE Char(16) 08/27/2016 13:52 Color Type* BCON Char(3) M4B Camera type** CAM_TYPE Char(20) Digital Camera manufacturer CAM_MAN Char(50) Zeiss Camera model CAM_MOD Char(25) DMC Sensor serial number SENSNUM Char(100) 30029 UTM zone UTM Char(3) 12 Corrected center point northing2 NORTH Double(19) 4342654.243 Corrected center point easting2 EAST Double(19) 448901.634 Flight altitude2,5 FLTALT Double(19) 7048.63 Num of GPS satellites acquired GPSNUM Short Int 5 Position Dilution of Precision2 PDOP Double(19) 1.5 IMU omega value2,6 OMEGA Double(19) .0001358 IMU phi value2,6 PHI Double(19) .01073000 IMU kappa value2,6 KAPPA Double(19) -.873265 1 Padded with leading zeros 2 Double data type shall be length of 19 (18 precision, 11 scale) 3 Calendar date in ISO 8601 complete date format (“yyyy-mm-dd” format) 4 Calendar date will be in “mm/dd/yyyy” format and time component will use local 24-hour clock. The start/end time will be for the collection of the individual polygon (will be the same for frame-based systems)

5 Altitude at camera, in meters above Mean Sea Level (MSL) in MMMMM.MM format

6 Inertial measurement unit (IMU) angular rate in radians in UTM

* Possible values are: NC (natural color), CIR (color infrared), and M4B (4-band) ** Possible values are: Digital or Film

(2) Flight Line Feature Class. The Contractor shall create a line feature class named

“Flight_Lines” for each flight line with the following attributes:

Flight Line number1 FLTLN Char(4) 0027 Date of exposure3 IDATE Char(10) 2016-08-27 Flight Line start date/time4 SDATE Char(16) 08/27/2016 13:52 Flight Line end date/time4 EDATE Char(16) 08/27/2016 13:53 Color Type* BCON Char(3) M4B Camera type** CAM_TYPE Char(20) Digital Camera manufacturer CAM_MAN Char(50) Intergraph Camera model CAM_MOD Char(25) DMC Sensor serial number SENSNUM Char(100) 30029

Flight Line Direction DIR Char(20) North Flight altitude2,5 FLTALT Double(19) 7048.63 1 Padded with leading zeros 2 Double data type shall be length of 19 (18 precision, 11 scale) 3 Calendar date in ISO 8601 complete date format (“yyyy-mm-dd” format) 4 Calendar date will be in “mm/dd/yyyy” format and time component will use local 24-hour clock.

5 Altitude at camera, in meters above Mean Sea Level (MSL) in MMMMM.MM format

(3) Image Footprint Polygon Feature Class. The Contractor shall create a polygon feature class named “Image_Footprint” for each georeferenced exposure footprint with the following attributes (polygon shall represent the actual ground displacement of the image acquired):

ATTRIBUTE NAME DATA

DESCRIPTION COLUMN TYPE EXAMPLE

Flight Line number1 FLTLN Char(4) 0027 Exposure number1 EXPNUM Char(4) 0001 Date of exposure3 IDATE Char(10) 2016-08-27 Image file name NAME Char(50) see Attachment 6 Polygon start date/time3 SDATE Char(16) 08/27/2016 13:52 Polygon end date/time3 EDATE Char(16) 08/27/2016 13:53 Color Type* BCON Char(3) M4B Camera type** CAM_TYPE Char(20) Digital Camera manufacturer CAM_MAN Char(50) Intergraph Camera model CAM_MOD Char(25) DMC Sensor serial number SENSNUM Char(100) 30029 Corrected center point (lat)2,5 LAT Double(19) 57.71936 Corrected center point (lon)2,5 LON Double(19) -135.41498 1 Padded with leading zeros 2 Double data type shall be length of 19 (18 precision, 11 scale) 3 Calendar date in ISO 8601 complete date format (“yyyy-mm-dd” format) 4 Calendar date will be in “mm/dd/yyyy” format and time component will use local 24-hour clock. The start/end time will be for the collection of the individual polygon (will be the same for frame-based systems)

5 Decimal degrees (DD.DDDDDD or -DDD.DDDDDD format)

(4) File Format. The Project Geodatabase shall be an Esri® file geodatabase compatible file that is compatible with Esri® ArcGIS® 10.2 and newer versions.

(5) Naming Convention. Image tiles shall use the file naming specified in Attachment 6, File Naming Convention. File names shall be in lower case only.

(6) Metadata (Deliverable). The Contractor shall create a FGDC compliant, per the

FGDC-STD-001-1998 specification, metadata file using the Government provided template for each geodatabase generated. The metadata must parse cleanly through the USGS metadata parser “mp” version 2.9.40 (or later version) without any errors. The metadata shall use the XML file format and shall use the same file naming convention as the geodatabase but with a “.xml” extension.

(7) Additional Support Files (Deliverable). The following support files are required for push boom sensors:

*.ads a pointer file that lists each of the *.tif image segments for the strip *.hist histogram for strip in xml format *.odf orientation data file, containing the x, y, z, omega, phi and kappa orientations for each scanline.

*.odf.adj orientation data after AT adjustment.

*.min list of minification files *.sup BAE SocetSet support file, georeference data for SocetSet and other stereo softcopy workstations *.tif multiple tiff files containing ADS imagery rectified to the AMT elevation.

\cam sub-folder with sensor calibration files.

(d) Pre-production Sample (Deliverable). For each project item, the Contractor shall provide a “group” of four radiometrically corrected image tiles (two adjoining images in each of two adjacent flight lines and a sample stereo block file pointing to the four images. The Government will evaluate and provide an approval or disapproval letter with comments no later than fifteen (15) business days. Additional project item area samples may be submitted for review if approved by the Contracting Officer Representative (COR).

4.4 Optional Task – Digital Surface Model.

(a) Point Cloud Dataset (Deliverable). The contractor shall provide a digital surface model (an elevation model that represents the earth's surface and includes all objects on it) using an industry standard algorithm (such as Semi-Global Matching software). The nominal spacing shall be double the native imagery resolution (i.e., 1m spacing for 50cm imagery). Four versions of the point clouds will be delivered: high resolution point cloud with RGB color encoding; high resolution point cloud with CIR color encoding; thinned point cloud with RGB color encoding; and thinned point cloud with CIR color encoding.

The dataset shall not have gaps in coverage either along flight lines or between flight lines except over water.

(1) Accuracy. The dataset shall have the same horizontal accuracy as the digital orthorectified imagery. There is no vertical accuracy specification for the dataset.

(2) Point Classification. The point cloud dataset shall be unedited. All points shall all have the same default classification of 0 (unclassified) or 2 (ground).

(3) Overlaps: The dataset shall have the same overlaps as the stereo option stated in paragraph C-4.2(a)(3), Overlaps.

(4) File Format. The point cloud data shall be a compressed (LAZ) file format and must conform to the ASPRS LAS 1.2 specification (dated Sep 2, 2008).

(5) Dataset Structure. Point cloud data shall delivered in a directory structure that separates files by block, flight lines within a block and individual LAZ segments within a flight line.

Example:

\AZ_A_z12_AT \001_512_150530_1601_

\002_512_150530_1622_ \FCIR_002_512_150530_1622__1_5856_2784.laz \FCIR_Thinned_002_512_150530_1622__1_5856_2784.laz \RGB_002_512_150530_1622__1_5856_2784.laz \RGB_Thinned_002_512_150530_1622__1_5856_2784.laz \FCIR_002_512_150530_1622__1_12000_2784.laz

(6) Naming Convention. The dataset shall use the file naming specified in Attachment 6, File Naming Convention. File names shall be in lower case only.

(7) Metadata (Deliverable). The Contractor shall create a FGDC compliant, per the

FGDC-STD-001-1998 specification, metadata file. A Government metadata template will not be provided. The metadata must parse cleanly through the USGS metadata parser “mp” version 2.9.40 (or later version) without any errors. The metadata shall use the XML file format and shall use the same file naming convention as the seamline shapefile but with an “.xml” extension.

(b) Shapefile Index. The contractor shall provide an Esri® compatible polygon shapefile index of all the LAZ files within the block. Polygons shall be a minimum bounding rectangle (MBR) of all the points within each LAZ file.

(1) File Format. Shapefile format compatible with Esri® ArcGIS 10.2 and newer version software.

(2) Naming Convention. The dataset shall use the file naming specified in Attachment 6, File Naming Convention. File names shall be in lower case only.

(3) Metadata (Deliverable). The Contractor shall create a Federal Geographic Data

Committee (FGDC) compliant, per the FGDC-STD-001-1998 specification, metadata file. A Government metadata template will not be provided. The metadata must parse cleanly through the USGS metadata parser “mp” version 2.9.40 (or later version) without any errors. The metadata shall use the XML file format and shall use the same file naming convention as the seamline shapefile but with an “.xml”

(c) Rasterized Image (Deliverable). The contractor shall provide a rasterized version of the point cloud dataset for each block. The image shall be a single-band, 32-bit floating point, georeferenced image file. Use of natural neighbor interpolation is recommended when creating the rasterized image. The raster post spacing should be between 5 and 10 times the ortho GSD.

(1) File Format. The image file shall be georeferenced and in ERDAS IMAGINE file format (*.img) with the no-data value defined in the header.

(2) Naming Convention. The *.img file name shall include the block name.

(3) Raster Support Files. The Contractor shall include image pyramids that are readable by Stereo Analyst extensions for ERDAS IMAGINE and Esri® ArcGIS.

(4) Metadata (Deliverable). The Contractor shall create a Federal Geographic Data

Committee (FGDC) compliant, per the FGDC-STD-001-1998 specification, metadata file. A Government metadata template will not be provided. The metadata must parse cleanly through the USGS metadata parser “mp” version 2.9.40 (or later version) without any errors. The metadata shall use the XML file format and shall use the same file naming convention as the seamline shapefile but with an “.xml”

5.0 GOVERNMENT-FURNISHED INFORMATION

Pursuant to the Government-Furnished Property (GFP) clause (see Section I-9, Government- Furnished Property) the Government shall only furnish items of property listed below:

5.1 Required Coverage. The Contractor will be furnished upon award one (1) Esri® compatible shapefile per project item containing the required contract coverage. The shapefile contains, at a minimum, the following attributes: USGS Geographic Name Information System (GNIS) quad name, latitude and longitude of the southeast corner (expressed in both decimal degrees and degrees, minutes, seconds), and UTM zone.

5.2 Metadata Template. The Contractor will be furnished upon award two (2) data text files (.txt file format) containing Federal Geographic Data Committee (FGDC) compliant metadata template to be used when creating the DOQQ tile metadata and the state-based shapefile metadata (as required in paragraph 3.3(i), Metadata, and 3.4(d), Shapefile Metadata, respectfully). If either the mosaic (paragraph 4.1, Compressed County Mosaic) or stereo (paragraph 4.2, Stereo Imagery) options are exercised, additional FGDC compliant metadata template(s) will be furnished to the Contractor to be used when creating the mosaic and/or stereo metadata (as required in paragraph 4.1(a)(5), Mosaic Metadata, 4.1(b)(3), Seamline Shapefile Metadata, 4.2(a)(9), Image Metadata, 4.2(b)(4), Block File Metadata, and 4.2(c)(6), Metadata. No metadata templates will be provide in the DSM option (paragraph 4.2, Digital Surface Model) is exercised.

5.3 Compressed County Mosaic (CCM) Coverage – DOQQ List. If the mosaic (paragraph 4.1, Compressed County Mosaic) option is exercised, the Contractor will be furnished upon award one (1) data text file (.txt) containing a list of all DOQQ tiles required for the creation of the CCM coverage for each county in that state item. The data text file will contain, as a minimum, quad name, quadrant, state, latitude and longitude of the SE corner of the quad, USGS quad number, NAPP station number, latitude and longitude of the quad center, USDA arckey number, and the native UTM zone.

6.0 ADMINISTRATIVE MATTERS

6.1 Wage Determination. Wage Determination number 1995-222, Revision xx, dated xxx xx, xxxx will be applicable for Contractors located nationwide. See Attachment 8, Wage Determination.

SECTION D– PACKING AND MARKING DRAFT RFP

SECTION D - PACKAGING AND MARKING

D-1 MEDIA REQUIREMENTS

(a) Hard Drive Disks. All hard disk drives (HDDs) used to deliver imagery shall be “factory new” industry standard internal Serial Advanced Technology Attachment (SATA), 3.0 Gb/sec transfer-rate hard drives, with a minimum rotation speed of 7,200 rpm. Drives may be either

3.5 inch or 2.5 inch form factors. The drives shall have a maximum storage capacity of four terabytes (4TB) with no more than ninety percent (90%) of the individual hard drive capacity used for actual storage. Each drive shall be enclosed in anti-static bag and shall have the label attached directly to the outer surface of the bag identifying the project contained on the drive in accordance with Attachment 9, Hard Drive Labeling Requirements. The files shall not be write-protected nor require an ‘administrator’ to access them. The drives shall become property of the Government and will not be returned to the Contractor. External hard drives are not allowed on this contract.

(b) Digital Versatile Disks. All digital versatile disks (DVDs) shall be delivered on archival media,

4.7 Gigabytes (GB) (120-minute) per disk DVD+/-R, ISO 9660 Mode 1 format using level 2 interchange. The Contractor must insure that each and every copy session has been properly closed. No multi-session enabled DVDs shall be acceptable. In addition to the packaging requirements in D-2, all DVD media shall be packaged in standard single DVD jewel cases (5- 5/8" x 4-15/16" x 3/8") with a clear front cover. The DVD label should be readable without opening the case or removing the DVD from the case. “Slim” or other non-standard sized jewel cases shall not be accepted.

D-2 PACKAGING FOR SHIPMENT

All material shall be packed for shipment in such a manner that ensures acceptance by common carrier and safe delivery at the destination. Containers and closures shall comply with the Interstate Commerce Commission regulations, Uniform Freight Classification rules, or regulations of other carriers as applicable to the mode of transportation. Damaged materials shall be replaced by the Contractor at no cost to the Government.

A packing slip shall accompany each shipment, itemizing all materials included in the shipment.

D-3 SHIPPING RECEIPTS

Receipts from common carriers for shipment of materials shall be retained by the Contractor and made available to the Contracting Officer upon request.

SECTION D– PACKING AND MARKING DRAFT RFP

D-4 SHIPPING CONTAINER MARKINGS

All shipping containers shall be clearly marked with the delivery address. See Section F-5, Place of Delivery.

D-5 CLAUSES INCORPORATED BY REFERENCE (FEB 1998) (FAR 52.252-2)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available.

Also, the full text of a clause may be accessed electronically at this/these address(es):

{No clauses for this Section of the Contract}

SECTION E– INSPECTION AND ACCEPTANCE DRAFT RFP

PART I -THE SCHEDULE

SECTION E - INSPECTION AND ACCEPTANCE

E-1 INSPECTION AND ACCEPTANCE (FEB 1988) (AGAR 452.246-70)

The Contracting Officer or the Contracting Officer's duly authorized representative will inspect and accept the supplies and/or services to be provided under this contract.

Inspection and acceptance will be performed at:

Aerial Photography Field Office 2222 West 2300 South Salt Lake City, Utah 84119-2020

E-2 INSPECTION PROCEDURE

All materials specified in Section F-2, Deliverables, will be inspected to determine conformance to all contract requirements and specifications. Inspections will be performed at APFO in Salt Lake City, Utah. (Refer to FAR 52.246-2, Inspection of Supplies-Fixed Price, and FAR 52.246-4, Inspection of Services-Fixed Price)

If any of the services do not conform to the contract requirements, the Government may require the Contractor to perform the services again in conformity with contract requirements, at no increase in contract amount. When the defects in services cannot be corrected by re-performance, the Government may:

(a) Require the Contractor to take necessary action to ensure that future performance conforms to contract requirements and

(b) Reduce the contract price to reflect the reduced value of services performed.

E-3 INSPECTION SCHEDULE

The Government will make every effort to inspect the Quarter Quadrangle Image Tiles and related data material within 12 months after they are received at the point designated. Should the inspection procedure be delayed longer than 12 months, the Contractor will be notified of the reason(s) for delay and given the estimated completion date. Contract materials will be inspected in the order of their receipt, unless otherwise prioritized by the Government.

The Contractor will be notified in writing whether the materials are satisfactory and what materials, if any, shall be remade because of non-conformance with contract requirements.

E-4 PARTIAL COVERAGE

SECTION E– INSPECTION AND ACCEPTANCE DRAFT RFP

If the Contractor obtains only partial coverage for any project item during the season, then all partial imagery shall be processed and delivered according to the requirements specified for completed imagery. The requirement for processing partial coverage may be waived only by the Contracting Officer.

E-5 ACCEPTANCE

Final acceptance will be made after inspection by the Government of all required materials delivered at the specified destination. Delivery dates for individual products by project item areas are specified in Section F-3, Schedule for Delivery of Materials. The acceptance date will be the date of the letter by the Government to the Contractor stating all materials are acceptable and an invoice may be submitted.

Partial acceptance on any fully completed project due to rejection of deficient or non-compliant material will be made based on both preliminary inspection results of the digital imagery and the final inspection results of all remaining materials. A partial acceptance will result in a price reduction based on the final determination of material compliance to contract requirements and specifications.

Acceptance on any uncompleted project item will be made only after the acquisition period has ended and all materials required for the project item have been delivered and inspected by the Government. The acceptance date will be the date of the letter by the Government to the Contractor identifying the amount of partial acceptance and the amount to invoice.

E-6 CLAUSES INCORPORATED BY REFERENCE (FEB 1998) (FAR 52.252-2)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available.

Also, the full text of a clause may be accessed electronically at this/these address(es):

52.246-02 Inspection of Supplies - Fixed Price (AUG 1996)

52.246-04 Inspection of Services - Fixed Price (AUG 1996)

52.246-16 Responsibility for Supplies (APR 1984)

SECTION F – DELIVERIES OR PERFORMANCE DRAFT RFP

SECTION F - DELIVERIES OR PERFORMANCE

F-1 EFFECTIVE PERIOD OF THE CONTRCT (FEB 1988) (AGAR 452.211-75)

The effective period of this contract is from Date of Award through January 31, 2019.

F-2 NOTICE TO PROCEED

The Contracting Officer will authorize and direct the acquisition period to begin or end anytime within thirty (30) days before or after the approximate acquisition dates given in the Schedule, depending upon the weather, ground, foliage, and sun angle conditions required for the project item or area. No imagery collection shall be undertaken before the Notice to Proceed is issued or after the final date of the acquisition period (or its extension) has occurred. Weather and ground conditions for all project locations will be monitored daily to determine Contractor compliance to performance requirements.

The Notice to Proceed will be given by telephone and confirmed in writing by regular mail. Failure of the Contractor to proceed with flights on a project item area within 10 calendar days after a "Notice to Proceed" is given, may be considered as evidence of failure to prosecute the work so as to ensure its timely completion. As evidence of performance, Progress Reports shall be submitted.

(see Paragraph C-3.5(a), Progress Reports)

F-3 DELIVERABLES

The following deliverables shall be submitted by the Contractor and prepared in accordance with the contract requirements and specifications, including work statement (Section C), packaging and marking (Section D), inspection and acceptance (Section E), and delivery schedule (Section F). The Government strongly encourages the Contractor to submit quarter quadrangle image tiles when available and not wait for a “complete set” prior to submitting. The deliverables for this contract consist of the following:

Deliverable Initial Submission Date Additional Submission(s)

Government Approval Required

Metadata Required

Pre-Production Imagery Sample

Within 21 days of the first image acquisition As required Yes No

Quarter Quadrangle Image Tiles

See paragraph F-4, Schedule for Delivery of Materials

As required Yes Yes (deliver with image tiles)

Seamline Shapefile

Deliver with final project item hard drive As required Yes Yes (deliver with seamlines)

Deliverable Initial Submission Date Additional Submission(s)

Government Approval Required

Metadata Required

Progress Reports Daily, starting with first day of acquisition period

Daily, until 100% imagery acquisition

No No

Subcontract Plan Within 15 business days of contract award As required Yes No

3.1 Optional Task – County Mosaics Deliverables.

Government Approval Required

Metadata Required

Compressed County Mosaic

Not later than 60 calendar days after the acquisition period has ended

As required Yes Yes (deliver with mosaics)

Seamline Shapefile Deliver with mosaics As required Yes Yes (deliver with seamlines)

3.2 Optional Task – Stereo Imagery Deliverables.

Government Approval Required

Metadata Required

Pre-Production Sample

Not later than 60 calendar days after the acquisition period has ended

As required Yes No

Color-corrected Image Files (with associated files)

Not later than 120 calendar days after the acquisition period has ended

As…