Revision 193
Added by Aaron Marcuse-Kubitza almost 13 years ago
mappings/join_all_vegbank | ||
---|---|---|
8 | 8 |
type="${map%.*}" # remove extension |
9 | 9 |
type="${type#*.}" # remove up to last "." |
10 | 10 |
../scripts/util/join <"$map" "VegX-VegBank.$type.csv"|\ |
11 |
../scripts/util/sort 1 >"${map/VegX/VegBank}" # sort on output col |
|
11 |
../scripts/util/sort 1 0 >"${map/VegX/VegBank}" # sort on output col
|
|
12 | 12 |
done |
mappings/for_review/SALVIAS-VegBank.organisms.csv | ||
---|---|---|
14 | 14 |
stem_canopy_position,"//stemLocation/definedValue[*_ID/userDefined[tableName=stemLocation,userDefinedName=stemCanopyPosition]]/definedValue",Brad: Should also be userDefined for VegBank. |
15 | 15 |
stem_height_first_branch_m,"//stemLocation/definedValue[*_ID/userDefined[tableName=stemLocation,userDefinedName=stemHeightFirstBranchM]]/definedValue","Brad: Should also be userDefined for VegBank. Same as for ht_first_branch_m, but applies to individuals stems, not trees. Rare." |
16 | 16 |
stem_liana_infestation,"//stemLocation/definedValue[*_ID/userDefined[tableName=stemLocation,userDefinedName=stemLianaInfestation]]/definedValue",Brad: Should also be userDefined for VegBank. |
17 |
stem_tag1,//stemLocation/stemCode,"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." |
|
18 |
stem_tag2,//stemLocation/stemCode,Brad: see above |
|
17 | 19 |
tag1,//stemLocation/stemCode,"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 | 20 |
tag2,//stemLocation/stemCode,"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 |
stem_tag1,//stemLocation/stemCode,"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." |
|
20 |
stem_tag2,//stemLocation/stemCode,Brad: see above |
|
21 | 21 |
x_position,//stemLocation/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." |
22 | 22 |
y_position,//stemLocation/stemYPosition,Brad: See comment above for x_position |
23 | 23 |
coll_number,/taxonInterpretation[roleCode=collector]/collectionNumber,Brad: Incorrect. Map instead as for voucher_string |
mappings/SALVIAS-VegBank.organisms.csv | ||
---|---|---|
14 | 14 |
stem_canopy_position,"/taxonImportance/stemCount/stemLocation/definedValue[*_ID/userDefined[tableName=stemLocation,userDefinedName=stemCanopyPosition]:[userDefinedType=varchar]]:[@fkey=tableRecord_ID]/definedValue",Brad: Should also be userDefined for VegBank. |
15 | 15 |
stem_height_first_branch_m,"/taxonImportance/stemCount/stemLocation/definedValue[*_ID/userDefined[tableName=stemLocation,userDefinedName=stemHeightFirstBranchM]:[userDefinedType=varchar]]:[@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." |
16 | 16 |
stem_liana_infestation,"/taxonImportance/stemCount/stemLocation/definedValue[*_ID/userDefined[tableName=stemLocation,userDefinedName=stemLianaInfestation]:[userDefinedType=varchar]]:[@fkey=tableRecord_ID]/definedValue",Brad: Should also be userDefined for VegBank. |
17 |
stem_tag1,/taxonImportance/stemCount/stemLocation/stemCode,"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." |
|
18 |
stem_tag2,/taxonImportance/stemCount/stemLocation/stemCode,Brad: see above |
|
17 | 19 |
tag1,/taxonImportance/stemCount/stemLocation/stemCode,"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 | 20 |
tag2,/taxonImportance/stemCount/stemLocation/stemCode,"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 |
stem_tag1,/taxonImportance/stemCount/stemLocation/stemCode,"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." |
|
20 |
stem_tag2,/taxonImportance/stemCount/stemLocation/stemCode,Brad: see above |
|
21 | 21 |
x_position,/taxonImportance/stemCount/stemLocation/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." |
22 | 22 |
y_position,/taxonImportance/stemCount/stemLocation/stemYPosition,Brad: See comment above for x_position |
23 | 23 |
coll_number,/taxonInterpretation[ROLE_ID/aux_Role/roleCode=collector]/collectionNumber,Brad: Incorrect. Map instead as for voucher_string |
Also available in: Unified diff
join_all_vegbank: Sort output by both columns