Two survey contractors can both deliver two-metre contours and draw different lines on an unchanged slope. Ask which elevations their lines represent. If one series uses even whole metres and the other uses odd whole metres, no pair of lines in the two series represents the same height. Before comparing any coordinates, agree a common origin for the interval or an explicit list of required levels. Make that list part of the purchase specification for a UVH1 survey project; the aircraft name cannot settle a cartographic decision.

Start with the number attached to the line

Consider a fictional stockyard whose relevant elevations lie between 100.4 and 109.6 metres. One analyst delivers lines labelled 102, 104, 106 and 108. Another delivers 101, 103, 105, 107 and 109. In both deliveries adjacent levels differ by two metres. Both answers can therefore satisfy the instruction “use a two-metre interval.” They cannot be substituted for each other in a comparison of the 104-metre line. The second drawing does not have one. Matching its nearest line to the first drawing creates an apparent movement that the numbers never described.

That example deliberately leaves out terrain error, changes to the site and differences in software. Removing those distractions helps a buyer identify a defect in the instruction itself. The contract named the spacing but left open the sequence to which the spacing applies. A simple extra sentence about the reference level would have made the two outputs comparable on this one issue. It would not, on its own, make the surveys accurate, establish their vertical reference or prove that the two surfaces describe the same date.

Decide what must line up at the receiving end

A designer tracing one specified elevation needs a different deliverable from a presentation team looking for an easily readable relief map. Start the meeting with the designer's question: which line must I be able to retrieve by its value? If the answer is an exact design level, name that value. If a series of benchmark levels is needed at every submission, list the rule and a few expected members. If the only need is visual, say whether the map maker may select sensible levels independently for each sheet.

Put the unit beside every number. Then identify the elevation reference in a separate field. The origin of a contour sequence is a parameter used to choose levels, not a substitute for a vertical datum. Moving the origin of the list does not transform the underlying elevation values into a different reference system. A supplier who changes only contour settings should not present the result as a datum correction. Conversely, when reference systems actually differ, resolving the level spacing alone does not solve the comparison problem.

Take special care when a project crosses multiple drawing sheets. If each supplier selects a pleasing first line from its own tile minimum and counts upward from there, the sheets may not share levels along a common edge. That is not necessarily a gap in coverage. Ask for the levels that each tile can represent under the project rule. If those lists agree where their elevation ranges overlap, move on to geometry and edge checks. If the lists disagree, start with the production instruction before spending money on a field investigation.

Ask the processor to show its choices

The GDAL contour documentation gives a useful example of the distinction. Its interval option controls the spacing between levels; its offset option sets the origin relative to zero for that interval. It can also accept a list of fixed levels. This is evidence about one program, not a requirement to use it. Another processor can meet the same purchasing need by documenting how it chose elevations and returning the actual values in a field the buyer can read.

Invite the processor to illustrate the rule with a short list inside the range of a proposed example surface. Avoid relying on a screenshot of an options dialogue. It may show a remembered default while the delivered layer came from a saved batch job. Better evidence includes the job settings, the input tile identity and a summary of distinct elevation values read back from the resulting file. Even a small project benefits from keeping those three pieces together. They link the intent, the processing choice and the observed result.

Not every requested elevation will occur on every tile. A level above the local maximum should not be invented to make an inventory look complete. Similarly, a single elevation can produce more than one line in different parts of a tile. Count distinct levels separately from the number of features. Write down whether an absent level is outside the input range, lies in an area with no usable data or requires investigation. Those explanations support different decisions and should not be collapsed into a single missing-line count.

Use a small, decisive acceptance tile

Choose a non-sensitive surface excerpt that spans several required levels. A hypothetical inclined plane can isolate the level-selection rule; a representative survey excerpt can then show how the supplier handles real coverage boundaries. Keep the synthetic example clearly labelled so nobody mistakes it for measured site evidence. Supply the expected level sequence or its derivation in advance. The acceptance exercise should test delivery against an agreed instruction, not guess what the evaluator privately intended.

Have the recipient open the actual vector layer, inspect the elevation attribute and extract its unique values. Compare those values with the required sequence over the covered range. If the drawing carries text labels, inspect those as a second output rather than assuming that a label is the stored value. A rounded display may look correct while the numeric attribute supplied for analysis is different. Decide who can approve a display convention and who owns the numeric data requirement. Usually those questions arise at different desks.

Record one positive and one negative result. For example, an evaluator might log that a value of 104 belongs in an even sequence, and that 105 must not be accepted as a replacement merely because its line is nearby. This written pair gives a future reviewer a way to challenge a silent change of defaults. It also protects a supplier against an unreasonable demand to provide levels the project never requested. A clear exclusion can be as valuable in a contract as a clear inclusion.

When a comparison looks wrong

Suppose a project manager overlays last month's contours and sees a series of roughly parallel displacements. Resist the temptation to order another survey from the picture alone. Click one line from each layer, read both attributes and check the units and source references. If the numbers are not the same, there is no like-for-like comparison yet. Obtain the two elevation surfaces or request a controlled regeneration at common levels before treating the displacement as terrain change.

If the numbers match, the problem has moved beyond contour origin. The surfaces may differ, the inputs may represent different dates, or other processing choices may matter. Preserve the original layers and assign the question to the qualified survey reviewer. Do not shift a drawing manually until it appears to match. That would make a more persuasive picture at the cost of losing the relationship between the contour, its elevation and the surface that produced it. The deliverable should explain disagreement, not conceal it.

The field lesson for a purchasing team is practical: put one named elevation on the acceptance sheet. It gives the person at the screen a question they can answer without knowing every processing option. “Show me the 104-metre feature and its source” is easier to verify than “confirm that the contours look consistent.” On another project, the named elevation may be different. The point is to agree one traceable example before comparing an entire site.

Scope the aircraft and mapping work separately

Use the UVH1 survey VTOL product listing to identify the proposed aircraft. Use the mapping statement of work to describe how data will be processed, which layers will be returned and who will check them. Do not infer that buying an aircraft includes terrain modelling, licensed survey services or a particular contour product. A quotation can cover those items only when the parties specify them. For the available aircraft configuration, contact us for configuration details.

When the resulting map feeds another asset register, the receiving team's definition of a spatial event also matters. The corridor crossing review shows why a genuine contact in a drawing need not be the class of event that a buyer ordered. For a programme buying more than one unit or delivery, the first article approval discussion explains why acceptance of an example does not silently remove the requirements on later work. Both distinctions apply before a clean-looking map is signed off.

Compare the VTOL and fixed-wing aircraft options against the acquisition need, then send a contour delivery inquiry with the intended use, units, elevation reference, level rule and a redacted example tile. Ask for separate prices or scope statements for capture, processing and acceptance evidence. The useful return is not a promise of neat lines. It is a proposal that identifies which lines will be delivered, what each means and how your own reviewer can verify the answer.