Revision 2013
Added by Aaron Marcuse-Kubitza about 12 years ago
| VegBIEN.organisms.csv | ||
|---|---|---|
| 26 | 26 |
height_m,/overallheight,Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob |
| 27 | 27 |
stem_height_m,/overallheight,"Brad: Same as for height, but applies to individuals stems, not trees. Rare." |
| 28 | 28 |
OBSERVATION_ID,/sourceaccessioncode,"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." |
| 29 |
tag1,"/stemobservation/stemtag[""""/iscurrent/_alt/2=true]/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.; Quotes sort it before tag2"
|
|
| 30 |
stem_tag1,"/stemobservation/stemtag[""""/iscurrent/_alt/2=true]/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.; Quotes sort it before tag2"
|
|
| 31 |
tag2,/stemobservation/stemtag[iscurrent=true]:[../stemtag?[iscurrent/_alt/2=true]/iscurrent/_alt/1=false]/tag/_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."
|
|
| 32 |
stem_tag2,/stemobservation/stemtag[iscurrent=true]:[../stemtag?[iscurrent/_alt/2=true]/iscurrent/_alt/1=false]/tag/_alt/2,Brad: see above
|
|
| 29 |
tag1,"/stemobservation/_collapse:[require=tag](/value/stemtag[""""/iscurrent/_alt/2=true])/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.; Quotes sort it before tag2"
|
|
| 30 |
stem_tag1,"/stemobservation/_collapse:[require=tag](/value/stemtag[""""/iscurrent/_alt/2=true])/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.; Quotes sort it before tag2"
|
|
| 31 |
tag2,/stemobservation/_collapse:[require=tag](/value/stemtag[iscurrent=true]:[../../../_collapse?(/value/stemtag[iscurrent/_alt/2=true])/iscurrent/_alt/1=false])/tag/_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."
|
|
| 32 |
stem_tag2,/stemobservation/_collapse:[require=tag](/value/stemtag[iscurrent=true]:[../../../_collapse?(/value/stemtag[iscurrent/_alt/2=true])/iscurrent/_alt/1=false])/tag/_alt/2,Brad: see above
|
|
| 33 | 33 |
x_position,/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." |
| 34 | 34 |
y_position,/stemobservation/yposition,Brad: See comment above for x_position |
| 35 | 35 |
basal_diam,,** No join mapping for /diameterBaseDistance[baseDistance/value=0]/diameter ** |
Also available in: Unified diff
mappings/VegX-VegBIEN.stems.csv: Added _collapse around subtrees that need to be removed if they are created around a NULL value