| 1 |
4857
|
aaronmk
|
OBSERVATION_ID,individualID,,"Brad: Neither is correct; this is just an internal ID for table plotObservations. However, it has the important property of uniquely identifying an ""observation"", which is an individual tree, in the case of an individual observation, or a records of a species with an associated count of individuals or measurement of percent cover, in the case of aggregate observations. Not sure where to store this. Main point is that it is not part of the original data, but an auto_increment added later."
|
| 2 |
6542
|
aaronmk
|
plot_code,locationName,,
|
| 3 |
4857
|
aaronmk
|
census_date,eventDate,,"This is for the subplot, not the organism, as all organisms in a subplot have the same value for it. The following query returns no rows:
|
| 4 |
|
|
-----
|
| 5 |
|
|
SELECT ""PLOT_ID"", subplot, count(DISTINCT census_date) AS census_date_count
|
| 6 |
|
|
FROM ""SALVIAS-CSV"".organisms
|
| 7 |
|
|
WHERE subplot IS NOT NULL AND census_date IS NOT NULL
|
| 8 |
|
|
GROUP BY ""PLOT_ID"", subplot
|
| 9 |
|
|
HAVING count(DISTINCT census_date) > 1
|
| 10 |
|
|
-----"
|
| 11 |
|
|
tag1,tag,/_alt/2/_alt/2,"The second tag supercedes the first. The stem tag supercedes the tree tag. Brad: Another type of code, typically a number, used by the original data provider to indicate an individual tree. These are numbers on physical tags attached to the tree. Tag2 Is the same thing, only used if the first tag was lost. Obviously not a good system as it's possible a tree tag could be lost and changed more than once."
|
| 12 |
5535
|
aaronmk
|
x_position,organismX_m,,"""x coordinate in meters"" (x_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: These are important, fundamental values of many tree plots"
|
| 13 |
|
|
y_position,organismY_m,,"""y coordinate in meters"" (y_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: See comment above for x_position"
|
| 14 |
7199
|
aaronmk
|
voucher_string,recordNumber,/_alt/2,"Brad: OMIT. This is the verbatim text, which includes both collectors name and collection number. I would use coll_number, below."
|
| 15 |
|
|
coll_number,recordNumber,/_alt/1,Brad: Map instead as for voucher_string
|
| 16 |
6831
|
aaronmk
|
coll_lastname,recordedBy_surName,,"Brad: This is the collector of a separate specimen which vouchers this tree or species. I worry that vouchers are not properly accommodated in VegX. Again, we need to check with Nick."
|
| 17 |
|
|
coll_firstname,recordedBy_givenName,,Brad: See comment above
|
| 18 |
4857
|
aaronmk
|
specific_authority,scientificNameAuthorship,,Brad: This is the author of the scientificName.
|
| 19 |
|
|
infra_rank_1,taxonRank,,
|
| 20 |
|
|
infra_ep_1,infraspecificEpithet,,
|
| 21 |
|
|
no_of_individuals,individualCount,,"Brad: This is a count of number of indiiduals for an *aggregate* observation. For VegBank, I'm not sure. Not exactly the same as stemCount. An individual tree could have 3 stems but would still only count as 1. We need to check with Bob on this."
|
| 22 |
|
|
stem_tag1,tag,/_alt/1/_alt/2,"The second tag supercedes the first. The stem tag supercedes the tree tag. Brad: Same as tag1 & tag2, but applied to individual stems. I'm still not clear how to distinguish between methods which tag only individuals trees, and those which tag individual stems."
|
| 23 |
5556
|
aaronmk
|
stem_height_m,height_m,/_alt/1,"""Total height of this stem only, in meters"" (stem_height_m definition at < http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: Same as for height, but applies to individuals stems, not trees. Rare."
|
| 24 |
7469
|
aaronmk
|
stem_height_first_branch_m,heightFirstBranch_m,,"Brad: Same as for ht_first_branch_m, but applies to individuals stems, not trees. Rare."
|
| 25 |
5062
|
aaronmk
|
orig_family,originalFamily,,Brad: OMIT
|
| 26 |
|
|
orig_species,originalSpecificEpithet,,Brad: OMIT
|
