Attachment_8_--_Sample_Task_Order_3.docx

Attachment 8

STATEMENT OF WORK

Collection of Orthoimagery and Elevation Data For the Tijuana River Watershed Near San Diego, California and Tijuana, Baja California

1. GENERAL INFORMATION

1.1 Background and Purpose

The International Boundary and Water Commission (IBWC) is a binational commission composed of two sections, the United States Section (USIBWC) and the Mexican Section (MXIBWC). These sections work cooperatively to oversee and resolve various treaty-related issues along the United States – Mexico International Boundary. The USIBWC is issuing this Statement of Work (SOW) to obtain high grade elevation data and high resolution orthoimagery of the Tijuana River Watershed near San Diego, California and Tijuana, Baja California. These data will then be used to develop hydrologic, hydraulic, and sediment transport studies/modeling that will be used to identify best management practices to address excessive sediment/garbage loading in the Tijuana River Basin, an issue that affects both the United States and Mexico.

1.2 General Project Description

Airborne Light Detection and Ranging (LiDAR) systems and orthoimagery sensors will be used to gather the data necessary to create specified LiDAR-derived products and 6-inch resolution, 3-band, true color orthoimagery during the 2013-2014 leaf-off season.

The data will then be input into a hydrologic model and used to create a sediment transport model to demonstrate the fate and transport of sediment and trash in the Tijuana River Basin. These data will then be used to provide recommendations for the reduction and control of sediment in the basin.

This project will be conducted over the specified area located along the United States – Mexico International Boundary near San Diego, California and Tijuana, Baja California (fig. 1). The area of interest spans an estimated 200 square miles.

1.3 Quality Assurance and Quality Control

To ensure that the collected data and their associated deliverables are of high quality, an independent quality assurance and quality control (QA/QC) review will be solicited by the USIBWC. The selected LiDAR/Orthoimagery contractor will cooperate with the selected QA/QC contractor during the project’s phases. The responsibilities for both the LiDAR/Orthoimagery contractor and the QA/QC contractor are outlined in this statement of work.

2. DEFINITIONS

This section defines terms and phrases used in this SOW.

· The Fundamental Vertical Accuracy (FVA) is the accuracy value for points located in clear open, hard, and flat areas where there is a very high probability that the sensor will have detected the ground surface. FVA will be specified for a confidence level. For example, if the specified confidence level is 95%, then 95% of the bare-earth points must meet or exceed the specified accuracy level.

· The Supplemental Vertical Accuracy (SVA) is similar to the FVA, but it is for points located in land cover types other than open terrain. These values are calculated individually per land cover type.

· The Consolidated Vertical Accuracy (CVA) is similar to the FVA and CVA, but it is for all collected points in all land cover types.

3. Government-Furnished Property and Services

Piloting aircraft in Mexico will require applying for and obtaining the proper permit(s). USIBWC will assist the selected contractor by coordinating these efforts through MXIBWC.

With the exception of the previous paragraph, USIBWC will not furnish any equipment or any additional services to the contractor during the duration of the contract.

4. Contractor-Furnished Property and Services

Other than any exceptions listed in section 3 (Government-Furnished Property and Services), the selected contractor must furnish everything needed to perform this contract according to all its terms.

5. Specific Tasks and Specifications

Each subsection provides a breakdown of major phases of work, specifications, and deliverable for the LiDAR/Orthoimagery contractor, the QA/QC contractor, sediment transport model, and final report with recommendations.

5.1 LiDAR Tasks and Specifications

5.1.1 LiDAR Project Phases

Kick-Off Meeting

System calibration and geodetic control validation

Flight plan

Sensor calibration report(s)

Fly project area to collect data

Verify data after each flight mission

Collect checkpoint survey

Checkpoint table and survey report

Point classification

Intensity image production

Generate hydro-flattening breaklines

Hydro-flattening breaklines

Intensity images

Generate metadata

Metadata

Deliver whole QA/QC checkpoint table to IBWC

Submit final QA/QC report

Project Closeout Meeting

5.1.2 LiDAR Project Specifications

Phases I & II: Pre-Flight Planning and Data Acquisition

Project Requirements

GPS Procedures and Accuracy

Phases III & IV: Data Processing and Product Development

Fully Classified All-Return Point Cloud

ASPRS Classifications Required Class 1. Unclassified Class 2. Bare-earth Ground Class 3. Low Vegetation Class 4. Medium Vegetation Class 5. High Vegetation Class 6. Building Class 7. Low Point (noise) Class 9. Water Class 13. Bridges/Culverts

Bare Earth Lidar / DEM Raster

Hydro-flattening Breaklines

Intensity Images

Metadata

Spatial Reference Framework

File Naming Convention

Each image name and label should include the date* the image was captured.

*If a tile includes pixels from more than one flight strip, the date of capture should be the acquisition date of the majority of the tile’s pixels.

Applies to the following:

All-return point cloud in LAS Bare-earth DEM Intensity images Tile-level metadata

Orthoimagery provider shall consult with IBWC Contract Representatives to establish acceptable file naming conventions for all data products.

Example naming convention: “########_yyyymmdd”

######## = National grid number y = acquisition year m = acquisition month d = acquisition day

5.1.3 LiDAR Deliverables

Deliverables

Phase I Deliverables

Phase II Deliverables

Phase III Deliverables

Hydro-flattening breaklines

Intensity images

Phase IV Deliverables

Metadata

Intellectual Property Rights

The contracting agency shall have unrestricted rights to all delivered reports and data. The contracting agency expects to place reports and data in the public domain.

5.2 Orthoimagery Tasks and Specifications

5.2.1 Orthoimagery Project Phases

Kick-Off Meeting

System calibration and geodetic control validation

Flight plan for AOI including base station map

Sensor calibration report(s)

Fly project area to collect data

Verify data after each flight mission

Checkpoint table and survey report

QA raw image data and determine re-flights

Aerial triangulation

Initial radiometric adjustments

Final orthorectification

Generate & QA mosaics

Rework problem areas

Re-submit production samples as necessary

Image data w/provisional georeferencing

Data processing status updates

Create final compressed orthoimagery

Generate vector index per product

Generate metadata

Final compressed orthoimagery

Vector index per product

Data processing status updates

Project Closeout Meeting

5.2.2 Orthoimagery Project Specifications

Pre-Flight Planning and Data Acquisition

The digital system shall be a tested, stable (maintained), geometrically calibrated system with appropriate documentation, suitable for use in the acquisition and production of precision photogrammetric orthoimagery.

The contract administrator shall be notified of all camera malfunctions within 72 hours with a written report of the malfunction. A malfunction is defined as a failure in any element or process of the camera that causes an interruption of the normal operations of the camera system which includes any key components, such as camera mount, airborne global positioning system, inertial measurement unit, and on-board data storage.

Airborne examples:

· Leica geosystems ADS80 SH82 Sensor Head (or ADS40) – Pushbroom Camera

· Microsfot Vexcel’s UltraCamx – Frame Camera

· Intergraph’s Z/I Imaging Digital Mapping Camera (DMC) --- Frame Camera

The use of more than one type of digital camera in the acquisition of the same project area of interest is NOT allowed.

Imagery shall be collected between 10:00 a.m. and 2:00 p.m. to minimize shadows due to sun-angle.

In some situations, collection could begin at 9:00 a.m. to reduce the chances of cloud cover.

Ground features should be free of excessive waters due to rain and free of snow. Other environmental factors causing non-manmade obstruction of the ground surface should be minimal.

Light conditions should be such that images are free from smear, blur, excessive glare, or noise.

Maximum 45% Average 20-30% over entire flight line

Data Processing and Product Development

Misregistration between any bands shall not exceed 1 pixel.

Sharpness, and Noise – as a guideline, see target values in NAIP Suggested Best Practices- Final Report.

Histogram:

Clipping - Imagery shall have a tonal range that prevents the clipping of highlight or shadow detail.

Brightness - the mean pixel count shall be within +/- 7.5% of the middle DN value allowed for 8-bit data (min. 108, max. 147).

Images should not appear too dark or too bright and should not be faded or washed out.

Color balancing should be performed so that no color shift (one dominate color) exists within an image. Overall tonal quality should be rich – not dull with an acceptable level of contrast.

Image data shall be free of artifacts and blemishes that obscure ground feature detail. Feature ‘blooming’ or oversaturation should be minimal.

Shadows should not be too dark. Features in shadow should retain a maximum level of detail without compromising other components of the image.

The image data shall not contain any non-image items.

Sharpened imagery is preferred, however, processes that highly sharpen data should be avoided in order to maintain absolute accuracy.

Features should exhibit their true color in a natural color composite.

MrSID (tiles)

Orthoimagery provider shall consult with State Contract Representatives on all details for any file formats not specified in this document.

GeoTIFF – Uncompressed Required minimum TIFF and GeoTIFF Tags and GeoKeys:

· ImageWidth – “Example: 6720”

· ImageLength – “Example: 7620”

· BitsPerSample – “Example: 8,8,8,8”

· Compression – “Example: None or 1”

· PhotometricInterpretation – “Example: RGB or 2”

· Orientation – “Example: Top Left or 1”

· StripOffsets

· SamplesPerPixel – “Example: 3 or 4”

· RowsPerStrip – “Example: 1”

· StripByteCounts

· ExtraSamples* – “0” *Required only if SamplesPerPixel is >3.

See TIFF Revision 6.0

· GeoPixelScale aka ModelPixelScaleTag

· GeoTiePoints aka ModelTiepointTag

· GTModelTypeGeoKey – ModelTypeProjected

· GTRasterTypeGeoKey – RasterPixelIsArea

· ProjectedCSTypeGeoKey

· PCSCitationGeoKey – “A free text file for describing the projection and datum as <datum>/<projection>format. Example: NAD83 / UTM zone 15N”

· GTCitationGeoKey – “A free text file for describing the imagery. Use file name.”

· ProjLinearUnitsGeoKey – “A coded value for the linear units used by the projection. Values are listed in section 6.3.3.1 of the GeoTIFF 1.0 standard. Examples: Linear_Meter, Linear_Foot, Linear_Foot_US_Survey”

See GeoTIFF Format Specification, GeoTIFF Revision 1.0

MrSID – Compressed, 15:1 optimal ratio, generation 3

Orthoimage data must have quality compression (lossless or lossy) for achieving a visually lossless result and manageable file size.

Compression should be the last step in the image processing chain.

World files are only required if geographic coordinates are not stored within a ‘spatially aware’ orthoimage, such as GMLJP2 for JPEG2000 data.

[TRUE ORTHORECTIFICATION, ABSOLUTELY NO FEATURE LEAN]

The extents shall be computed by projecting the geographic corners and side midpoints to the appropriate projection, then adding the buffer on each side of the resulting minimum bounding rectangle.

*If a tile includes pixels from more than one flight strip, the date of capture should be the acquisition date of the majority of the tile’s pixels.

Orthoimagery provider shall consult with IBWC Contract Representatives to establish acceptable file naming conventions for all data products.

Example naming convention: “########_yyyymmdd”

######## = National grid number y = acquisition year m = acquisition month d = acquisition day

At a minimum, the indices should include date of capture and filename fields.

Metadata should include all processing steps and software used.

All image corrections should be well documented in the metadata.

Tested RMSE and CE both at 95% should be reported.

Additionally, these topics should be addressed in the metadata:

· Aircraft type and tail number

· Average flying/acquisition height (AGL)

· Camera manufacturer and model

· Camera calibration process

· Camera footprint description

· Raw capture pixel resolution and bit depth

· Final pixel resolution of product

· Total bands of data acquired and spectral ranges (μm)

· Use of ground control and/or GPS/IMU and associated internal validation or inspection processes

· DEM used and detail (e.g. date DEM obtained from NED, resolution, did it require repair, etc.)

· Quality control – Tests for accuracy

Spatial Reference Framework

The projection must be defined (readable in stakeholder software) for every uncompressed and compressed orthoimage raster file.

Accuracy

Orthoimagery should be free of color artifacts and missing data values. Images should be cloud free or <5% (includes shadows) per final image tile.

Orthoimagery should be free of smears and contain no warped features.ratio

Mis-registration among bands should be minimal and not exceed one (1) pixel.

The natural content of the orthoimagery should be maintained as close as possible barring any radiometric adjustments necessary for the orthophoto production process

5.2.3 Orthoimagery Deliverables

Deliverables

Phase I Deliverables

Phase II Deliverables

Phase III Deliverables

Phase IV Deliverables

Attributes:

ATTRIBUTE DATA ,COLUMN NAME, EXAMPLE

Image acquisition date, IDATE, 20120723 Polygon start date/time 1, SDATE, 20120723 13:52 Polygon end date/time 1 , EDATE, 20120723 13:53 Spectral resolution 2, SPEC, M4B Camera manufacturer, CAM_MAN, Leica Geosystems Camera model, CAM_MOD, ADS-80 Sensor or lens serial number, SENSNUM, 30029 Aircraft type 3 , AC_TYPE, C441 Aircraft tail number, ACTAILNUM, N12345R Average flying altitude (feet), ALT, 10,000

1 Local 24-hour clock. Start/end time is for the individual polygon and will be the same for frame-based systems.

2 Possible values: NC (natural color), CIR (color infrared), and M4B (4-band) 3 ICAO designator (e.g. use C441 for a Cessna 441 Conquest II)

Compressed mosaic(s)

Mosaic(s) shall be tone balanced to give a consistent and uniform image quality appearance that eliminates a checkerboard effect. The mosaic(s) should maintain as much of the original color and appearance of the color corrected tiles as practical.

The horizontal accuracy requirement will apply to the mosaic(s).

The file format will be MrSID (Generation 3).

File level metadata per final uncompressed and compressed image tile – FGDC-compliant

All orthoimage and associated data deliverables must meet specifications listed in this document. All image products are to be delivered to IBWC no later than [date.] [number of days after completion of acquisition.]

All final orthoimage products will be delivered on portable hard drives. Portable hard drives will become the property of IBWC. File compression such as ZIP or RAR should not be applied to the products; this requirement should not be confused with image compression (MrSID, etc.). Raw and/or preliminary products may be delivered via FTP.

Intellectual Property Rights

IBWC shall have unrestricted rights to all delivered reports and data. All orthoimage products will become the property of IBWC. All orthoimage products will be put in the public domain and be accessible from IBWC.

5.3 Independent Quality Assurance and Quality Control Review

5.3.1 LiDAR Quality Assurance and Quality Control Review

Quality Assurance and Quality Control

Checkpoint Acquisition

Land cover categories

· Open terrain (sand, rock, dirt, lawns, golf courses)

· Tall weeds and crops

· Brush lands and low trees

· Forested area fully covered by trees

· Urban areas with dense manmade structures

Checkpoint table

Deliverable 1: The surveyor will provide IBWC and the QA/QC team with all checkpoints collected including (at a minimum) UTM coordinates (X,Y,Z) to three (3) decimal places, point ID and land cover type. Point data must be in electronic format. Acceptable formats include: ASCII, .csv, .txt, .shp, .xls(x), .mdb

Checkpoint survey report

Deliverable 2: Along with checkpoint table, QA/QC contractor shall submit associated survey report including at a minimum selected GPS network (i.e. RTK) and spatial parameters (i.e. coordinate system, geoid model) as well as reference site photos. Acceptable formats include: .doc(x), .pdf, .odt

Lidar Accuracy Assessment

Project Review and Final Report

5.3.2 Orthoimagery Quality Assurance and Quality Control Review

This section is provided for coordination between the USIBWC independent contractor and this contract and not for proposal and bid.

Independent QA/QC Primary Review Tasks

· All data tiles can be read.

· All data tiles required for the QA review were delivered.

· Data format(s) is correct.

· All data filenames are correct and consistent, including extensions.

· All required ancillary data files are present, such as world files, .xml’s, etc.

· The ground sample distance is correct.

· The projection definition is present and correct.

· Bit depth is correct.

· Compression ratio is correct, if applicable.

· Image coverage is complete according to the project AOI, no data voids.

· Orthoimage tiles conform to the correct footprint and have acceptable image tile buffers.

· No missing bands.

· Orthoimage index present and acceptable.

· Tonal balance issues; too dark, too bright, too much contrast, too little contrast, not consistent with approved sample.

· Abnormal histograms, not normally distributed or excessively clipped.

· Shadows too dark.

· Features too bright or oversaturated causing excessive glare.

· Image artifacts and blemishes.

· Unacceptable compression artifacts.

· Inconsistent background or ‘no data’ values or background values that are within the AOI.

· Cloud and cloud shadow.

· Smears.

· Warped or wavy features.

· Feature lean, especially over roads, sidewalks, or parking lots.

· Band mis-registration.

· Obvious mosaic seam lines (not over water) or mismatched features.

If there is an overall consistent issue in the dataset, a select number may be flagged that represent the problem. Statements describing the issue in the dataset as a whole should be included in the report.

A horizontal accuracy assessment should be conducted using photo identifiable checkpoints.

None of the checkpoints may be used that were employed during orthoimage production.

Ideally, the checkpoints have a horizontal accuracy better than the orthoimage ground sample distance. The checkpoints must be collected by an entity other than the producer of the orthoimagery.

The checkpoints should be distributed fairly evenly throughout the orthoimage AOI.

Metadata should be checked for FGDC-compliance.

Deliverables

5.4 Development of a sediment transport model

5.4.1 Sediment Transport Model Project Phases

Kick-Off Meeting

Present selection and reasoning to USIBWC

Perform QC/QA on model outputs to insure accuracy

Prepare sediment transport results in graphical format

Model results and evaluation

5.5 Final Report

Final Report

Final Report

Present final report and results of all tasks to the IBWC

Sign in sheet and meeting minutes

5.6 Schedule of deliverables

Task Phase

Description

Date

5.1

LIDAR

I

Pre Flight

60 days after Notice to Proceed

II

Data Acquisition 60 days after 5.1 phase I

III

Data Processing

90 days after 5.1 Phase II

IV

Final Product 30 days after 5.1 Phase III

5.2

ORTHOIMAGERY

5.3

5.4

SEDIMENT TRANSPORT MODEL

5.5

FINAL REPORT

IBWC will provide comments 14 days after receipt of draft Final is due 14 days after receipt of comments

Total Contract schedule is 400 days after notice to proceed

6.0 Monthly Reporting

Progress reports are required on the first of each month detailing progress completion, completed work since last report, current work, any issues that could affect the project

7.0 Point of Contact Information

Contracting Officer (CO) Laura Baker

USIBWC

4171 N. Mesa, C-100 El Paso, TX 79902 Phone: (915) 832-4119

Laura.baker@ibwc.gov

Contracting Officer Representative (COR) Environmental Management Division

USIBWC

4171 N. Mesa, C-100 El Paso, TX 79902 Phone: TBD

TBD

image1.jpeg