Revision 4824
Added by Aaron Marcuse-Kubitza about 12 years ago
| map.csv | ||
|---|---|---|
| 3 | 3 |
PLOT_ID,locationID,, |
| 4 | 4 |
plot_code,plotName,, |
| 5 | 5 |
census_no,censusNumber,,"Brad: Assigned by SALVIAS. 1 for first plot, then 2, 3, etc. I can't recall if we even have repeat censuses in SALVIAS. Probably not." |
| 6 |
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:
|
|
| 7 |
-----
|
|
| 8 |
SELECT ""PLOT_ID"", subplot, count(DISTINCT census_date) AS census_date_count
|
|
| 9 |
FROM ""SALVIAS-CSV"".organisms
|
|
| 10 |
WHERE subplot IS NOT NULL AND census_date IS NOT NULL
|
|
| 11 |
GROUP BY ""PLOT_ID"", subplot
|
|
| 12 |
HAVING count(DISTINCT census_date) > 1
|
|
| 6 |
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: |
|
| 7 |
----- |
|
| 8 |
SELECT ""PLOT_ID"", subplot, count(DISTINCT census_date) AS census_date_count |
|
| 9 |
FROM ""SALVIAS-CSV"".organisms |
|
| 10 |
WHERE subplot IS NOT NULL AND census_date IS NOT NULL |
|
| 11 |
GROUP BY ""PLOT_ID"", subplot |
|
| 12 |
HAVING count(DISTINCT census_date) > 1 |
|
| 13 | 13 |
-----" |
| 14 | 14 |
subplot,subplot,, |
| 15 | 15 |
individual_code,recordNumber,,"Brad: Code, if any, used by the data provider to indicate an individual tree. Scope is unknown, although typically this value is unique only within plot, or sometimes only within subplot." |
| 16 | 16 |
ind_id,ind_id,,Brad: OMIT |
| 17 |
tag1,tag,/_alt/1,"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."
|
|
| 18 |
tag2,previousTag,/_alt/1,"Brad: See commend for tag1. Your mapping for tag2 looks correct. Probably both values would go here, only nested, with one superceding the other."
|
|
| 17 |
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."
|
|
| 18 |
tag2,tag,/_alt/2/_alt/1,"The second tag supercedes the first. The stem tag supercedes the tree tag. Brad: See commend for tag1. Your mapping for tag2 looks correct. Probably both values would go here, only nested, with one superceding the other."
|
|
| 19 | 19 |
x_position,organismX,,"Brad: These are important, fundamental values of many tree plots" |
| 20 | 20 |
y_position,organismY,,Brad: See comment above for x_position |
| 21 | 21 |
voucher_string,catalogNumber,/_alt/2,"Brad: OMIT. This is the verbatim text, which includes both collectors name and collection number. I would use coll_number, below." |
| ... | ... | |
| 41 | 41 |
intercept_cm,intercept_cm,,"Brad: This is an aggregate observation. Used in line-intercept methodology only, describes the point along centerline at which an individual intercepts the center line of the plot. Used to determin relative abundance." |
| 42 | 42 |
height_m,height,/_alt/2, |
| 43 | 43 |
ht_first_branch_m,heightFirstBranch,, |
| 44 |
stem_tag1,tag,/_alt/2,"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."
|
|
| 45 |
stem_tag2,previousTag,/_alt/2,Brad: see above
|
|
| 44 |
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."
|
|
| 45 |
stem_tag2,tag,/_alt/1/_alt/1,The second tag supercedes the first. The stem tag supercedes the tree tag. Brad: see above
|
|
| 46 | 46 |
stem_dbh,diameterBreastHeight,, |
| 47 | 47 |
basal_diam,basalDiameter,, |
| 48 | 48 |
stem_height_m,height,/_alt/1,"Brad: Same as for height, but applies to individuals stems, not trees. Rare." |
Also available in: Unified diff
inputs/SALVIAS/*/map.csv: Remapped all versions of stem and tree tags to tag, with the second tag superceding the first, to avoid the complex VegCore-VegBIEN mapping logic that attempts to place both tags in VegBIEN in the correct order but does not work for column-based import. inputs/SALVIAS-CSV/Organism/map.csv: stem and tree tags: Made the stem tag supercede the tree tag instead of vice versa, to have as specific of a tag as possible.