Revision 1059
Added by Aaron Marcuse-Kubitza almost 13 years ago
| VegBIEN.organisms.csv | ||
|---|---|---|
| 6 | 6 |
OBSERVATION_ID,/aggregateoccurrence/*_id/plantobservation/authorplantcode,"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." |
| 7 | 7 |
height_m,/aggregateoccurrence/*_id/plantobservation/overallheight,Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob |
| 8 | 8 |
stem_height_m,/aggregateoccurrence/*_id/plantobservation/overallheight,"Brad: Same as for height, but applies to individuals stems, not trees. Rare." |
| 9 |
stem_tag1,/aggregateoccurrence/*_id/plantobservation/stemobservation/authorstemcode,"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." |
|
| 10 |
stem_tag2,/aggregateoccurrence/*_id/plantobservation/stemobservation/authorstemcode,Brad: see above |
|
| 11 |
tag2,/aggregateoccurrence/*_id/plantobservation/stemobservation/authorstemcode/_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." |
|
| 12 |
tag1,/aggregateoccurrence/*_id/plantobservation/stemobservation/authorstemcode/_alt/2,"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." |
|
| 13 | 9 |
basal_diam,"/aggregateoccurrence/*_id/plantobservation/stemobservation/definedvalue[*_id/userdefined[tablename=stemobservation,userdefinedname=basalDiameter]]:[@fkey=tableRecord_ID]/definedvalue", |
| 14 | 10 |
stem_canopy_form,"/aggregateoccurrence/*_id/plantobservation/stemobservation/definedvalue[*_id/userdefined[tablename=stemobservation,userdefinedname=canopyForm]]:[@fkey=tableRecord_ID]/definedvalue",Brad: Should also be userDefined for VegBank. |
| 15 | 11 |
stem_canopy_position,"/aggregateoccurrence/*_id/plantobservation/stemobservation/definedvalue[*_id/userdefined[tablename=stemobservation,userdefinedname=canopyPosition]]:[@fkey=tableRecord_ID]/definedvalue",Brad: Should also be userDefined for VegBank. |
| ... | ... | |
| 17 | 13 |
stem_height_first_branch_m,"/aggregateoccurrence/*_id/plantobservation/stemobservation/definedvalue[*_id/userdefined[tablename=stemobservation,userdefinedname=heightFirstBranchM]]:[@fkey=tableRecord_ID]/definedvalue","Brad: Should also be userDefined for VegBank. Same as for ht_first_branch_m, but applies to individuals stems, not trees. Rare." |
| 18 | 14 |
stem_liana_infestation,"/aggregateoccurrence/*_id/plantobservation/stemobservation/definedvalue[*_id/userdefined[tablename=stemobservation,userdefinedname=lianaInfestation]]:[@fkey=tableRecord_ID]/definedvalue",Brad: Should also be userDefined for VegBank. |
| 19 | 15 |
stem_dbh,/aggregateoccurrence/*_id/plantobservation/stemobservation/diameter, |
| 16 |
stem_tag1,"/aggregateoccurrence/*_id/plantobservation/stemobservation/stemtag:[""""/iscurrent/_alt/2=true](/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.; Quotes sort it before tag2" |
|
| 17 |
stem_tag2,"/aggregateoccurrence/*_id/plantobservation/stemobservation/stemtag:[""""/iscurrent/_alt/2=true](/tag)",Brad: see above; Quotes sort it before tag2 |
|
| 18 |
tag1,"/aggregateoccurrence/*_id/plantobservation/stemobservation/stemtag:[""""/iscurrent/_alt/2=true](/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.; Quotes sort it before tag2" |
|
| 19 |
tag2,"/aggregateoccurrence/*_id/plantobservation/stemobservation/stemtag:[../stemtag[iscurrent/_alt/2=true]/iscurrent/_alt/1=false,iscurrent=true](/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." |
|
| 20 | 20 |
x_position,/aggregateoccurrence/*_id/plantobservation/stemobservation/xposition,"Brad: Correct for VegBank. I'm not so sure for VegX. Let's ask Nick about this. These are important, fundamental values of many tree plots, and should be accommodated within VegX." |
| 21 | 21 |
y_position,/aggregateoccurrence/*_id/plantobservation/stemobservation/yposition,Brad: See comment above for x_position |
| 22 | 22 |
no_of_individuals,/aggregateoccurrence/count,"Brad: Incorrect for VegX. 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." |
Also available in: Unified diff
VegX-VegBIEN mapping: Mapped stem tags to new stemtag table