12314418R0005_0003.pdf

(x)

12314418R0005 x x

1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted ; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGEMENT TO BE RECEIVED AT

THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted , such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

x

DASO-OPPM-POD-AMB-CO

Fort Collins CO 80521-2795 301 S. Howes St., Suite 321 Acquisition Management Branch-CO

USDA, DM/OPPM/POD

05/10/20180003

13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS. IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

12. ACCOUNTING AND APPROPRIATION DATA (If required) is not extended.is extended, Items 8 and 15, and returning

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended , by one of the following methods: (a) By completing

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

FACILITY CODE CODE

10B. DATED (SEE ITEM 13)

10A. MODIFICATION OF CONTRACT/ORDER NO.

9B. DATED (SEE ITEM 11)

9A. AMENDMENT OF SOLICITATION NO.

CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)

7. ADMINISTERED BY (If other than Item 6)CODE 6. ISSUED BY

PAGE OF PAGES

4. REQUISITION/PURCHASE REQ. NO.3. EFFECTIVE DATE2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO. (If applicable)

1. CONTRACT ID CODE

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

04/17/2018

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority) appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

E. IMPORTANT: Contractor is not, is required to sign this document and return ___1_______________ copies to the issuing office.

ORDER NO. IN ITEM 10A.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

The Purpose of Amendment 0003 is to address the following:

1)Enclosed is Q & A for RFP, 12314418R0005, titled: 12314418R0005_0003_Q&A_NAIP 2018.

2)Remove FAR 52.217-3, Evaluation Exclusive of Options (JUL 1990).

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)15A. NAME AND TITLE OF SIGNER (Type or print)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 15B. CONTRACTOR/OFFEROR 16C. DATE SIGNED

(Signature of person authorized to sign) (Signature of Contracting Officer)

JASON A. KATTMAN

STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

NSN 7540-01-152-8070

Previous edition unusable

Except as provided herein, all terms and conditions of the document referenced in Item 9 A or 10A, as heretofore changed, remains unchanged and in full force and effect .

x

PART I – THE SCHEDULE

SECTION B – SUPPLIES OR SERVICES AND PRICES/COSTS 12314418R0005_RFP

2018 National Agriculture Imagery Program (NAIP) Page 2 of 131

PART I ‐ THE SCHEDULE

SECTION B ‐ SUPPLIES OR SERVICES AND PRICES/COSTS

B‐1 SCHEDULE OF ITEMS ‐ UPDATE

CLIN 0001: Base Project Items

STATE

QUARTER

QUADS

ACQUISITION

SEASON(S)

UNIT PRICE TOTAL

California 11,082 15 Apr ‐ 7 Aug (4) *

Delaware 176 15 Jun ‐ 15 Aug

Indiana 2,689 15 Jun ‐ 15 Aug

Kentucky 2,930 15 May ‐ 15 Aug

Maine 2,754 1 Jul ‐ 31 Aug

Maryland 901 1 Jun ‐ 15 Aug*

Michigan 4,846 1 Jul ‐ 31 Aug (2)

Mississippi 3,236 15 Jun ‐ 31 Aug

Missouri 5,018 15 Jun ‐ 31 Jul

Nebraska 5,627 1 Jul ‐ 31 Aug

North Dakota 5,712 20 Jun ‐ 20 Aug*

Oregon 7,473 1 Jun ‐ 15 Aug (2)

South Dakota 5,992 1 Jul ‐ 31 Aug*

Tennessee 3,000 1 Apr ‐ 15 Sep (2)

Utah 6,032 15 Jun ‐ 15 Aug

Virginia 3,031 15 Apr ‐ 31 Aug (2)

Wisconsin 4,484 20 Jun ‐ 31 Aug*

In case of discrepancy between a unit price (i.e. price per DOQQ) and the total price, the unit price will be presumed to be correct. If your proposal includes adjoining states with the same acquisition periods, duplicate DOQQs along the boundary will be eliminated from the total quantity during final negotiations.

Legend: *A non‐contractual flying preference has been requested by the state Number in parenthesis indicate the number of acquisition periods

OPTION CLIN 0002: Additional Project Items

STATE

QUARTER

QUADS

ACQUISITION

SEASON(S)

UNIT PRICE TOTAL

Connecticut 413 1 Jul ‐ 15 Aug

Massachusetts 744 1 Jul ‐ 31 Aug

New Hampshire 771 1 Jul ‐ 31 Aug

New Mexico 8,028 15 May ‐ 15 Aug*

North Carolina 3,582 15 May ‐ 15 Aug

Rhode Island 116 1 Jul ‐ 15 Aug

Texas 17,277 15 Apr ‐ 30 Sep (4)

Vermont 812 1 Jul ‐ 31 Aug

West Virginia 1,831 1 Jul ‐ 30 Sep

2018 National Agriculture Imagery Program (NAIP) Page 3 of 131

In case of discrepancy between a unit price (i.e. price per DOQQ) and the total price, the unit price will be presumed to be correct. If your proposal includes adjoining states with the same acquisition periods, duplicate DOQQs along the boundary will be eliminated from the total quantity during final negotiations.

Legend: *A non‐contractual flying preference has been requested by the state Number in parenthesis indicate the number of acquisition periods

OPTION CLIN 0003: Early Access Web Service

STATE

EXERCISE BY

DATE

TOTAL PRICE

California

Connecticut

Delaware

Indiana

Kentucky

Maine

Maryland

Massachusetts

Michigan

Mississippi

Missouri

Nebraska

New Hampshire

New Mexico

North Carolina

North Dakota

Oregon

Rhode Island

South Dakota

Tennessee

Texas

Utah

Vermont

Virginia

West Virginia

Wisconsin

2018 National Agriculture Imagery Program (NAIP) Page 4 of 131

OPTION CLIN 0004: Compressed County Mosaics

EXERCISE

BY

NC ONLY NC & CIR

STATE DATE QUANTITY UNIT PRICE

TOTAL

PRICE

UNIT

PRICE

TOTAL

PRICE

California 58

Connecticut 8

Delaware 3

Indiana 92

Kentucky 120

Maine 16

Maryland 24

Massachusetts 14

Michigan 83

Mississippi 82

Missouri 115

Nebraska 93

New Hampshire 10

New Mexico 33

North Carolina 100

North Dakota 53

Oregon 36

Rhode Island 5

South Dakota 66

Tennessee 95

Texas 254

Utah 29

Vermont 14

Virginia 100

West Virginia 55

Wisconsin 72

2018 National Agriculture Imagery Program (NAIP) Page 5 of 131

OPTION CLIN 0005: Stereo Imagery

EXERCISE

BY DATE

QUANTITY

(SQ MILES)

UNIT PRICE TOTAL PRICE

California 164,692

Connecticut 5,768

Delaware 2,550

Indiana 38,478

Kentucky 43,364

Maine 36,162

Maryland 13,065

Massachusetts 10,307

Michigan 64,620

Mississippi 50,776

Missouri 73,386

Nebraska 79,026

New Hampshire 10,425

New Mexico 123,439

North Carolina 54,397

North Dakota 72,238

Oregon 100,610

Rhode Island 1,619

South Dakota 79,962

Tennessee 45,364

Texas 274,703

Utah 87,040

Vermont 10,901

Virginia 44,886

West Virginia 26,664

Wisconsin 59,640

2018 National Agriculture Imagery Program (NAIP) Page 6 of 131

OPTION CLIN 0006: Digital Surface Model

EXERCISE

BY DATE

QUANTITY

(SQ MILES)

UNIT PRICE TOTAL PRICE

California 164,692

Connecticut 5,768

Delaware 2,550

Indiana 38,478

Kentucky 43,364

Maine 36,162

Maryland 13,065

Massachusetts 10,307

Michigan 64,620

Mississippi 50,776

Missouri 73,386

Nebraska 79,026

New Hampshire 10,425

New Mexico 123,439

North Carolina 54,397

North Dakota 72,238

Oregon 100,610

Rhode Island 1,619

South Dakota 79,962

Tennessee 45,364

Texas 274,703

Utah 87,040

Vermont 10,901

Virginia 44,886

West Virginia 26,664

Wisconsin 59,640

B‐2 TYPE OF CONTRACT (FAR 52.216‐1, APR 1984)

The Government contemplates award of a Firm‐Fixed‐Price contract resulting from this solicitation.

B‐3 AVAILABILITY OF FUNDS (FAR 52.232‐18, APR 1984)

Funds are not presently available for this contract. The Government’s obligation under this contract is contingent upon the availability of appropriated funds from which payment for contract purposes can be made. No legal liability on the part of the Government for any payment may arise until funds are made available to the Contracting Officer for this contract and until the Contractor receives notice of such availability, to be confirmed in writing by the Contracting Officer.

2018 National Agriculture Imagery Program (NAIP) Page 7 of 131

B‐4 AVAILABILITY OF FUNDS FOR THE NEXT FISCAL YEAR (FAR 52.232‐19, APR 1984)

Funds are not presently available for performance under this contract. The Government’s obligation for performance of this contract beyond that date is contingent upon the availability of appropriated funds from which payment for contract purposes can be made. No legal liability on the part of the Government for any payment may arise for performance under this contract until funds are made available to the Contracting Officer for performance and until the Contractor receives notice of availability, to be confirmed in writing by the Contracting Officer.

SECTION C – DESCRIPTION/SPECIFICATIONS/WORK STATEMENT 12314418R0005_RFP

2018 National Agriculture Imagery Program (NAIP) Page 8 of 131

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. It is anticipated this solicitation will result in multiple award(s), single year, firm fixed price contract.

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 rejection or 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

2018 National Agriculture Imagery Program (NAIP) Page 9 of 131 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 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 twenty degrees (20°).

(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.

2018 National Agriculture Imagery Program (NAIP) Page 10 of 131

(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 4‐band (natural color and color near‐infrared), digital orthorectified imagery. The image tiles shall be projected in the native Universal Transverse Mercator (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 United States

Geological Survey (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 e. 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 shall 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.

2018 National Agriculture Imagery Program (NAIP) Page 11 of 131

(i) Media Requirements. Image tiles and associated metadata files shall be delivered electronically as defined in the contract Section D‐1(a), Media Shuttle. 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 USB thumb drive, 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).

(l) 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.

(1) 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

2018 National Agriculture Imagery Program (NAIP) Page 12 of 131

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 platforms only. Blank attribute for space‐based systems 6 Double data types 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.

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

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

(4) 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”

3.5 TASK 4: 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.

2018 National Agriculture Imagery Program (NAIP) Page 13 of 131

(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 5: 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. The Government will evaluate offers for award purposes by including only the price for the basic requirements; i.e., options prices will not be included in the evaluation for award purposes. The unit prices for optional deliverable items 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 before the option date specified in Section B.

4.1 Optional Task – Additional States. Non‐priority states are considered optional tasks and may be exercised upon contract award or by 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 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 – Early Access and Provisional Web Services. The Contractor shall provide and maintain two separate web services, a provisional and a final production service, for each

2018 National Agriculture Imagery Program (NAIP) Page 14 of 131 state in accordance with the requirements specified below. Farm Service Agency’s state and county offices will use the web service, by means of standard GIS desktop or web‐based applications, to allow for visual verification of current field conditions prior to crop harvesting in support of farm related programs.

(a) General Requirements.

(1) Deliver a single 4‐band Esri® ArcGIS Server RESTful service per state with a spatial resolution at, or better resolution, than specified in Paragraph C‐3.3(b), Ground Sample Distance. Imagery shall be visible at all scales (between 1:1 and 1:15,000,000).

(2) Deliver a vector metadata service that provides, as minimum, the image collection date and time for each exposure footprint as a polygon. A vector should completely cover the entire area represented by the extents of the visible imagery. This vector service should be “hollow” allowing the end user to see the imagery underneath. In addition, each polygon in the vector service shall be symbolized with different colors (prefer unique color per acquisition date) and contain a single 10pt Arial Bold font, or similar, label of the date of acquisition using a MM/DD/YYYY format. Labels shall be visible at screen scales of 1:100K and larger.

(3) The services shall have an average uptime of 99% during the hours of 6am – 10pm (eastern daylight time), Monday through Friday (excluding Federal holidays).

Downtime of 4 hours or less during peak usage times will be permissible, with prior Contractor Officers approval, to allow new and/or corrected imagery to be added to the services.

(4) The services shall be able to be consumed by client applications including Esri® ArcGIS 10.x and Esri® ArcGIS Online.

(5) Use a disinterested third‐party to monitor server performance and response time.

Monitoring image service render speed is recommended but not required. Any non‐ third‐party observer/software needs prior Contractor Officers approval.

(6) The service shall support and authenticate, at a minimum, 100 Government users (up to a maximum of 1,000 users) concurrently accessing the services for each state.

The service shall use Hyper Text Transfer Protocol Secure (HTTPS) and shall have a current SSL Certificate. Authentication using individual unique usernames and passwords is prohibited.

(b) EAWS Reports (Deliverable). The Contractor shall provide service status via three weekly reports.

(1) The first report shall document the imagery upload status (see paragraph C‐4.5(a) requirements) and shall be updated cumulatively. The report shall have a separate record/row for each exposure and contains, as a minimum, the following three columns: exposure id, date of acquisition, and date of upload. Weekly reports shall begin when the first upload takes places and continue until 30 days after final QQ delivery for that state.

(2) The second report shall document the services uptime/availability (see paragraph 4.2(a)(3) requirements) and server performance/response time (see paragraph 4.2(a)(5) requirements) for the previous week. Weekly reports shall begin when the first upload takes place and continue until the shutdown of the production services.

2018 National Agriculture Imagery Program (NAIP) Page 15 of 131

A one‐time cumulative report covering the entire contract period shall be submitted when the production services are shutdown.

(3) The third report shall document the usage statistics of the services. At a minimum, the reports shall include the number of unique uses by week, number of image requests, and the IP/domain names of the top 20 users (for the reporting period).

Weekly reports shall be submitted on the same schedule as the second report. A one‐time cumulative report covering the entire contract period shall be submitted when the production services are shutdown.

The reports shall be digital format compatible with Microsoft® Office software (such as Word, Excel, or Access) or Adobe® PDF file format. Additional data/attributes may be submitted in optional worksheet columns but must be after the required columns.

(c) Provisional Imagery Web Service Requirements. The Contractor shall provide a provisional imagery service composed of spatially defined imagery that was collected to support the production of the DOQQs required under paragraph C‐3.3, TASK 3:

Orthorectification and Related Services. Imagery shall be added to the web service incrementally as acquired throughout the acquisition period. The following requirements only apply to the provisional imagery services.

(1) The provisional imagery, including any reflights, shall be uploaded and available for consumption on average five (5) business days after the acquisition date. The average will be a prorated calculation. The square miles of each exposure divided by the sum of the total square miles acquired will be used to determine the weight of each upload exposure.

(2) The provisional imagery shall be orthorectified and shall be projected in NAD83, using the corresponding native majority UTM zone for each state. All well‐defined points tested shall fall within ten (10) meters of true ground at a 95% confidence level (see FGDC‐STD‐007.3‐1998, page 3‐10).

(3) At a minimum, the provisional imagery shall be color corrected/adjusted to allow reasonable determination of field conditions (radiometrically balancing across images is not required).

(4) The services shall be operational from the first day of the acquisition period until 30 days after the production imagery web service has been completed and loaded with all final production imagery for the state.

(5) The provisional services shall use the following naming convention:

Image Service: <st>_EAWS_4B_2018 Metadata Service: <st>_EAWS_ACQDATE_2018

Where:

<st> ‐ two letter official state abbreviation

Example:

Image Service: AR_EAWS_4B_2018 Metadata Service: AR_EAWS_ACQDATE_2018

(d) Production Imagery Web Service Requirements. The Contractor shall provide a production imagery service composed of the final DOQQ production imagery delivered

2018 National Agriculture Imagery Program (NAIP) Page 16 of 131 to the Government under paragraph C‐3.3, TASK 3: Orthorectification and Related Services. The following requirements only apply to the production imagery services.

(1) The services shall be operational from the date of the first incremental DOQQ production imagery delivery until March 31, 2019. All additional incremental DOQQ deliveries shall be uploaded to the service within three business days.

(2) The production services shall use the following naming convention:

Image Service: <st>_PROD_4B_2018 Metadata Service: <st>_PROD_ACQDATE_2018

Where:

<st> ‐ two letter official state abbreviation

Example:

Image Service: AR_PROD_4B_2018 Metadata Service: AR_PROD_ACQDATE_2018

4.3 Optional Task – County Mosaics.

(a) Compressed County Mosaic (Deliverable): The Contractor shall create a natural color and false color infrared mosaic (depending on awarded option) for each county in the project item.

(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 40:1. 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.

2018 National Agriculture Imagery Program (NAIP) Page 17 of 131

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. The shapefile shall have the same attributes and requirements, including the metadata file, as stated in paragraph 3.3(l), 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.3(l)(4), Shapefile Metadata, except for 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.

(c) Media Requirements. Mosaics, shapefiles, and associated metadata files shall be delivered on hard drives as defined in contract Section D‐1(b), Hard Drive Disks or flash drives as defined in contract SectionD‐1(c), USB Flash Drives. No more than one project item may be placed on a drive.

4.4 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 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 zero (0) digital number (DN) values.

2018 National Agriculture Imagery Program (NAIP) Page 18 of 131

(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 four (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 or image viewing software including Esri® ArcGIS and Adobe® Photoshop. 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.4(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.

2018 National Agriculture Imagery Program (NAIP) Page 19 of 131

(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.

(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 push broom 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

2018 National Agriculture Imagery Program (NAIP) Page 20 of 131

1 Padded with leading zeros 2 Double data types shall be length of 19 (18 precision, 11 scale) 3 Calendar dates in ISO 8601 complete date format (“yyyy‐mm‐dd” format) 4 Calendar dates 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 types shall be length of 19 (18 precision, 11 scale) 3 Calendar dates in ISO 8601 complete date format (“yyyy‐mm‐dd” format) 4 Calendar dates 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

2018 National Agriculture Imagery Program (NAIP) Page 21 of 131

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 types shall be length of 19 (18 precision, 11 scale) 3 Calendar dates in ISO 8601 complete date format (“yyyy‐mm‐dd” format) 4 Calendar dates 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) Media Requirements. Image tiles and associated metadata files shall be delivered on hard drives as defined in the contract Section D‐1(b), Hard Drive Disks. No more than one project item may be placed on a drive using the following directory structure (all directories shall be created at the root directory):

\georeferenced Color corrected georeferenced imagery. All stereo block files and associated support files. If a Leica ADS sensor is used, the following files as well: .ads, .hist, .odf, .odf.adj

\gps No data is to be stored here \gps_base Any GPS ground data used to supplement the ABGPS positional data adjustments such as base stations or CORS \index Project file geodatabase

2018 National Agriculture Imagery Program (NAIP) Page 22 of 131

\minification All scanning sensor minification files (. min). Note: This directory shall only include data if a scanning sensor is used

(e) Pre‐production Sample (Deliverable).