HOM vs POM?

[gabrielareto]

Very unclear what the difference is. Users are confused. It seems the app treats HOM as a number, and POM as a code (breast, base? I never saw this). But this distinction is not standard, people use these two terms interchangeably.

[ValentineHerr]

This is to be able to deal with the fact that some networks don't actually measure the height of measurement and instead use a code to say if the point of measurement has changed.

I'll try rewording it.

[ValentineHerr]

This is my rewoarding. OK?

[gabrielareto]

HOM vs. POM are used very often and exchangeably by people, and have mental intertias linked to them. I doubt we can use these acronyms and avoid the risk of not being clear, regardless of how we define them. We have to avoid the acronyms, and write directly what we mean.

e.g., for the HOM column write directly the definition, "Height at which the DBH was measured, above the ground or above the base of the stem".

I still don't understand what "POM" means. What is the expected content there? "TRUE" or "change" or "new" if the POM changed? I.e. just a flag to avoid calculating growth for that stem and interval?

Do you mean "change" as "deviation from the standard 130 cm" or "change between censuses"?

How can HOM and POM be not congruent with each other? If there is content in POM, can there be content in HOM? Do we expect HOM to be filled with "130 cm" for every single stem (like the default HOM) and then "POM = 175 cm" in some cases that deviate from the standard?

Please explain, I would like to understand what situation motivated the inclusion of these columns as two separated ones.

[gabrielareto]

This is creating more problems than solutions. Remove POM as an option. Just keep one field to express the height at which the DBH is measured.