GithubHelp home page GithubHelp logo

anzsoildata / def-au-asls-soil-prof Goto Github PK

View Code? Open in Web Editor NEW
0.0 0.0 0.0 41.21 MB

Machine-readable representation of the classifiers described in chapter 8 Soil Profile, by R.C. McDonald and R.F. Isbell, in Australian soil and land survey field handbook (3rd edn)

def-au-asls-soil-prof's People

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

def-au-asls-soil-prof's Issues

horizon prefix and suffix

prefix and suffix into one result/one column of data against obsv property “horizon classification”
This requires a vocab for eg for “B22k”

Does each prefix suffix combination need to be created?

classifiers and numeric results

The YB assigns classifiers to numeric ranges
eg see size "2" "Medium" for results in range of 5 - 15 mm

if data providers give a number as a result eg "7 mm", then we are storing it as that.

We were not sure if "medium" was more meaningful as a result to some soil folk? we stored this as a separate result (for one dataset, at least) - Pretty cumbersome

Don't think this has implications for YB encoding, but just flagging FYI as data transfer issue

@bsimons14 may have further comment here

feature type concepts

We are using the following vocab terms and their identifiers to describe features.
Currently they are type SKOS Collection (not features).
I think this is all of them. We are only using a subset of these, but we have them stored in our DB as features
http://anzsoil.org/def/au/asls/soil-profile/boundaries-between-horizons

http://anzsoil.org/def/au/asls/soil-profile/coarse-fragments

http://anzsoil.org/def/au/asls/soil-profile/cutans

http://anzsoil.org/def/au/asls/soil-profile/mottles-and-other-colour-patterns

http://anzsoil.org/def/au/asls/soil-profile/pans

http://anzsoil.org/def/au/asls/soil-profile/roots
http://anzsoil.org/def/au/asls/soil-profile/voids

peds and segregations-of-pedogenic-origin – we are not using as features

For observable properties you have defined as type SKOS Collection and type Observable Property. Might it be possible to do similar for features also?

obsv prop and procedure as the one concept/PID

re concepts that are collections and also observable properties (eg texture class)
They include the procedure in the descriptions

This made it a bit confusing to know:
whether it is appropriate to use these obsv properties in association with results obtained by different procedures
to know whether to use the YB classifiers if the procedure that was used to obtain the results was unknown

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.