/ - Diff - BIEN 3 - NCEAS Projects

                 <stemCount>
                     <stemCount>1</stemCount>
                     <individual>
                         <stemCode>7</stemCode>
                         <stemCode>8</stemCode>
                     </individual>
                     <stemDiameter>662</stemDiameter>
-...
                 <stemCount>
                     <stemCount>1</stemCount>
                     <individual>
                         <stemCode>84</stemCode>
                         <stemCode>91</stemCode>
                     </individual>
                     <stemDiameter>215</stemDiameter>

         <individualOrganisms>
             <individualOrganism id="0">
                 <taxonNameUsageConceptsID>0</taxonNameUsageConceptsID>
                 <identificationLabel>7</identificationLabel>
                 <identificationLabel>8</identificationLabel>
             </individualOrganism>
             <individualOrganism id="1">
                 <taxonNameUsageConceptsID>1</taxonNameUsageConceptsID>
                 <identificationLabel>84</identificationLabel>
                 <identificationLabel>91</identificationLabel>
             </individualOrganism>
         </individualOrganisms>

     "/simpleUserdefined[name=substrate]/value","/taxonImportance/stemCount/stemLocation/definedValue[*_ID/userDefined[tableName=stemLocation,userDefinedName=substrate]:[userDefinedType=varchar]]:[@fkey=tableRecord_ID]/definedValue"
     "/simpleUserdefined[name=vegetation]/value","/taxonImportance/stemCount/stemLocation/definedValue[*_ID/userDefined[tableName=stemLocation,userDefinedName=vegetation]:[userDefinedType=varchar]]:[@fkey=tableRecord_ID]/definedValue"
     "/*ID->/*s/individualOrganism/identificationLabel","/taxonImportance/stemCount/stemLocation/stemCode"
     "/*ID->/*s/individualOrganism/identificationLabel/_alt/1","/taxonImportance/stemCount/stemLocation/stemCode/_alt/1"
     "/*ID->/*s/individualOrganism/identificationLabel/_alt/2","/taxonImportance/stemCount/stemLocation/stemCode/_alt/2"
     "/simpleUserdefined[name=xPosition]/value","/taxonImportance/stemCount/stemLocation/stemXPosition"
     "/simpleUserdefined[name=yPosition]/value","/taxonImportance/stemCount/stemLocation/stemYPosition"
     "/*ID->/*s/individualOrganism/*sID->/*s/taxonNameUsageConcept/authorCode","/taxonInterpretation[ROLE_ID/aux_Role/roleCode=collector]/collectionNumber"

     cover_percent,/collectiveobs/cover,
     intercept_cm,"/collectiveobs/definedValue[*_ID/userDefined[tableName=collectiveobs,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."
     ht_first_branch_m,"/collectiveobs/stemCount/individual/definedValue[*_ID/userDefined[tableName=individual,userDefinedName=heightFirstBranchM]:[userDefinedType=varchar]]:[@fkey=tableRecord_ID]/definedValue",Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob
     tag1,/collectiveobs/stemCount/individual/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."
     tag2,/collectiveobs/stemCount/individual/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."
     tag2,/collectiveobs/stemCount/individual/stemCode/_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."
     tag1,/collectiveobs/stemCount/individual/stemCode/_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."
     x_position,/collectiveobs/stemCount/individual/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."
     y_position,/collectiveobs/stemCount/individual/stemYPosition,Brad: See comment above for x_position
     temp_dbh,/collectiveobs/stemCount/stemDiameter,

     /simpleUserdefined[name=substrate]/value,"/collectiveobs/stemCount/individual/definedValue[*_ID/userDefined[tableName=individual,userDefinedName=substrate]:[userDefinedType=varchar]]:[@fkey=tableRecord_ID]/definedValue"
     /simpleUserdefined[name=vegetation]/value,"/collectiveobs/stemCount/individual/definedValue[*_ID/userDefined[tableName=individual,userDefinedName=vegetation]:[userDefinedType=varchar]]:[@fkey=tableRecord_ID]/definedValue"
     /*ID->/*s/individualOrganism/identificationLabel,/collectiveobs/stemCount/individual/stemCode
     /*ID->/*s/individualOrganism/identificationLabel/_alt/1,/collectiveobs/stemCount/individual/stemCode/_alt/1
     /*ID->/*s/individualOrganism/identificationLabel/_alt/2,/collectiveobs/stemCount/individual/stemCode/_alt/2
     /simpleUserdefined[name=xPosition]/value,/collectiveobs/stemCount/individual/stemXPosition
     /simpleUserdefined[name=yPosition]/value,/collectiveobs/stemCount/individual/stemYPosition
     /diameterBaseDistance[baseDistance=1.37]/diameter,/collectiveobs/stemCount/stemDiameter

     "subplot","/*ID->/*s/plotObservation/*UniqueIdentifierID->/*s/plot/plotUniqueIdentifier",
     "individual_code","/simpleUserdefined[name=individualCode]/value","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."
     "ind_id",,"Brad: OMIT"
     "tag1","/*ID->/*s/individualOrganism/identificationLabel","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."
     "tag2","/*ID->/*s/individualOrganism/identificationLabel","Brad: See commend for tag1. Your mapping for tag2 looks correct. Probably both values would go here, only nested, with one superceding the other."
     "tag1","/*ID->/*s/individualOrganism/identificationLabel/_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."
     "tag2","/*ID->/*s/individualOrganism/identificationLabel/_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."
     "x_position","/simpleUserdefined[name=xPosition]/value","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."
     "y_position","/simpleUserdefined[name=yPosition]/value","Brad: See comment above for x_position"
     "voucher_string",,"Brad: OMIT. This is the verbatim text, which includes both collectors name and collection number. I would use coll_number, below."

     /simpleUserdefined[name=substrate]/value,"//stemLocation/definedValue[*_ID/userDefined[tableName=stemLocation,userDefinedName=substrate]]/definedValue"
     /simpleUserdefined[name=vegetation]/value,"//stemLocation/definedValue[*_ID/userDefined[tableName=stemLocation,userDefinedName=vegetation]]/definedValue"
     //individualOrganism/identificationLabel,//stemLocation/stemCode
     //individualOrganism/identificationLabel/_alt/1,//stemLocation/stemCode/_alt/1
     //individualOrganism/identificationLabel/_alt/2,//stemLocation/stemCode/_alt/2
     /simpleUserdefined[name=xPosition]/value,//stemLocation/stemXPosition
     /simpleUserdefined[name=yPosition]/value,//stemLocation/stemYPosition
     //taxonNameUsageConcept/authorCode,/taxonInterpretation[roleCode=collector]/collectionNumber

     cover_percent,//collectiveobs/cover,
     intercept_cm,"//collectiveobs/definedValue[*_ID/userDefined[tableName=collectiveobs,userDefinedName=interceptCm]]/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."
     ht_first_branch_m,"//individual/definedValue[*_ID/userDefined[tableName=individual,userDefinedName=heightFirstBranchM]]/definedValue",Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob
     tag1,//individual/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."
     tag2,//individual/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."
     tag2,//individual/stemCode/_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."
     tag1,//individual/stemCode/_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."
     x_position,//individual/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."
     y_position,//individual/stemYPosition,Brad: See comment above for x_position
     temp_dbh,//stemCount/stemDiameter,

     /simpleUserdefined[name=substrate]/value,"//individual/definedValue[*_ID/userDefined[tableName=individual,userDefinedName=substrate]]/definedValue"
     /simpleUserdefined[name=vegetation]/value,"//individual/definedValue[*_ID/userDefined[tableName=individual,userDefinedName=vegetation]]/definedValue"
     //individualOrganism/identificationLabel,//individual/stemCode
     //individualOrganism/identificationLabel/_alt/1,//individual/stemCode/_alt/1
     //individualOrganism/identificationLabel/_alt/2,//individual/stemCode/_alt/2
     /simpleUserdefined[name=xPosition]/value,//individual/stemXPosition
     /simpleUserdefined[name=yPosition]/value,//individual/stemYPosition
     /diameterBaseDistance[baseDistance=1.37]/diameter,//stemCount/stemDiameter

     subplot,//plot/plotUniqueIdentifier,
     individual_code,/simpleUserdefined[name=individualCode]/value,"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."
     ind_id,,Brad: OMIT
     tag1,//individualOrganism/identificationLabel,"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."
     tag2,//individualOrganism/identificationLabel,"Brad: See commend for tag1. Your mapping for tag2 looks correct. Probably both values would go here, only nested, with one superceding the other."
     tag1,//individualOrganism/identificationLabel/_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."
     tag2,//individualOrganism/identificationLabel/_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."
     x_position,/simpleUserdefined[name=xPosition]/value,"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."
     y_position,/simpleUserdefined[name=yPosition]/value,Brad: See comment above for x_position
     voucher_string,,"Brad: OMIT. This is the verbatim text, which includes both collectors name and collection number. I would use coll_number, below."

     stem_liana_infestation,"//stemLocation/definedValue[*_ID/userDefined[tableName=stemLocation,userDefinedName=stemLianaInfestation]]/definedValue",Brad: Should also be userDefined for VegBank.
     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."
     stem_tag2,//stemLocation/stemCode,Brad: see above
     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."
     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."
     tag2,//stemLocation/stemCode/_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."
     tag1,//stemLocation/stemCode/_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."
     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."
     y_position,//stemLocation/stemYPosition,Brad: See comment above for x_position
     coll_number,/taxonInterpretation[roleCode=collector]/collectionNumber,Brad: Incorrect. Map instead as for voucher_string

     Line,,
     Ind,/simpleUserdefined[name=individualCode]/value,"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."
     ind_id,,Brad: OMIT
     tag1,//individualOrganism/identificationLabel,"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."
     tag2,//individualOrganism/identificationLabel,"Brad: See commend for tag1. Your mapping for tag2 looks correct. Probably both values would go here, only nested, with one superceding the other."
     tag1,//individualOrganism/identificationLabel/_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."
     tag2,//individualOrganism/identificationLabel/_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."
     x_position,/simpleUserdefined[name=xPosition]/value,"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."
     y_position,/simpleUserdefined[name=yPosition]/value,Brad: See comment above for x_position
     dist,,

     stem_liana_infestation,"//individual/definedValue[*_ID/userDefined[tableName=individual,userDefinedName=stemLianaInfestation]]/definedValue",Brad: Should also be userDefined for VegBank.
     stem_tag1,//individual/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."
     stem_tag2,//individual/stemCode,Brad: see above
     tag1,//individual/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."
     tag2,//individual/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."
     tag2,//individual/stemCode/_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."
     tag1,//individual/stemCode/_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."
     x_position,//individual/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."
     y_position,//individual/stemYPosition,Brad: See comment above for x_position
     stem_dbh,//stemCount/stemDiameter,

     temp_dbh,//stemCount/stemDiameter,
     height_m,//stemCount/stemHeight,Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob
     ht_first_branch_m,"//stemLocation/definedValue[*_ID/userDefined[tableName=stemLocation,userDefinedName=heightFirstBranchM]]/definedValue",Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob
     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."
     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."
     tag2,//stemLocation/stemCode/_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."
     tag1,//stemLocation/stemCode/_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."
     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."
     y_position,//stemLocation/stemYPosition,Brad: See comment above for x_position
     coll_number,/taxonInterpretation[roleCode=collector]/collectionNumber,Brad: Incorrect. Map instead as for voucher_string

     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.
     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."
     stem_tag2,/taxonImportance/stemCount/stemLocation/stemCode,Brad: see above
     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."
     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."
     tag2,/taxonImportance/stemCount/stemLocation/stemCode/_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."
     tag1,/taxonImportance/stemCount/stemLocation/stemCode/_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."
     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."
     y_position,/taxonImportance/stemCount/stemLocation/stemYPosition,Brad: See comment above for x_position
     coll_number,/taxonInterpretation[ROLE_ID/aux_Role/roleCode=collector]/collectionNumber,Brad: Incorrect. Map instead as for voucher_string

     "Line",,
     "Ind","/simpleUserdefined[name=individualCode]/value","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."
     "ind_id",,"Brad: OMIT"
     "tag1","/*ID->/*s/individualOrganism/identificationLabel","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."
     "tag2","/*ID->/*s/individualOrganism/identificationLabel","Brad: See commend for tag1. Your mapping for tag2 looks correct. Probably both values would go here, only nested, with one superceding the other."
     "tag1","/*ID->/*s/individualOrganism/identificationLabel/_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."
     "tag2","/*ID->/*s/individualOrganism/identificationLabel/_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."
     "x_position","/simpleUserdefined[name=xPosition]/value","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."
     "y_position","/simpleUserdefined[name=yPosition]/value","Brad: See comment above for x_position"
     "dist",,

     stem_liana_infestation,"/collectiveobs/stemCount/individual/definedValue[*_ID/userDefined[tableName=individual,userDefinedName=stemLianaInfestation]:[userDefinedType=varchar]]:[@fkey=tableRecord_ID]/definedValue",Brad: Should also be userDefined for VegBank.
     stem_tag1,/collectiveobs/stemCount/individual/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."
     stem_tag2,/collectiveobs/stemCount/individual/stemCode,Brad: see above
     tag1,/collectiveobs/stemCount/individual/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."
     tag2,/collectiveobs/stemCount/individual/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."
     tag2,/collectiveobs/stemCount/individual/stemCode/_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."
     tag1,/collectiveobs/stemCount/individual/stemCode/_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."
     x_position,/collectiveobs/stemCount/individual/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."
     y_position,/collectiveobs/stemCount/individual/stemYPosition,Brad: See comment above for x_position
     stem_dbh,/collectiveobs/stemCount/stemDiameter,

     temp_dbh,/taxonImportance/stemCount/stemDiameter,
     height_m,/taxonImportance/stemCount/stemHeight,Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob
     ht_first_branch_m,"/taxonImportance/stemCount/stemLocation/definedValue[*_ID/userDefined[tableName=stemLocation,userDefinedName=heightFirstBranchM]:[userDefinedType=varchar]]:[@fkey=tableRecord_ID]/definedValue",Brad: Incorrect for VegBank. This is a measurement applied to a single tree. Check with Bob
     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."
     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."
     tag2,/taxonImportance/stemCount/stemLocation/stemCode/_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."
     tag1,/taxonImportance/stemCount/stemLocation/stemCode/_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."
     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."
     y_position,/taxonImportance/stemCount/stemLocation/stemYPosition,Brad: See comment above for x_position
     coll_number,/taxonInterpretation[ROLE_ID/aux_Role/roleCode=collector]/collectionNumber,Brad: Incorrect. Map instead as for voucher_string

Project

General

Profile

Revision 320

Added by Aaron Marcuse-Kubitza almost 13 years ago