CMP_SOW_V15_FINAL_-_08APR19_(2).pdf

Version 15

January 2019

SCOPE OF WORK FOR SHORELINE MAPPING

UNDER THE

NOAA COASTAL MAPPING PROGRAM

REMOTE SENSING DIVISION

NATIONAL GEODETIC SURVEY

NATIONAL OCEAN SERVICE

NATIONAL OCEANIC AND ATMOSPHERIC ADMINISTRATION

U.S. DEPARTMENT OF COMMERCE

CREDITS (CONTRIBUTORS):

Michael L. Aslaksen, Jr., Tim Blackford, Dan Callahan, Bob Clark, Ted Doyle, Wes Engelhardt, Mike Espey, Daniel Gillens, Steve Goodell, Doug Graham, Bill Hawken, Ryan Hippenstiel, David Jennings, Chris Kerns, Christine Livengood, Ruslan Marmalyukov, Steve Matula, Rupesh Pakai, Chris Sloan, Eric Smith, Gregory Stinner, Danielle Stuby, Mark Sweeney, Ivan Tauler, Kevin Bashant

SCOPE OF WORK

TABLE OF CONTENTS

1. INTRODUCTION

2. SCOPE

3. PROJECT PARAMETERS

3.1 PROJECT LIMITS

3.2 PRIORITY

3.3 ACCURACY

3.4 COMPLIANCE REQUIREMENTS

3.5 NATIONAL SPATIAL REFERENCE SYSTEM

3.6 REFERENCES AND GLOSSARIES

4. GOVERNMENT SUPPLIED INFORMATION AND MATERIALS

4.1 SCOPE OF WORK

4.2 PROJECT INSTRUCTIONS

4.3 (removed) …………………………………………………………

4.4 ELECTRONIC EXPOSURE DATA (VER.2) FILE CHECKING SOFTWARE

4.5 TIDAL SOFTWARE …

4.6 NGS AND NOS SURVEY MARKS

5. TECHNICAL AND COST PROPOSALS

5.1 TECHNICAL PROPOSAL

5.2 COST PROPOSAL

6. DATA ACQUISITION

6.1 REMOTELY SENSED DATA

6.2 GROUND CONTROL SURVEYS

6.3 TIDE/WATER LEVEL REQUIREMENTS........................................... …………… 17

7. DATA PROCESSING

7.1 GROUND PHOTO CONTROL SURVEYS

7.2 TIDE/WATER LEVELS

7.3 AEROTRIANGULATION

7.4 OTHER DATA……………………………………………………………………… 18

8. OFFICE DATA COLLECTION

8.1 GEOGRAPHIC CELL …………………………

8.2 COASTAL CARTOGRAPHIC OBJECT ATTRIBUTE SOURCE TABLE ………. 19

8.3 FILE NAMING CONVENTION

8.4 COMPILATION METHODOLOGY

8.5 FEATURE COMPILATION

8.6 DATA SUBMISSION……………………………………………………………… 21

9. QUALITY CONTROL AND FINAL PRODUCT PREPARATION

9.1 QUALITY CONTROL

9.2 FINAL SHAPEFILE PREPARATION

9.3 CHART EVALUATION FILE

9.4 PROJECT COMPLETION REPORT

10. DELIVERABLES

10.1 LABOR, EQUIPMENT, ETC

10.2 GOVERNMENT SUPPLIED ITEMS

10.3 WEEKLY STATUS REPORTS

10.4 GROUND PHOTO CONTROL DATA AND REPORT

10.5 GROUND CONTROL DATA AND REPORT …………………………………… 25

10.6 AERIAL PHOTOGRAPHY ASSOCIATED DELIVERABLES

10.7 AEROTRIANGULATION DATA & REPORT…………………………………... 25

10.8 FULL-RESOLUTION LIDAR SHORELINE INTERIM SHAPEFILE…………… 26

10.9 CHART ANNOTATIONS

10.10 PROJECT COMPLETION REPORT

10.11 GEOGRAPHIC CELL PILOT ……………………………………...………

10.12 GEOGRAPHIC CELL INTERIM FILES………………………………………… 26

10.13 GEOGRAPHIC CELL FINAL FILES……………………………………………. 26

10.14 TRANSMITTAL LETTER

10.15 TIDE STATION DATA……………………………………..…………………… 26

11. DELIVERY SCHEDULE

11.1 DATE

11.2 REQUESTS FOR MODIFICATION

11.3 MODIFICATIONS

12. POINTS OF CONTACT

13. SECURITY

13.1 INFORMATION TECHNOLOGY SECURITY…………………………………. 27

13.2 NOAA BUILDING SECURITY ……………………………………...………….. 27

14. PLACE OF PERFORMANCE …………………………………………………..…. 28

15. PERIOD OF PERFORMANCE …………………………………………………..… 28

ATTACHMENTS

A. (removed)

B. (removed)

C. (removed)

D. SHAPEFILE REQUIREMENTS

E. COASTAL CARTOGRAPHIC OBJECT ATTRIBUTE SOURCE TABLE [C-COAST]

F. C-COAST GLOSSARY

G. WEEKLY STATUS REPORT

H. ELECTRONIC EXPOSURE DATA FILE CHECKING PROGRAMS

I. AEROTRIANGULATION

J. TIDAL COORDINATION REQUIREMENTS

K. FEATURE COMPILATION

L. PROJECT COMPLETION REPORT

M. COASTAL MAPPING PROGRAM GLOSSARY

N. (removed)

O. GROUND PHOTO CONTROL

P. GROUND SURVEYS

Q. HORIZONTAL CONTROL FORMS

R. REQUIREMENTS FOR DIGITAL PHOTOGRAPHS OF SURVEY CONTROL

S. WRITING STATION DESCRIPTIONS AND RECOVERY NOTES

T. SETTING CONCRETE MARKS

U. SETTING A SURVEY DISK IN BEDROCK OR A STRUCTURE

V. SETTING AN NGS 3D MARK

W. STATION SITE SELECTION GUIDE

X. BENCH MARK TIES

Y. CMP LIDAR REQUIREMENTS

Z. DIGITAL AERIAL CAMERA USAGE AND DATA PROCESSING FOR THE CMP

AA. (removed)

AB. (removed)

AC. TRANSMITTAL LETTER SAMPLE

AD. (removed)

AE. CHART EVALUATION FILE

AF. SUN ANGLE NOMOGRAMS (AND SUN REFLECTIONS)

AG. MARK RECOVERY

AH. (removed)

AI. TASK ORDER MANAGEMENT AND INFORMATION SYSTEM (TOMIS)

AJ. AIRPORT AERIAL DIGITAL IMAGERY (No text. See Attachment Z.)

AK. REPORT OF GOVERNMENT PROPERTY IN POSSESSION OF CONTRACTOR

AL. ORTHOPHOTOGRAPHY

AM. GRAVITY FOR THE REDEFINITION OF THE AMERICAN VERTICAL DATUM

(GRAV-D) GOVERNMENT FURNISHED PROPERTY

AN. CONTINUOUSLY UPDATED SHORELINE PRODUCT (CUSP)

AO. ADDITIONAL REMOTE SENSING TECHNOLOGIES, SERVICES, AND

CAPABILITIES

Version 15

NATIONAL OCEAN SERVICE

1. INTRODUCTION

This Scope of Work (SOW) includes remote sensing, digital shoreline mapping, surveying, and associated tasks for the U.S. Department of Commerce, National Oceanic and Atmospheric

Administration (NOAA), National Ocean Service (NOS), National Geodetic Survey’s (NGS), Coastal Mapping Program (CMP) in support of NOAA’s Nautical Chart production. NOAA’s charting responsibilities date back to 1807 when President Thomas Jefferson founded the Survey of the Coast. Over the years the agency name has changed several times, but the enormous responsibility for producing accurate maps and charts of the nation’s entire shoreline has remained constant. The Nautical Chart has been called the most fundamental of navigation instruments making the chart’s accuracy and completeness essential for maritime safety. A

Nautical chart depicts water depths, shoreline, topographic features, navigational hazards, aids to navigation, landmarks, vertical (overhead) clearances and other navigational information. Vessel navigators use charts to determine their position, the location of their destination, and the safest and most economical route between these points. Charts used to be paper products, but are now widely available electronically. Contract personnel working on this contract must have a thorough understanding of Nautical charts as well as familiarity with the specific charts depicting the project area.

This SOW also supports data collection for NGS’ Aeronautical Survey Program (ASP), including remote sensing and ground surveys. Airport data is critical to the safety of aircraft in the National

Air Space and on the ground. In addition, this SOW supports data collection for NGS’ Gravity for the Redefinition of the American Vertical Datum (GRAV-D) program. Data from this SOW may also be used to support the Integrated Ocean Observing System (IOOS), the Integrated

Ocean and Coastal Mapping (IOCM) programs, and other NOAA programs.

2. SCOPE

Projects may include one or more phases of shoreline mapping or other surveying and mapping tasks including: planning; collecting remotely sensed data from ground, aircraft, and/or satellite based sensors, with positioning and orientation parameters; conducting ground geodetic surveys using conventional and/or precise Global Positioning System (GPS) methods; installing tide gauges and tidal bench marks, making tidal and leveling observations, and processing this data to determine tidal datums, predicted tide values, and actual tide values; performing

AeroTriangulation (AT); performing digital map compilation, with attribution; producing orthophotos; controlling quality, including equipment calibrations; processing data; and writing reports. Projects may also include: airport aerial photography, LIDAR or other remotely sensed data over airports, ground control surveys and obstruction surveys on airports, emergency response to disasters; and/or leveling, gravity surveys, and other special case surveying and mapping tasks. The remotely sensed data may include: LIDAR (see Attachments Y), imagery

(see Attachment Z), and/or gravity data. The Project Instructions will define any unique project specific requirements.

3. PROJECT PARAMETERS

3.1 PROJECT LIMITS – Coastal Mapping Program projects may be along any portion of the

U.S. shoreline including U.S. possessions in the Caribbean and the Pacific, and other areas of interest. ASP projects may be at any airports across the U.S. including U.S. possessions in the

Caribbean and the Pacific, and other areas of interest. Individual project limits will be defined in the Project Instructions and will be outlined on government provided diagrams (paper or digital) of the area. The CMP photo coverage is planned to include all of the shoreline within the project area and all of the land within 2000 feet of that shoreline and sufficiently seaward to include all offshore hazards to navigation (e.g. islands and rocks).

3.2 PRIORITY – Priority, if any, will be defined in the Project Instructions.

3.3 ACCURACY – For the CMP, general guidance on HORIZONTAL accuracy at a 95% confidence level for well defined points compiled in the Geographic Cell (GC) File is:

Harbors, ports, channels, etc. 1 meter, Approach areas to ports 3 meters, Open coastal areas 5 meters.

Airport survey specifications are contained in the latest versions of:

A. FAA Advisory Circular: General Guidance and Specifications for Aeronautical

Surveys: Establishment of Geodetic Control and Submission to the National Geodetic

Survey. AC No. 150/5300-16A, September 15, 2007 (AC-16A);

B. FAA Advisory Circular: General Guidance and Specifications for Aeronautical

Surveys: Airport Imagery Acquisition and Submission to the NGS, AC No. 150/5300-

17B, September 29, 2008 (AC-17B);

C. FAA Advisory Circular: General Guidance and Specifications for Aeronautical

Surveys to NGS; Field Data Collection and Geographic Information System Standards

AC No. 150/5300-18B, May 21, 2009 (AC-18B).

For specific requirements, see Project Instructions.

3.4 COMPLIANCE REQUIREMENTS –

A. PROJECT INSTRUCTIONS PRECEDENCE – The Project Instructions shall take precedence over this Scope of Work, since the Project Instructions provide detailed and often unique information about each project (e.g. project limits).

B. TERMS – The following conventions have been adopted for this document. The term

“shall” means that compliance is required. The term “should” implies that compliance is not required, but is strongly recommended.

C. MODIFICATION – Requests to exceed or deviate from this SOW or the Project

Instructions will be considered if written justification is provided in advance. No deviation is permitted until written approval is received from NOAA. All requests for modification to this SOW and/or the Project Instructions shall be submitted by the

Contractor in writing to the Contracting Officer prior to the due date on the Task Order and as soon as identified. Send a copy of the request to the NGS points of contact. If the

Contractor anticipates not meeting a required deadline, the Contractor shall request, in writing, an extension from the Contracting Officer. Provide a copy of the extension request to NGS. Extensions may be granted if extenuating circumstances that prevent on-time completion exist.

D. UNUSUAL CIRCUMSTANCES – The Contractor shall also notify NGS immediately of any unusual circumstances that occur during the performance under this SOW which might affect the Deliverables or their quality, and especially of any deviation from this

SOW and/or the Project Instructions.

E. ORIGINAL DATA – Observation logs and other records generated during this project are legal records which will be archived by the government. It is very important that these logs be original, legible, neat, clear, and fully completed in indelible black ink. Original data shall be saved, unmodified, whether in hand written or computer recorded form, and shall be marked “ORIGINAL DATA”. In the original records (paper or digital), nothing is ever erased or obliterated. All available spaces on the recording forms should be completed. If a space on a form does not apply, then enter “N.A.” for “Not Applicable”.

If a mistake is made on a form, draw a single line through the mistake and write the correction above or to the side. If space is too limited to permit a field correction, restart with a new log sheet, however, the form should not be recopied in the office in order to make a “clean” copy. An explanatory note shall be made, and initialed for all corrections to the original recorded figures. It is essential that all recorded figures be neat and legible.

All editing of computer recorded data shall be done on a copy of the original. Always submit the original version of the data, not a handmade copy nor a photocopy nor a digital copy.

F. DATA BACKUP – The Contractor shall back up all data and take steps necessary to ensure the safety of all data, especially original, raw data. The Contractor shall save all data back-ups for six months after NGS has accepted all data for that Task Order. The

Contractor shall sanitize all equipment following NIST Special Publications 800-88

Guidelines for Media Sanitization, http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIS.SP.800-88r1.pdf, that stored data utilized during this project.

G. GOVERNMENTAL RULES AND REGULATIONS – The Contractor shall ensure that they comply with applicable regulations of government agencies, including the:

• Federal Aviation Administration (FAA), https://www.faa.gov/regulations_policies/

• US Coast Guard (USCG), https://www.navcen.uscg.gov/?pageName=navRuleChanges

• Environmental Protection Agency (EPA), https://www.epa.gov/laws-regulations

• Occupation Safety & Health Admin. (OSHA), https://www.osha.gov/html/compliance.html

• National Park Service (NPS), https://www.nps.gov/aboutus/lawsandpolicies.htm

• Homeland Security, https://www.dhs.gov/

• Surface Transportation Board, https://www.stb.gov/stb/index.html and other federal, tribal, state, commonwealth, and local governmental rules and regulations. The Contractor shall be responsible for identifying, obtaining, completing, and submitting required applications or forms; and for obtaining approval of all necessary permits for work performed under this contract.

H. CYBER SECURITY AND QUALITY ASSURANCE CONTROLS See section 13

Security

3.5 NATIONAL SPATIAL REFERENCE SYSTEM (NSRS) – All surveying, positioning, and mapping shall be tied to the NSRS. See:

http://www.ngs.noaa.gov/INFO/OnePagers/One-Pager_NSRS.pdf

A. HORIZONTAL CONTROL – North American Datum 1983 (NAD 83, 2011), Epoch

2010.

B. VERTICAL REFERENCE –

i. North American Vertical Datum 1988 (NAVD 88).

ii. Alaska and other areas outside the continental U.S., see SOW Main Text, Section 6.2.

iii. or other local datum if required by the Project Instructions.

C. TIDAL SHORELINE REFERENCE –

http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIS.SP.800-88r1.pdf https://www.faa.gov/regulations_policies/ https://www.faa.gov/regulations_policies/ https://www.navcen.uscg.gov/?pageName=navRuleChanges https://www.epa.gov/laws-regulations https://www.epa.gov/laws-regulations https://www.epa.gov/laws-regulations https://www.osha.gov/html/compliance.html https://www.osha.gov/html/compliance.html https://www.nps.gov/aboutus/lawsandpolicies.htm https://www.dhs.gov/ https://www.stb.gov/stb/index.html http://www.ngs.noaa.gov/INFO/OnePagers/One-Pager_NSRS.pdf

i. MEAN LOWER LOW WATER (MLLW)

ii. MEAN HIGH WATER (MHW)

D. GEOID MODEL – Use the most recent NGS model, currently GEOID12B, see:

http://www.ngs.noaa.gov/GEOID/ . For projects in Alaska and other areas outside the conterminous 48 states, see the Project Instructions for any special requirements.

E. NATIONAL SPATIAL REFERENCE SYSTEM (NSRS) – All positioning shall be tied to the NSRS. See https://www.ngs.noaa.gov/INFO/OnePagers/NSRSOnePager.pdf

The contractor shall record all processing steps and software used including version number;

The contractor shall use either the rapid or precise IGS orbit ephemeris for GPS processing.

3.6 REFERENCES AND GLOSSARIES –

A. NOAA’s Nautical Charts, Main Page – https://nauticalcharts.noaa.gov/

B. U.S. Chart No. 1 (Chart symbols, abbreviations, and terms) at:

https://nauticalcharts.noaa.gov/publications/us-chart-1.html

C. Dates of Latest Editions of Charts: http://www.charts.noaa.gov/RNCs/RNCsIndv.shtml

D. NOAA Chart Catalog and Chart Viewer – View and download and of NOAA’s 1,000+ nautical charts: https://nauticalcharts.noaa.gov/charts/noaa-raster-charts.html

E. NOAA Online RNC® Viewer – Seamless online viewer for NOAA RNCs:

http://www.nauticalcharts.noaa.gov/mcd/OnLineViewer.html

F. NOAA Center for Operational Oceanographic Products and Services (CO-OPS) web

Site: http://tidesandcurrents.noaa.gov/

G. NOAA NGS web Site: http://www.ngs.noaa.gov/

H. U.S. Coast Guard Light List: http://www.navcen.uscg.gov/?pageName=lightLists

I. See Glossaries in Attachments F and M.

J. Manual Of Photogrammetry, Sixth Edition, 2013.

K. Manual of Color Aerial Photography, First Edition, 1968.

L. Water Level Station Specifications and Deliverables for Shoreline Mapping Projects, May 2009, at:

https://tidesandcurrents.noaa.gov/publications/Water_Level_Station_Specifications_and_

Deliverables_for_Shoreline_Mapping_Projects,_Updated_May_2009.pdf http://www.ngs.noaa.gov/GEOID/ https://www.ngs.noaa.gov/INFO/OnePagers/NSRSOnePager.pdf https://nauticalcharts.noaa.gov/ https://nauticalcharts.noaa.gov/publications/us-chart-1.html http://www.charts.noaa.gov/RNCs/RNCsIndv.shtml https://nauticalcharts.noaa.gov/charts/noaa-raster-charts.html http://www.nauticalcharts.noaa.gov/mcd/OnLineViewer.html http://tidesandcurrents.noaa.gov/ http://www.ngs.noaa.gov/ http://www.navcen.uscg.gov/?pageName=lightLists https://tidesandcurrents.noaa.gov/publications/Water_Level_Station_Specifications_and_Deliverables_for_Shoreline_Mapping_Projects%2C_Updated_May_2009.pdf https://tidesandcurrents.noaa.gov/publications/Water_Level_Station_Specifications_and_Deliverables_for_Shoreline_Mapping_Projects%2C_Updated_May_2009.pdf https://tidesandcurrents.noaa.gov/publications/Water_Level_Station_Specifications_and_Deliverables_for_Shoreline_Mapping_Projects%2C_Updated_May_2009.pdf

M. Hydrographic Specifications and Deliverables (see Chapter 4 in particular; the primary CO-OPS reference for shoreline mapping):

https://www.nauticalcharts.noaa.gov/publications/docs/standards-and-requirements/specs/hssd-2017.pdf

4. GOVERNMENT SUPPLIED INFORMATION AND MATERIALS

4.1 SOW, WITH ATTACHMENTS (this document).

4.2 PROJECT INSTRUCTIONS – Project Instructions are a separate document providing specific project information, containing any unique project requirements, and may contain any or all of the following information:

A. PROJECT DIAGRAMS – Diagrams (paper or digital) with the project limits marked by NGS. These Diagram(s) of the project area show the shoreline to be compiled;

compilation limits, if different from the 2000 foot requirement; and, as required, limits of tide coordination areas (if different from compilation limits);

B. TIDAL ZONING DIAGRAM;

C. TIDAL ZONING MEMO;

D. FLIGHT LINE MAP (CMP and/or ASP);

E. WAYPOINT FILE (CMP and/or ASP);

F. ADDITIONAL INSTRUCTIONS – Instructions regarding tidal coordination, ground control, Gravity for the Redefinition of the American Vertical Datum (GRAV-D), and any other project specific requirements;

G. PROJECT IDENTIFIER – The “Project Identifier,” an eleven or twelve character alpha-numeric Identifier (ID) unique to each project (i.e. FL1701A-CM-N);

H. AIRPORT MAPS for Aeronautical Survey Program.

4.3 (removed)

4.4 ELECTRONIC EXPOSURE DATA (VER. 2) FILE CHECKING SOFTWARE – For all contracted aerial imagery acquisitions, the Contractor shall check every Electronic Exposure Data

Version 2 (EED2) file with the government supplied software prior to submitting each EED2 file to NGS. The software first checks the EED2 file for proper formatting and valid field entries.

The software then computes and displays the aerial photography footprints, enabling reviewers to immediately see positioning, spacing, and/or orientation problems. See Attachment H for documentation on this software as well as the EED2 file format.

https://www.nauticalcharts.noaa.gov/publications/docs/standards-and-requirements/specs/hssd-2017.pdf https://www.nauticalcharts.noaa.gov/publications/docs/standards-and-requirements/specs/hssd-2017.pdf https://www.nauticalcharts.noaa.gov/publications/docs/standards-and-requirements/specs/hssd-2017.pdf

4.5 TIDAL SOFTWARE – The contractor may use any software, commercial or proprietary, to calculate the times wherein the tides in the project area are at the appropriate height to acquire tide coordinated imagery. The only restriction on the use of contractor supplied software for this purpose is that the times calculated by such software must coincide with the times calculated by the Government's in-house tide window prediction software. The

Government will, at the contractor's request, provide the most current version of the software that the Remote Sensing Division (RSD) uses, and is able to freely distribute, to predict such tide windows. The Government will, at the contractor's request, provide training in the use of the RSD program. Such training will be at a time and place mutually convenient to both the contractor and the Government. See Attachment J for an explanation of tides and tide windows.

4.6 NGS AND NOS SURVEY MARKS – If required and when requested by the Contractor, NGS brass survey disks and/or NGS aluminum logo caps will be supplied to mark horizontal and/or vertical geodetic survey points. If required and when requested by the Contractor, NOS brass survey disks and/or NOS aluminum logo caps will be supplied for use as tidal bench marks.

The Contractor shall acknowledge receipt of Government Supplied Items by inventorying the shipment, signing the Transmittal Letter (TL), and faxing the TL to NGS. At this time

Contractors cannot use the Task Order Management and Information System (TOMIS) to acknowledge receipt of Government Supplied Items sent by the Government.

5. TECHNICAL AND COST PROPOSALS

5.1 TECHNICAL PROPOSAL –

A. TECHNICAL – After receiving and reviewing the Project Instructions, the Contractor shall submit a Technical Proposal summarizing their proposed implementation plan. This report shall include at least the following:

i. Contractor planned flight lines with a nautical chart background, if required (see

Project Instructions),

ii. proposed ground control methods and locations (using different symbols for:

Continuously Operating Reference Stations (CORS), new survey control, old survey control, photo control, and airborne Kinematic Global Positioning System

(KGPS) Ground Base Stations, if required).

iii. proposed tide/water level stations, if required,

iv. proposed approximate date range of imagery acquisition,

v. summary of all field and office data collection,

vi. data processing (methods, equipment, hardware, software,

vii. personnel.

B. QUALITY CONTROL PLAN – The Contractor shall have the responsibility for the overall quality of the Project. The Contractor’s Final Reviewer and other Contractor personnel, as required, shall become intimately familiar with the Project Instructions, the

SOW, the SOW Attachments, and References. The Contractor shall submit a written

Quality Control Plan (QCP) prior to beginning work (as part of their Technical Proposal), to include at least the following:

i. checking manually recorded data,

ii. checking data manually entered into a computer system,

iii. checking data at various points in the overall process,

iv. reviewing the compilation data on-line (see Attachment K),

v. comparing the compilation data with the largest scale Nautical charts of the same area,

vi. comparing compilation data with the aerial photographs of the same area,

vii. checking all documents and reports submitted.

The Plan shall include both Quality Control (QC) and Quality Assurance (QA), as defined in Attachment M - Coastal Mapping Program Glossary.

The Contractor shall also describe how data will be backed up and how it will be ensured that original data are not modified. See Section 10, Deliverables.

C. TOMIS SPREADSHEET – The Contractor shall submit a completed TOMIS spreadsheet containing a listing of all Deliverables, percents, and due dates, and in the specified format. See Attachment AI.

5.2 COST PROPOSAL – The Contractor shall submit a proposal with the costs broken down into at least the following categories, for all work required by the Project Instructions:

A. MISSION PLANNING,

B. GPS SURVEY PLANNING,

C. GROUND AND PHOTO CONTROL,

D. TIDES AND WATER LEVELS,

E. AERIAL DATA ACQUISITION (IMAGERY, LIDAR, ETC.),

F. DATA PROCESSING,

G. AEROTRIANGULATION,

H. COMPILATION,

I. FINAL PRODUCT PREPARATION.

Include number of labor hours, labor costs, and non-labor costs for each category.

6. DATA ACQUISITION

6.1 REMOTELY SENSED DATA –

A. AERIAL PHOTOGRAPHY – The Contractor may be required to acquire aerial photography. Aerial photography for the CMP is usually required to meet three main parameters: sun angle of at least 25 degrees, clear sky, and tide coordination. See information below and in Attachments: Z, J, and AF.

i. Flight Line Planning – The Project Instructions may require the Contractor to plan flight lines or may state that NGS has planned the lines.

- Contractor Planned Flight Lines – The Contractor may be required to plan the flight lines given the project area and other information contained in the

Project Instructions. Flight line maps shall be depicted with a NOAA nautical chart as the background. The photo coverage shall be planned to include all of the shoreline within the project area, all of the land within

2000 feet of that shoreline, and offshore features such as islands, rocks, man-made obstructions, fixed aids to navigation, piers, and jetties. See

Attachment Z for additional requirements.

- Government Planned Flight Lines – If NGS plans the flight lines, NGS will supply flight line maps and waypoint files in standard NGS format (see

Attachment Z for format). The Contractor shall review these flight lines to ensure adequate coverage as defined in the paragraph immediately above, and immediately notify NGS of any problems.

ii. Exposure Test and Production – The Contractor shall conduct and submit an exposure test over an area similar to the project area for each type of emulsion and each camera system to be used. After NGS review and approval of the exposure test, the Contractor may begin production photography; see Attachment Z. The

Electronic Exposure Data (EED) file shall be sent to NGS within 3 working days via email. The Contractor shall check all manual data entries. See Attachment Z for complete details. Note, the Project Instructions will state if new exposure tests are required for future Task Orders. Normally an unaltered camera system that has already had an Exposure Test in a similar geographic area will not require a newExposure Test.

iii. Tide Coordination – The Project Instructions may require that imagery for the

CMP be tide coordinated. When shoreline data is to be compiled using aerial photographs, RGB (Color), Color Infra-Red (Color IR), and/or Black-and-White

IR (B&W IR) images may be required to be captured when the water level is at observed or predicted MHW, observed or predicted MLLW, and/or below or between these water levels. Normally NGS allows a tolerance on either side of

MHW and MLLW, see Attachments Z and J. See the Project Instructions for detailed project information.

iv. Airborne Positioning and Orientation – All remotely sensed imagery (including color and infrared) for the CMP shall be positioned using airborne Kinematic GPS

(KGPS) (with dual-frequency, carrier-phase measurements). Airborne KGPS is normally not required for airport photography.

v. Camera Ports – An aircraft with dual camera ports may be required for CMP projects so that two sensors can collect data simultaneously.

B. OTHER REMOTELY SENSED DATA – The Project Instructions may include requirements for any photographic systems and/or remote or local sensors that convert energy from the electromagnetic spectrum into analog or digital data obtained from any ground, airborne, or space borne satellite platform. Also gravity data may be required.

See Project Instructions for specific requirements.

C. PROPERTY OF DATA - All original data, from the instant of acquisition, and other deliverables required through this contract including final data, are and shall remain the property of the United States Government. This includes data collection outside the project area. These items include the contractor-furnished materials.

6.2 GROUND CONTROL SURVEYS –

A. CHECK POINTS – For CMP projects under this SOW, at least four Check Points are required. These points shall have horizontal and vertical positions. In Alaska and other areas outside the continental United States where NAVD 88 bench marks are not available, the Contractor may be required to make GPS ties to existing tidal bench marks.

Additional information may be supplied in the Project Instructions. The Check Points shall be approximately evenly spaced in the project area and shall be positioned using specifications listed below. On large projects, use at least one Check Point for every four strips, and at least one near each corner of a block. These four or more points shall not be used in the aerotriangulation computations, but rather serve as an independent check of the photogrammetric solution. The Contractor shall hold these back until the aerotriangulation is complete. The Contractor shall compare the ground positions of the

Check Points to the results derived from the aerotriangulation solution and shall report these results to NGS in table form in the Aerotriangulation Report.

For ASP projects, Check Points are usually not required.

B. PHOTO CONTROL POINTS – For CMP projects, the Contractor may propose additional ground control points, these to be used in the aerotriangulation. These points are called “Photo Control Points” to distinguish them from the “Check Points” described above. The Contractor shall determine an adequate number and distribution of these Photo

Control Points. A description of the plan and the number, type and spacing of these points shall be included in the Technical Proposal. Contractors should use CORS and Online Positioning User

Service (OPUS), including OPUS Rapid-Static (OPUS-RS), to position both types of photo ground control. Any updates in this SOW’s OPUS requirements will be included in the Project

Instructions. See Attachment O for ground photo control requirements.

If Photo Control Points are required for ASP projects, they will be specified in the Project

Instructions.

C. GROUND SURVEYS – See Attachment P for requirements for Ground Control

Extension Surveys (marks used to position other marks). In most CMP cases, this type of point should not be required.

D. AIRBORNE KGPS BASE STATIONS – GPS Base Stations are required to control airborne data collections. The Contractor shall use existing CORS, and/or use existing

NSRS control points, and/or establish new ground control points, in that order of priority.

See Attachment Z for details.

E. OTHER CHECK POINTS – Check Points for other types of sensors will be specified in the Project Instructions.

F. GENERAL – Additional survey related requirements may include: recovering survey marks, setting marks, constructing photo panels, photo identifying control points, writing digital mark descriptions and/or mark recovery notes, using conventional and/or GPS survey methods, including leveling, taking digital photographs during the ground surveys, and preparing: visibility diagrams, GPS observation logs, station sketches, and reports.

Detailed specifications for ground control surveys, including recommended forms, formats, and procedures are contained in Attachments O, P, Q, R, S, T, U, V, W, X, AG, and AJ.

G. GROUND SURVEYS AT AIRPORTS – The Contractor may be required to perform ground surveys at airports including: runways, air navigation aids, aircraft obstructions, and other related surveys.

H. GROUND TRUTH FOR REMOTE SENSING – Ground truth for various ground, airborne or space sensors may be required.

6.3 TIDE/WATER LEVEL REQUIREMENTS – See the CO-OPS reference listed in

Section 3.6M, above. When required, additional specifications for predicting water levels, observing water levels in real time, installing water level gauges and tidal bench marks, collecting water level data, leveling between bench marks, GPS observations on tidal bench marks, or processing all these observations will be included in the Project Instructions. Data shall be submitted in CO-OPS and NGS specified formats. In any cases where the requirements conflict or would cause duplicate effort, consult Attachment AH and then contact NGS for clarification.

See Attachment J for information on tidal acquisition windows and Attachments: Z and P for other requirements. For additional information on tides and water levels, see the CO-OPS site at:

http://tidesandcurrents.noaa.gov/ . In particular, the following pages/links may be helpful:

“Our Restless Tides” – https://tidesandcurrents.noaa.gov/restles1.html

“Fantastic Tidal Datums” – https://tidesandcurrents.noaa.gov/publications/fantastic_tidal_datums.pdf

“Understanding Tides” – http://tidesandcurrents.noaa.gov/publications/Understanding_Tides_by_Steacy_finalFINA

L11_30.pdf

Note, predicted tides may not be accurate in time or height. The following is from the CO-OPS

Frequently Asked Questions section on the CO-OPS WWW site.

“Q: How accurate are the predictions?

“The accuracy of the tide predictions is different for each location. Periodically we do a comparison of the predicted tides vs. the observed tides for a calendar year. The information generated is compiled in a Tide Prediction Accuracy Table. We work to insure that the predictions are as accurate as possible. However, we can only predict the astronomical tides we cannot predict the effect that wind, rain, freshwater runoff, and other short-term meteorological events will have on the observed tides.

“In general, predictions for stations along the outer coast are more accurate than those for stations farther inland; along a river, or in a bay or other estuary. Inland stations tend to have a stronger non-tidal influence; that is, they are more susceptible to the effects of wind and other meteorological effects than stations along the outer coast. An example of an inland station which is difficult to predict is Baltimore, Maryland. This station is located at the northern end of

Chesapeake Bay. Winds which blow along the length of the bay have been known to cause water levels to be 1-2 feet above or below the predicted tides.

“Stations in relatively shallow water, or with a small tidal range, are also highly susceptible to meteorological effects and thus difficult to accurately predict. At these stations, short-term weather events can completely mask the astronomical tides. Many of the stations along the western Gulf of Mexico fall into this category. An example is Galveston, Texas. This station is in a bay which is relatively shallow and has a small opening to the sea. At this station it is possible for meteorological events to delay or accelerate the arrival of the predicted tides by an hour or more.”

7. DATA PROCESSING

http://tidesandcurrents.noaa.gov/ https://tidesandcurrents.noaa.gov/restles1.html https://tidesandcurrents.noaa.gov/publications/fantastic_tidal_datums.pdf http://tidesandcurrents.noaa.gov/publications/Understanding_Tides_by_Steacy_finalFINAL11_30.pdf http://tidesandcurrents.noaa.gov/publications/Understanding_Tides_by_Steacy_finalFINAL11_30.pdf

7.1 GROUND PHOTO CONTROL SURVEYS – Data shall be processed with NGS approved software and submitted in required formats. A final report is required. Specifications for ground photo control survey data processing and reports are in Attachment O. Requirements for positioning the GPS Base Station for the ground GPS receiver for the airborne KGPS are found in

Attachment Z.

7.2 TIDE/WATER LEVELS – When required by the Project Instructions, tide/water level data shall be processed in accordance with the CO-OPS reference in Section 3.6.M, above, its references, and Attachment J.

7.3 AEROTRIANGULATION – For CMP projects, the Contractor is required to perform the standard processes of aerotriangulation (AT) for all photographs (including color and IR) used in the shoreline mapping project. All imagery (color and IR) for an entire project shall be included in the same AT solution. The Contractor shall include in the project Technical Proposal a plan explaining how the AT work will be performed. Upon completion of the AT, the Contractor shall provide a written report which includes the listed requirements as found in Attachment I. See also requirements regarding Check Points in Section 6.2A above.

Aerotriangulation may be required for ASP projects.

7.4 OTHER DATA – Other types of data shall be processed according to standard industry procedures and any additional requirements as specified in the Project Instructions.

8. OFFICE DATA COLLECTION

8.1 GEOGRAPHIC CELL (GC) – The GC is set of digital files, containing the geometry and attribution of the features extracted from imagery or other remotely sensed source data. The original compilation data will necessarily be in whatever file format is used by the Contractor’s digital mapping system, but the data submitted to the government shall be in Esri® shapefile format as defined in Attachment D. The Contractor shall supply two sets of cartographic feature files, the first being for the NGS quality assurance process (interim files) and the second as the final Deliverable product to NGS. The Interim Shapefiles use an attribution schema that can be imported into NGS's digital photogrammetric softcopy workstations for stereoscopic review purposes.

8.2 COASTAL CARTOGRAPHIC OBJECT ATTRIBUTE SOURCE TABLE – The final product shapefiles use the NGS’s “Coastal Cartographic Object Attribute Source Table”

(C-COAST) attribution schema which is listed in Attachment E. There is a one-to-one translation from the interim to C-COAST attribution. The C-COAST attribution scheme was developed to conform the attribution of various sources of shoreline data into one attribution catalog.

C-COAST is not a recognized standard, but was influenced by the International Hydrographic

Organization’s S-57 Object-Attribute Standard so the data would be more accurately translated into S-57. The glossary for the C-COAST feature attribute description is in Attachment F.

The shapefile attributes and attribute values are case sensitive. All shapefile attribute labels shall be upper case. See Attachment D for Interim and Final Shapefile attribute requirements, including character and case sensitivity. General cartographic feature definitions within the CMP are included in a second Glossary in Attachment M.

8.3 FILE NAMING CONVENTION –

A. GENERAL – The Contractor shall clearly label file names on all submitted media.

All data submitted shall be labeled with a systematic naming convention. All label and file naming conventions shall be documented and explained with each data submission. All original data shall be marked “ORIGINAL” on the data medium.

B. IMAGE NAMING CONVENTION – All contractor acquired imagery shall follow a

STRIP_FRAME image naming convention as follows: 130001_00001

The STRIP (prefix) is a 6-digit designator, where:

Digit 1 holds Data Type as defined:

1 = color/non-tide coordinated

2 = IR/MHW

3 = IR/MLLW

4 = IR/non-tide coordinated

5 = color/MHW

6 = color/MLLW

7 = multispectral/MHW

8 = multispectral/MLLW

9 = multispectral/non-tide coordinated

Digits 2-3 hold Image Scale (flying hgt / focal len)

Digits 4-6 hold the unique Strip #.

Note that any tide stage other than MHW or MLLW is considered non-tide coordinated for this purpose.

The FRAME (suffix) uses the remaining 5-digits and holds the frame #, which shall be unique within each strip, ensuring each frame will be uniquely named within a project.

C. SHAPEFILES – The Contractor shall request GC file names from NGS via email.

NGS will normally respond within five working days of the request.

The Interim Shapefiles, including pilot areas, should be named for the GC identifier that corresponds to a given subdivided region. The Interim Shapefile that was subdivided should be named in the following manner: GCxxxxx where “xxxxx” is a sequential number assigned by NGS.

This final deliverable shapefile shall have the prefix name of the project identifier as defined in the Project Instructions.

The final deliverable shapefile's SOURCE_ID attribute value is the corresponding GC identifier.

8.4 COMPILATION METHODOLOGY – Unless specifically directed, Contractors shall compile all aerial photographic data using stereo models in a digital photogrammetric system that meets the accuracy requirements set forth in this SOW and that produces data in a format(s) compatible with SOCET SET® software (latest version released). Compile within the limits of the stereoscopic neat model. See Attachment K.

8.5 FEATURE COMPILATION –

A. VECTOR COLLECTION INTERVAL AND ACCURACY – As a line of natural shoreline is digitized, the Contractor shall measure vertices frequently enough to ensure that the agreement between the digital shoreline and the shoreline visible on the mapping imagery is equal or better than the allowed discrete point accuracy, for 95% of points along the digital shoreline. Manual point-to-point mode of compilation should be used for all feature extraction, particularly when collecting well-defined points such as corners of a pier or wharf. If stream mode is used, parameters should be carefully set in order to avoid unnecessarily large file sizes. See Attachment K.

B. DISCRETE POINTS – Many well-defined point features, such as landmarks, fixed aids to navigation, and small rocks, serve as check points and supplemental control for various remotely sensed images. The cartographer should exercise extreme care in the measurement of well-defined discrete points. See Attachment K.

C. LINEAR FEATURES CONNECTIVITY – Collected linear data shall be topologically cleaned by removing all erroneous dangles and gaps, caused by inadequate snapping, so that linear features are continuous. Other important general topological considerations include:

i. Line features that cross other line features shall not be split into multiple features where they cross (e.g. overhead cable crossing a shoreline).

ii. Line features must never cross over themselves.

iii. All individual line features compiled to form closed polygons must begin and end precisely at the same node (w/no dangles or gaps).

iv. Multiple instances of a feature with the same attribution occupying the same geographic space (duplicate features) are never allowed in final line and point shapefiles or Chart Evaluation File (CEF).

v. Short (tiny) line features must not be created solely for the purpose of establishing topological connectivity. In general, line features < 0.5 mm at the compilation scale should not be compiled except in specific circumstances (see

Attachment K).

D. COMPILATION LIMITS – In all project areas, the features to be compiled include:

the shoreline; hazards to navigation in the water (rocks, islands, etc.), physical and cultural features visible from the water and thus of value to the mariner; and other significant features on the land for a distance inland of 2000 feet from the shoreline. All landmarks meeting requirements and within the photo coverage, shall be compiled. See

Attachment K.

E. COMPILATION CONTENTS AND LEVEL OF DETAIL – Contents and level of detail are closely related to compilation scale (see Attachment K). In general provide at least the same level of detail as depicted on the largest scale nautical chart(s) of the project area. Additional detail may be required on and along land areas facing navigational channels (those waterways with Aids To Navigation).

Significant types of features include, but are not limited to: shoreline; fixed aids to navigation; landmarks; major roads; major buildings; railroads; canals; bridges; tanks

(other than landmarks); pipelines; and power lines. See Attachment K.

F. SUBPROJECTS – CMP projects are often quite large and complex, and are therefore typically divided into subprojects to more readily facilitate application of the resulting data products to NOAA’s Nautical Chart suite. The Government will, in almost every case, create the subproject boundaries and assign project names based on the geographic extents.

8.6 DATA SUBMISSION –

A. PILOT AREA – The contractor shall select a Pilot Area and submit this proposed Area as part of their Technical Proposal. This Pilot Area, constituting approximately 10% of a single subproject (assuming the project is subdivided), should contain a representative sample of shoreline and associated features contained in the project as a whole. Once the

Technical Proposal is accepted and the notice to proceed has been received, the Contractor shall compile this area and submit Interim Shapefiles (see Attachment D) covering the

Pilot Area. The Contractor shall not begin compilation on other portions of the project until NGS approves the Pilot Area compilation. The purpose of the Pilot Area is to ensure the Contractor’s understanding of compilation requirements and thereby mitigate the risk of lengthy correction and resubmission cycles.

B. INTERIM SHAPEFILES – After the initial Pilot Area compilation is approved by

NGS, the Contractor shall proceed with compilation of the remaining portion of the subproject in which the Pilot Area is contained. Upon completion of Quality Control

(QC) tasks the Contractor shall deliver Interim Shapefiles for Government review when the subproject is 100% complete. Remaining subprojects should be submitted thereafter, one area at a time.

C. FINAL SHAPEFILES – See Section 9.2 below.

9. QUALITY CONTROL AND FINAL PRODUCT PREPARATION

9.1 QUALITY CONTROL – The Contractor shall conduct Quality Control (QC) of all the work performed and all Deliverables produced in accordance with the Contractor’s Quality Control

Plan, submitted with the Technical Proposal and approved by NGS. The Contractor shall check all data to ensure completeness, reliability, and accuracy. Project specific accuracy requirements may be given in the Project Instructions. The Contractor’s personnel shall be thoroughly familiar with the SOW; the Project Instructions; the definitions of terms; and material covered in the other references and publications as required. See Section 3.6 for a list of References.

The Contractor shall conduct a thorough quality review of feature compilation prior to submitting all compilation Deliverables to ensure accuracy of delineation, correct feature attribution, completeness, and adherence to all project requirements (see Attachment K). A summary of

QC/QA work performed shall be included in the Final Review section of the Project Completion

Report (see Attachment L).

9.2 FINAL SHAPEFILE PREPARATION – After the Interim Shapefiles have been reviewed and accepted by NGS, the Final Shapefiles (Attachment D) shall be prepared and submitted. The preparation of the Final Shapefiles typically consists of merging the multiple Interim Shapefiles into a single point shapefile and a single line shapefile; changing the coordinate system;

implementing final attribution; topologically cleaning the files of stray dangles and gaps; etc. The actual data processing steps required for a project will depend on the particular systems, software, and methodology used by the Contractor, and may differ from the procedures listed here.

9.3 CHART EVALUATION FILE – The Chart Evaluation File (CEF) is a polygon shapefile corresponding to the largest scale Nautical Chart coverage of the project area. The purpose is to document navigational hazards, landmarks, and coastline features portrayed on NOAA Nautical

Chart products whose existence or geographic position cannot be confirmed photogrammetrically, or whose size, shape, orientation or position appear to have changed significantly from the current chart portrayal. The CEF shall contain the necessary annotations made by the compiler during the feature collection process, as described in Attachment K. The annotations in the CEF are used by the Office of Coast Survey to aid in the application of the GC data when updating charts and when performing hydrographic survey operations. Any additional notes that are not relevant to these uses shall not be transferred to the CEF. See Attachment AE, for details and examples.

9.4 PROJECT COMPLETION REPORT (PCR) – The Contractor shall prepare a final report which summarizes all phases of the work performed for the project. If more than one project is assigned in a single task order, then a separate and complete PCR is required for each project. If a project is broken into sub-areas (A, B, C, etc.), then a separate and complete PCR is required for each sub-area. Submit the PCR after all other work has been completed.

The PCR shall conform to all of the requirements outlined in Attachment L, which includes a sample PCR for reference. It is important that the discussion of the work performed includes any unusual circumstances that may have occurred, and any deviations from the SOW, Project

Instructions, and/or normal operating procedures. The PCR shall be delivered in the following formats: Microsoft (MS) Word®, and the Adobe Acrobat® Portable Document Format (PDF).

NGS will make the PCR (in PDF format) available on the NOAA Shoreline Data Explorer website for download along with the project shapefiles. See Attachment L.

10. DELIVERABLES

The Contractor shall submit all Task Order Deliverables and Weekly Status Reports to NGS using the TOMIS system. All Deliverables shall be named exactly the same as they are listed in

TOMIS. All Weekly Status Reports shall be submitted directly to TOMIS by 2:00 pm EST every

Monday. All Deliverables smaller than about 10 MB in size shall be submitted to TOMIS as an attachment. This should include almost all digital files, except imagery. Larger files may be compressed and submitted to TOMIS in compressed format. If the Deliverable is still too large after compression, the Contractor shall submit a report to TOMIS expressly stating what the

Deliverable is and how the Deliverable is being delivered, i.e. via express mail, Secure File

Transfer Protocol (SFTP), etc. The Contractor shall submit the data delivery report to TOMIS the same day that the Deliverable is sent. Use a Transmittal Letter (TL) for all shipments of data outside TOMIS.