|
1
|
SALVIAS,VegBIEN:/plotevent,Comments
|
|
2
|
plot_area_ha,//plot/area,"Brad: Area in hectares. Is there any way to store units?; Aaron: VegX plot area annotation says ""Total area of the plot in square meters."" so units are fixed"
|
|
3
|
elev_m,//plot/elevation,Brad: Mean elevation in meters. This is a constrained decimal value; is there no place for this in VegX other than verbatimElevation? Check with Nick.
|
|
4
|
country,"//*_ID/namedPlace[placeSystem=""area|country|territory""]/placeName",
|
|
5
|
pol1,"//*_ID/namedPlace[placeSystem=""region|state|province""]/placeName",Brad: No; pol1=stateProvince
|
|
6
|
major_geo,//*_ID/namedPlace[placeSystem=continent]/placeName,
|
|
7
|
pol2,//*_ID/namedPlace[placeSystem=county]/placeName,Brad: No pol2=countyParish
|
|
8
|
locality_description,//namedPlace/placeDescription,"Brad: No; this is free text description of locality where plot was situated, same as for DwC. Not a description of vegetation. Most likely='namedPlace.placeDescription' in VB; not sure about VX, again need to ask Nick where locality descriptions live in VX"
|
|
9
|
lat_decimal,//plot/realLatitude,
|
|
10
|
long_decimal,//plot/realLongitude,
|
|
11
|
slope_aspect,//plot/slopeAspect,
|
|
12
|
slope_gradient,//plot/slopeGradient,
|
|
13
|
elev_max_m,"/*_ID/plot/{elevation/_avg/max,elevationRange/_range/to}",
|
|
14
|
elev_min_m,"/*_ID/plot/{elevation/_avg/min,elevationRange/_range/from}",
|
|
15
|
project,//project/projectName,
|
|
16
|
life_zone_code,//*/commName,
|
|
17
|
holdridge_life_zone,//commConcept/commDescription,
|
|
18
|
precip_mm,"/definedValue[*_ID/userDefined[tableName=plotevent,userDefinedName=precipitationMm]]/definedValue",
|
|
19
|
temp_c,"/definedValue[*_ID/userDefined[tableName=plotevent,userDefinedName=temperatureC]]/definedValue",
|
|
20
|
plot_methodology,/methodNarrative,
|
|
21
|
date_finish,/obsEndDate/_date/date,
|
|
22
|
date_start,/obsStartDate/_date/date,
|
|
23
|
soil_acidity,"//soilObs/definedValue[*_ID/userDefined[tableName=soilObs,userDefinedName=soilAcidity]]/definedValue",
|
|
24
|
soil_base,"//soilObs/definedValue[*_ID/userDefined[tableName=soilObs,userDefinedName=soilBase]]/definedValue",
|
|
25
|
soil_Ca,"//soilObs/definedValue[*_ID/userDefined[tableName=soilObs,userDefinedName=soilCalcium]]/definedValue",
|
|
26
|
soil_C,"//soilObs/definedValue[*_ID/userDefined[tableName=soilObs,userDefinedName=soilCarbon]]/definedValue",
|
|
27
|
soil_cation_cap,"//soilObs/definedValue[*_ID/userDefined[tableName=soilObs,userDefinedName=soilCationCap]]/definedValue",
|
|
28
|
soil_conductivity,"//soilObs/definedValue[*_ID/userDefined[tableName=soilObs,userDefinedName=soilConductivity]]/definedValue",
|
|
29
|
soil_Mg,"//soilObs/definedValue[*_ID/userDefined[tableName=soilObs,userDefinedName=soilMagnesium]]/definedValue",
|
|
30
|
soil_N,"//soilObs/definedValue[*_ID/userDefined[tableName=soilObs,userDefinedName=soilNitrogen]]/definedValue",
|
|
31
|
soil_P,"//soilObs/definedValue[*_ID/userDefined[tableName=soilObs,userDefinedName=soilPhosphorus]]/definedValue",
|
|
32
|
soil_K,"//soilObs/definedValue[*_ID/userDefined[tableName=soilObs,userDefinedName=soilPotassium]]/definedValue",
|
|
33
|
soil_Na,"//soilObs/definedValue[*_ID/userDefined[tableName=soilObs,userDefinedName=soilSodium]]/definedValue",
|
|
34
|
clay_percent,//soilObs/soilClay,
|
|
35
|
organic_percent,//soilObs/soilOrganic,
|
|
36
|
pH,//soilObs/soilPH,"Brad: For all these soil variables, how do we store information on method, units. Seems like an ontological structure would be more appropriate (measurementName, measurementValue, measurementUnits, measurementMethod). Same as BIEN traits table. Something to discuss."
|
|
37
|
sand_percent,//soilObs/soilSand,
|
|
38
|
silt_percent,//soilObs/soilSilt,
|
|
39
|
soil_texture,//soilObs/soilTexture,
|
|
40
|
plot_code,"/{*_ID/plot/authorPlotCode/_alt/2,authorObsCode}",Brad: plotCode is as-assigned by data provider; guranteed to be unique only within dataset (=project)
|
