Revision 570
Added by Aaron Marcuse-Kubitza almost 13 years ago
| VegBIEN.organisms.csv | ||
|---|---|---|
| 1 | 1 |
SALVIAS:plotObservations,VegBIEN:/taxonoccurrence,Comments |
| 2 |
PlotID,/*_id/locationevent/sourceid/_alt/1,"Brad: Not sure why this is repeated? This field and plotCode, as the same as above."
|
|
| 2 |
PlotID,/*_id/locationevent/authoreventcode/_alt/1,"Brad: Not sure why this is repeated? This field and plotCode, as the same as above."
|
|
| 3 | 3 |
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." |
| 4 | 4 |
cover_percent,/aggregateoccurrence/cover, |
| 5 | 5 |
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." |
| 6 | 6 |
height_m,/aggregateoccurrence/individualplant/overallheight,Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob |
| 7 |
tag2,/aggregateoccurrence/individualplant/stem/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." |
|
| 8 |
tag1,/aggregateoccurrence/individualplant/stem/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." |
|
| 7 | 9 |
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 |
| 8 | 10 |
temp_dbh,/aggregateoccurrence/individualplant/stem/diameter, |
| 9 |
tag2,/aggregateoccurrence/individualplant/stem/sourceid/_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." |
|
| 10 |
tag1,/aggregateoccurrence/individualplant/stem/sourceid/_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." |
|
| 11 | 11 |
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." |
| 12 | 12 |
y_position,/aggregateoccurrence/individualplant/stem/yposition,Brad: See comment above for x_position |
| 13 | 13 |
coll_number,/specimen:[*_id/reference]/catalognumber_dwc,Brad: Incorrect. Map instead as for voucher_string |
| ... | ... | |
| 28 | 28 |
infra_ep_1,"/taxondetermination[role_id/aux_role/rolecode=computer,*_id/plantconcept/plantstatus/plantlevel=Subspecies]:[determinationtype=""Computer (automated)"",originaldetermination=false,currentdetermination=true,determinationdate=epoch,*_id/party]/*_id/plantconcept:[plantstatus:[plantconceptstatus=accepted,startdate=epoch,*_id/party],*_id/reference]/_name/last", |
| 29 | 29 |
OrigFamily,"/taxondetermination[role_id/aux_role/rolecode=identifier,*_id/plantconcept/plantstatus/plantlevel=Family]:[determinationtype=Author,originaldetermination=true,currentdetermination=true,determinationdate=epoch,*_id/party]/*_id/plantconcept:[plantstatus:[plantconceptstatus=accepted,startdate=epoch,*_id/party],*_id/reference]/*_id/*/plantname",Brad: OMIT |
| 30 | 30 |
OrigSpecies,"/{taxondetermination[role_id/aux_role/rolecode=collector]:[determinationtype=Author,originaldetermination=true,currentdetermination=true,determinationdate=epoch,*_id/party]/*_id/plantconcept:[*_id/reference]/*_id/*/plantname/_alt/2,taxondetermination[role_id/aux_role/rolecode=identifier,*_id/plantconcept/plantstatus/plantlevel=Species]:[determinationtype=Author,originaldetermination=true,currentdetermination=true,determinationdate=epoch,*_id/party]/*_id/plantconcept:[plantstatus:[plantconceptstatus=accepted,startdate=epoch,*_id/party],*_id/reference]/*_id/*/plantname}",Brad: OMIT
|
| 31 |
PlotObsID,":[aggregateoccurrence/count/_alt/2=1]/{aggregateoccurrence/individualplant/sourceid,specimen:[*_id/reference]/sourceaccessionnumber,*_id/locationevent/sourceid/_alt/2,*_id/locationevent/*_id/location:[confidentialitystatus=0]/sourceid/_alt/3}","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."
|
|
| 31 |
PlotObsID,":[aggregateoccurrence/count/_alt/2=1]/{aggregateoccurrence/individualplant/authorplantcode,specimen:[*_id/reference]/sourceaccessionnumber,*_id/locationevent/authoreventcode/_alt/2,*_id/locationevent/*_id/location:[confidentialitystatus=0]/authorlocationcode/_alt/3}","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."
|
|
Also available in: Unified diff
VegBIEN: Renamed sourceid to author*code