============================ Output table fields & values ============================ | To serve OCTOPUS database collections as geospatial layers via an interactive map :ref:`Web_interface` and to allow for data manipulation via the :ref:`Web_Feature_Service` protocol, data sub-collections are served to GeoServer as a flat data tables, which are described in detail below [#]_. | When downloading data from OCTOPUS, users are presented with point or polygon geospatial data files with associated attribute tables. Direct connections to the PostgreSQL/PostGIS database are possible upon request. Munack and Codilean (`2022 `_) provide a complete documentation of the relational database, including a detailed database model diagram and searchable HTML documentation generated using SchemaSpy (https://schemaspy.org, last access: 21 Aug 2023). .. note:: The above section is a modified version of Section 3 from `Codilean et al. 2022 `_ .. _CRN_output: CRN output ---------- | OCTOPUS CRN Be-10 and Al-26 data have been recalculated [#]_ so that nuclide concentrations and denudation rates are internally consistent and comparable. These and related data, including concentrations and denudation rates as published, are served as geospatial vector layers (see :ref:`CRN_vector_spatial_data`). | In addition, OCTOPUS CRN collections also provide :ref:`CRN_ancillary_data` comprising **raster layers**\ , including a digital elevation model, gradient raster, flow direction and flow accumulation rasters, atmospheric pressure raster, and CRN production scaling and topographic shielding factor rasters, as well as a set of **structured input data files** (see :ref:`CSV_folder` subsection) for the purpose of data recalculation integrity. The idea behind the above is that, since the CAIRN algorithm is automated (see `LSDTopoTools documentation `_), users can simply publish a DEM of their study area, CRN data files, and CAIRN input files, and denudation rates should be reproducible. .. _CRN_vector_spatial_data: CRN vector spatial data ^^^^^^^^^^^^^^^^^^^^^^^ The vector spatial data uses the WGS84 / Pseudo-Mercator (EPSG: 3857) projected coordinate reference system. .. csv-table:: :file: ./csv_tables/crn_output.csv :header-rows: 1 .. tip:: For detailed field / variable descriptions follow the links given under "Origin (Alias)". .. _CRN_ancillary_data: CRN ancillary data ^^^^^^^^^^^^^^^^^^ .. _CSV_folder: 'CSV' folder ~~~~~~~~~~~~ * s..._\ **CRNData.csv** -- CAIRN CRN concentrations input file (see `LSDTopoTools documentation `_) * s..._\ **CRNRasters.csv** -- Path to raster files (see `LSDTopoTools documentation `_) * s..._\ **CRNResults.csv** -- Original CAIRN output (= results) * s..._\ **CRONUSInput.txt** -- CAIRN-derived CRONUS copy-and-paste input * s...._\ **CRNParam** -- CAIRN input parameter file (see `LSDTopoTools documentation `_) .. _Raster_folder: 'Raster' folder ~~~~~~~~~~~~~~~ The raster data uses the WGS84/UTM projected coordinate reference system, UTM zones depending on the extent and location of each data package. * s..._\ **atmospres**\ .bil -- An atmospheric pressure raster, showing local atmospheric pressure in hPa calculated based on the NCEP2 climate reanalysis data (`Compo et al., 2011 `_) * s..._\ **atmospres**\ .hdr -- *s..._atmospres.bil* header file * s..._\ **d8flowdir**\ .bil -- A flow-direction raster calculated using the D8 flow-routing method (`Jenson and Domingue, 1988 `_) * s..._\ **d8flowdir**\ .hdr -- *s..._d8flowdir.bil* header file * s..._\ **demhydro**\ .bil -- A hydrologically corrected DEM with elevation values in metres (raster) * s..._\ **demhydro**\ .hdr -- *s..._demhydro.bil* header file * s..._\ **flowacc**\ .bil -- A flow-accumulation raster calculated with the same D8 method as used for *d8flowdir* * s..._\ **flowacc**\ .hdr -- *s..._flowacc.bil* header file * s..._\ **gradmkm**\ .bil -- A slope gradient raster calculated using the method described in Horn (`1981 `_) with units in m km-1 * s..._\ **gradmkm**\ .hdr -- *s..._gradmkm.bil* header file * s..._\ **prodscale**\ .bil -- A cosmogenic nuclide production scaling raster calculated using the method described in Stone (`Stone, 2000 `_) * s..._\ **prodscale**\ .hdr -- *s..._prodscale.bil* header file * s..._\ **toposhield**\ .bil -- A cosmogenic nuclide production topographic shielding raster calculated using the method described in Codilean (`2006 `_) * s..._\ **toposhield**\ .hdr -- *s..._toposhield.bil* header file .. note:: Raster files are provided in .bil (**B**\ and **I**\ nterleaved by **L**\ ine) image encoding format, which cannot be considered an image format itself, but is depended on the accompanying header (.hdr) file meaning that users will always need the pair of files with one and the same filename. .. _SahulArch_output: SahulArch output ---------------- .. _SahulArch_C14_output: SahulArch C14 output ^^^^^^^^^^^^^^^^^^^^ .. csv-table:: :file: ./csv_tables/arch_c14_output.csv :header-rows: 1 .. tip:: For detailed field / variable descriptions follow the links given under "Origin (Alias)". .. _SahulArch_OSL_output: SahulArch OSL output ^^^^^^^^^^^^^^^^^^^^ .. csv-table:: :file: ./csv_tables/arch_osl_output.csv :header-rows: 1 .. tip:: For detailed field / variable descriptions follow the links given under "Origin (Alias)". .. _SahulArch_TL_output: SahulArch TL output ^^^^^^^^^^^^^^^^^^^ .. csv-table:: :file: ./csv_tables/arch_tl_output.csv :header-rows: 1 .. tip:: For detailed field / variable descriptions follow the links given under "Origin (Alias)". .. _SahulSed_output: SahulSed output --------------- .. _SahulSed_OSL_output: SahulSed OSL output ^^^^^^^^^^^^^^^^^^^ .. csv-table:: :file: ./csv_tables/sed_osl_output.csv :header-rows: 1 .. tip:: For detailed field / variable descriptions follow the links given under "Origin (Alias)". .. _SahulSed_TL_output: SahulSed TL output ^^^^^^^^^^^^^^^^^^ .. csv-table:: :file: ./csv_tables/sed_tl_output.csv :header-rows: 1 .. tip:: For detailed field / variable descriptions follow the links given under "Origin (Alias)". .. _FosSahul_output: FosSahul output --------------- .. csv-table:: :file: ./csv_tables/fos_output.csv :header-rows: 1 .. tip:: For detailed field / variable descriptions follow the links given under "Origin (Alias)". .. _expage_output: ExpAge output ------------- .. csv-table:: :file: ./csv_tables/expage_output.csv :header-rows: 1 .. tip:: For detailed field / variable descriptions follow the links given under "Origin (Alias)". .. rubric:: Footnotes .. [#] The deployed version of GeoServer does not accept dynamically generated PostgreSQL virtual tables (knows as "views"); therefore, the generation of static flat data tables was required to serve the purpose of a view. Newer versions of GeoServer, however, accept materialised views, and an upgrade would present a possible improvement in the database by eliminating the need to store duplicate data. .. [#] Be-10 and Al-26 concentrations (atoms g-1) were renormalised to the Nishiizumi 2007 Be-10 AMS standard (`Nishiizumi et al., 2007 `_) and to the Nishiizumi 2004 Al-26 AMS standard (`Nishiizumi, 2004 `_) respectively. Basin-wide denudation rates were recalculated with the open-source program CAIRN (`Mudd et al., 2016 `_) with the following parameter settings: (i) nuclide production from neutrons and muons was calculated with the approximation of Braucher et al. (`2011 `_) using a sea-level and high-latitude total production rate of 4.3 atoms g-1 yr-1 for Be-10 and of 31.1 atoms g-1 yr-1 for Al-26; (ii) latitude and altitude scaling factors were calculated using the time-independent Lal--Stone scaling scheme (`Stone, 2000 `_) with atmospheric pressure calculated via interpolation from the National Centers for Environmental Prediction NCEP2 reanalysis data (`Compo et al., 2011 `_); and (iii) topographic shielding was calculated from the same digital elevation model (DEM) using the method of Codilean (`2006 `_).