diff --git a/.nojekyll b/.nojekyll new file mode 100644 index 0000000..8b13789 --- /dev/null +++ b/.nojekyll @@ -0,0 +1 @@ + diff --git a/404.html b/404.html new file mode 100644 index 0000000..690c513 --- /dev/null +++ b/404.html @@ -0,0 +1,87 @@ + + +
+ + + + +CODE_OF_CONDUCT.md
+ We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+Examples of behavior that contributes to a positive environment for our community include:
+Examples of unacceptable behavior include:
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at adamhsparks@gmail.com. All complaints will be reviewed and investigated promptly and fairly.
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+Community Impact: A violation through a single incident or series of actions.
+Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+Community Impact: A serious violation of community standards, including sustained inappropriate behavior.
+Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+Consequence: A permanent ban from any sort of public interaction within the community.
+This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+Community Impact Guidelines were inspired by [Mozilla’s code of conduct enforcement ladder][https://github.com/mozilla/inclusion].
+For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
+YEAR: 2024 +COPYRIGHT HOLDER: abares authors ++ +
LICENSE.md
+ Copyright (c) 2024 read.abares authors
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+vignettes/read.abares.Rmd
+ read.abares.Rmd
You can download the CSV files directly in your R session as +illustrated below.
+
+library(read.abares)
+
+get_hist_nat_est() |>
+ head()
+#> Variable Year Value RSE Industry
+#> <char> <int> <num> <int> <char>
+#> 1: AI stud fees and herd testing ($) 1990 790 39 All Broadacre
+#> 2: Accounting services ($) 1990 2850 4 All Broadacre
+#> 3: Advisory services ($) 1990 280 37 All Broadacre
+#> 4: Age of owner manager (yrs) 1990 53 1 All Broadacre
+#> 5: Age of spouse (yrs) 1990 49 1 All Broadacre
+#> 6: Agistment ($) 1990 1950 36 All Broadacre
+
+get_hist_sta_est() |>
+ head()
+#> Variable Year Value RSE State Industry
+#> <char> <int> <num> <int> <char> <char>
+#> 1: AI stud fees and herd testing ($) 1990 210 118 New South Wales All Broadacre
+#> 2: Accounting services ($) 1990 2740 7 New South Wales All Broadacre
+#> 3: Advisory services ($) 1990 190 105 New South Wales All Broadacre
+#> 4: Age of owner manager (yrs) 1990 55 2 New South Wales All Broadacre
+#> 5: Age of spouse (yrs) 1990 52 2 New South Wales All Broadacre
+#> 6: Agistment ($) 1990 2790 71 New South Wales All Broadacre
+
+get_hist_reg_est() |>
+ head()
+#> Variable Year ABARES region Value RSE
+#> <char> <int> <char> <num> <int>
+#> 1: AI stud fees and herd testing ($) 1990 NSW Central West 90 68
+#> 2: Accounting services ($) 1990 NSW Central West 2420 19
+#> 3: Advisory services ($) 1990 NSW Central West 120 80
+#> 4: Age of owner manager (yrs) 1990 NSW Central West 57 5
+#> 5: Age of spouse (yrs) 1990 NSW Central West 51 4
+#> 6: Agistment ($) 1990 NSW Central West 310 52
You can download files and pipe directly into the class object that +you desire for the Australian Farm Gridded Data (AGFD) data.
+Directly from the DAFF website:
+++The Australian Gridded Farm Data are a set of national scale maps +containing simulated data on historical broadacre farm business outcomes +including farm profitability on an 0.05-degree (approximately 5 km) +grid.
+
++These data have been produced by read.abares as part of the ongoing +Australian Agricultural Drought Indicator (AADI) project (previously +known as the Drought Early Warning System Project) and were derived +using read.abares farmpredict model, which in turn is based on +read.abares Agricultural and Grazing Industries Survey (AAGIS) data.
+
++These maps provide estimates of farm business profit, revenue, costs +and production by location (grid cell) and year for the period 1990-91 +to 2022-23. The data do not include actual observed outcomes but rather +model predicted outcomes for representative or ‘typical’ broadacre farm +businesses at each location considering likely farm characteristics and +prevailing weather conditions and commodity prices.
+
++The Australian Gridded Farm Data remain under active development, and +as such should be considered experimental.
+
– Australian Department of Agriculture, Fisheries and Forestry.
+
+library(read.abares)
+
+## A list of {stars} objects
+star <- get_agfd(cache = TRUE) |>
+ read_agfd_stars()
+#> Will return stars object with 612226 cells.
+#> No projection information found in nc file.
+#> Coordinate variable units found to be degrees,
+#> assuming WGS84 Lat/Lon.
+
+head(star[[1]])
+#> stars object with 2 dimensions and 6 attributes
+#> attribute(s):
+#> Min. 1st Qu. Median Mean 3rd Qu.
+#> farmno 15612.000000 233091.50000000 329567.0000000 324737.7187618 418508.5000000
+#> R_total_hat_ha 2.954396 7.88312157 21.7520529 169.5139301 174.8553843
+#> C_total_hat_ha 1.304440 4.34079101 9.9449849 93.2210542 95.7221857
+#> FBP_fci_hat_ha -143.759785 3.60529967 11.5796641 76.2928759 77.6748501
+#> FBP_fbp_hat_ha -349.521639 3.36599833 11.5074294 60.0750936 62.8596117
+#> A_wheat_hat_ha 0.000000 0.04062786 0.1114289 0.1365683 0.2112845
+#> Max. NA's
+#> farmno 669706.0000000 443899
+#> R_total_hat_ha 2415.7556059 443899
+#> C_total_hat_ha 1853.5385298 443899
+#> FBP_fci_hat_ha 1186.5830232 443899
+#> FBP_fbp_hat_ha 1240.6003218 443899
+#> A_wheat_hat_ha 0.5047761 565224
+#> dimension(s):
+#> from to refsys values x/y
+#> lon 1 886 WGS 84 [886] 112,...,156.2 [x]
+#> lat 1 691 WGS 84 [691] -44.5,...,-10 [y]
+
+## A {terra} `rast` object
+terr <- get_agfd(cache = TRUE) |>
+ read_agfd_terra()
+
+head(terr[[1]])
+#> class : SpatRaster
+#> dimensions : 6, 886, 41 (nrow, ncol, nlyr)
+#> resolution : 0.05, 0.05 (x, y)
+#> extent : 111.975, 156.275, -10.275, -9.975 (xmin, xmax, ymin, ymax)
+#> coord. ref. : lon/lat WGS 84
+#> source(s) : memory
+#> names : farmno, R_tot~at_ha, C_tot~at_ha, FBP_f~at_ha, FBP_f~at_ha, A_whe~at_ha, ...
+#> min values : NaN, NaN, NaN, NaN, NaN, NaN, ...
+#> max values : NaN, NaN, NaN, NaN, NaN, NaN, ...
+
+## A list of {tidync} objects
+tdnc <- get_agfd(cache = TRUE) |>
+ read_agfd_tidync()
+
+head(tdnc[[1]])
+#> $source
+#> # A tibble: 1 × 2
+#> access source
+#> <dttm> <chr>
+#> 1 2024-10-26 18:24:24 /Users/adamsparks/Library/Caches/org.R-project.R/R/read.abares/historic…
+#>
+#> $axis
+#> # A tibble: 84 × 3
+#> axis variable dimension
+#> <int> <chr> <int>
+#> 1 1 lon 0
+#> 2 2 lat 1
+#> 3 3 farmno 0
+#> 4 4 farmno 1
+#> 5 5 R_total_hat_ha 0
+#> 6 6 R_total_hat_ha 1
+#> 7 7 C_total_hat_ha 0
+#> 8 8 C_total_hat_ha 1
+#> 9 9 FBP_fci_hat_ha 0
+#> 10 10 FBP_fci_hat_ha 1
+#> # ℹ 74 more rows
+#>
+#> $grid
+#> # A tibble: 3 × 4
+#> grid ndims variables nvars
+#> <chr> <int> <list> <int>
+#> 1 D0,D1 2 <tibble [41 × 1]> 41
+#> 2 D0 1 <tibble [1 × 1]> 1
+#> 3 D1 1 <tibble [1 × 1]> 1
+#>
+#> $dimension
+#> # A tibble: 2 × 8
+#> id name length unlim coord_dim active start count
+#> <int> <chr> <dbl> <lgl> <lgl> <lgl> <int> <int>
+#> 1 0 lon 886 FALSE TRUE TRUE 1 886
+#> 2 1 lat 691 FALSE TRUE TRUE 1 691
+#>
+#> $variable
+#> # A tibble: 43 × 7
+#> id name type ndims natts dim_coord active
+#> <int> <chr> <chr> <int> <int> <lgl> <lgl>
+#> 1 0 lon NC_DOUBLE 1 2 TRUE FALSE
+#> 2 1 lat NC_DOUBLE 1 2 TRUE FALSE
+#> 3 2 farmno NC_DOUBLE 2 1 FALSE TRUE
+#> 4 3 R_total_hat_ha NC_DOUBLE 2 1 FALSE TRUE
+#> 5 4 C_total_hat_ha NC_DOUBLE 2 1 FALSE TRUE
+#> 6 5 FBP_fci_hat_ha NC_DOUBLE 2 1 FALSE TRUE
+#> 7 6 FBP_fbp_hat_ha NC_DOUBLE 2 1 FALSE TRUE
+#> 8 7 A_wheat_hat_ha NC_DOUBLE 2 1 FALSE TRUE
+#> 9 8 H_wheat_dot_hat NC_DOUBLE 2 1 FALSE TRUE
+#> 10 9 A_barley_hat_ha NC_DOUBLE 2 1 FALSE TRUE
+#> # ℹ 33 more rows
+#>
+#> $attribute
+#> # A tibble: 49 × 4
+#> id name variable value
+#> <int> <chr> <chr> <named list>
+#> 1 0 _FillValue lon <dbl [1]>
+#> 2 1 units lon <chr [1]>
+#> 3 0 _FillValue lat <dbl [1]>
+#> 4 1 units lat <chr [1]>
+#> 5 0 _FillValue farmno <dbl [1]>
+#> 6 0 _FillValue R_total_hat_ha <dbl [1]>
+#> 7 0 _FillValue C_total_hat_ha <dbl [1]>
+#> 8 0 _FillValue FBP_fci_hat_ha <dbl [1]>
+#> 9 0 _FillValue FBP_fbp_hat_ha <dbl [1]>
+#> 10 0 _FillValue A_wheat_hat_ha <dbl [1]>
+#> # ℹ 39 more rows
+
+## A {data.table} object
+get_agfd(cache = TRUE) |>
+ read_agfd_dt() |>
+ head()
+#> id farmno R_total_hat_ha C_total_hat_ha FBP_fci_hat_ha
+#> <char> <num> <num> <num> <num>
+#> 1: f2022.c1991.p2022.t2022.nc 15612 7.636519 4.405228 3.231292
+#> 2: f2022.c1991.p2022.t2022.nc 21495 14.811169 9.165632 5.645538
+#> 3: f2022.c1991.p2022.t2022.nc 23418 24.874456 14.858595 10.015861
+#> 4: f2022.c1991.p2022.t2022.nc 24494 15.043653 9.326359 5.717294
+#> 5: f2022.c1991.p2022.t2022.nc 32429 23.630099 13.681063 9.949036
+#> 6: f2022.c1991.p2022.t2022.nc 32485 15.009926 9.815501 5.194425
+#> FBP_fbp_hat_ha A_wheat_hat_ha H_wheat_dot_hat A_barley_hat_ha H_barley_dot_hat
+#> <num> <num> <num> <num> <num>
+#> 1: 1.766127 NaN NaN NaN NaN
+#> 2: 6.178280 NaN NaN NaN NaN
+#> 3: 15.504923 NaN NaN NaN NaN
+#> 4: 7.212161 NaN NaN NaN NaN
+#> 5: 9.612778 NaN NaN NaN NaN
+#> 6: 6.582035 NaN NaN NaN NaN
+#> A_sorghum_hat_ha H_sorghum_dot_hat A_oilseeds_hat_ha H_oilseeds_dot_hat R_wheat_hat_ha
+#> <num> <num> <num> <num> <num>
+#> 1: NaN NaN NaN NaN NaN
+#> 2: NaN NaN NaN NaN NaN
+#> 3: NaN NaN NaN NaN NaN
+#> 4: NaN NaN NaN NaN NaN
+#> 5: NaN NaN NaN NaN NaN
+#> 6: NaN NaN NaN NaN NaN
+#> R_sorghum_hat_ha R_oilseeds_hat_ha R_barley_hat_ha Q_wheat_hat_ha Q_barley_hat_ha
+#> <num> <num> <num> <num> <num>
+#> 1: NaN NaN NaN NaN NaN
+#> 2: NaN NaN NaN NaN NaN
+#> 3: NaN NaN NaN NaN NaN
+#> 4: NaN NaN NaN NaN NaN
+#> 5: NaN NaN NaN NaN NaN
+#> 6: NaN NaN NaN NaN NaN
+#> Q_sorghum_hat_ha Q_oilseeds_hat_ha S_wheat_cl_hat_ha S_sheep_cl_hat_ha
+#> <num> <num> <num> <num>
+#> 1: NaN NaN NaN 0.000046854152
+#> 2: NaN NaN NaN 0.000066325878
+#> 3: NaN NaN NaN 0.000007771546
+#> 4: NaN NaN NaN 0.000070963917
+#> 5: NaN NaN NaN 0.000007780997
+#> 6: NaN NaN NaN 0.000059600116
+#> S_sheep_births_hat_ha S_sheep_deaths_hat_ha S_beef_cl_hat_ha S_beef_births_hat_ha
+#> <num> <num> <num> <num>
+#> 1: 0.000048411171 0.000007187978 0.02034820 0.005212591
+#> 2: 0.000057753874 0.000009039695 0.02974461 0.007970856
+#> 3: 0.000007320093 0.000000000000 0.05393181 0.014745383
+#> 4: 0.000062521929 0.000009726773 0.03057606 0.008602196
+#> 5: 0.000006834211 0.000000000000 0.04944272 0.011527594
+#> 6: 0.000053976389 0.000008478467 0.03322463 0.008456550
+#> S_beef_deaths_hat_ha Q_beef_hat_ha Q_sheep_hat_ha Q_lamb_hat_ha R_beef_hat_ha
+#> <num> <num> <num> <num> <num>
+#> 1: 0.000989490 0.004790528 0.00007117650 0 7.392679
+#> 2: 0.001468278 0.009646485 0.00009448864 0 14.281910
+#> 3: 0.002867331 0.014401773 0.00001299674 0 24.308574
+#> 4: 0.001446424 0.009577272 0.00010191595 0 14.518771
+#> 5: 0.002491037 0.014668761 0.00001283228 0 23.060943
+#> 6: 0.001627910 0.009281578 0.00008869032 0 14.474964
+#> R_sheep_hat_ha R_lamb_hat_ha C_fodder_hat_ha C_fert_hat_ha C_fuel_hat_ha C_chem_hat_ha
+#> <num> <num> <num> <num> <num> <num>
+#> 1: 0.010222802 0 0.3553107 0.0007795925 0.4282799 0.0002169123
+#> 2: 0.014485890 0 0.7040333 0.0670951492 0.5663560 0.0212989625
+#> 3: 0.001821158 0 0.9473936 0.1475929946 0.9244438 0.0398376851
+#> 4: 0.015352095 0 0.7060111 0.0764850563 0.5688555 0.0223214940
+#> 5: 0.001892115 0 1.0269189 0.1592835324 0.8337981 0.0416492516
+#> 6: 0.013278806 0 0.7019839 0.0997758317 0.5575842 0.0293469147
+#> A_total_cropped_ha FBP_pfe_hat_ha farmland_per_cell lon lat
+#> <num> <num> <num> <num> <num>
+#> 1: 0.000001588013 2.142158 62.26270 142.60 -10.75
+#> 2: 0.000144292922 6.679382 61.71605 136.75 -11.05
+#> 3: 0.000296036096 16.185389 61.82964 132.90 -11.15
+#> 4: 0.000151675639 7.711993 72.85995 136.70 -11.20
+#> 5: 0.000316535762 10.294743 61.82964 133.45 -11.60
+#> 6: 0.000201161236 7.101658 61.71605 136.25 -11.60
You can download the soil depth map and import it as a {stars} or +terra::rast() object.
+
+library(read.abares)
+get_soil_thickness(cache = TRUE) |>
+ read_soil_thickness_stars()
+#> stars object with 2 dimensions and 1 attribute
+#> attribute(s), summary of first 100000 cells:
+#> Min. 1st Qu. Median Mean 3rd Qu. Max. NA's
+#> thpk_1 NA NA NA NaN NA NA 100000
+#> dimension(s):
+#> from to offset delta refsys x/y
+#> x 1 4150 112.5 0.01 WGS 84 [x]
+#> y 1 3401 -9.995 -0.01 WGS 84 [y]
+
+x <- get_soil_thickness(cache = TRUE) |>
+ read_soil_thickness_terra()
For your convenience, {read.abares} re-exports [terra::plot()], so +you can just use:
+
+plot(x)
By default, a brief bit of metadata is printed to the console when +you call the soil thickness object in your R session.
+
+library(read.abares)
+get_soil_thickness(cache = TRUE)
+#>
+#> ── Soil Thickness for Australian areas of intensive agriculture of Layer 1 (A Horizon - top-so
+#>
+#> ── Dataset ANZLIC ID ANZCW1202000149 ──
+#>
+#> Feature attribute definition Predicted average Thickness (mm) of soil layer 1 in the 0.01 X
+#> 0.01 degree quadrat.
+#>
+#> Custodian: CSIRO Land & Water
+#>
+#> Jurisdiction Australia
+#>
+#> Short Description The digital map data is provided in geographical coordinates based on the
+#> World Geodetic System 1984 (WGS84) datum. This raster data set has a grid resolution of 0.001
+#> degrees (approximately equivalent to 1.1 km).
+#>
+#> The data set is a product of the National Land and Water Resources Audit (NLWRA) as a base
+#> dataset.
+#>
+#> Data Type: Spatial representation type RASTER
+#>
+#> Projection Map: projection GEOGRAPHIC
+#>
+#> Datum: WGS84
+#>
+#> Map Units: DECIMAL DEGREES
+#>
+#> Scale: Scale/ resolution 1:1 000 000
+#>
+#> Usage Purpose Estimates of soil depths are needed to calculate the amount of any soil
+#> constituent in either volume or mass terms (bulk density is also needed) - for example, the
+#> volume of water stored in the rooting zone potentially available for plant use, to assess
+#> total stores of soil carbon for greenhouse inventory or to assess total stores of nutrients.
+#>
+#> Provide indications of probable thickness soil layer 1 in agricultural areas where soil
+#> thickness testing has not been carried out.
+#>
+#> Use Limitation: This dataset is bound by the requirements set down by the National Land &
+#> Water Resources Audit
+#> To see the full metadata, call `print_soil_thickness_metadata()` in your R session.
But, {read.abares} provides a function for you to browse the soil +thickness metadata in your console.
+
+library(read.abares)
+get_soil_thickness(cache = TRUE) |>
+ print_soil_thickness_metadata()
+#>
+#> ── Soil Thickness for Australian areas of intensive agriculture of Layer 1 (A Horizon - top-so
+#>
+#> ── Dataset ANZLIC ID ANZCW1202000149 ──
+#>
+#> Dataset ANZLIC ID ANZCW1202000149
+#>
+#> Title Soil Thickness for Australian areas of intensive agriculture of Layer 1 (A Horizon -
+#> top-soil) (derived from soil mapping)
+#>
+#> Custodian CSIRO, Land & Water
+#>
+#> Jurisdiction Australia
+#>
+#> Description Abstract Surface of predicted Thickness of soil layer 1 (A Horizon - top-soil)
+#> surface for the intensive agricultural areas of Australia. Data modelled from area based
+#> observations made by soil agencies both State and CSIRO and presented as .0.01 degree grid
+#> cells.
+#>
+#> Topsoils (A horizons) are defined as the surface soil layers in which organic matter
+#> accumulates, and may include dominantly organic surface layers (O and P horizons).
+#>
+#> The depth of topsoil is important because, with their higher organic matter contents,
+#> topsoils (A horizon) generally have more suitable properties for agriculture, including
+#> higher permeability and higher levels of soil nutrients.
+#>
+#> Estimates of soil depths are needed to calculate the amount of any soil constituent in either
+#> volume or mass terms (bulk density is also needed) - for example, the volume of water stored
+#> in the rooting zone potentially available for plant use, to assess total stores of soil
+#> carbon for Greenhouse inventory or to assess total stores of nutrients.
+#>
+#> The pattern of soil depth is strongly related to topography - the shape and slope of the
+#> land. Deeper soils are typically found in the river valleys where soils accumulate on
+#> floodplains and at the footslopes of ranges (zones of deposition), while soils on hillslopes
+#> (zones of erosion) tend to be shallow. Map of thickness of topsoil was derived from soil map
+#> data and interpreted tables of soil properties for specific soil groups.
+#>
+#> The quality of data on soil depth in existing soil profile datasets is questionable and as
+#> the thickness of soil horizons varies locally with topography, values for map units are
+#> general averages.
+#>
+#> The final ASRIS polygon attributed surfaces are a mosaic of all of the data obtained from
+#> various state and federal agencies. The surfaces have been constructed with the best
+#> available soil survey information available at the time. The surfaces also rely on a number
+#> of assumptions. One being that an area weighted mean is a good estimate of the soil
+#> attributes for that polygon or map-unit. Another assumption made is that the look-up tables
+#> provided by McKenzie et al. (2000), state and territories accurately depict the soil
+#> attribute values for each soil type.
+#>
+#> The accuracy of the maps is most dependent on the scale of the original polygon data sets and
+#> the level of soil survey that has taken place in each state. The scale of the various soil
+#> maps used in deriving this map is available by accessing the data-source grid, the scale is
+#> used as an assessment of the likely accuracy of the modelling. The Atlas of Australian Soils
+#> is considered to be the least accurate dataset and has therefore only been used where there
+#> is no state based data. Of the state datasets Western Australian sub-systems, South
+#> Australian land systems and NSW soil landscapes and reconnaissance mapping would be the most
+#> reliable based on scale. NSW soil landscapes and reconnaissance mapping use only one dominant
+#> soil type per polygon in the estimation of attributes. South Australia and Western Australia
+#> use several soil types per polygon or map-unit.
+#>
+#> The digital map data is provided in geographical coordinates based on the World Geodetic
+#> System 1984 (WGS84) datum. This raster data set has a grid resolution of 0.001 degrees
+#> (approximately equivalent to 1.1 km).
+#>
+#> The data set is a product of the National Land and Water Resources Audit (NLWRA) as a base
+#> dataset.
+#>
+#> Search Word(s) AGRICULTURE SOIL Physics Models
+#>
+#> Geographic Extent Name(s) GEN Category
+#>
+#> GEN Custodial Jurisdiction
+#>
+#> GEN Name
+#>
+#> Geographic Bounding Box North Bounding Latitude -10.707149 South Bounding Latitude -43.516831
+#> East Bounding Longitude 113.19673 West Bounding Longitude 153.990779
+#>
+#> Geographic Extent Polygon(s) 115.0 -33.5,115.7 -33.3,115.7 -31.7,113.2 -26.2,113.5
+#> -25.4,114.1 -26.4,114.3 -26.0,113.4 -24.3,114.1 -21.8,122.3 -18.2,122.2 -17.2,126.7
+#> -13.6,129.1 -14.9,130.6 -12.3,132.6 -12.1,132.5 -11.6,131.9 -11.3,132.0 -11.1,137.0
+#> -12.2,135.4 -14.7,140.0 -17.7,140.8 -17.4,141.7 -15.1,141.4 -13.7,142.2 -10.9,142.7
+#> -10.7,143.9 -14.5,144.6 -14.1,145.3 -14.9,146.3 -18.8,148.9 -20.5,150.9 -22.6,153.2
+#> -25.9,153.7 -28.8,153.0 -31.3,150.8 -34.8,150.0 -37.5,147.8 -37.9,146.3 -39.0,144.7
+#> -38.4,143.5 -38.8,141.3 -38.4,139.7 -37.3,139.7 -36.9,139.9 -36.7,138.9 -35.5,138.1
+#> -35.7,138.6 -34.7,138.1 -34.2,137.8 -35.1,136.9 -35.3,137.0 -34.9,137.5 -34.9,137.4
+#> -34.0,137.9 -33.5,137.8 -32.6,137.3 -33.6,135.9 -34.7,136.1 -34.8,136.0 -35.0,135.1
+#> -34.6,135.2 -34.5,135.4 -34.5,134.7 -33.3,134.0 -32.9,133.7 -32.1,133.3 -32.2,132.2
+#> -32.0,131.3 -31.5,127.3 -32.3,126.0 -32.3,123.6 -33.9,123.2 -34.0,122.1 -34.0,121.9
+#> -33.8,119.9 -34.0,119.6 -34.4,118.0 -35.1,116.0 -34.8,115.0 -34.3,115.0 -33.5
+#>
+#> 147.8 -42.9,147.9 -42.6,148.2 -42.1,148.3 -42.3,148.3 -41.3,148.3 -41.0,148.0 -40.7,147.4
+#> -41.0,146.7 -41.1,146.6 -41.2,146.5 -41.1,146.4 -41.2,145.3 -40.8,145.3 -40.7,145.2
+#> -40.8,145.2 -40.8,145.2 -40.8,145.0 -40.8,144.7 -40.7,144.7 -41.2,145.2 -42.2,145.4
+#> -42.2,145.5 -42.4,145.5 -42.5,145.2 -42.3,145.5 -43.0,146.0 -43.3,146.0 -43.6,146.9
+#> -43.6,146.9 -43.5,147.1 -43.3,147.0 -43.1,147.2 -43.3,147.3 -42.8,147.4 -42.9,147.6
+#> -42.8,147.5 -42.8,147.8 -42.9,147.9 -43.0,147.7 -43.0,147.8 -43.2,147.9 -43.2,147.9
+#> -43.2,148.0 -43.2,148.0 -43.1,148.0 -42.9,147.8 -42.9
+#>
+#> 136.7 -13.8,136.7 -13.7,136.6 -13.7,136.6 -13.8,136.4 -13.8,136.4 -14.1,136.3 -14.2,136.9
+#> -14.3,137.0 -14.2,136.9 -14.2,136.7 -14.1,136.9 -13.8,136.7 -13.8,136.7 -13.8
+#>
+#> 139.5 -16.6,139.7 -16.5,139.4 -16.5,139.2 -16.7,139.3 -16.7,139.5 -16.6
+#>
+#> 153.0 -25.2,153.0 -25.7,153.1 -25.8,153.4 -25.0,153.2 -24.7,153.2 -25.0,153.0 -25.2
+#>
+#> 137.5 -36.1,137.7 -35.9,138.1 -35.9,137.9 -35.7,137.6 -35.7,137.6 -35.6,136.6 -35.8,136.7
+#> -36.1,137.2 -36.0,137.5 -36.1
+#>
+#> 143.9 -39.7,144.0 -39.6,144.1 -39.8,143.9 -40.2,143.9 -40.0,143.9 -39.7
+#>
+#> 148.0 -39.7,147.7 -39.9,147.9 -39.9,148.0 -40.1,148.1 -40.3,148.3 -40.2,148.3 -40.0,148.0
+#> -39.7
+#>
+#> 148.1 -40.4,148.0 -40.4,148.4 -40.3,148.4 -40.5,148.1 -40.4
+#>
+#> 130.4 -11.3,130.4 -11.2,130.6 -11.3,130.7 -11.4,130.9 -11.3,131.0 -11.4,131.1 -11.3,131.2
+#> -11.4,131.3 -11.2,131.5 -11.4,131.5 -11.5,131.0 -11.9,130.8 -11.8,130.6 -11.7,130.0
+#> -11.8,130.1 -11.7,130.3 -11.7,130.1 -11.5,130.4 -11.3
+#>
+#> Data Currency Beginning date 1999-09-01
+#>
+#> Ending date 2001-03-31
+#>
+#> Dataset Status Progress COMPLETE
+#>
+#> Maintenance and Update Frequency NOT PLANNED
+#>
+#> Access Stored Data Format DIGITAL - ESRI Arc/Info integer GRID
+#>
+#> Available Format Type DIGITAL - ESRI Arc/Info integer GRID
+#>
+#> Access Constraint Subject to the terms & condition of the data access & management agreement
+#> between the National Land & Water Audit and ANZLIC parties
+#>
+#> Data Quality Lineage The soil attribute surface was created using the following datasets 1.
+#> The digital polygon coverage of the Soil-Landforms of the Murray Darling Basis (MDBSIS)(Bui
+#> et al. 1998), classified as principal profile forms (PPF's) (Northcote 1979). 2. The digital
+#> Atlas of Australian Soils (Northcote et al.1960-1968)(Leahy, 1993). 3. Western Australia land
+#> systems coverage (Agriculture WA). 4. Western Australia sub-systems coverage (Agriculture
+#> WA). 5. Ord river catchment soils coverage (Agriculture WA). 6. Victoria soils coverage
+#> (Victorian Department of Natural Resources and Environment - NRE). 7. NSW Soil Landscapes and
+#> reconnaissance soil landscape mapping (NSW Department of Land and Water Conservation - DLWC).
+#> 8. New South Wales Land systems west (NSW Department of Land and Water Conservation - DLWC).
+#> 9. South Australia soil land-systems (Primary Industries and Resources South Australia -
+#> PIRSA). 10. Northern Territory soils coverage (Northern Territory Department of Lands,
+#> Planning and Environment). 11. A mosaic of Queensland soils coverages (Queensland Department
+#> of Natural Resources - QDNR). 12. A look-up table linking PPF values from the Atlas of
+#> Australian Soils with interpreted soil attributes (McKenzie et al. 2000). 13. Look_up tables
+#> provided by WA Agriculture linking WA soil groups with interpreted soil attributes. 14.
+#> Look_up tables provided by PIRSA linking SA soil groups with interpreted soil attributes.
+#>
+#> The continuous raster surface representing Thickness of soil layer 1 was created by combining
+#> national and state level digitised land systems maps and soil surveys linked to look-up
+#> tables listing soil type and corresponding attribute values.
+#>
+#> Because thickness is used sparingly in the Factual Key, estimations of thickness in the
+#> look-up tables were made using empirical correlations for particular soil types.
+#>
+#> To estimate a soil attribute where more than one soil type was given for a polygon or
+#> map-unit, the soil attribute values related to each soil type in the look-up table were
+#> weighted according to the area occupied by that soil type within the polygon or map-unit. The
+#> final soil attribute values are an area weighted average for a polygon or map-unit. The
+#> polygon data was then converted to a continuous raster surface using the soil attribute
+#> values calculated for each polygon.
+#>
+#> The ASRIS soil attribute surfaces created using polygon attribution relied on a number of
+#> data sets from various state agencies. Each polygon data set was turned into a continuous
+#> surface grid based on the calculated soil attribute value for that polygon. The grids where
+#> then merged on the basis that, where available, state data replaced the Atlas of Australian
+#> Soils and MDBSIS. MDBSIS derived soil attribute values were restricted to areas where MDBSIS
+#> was deemed to be more accurate that the Atlas of Australian Soils (see Carlile et al (2001a).
+#>
+#> In cases where a soil type was missing from the look-up table or layer 2 did not exist for
+#> that soil type, the percent area of the soils remaining were adjusted prior to calculating
+#> the final soil attribute value. The method used to attribute polygons was dependent on the
+#> data supplied by individual State agencies.
+#>
+#> The modelled grid was resampled from 0.0025 degree cells to 0.01 degree cells using bilinear
+#> interpolation
+#>
+#> Positional Accuracy The predictive surface is a 0.01 X 0.01 degree grid and has a locational
+#> accurate of about 1m.
+#>
+#> The positional accuracy of the defining polygons have variable positional accuracy most
+#> locations are expected to be within 100m of the recorded location. The vertical accuracy is
+#> not relevant. The positional assessment has been made by considering the tools used to
+#> generate the locational information and contacting the data providers.
+#>
+#> The other parameters used in the production of the led surface have a range of positional
+#> accuracy ranging from + - 50 m to + - kilometres. This contribute to the loss of attribute
+#> accuracy in the surface.
+#>
+#> Attribute Accuracy Input attribute accuracy for the areas is highly variable. The predictive
+#> has a variable and much lower attribute accuracy due to the irregular distribution and the
+#> limited positional accuracy of the parameters used for modelling.
+#>
+#> There are several sources of error in estimating soil depth and thickness of horizons for the
+#> look-up tables. Because thickness is used sparingly in the Factual Key, estimations of
+#> thickness in the look-up tables were made using empirical correlations for particular soil
+#> types. The quality of data on soil depth in existing soil profile datasets is questionable,
+#> in soil mapping, thickness of soil horizons varies locally with topography, so values for map
+#> units are general averages. The definition of the depth of soil or regolith is imprecise and
+#> it can be difficult to determine the lower limit of soil.
+#>
+#> The assumption made that an area weighted mean of soil attribute values based on soil type is
+#> a good estimation of a soil property is debatable, in that it does not supply the soil
+#> attribute value at any given location. Rather it is designed to show national and regional
+#> patterns in soil properties. The use of the surfaces at farm or catchment scale modelling may
+#> prove inaccurate. Also the use of look-up tables to attribute soil types is only as accurate
+#> as the number of observations used to estimate a attribute value for a soil type. Some soil
+#> types in the look-up tables may have few observations, yet the average attribute value is
+#> still taken as the attribute value for that soil type. Different states are using different
+#> taxonomic schemes making a national soil database difficult. Another downfall of the area
+#> weighted approach is that some soil types may not be listed in look-up tables. If a soil type
+#> is a dominant one within a polygon or map-unit, but is not listed within the look-up table or
+#> is not attributed within the look-up table then the final soil attribute value for that
+#> polygon will be biased towards the minor soil types that do exist. This may also happen when
+#> a large area is occupied by a soil type which has no B horizon. In this case the final soil
+#> attribute value will be area weighted on the soils with a B horizon, ignoring a major soil
+#> type within that polygon or map-unit. The layer 2 surfaces have large areas of no-data
+#> because all soils listed for a particular map-unit or polygon had no B horizon.
+#>
+#> Logical Consistency Surface is fully logically consistent as only one parameter is shown, as
+#> predicted average Soil Thickness within each grid cell
+#>
+#> Completeness Surface is nearly complete. There are some areas (about %1 missing) for which
+#> insufficient parameters were known to provide a useful prediction and thus attributes are
+#> absent in these areas.
+#>
+#> Contact Information Contact Organisation (s) CSIRO, Land & Water
+#>
+#> Contact Position Project Leader
+#>
+#> Mail Address ACLEP, GPO 1666
+#>
+#> Locality Canberra
+#>
+#> State ACT
+#>
+#> Country AUSTRALIA
+#>
+#> Postcode 2601
+#>
+#> Telephone 02 6246 5922
+#>
+#> Facsimile 02 6246 5965
+#>
+#> Electronic Mail Address neil.mckenzie@cbr.clw.csiro.au
+#>
+#> Metadata Date Metadata Date 2001-07-01
+#>
+#> Additional Metadata Additional Metadata
+#>
+#> Entity and Attributes Entity Name Soil Thickness Layer 1 (derived from mapping)
+#>
+#> Entity description Estimated Soil Thickness (mm) of Layer 1 on a cell by cell basis
+#>
+#> Feature attribute name VALUE
+#>
+#> Feature attribute definition Predicted average Thickness (mm) of soil layer 1 in the 0.01 X
+#> 0.01 degree quadrat
+#>
+#> Data Type Spatial representation type RASTER
+#>
+#> Projection Map projection GEOGRAPHIC
+#>
+#> Datum WGS84
+#>
+#> Map units DECIMAL DEGREES
+#>
+#> Scale Scale/ resolution 1:1 000 000
+#>
+#> Usage Purpose Estimates of soil depths are needed to calculate the amount of any soil
+#> constituent in either volume or mass terms (bulk density is also needed) - for example, the
+#> volume of water stored in the rooting zone potentially available for plant use, to assess
+#> total stores of soil carbon for Greenhouse inventory or to assess total stores of nutrients.
+#>
+#> Provide indications of probable Thickness soil layer 1 in agricultural areas where soil
+#> thickness testing has not been carried out
+#>
+#> Use Use Limitation This dataset is bound by the requirements set down by the National Land &
+#> Water Resources Audit
But you can also access it directly and use pander::pander() to +include it in a document like this vignette.
+++++library(read.abares) +library(pander) +x <- get_soil_thickness(cache = TRUE) +y <- x$metadata +pander(y)
Dataset ANZLIC ID ANZCW1202000149
+Title Soil Thickness for Australian areas of intensive agriculture of +Layer 1 (A Horizon - top-soil) (derived from soil mapping)
+Custodian CSIRO, Land & Water
+Jurisdiction Australia
+Description Abstract Surface of predicted Thickness of soil layer 1 +(A Horizon - top-soil) surface for the intensive agricultural areas of +Australia. Data modelled from area based observations made by soil +agencies both State and CSIRO and presented as .0.01 degree grid +cells.
+Topsoils (A horizons) are defined as the surface soil layers in which +organic matter accumulates, and may include dominantly organic surface +layers (O and P horizons).
+The depth of topsoil is important because, with their higher organic +matter contents, topsoils (A horizon) generally have more suitable +properties for agriculture, including higher permeability and higher +levels of soil nutrients.
+Estimates of soil depths are needed to calculate the amount of any +soil constituent in either volume or mass terms (bulk density is also +needed) - for example, the volume of water stored in the rooting zone +potentially available for plant use, to assess total stores of soil +carbon for Greenhouse inventory or to assess total stores of +nutrients.
+The pattern of soil depth is strongly related to topography - the +shape and slope of the land. Deeper soils are typically found in the +river valleys where soils accumulate on floodplains and at the +footslopes of ranges (zones of deposition), while soils on hillslopes +(zones of erosion) tend to be shallow. Map of thickness of topsoil was +derived from soil map data and interpreted tables of soil properties for +specific soil groups.
+The quality of data on soil depth in existing soil profile datasets +is questionable and as the thickness of soil horizons varies locally +with topography, values for map units are general averages.
+The final ASRIS polygon attributed surfaces are a mosaic of all of +the data obtained from various state and federal agencies. The surfaces +have been constructed with the best available soil survey information +available at the time. The surfaces also rely on a number of +assumptions. One being that an area weighted mean is a good estimate of +the soil attributes for that polygon or map-unit. Another assumption +made is that the look-up tables provided by McKenzie et al. (2000), +state and territories accurately depict the soil attribute values for +each soil type.
+The accuracy of the maps is most dependent on the scale of the +original polygon data sets and the level of soil survey that has taken +place in each state. The scale of the various soil maps used in deriving +this map is available by accessing the data-source grid, the scale is +used as an assessment of the likely accuracy of the modelling. The Atlas +of Australian Soils is considered to be the least accurate dataset and +has therefore only been used where there is no state based data. Of the +state datasets Western Australian sub-systems, South Australian land +systems and NSW soil landscapes and reconnaissance mapping would be the +most reliable based on scale. NSW soil landscapes and reconnaissance +mapping use only one dominant soil type per polygon in the estimation of +attributes. South Australia and Western Australia use several soil types +per polygon or map-unit.
+The digital map data is provided in geographical coordinates based on +the World Geodetic System 1984 (WGS84) datum. This raster data set has a +grid resolution of 0.001 degrees (approximately equivalent to 1.1 +km).
+The data set is a product of the National Land and Water Resources +Audit (NLWRA) as a base dataset.
+Search Word(s) AGRICULTURE
+
+SOIL Physics ModelsGeographic Extent Name(s) GEN Category
+GEN Custodial Jurisdiction
+GEN Name
+Geographic Bounding Box North Bounding Latitude -10.707149 South +Bounding Latitude -43.516831 East Bounding Longitude 113.19673 West +Bounding Longitude 153.990779
+Geographic Extent Polygon(s) 115.0 -33.5,115.7 -33.3,115.7 +-31.7,113.2 -26.2,113.5 -25.4,114.1 -26.4,114.3 -26.0,113.4 -24.3,114.1 +-21.8,122.3 -18.2,122.2 -17.2,126.7 -13.6,129.1 -14.9,130.6 -12.3,132.6 +-12.1,132.5 -11.6,131.9 -11.3,132.0 -11.1,137.0 -12.2,135.4 -14.7,140.0 +-17.7,140.8 -17.4,141.7 -15.1,141.4 -13.7,142.2 -10.9,142.7 -10.7,143.9 +-14.5,144.6 -14.1,145.3 -14.9,146.3 -18.8,148.9 -20.5,150.9 -22.6,153.2 +-25.9,153.7 -28.8,153.0 -31.3,150.8 -34.8,150.0 -37.5,147.8 -37.9,146.3 +-39.0,144.7 -38.4,143.5 -38.8,141.3 -38.4,139.7 -37.3,139.7 -36.9,139.9 +-36.7,138.9 -35.5,138.1 -35.7,138.6 -34.7,138.1 -34.2,137.8 -35.1,136.9 +-35.3,137.0 -34.9,137.5 -34.9,137.4 -34.0,137.9 -33.5,137.8 -32.6,137.3 +-33.6,135.9 -34.7,136.1 -34.8,136.0 -35.0,135.1 -34.6,135.2 -34.5,135.4 +-34.5,134.7 -33.3,134.0 -32.9,133.7 -32.1,133.3 -32.2,132.2 -32.0,131.3 +-31.5,127.3 -32.3,126.0 -32.3,123.6 -33.9,123.2 -34.0,122.1 -34.0,121.9 +-33.8,119.9 -34.0,119.6 -34.4,118.0 -35.1,116.0 -34.8,115.0 -34.3,115.0 +-33.5
+147.8 -42.9,147.9 -42.6,148.2 -42.1,148.3 -42.3,148.3 -41.3,148.3 +-41.0,148.0 -40.7,147.4 -41.0,146.7 -41.1,146.6 -41.2,146.5 -41.1,146.4 +-41.2,145.3 -40.8,145.3 -40.7,145.2 -40.8,145.2 -40.8,145.2 -40.8,145.0 +-40.8,144.7 -40.7,144.7 -41.2,145.2 -42.2,145.4 -42.2,145.5 -42.4,145.5 +-42.5,145.2 -42.3,145.5 -43.0,146.0 -43.3,146.0 -43.6,146.9 -43.6,146.9 +-43.5,147.1 -43.3,147.0 -43.1,147.2 -43.3,147.3 -42.8,147.4 -42.9,147.6 +-42.8,147.5 -42.8,147.8 -42.9,147.9 -43.0,147.7 -43.0,147.8 -43.2,147.9 +-43.2,147.9 -43.2,148.0 -43.2,148.0 -43.1,148.0 -42.9,147.8 -42.9
+136.7 -13.8,136.7 -13.7,136.6 -13.7,136.6 -13.8,136.4 -13.8,136.4 +-14.1,136.3 -14.2,136.9 -14.3,137.0 -14.2,136.9 -14.2,136.7 -14.1,136.9 +-13.8,136.7 -13.8,136.7 -13.8
+139.5 -16.6,139.7 -16.5,139.4 -16.5,139.2 -16.7,139.3 -16.7,139.5 +-16.6
+153.0 -25.2,153.0 -25.7,153.1 -25.8,153.4 -25.0,153.2 -24.7,153.2 +-25.0,153.0 -25.2
+137.5 -36.1,137.7 -35.9,138.1 -35.9,137.9 -35.7,137.6 -35.7,137.6 +-35.6,136.6 -35.8,136.7 -36.1,137.2 -36.0,137.5 -36.1
+143.9 -39.7,144.0 -39.6,144.1 -39.8,143.9 -40.2,143.9 -40.0,143.9 +-39.7
+148.0 -39.7,147.7 -39.9,147.9 -39.9,148.0 -40.1,148.1 -40.3,148.3 +-40.2,148.3 -40.0,148.0 -39.7
+148.1 -40.4,148.0 -40.4,148.4 -40.3,148.4 -40.5,148.1 -40.4
+130.4 -11.3,130.4 -11.2,130.6 -11.3,130.7 -11.4,130.9 -11.3,131.0 +-11.4,131.1 -11.3,131.2 -11.4,131.3 -11.2,131.5 -11.4,131.5 -11.5,131.0 +-11.9,130.8 -11.8,130.6 -11.7,130.0 -11.8,130.1 -11.7,130.3 -11.7,130.1 +-11.5,130.4 -11.3
+Data Currency Beginning date 1999-09-01
+Ending date 2001-03-31
+Dataset Status Progress COMPLETE
+Maintenance and Update Frequency NOT PLANNED
+Access Stored Data Format DIGITAL - ESRI Arc/Info integer GRID
+Available Format Type DIGITAL - ESRI Arc/Info integer GRID
+Access Constraint Subject to the terms & condition of the data +access & management agreement between the National Land & Water +Audit and ANZLIC parties
+Data Quality Lineage The soil attribute surface was created using the +following datasets 1. The digital polygon coverage of the Soil-Landforms +of the Murray Darling Basis (MDBSIS)(Bui et al. 1998), classified as +principal profile forms (PPF’s) (Northcote 1979). 2. The digital Atlas +of Australian Soils (Northcote et al.1960-1968)(Leahy, 1993). 3. Western +Australia land systems coverage (Agriculture WA). 4. Western Australia +sub-systems coverage (Agriculture WA). 5. Ord river catchment soils +coverage (Agriculture WA). 6. Victoria soils coverage (Victorian +Department of Natural Resources and Environment - NRE). 7. NSW Soil +Landscapes and reconnaissance soil landscape mapping (NSW Department of +Land and Water Conservation - DLWC). 8. New South Wales Land systems +west (NSW Department of Land and Water Conservation - DLWC). 9. South +Australia soil land-systems (Primary Industries and Resources South +Australia - PIRSA). 10. Northern Territory soils coverage (Northern +Territory Department of Lands, Planning and Environment). 11. A mosaic +of Queensland soils coverages (Queensland Department of Natural +Resources - QDNR). 12. A look-up table linking PPF values from the Atlas +of Australian Soils with interpreted soil attributes (McKenzie et +al. 2000). 13. Look_up tables provided by WA Agriculture linking WA soil +groups with interpreted soil attributes. 14. Look_up tables provided by +PIRSA linking SA soil groups with interpreted soil attributes.
+The continuous raster surface representing Thickness of soil layer 1 +was created by combining national and state level digitised land systems +maps and soil surveys linked to look-up tables listing soil type and +corresponding attribute values.
+Because thickness is used sparingly in the Factual Key, estimations +of thickness in the look-up tables were made using empirical +correlations for particular soil types.
+To estimate a soil attribute where more than one soil type was given +for a polygon or map-unit, the soil attribute values related to each +soil type in the look-up table were weighted according to the area +occupied by that soil type within the polygon or map-unit. The final +soil attribute values are an area weighted average for a polygon or +map-unit. The polygon data was then converted to a continuous raster +surface using the soil attribute values calculated for each polygon.
+The ASRIS soil attribute surfaces created using polygon attribution +relied on a number of data sets from various state agencies. Each +polygon data set was turned into a continuous surface grid based on the +calculated soil attribute value for that polygon. The grids where then +merged on the basis that, where available, state data replaced the Atlas +of Australian Soils and MDBSIS. MDBSIS derived soil attribute values +were restricted to areas where MDBSIS was deemed to be more accurate +that the Atlas of Australian Soils (see Carlile et al (2001a).
+In cases where a soil type was missing from the look-up table or +layer 2 did not exist for that soil type, the percent area of the soils +remaining were adjusted prior to calculating the final soil attribute +value. The method used to attribute polygons was dependent on the data +supplied by individual State agencies.
+The modelled grid was resampled from 0.0025 degree cells to 0.01 +degree cells using bilinear interpolation
+Positional Accuracy The predictive surface is a 0.01 X 0.01 degree +grid and has a locational accurate of about 1m.
+The positional accuracy of the defining polygons have variable +positional accuracy most locations are expected to be within 100m of the +recorded location. The vertical accuracy is not relevant. The positional +assessment has been made by considering the tools used to generate the +locational information and contacting the data providers.
+The other parameters used in the production of the led surface have a +range of positional accuracy ranging from + - 50 m to + - kilometres. +This contribute to the loss of attribute accuracy in the surface.
+Attribute Accuracy Input attribute accuracy for the areas is highly +variable. The predictive has a variable and much lower attribute +accuracy due to the irregular distribution and the limited positional +accuracy of the parameters used for modelling.
+There are several sources of error in estimating soil depth and +thickness of horizons for the look-up tables. Because thickness is used +sparingly in the Factual Key, estimations of thickness in the look-up +tables were made using empirical correlations for particular soil types. +The quality of data on soil depth in existing soil profile datasets is +questionable, in soil mapping, thickness of soil horizons varies locally +with topography, so values for map units are general averages. The +definition of the depth of soil or regolith is imprecise and it can be +difficult to determine the lower limit of soil.
+The assumption made that an area weighted mean of soil attribute +values based on soil type is a good estimation of a soil property is +debatable, in that it does not supply the soil attribute value at any +given location. Rather it is designed to show national and regional +patterns in soil properties. The use of the surfaces at farm or +catchment scale modelling may prove inaccurate. Also the use of look-up +tables to attribute soil types is only as accurate as the number of +observations used to estimate a attribute value for a soil type. Some +soil types in the look-up tables may have few observations, yet the +average attribute value is still taken as the attribute value for that +soil type. Different states are using different taxonomic schemes making +a national soil database difficult. Another downfall of the area +weighted approach is that some soil types may not be listed in look-up +tables. If a soil type is a dominant one within a polygon or map-unit, +but is not listed within the look-up table or is not attributed within +the look-up table then the final soil attribute value for that polygon +will be biased towards the minor soil types that do exist. This may also +happen when a large area is occupied by a soil type which has no B +horizon. In this case the final soil attribute value will be area +weighted on the soils with a B horizon, ignoring a major soil type +within that polygon or map-unit. The layer 2 surfaces have large areas +of no-data because all soils listed for a particular map-unit or polygon +had no B horizon.
+Logical Consistency Surface is fully logically consistent as only one +parameter is shown, as predicted average Soil Thickness within each grid +cell
+Completeness Surface is nearly complete. There are some areas (about +%1 missing) for which insufficient parameters were known to provide a +useful prediction and thus attributes are absent in these areas.
+Contact Information Contact Organisation (s) CSIRO, Land & +Water
+Contact Position Project Leader
+Mail Address ACLEP, GPO 1666
+Locality Canberra
+State ACT
+Country AUSTRALIA
+Postcode 2601
+Telephone 02 6246 5922
+Facsimile 02 6246 5965
+Electronic Mail Address neil.mckenzie@cbr.clw.csiro.au
+Metadata Date Metadata Date 2001-07-01
+Additional Metadata Additional Metadata
+Entity and Attributes Entity Name Soil Thickness Layer 1 (derived +from mapping)
+Entity description Estimated Soil Thickness (mm) of Layer 1 on a cell +by cell basis
+Feature attribute name VALUE
+Feature attribute definition Predicted average Thickness (mm) of soil +layer 1 in the 0.01 X 0.01 degree quadrat
+Data Type Spatial representation type RASTER
+Projection Map projection GEOGRAPHIC
+Datum WGS84
+Map units DECIMAL DEGREES
+Scale Scale/ resolution 1:1 000 000
+Usage Purpose Estimates of soil depths are needed to calculate the +amount of any soil constituent in either volume or mass terms (bulk +density is also needed) - for example, the volume of water stored in the +rooting zone potentially available for plant use, to assess total stores +of soil carbon for Greenhouse inventory or to assess total stores of +nutrients.
+Provide indications of probable Thickness soil layer 1 in +agricultural areas where soil thickness testing has not been carried +out
+Use Use Limitation This dataset is bound by the requirements set down by +the National Land & Water Resources Audit +