We currently have two items in the Standard Data Type definitions that may need cleanup since they are vague and/or US-Centric.
(Reference) LayerType: COMMON_LAND_UNIT. Perhaps we can generalize this to be "REFERENCE_BOUNDARIES" defined as a comprehensive layer of field boundaries as defined by a governmental or other external entity.
Textual DTD - "Legal Description". We added this one without a lot of discussion. Does it really only mean "PLSS Legal Description" within a US Geopolitical Context (and more specifically within PLSS states?) Furthermore, is the intent simply Township Range and Section or a more comprehensive cadastral definition such as the "south half of the northeast quarter, etc." If only PLSS TRS, then I suggest we call it that in some form.
Per discussion in 13 December 2023 meeting, we will drop the legal description Data Type Definition since it is vague, and we will use ADMINISTRATIVE_BOUNDARIES for COMMON_LAND_UNIT
We currently have two items in the Standard Data Type definitions that may need cleanup since they are vague and/or US-Centric.
(Reference) LayerType: COMMON_LAND_UNIT. Perhaps we can generalize this to be "REFERENCE_BOUNDARIES" defined as a comprehensive layer of field boundaries as defined by a governmental or other external entity.
Textual DTD - "Legal Description". We added this one without a lot of discussion. Does it really only mean "PLSS Legal Description" within a US Geopolitical Context (and more specifically within PLSS states?) Furthermore, is the intent simply Township Range and Section or a more comprehensive cadastral definition such as the "south half of the northeast quarter, etc." If only PLSS TRS, then I suggest we call it that in some form.