UG39 Lidar Proposals: Does the Density Figure Count Pulses or Returns?
United UAV
Before comparing lidar density figures in a proposed UG39 sensor workflow, ask whether they count pulses, returns or a defined subset of points. Also request the assessment area and the treatment of overlapping coverage. Similar-looking density labels can describe different quantities. The aircraft model does not establish the counting method, the suitability of a lidar payload or the quality of a delivered point cloud.
A density number needs a noun
Two survey proposals reach a procurement team with a density figure prominently displayed. One provider refers to a pulse-based measure; the other describes all delivered points. The buyer puts both figures in the same comparison column. The problem is not necessarily that either provider has calculated incorrectly. It is that the comparison has erased the difference between the quantities. This is a hypothetical procurement example, not a measurement from a UG39 flight or a statement about any current supplier's offer.
Start by asking the provider to complete an ordinary sentence: this figure counts these records, over this area, under this treatment of overlap. That sentence should be understandable to the technical evaluator even if the full method is documented elsewhere. An unexplained abbreviation in a quotation should not become the buyer's acceptance criterion by accident. A higher number is not useful until the team knows what it represents.
The terminology source and its boundary
The USGS Lidar Base Specification glossary defines nominal pulse density using pulses per area, with first or last returns used as surrogates. It distinguishes that single-swath measure from aggregate measures involving multiple passes or instruments. These definitions support a careful question about counting. They do not establish a UG39 sensor configuration, impose a requirement on every private contract or automatically apply a US specification to a Singapore project.
The buyer's next step is to identify the specification actually proposed for the work. If a quotation cites a standard, ask for the exact edition and the clauses the supplier intends to meet. If it uses a project-specific measure, ask for the definition directly. Avoid combining a familiar technical label with an unstated calculation method. The responsible survey specialist should explain how the chosen measure relates to the required deliverable.
Keep three questions separate
First, what was counted? Second, where was it counted? Third, how will the result be used in acceptance? These questions belong together but are not interchangeable. A clear record count does not define the spatial assessment. A clear spatial assessment does not establish an adequate acceptance threshold. The buyer should appoint a technical owner for the whole interpretation while retaining separate answers to each part.
| Question | Evidence to request | Ambiguity to avoid |
|---|---|---|
| Which records? | The included return or point categories and relevant exclusions | Assuming every delivered point represents a separate pulse |
| Which area? | The evaluation footprint and the way it was divided for review | Comparing a local result with an overall average |
| Which coverage? | The stated handling of overlap and repeated collection | Treating aggregate coverage as a single-swath result |
| Which decision? | The named acceptance criterion and responsible reviewer | Calling a large number sufficient for every intended use |
Use this table as a discussion aid, not as an automatic compliance test. Some projects need additional distinctions and others use a different reporting arrangement. Ask the provider to identify those differences rather than squeeze its explanation into an unsuitable template. The aim is to make the proposals comparable on the questions that matter to your contract.
Ask for one inspectable calculation example
A sample density report becomes much more useful when the analyst can point to the records included in one assessment unit and explain the denominator. Request a representative example that can be inspected under the proposed delivery arrangements. The buyer does not need to recreate the entire production pipeline in a sales meeting. It does need evidence that the headline figure can be traced to a stated method rather than copied from an unrelated demonstration.
Have the technical reviewer select the example with the intended use in mind. A uniformly covered open area may not answer the same questions as the edge of the project or a location with more complicated coverage. Do not infer the full site's condition from one convenient crop. Ask how the provider will report variation and exceptions across the actual scope, then decide which supporting materials should accompany the final deliverable.
Look beyond the average without inventing a threshold
An overall summary can be useful for orientation, but the buyer still needs to know where the acceptance decision is made. Is the contract assessed by delivery unit, by an agreed spatial grid, by another defined area or by a combination of reports? That choice should be visible in the proposal. Otherwise, a discussion about one weak location may become a disagreement about a rule neither side wrote down.
This article deliberately does not supply a universal density target. The required evidence depends on the intended output and the applicable project specification. Ask a qualified evaluator to determine that requirement, explain its limitations and distinguish it from other quality considerations. Do not turn a procurement article into a substitute for the technical scope. A supplier should be able to say when the available evidence is insufficient for the buyer's proposed conclusion.
Separate the density report from other evidence
A well-defined density measure does not answer every point-cloud question. The project may also need evidence concerning classification, coverage, coordinate reference, processing history and fitness for the chosen analysis. Keep those requests distinct. A provider's satisfactory answer about counting should not be recorded as approval of unrelated properties, and an unresolved issue elsewhere should not erase the value of a properly documented density result.
Likewise, do not let a polished visualization stand in for the report. A point-cloud viewer can help reviewers navigate a sample, but acceptance should refer to the agreed evidence rather than the apparent fullness of a screenshot. Ask which supplied files reproduce the reviewed example and whether the receiving team has the means to inspect them. An impressive demonstration on the provider's workstation may leave a gap if the buyer cannot examine the delivered records.
A buyer lesson for the comparison meeting
Our recommended desk-based exercise is to remove the headline numbers from the comparison sheet temporarily. Ask each bidder to explain its count definition, footprint and overlap treatment in the same order. Only restore the numbers after the evaluator has established which columns genuinely describe comparable quantities. This is an editorial procurement technique, not a claim about personal field experience or a test flown with the product.
Record any unresolved differences in the clarification log. If one supplier needs to recalculate a measure to make it comparable, identify the revised report and the date it supersedes the original. Avoid manually converting a figure using an assumption that the provider has not confirmed. A quick spreadsheet adjustment may make two columns look consistent while concealing a material difference in the underlying evidence.
Carry the final definition into the purchase documents, not only the meeting notes. Identify any sample that was accepted as the reporting model and retain its limitations. When another project manager takes over, that record should explain why the comparison was considered valid and which questions still belonged to the technical evaluator. A handover should not require reconstructing the discussion from the largest figure in a slide deck.
Place the UG39 inquiry in the correct scope
The current approved catalog identifies the UG39 Extended-Route UAV Fixed Wing Drone for Survey, Inspection and Sensor Missions. That identity provides a starting point for an aircraft inquiry. It does not prove compatibility with a particular lidar unit, the inclusion of processing services or the achievement of a density requirement. Ask for configuration-specific evidence and identify the integrator responsible for any proposed payload before drawing those conclusions.
US and Singapore buyers can use the same clarification structure while commissioning different work under different requirements. Specify the intended deliverable, the technical reviewer and the applicable project documents. This article offers no local operating authorization or surveying compliance determination. Keep those responsibilities with the appropriate specialists. Aircraft supply, payload integration and data acceptance may involve different organizations, and the quote should make those boundaries explicit.
What if the provider cannot explain the count?
Do not replace the missing explanation with an estimate drawn from marketing material. Mark the density claim unresolved and ask who can supply the method. A useful response may be a corrected definition, an additional report or a statement that the proposed service cannot meet the requested evidence scope. The buyer can then make a deliberate decision instead of assigning false precision to an unsupported comparison.
Related deliverable questions deserve their own review: contour smoothing can change the interpretation of linework, while mosaic color balancing raises presentation-versus-analysis questions. These checks address different processing decisions. Keeping them separate helps the team build a focused acceptance package rather than relying on a single vague promise of high-quality survey data.
Browse the VTOL and fixed-wing drone collection and send your proposed point-cloud deliverable requirements. Include the intended analysis, the specification you expect to use and the density definition that needs clarification. Request an aircraft configuration discussion and a separately identified payload and data-evidence scope. The strongest next step is an inspectable explanation of the count, not a larger unsupported number.