SOURCES SOUGHT
70 -- Software Application to Support Automatic and Manual QA
- Notice Date
- 4/22/2011
- Notice Type
- Sources Sought
- NAICS
- 541511
— Custom Computer Programming Services
- Contracting Office
- USGS OAG DENVER ACQUISITION BRANCHPO BOX 25046204 DENVER FEDERAL CENTERDENVERCO80225-0046US
- ZIP Code
- 00000
- Solicitation Number
- 11GDB008NoSolicitation
- Response Due
- 5/23/2011
- Archive Date
- 6/22/2011
- Point of Contact
- Robert Valdez
- E-Mail Address
-
rvaldez@usgs.gov
(rvaldez@usgs.gov)
- Small Business Set-Aside
- N/A
- Description
- REQUEST FOR INFORMATION Acquisition of Software Tools to Support Quality Assurance Testing of Lidar Point Cloud and Associated Data Deliveries I. AREA OF INTEREST The U.S. Geological Survey (USGS) is requesting product, cost, and delivery information for software applications to support automatic and manual Quality Assurance (QA) of lidar point cloud and associated derived data products. In addition, the USGS is also soliciting information to determine the availability of capable contractors that can provide these tools, provide training, and perform software maintenance support. II. RESPONSES Respondents should submit the RFI deliverables specified below for Software Tools to support QA of lidar point cloud and associated data deliveries. Although information gained from this Request for Information (RFI) may be used to secure funding and initiate mapping contracts, the government does not intend to award a contract on the basis of this RFI. It is issued solely for information and planning purposes. The government will not pay for any information or administrative cost incurred in response to this RFI. III. BACKGROUND Continued development of lidar technology and the industry over the past decade has demonstrated the broad range of applications of lidar point cloud data, beyond simple derived DEMs. Many of these non-DEM applications are of significant interest to the USGS. With the implementation of the USGS-NGP Lidar Guidelines and Base Specifications-Draft v13 (the Spec), the USGS has expanded its technical interest in lidar beyond the delivery of derived DEMs to include the source lidar point cloud data, intensity image, and perhaps waveform data. This shift is particularly important as lidar coverage continues to expand, potentially spawning a national lidar layer, and the need for consistency in point cloud data structure becomes more urgent.The v13 Spec includes a number of new technical requirements on lidar point cloud deliverables for which efficient means of validation are currently unavailable. These include, but are not limited to, validation of: LAS compliance; presence of all requisite deliverables; conformance to the Spec and project-specific requirements; content; and accuracy of metadata and reports. Many of these requirements can be validated automatically by configurable software. Other requirements will require a framework for visualization and manipulation in which QA task-driven manual inspection can occur. The USGS seeks detailed technical information on existing software tools, the potential for modification of existing applications, or the development of new software tools to allow efficient, accurate, and detailed QA of lidar point cloud and associate data products. IV. PROPOSED MINIMUM SPECIFICATIONS It is assumed that any application will require some initial user input/configuration to establish the location and identification of key files, a folder containing deliverable files, and project specific parameters that may differ from the base requirements of the v13 Spec. The v13 Spec requires full compliance with the LAS Specification. Some of the LAS requirements may be noted in this RFI. The exclusion of specific LAS requirements in this document DOES NOT mean that these requirements do not need to be checked. Respondents should thoroughly review the LAS v1.2/v1.3 specifications. The following list may not be exhaustive. Recommendations from respondents on additional or alternative functions are welcome and should be included in the response. The Automatic and Manual checks can be addressed by separate software modules, provided there is integration between the modules to remove the necessity for manual transfer of initial configuration or derived information between modules. AUTOMATIC CHECKS 1. Verify that all LAS files are fully compliant with either LAS v1.2 or v1.3 (this covers a very large number of checks which will not be detailed in this RFI. A thorough review of the LAS Specification by respondents will be required).2. Verify that any LAS v1.3 files use external wave packet files, and that each v1.3.las file has a corresponding.wpd file.3. Verify that LAS files have not been trimmed (presence of Edge Of Scan flags)4. Verify that all LAS files use Point Record Format 1, 3, 4, or 55. Verify that all LAS files are =< 2GB6. Verify that all LAS files do not use Class=127. Verify that all points have been classified (no Class=0)8. Verify that the Withheld Bit has been used9. Verify that all LAS files use the correct GPS Time format and that recorded times are logical.10. Verify (identify) the collection time windows.11. Verify that all LAS files use the same CRS and contain complete and correct projection information.12. Verify the NPS of the LAS data (single swath, 1st returns) 13. Verify the non-clustering of the LAS data (single swath, 1st returns)14. Verify the overlap of the LAS data (swath)15. Verify the maximum scan angle (swath)16. Verify that all Classification values conform to the project Specs (tiles)17. Verify that LAS data (swaths) are free of data voids identify void areas18. Verify the relative accuracy between swaths19. Verify the relative accuracy within swaths20. Verify absolute accuracy calculations using provided check-points:a. Against Lidar Points (FVA only)b. Against DEMs (FVA, SVA(s), CVA)21. Verify that the collection completely covers the buffered project area22. Verify that each swath contains a unique File Source ID23. Verify that each point contains a Point Source ID consistent with its File Source ID (swaths)24. Verify that Point Source IDs have been carried-over into LAS tiles25. Verify (identify) the range of Intensity values in all LAS files.26. Verify that all points in all LAS files contain Intensity Values27. Verify the validity of the XML Metadata files28. Verify consistency between metadata information and LAS header information29. Verify that units of Foot or Feet specify US Survey or International.30. Verify that the number of tiled deliverables (LAS, DEM, Intensity, etc.) is consistent with the number of tiles in the Project Tile Index31. Verify that the naming of tiled deliverables is consistent with the tile names in the Project Tile Index32. Verify that within tiled deliveries, tiles do not contain overlap33. Verify that all tiled deliverables contain correct and complete CRS information34. Verify that breaklines are PolylineZ or PolygonZ (3D geometry)35. Verify that Intensity Images (if delivered) are rescaled to 8-bit grayscale.36. Verify that breakline elevations are at or below the coincident DEM elevations37. Verify that coincident vertices/nodes (same X-Y) within the breaklines have the same Z. MANUAL CHECKS A basic visualization framework is needed to perform the following inspections. May be a separate module from the automatic check module, and may utilize another visualization environment such as ArcGIS. 1. Inspection of all delivered products (LAS, DEM, Breaklines, Images) with display of embedded CRS information, and compared to known CRS geo-spatial reference data (i.e., ESRI data)2. Inspection of identified VOID areas, comparing imagery, lidar points, and breaklines3. Inspection of swath overlap, comparing full swaths.4. Inspection of data coverage, comparing LAS swaths/tiles, DEMs, images against shapefiles5. Inspection of entire projects for systematic errors, viewing and/or filtering all LAS points by Elevation, Classification, Return Type, File, Point Source ID, etc. Visualization of entire project DEM surfaces in grayscale or color ramp, with or without hill-shading.6. Visualization of LAS points over Point TIN and/or DEM surfaces. Points must be symbolized independently from surface (i.e., Points colors by Classification with surface colored by hill-shaded elevation).7. Inspection of hydro-flattening, comparing DEM surface, breaklines, and imagery8. Measurement tools (length and area)9. Identification tools (elevation values from DEMs, intensity values from imagery, lidar point attributes)10. XML metadata reader/editor V. GENERAL INFORMATION Posting Date: April 22, 2011Response Date: May 23, 2011 Contracting Office Address: Robert Valdez, Contracting OfficerUnited States Geological SurveyP.O. Box 25046, MS 204BDenver Federal Center, Denver, CO 80225 Please send one copy of your response to Robert Valdez. Please send two copies of your response to: Tim Saultz, MS 670U.S. Geological Survey, NGTOC-Rolla1400 Independence RoadRolla, MO 65401573.308.3654 Developers and software vendors may download reference documents from the following locations: USGS-NGP Lidar Guidelines and Base Specifications-Draft v13: http://lidar.cr.usgs.gov/USGS-NGP%20Lidar%20Guidelines%20and%20Base%20Specification%20v13(ILMF).pdf ASPRS LAS v1.3 Specifications: http://www.asprs.org/society/committees/standards/LAS_1_3_r11.pdf NDEP/ASPRS LAS v1.3 Specifications: http://www.ndep.gov/NDEP_Elevation_Guidelines_Ver1_10May2004.pdf Interested developers and software vendors may request sample lidar data to support their development efforts by sending a 2TB external hard drive (USB or eSATA interface required), with a letter referencing this RFI number, to: H Karl Heidemann, GISPU.S. Geological SurveyEarth Resources Observation and Science Center47914 252nd Street, Sioux Falls, SD 57198Phone:605-594-2861Fax:605-594-6529kheidemann@usgs.govhttp://lidar.cr.usgs.gov Developers and software vendors seeking further information about this RFI or seeking clarification to any part are invited to submit their questions in writing via email to: rvaldez@usgs.gov with cc to: tsaultz@usgs.gov and kheidemann@usgs.gov This is the only approved way for a vendor to submit questions or comments to the government during the open period of this RFI.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DOI/USGS/USGS/11GDB008NoSolicitation/listing.html)
- Record
- SN02431274-W 20110424/110422234224-c3f2d8c77abac80ddf6b63d96eae5a5b (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |