-----

-----"

FROM ""SALVIAS-CSV"".organisms

GROUP BY ""PLOT_ID"", subplot

HAVING count(DISTINCT census_date) > 1

OBSERVATION_ID,individualID,,"Brad: Neither is correct; this is just an internal ID for table plotObservations. However, it has the important property of uniquely identifying an ""observation"", which is an individual tree, in the case of an individual observation, or a records of a species with an associated count of individuals or measurement of percent cover, in the case of aggregate observations. Not sure where to store this. Main point is that it is not part of the original data, but an auto_increment added later."

SELECT ""PLOT_ID"", subplot, count(DISTINCT census_date) AS census_date_count

WHERE subplot IS NOT NULL AND census_date IS NOT NULL

basal_diam,basalDiameter,,

census_date,eventDate,,"This is for the subplot, not the organism, as all organisms in a subplot have the same value for it. The following query returns no rows:

census_no,censusNumber,,"Brad: Assigned by SALVIAS. 1 for first plot, then 2, 3, etc. I can't recall if we even have repeat censuses in SALVIAS. Probably not."

cf_aff,identificationQualifier,,"Brad: Not sure where this goes. Indicator of identification uncertainty. 'cf.'=similar to the species listed, 'aff.'=related to the species list, but not the same. You'll need to check with Bob and with Nick where these go in VegX and VegBank."

coll_firstname,recordedBy_givenName,,Brad: See comment above

coll_lastname,recordedBy_surName,,"Brad: This is the collector of a separate specimen which vouchers this tree or species. I worry that vouchers are not properly accommodated in VegX. Again, we need to check with Nick."

coll_number,recordNumber,/_alt/1,Brad: Map instead as for voucher_string

date_finish,endDate,,

date_start,startDate,,

det_type,voucherType,,"Brad: A SALVIAS value referring to the relationship between the voucher specimen and the observation. Affect how the identification of the specimen(latin name) is transferred to the observation. 'direct'=voucher specimen was collected from this same tree; they are one and the same individual. 'indirect'=voucher specimen was collected for a different individual, but the original data provider confirmed that this is the same species. 'default'=basically same as 'indirect'. 'uncollected'=no voucher specimen, data provider  asserted that this was the name but was unable to collect. The main different is that with 'direct', 'indirect', and 'default', the scientific name can be updated automatically based on the name attached to the specimen voucher (assuming you have a link to that data, presumably from a herbarium database. Whereas, if det_type='uncollected', the name can never change because there is no specimen."

elev_m,elevationInMeters,,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,maximumElevationInMeters,,

elev_min_m,minimumElevationInMeters,,

holdridge_life_zone,communityID,,

ht_first_branch_m,heightFirstBranch,,

infra_ep_1,infraspecificEpithet,,

infra_rank_1,taxonRank,,

lat_decimal,decimalLatitude,,

life_zone_code,communityName,,

locality_description,locality,,"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"

long_decimal,decimalLongitude,,

major_geo,continent,,

no_of_individuals,individualCount,,"Brad: This is a count of number of indiiduals for an *aggregate* observation. For VegBank, I'm not sure. Not exactly the same as stemCount. An individual tree could have 3 stems but would still only count as 1. We need to check with Bob on this."

orig_family,originalFamily,,Brad: OMIT

orig_species,originalSpecificEpithet,,Brad: OMIT

plot_code,locationName,,

plot_code,locationName,,Brad: plotCode is as-assigned by data provider; guranteed to be unique only within dataset (=project)

plot_methodology,samplingProtocol,,

pol1,stateProvince,,Brad: No; pol1=stateProvince

pol2,county,,Brad: No pol2=countyParish

precip_mm,precipitation,,

project,projectName,,

soil_C,carbon_percent,,Assuming units are % based on the range of values

soil_Ca,calcium_percent,,Assuming units are % based on the range of values

soil_K,potassium_percent,,Assuming units are % based on the range of values

soil_Mg,magnesium_percent,,Assuming units are % based on the range of values

soil_N,nitrogen_percent,,Assuming units are % based on the range of values

soil_Na,sodium_percent,,Assuming units are % based on the range of values

soil_P,phosphorus_percent,"/_map:[""<0.05""=0,*=*]/value",Assuming units are % based on the range of values

soil_acidity,acidity_percent,"/_map:[""<0.05""=0,*=*]/value",Assuming units are % based on the range of values

soil_base,baseSaturation_percent,,Assuming units are % based on the range of values

soil_cation_cap,cationExchangeCapacity_cmol_kg,,

soil_conductivity,conductivity,,

soil_texture,texture,,

specific_authority,scientificNameAuthorship,,Brad: This is the author of the scientificName.

stem_canopy_form,canopyForm,,

stem_canopy_position,canopyPosition,,

stem_dbh,diameterBreastHeight_cm,,"Assuming units based on the units for intercept_cm, which measures the same dimension"

stem_height_first_branch_m,heightFirstBranch,,"Brad: Same as for ht_first_branch_m, but applies to individuals stems, not trees. Rare."

stem_height_m,height_m,/_alt/1,"""Total height of this stem only, in meters"" (stem_height_m definition at < http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: Same as for height, but applies to individuals stems, not trees. Rare."

stem_liana_infestation,lianaInfestation,,

stem_tag1,tag,/_alt/1/_alt/2,"The second tag supercedes the first. The stem tag supercedes the tree tag. 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,tag,/_alt/1/_alt/1,The second tag supercedes the first. The stem tag supercedes the tree tag. Brad: see above

tag1,tag,/_alt/2/_alt/2,"The second tag supercedes the first. The stem tag supercedes the tree tag. 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,tag,/_alt/2/_alt/1,"The second tag supercedes the first. The stem tag supercedes the tree tag. Brad: See commend for tag1. Your mapping for tag2 looks correct. Probably both values would go here, only nested, with one superceding the other."

temp_c,temperature,,

voucher_string,recordNumber,/_alt/2,"Brad: OMIT. This is the verbatim text, which includes both collectors name and collection number. I would use coll_number, below."

x_position,organismX_m,,"""x coordinate in meters"" (x_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: These are important, fundamental values of many tree plots"

y_position,organismY_m,,"""y coordinate in meters"" (y_position definition at <http://salvias.net/Documents/salvias_data_dictionary.html#Plot+data>). Brad: See comment above for x_position"