Put the unit in the field definition
Labels such as diameter_mm, height_m and crown_spread_m make the intended units clear in a spreadsheet. Agree the measurement method and reference point for each field in the project brief. Where a specialist assessment requires a particular method, use that method and retain its description; a column label alone does not define how a measurement was taken.
Check a conversion with an example
A diameter recorded as 35 centimetres is 350 millimetres. If the receiving schedule expects millimetres, entering 35 without conversion changes the meaning by a factor of ten. Keep the source value and source unit when reviewing an imported schedule, then record the conversion. Do not infer the unit solely from what looks like a plausible tree size.
Do not confuse circumference and diameter
They describe different measurements. Record which was measured. If a conversion is appropriate to the agreed method, document it instead of copying the circumference into a diameter column. Irregular form and multiple stems can require additional context; confirm how they will be represented rather than forcing every tree into one unexplained value.
Retain uncertainty
- Mark estimated height separately from instrument or directly measured values.
- Describe visibility or access limits affecting the measurement.
- Use consistent rounding that suits the method and purpose.
- Keep blank, zero and not applicable distinct.
- Do not add decimal places that imply accuracy the method did not provide.
Review after export
Open the client schedule and check its column headings, units, notes and estimate flags. Compare a few source records with the exported values. Keep the field definitions with the handover so another surveyor can interpret them later. See schedule quality checks and writing the project brief to agree the requirements before collection begins.
Prepared by Canopy.