| 1 |
1197
|
aaronmk
|
SALVIAS-CSV,VegBIEN:/locationevent,Comments
|
| 2 |
781
|
aaronmk
|
plot_area_ha,/*_id/location/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,/*_id/location/elevation/_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.
|
| 4 |
1351
|
aaronmk
|
pol2,"/*_id/location/locationdetermination/namedplace_id/_simplifyPath:[next=""parent_id/namedplace"",require=placename]/path/_forEach:[in:[],do=""namedplace[rank=_val]/parent_id""]/namedplace[rank=county]/placename",Brad: No pol2=countyParish
|
| 5 |
1353
|
aaronmk
|
pol1,"/*_id/location/locationdetermination/namedplace_id/_simplifyPath:[next=""parent_id/namedplace"",require=placename]/path/_forEach:[in:[county,],do=""namedplace[rank=_val]/parent_id""]/namedplace[rank=stateProvince]/placename",Brad: No; pol1=stateProvince
|
| 6 |
|
|
country,"/*_id/location/locationdetermination/namedplace_id/_simplifyPath:[next=""parent_id/namedplace"",require=placename]/path/_forEach:[in:[county,stateProvince,],do=""namedplace[rank=_val]/parent_id""]/namedplace[rank=country]/placename",
|
| 7 |
|
|
major_geo,"/*_id/location/locationdetermination/namedplace_id/_simplifyPath:[next=""parent_id/namedplace"",require=placename]/path/_forEach:[in:[county,stateProvince,country,],do=""namedplace[rank=_val]/parent_id""]/namedplace[rank=continent]/placename",
|
| 8 |
1025
|
aaronmk
|
locality_description,/*_id/location/locationnarrative,"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 |
781
|
aaronmk
|
slope_aspect,/*_id/location/slopeaspect,
|
| 10 |
|
|
slope_gradient,/*_id/location/slopegradient,
|
| 11 |
1465
|
aaronmk
|
elev_max_m,"/*_id/location/{elevation/_alt/2/_avg/max,elevationrange/_range/to}/_units:[units=""m""]/value",
|
| 12 |
|
|
elev_min_m,"/*_id/location/{elevation/_alt/2/_avg/min,elevationrange/_range/from}/_units:[units=""m""]/value",
|
| 13 |
1323
|
aaronmk
|
lat_decimal,"/*_id/location/{locationdetermination/latitude,centerlatitude}",
|
| 14 |
|
|
long_decimal,"/*_id/location/{locationdetermination/longitude,centerlongitude}",
|
| 15 |
1099
|
aaronmk
|
plot_methodology,/*_id/method/name,
|
| 16 |
1073
|
aaronmk
|
project,/*_id/project:[datasource_id/party/organizationname/_alt/2=$/_ignore/inLabel]/projectname,
|
| 17 |
950
|
aaronmk
|
holdridge_life_zone,/commclass/commdetermination/*_id/commconcept/*_id/*/commname,
|
| 18 |
|
|
life_zone_code,/commclass/commdetermination/*_id/commconcept/commdescription,
|
| 19 |
781
|
aaronmk
|
date_finish,/obsenddate/_*/date,
|
| 20 |
|
|
date_start,/obsstartdate/_*/date,
|
| 21 |
1220
|
aaronmk
|
precip_mm,/precipitation,
|
| 22 |
1230
|
aaronmk
|
soil_acidity,"/soilobs/acidity/_map:[""<0.05""=0]/value/_units:[units=""%""]/value",
|
| 23 |
|
|
soil_base,"/soilobs/basesaturation/_units:[units=""%""]/value",
|
| 24 |
|
|
soil_Ca,"/soilobs/calcium/_units:[units=""%""]/value",
|
| 25 |
|
|
soil_C,"/soilobs/carbon/_units:[units=""%""]/value",
|
| 26 |
|
|
soil_cation_cap,/soilobs/cationexchangecapacity,
|
| 27 |
|
|
clay_percent,"/soilobs/clay/_units:[units=""%""]/value",
|
| 28 |
|
|
soil_conductivity,/soilobs/conductivity,
|
| 29 |
|
|
soil_Mg,"/soilobs/magnesium/_units:[units=""%""]/value",
|
| 30 |
|
|
soil_N,"/soilobs/nitrogen/_units:[units=""%""]/value",
|
| 31 |
|
|
organic_percent,"/soilobs/organic/_units:[units=""%""]/value",
|
| 32 |
|
|
pH,/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."
|
| 33 |
|
|
soil_P,"/soilobs/phosphorus/_map:[""<1,5""=0]/value/_units:[units=""%""]/value",
|
| 34 |
|
|
soil_K,"/soilobs/potassium/_units:[units=""%""]/value",
|
| 35 |
|
|
sand_percent,"/soilobs/sand/_units:[units=""%""]/value",
|
| 36 |
|
|
silt_percent,"/soilobs/silt/_units:[units=""%""]/value",
|
| 37 |
|
|
soil_Na,"/soilobs/sodium/_units:[units=""%""]/value",
|
| 38 |
|
|
soil_texture,/soilobs/texture,
|
| 39 |
1220
|
aaronmk
|
temp_c,/temperature,
|
| 40 |
1086
|
aaronmk
|
plot_code,:[datasource_id/party/organizationname/_alt/2=$/_ignore/inLabel]/authorlocationcode,Brad: plotCode is as-assigned by data provider; guranteed to be unique only within dataset (=project)
|
| 41 |
1077
|
aaronmk
|
PLOT_ID,:[datasource_id/party/organizationname/_alt/2=$/_ignore/inLabel]/sourceaccessioncode,"Brad: This is artificial internal database ID; a unique identifier within SALVIAS DB to each plot, within the table plotMetadata."
|
| 42 |
781
|
aaronmk
|
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"
|
| 43 |
|
|
recensused,,"Brad: This is a 0/1 value, internal to SALVIAS. 1 indicates that a plot has >1 set of values, from different census events.; Aaron: Different censuses are distinguished in organisms data by different census_no values"
|
