QUOTE REQUESTED BY:<Company Name>

<Location>

Bathymetric LiDAR Acquisition

QUOTE REQUESTED BY:<Company Name>

Request for Quote No: <Quote Number>

Date issued: <Date>

Requested by:<Contract Manager>

Telephone No: <Contact Number

Preface

Digital elevation data which describes Australia’s landforms and seabed is crucial for addressing issues relating to the impacts of climate change, disaster management, water security, environmental management, urban planning and infrastructure design. In recent years dramatic developments in LiDAR technology and industry capabilities have revolutionised our ability to address these issues at the local level. However, inconsistent and diverse product specifications, and variable data quality are often making it difficult to integrate datasets to address regional, state and national issues. In order to optimise investment and the utility of both existing and future data collections there is a need for a national base specification which defines a consistent set of minimum products which ensure compatibility across projects and States.

In late 2008, the Australian Intergovernmental Committee for Surveying and Mapping (ICSM) Elevation Working Group released Version 1.0 of the Guidelines for Digital Elevation Data (topographic) acquisition. In late 2012, the ICSM Bathymetry Working Group released Version 1.0 of the Guidelines for Digital Bathymetry Data acquisition. The intent of these specifications and tender templates is to further improve on the quality, consistency, utility and compatibility of data being captured by government and commercial off-the-shelf (COTS) products increasingly being offered by the private sector. Moreover, the specifications and tender template provide opportunities for greater collaborative investment across all levels of government, and capacity to reduce tender and compliance costs for investors and providers.

Use of these specifications will also ensure that primary LiDAR point cloud data and derived products can be easily integrated and ingested into the National Elevation Framework Data Portal (NEDF-Portal), providing increased discoverability and access to the broader user community.

The specifications have drawn on recent experience across all levels of Australian government, consultation with LiDAR data providers, and the U.S. Center for LiDAR Information, Coordination and Knowledge (CLICK). They provide a minimum base specification and are not intended to limit development of more specialised products. Nor are they intended to inhibit industry development and innovation. We therefore encourage interested users, investors, researchers and suppliers to contribute to ongoing development. If you wish to make a submission aimed at improving this document or require technical support, please email . For further related information please visit the following sites:

Bathymetric LiDAR Acquisition for the <Location> – <Month> <Year>

Contents

2Project Brief

3General Project Requirements

4Project Details and Timeframe

5Project Area

6Product Summary of Key Deliverables

7General Bathymetric LiDAR Specifications

8LiDAR Point Cloud Specifications

9Bathymetric LiDAR Derivative Data Specifications

10Data Supply Specifications

11Project Planning and Reporting Specifications

12Bathymetric LiDAR Quality Assurance Specifications

Attachment A – Project Area Maps and Available Geodetic Control Points

Attachment C – NEDF Metadata Specifications

Attachment D - Submission of Quotation

Attachment E - Quotation Template

Attachment F - Ownership/licensing of Foreground Intellectual Property

Attachment G – Statement of Compliance

2Project Brief

Provide an overview of the background to the project and the project objectives.

3General Project Requirements

Provide a summary of the required project deliverables and any specific issues that must be addressed in the project.

4Project Details and Timeframe

Provide a summary of the overall project timeframes and specific milestone dates. This should include dates relating to the Tender process, data acquisition, product delivery and reporting. Any requirements for any staged delivery of services and products should also be specified.

Lodgement of the tender by email (20 MB LIMIT) or received by post by <Time and Date>. <Company Name>reserves the right to not accept any tender lodged after the closing date. Direct any further enquiries or questions to <Contract Manager>.

Email: <Contact E-mail>

Phone:<Contact Phone>

Post: <Contract Manager>

<Contract Manager Title

<Address>
The following timeline for the project is required:

5Project Area

Provide an overview map of the project area and any detailed maps or diagrams as an attachment. Describe the overall characteristics (biophysical, cultural, climatic, etc) which may affect data acquisition, processing or validation. For example, the nature of the bathymetry, vegetation that may impact on responses, access for validation. Provide a digital file in shapefile format depicting the extent of the project and other relevant features.

6Product Summary of Key Deliverables

7General Bathymetric LiDAR Specifications

1. LiDAR: specific capture window requirements.
2. Field Data: specific requirements relative to LiDAR acquisition.

1. Fundamental Vertical Accuracy (FVA)
2. <= ±25cm. 95% confidence interval (1.96 x RMSE)
3. Fundamental Horizontal Accuracy (FHA)
4. <= ±2.0m. 95% confidence interval (1.73 x RMSE)

1. All survey control data used or derived from this contract must be supplied to ensure independent Quality Assurance (QA) of the survey operations, and for possible inclusion in the State’s survey control infrastructure. It is therefore essential that all primary ground stations are permanently marked in accordance with the appropriate State system.
2. The primary ground control and check point surveys must be referenced to the local datum specified above comprising State survey control marks with “established” GDA94 coordinates and/or “accurate AHD” heights as defined in the relevant State Surveying regulation.
3. Survey to establish new primary control shall use techniques to achieve a minimum standard of:
4. Horizontal: Class B
5. Vertical: Class B or LD.

1. The survey control needs to be outlined in the tender response and in more detail in the Pre-Survey QA Plan. The tide management will form part of the survey control.
2. The analysed differences with overlapping topographic LiDAR and the survey integration points should form part of the control. Areas which will be tested for differences should be highlighted in the pre-survey QA plan.

1. Tide Model Diagram
2. Tide Station Details (position, LAT / MSL difference, status (observer / monitor / dummy))
3. Prediction Constituents
4. All observed tides
5. Observed and predicted turbid areas

1. detecting the seafloor to depths of at least 40m.
2. recording the backscatter from each pulse.

1. The aerial photography should be metric digital and coincident with the bathymetric LiDAR.
2. The collection of aerial photography will be secondary to the collection of LiDAR data. Whilst the atmospheric conditions should take into account the quality of the aerial photography it should not do so at the expense of LiDAR capture.
3. The aerial photography should be supplied as an ECW mosaic for the full extent of data acquired and as geotiff tiles using the same tile index used for the LiDAR delivery.
4. The RFQ response should identify the achievable image resolution based on the flying height required to meet LiDAR acquisition specifications. A resolution better than 50cm is required.
5. The spectral range of the imagery should be three band: R,G,B.
6. The aerial photography should be corrected using a georeferenced solution. The accuracies for a georeferenced product are considered “relaxed” in relation to fully orthorectified products (see spatial accuracy below). The rectification process may not necessarily follow a complete orthorectification process work flow, however, providers should clearly outline the processing steps in their proposal, including the use of control and camera corrections.
7. The spatial accuracy of the aerial photography should be ±4 x GSD RMSE (1 sigma or 68%).
8. There should be no gaps between imagery from adjacent flight lines.
9. Colour balancing and colour matching between frames is not expected.
10. Contrast and brightness adjustment of each image is not expected.
11. Frame selection should minimise noticeable exposure patches, vertical height displacement and seam lines between ground features.
12. For all image products, ensure the data values are set to the range of 0-255, with the value 0 or 255 reserved for null image data.
13. The inclusion of aerial photography within the scope of the project will depend on cost and impact on the LiDAR. The RFQ response should include any potential impact on the LiDAR collection.
14. If, after collection, the photography is affected by significant cloud the contracting authority may remove the product from the scope of the project. Therefore, the costs need to be split between collection and supply.

8LiDAR Point Cloud Specifications