plot_code,"/location/_if[@name=""if subplot""]/else/authorlocationcode/_first/1",Brad: plotCode is as-assigned by data provider; guranteed to be unique only within dataset (=project)

PLOT_ID,"/location/_if[@name=""if subplot""]/else/sourceaccessioncode","Brad: This is artificial internal database ID; a unique identifier within SALVIAS DB to each plot, within the table plotMetadata."

plot_area_ha,/location/area_m2/_ha_to_m2/value,"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"

elev_m,/location/elevation_m/_alt/1,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.

elev_max_m,/location/elevation_m/_alt/2/_avg/max,

elev_min_m,/location/elevation_m/_alt/2/_avg/min,

lat_decimal,"/location/locationcoords/latitude_deg/_nullIf:[null=0,type=float]/value",

plot_methodology,/location/locationevent/*_id/method/name,

plot_code,"/location/locationevent/_if[@name=""if subplot""]/then/_if[@name=""if event""]/then/parent_id/locationevent/*_id/location/authorlocationcode",Brad: plotCode is as-assigned by data provider; guranteed to be unique only within dataset (=project)

holdridge_life_zone,/location/locationevent/commclass/commdetermination/*_id/commconcept/*_id/*/commname,

date_finish,/location/locationevent/obsenddate/_*/date/_alt/1,

precip_mm,/location/locationevent/precipitation_m,

soil_acidity,"/location/locationevent/soilobs/acidity_fraction/_percent_to_fraction/value/_units:[default=""%"",to=]/value/_map:[""<0.05""=0,*=*]/value",

soil_cation_cap,/location/locationevent/soilobs/cationexchangecapacity_cmol_kg,

clay_percent,"/location/locationevent/soilobs/clay_fraction/_percent_to_fraction/value/_units:[default=""%"",to=]/value",

soil_conductivity,/location/locationevent/soilobs/conductivity,

soil_Mg,"/location/locationevent/soilobs/magnesium_fraction/_percent_to_fraction/value/_units:[default=""%"",to=]/value",

pH,/location/locationevent/soilobs/ph,"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."

soil_P,"/location/locationevent/soilobs/phosphorus_fraction/_percent_to_fraction/value/_units:[default=""%"",to=]/value/_map:[""<1,5""=0,*=*]/value",

soil_texture,/location/locationevent/soilobs/texture,

PLOT_ID,"/location/locationevent/taxonoccurrence/authortaxoncode/_first/1/_first/2/_if[@name=""if is organism""]/cond/_exists","Brad: This is artificial internal database ID; a unique identifier within SALVIAS DB to each plot, within the table plotMetadata."

temp_c,/location/locationevent/temperature_c,

locality_description,/location/locationnarrative/_merge/1,"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"

major_geo,/location/locationplace/*_id/placepath/continent,

slope_aspect,/location/slopeaspect_deg/_alt/1/_compass/value,

slope_gradient,/location/slopegradient_fraction/_alt/1,

observation_type,,"** No join mapping for observation_type ** Brad: SALVIAS internal metadata indicating whether the record represents an individual or aggregate observation. Rather than storing, use to decide where to store in VegX.; Aaron: VegX aggregateOrganismObservation table is missing many fields available in individualOrganismObservation, so we're mapping to individualOrganismObservation regardless of observation type"