GithubHelp home page GithubHelp logo

anzsoildata / def-au-parameters Goto Github PK

View Code? Open in Web Editor NEW
0.0 5.0 0.0 3 KB

A representation of chemical and physical parameters of soil based on the Parameter Usage Vocabulary (PUV) Semantic Model

License: Creative Commons Zero v1.0 Universal

def-au-parameters's People

Contributors

meganrwong avatar

Watchers

brandon whitehead avatar Simon Cox avatar Bruce Simons avatar Alistair Ritchie avatar  avatar

def-au-parameters's Issues

use of 'Concentration' and 'ConcentrationRatio' for S06 chemistry

Feedback welcome, logging issue and decision reached

Have decided not to use 'proportion' for S06 of for any of the soil chemical parameters measured by procedures in the 'green books'.

Did not use Mass Ratio either. ConcentrationRatio was used. Total organic carbon (TOC) to total soil nitrogen (TSN) could be Mass Ratio - but have used concentration of in all of the underlying methods, because they inconsistently say 'report as concentration', though all report in %.

And, it is not clear in S06 examples what when 'proportion of ' v 'concentration of' should be used. So, for now, have just used 'concentration of' in all instances

Though 'proportion' may make more sense in some cases (community feedback welcome), the rationale for using 'proportion' consistently for the soil chem parameters could not be determined

Concentration was used for everything reported in percentages, MassRatios eg in mg/kg , MassConcentrations eg in ug/L and AmountOfSubstancePerUnitVolume eg cmol/L

see terms used in BODC S06 - https://vocab.nerc.ac.uk/collection/S06/current/

differentiation between S06 and S29 - feedback sought

at present we are only using these S06 terms -
concentration
concentration ratio
presence or absence of

what could have been properties, have been moved to S29. These include complex properties that are for example calculation such as indices, ratios etc, proxies etc. In general, those properties that do not make sense to break down under the model. For example, there are some cases that have 'concentration' and 'ratio' in the S29 term, and 'percentage'. It did not make sense to break these out, the community is used to seeing these things as they are this way.

extract of some of our S29 looks like -

moisture content
Electrical conductivity (EC)
Estimated soluble salts
Ionic strength
Redox potential (Eh)
pH
pH reactivity class
pH change (ฮ” pH)
total organic carbon (TOC) to total soil nitrogen (TSN)
Anion storage capacity (previously P retention)
Phosphate Sorption Index (P sorption index)
P buffer index (PBI)
Equilibrium phosphorus concentration (EPC)
Phosphorus buffering capacity (PBC)
P saturation ratio
Colwell-P/PBI (ColP) ratio
Electrical conducivity (EC)
cation exchange capacity (CEC)
Exchange acidity
Effective cation exchange capacity (ECEC)
Base saturation percentage (BSP)
Calcium to Magnesium (Ca2+/Mg2+)
extractable Calcium (Ca)
soluble Sulfur (S)
Total Sulfidic Acidity (TSAD-B)
Residual Quick Neutralising Capacity (RQNCD-B)
lime requirement for drain spoil

However, perhaps some of these should be properties under S06 (or the, are 'compound properties' under I-ADOPT.

For example:

note - we decided it was not great to use terms 'determination' and 'measurement' in S29 so have not done so

related Entities

for soil chem parameters as measured by scm books/methods
we can assume these are all on fine soil fraction <2mm soil
is there any need to build this into parameter, or the parameters model in any way?

There seems to be just one exception in scm - https://raw.githack.com/ANZSoilData/def-au-scma/master/html/19-alkaline-earth-carbonates/19C1.html
method 19C1 measures the presence or absence of carbonates in -

  1. bedrock fragment
  2. Carbonate concretions > nodules, threads and masses
  3. fine soil ('soil matrix') <2mm particle size

@dr-shorthair These could be built into the soil parameter model? In I-ADOPT I see this is Entity
Presuming these Entities will need to go into ANSIS model.....

Notation and Alt labels

required?
not sure what these would be if required
Could include some acronyms from the methods eg "TPA"

chemical qualifiers - in S27?

Question from within #nvs-vocabs/P01/issues/208

"in our application, there are a variety of 'qualifiers' of chemicals used, including soluble, exchangable, pseudo, oxidisable, extractable, reducible, titratable. Do you think these should be included in separate S27 entities, in the same way that you have Organic carbon and easily-reducible total iron "

Solution, for now - they are within S27 eg 'oxidisable carbon' . 'total' is integrated too eg 'total carbon'

So, note now we have no subcomponent terms https://vocab.nerc.ac.uk/collection/S12/current/ocab.nerc.ac.uk/collection/S12/current/

Feedback welcome on our approach

related chemical entity - to eg CAS or ChEBI

Chem experts could work on this. To compile the list of related chem entities for each parameter, checking the valencies etc and matching with CAS number and or ChEBI
For now, we have just expressed all as stated in the method headers and or 'report as' sections, without referencing CAS or ChEBI (or other list if more appropriate? )

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.