Follow-up from "Separated completeness and area_type fields"
The following discussion from !14 should be addressed:
Currently the manual completeness assessment resides in
obm_tiles.completeness. For all water types the respective
area_typevalue can be set. Do we also need the water in
I'm also thinking if we should switch to a bit type for the manual completeness assessment in
obm_assessmentas well. Will require a new column, though.
area_type being a 4 Bit representation, the idea is to also represent the completeness assessment (complete, incomplete, almost complete and undecidable) in 4 Bits and to streamline both into a single 8 Bit = 1 Byte data object / column in the database.