Geology TAS Classification Lookup

Silica/total-alkali TAS class coordinates, independently verified same-edition polygons, not plotting bands. Shared boundaries and overlaps retained; polygons must be simple non-self-intersecting. Caller independently establishes matching units, evidence, method edition and applicability; output is not compliance, diagnosis, work-safety approval, geological identity or validated hazard prediction.

Description

A total-alkali–silica classification uses composition coordinates and an adopted set of class boundaries.

A total-alkali–silica classification uses composition coordinates and an adopted set of class boundaries.^[1]

Classifying a point requires independently normalized analyses and the correct diagram edition; polygon containment alone does not identify a rock. Use this tool to calculate tas classification lookup from the supplied measurements and assumptions.

When to use Geology TAS Classification Lookup

Use this tool to calculate tas classification lookup from the supplied measurements and assumptions. Establish the measurement units, sampled interval, calibration or model edition and geological assumptions before entering data.

How to use Geology TAS Classification Lookup and understand its results

Establish the measurement units, sampled interval, calibration or model edition and geological assumptions before entering data.
Enter observedTasX, observedTasY, callerTasClassIds, callerTasVertices, using the field meanings and rules below, then run the tool.
Read matchingClasses. Interpret the fields using their units, signs and evidence conventions below.
If input validation fails, correct the reported field and run again. Before applying the result, check reference scope, model assumptions and any missing evidence or placeholder values.

Input field	Meaning	Value type	Requirement
observedTasX	Observed tas x	number	Required
observedTasY	Observed tas y	number	Required
callerTasClassIds	Caller tas class ids	list of string	Required
callerTasVertices	Caller tas vertices	list of list of number	Required

Enter finite point coordinates, unique class IDs and a vertex matrix whose rows are [zero-based class index, x, y]. Use at most 64 classes and 128 total vertices. Group vertices by class in the supplied order; each polygon needs at least three distinct vertices and nonzero area. A repeated closing endpoint is removed; other repeated vertices, intersecting nonadjacent edges and invalid integer class indices fail. The implementation applies an even–odd ray-crossing test and includes points exactly on a segment. Return every containing class in caller order, so overlapping polygons or shared boundaries may yield several classes; no match yields an empty list. Boundaries and coordinate preprocessing are independently supplied.

matches={class_i:point is inside polygon_i or exactly on its boundary}

Use the exact units, boundary rules, ordering and missing-evidence conventions above.

Output field	Meaning	Value type
matchingClasses	Matching Classes; follow the units, sign, ordering and evidence convention stated above	list of string

json

{
  "input": {
    "observedTasX": 0.5,
    "observedTasY": 0.5,
    "callerTasClassIds": [
      "a",
      "b"
    ],
    "callerTasVertices": [
      [
        0,
        0,
        0
      ],
      [
        0,
        1,
        0
      ],
      [
        0,
        1,
        1
      ],
      [
        0,
        0,
        1
      ],
      [
        1,
        0.5,
        0.5
      ],
      [
        1,
        2,
        0.5
      ],
      [
        1,
        2,
        2
      ],
      [
        1,
        0.5,
        2
      ]
    ]
  },
  "output": {
    "matchingClasses": [
      "a",
      "b"
    ]
  }
}

Limitations and assumptions

Classifying a point requires independently normalized analyses and the correct diagram edition; polygon containment alone does not identify a rock. Interpretation depends on the units, sampling scope and exact model described above.

All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse evidence arrays fail validation; the specific bounds and alignment requirements are stated above. Extremely large inputs or outputs can also be rejected. An input error is distinct from a successful result reporting false, no matches or missing evidence.

Alternative or Complementary methods

Use Geology QAPF Classification Lookup for this related task: QAPF classification uses independently determined mineral proportions and a specified classification diagram.

Use Geology Folk Sandstone Classification Lookup when its separate inputs and assumptions fit the question: A Folk sandstone classification depends on independently identified components and the adopted diagram convention.

References

Geology TAS Classification Lookup — tool.io

Similar or alternative tools

Geology QAPF Classification Lookup
QAPF classification uses independently determined mineral proportions and a specified classification diagram.
Geology Folk Sandstone Classification Lookup
A Folk sandstone classification depends on independently identified components and the adopted diagram convention.