Vegetation context stays explainable and contract-bounded.
This generalized example shows the questions a reviewer would inspect; it is not a live regional assessment or current capability claim.
Charging Grid Intelligence...
Vegetation intelligence
Vegetation can contribute to grid stress when trees or branches interact with infrastructure, especially during wind, precipitation, ice, or other severe conditions. When an exact region-and-horizon source and feature contract permits it, GeoGridIQ can use dated vegetation indicators as screening context alongside weather, outage history, and generalized infrastructure context. NDVI does not directly measure clearance, species, tree condition, or contact with an asset, and it cannot establish outage cause. This page is conceptual: a current capability claim requires separate dynamic evidence for the relevant region and horizon.
Visual evidence
Illustrative examples - not live utility forecasts.
This generalized example shows the questions a reviewer would inspect; it is not a live regional assessment or current capability claim.
Each source must be permitted for the exact scope and available by the issue-time cutoff; presence in this table does not prove current use.
| Signal | What it measures | Why it matters |
|---|---|---|
| Satellite vegetation indicators | Dated greenness or change proxies when permitted | Screen broad areas; do not measure clearance, species, health, or contact |
| Pre-cutoff outage history | Past qualifying events under a declared label contract | Provides association context, not proof that vegetation caused an outage |
| Weather evidence | Authorized forecasts or observations available by issue time | Describes environmental stress without converting NDVI into a probability |
| Generalized infrastructure context | Non-sensitive corridor or asset-class context | Supports review without exposing precise protected locations |
| Spatial alignment | Declared grid, resolution, buffers, and coverage | Prevents a coarse vegetation pixel from implying exact asset conditions |
| Source-health evidence | Freshness, completeness, quality, and missingness | Determines whether the signal is usable, limited, or unavailable |
These categories are conceptual. They do not assign contribution weights or claim that a signal caused an outage.
| Context signal | Supported interpretation | Required boundary |
|---|---|---|
| Vegetation indicator | A dated satellite proxy may suggest broad greenness | Not tree-to-line clearance, condition, species, or causation |
| Historical association | Past events may identify an area for review | Not a vegetation-cause determination |
| Weather stress | Permitted forecasts may describe relevant conditions | Not proof of asset contact or failure |
| Essential-service context | Consequence may affect human review priority | Does not raise physical outage likelihood |
A real ordering requires an authorized ranking mode, exact eligible population, issue time, and dynamic availability evidence.
| Generalized area | Illustrative review context | Do not infer |
|---|---|---|
| Screening area A | Vegetation indicator and weather context available | A calibrated outage probability |
| Screening area B | Vegetation evidence is older than other sources | Current conditions from stale imagery |
| Screening area C | Partial satellite coverage | That uncovered locations have low exposure |
| Screening area D | Generalized essential-service context | An exact protected-asset location |
| Screening area E | Required evidence missing | A zero-risk or low-priority result |
This non-live schematic shows spatial relationships only; it is not a current map, a probability surface, or a field-clearance survey.
The workflow applies only when its exact source, spatial, temporal, and feature contracts pass; it does not automate maintenance or dispatch.
Permitted, dated satellite indicators can screen broad greenness or change while retaining their resolution and coverage limits.
Pre-cutoff qualifying outage history can provide association context without assigning a vegetation cause.
Weather evidence may add timing context when it is available by issue time and valid for the declared window.
Operators inspect mode, provenance, uncertainty, consequence, and current capability evidence before choosing any action.
This conceptual matrix describes questions a documented issue-time evaluation could test; it does not report current performance.
| Question | GeoGridIQ evidence | Operational value |
|---|---|---|
| Which areas were eligible? | Declared population, dated source coverage, and feature contract | Avoid treating missing coverage as low exposure |
| What did the issue-time snapshot contain? | Immutable values, missingness, freshness, and provenance | Prevent later data from leaking into the review |
| Did a later qualifying event match? | Separate spatial, temporal, label, and provider-coverage rules | Distinguish observed outcomes from unknowns |
| Was the signal useful? | Named evaluation period, eligible population, and declared metrics | Support evidence-based review without causal claims |
| Is the capability current? | Dynamic source, artifact, batch, validity, and display gates | Show unavailable when current evidence does not pass |
When permitted by the exact region-and-horizon contract, GeoGridIQ may combine dated satellite vegetation indicators, eligible pre-cutoff outage history, authorized weather evidence, generalized infrastructure context, and spatial-quality flags to screen areas for review. A listed source family does not prove that it is active, fresh, complete, or used in a current model.
Vegetation may interact with wind, precipitation, ice, soil conditions, and infrastructure. NDVI is a broad satellite greenness proxy: it does not directly observe tree-to-line clearance, species, structural condition, ownership, trimming need, or an outage cause. Field and provider evidence remain necessary for those conclusions.
A contract-bounded assessment can help reviewers compare eligible areas, inspect change and source quality, and identify where additional evidence may be useful. Relative ordering is not calibrated probability, missing data is not low risk, and generalized vegetation context does not identify the condition of a particular circuit or asset.
An explanation should name the exact row, issue time, valid window, mode, batch, source state, and supported context. Vegetation, history, weather, and consequence may be presented as review factors, but no causal driver percentage is implied. Confidence, where implemented, describes the declared evidence-quality contract rather than probability or certainty that vegetation caused an event.
When current dynamic evidence shows the capability is available, the bounded context may support inspection planning, corridor review, storm preparation, and requests for better data. It does not confirm a hazard, order maintenance, dispatch crews, or replace utility procedures, field inspection, or operator judgment.
Scheduled inspections, utility records, and field expertise remain authoritative for vegetation management. A separately authorized predictive or ranking path may add time-bound screening context, but only for its declared geography, population, horizon, and output semantics. No output autonomously schedules work or dispatches a crew.
Evaluation requires an issue-time snapshot recorded before outcomes, adequate provider coverage, and declared spatial, temporal, and label-matching rules. Later associations can test usefulness but do not establish vegetation causation. Performance must be reported with its exact track, region, horizon, period, population, and limitations; this page does not publish a current performance result.
Frequently asked questions
NDVI is the Normalized Difference Vegetation Index, a satellite-derived greenness indicator. It can support broad screening, but resolution, season, cloud, surface type, and source age matter. It does not directly measure clearance, species, tree condition, contact with infrastructure, or outage cause.
No. Vegetation is contextual evidence and only enters a forecast when the exact source and feature contract permits it. Any current output also needs passing source, exact public-serving path, batch, validity, and display evidence; otherwise the capability must be shown as limited or unavailable.
Related GeoGridIQ resources
See how GeoGridIQ presents time-bound outage-risk outputs with source, model, validity, uncertainty, and explanation context for human review.
Learn how generalized, non-sensitive essential-service context may support consequence-aware outage-risk review without replacing physical-likelihood evidence or operator judgment.
Learn how conditional, human-reviewed crew-staging context may support preparedness when access, prediction, and authoritative crew-data gates pass.