Project

General

Profile

« Previous | Next » 

Revision 4857

input.Makefile: Maps validation: %/new_terms.csv: Include the entire map spreadsheet row, so that each new term is listed together with its mapping. This facilitates adding new mappings to mappings/Veg+-VegCore.csv directly from any new_terms.csv. Note that the use of `sort -u` (in lib/mappings.Makefile) causes multiline comments to be separated, leading to spurious lines for each multiline comment line.

View differences:

new_terms.csv
1
OBSERVATION_ID
2
basal_diam
3
census_date
4
census_no
5
cf_aff
6
clay_percent
7
coll_firstname
8
coll_lastname
9
coll_number
10
date_finish
11
date_start
12
det_type
13
elev_m
14
elev_max_m
15
elev_min_m
16
height_m
17
holdridge_life_zone
18
ht_first_branch_m
19
individual_code
20
infra_ep_1
21
infra_rank_1
22
lat_decimal
23
life_zone_code
24
locality_description
25
long_decimal
26
major_geo
27
no_of_individuals
28
organic_percent
29
orig_family
30
orig_species
31
plot_code
32
plot_methodology
33
pol1
34
pol2
35
precip_mm
36
project
37
sand_percent
38
silt_percent
39
soil_C
40
soil_Ca
41
soil_K
42
soil_Mg
43
soil_N
44
soil_Na
45
soil_P
46
soil_acidity
47
soil_base
48
soil_cation_cap
49
soil_conductivity
50
soil_texture
51
specific_authority
52
stem_canopy_form
53
stem_canopy_position
54
stem_dbh
55
stem_height_first_branch_m
56
stem_height_m
57
stem_liana_infestation
58
stem_tag1
59
stem_tag2
60
tag1
61
tag2
62
temp_c
63
voucher_string
64
x_position
65
y_position
1
-----
2
-----"
3
FROM ""SALVIAS-CSV"".organisms
4
GROUP BY ""PLOT_ID"", subplot
5
HAVING count(DISTINCT census_date) > 1
6
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."
7
SELECT ""PLOT_ID"", subplot, count(DISTINCT census_date) AS census_date_count
8
WHERE subplot IS NOT NULL AND census_date IS NOT NULL
9
basal_diam,basalDiameter,,
10
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:
11
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."
12
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."
13
clay_percent,clay,"/_units:[default=""%"",to=]/value",
14
coll_firstname,recordedBy.givenName,,Brad: See comment above
15
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."
16
coll_number,catalogNumber,/_alt/1,Brad: Map instead as for voucher_string
17
date_finish,endDate,,
18
date_start,startDate,,
19
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."
20
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.
21
elev_max_m,maximumElevationInMeters,,
22
elev_min_m,minimumElevationInMeters,,
23
height_m,height,/_alt/2,
24
holdridge_life_zone,communityID,,
25
ht_first_branch_m,heightFirstBranch,,
26
individual_code,recordNumber,,"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."
27
infra_ep_1,infraspecificEpithet,,
28
infra_rank_1,taxonRank,,
29
lat_decimal,decimalLatitude,,
30
life_zone_code,communityName,,
31
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"
32
long_decimal,decimalLongitude,,
33
major_geo,continent,,
34
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."
35
organic_percent,organic,"/_units:[default=""%"",to=]/value",
36
orig_family,verbatimFamily,,Brad: OMIT
37
orig_species,verbatimSpecificEpithet,,Brad: OMIT
38
plot_code,plotName,,
39
plot_code,plotName,,Brad: plotCode is as-assigned by data provider; guranteed to be unique only within dataset (=project)
40
plot_methodology,samplingProtocol,,
41
pol1,stateProvince,,Brad: No; pol1=stateProvince
42
pol2,county,,Brad: No pol2=countyParish
43
precip_mm,precipitation,,
44
project,projectName,,
45
sand_percent,sand,"/_units:[default=""%"",to=]/value",
46
silt_percent,silt,"/_units:[default=""%"",to=]/value",
47
soil_C,carbon,"/_units:[default=""%"",to=]/value",
48
soil_Ca,calcium,"/_units:[default=""%"",to=]/value",
49
soil_K,potassium,"/_units:[default=""%"",to=]/value",
50
soil_Mg,magnesium,"/_units:[default=""%"",to=]/value",
51
soil_N,nitrogen,"/_units:[default=""%"",to=]/value",
52
soil_Na,sodium,"/_units:[default=""%"",to=]/value",
53
soil_P,phosphorus,"/_units:[default=""%"",to=]/value/_map:[""<1,5""=0,*=*]/value",
54
soil_acidity,acidity,"/_units:[default=""%"",to=]/value/_map:[""<0.05""=0,*=*]/value",
55
soil_base,baseSaturation,"/_units:[default=""%"",to=]/value",
56
soil_cation_cap,cationExchangeCapacity,,
57
soil_conductivity,conductivity,,
58
soil_texture,texture,,
59
specific_authority,scientificNameAuthorship,,Brad: This is the author of the scientificName.
60
stem_canopy_form,canopyForm,,
61
stem_canopy_position,canopyPosition,,
62
stem_dbh,diameterBreastHeight_m,,
63
stem_height_first_branch_m,heightFirstBranch,,"Brad: Same as for ht_first_branch_m, but applies to individuals stems, not trees. Rare."
64
stem_height_m,height,/_alt/1,"Brad: Same as for height, but applies to individuals stems, not trees. Rare."
65
stem_liana_infestation,lianaInfestation,,
66
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."
67
stem_tag2,tag,/_alt/1/_alt/1,The second tag supercedes the first. The stem tag supercedes the tree tag. Brad: see above
68
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."
69
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."
70
temp_c,temperature,,
71
voucher_string,catalogNumber,/_alt/2,"Brad: OMIT. This is the verbatim text, which includes both collectors name and collection number. I would use coll_number, below."
72
x_position,organismX,,"Brad: These are important, fundamental values of many tree plots"
73
y_position,organismY,,Brad: See comment above for x_position

Also available in: Unified diff