Revision 490
Added by Aaron Marcuse-Kubitza almost 13 years ago
SALVIAS_db-VegBIEN.organisms.csv | ||
---|---|---|
4 | 4 |
NoInd,/aggregateoccurrence/count/_alt/1,"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." |
5 | 5 |
cover_percent,/aggregateoccurrence/cover, |
6 | 6 |
intercept_cm,"/aggregateoccurrence/definedvalue[*_id/userdefined[tablename=aggregateoccurrence,userdefinedname=interceptCm]:[userdefinedtype=varchar]]:[@fkey=tableRecord_ID]/definedvalue","Brad: Incorrect for VegBank 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." |
7 |
temp_dbh,/aggregateoccurrence/individualplant/diameter, |
|
8 |
height_m,/aggregateoccurrence/individualplant/height,Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob |
|
7 | 9 |
tag2,/aggregateoccurrence/individualplant/stem/authorcode/_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." |
8 | 10 |
tag1,/aggregateoccurrence/individualplant/stem/authorcode/_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." |
9 | 11 |
ht_first_branch_m,"/aggregateoccurrence/individualplant/stem/definedvalue[*_id/userdefined[tablename=stem,userdefinedname=heightFirstBranchM]:[userdefinedtype=varchar]]:[@fkey=tableRecord_ID]/definedvalue",Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob |
10 |
x_position,/aggregateoccurrence/individualplant/stem/stemxposition,"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." |
|
11 |
y_position,/aggregateoccurrence/individualplant/stem/stemyposition,Brad: See comment above for x_position |
|
12 |
temp_dbh,/aggregateoccurrence/individualplant/stemdiameter, |
|
13 |
height_m,/aggregateoccurrence/individualplant/stemheight,Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob |
|
12 |
x_position,/aggregateoccurrence/individualplant/stem/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." |
|
13 |
y_position,/aggregateoccurrence/individualplant/stem/yposition,Brad: See comment above for x_position |
|
14 | 14 |
census_date,/taxondetermination[role_id/aux_role/rolecode=collector]/collectiondate/_date/date, |
15 | 15 |
coll_number,/taxondetermination[role_id/aux_role/rolecode=collector]/collectionnumber,Brad: Incorrect. Map instead as for voucher_string |
16 | 16 |
coll_firstname,"/taxondetermination[role_id/aux_role/rolecode=collector]/collector_id/party/{givenname/_namePart/first,middlename/_namePart/last}",Brad: See comment above |
Also available in: Unified diff
VegBIEN: Removed stem* prefix from stem measurements because it's redundant and because these same field names were reused in non-stem tables