Note that FIA does not provide data for some states, e.g. HI.

e-mail from Bob Peet on 2013-1-24:

-----

One concern I have is that Aaron needs to recognize what constitutes a single plot in the input stream as there is a risk that our BIEN2 database included replicates (both spatial and temporal) as separate plots. There should be a total of around 125,000 plots prior to dropping unwanted plots, so this could be one test.

My second concern is the identification of planted versus natural stems. This is probably well documented, but I have not checked on this.

A third concern is the validity of the geo-coordinates.  Most plots have been randomly offset by up to 1.6 km, but this we can handle with an error term.  More critical is the assertion that "data for a proportion of the private locations have been switched between pairs of plot locations having the same forest type and owner class (but not the same owner) within a county." I do not know what this proportion is, but we may need to assume county-level precision for all private land, assuming we can identify the private holdings.

My fourth concern is the relatively high number of taxonomic problems in the database.  Some identifications are obvious errors (we have several western US trees that are never planted in the FIA inventory for NC).  Some taxa are obviously routinely composites of species but without acknowledgement of the problem. We may need to assess the meaning of the names in each state list as a separate project, which could be a painful undertaking.

A final issue is that we should probably try to capture the complete floristics data that are available for the 1/16th of the plots that are designated as "forest health" plots.  This is a rather recent innovation and not fully implemented yet, but where these data are available, we should try to capture them.  However, the taxonomic challenges for full floristics are enormous relative to trees and we need some assessment as to whether these data are of sufficiently quality to want to bother with.

-----

Note that the refresh is missing some PLT_CN values present in the original version, making COND_unique and Organism incompatible [1].

[1] The following query returns 180,215 rows:

-----

SELECT "PLT_CN"::text FROM "FIA"."FIA_COND_unique"

EXCEPT

SELECT "PLT_CN" FROM "FIA"."COND_unique"

-----

e-mail from Brad Boyle on 2013-2-8:

-----

Attached [Recommended FIA filter criteria for BIEN.docx, FIA tables and columns to import to BIEN.docx] is a description of the protocol we are recommending for filtering the FIA plots. Give it a try and let me know if you have questions.

If you want to check the meanings of different tables and columns yourself, see the most recent FIA database manual (http://www.fia.fs.fed.us/library/database-documentation/current/ver5.1.4/FIADB_user%20manual_5-1-4_p2_11_2012.pdf). It's a monster, but you can ignore most of it and just navigate to the table and column descriptions. Chap. 3 pages 19-26 gives a thorough description of primary and foreign keys.

Attached also is an example R script from Jes Coyle (a student of Bob Peet) showing how she compiled and filtered FIA plots for a study of eastern US forests. I include it only as an example; please use the filter criteria provided in my document, not hers.

Finally, I've  prepared a list of the columns that should be imported to BIEN, after you haver constructed the primary keys and completed filtering (Bob, Brian M, if you think anything is missing from that list, let us know).

-----