Revision 5535
Added by Aaron Marcuse-Kubitza over 12 years ago
inputs/SALVIAS-CSV/Organism/map.csv | ||
---|---|---|
16 | 16 |
ind_id,*ind_id,,Brad: OMIT |
17 | 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 | 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 |
x_position,organismX,,"Brad: These are important, fundamental values of many tree plots"
|
|
20 |
y_position,organismY,,Brad: See comment above for x_position
|
|
19 |
x_position,organismX_m,,"""x coordinate in meters"" (x_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: These are important, fundamental values of many tree plots"
|
|
20 |
y_position,organismY_m,,"""y coordinate in meters"" (y_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). 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." |
22 | 22 |
coll_number,catalogNumber,/_alt/1,Brad: Map instead as for voucher_string |
23 | 23 |
collector_code,*collector_code,,Brad: OMIT |
inputs/SALVIAS-CSV/Organism/VegBIEN.csv | ||
---|---|---|
53 | 53 |
stem_tag1,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/stemobservation/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." |
54 | 54 |
tag2,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/stemobservation/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." |
55 | 55 |
tag1,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/stemobservation/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." |
56 |
x_position,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/stemobservation/xposition_m,"Brad: These are important, fundamental values of many tree plots" |
|
57 |
y_position,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/stemobservation/yposition_m,Brad: See comment above for x_position
|
|
56 |
x_position,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/stemobservation/xposition_m,"""x coordinate in meters"" (x_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: These are important, fundamental values of many tree plots"
|
|
57 |
y_position,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/stemobservation/yposition_m,"""y coordinate in meters"" (y_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: See comment above for x_position"
|
|
58 | 58 |
PLOT_ID,"/location/locationevent/taxonoccurrence/authortaxoncode/_if[@name=""if in plot""]/cond/_exists", |
59 | 59 |
plot_code,"/location/locationevent/taxonoccurrence/authortaxoncode/_if[@name=""if in plot""]/cond/_exists", |
60 | 60 |
individual_code,"/location/locationevent/taxonoccurrence/authortaxoncode/_if[@name=""if in plot""]/then/_first/1/_first/1","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." |
inputs/SALVIAS-CSV/Organism/new_terms.csv | ||
---|---|---|
12 | 12 |
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." |
13 | 13 |
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." |
14 | 14 |
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." |
15 |
x_position,organismX,,"Brad: These are important, fundamental values of many tree plots"
|
|
16 |
y_position,organismY,,Brad: See comment above for x_position
|
|
15 |
x_position,organismX_m,,"""x coordinate in meters"" (x_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: These are important, fundamental values of many tree plots"
|
|
16 |
y_position,organismY_m,,"""y coordinate in meters"" (y_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: See comment above for x_position"
|
|
17 | 17 |
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." |
18 | 18 |
coll_number,catalogNumber,/_alt/1,Brad: Map instead as for voucher_string |
19 | 19 |
coll_lastname,recordedBy.surName,,"Brad: This is the collector of a separate specimen which vouchers this tree or species. I worry that vouchers are not properly accommodated in VegX. Again, we need to check with Nick." |
inputs/SALVIAS/plotObservations/map.csv | ||
---|---|---|
17 | 17 |
ind_id,*ind_id,,Brad: OMIT |
18 | 18 |
tag1,tag,/_alt/2,"The second tag supercedes the first. 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." |
19 | 19 |
tag2,tag,/_alt/1,"The second tag supercedes the first. 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 |
x_position,organismX,,"Brad: These are important, fundamental values of many tree plots"
|
|
21 |
y_position,organismY,,Brad: See comment above for x_position
|
|
20 |
x_position,organismX_m,,"""x coordinate in meters"" (x_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: These are important, fundamental values of many tree plots"
|
|
21 |
y_position,organismY_m,,"""y coordinate in meters"" (y_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: See comment above for x_position"
|
|
22 | 22 |
dist,*dist,, |
23 | 23 |
perp_dist,*perp_dist,, |
24 | 24 |
SourceVoucher,catalogNumber,/_alt/2,"Brad: OMIT. This is the verbatim text, which includes both collectors name and collection number. I would use coll_number, below." |
inputs/SALVIAS/plotObservations/VegBIEN.csv | ||
---|---|---|
48 | 48 |
ht_first_branch_m,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/stemobservation/heightfirstbranch_m, |
49 | 49 |
tag2,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/stemobservation/tag/_alt/1,"The second tag supercedes the first. Brad: See commend for tag1. Your mapping for tag2 looks correct. Probably both values would go here, only nested, with one superceding the other." |
50 | 50 |
tag1,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/stemobservation/tag/_alt/2,"The second tag supercedes the first. 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." |
51 |
x_position,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/stemobservation/xposition_m,"Brad: These are important, fundamental values of many tree plots" |
|
52 |
y_position,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/stemobservation/yposition_m,Brad: See comment above for x_position
|
|
51 |
x_position,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/stemobservation/xposition_m,"""x coordinate in meters"" (x_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: These are important, fundamental values of many tree plots"
|
|
52 |
y_position,/location/locationevent/taxonoccurrence/aggregateoccurrence/plantobservation/stemobservation/yposition_m,"""y coordinate in meters"" (y_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: See comment above for x_position"
|
|
53 | 53 |
PlotCode,"/location/locationevent/taxonoccurrence/authortaxoncode/_if[@name=""if in plot""]/cond/_exists", |
54 | 54 |
PlotID,"/location/locationevent/taxonoccurrence/authortaxoncode/_if[@name=""if in plot""]/cond/_exists", |
55 | 55 |
Ind,"/location/locationevent/taxonoccurrence/authortaxoncode/_if[@name=""if in plot""]/then/_first/1/_first/1","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." |
inputs/SALVIAS/plotObservations/new_terms.csv | ||
---|---|---|
13 | 13 |
Ind,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." |
14 | 14 |
tag1,tag,/_alt/2,"The second tag supercedes the first. 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." |
15 | 15 |
tag2,tag,/_alt/1,"The second tag supercedes the first. Brad: See commend for tag1. Your mapping for tag2 looks correct. Probably both values would go here, only nested, with one superceding the other." |
16 |
x_position,organismX,,"Brad: These are important, fundamental values of many tree plots"
|
|
17 |
y_position,organismY,,Brad: See comment above for x_position
|
|
16 |
x_position,organismX_m,,"""x coordinate in meters"" (x_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: These are important, fundamental values of many tree plots"
|
|
17 |
y_position,organismY_m,,"""y coordinate in meters"" (y_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: See comment above for x_position"
|
|
18 | 18 |
SourceVoucher,catalogNumber,/_alt/2,"Brad: OMIT. This is the verbatim text, which includes both collectors name and collection number. I would use coll_number, below." |
19 | 19 |
coll_number,catalogNumber,/_alt/1,Brad: Map instead as for voucher_string |
20 | 20 |
coll_lastname,recordedBy.surName,,"Brad: This is the collector of a separate specimen which vouchers this tree or species. I worry that vouchers are not properly accommodated in VegX. Again, we need to check with Nick." |
Also available in: Unified diff
inputs/SALVIAS/plotObservations/map.csv, inputs/SALVIAS-CSV/Organism/map.csv: x_position, y_position: Remapped to organismX_m/organismY_m using units from <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>