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
stem_id
2
PlotObsID
3
NoInd
4
basal_diam
5
stem_dbh
6
gentry_dbh
7
stem_tag1
8
stem_tag2
9
stem_height_m
10
stem_height_first_branch_m
11
stem_canopy_form
12
stem_canopy_position
13
stem_liana_infestation
1
stem_id,stemID,,
2
PlotObsID,individualID,,
3
NoInd,stemCount,,
4
basal_diam,basalDiameter,,
5
stem_dbh,diameterBreastHeight_m,,
6
gentry_dbh,diameterBreastHeightGentry,,
7
stem_tag1,tag,/_alt/2,"The second tag supercedes the first. 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."
8
stem_tag2,tag,/_alt/1,"The second tag supercedes the first. Brad: See commend for tag1. Your mapping for tag2 looks correct. Probably both values would go here, only nested, with one superceding the other."
9
stem_height_m,height,,"Brad: Same as for height, but applies to individuals stems, not trees. Rare."
10
stem_height_first_branch_m,heightFirstBranch,,"Brad: Same as for ht_first_branch_m, but applies to individuals stems, not trees. Rare."
11
stem_canopy_form,canopyForm,,
12
stem_canopy_position,canopyPosition,,
13
stem_liana_infestation,lianaInfestation,,

Also available in: Unified diff