Am2_Q___A_rfq140G0326Q0120_0002.pdf
PDF 564 KB Posted
- Attached to
- PINGMapper Python Programming Services
- Solicitation number
- 140G0326Q0120
About this file
This is a Questions and Answers document for RFQ 140G0326Q0120 Amendment 2 concerning PINGMapper Python Programming Services.
The RFQ addresses modifications to PINGMapper software to process side-scan sonar data collected along the Klamath River. The specific sonar hardware used is a Humminbird 710292-1 XM 14 HW MSI T SOLIX unit that generates data in three file formats (.DAT, .SON, .IDX). Work will begin from the baseline PINGMapper codebase without existing scripts or prior modifications to build upon. The contractor must be capable of independent analysis and interpretation of results, not merely technical implementation. The dataset comprises 150 total scans (~6GB raw data, ~2GB post-processed data) across 75 sites collected in three survey years: pre-dam removal datasets from 2022 and 2023, and post-dam removal dataset from 2025. USGS has already post-processed all datasets using the current version of PINGMapper and will share all raw and post-processed datasets with the contractor, along with a shapefile containing digitized ripple mark locations for validation and accuracy estimates. GPS data was collected using Trimble R8/R10 base stations and R12 rovers, synchronized to GPS time with documented physical position offsets between sonar and GNSS receivers. No project manager, site visits, or travel are required. The vendor must provide all computing resources. Reference sample sonar data from other USGS field sites can be accessed at https://data.usgs.gov/.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Sol_140G0326Q0120_Amd_0002.pdf | ||
| Sol_140G0326Q0120_Amd_0001.pdf | ||
| Sol_140G0326Q0120.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Questions and Answers
1. What specific outputs or modifications to PINGMapper are required beyond its current published capabilities?
THOSE LISTED IN THE SCOPE OF WORK
2. What sonar hardware and data formats are used in the field data collection for this study?
HUMMINBIRD SIDE SCAN SONAR USED TO COLLECT SONAR RECORDINGS; SPECIFIC
SIDE SCAN SONAR UNIT USED FOR DATA COLLECTION IS HUMMINBIRD 710292-1 XM 14
HW MSI T SOLIX. THREE FILE FORMATS - .DAT .SON .IDX
3. Are there existing scripts, preprocessing workflows, or prior modifications to build upon, or would this work begin from PINGMapper's current baseline codebase?
BEGIN FROM BASELINE PINGMAPPER CODE
4. Will the scientific interpretation of the sonar data, including determining what the analysis should show, be handled by the USGS team, with the contractor responsible for the code and technical implementation that produces those outputs?
CONTRACTOR MUST BE CAPABLE OF INDEPENDENT ANALYSIS AND INTERPRETATION OF
RESULTS
5. Would it be possible to share a sample of the raw sonar data, along with a description of the specific outputs required, so that we can properly size and scope the work for our quote?
KLAMATH DATA HAS NOT BEEN PUBLISHED - EXAMPLES OF SIDE SCAN SONAR DATA,
COLLECTED AT OTHER USGS FIELD SITES, CAN BE FOUND AND DOWNLOADED BY
SEARCHING AT https://data.usgs.gov/
RFQ 140G0326Q0120 Am2 PINGMapper Python Programming Services Page 1 of 3 https://data.usgs.gov/datacatalog/search?usgsKeyword=%5B%22sidescan+sonar%22%5D&isoKeyword=%5B%22inlandwaters%22%5D&otherKeyword=%5B%22sidescan+sonar%22%5D
6. Are there any specific 'project manager' requirements in this case? Based on the documentation I did not find, but I would like to confirm.
NO
7. Are there any specific requirements in terms of 'onsite' or other places to visit and travel?
NO SITE VISITS OR TRAVEL
8. For the 'compute' of the project, does the vendor bring (and quote) his or her own, or is anything provided by the agency? Some tasks require computational power, and we typically lease it from Fed-approved Cloud Providers.
VENDOR IS REQUIRED TO PROVIDE COMPUTING RESOURCES
9. Any additional requirements I should be mindful of.
NO
10. For the 2025 GPS data, were the GNSS receiver and Hummingbird clocks synchronized to a centralized time reference during collection? If so, what was the method for synchronization?
YES SYNCED USING GPS TIME
11. During the 2025 data collection, if the clocks were not synchronized, was there any documentation during collection on the magnitude of drift between the two device clocks.
CLOCKS WERE SYNCED
12. For the 2025 GPS data, what GNSS receiver (make and model) was used, and what format was the data stored as?
TRIMBLE R8/R10 BASE STATION AND R12 ROVER
RFQ 140G0326Q0120 Am2 PINGMapper Python Programming Services Page 2 of 3
13. During the 2025 data collection, was the physical position offset between the sonar receiver and the GNSS receiver documented?
YES, OFFSET WAS MEASURED
14. Are the 75 sites consistent across all three survey years, or did the site locations and/or boundaries change between surveys?
THERE ARE A TOTAL OF 75 SITES WITH REPEAT SURVEYS WITH OVERLAPPING DATASETS.
A PRE-DAM REMOVAL DATASET WAS COLLECTED IN 2022 and 2023, AND A POST-DAM
REMOVAL DATASET WAS COLLECTED IN 2025.
15. How many individual sonar recordings (files) are there across the 75 sites and three survey years, and what is the approximate total data volume?
THERE ARE A TOTAL OF 150 SCANS (~6GB of RAW DATA AND ~ 2GB of POST PROCESSED
DATA)
16. Has any preliminary processing already been applied to the sonar recordings for any of the years, or will raw unprocessed files be delivered?
YES, USGS POST-PROCESSED ALL DATASETS USING CURRENT VERSION OF PINGMAPPER
17. Were any of the surveys processed with any version of PINGMapper or any other processing software? If so, are those outputs available for reference?
YES, USGS WILL SHARE ALL RAW AND POST-PROCESSED DATASETS
18. Are there any manually labeled substrate references along the Klamath that could be used to validate and calibrate the confidence thresholds developed in Task 1?
YES, USGS WILL PROVIDE A SHAPEFILE WITH DIGITIZED LOCATIONS OF RIPPLE MARKS
TO CALCULATE AN ACCURACY ESTIMATE FOR THE FINES RIPPLE CLASS
RFQ 140G0326Q0120 Am2 PINGMapper Python Programming Services Page 3 of 3
File details come from the government source that posted it. Updated .