Add a property¶
Before adding a canonical property, define what the concept includes and excludes. “Available phosphorus,” “cation exchange capacity,” and “pH” are method-dependent families, not context-free numbers.
Required changes¶
- Add ID, display name, description, standard unit, aliases, conversion notes, method warning, and status to the property registry.
- Document method distinctions and approved units.
- Map provider columns only when they represent the same canonical concept.
- Preserve original field, value, unit, depth, and method in each observation.
- Add success, null, alias, unsupported-provider, and schema tests.
- Add a decision record for any conversion or potentially ambiguous mapping.
Conversion review¶
A conversion must state input/output units, formula, precision behavior, domain limits, and source. The response must append a transformation. Derived relationships—such as organic matter to organic carbon—are not unit conversions and require a method/model with their own uncertainty and warnings.