Complete data from the Barro Colorado 50-ha plot: 423617 trees, 35 years

R Analytical Tables: Tree and Stem These are 16 tables in R format, 8 tables in the tree format, one table per census, and 8 more in the stem format. They are named bci.tree1 through bci.tree8 and bci.stem1 through bci.stem8, with the number corresponding to a census. Every tree table includes a record for every tree appearing in the 50-ha plot across all censuses, with one row per tree and one table per census. Trees not yet censused and dead trees are included, allowing the fate of every tree to be tallied in every census. The rows in every tree table are in exactly the same order, so the 8 tree tables are effectively a single giant table, with columns for every one of the 8 censuses. They are divided into separate tables for easier access. Moreover, each individual census table is self-contained, and if a user needs only one census, then only that one census table is necessary. For most purposes the most recent, bci.tree8, should serve for a single census. The 8 stem tables form a parallel set having one row for every stem ever censused. In the tree tables, if stemID matches for a given tree in 2 censuses, then it is certain that the same stem was measured in both censuses. If the stemID differs between censuses, it often means that the first stem broke and a new stem was measured. However, in trees with 2 or more stems, it was not always possible to identify stems with certainty across censuses prior to 2010, because stem tags were not used. This means that there are cases where the stemID changes even though the stem(s) really did persist. The cleanest way to assess growth is to use only those cases where the stemID matches between censuses. It is also necessary to check the HOM (height-of-measurement) in case it changes between censuses. In the stem tables, records on matching rows are guaranteed to be the same stem, but the HOM might change. The 8 tree tables are zipped into the single file bci.tree.zip, and the 8 stem tables into bci.stem.zip. Columns in R Analytical Tables: Tree and Stem treeID: The unique tree identifier in the database. Guarantees a tree match. stemID: The unique stem identifier in the database. Guarantees a stem match. tag: Tag number on the tree (occasionally negative where a tag was duplicated by mistake). StemTag: Tag number on the individual stem, if present. sp: The species mnemonic. See the R Species Table for full Latin names. quadrat: Quadrat designation, as a 2-digit row number then 2-digit column number on a 20x20 m grid. gx: The x coordinate within the plot, meters from the west border of the plot, always in [0,1000). gy: The y coordinate, meters from the south border, always in [0,500). dbh: Diameter (mm) of one stem on the tree, the stem whose stemID is given. hom: The height-of-measure, meters above the ground, where the dbh was measured. ExactDate: The date on which a tree was measured. date: Integer date for easy calculation of time interval between censuses (the number of days since 1 Jan 1960). codes: The codes describing the measurement as recorded in the field. See Condit (1998) for a description of field codes. For analyses, status codes should be used, not field codes. status: A status code for the tree or stem. See the section below, Status Codes for Analyses. DFstatus: Alternate stem status, redundant relative to status. nostems: The number of living stems on the date of measurement. agb: Above-ground-biomass of all stems on the tree, in Mg (= metric tons), or for the individual stem. Note that agb=0 for dead trees. ba: Basal area of all stems on the tree, in square meters. Note that ba=0 for dead trees. Status Codes for Analyses These indicate whether a tree (stem) is alive (A) or dead (D), with some further complications. Status A=alive is assigned to a tree if it has any living stem or sprout. Status D=dead is only used when an entire tree is dead. A third status is P=prior, necessary because each of the analytical tables has a record for every tree (or stem). Thus, there must be records in early censuses for trees that recruited in later censuses, and these trees have status P. In a complete life cycle, a tree begins with status P, becomes A, then D; for many trees, the cycle includes only P to A, or A to D, or just A over all 8 censues. Additional status codes are necessary because a stem can be dead while the tree is still alive, and for rare cases where trees were missed during a census or recorded as dead once then later alive. Status Codes for Analyses (the status column in R Analytical Tables) A: Alive, applied to either the tree or stem. D: Dead, meaning the entire tree is dead, ie with no living stems or sprouts. P: Prior, applied to a tree (or stem) in censuses prior to its appearance in the plot. M: Missing, indicating that the tree was skipped by mistake during the census, so it could have been alive or dead. AD: A seldom-used code, applied when a tree was noted as dead in one census but was found alive in a later census. For most purposes, this code should be interpreted the same as code A for alive. AR: A similar unusual code, applied when a stem was noted as broken in one census but intact in a later census. For most purposes, this code should be interpreted the same as code A for alive. G: Gone, for stems only, meaning the stem broke or otherwise disappeared, but other stems on the tree were alive and measured. V: Vanished, for stems only. This is needed in the BCI plot because stem tags were not used before the 2010 census. It is often the case where a tree had 2 or more stems that were, after 5 years, impossible to match. When this was true, new stems with new stemIDs and thus new rows in the stem table were created. Earlier stems were given status=V. In most cases, V means the stems persisted but could not be tracked. R Species Table A single table in R format with taxonomic details on the species names used in the plot database as well as wood density. This is matched to the R Analytical Tables with the species mnemonic (column sp). The R species table includes many species not found in the 50-ha plot but known in other plots in Panama. More information and references about the plot tree species, including all taxonomic changes since 1982, is available in a separate data archive (Condit et al. 2019). Columns in R Species Table sp: The species mnemonic. Latin: Full Latin name. Genus: Taxonomic genus. Species: Taxonomic species. Family: Following (mostly) the angiosperm classification at http://www.mobot.org/MOBOT/research/APweb/. SpeciesID: The unique species identifier in the database. Guarantees a species match. SubspeciesID: The unique subspecies identifier in the database. Guarantees a subspecies match. Authority: Taxonomic authority. IDLevel: The taxonomic level to which the species is identified, usually species, otherwise it is a recognizable morphospecies, not named to species (usually the genus is known). syn: Prior names used in the BCI plot. subsp: Infraspecific name (blank in most cases because no subspecies name is used). wsg: Wood specific gravity (grams per cm3 dry weight). wsglevel: The taxonomic level for which wsg is known, ie where this is genus it means the wsg is the average for the genus (unrelated to IDLevel). Topography of the BCI plot A tab-delimited ascii text table, BCIelev.tsv, with precise topography of the BCI 50-ha plot. See Harms et al. (2001) for details. Columns in Topography of the BCI plot x: The x coordinate within the plot, in meters from the west border. y: The y plot coordinate, in meters from the south border. elev: Elevation above sea-level in meters. Full Measurement Table A tab-delimited text table, FullMeasurementBCI.tsv, zipped as FullMeasurementBCI.zip. The table includes a measurement of every stem at every HOM (height-of-measure) taken in the 50-ha plot over 1982-2015. In this table, every measurement is a separate row, so records for the same tree are on multiple rows. The R Analytical tables include the same measurements in a more convenient format for analysis. However, there are some measurements in this full table not appearing in analytical tables. Those are cases where a tree was measured at several HOMs due to buttresses. In the R tables, only a single measurement per stem is included, designed so that as many censuses as possible are at the same HOM. Analyses of trunk taper require this table instead of R Analytical Tables (Cushman 2014). Columns in Full Measurement Table Family: Same as R Species Table. Genus: Same as R Species Table. SpeciesName: Same as Species in R Species Table. Mnemonic: Same as sp in R Species Table. Subspecies: Same as subsp in R Species Table. SpeciesID: Same as R Species Table. SubspeciesID: Same as R Species Table. QuadratName: Same as quadrat in R Analytical Table. PX: Same as gx in R Analytical Table. PY: Same as gy in R Analytical Table. TreeID: Same as R Analytical Table. Tag: Same as R Analytical Table. StemID: Same as R Analytical Table. StemTag: Same as R Analytical Table. PlotCensusNumber: Census number 1-8. DBH: Same as column dbh in R Analytical Table. HOM: Same as column hom in R Analytical Table. ExactDate: Same as R Analytical Table. Date: Same as R Analytical Table. ListOfTSM: Same as codes in R Analytical Table. HighHOM: A flag, with 1 indicating this hom is at the highest position on the stem, otherwise 0. Status: Same as status in R Analytical Table. Complete MySQL Database This is the full MySQL database, zipped as condit_bci_23May2019.zip. Within the zip is a single mysql dump file that must be sourced within MySQL to restore the database. Most users will never need this, and further details are omitted here. A more thorough description of the tables can be found in Condit et al. (2014).

R分析表格：树木与茎干（R Analytical Tables: Tree and Stem）
本数据集包含16个R格式表格，其中8个为树木格式表格、8个为茎干格式表格，每个表格对应一次普查。文件命名为bci.tree1至bci.tree8，以及bci.stem1至bci.stem8，编号对应普查轮次。
每棵树木表格包含50公顷样地内所有普查中出现过的每棵树木的记录：每棵树木占一行，每次普查对应一张表格。未参与普查的树木与死亡树木均被纳入，以便统计每次普查中每棵树木的存活状态。所有树木表格的行顺序完全一致，因此8张树木表格可整合为一张超大表格，包含对应8次普查的全部列。为便于访问，数据被拆分为独立的表格。此外，每张单独的普查表格均为自包含的，若用户仅需某一次普查的数据，仅需加载对应普查的表格即可。多数场景下，最新的bci.tree8可满足单次普查的分析需求。
8张茎干表格为平行数据集，每一行对应一次普查中被测量过的每一根茎干。在树木表格中，若两次普查中某棵树木的stemID（茎干唯一标识符）一致，则可确定两次普查测量的为同一根茎干；若stemID不同，则通常意味着原茎干折断，后续测量了新的茎干。但对于拥有2根及以上茎干的树木，2010年之前的普查中因未使用茎干标签，无法始终准确匹配跨普查的茎干，因此存在即使茎干实际存活但stemID发生变更的情况。评估生长情况的最优方式是仅使用跨普查stemID一致的记录，同时需检查测量高度（height-of-measurement, HOM）是否在普查间发生变化。
在茎干表格中，匹配行的记录可确定为同一根茎干，但测量高度（HOM）仍可能发生变更。
8张树木表格被打包为单个压缩文件bci.tree.zip，8张茎干表格被打包为bci.stem.zip。

### R分析表格的列定义
1. treeID：数据库中树木的唯一标识符，可确保树木匹配的准确性。
2. stemID：数据库中茎干的唯一标识符，可确保茎干匹配的准确性。
3. tag：树木上的标签编号（因标签重复失误，偶尔会出现负值）。
4. StemTag：单根茎干的标签编号（若存在）。
5. sp：物种助记符，完整拉丁名请参见R物种表格。
6. quadrat：样方编号，格式为2位行号加2位列号，对应20×20米的网格。
7. gx：样地内的X坐标，单位为米，以样地西边界为原点，取值范围为[0,1000)。
8. gy：样地内的Y坐标，单位为米，以样地南边界为原点，取值范围为[0,500)。
9. dbh：对应stemID所指茎干的胸径（单位：毫米）。
10. hom：测量胸径时的地面以上测量高度（单位：米）。
11. ExactDate：树木的测量日期。
12. date：整数格式的日期，便于计算普查间的时间间隔（即自1960年1月1日起的天数）。
13. codes：野外记录的测量代码，详细说明请参见Condit (1998)。分析时应使用状态代码而非野外代码。
14. status：树木或茎干的状态代码，详细说明请参见下文的"分析用状态代码"章节。
15. DFstatus：备用茎干状态代码，与status字段冗余。
16. nostems：测量当日活茎干的数量。
17. agb：树木所有茎干的地上生物量（单位：兆克，即公吨），或单根茎干的地上生物量。注意：死亡树木的agb值为0。
18. ba：树木所有茎干的基面积（单位：平方米）。注意：死亡树木的ba值为0。

### 分析用状态代码
该代码用于指示树木（茎干）的存活状态（活A或死D），并包含部分复杂场景的标识。
- 状态A=存活：若树木存在任意活茎干或萌芽，则标记为A。
- 状态D=死亡：仅当整棵树木完全死亡时使用该代码。
- 状态P=前期：因每张分析表格均包含所有树木（或茎干）的记录，因此对于后期才出现在样地中的树木，其早期普查的记录需标记为P。完整生命周期中，树木的状态依次为P→A→D；多数树木的生命周期仅包含P→A、A→D，或全程为A。
- 补充状态代码用于处理以下场景：茎干死亡但树木仍存活，以及极少数普查中漏测的树木，或曾被记录为死亡但后续被发现存活的树木。

#### 分析用状态代码（R分析表格中的status列）
1. A：存活，可应用于树木或茎干。
2. D：死亡，指整棵树木完全死亡，无存活茎干或萌芽。
3. P：前期，指该树木（或茎干）在首次出现在样地之前的普查中的状态。
4. M：缺失，指普查时因失误跳过了该树木，无法确定其实际存活状态。
5. AD：极少使用的代码，指某树木在一次普查中被记录为死亡，但后续普查中被发现存活。多数场景下，该代码可等同于A（存活）。
6. AR：类似的罕见代码，指某茎干在一次普查中被记录为折断，但后续普查中被发现完好。多数场景下，该代码可等同于A（存活）。
7. G：消失，仅适用于茎干，指茎干折断或其他方式消失，但该树木的其他茎干仍存活并被测量。
8. V：消失（仅适用于茎干）。因2010年之前的BCI样地未使用茎干标签，该代码用于无法匹配跨普查茎干的场景：当一棵树拥有2根及以上茎干，且时隔5年后无法准确匹配时，会为新茎干分配新的stemID并在茎干表格中新增行，原茎干被标记为状态V。多数情况下，V代表茎干实际存活但无法被追踪。

### R物种表格
本数据集包含一张R格式表格，包含样地数据库中所用物种的分类学细节与木材密度数据，通过物种助记符（sp列）与R分析表格关联。R物种表格包含大量未在50公顷样地中出现，但在巴拿马其他样地中存在的物种。更多关于样地树木物种的信息与参考文献（包括1982年以来的所有分类学变更）可参见单独的数据存档（Condit et al. 2019）。

#### R物种表格的列定义
1. sp：物种助记符。
2. Latin：完整拉丁学名。
3. Genus：分类学属名。
4. Species：分类学种名。
5. Family：分类学科名（主要遵循http://www.mobot.org/MOBOT/research/APweb/的被子植物分类系统）。
6. SpeciesID：数据库中物种的唯一标识符，可确保物种匹配的准确性。
7. SubspeciesID：数据库中亚种的唯一标识符，可确保亚种匹配的准确性。
8. Authority：分类学命名人。
9. IDLevel：物种的分类学鉴定等级，通常为种级，若未鉴定到种，则为可识别的形态种（通常仅已知属名）。
10. syn：巴罗科罗拉多岛样地曾使用的旧名称。
11. subsp：种下名称（多数情况下为空，因未使用亚种名称）。
12. wsg：木材比重（单位：克/立方厘米干重）。
13. wsglevel：已知木材比重的分类学等级，例如若为属级，则wsg为该属的平均木材比重（与IDLevel无关）。

### BCI样地地形数据
本数据集为制表符分隔的ASCII文本表格BCIelev.tsv，包含BCI 50公顷样地的精确地形数据，详细说明请参见Harms et al. (2001)。

#### 地形数据的列定义
1. x：样地内的X坐标，单位为米，以样地西边界为原点。
2. y：样地内的Y坐标，单位为米，以样地南边界为原点。
3. elev：海拔高度（单位：米，相对于海平面）。

### 完整测量表格
本数据集为制表符分隔的文本表格FullMeasurementBCI.tsv，打包为FullMeasurementBCI.zip。表格包含1982-2015年间50公顷样地内所有茎干在各测量高度（HOM）下的测量数据。该表格中，每一条测量记录占一行，因此同一棵树木的记录会分布在多行。R分析表格以更便于分析的格式整合了相同的测量数据，但完整测量表格包含部分R分析表格未收录的测量数据，即因板状根导致树木在多个测量高度被测量的记录。R分析表格中仅包含每根茎干的单条测量记录，设计目标是尽可能让多次普查的测量高度保持一致。树干锥度分析需使用该完整测量表格而非R分析表格（Cushman 2014）。

#### 完整测量表格的列定义
1. Family：与R物种表格中的Family列一致。
2. Genus：与R物种表格中的Genus列一致。
3. SpeciesName：与R物种表格中的Species列一致。
4. Mnemonic：与R分析表格中的sp列一致。
5. Subspecies：与R物种表格中的subsp列一致。
6. SpeciesID：与R物种表格中的SpeciesID列一致。
7. SubspeciesID：与R物种表格中的SubspeciesID列一致。
8. QuadratName：与R分析表格中的quadrat列一致。
9. PX：与R分析表格中的gx列一致。
10. PY：与R分析表格中的gy列一致。
11. TreeID：与R分析表格中的treeID列一致。
12. Tag：与R分析表格中的tag列一致。
13. StemID：与R分析表格中的stemID列一致。
14. StemTag：与R分析表格中的StemTag列一致。
15. PlotCensusNumber：普查编号，取值为1-8。
16. DBH：与R分析表格中的dbh列一致。
17. HOM：与R分析表格中的hom列一致。
18. ExactDate：与R分析表格中的ExactDate列一致。
19. Date：与R分析表格中的date列一致。
20. ListOfTSM：与R分析表格中的codes列一致。
21. HighHOM：标记位，取值为1表示该HOM为茎干的最高测量位置，否则为0。
22. Status：与R分析表格中的status列一致。

### 完整MySQL数据库
本数据集为完整的MySQL数据库，打包为condit_bci_23May2019.zip。压缩包内包含单个MySQL转储文件，需在MySQL中执行source命令以恢复数据库。多数用户无需使用该数据集，此处省略详细说明。更详细的表格说明可参见Condit et al. (2014)。