Fetch commonly used site/pedon/horizon data from a PedonPC database.
Fetch commonly used site/pedon/horizon data from a PedonPC or local NASIS database, return as a SoilProfileCollection object.
1 2 3
should pedons with horizonation errors be removed from the results? (default: TRUE)
should fragment volumes of NULL be interpreted as 0? (default: TRUE), see details
which colors should be used to generate the convenience field 'soil_color'? ('moist' | 'dry')
should horizonation by strictly enforced? (TRUE)
The value of
nullFragsAreZero will have a significant impact on the rock fragment fractions returned by
nullFragsAreZero = FALSE in those cases where there are many data-gaps and NULL rock fragment values should be interpretated as NULLs. Set
nullFragsAreZero = TRUE in those cases where NULL rock fragment values should be interpreted as 0.
This function attempts to do most of the boilerplate work when extracting site/pedon/horizon data from a local NASIS database. Pedons that are missing horizon data, or have errors in their horizonation are excluded from the returned object, however, their IDs are printed on the console. Pedons with combination horizons (e.g. B/C) are erroneously marked as errors due to the way in which they are stored in NASIS as two overlapping horizon records.
getHzErrorsNASIS for a simple approach to identifying pedons with problematic horizonation.
a SoilProfileCollection class object
This function currently works only on Windows, and requires a 'nasis_local' ODBC connection.
D. E. Beaudette and J. M. Skovlin
1 2 3 4 5 6 7 8 9 10 11 12 13
## Not run: # query depends on some pedon data, queried against the national database # note that you must setup this connection ahead of time f <- fetchNASIS() # plot only those profiles with densic contact plot(f[which(f$densic.contact), ], name='hzname') # get basic component data from local NASIS, after performing a # DMU-* query against the national database fc <- fetchNASIS_component_data() ## End(Not run)