Skip to content

Main content

Grain Size Bin Closure Token Tool

Apply explicit sieve-size bin endpoint conventions in one common size unit.

Loading tool…

Description

inBin combines the supplied includeLower and includeUpper rules when comparing size against the two numeric endpoints.

Spatial and grain-size summaries depend on area, bin width, scale and boundary conventions. Area-weighted coverage differs from pixel counts, while density per transformed grain-size unit differs from a raw bin fraction.

inBin combines the supplied includeLower and includeUpper rules when comparing size against the two numeric endpoints.

When to use this tool

Use Grain Size Bin Closure Token when checking a supplied spatial, grain-bin or ground-support quantity.

How to use the tool and how it works

  1. Enter size, lower, upper, includeLower, includeUpper. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read inBin. Inspect inBin before interpreting the associated values.

Require lower < upper. inBin combines the supplied includeLower and includeUpper rules when comparing size against the two numeric endpoints.1

Input fieldMeaning and unitsAccepted input
sizeSizeRequired. Finite number.
lowerLower bound under the stated coordinate, derivative or uncertainty convention.Required. Finite number.
upperUpper bound under the stated coordinate, derivative or uncertainty convention.Required. Finite number.
includeLowerInclude LowerRequired. Boolean.
includeUpperInclude UpperRequired. Boolean.
Output fieldInterpretationReturned shape
inBinIn BinRequired. Boolean.
json
{
  "input": {
    "size": 2,
    "lower": 1,
    "upper": 2,
    "includeLower": true,
    "includeUpper": false
  },
  "output": {
    "inBin": false
  }
}

Limitations and assumptions

  • No size positivity or grain classification is inferred. Shared-edge double counting depends on how callers assign closure across neighboring bins.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Use suitable mapping, grain-size and sampling methods for complete spatial distributions and geological interpretation.

References

  1. Calculation and input contract: earth-science/grain-size-bin-closure-token — tool.io

Similar or alternative tools