Currently, hasLatewood is tied to Dendro Elevator assets under meta data. As it controls how many increments there are per year, it is not truly metadata. It would be better suited to live in the JSON data, so when data is downloaded, it's status is obvious (one or two increments per year).
Also, it would allow the user to easily change the amount of increments they want to measure per year.
Currently, hasLatewood is tied to Dendro Elevator assets under meta data. As it controls how many increments there are per year, it is not truly metadata. It would be better suited to live in the JSON data, so when data is downloaded, it's status is obvious (one or two increments per year).
Also, it would allow the user to easily change the amount of increments they want to measure per year.