ForHosting KIT · Travel & geography

Pollen Count Severity Category Classifier

A tree pollen count of 95 grains per cubic metre is high, because the tree scale turns high at 90 and very high at 1,500. Grass and weed pollen each use their own thresholds. Free in your browser.

  • Free
  • Runs in your browser
  • No sign-up
  • Your data stays on your device
Use it from WebAPIEmailTelegramApp soon
If you enter
Quantity
95
Pollen type
tree
You get
Category
high

Pollen numbers are difficult to interpret without knowing which plant group produced them. This classifier converts a non-negative airborne pollen count into a clear low, moderate, high, or very-high category using common allergy reference thresholds for tree, grass, and weed pollen. It also returns the normalized pollen type and the boundaries used for that scale, making the result easy to display, audit, or use in an automated alert. The calculation is deterministic, requires no network lookup, and rejects unsupported pollen types instead of applying a misleading generic threshold.

Choose the pollen type before interpreting the count

A raw pollen count does not have one universal meaning because tree, grass, and weed pollen are released and measured at very different typical concentrations. Start by supplying the count in grains per cubic meter and identify the source as tree, grass, or weed. The classifier normalizes capitalization and surrounding spaces, so values such as TREE and tree are treated consistently.

It deliberately does not guess a source from a plant name or accept an unknown group. That strict behavior matters: a count that is moderate on a tree scale may already be high on another scale. By returning an error for an unrecognized type, the capability prevents a plausible-looking but scientifically mismatched label from entering a forecast, notification, or patient-facing display.

Counts must be finite and non-negative. Decimal counts are accepted, which is useful when an upstream instrument or aggregation process reports an average rather than a whole-number observation. The response repeats the normalized count and pollen type so downstream systems can confirm exactly what was classified.

Understand the category boundaries

The calculation uses widely cited allergy reporting bands. Tree pollen is low below 15, moderate from 15 through values below 90, high from 90 through values below 1,500, and very high at 1,500 or above. Grass pollen is low below 5, moderate from 5 through values below 20, high from 20 through values below 200, and very high at 200 or above.

Weed pollen is low below 10, moderate from 10 through values below 50, high from 50 through values below 500, and very high at 500 or above. Boundary comparisons are exact: a value equal to the start of a band belongs to that band. Personal symptoms vary with sensitization, exposure duration, medication, location, and other conditions, so the result should support general information and operational decisions rather than replace individualized clinical advice.

Use consistent classifications in products and workflows

Use the classifier after obtaining a pollen observation from a monitoring station, laboratory feed, or your own approved dataset. Pass each observation with its matching source group, then store or display the returned category beside the original value. Weather applications can map the four stable category strings to colors, while alerting workflows can trigger only for high or very-high results.

Data teams can also classify historical records before charting them, ensuring that the same boundary logic is applied across every row and every release of a product. Because the algorithm has no network requests, random values, current-time dependency, or mutable state, the same input always produces the same output. That makes results reproducible in tests and audits.

Keep the source count and pollen type with the result because monitoring organizations may publish values with different sampling periods or local conventions. If your provider explicitly defines another scale, follow that provider instead of silently mixing its counts with these common reference bands.

Label a pollen dashboard

Turn station readings into consistent low, moderate, high, and very-high labels for tree, grass, and weed panels.

Power exposure alerts

Classify incoming observations before deciding whether an application should issue a high-pollen notification.

Normalize historical data

Apply one documented set of category boundaries to archived pollen readings before analysis or visualization.

Which pollen types are supported?

Tree, grass, and weed pollen are supported. Any other value returns an invalid-input error so the wrong scale is never selected silently.

What unit should the count use?

Provide the airborne concentration in pollen grains per cubic meter of air, the unit commonly used with these category bands.

How are exact boundary values classified?

A value equal to a boundary enters the higher band. For example, a tree count of 90 is high, while 1,500 is very high.

Does a high category predict my symptoms?

No. It categorizes airborne concentration. Individual reactions depend on sensitization, exposure, health, medication, and other factors.

Why does the same count get different categories for grass and tree pollen?

Each plant group is released and measured at very different typical levels, so each has its own scale. A count of 20 is already high for grass pollen but only moderate for tree or weed pollen.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/weather/pollen-count-category

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/weather/pollen-count-category \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"count":95,"pollen_type":"tree"}'
{
  "count": 95,
  "pollen_type": "tree"
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "weather.pollen_count_category",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Understand the category boundaries

The output includes moderate_from, high_from, and very_high_from values so an interface can explain the decision without duplicating constants. These categories describe airborne concentration, not an individual medical outcome.

Use consistent classifications in products and workflows

The endpoint costs $0.002 per item through the API and uses the same deterministic calculation as the browser experience.

What does an API classification cost?

Each item costs $0.002. The calculation is deterministic and does not call an external data provider.

Read the full KIT documentation →