Environmental Intelligence (ENVINT): Intelligence Discipline Guide

Physical conditions decide whether a site stays operational, whether a supplier ships, and whether a claim about the ground is true. Environmental intelligence reads the ground itself.

What Environmental Intelligence is as a discipline

Environmental intelligence is the collection and analysis of information about the physical environment surrounding assets, operations and incidents: terrain, land use, hydrology, seismic and flood hazard, air and water quality, industrial contamination, fire and vegetation state, and observable damage or change. It relies heavily on remote sensing, combining optical, radar, thermal and multispectral satellite imagery with ground truth from environmental monitoring agencies, geological surveys and open geospatial datasets. Analysis is change-focused: what is different, when did it change, and what plausibly caused it.

Sub-methods include change detection comparing co-registered image pairs across time, hazard modelling overlaying assets on flood, seismic and wildfire exposure layers, damage assessment after an event, and environmental-crime detection covering illegal mining, deforestation, dumping and unpermitted discharge. Maturity runs from ad-hoc imagery review to automated change alerting over defined areas of interest, with every imagery-derived observation validated against an independent sensor or ground record before an assessment is issued.

Why it matters

Environmental intelligence answers what physically happened at a location and what is physically at risk there. It provides independent verification when a counterparty, supplier or claimant describes conditions on the ground. It quantifies exposure that appears nowhere in financial or corporate records, such as a data centre inside a floodplain or a supplier whose only plant sits in a wildfire corridor. For investigators it produces dated, geolocated evidence of activity that nobody reported.

What analysts actually look for

These are the concrete, observable signals that carry weight in this area of work:

Multi-date optical imagery change showing construction, demolition, excavation, tailings expansion or vegetation clearance with dated acquisition times
Synthetic aperture radar backscatter change detecting surface disturbance and flood extent through cloud cover and at night
Thermal anomalies and active-fire detections indicating flaring, burning, industrial activity or wildfire progression and direction
Flood extent, river gauge levels and inundation modelling assessed relative to asset footprints and access routes
Seismic event catalogues with magnitude, depth and distance to critical facilities, plus historical recurrence for that fault system
Air and water quality measurements from official monitoring networks near an operation, including particulate, gas and turbidity readings
Land cover classification change indicating deforestation, illegal mining, agricultural conversion or waste dumping over time
Ground deformation from radar interferometry revealing subsidence, landslide movement or structural instability beneath infrastructure

Where the data comes from

Authoritative and openly available collection points. Always confirm licensing and terms before operational or commercial use:

Copernicus Sentinel — Free optical and radar imagery on a short revisit cycle, the backbone of open change detection
USGS Landsat and EarthExplorer — Decades of consistent multispectral imagery supporting long-baseline change and land use analysis
NASA FIRMS — Near-real-time active fire and thermal anomaly detections from MODIS and VIIRS instruments
Copernicus Emergency Management Service — Rapid mapping products with flood, fire and damage extents published after major events
USGS Earthquake Hazards Program — Authoritative global seismic event catalogue with magnitude, depth and hazard modelling products
OpenStreetMap — Open base geography for infrastructure, roads, land use and building footprints to overlay on imagery
Global Forest Watch — Deforestation and land cover change alerts with historical baselines and per-country reporting
National environmental agency data — EPA and equivalent bodies publish permits, emissions, discharge and air and water quality readings

A working method

A repeatable sequence beats ad-hoc searching. This is a practical starting workflow:

Define area and question — Fix the geographic boundary, the time window and the specific physical question. Imagery without a question produces pictures, not intelligence.
Assemble a baseline — Collect pre-event imagery and environmental readings so change is measured against a documented normal state rather than an assumption.
Select the right sensor — Match sensor to problem: radar for cloud and night, thermal for heat and fire, multispectral for vegetation and water condition.
Detect and measure change — Compare co-registered scenes, quantify change in area and magnitude, and record acquisition timestamps for every image used.
Corroborate on the ground — Validate the interpretation against gauges, monitoring stations, permits or official reporting before drawing any causal conclusion.
Assess consequence — Overlay the change on asset, population and supply-route layers to translate a physical fact into operational or legal significance.
Document reproducibly — Record scene identifiers, processing steps and coordinate reference systems so another analyst can reproduce the finding exactly.

How this connects across the intelligence taxonomy

Intelligence work does not respect neat boundaries. The mission domain you are working, the disciplines you practise, and the data points you pivot on are one connected system. These are the direct relationships for this entry — every link is also a tag, so you can follow any thread across the whole library.

Applied in these mission domains

Operates on these data points

Location / Coordinates — A geographic point, place, or region — the basis of GEOINT analysis.
Shipment / Bill of Lading — A consignment record linking shipper, consignee, goods, and route.
Company / Organization — A legal entity — corporation, LLC, NGO, or business.
Event / Incident — A discrete real-world occurrence — protest, strike, breach, seizure — with time, place, and actors.
Satellite Imagery — Overhead imagery of an area of interest, used for change detection and site analysis.
GPS Coordinates — Precise latitude/longitude coordinates identifying an exact point on Earth — the atomic unit of GEOINT analysi
HS Commodity Code — The Harmonized System code classifying a traded good — the key to trade-flow analysis.
Facility / Site — A physical installation — plant, base, port, data centre — with a fixed footprint and function.
Image / Photograph — A still image — carries EXIF metadata and is the primary artifact for visual verification.

Related disciplines

Meteorological Intelligence — Weather, Ocean, and Atmospheric Conditions

Inside the platform: where Environmental Intelligence lives

The Quantus platform is 204 pages behind a 147-item sidebar organised into six working groups: Command (24 items), Dashboards (15), Threat Theaters (14), Intelligence Domains (15), Investigate (34), and Administration (45). This entry is not a page in isolation — it is a thread running through several of them.

The modules that matter most here:

discipline.php?d=ENVINT — Discipline hub
source-catalog.php?disc=ENVINT — Source catalogue filtered to this discipline
search.php — Company / Organization profile
correlate.php — Correlation graph
cases.php — Case management

Each dashboard is local-first: it renders from the platform’s own database rather than depending on a live third-party call, so it still works when an upstream API is unreachable or rate-limited. Heavy aggregates are cached with a hard query time cap and degrade to the last good value instead of hanging the page.

Automation, playbooks and AI skills

Analysis that only happens when someone remembers to run it is not a capability. The platform ships a 30-step automation pipeline (cron.php) that collects, ingests, resolves, enriches, correlates and scores on a schedule — 25 seeders, 11 resolvers and 7 enrichment runners, all idempotent and cursor-based so a run can be interrupted and resumed without duplicating or losing work.

AI skills that apply

The 16 one-click operations in ai-skills.php are deterministic jobs, not free-text generation. The ones that matter here:

Score Country Risk
Sync Intel Domains
Resolve Everything
Summarise (Copilot)
Generate Report

Alerting closes the loop: rules in alerts.php fire on new indicators matching a saved query, so a first sighting in this area raises a notification rather than waiting to be noticed at the next review.

Feeds, data sources and the API

The collection layer runs a feed registry of free, machine-readable sources — bulk blocklists and trackers (Maltrail, IPsum, FireHOL, the full abuse.ch corpora, phishing databases, Emerging Threats, Spamhaus, DigitalSide, ThreatView), authoritative government feeds (CISA KEV, OFAC, UN and EU sanctions lists), and reference datasets (RIR allocations, ip-to-ASN and geolocation tables, MITRE ATT&CK, EPSS). collect.php pulls them server-side on a schedule; feeds.php and source-catalog.php show what is registered, what it covers and when it last ran.

Anything the platform holds is reachable programmatically. The REST API in api.php exposes 11 endpoints — status, stats, search, lookup, recent, export, bulk_check, top_threats, by_category, categories, check — and export.php streams 18 formats in bounded chunks, so a million-row export neither exhausts memory nor times out:

STIX 2.1, MISP, OpenIOC 1.1, CEF (ArcSight), LEEF 2.0 (QRadar), Zeek/Bro intel, Snort/Suricata rules, Palo Alto EDL, BIND RPZ, hosts blackhole, iptables, CSV, JSON, NDJSON/JSONL, XML.

That covers the CTI standards (STIX 2.1, MISP, OpenIOC), SIEM ingestion (CEF, LEEF, Zeek), detection engines (Snort/Suricata), and direct enforcement (Palo Alto EDL, BIND RPZ, hosts, iptables) — so intelligence developed here can be actioned in the tools you already run, without a manual reformatting step. A TAXII 2.1 server and a MISP/RSS feed are also served for pull-based sharing.

Use cases

Three ways this entry earns its keep in day-to-day work:

Triage under time pressure. An artifact or report lands and you need a defensible read in minutes, not days. Define area and question is the first move; the platform pre-computes the enrichment so the analyst spends the time on judgement rather than lookups.
Building the picture. A single indicator is rarely the story. Select the right sensor turns one artifact into a network — shared infrastructure, repeated selectors, the same operator behind different names — via the correlation graph and the cross-entity link engine.
Producing something actionable. Analysis that ends in a document nobody can use is wasted. Document reproducibly feeds the case file, the detection rule, the block list or the referral — with sourcing attached so the recipient can verify it.

Case management (cases.php), watchlists, saved searches and scheduled reports mean the work persists between sessions and survives an analyst leaving the team.

How each sector uses Environmental Intelligence

The same entry is worked very differently depending on who you are, what authority you hold, and what you are ultimately producing. A military analyst is supporting a commander’s decision; a journalist is meeting a publication standard; an NGO caseworker is protecting a person. The underlying artifacts are shared — the constraints, outputs and thresholds are not.

🎖 Military and defence

Defence practitioners use environmental intelligence for terrain analysis, mobility assessment, engineering planning and force protection. The discipline produces trafficability estimates from soil and moisture data, flood and landslide hazard for route and site selection, vegetation state for concealment and fire risk, and change detection over infrastructure and facilities. It is a core input to intelligence preparation of the operating environment and to basing and sustainment decisions. Constraint: remote sensing products used to support any targeting process must go through the established collateral damage and legal review, and environmental analysis touching protected sites, cultural property or civilian water infrastructure carries specific obligations under the law of armed conflict.

🕵 National intelligence

National services practise environmental intelligence as geospatial and remote sensing analysis in support of requirements on facilities, resource extraction, nuclear and industrial activity, and environmental change with strategic consequences. The analytic method is change detection over time series, combining optical, radar and thermal observation so that cloud, night and deliberate concealment do not create gaps. Commercial imagery has substantially changed this discipline by making much of it releasable, so products are commonly written at a level that can be shared with partners and, in some cases, publicly. Handling reflects that the target selection and the tasking of national systems remain sensitive even where the finding does not.

👮 Law enforcement

Investigators use environmental intelligence in pollution, waste crime, illegal extraction, wildlife and land use cases. Satellite and aerial imagery evidences when a site changed, how far a discharge spread and how long an activity ran, which is often the only continuous record available. Evidential use requires documented provenance: the sensor, acquisition date and time, processing level, coordinate reference system and any transformation applied, so another analyst can reproduce the product. Ground truth and sampling under a documented protocol are normally still required, since imagery establishes extent and timing while chemistry establishes substance and harm. Expert evidence is usually needed to put remote sensing analysis before a court.

🔍 Private investigation and corporate security

Corporate practitioners use environmental intelligence for site risk assessment, business continuity, insurance and transaction diligence. Flood, subsidence, wildfire, seismic and contamination exposure at a specific site is assessable from public hazard datasets and imagery without ever visiting, which makes it a standard input to property and supply chain decisions. Against third party sites, remote observation of publicly available imagery is lawful; what a private actor may not do is trespass, fly drones outside the applicable aviation and privacy rules, or conduct surveillance of individuals. Findings feed valuation, contractual environmental warranties and remediation cost estimates.

📰 Journalism and OSINT media

Journalists use satellite imagery to evidence environmental damage, illegal deforestation, mining, industrial discharge and disaster impact, with the advantage that much source imagery is free and the analysis can be shown to readers. Verification requires stating the sensor, the acquisition dates and the processing applied, and having the analysis reviewed by an independent remote sensing specialist. Avoid the common errors of comparing images taken in different seasons or at different resolutions and calling the difference change. Corroborate with ground reporting where possible, and consider whether publishing precise coordinates endangers communities or activists at the site.

🌍 NGO, humanitarian and human rights

Humanitarian and human rights organisations use environmental intelligence for disaster response, damage assessment, land rights documentation and evidence of environmental harm. Imagery-based damage assessment supports needs estimation within days of an event, and time series document destruction of villages, water infrastructure and agricultural land for accountability processes. Do-no-harm is central: publishing precise locations of displaced populations, informal settlements or activist-monitored sites can expose people to targeting, so coordinates are frequently generalised. Documentation is prepared to accountability standards for use by courts and United Nations mechanisms, with full provenance so it survives challenge.

🎓 University and research

Researchers use Earth observation as primary data for land cover change, hydrology, air quality, disaster impact and climate research. Methodology must document the sensor, the atmospheric and geometric corrections applied, the classification approach, the training data and the accuracy assessment, since remote sensing results are highly sensitive to processing choices. Reproducibility requires publishing the processing chain and the scene identifiers rather than only the derived maps. Ethics approval applies where analysis concerns identifiable communities or informal settlements, and there are real harms from publishing high-resolution locations of vulnerable populations. Cite the data provider, the collection and the processing level explicitly.

Playbook: working Environmental Intelligence end to end

A repeatable sequence, from the moment the requirement lands to the moment a product is delivered and the case is closed out. Each phase states what you are trying to establish, not merely what to click — the point is a defensible chain of reasoning, not a checklist.

Phase 1 — Define the environmental question and the area

Establish exactly what is being assessed, over what geographic extent and over what period. Distinguish state questions, such as what the flood hazard is at this site, from change questions, such as what happened here between two dates, because they need different data and different methods. Fix the coordinate reference system and the area of interest boundary at the start. A good output is a written task with a geometry, a date range and a decision it supports. Stop when the question can be answered by a measurement rather than by a description of the landscape.

Phase 2 — Select sensors for the problem

Choose observation types by physics rather than by availability. Optical imagery gives interpretable detail but fails under cloud and at night; synthetic aperture radar penetrates cloud and works at night and is the only reliable choice in persistently cloudy regions and for flood mapping; thermal reveals heat signatures from industrial activity and fire; multispectral supports vegetation, water quality and burn severity indices. Note revisit interval and resolution against the change rate you need to detect. A good output is a sensor plan justified against the question. Stop when the plan covers the period without gaps that could hide the event.

Phase 3 — Assemble the imagery time series

Retrieve a consistent stack of scenes covering the period, preferring the same sensor, similar acquisition geometry and comparable seasons, because seasonal and illumination differences are the leading cause of false change. Record scene identifiers, acquisition timestamps, processing level and cloud cover for every image. Fill gaps with an alternative sensor only where the comparison remains valid. A good output is an archived, documented scene stack with a manifest. Stop when the series brackets the event of interest with adequate temporal density.

Phase 4 — Preprocess consistently

Apply geometric and atmospheric correction consistently across the stack, co-register scenes precisely, and mask clouds and shadow. Record every processing step and parameter, because processing choices materially change results and an undocumented chain cannot be reproduced or defended. For radar, apply the appropriate speckle filtering and terrain correction. A good output is an analysis-ready stack with a written processing log. Stop when pixels align across dates well enough that co-registration error is smaller than the change you intend to measure.

Phase 5 — Establish the environmental baseline

Characterise the normal state of the area before assessing deviation: land cover, hydrology and drainage, seasonal vegetation cycle, typical water extent, existing infrastructure and known industrial sites. Bring in ancillary data such as terrain models, soil and geology, flood and seismic hazard mapping, and protected area boundaries. Without a baseline, any observed condition looks like an anomaly. A good output is a baseline description with the seasonal range quantified. Stop when you can state what the site normally looks like at the time of year in question.

Phase 6 — Detect and quantify change

Run the change detection appropriate to the question: spectral indices for vegetation, water and burn severity; radar backscatter differencing or coherence change for structural damage and flooding; thermal anomalies for industrial and fire activity. Quantify the change in physical units and area rather than describing it, and produce an uncertainty estimate. A good output is a quantified change product with a stated method and confidence. Stop when the measured change exceeds the demonstrated noise level of the method by a margin you can defend.

Phase 7 — Rule out the benign explanation

For every apparent change, test the alternatives before concluding. Seasonal phenology, harvest, illumination and view angle differences, sensor differences, atmospheric effects, reservoir management and normal flood cycles all produce convincing false positives. Check the same location in prior years at the same season to establish whether the observed pattern is recurrent. A good output is, for each finding, the alternative explanations considered and the evidence discounting them. Stop when the finding survives seasonal and sensor-artefact challenge or is withdrawn.

Phase 8 — Corroborate with ground and ancillary evidence

Test the remote finding against independent evidence: ground photography with verifiable location, official monitoring station data for air and water quality, permits and regulatory filings, local reporting, and where lawful and safe, direct sampling under a documented protocol. Imagery establishes extent and timing; it rarely establishes substance, cause or responsibility. A good output is a corroboration record linking the remote observation to ground evidence with dates. Stop when the material claims are each supported by at least one non-imagery source or the limitation is stated.

Phase 9 — Attribute cause carefully

Separate what happened from who caused it. Imagery can show a discharge plume, a clearing or a new access road, and can establish timing that narrows responsibility, but attribution normally requires corporate, permit, ownership or operational evidence. Combine land title and concession records, corporate registry data on the operator, permit and enforcement history, and vessel or vehicle movement where relevant. A good output is a causal assessment with the evidence chain set out and the inference explicit. Stop when responsibility is evidenced or the assessment clearly states that only the event, not the actor, is established.

Phase 10 — Produce a defensible geospatial product

Deliver maps and figures that carry their own provenance: sensor, acquisition dates, processing level, coordinate reference system, scale, and a clear legend distinguishing observed from interpreted features. Include the uncertainty and the areas not assessed. For accountability or evidential use, package the source scene identifiers and the processing chain so an independent analyst can reproduce the result. A good output is a product that can be handed to an opposing expert without embarrassment. Stop when every element on the map can be traced to its source.

Phase 11 — Set monitoring and revisit

Where the situation is ongoing, establish automated monitoring on the area with defined change thresholds and alerting, using free medium-resolution imagery for routine watch and tasking higher resolution only when triggered. This is far cheaper than periodic manual review and detects change closer to when it happens. Record detections and their dispositions. A good output is a monitoring configuration with measured detection latency and false positive rate. Stop tuning when detections are actioned rather than filtered.

Phase 12 — Handle harm and sensitivity before publication

Assess who is put at risk by publication. Precise coordinates of informal settlements, displaced populations, activist-monitored sites, protected species locations and unexploded ordnance can all cause direct harm. Consider generalising locations, delaying publication or sharing only with responders. Where the work supports accountability, preserve the full-precision material securely for legal processes while publishing at a coarser resolution. A good output is a documented harm assessment attached to the product. Stop and re-scope if publication cannot be made safe for the people at the location.

The platform ships this as a step-checked workflow in playbooks.php, so progress is recorded against a case rather than held in someone’s head.

Source register: what to collect from, and how

Sources are listed with their access model so you can plan around cost and licensing before you build a dependency on them. Open means no account required; registration means a free account or API key; licensed means paid or institutional access. Always confirm current terms — licensing changes, and a source that was free for research may not be free for commercial or evidential use.

Source	Access	What it gives you	How it is used here
Copernicus	Registration	European Earth observation programme providing free optical and radar imagery from the Sentinel satellites plus derived environmental services.	Primary free source of consistent optical and radar time series for change detection and flood mapping.
Copernicus Data Space Ecosystem	Registration	Access platform for Sentinel data archives with processing tools, browsing and programmatic retrieval.	Retrieval and processing of Sentinel scene stacks with recorded identifiers for reproducible analysis.
NASA Earthdata	Registration	Access point for NASA Earth science data including land, atmosphere, fire, and hydrology products across many missions.	Fire detection, land surface and atmospheric products complementing European imagery for multi-sensor analysis.
USGS	Open	United States geological survey providing Landsat archives, terrain data, earthquake catalogues and hydrological monitoring.	Long-run Landsat time series for decadal change analysis and authoritative seismic and terrain baselines.
NOAA	Open	United States agency publishing atmospheric, oceanic, coastal and climatological observation and modelling data.	Environmental baseline data for coastal, hydrological and atmospheric conditions affecting a site or event.
European Space Agency	Open	Mission documentation, data access and technical specifications for European Earth observation satellites and instruments.	Authoritative sensor characteristics needed to justify sensor selection and interpret processing artefacts.
Copernicus Climate Data Store	Registration	Reanalysis, seasonal forecast and climate projection datasets including long-run atmospheric and land surface variables.	Supplies the climatological baseline that distinguishes an anomalous condition from normal seasonal variation.
UN Environment Programme	Open	United Nations body publishing environmental assessments, conflict and environment reporting and global environmental data.	Contextual assessments and standards for environmental damage documentation in conflict and disaster settings.
UNOSAT	Open	United Nations satellite analysis service producing rapid mapping and damage assessment products for humanitarian response.	Reference damage assessment products and methodology for humanitarian and accountability applications.
European Environment Agency	Open	European datasets on land cover, air and water quality, industrial emissions and protected areas.	Regulatory monitoring data and protected area boundaries for corroborating remotely observed environmental change.
Global Forest Watch	Open	Near real-time forest change alerts, tree cover loss data and concession boundary layers derived from satellite monitoring.	Detection and quantification of deforestation with concession overlays supporting attribution to an operator.
OpenStreetMap	Open	Collaboratively maintained global geographic database of roads, buildings, land use and infrastructure features.	Base mapping and infrastructure context for interpreting imagery, particularly where official mapping is absent.
OGC	Open	Standards body defining interoperable geospatial data formats, web services and metadata conventions.	Governs the formats and metadata that make geospatial products interoperable and independently reproducible.
Berkeley Protocol via OHCHR	Open	United Nations methodological standard for digital open source investigation including imagery verification and preservation.	Provides the verification and provenance standard for imagery used in accountability and legal processes.

Prefer sources that publish a methodology and a revision history. A dataset that changes silently is a liability in any product that has to survive challenge.

Tooling

Tools commonly used against Environmental Intelligence. None of these replace judgement, and each carries its own failure modes — know what a tool infers versus what it observes.

QGIS — Open source geographic information system for analysis, mapping and product preparation. Limitation: large raster time series processing is slow without careful workflow design.
SNAP toolbox — Processes Sentinel optical and radar data including terrain correction and interferometric workflows. Limitation: steep learning curve and heavy resource requirements.
Google Earth Engine — Cloud processing over large public imagery archives without local storage. Limitation: reproducibility depends on recording asset versions, and terms restrict some uses.
Python geospatial stack with rasterio and GDAL — Scripted, reproducible raster processing and index computation. Limitation: correctness depends on explicit handling of projections and nodata values.
Sentinel Hub browsing and processing services — Rapid visual comparison and index rendering across dates for triage. Limitation: quick-look rendering hides processing choices that matter for measurement.
Radar coherence change detection workflows — Detect structural damage and change under cloud and at night. Limitation: interpretation requires expertise and is sensitive to baseline and terrain.
Terrain and hydrological modelling tools — Derive slope, flow accumulation and inundation extent from elevation models. Limitation: output quality is bounded entirely by elevation model resolution and currency.
Commercial very high resolution tasking services — Acquire targeted imagery at sub-metre resolution on request. Limitation: expensive, weather dependent, and licensing restricts onward publication.
Geolocation verification tools — Confirm the location of ground photographs against imagery and terrain for corroboration. Limitation: labour intensive and dependent on distinctive visible features.

AI skills and automation in detail

These are deterministic jobs with defined inputs and outputs, not open-ended prompting. Each is idempotent and cursor-based: interrupt one and it resumes where it stopped rather than duplicating work or losing progress.

Score Country Risk — Recomputes country risk from the weighted inputs and snapshots the result so movement over time is measurable.
Sync Intel Domains — Refreshes the reference and country-level intelligence datasets from their authorities.
Resolve Everything — Batch-resolves ASN, country, org and netblock for every IP from local reference datasets — no API calls, so it runs at millions of rows and works offline.
Summarise (Copilot) — Produces a narrative summary beside the underlying records. It explains; it never creates indicators or assigns attribution.
Generate Report — Assembles a sourced product from the current case or query, with provenance attached to each element.

A note on the boundary: the only skill that involves a language model is Summarise (Copilot), and it writes prose about records that already exist. Nothing else on this list involves generation of any kind. No indicator, relationship or attribution in the platform originates from a model. See the full skill list.

Tradecraft notes

The distinctions that separate a competent analyst from a fast one:

Season matters more than resolution. The most common false finding in this discipline is a comparison between images taken at different times of year, where phenology and illumination produce apparent change that has nothing to do with the event.
Radar is the answer to cloud and night, not a fallback. In persistently cloudy regions an optical-only approach systematically misses events, and flood extent in particular is far better measured from backscatter than from a clear-sky optical scene that never arrives.
Check prior years at the same date before calling anything anomalous. Recurrent seasonal flooding, annual burning and harvest cycles look exactly like events, and the archive is free, so there is no excuse for skipping the check.
Imagery establishes extent and timing; it rarely establishes substance or responsibility. A plume is visible, its chemistry is not, and the step from observed discharge to a named operator requires permit, ownership and operational evidence.
Record the processing chain as part of the finding. Atmospheric correction, co-registration and index formulation choices change results materially, and an undocumented chain cannot be reproduced, which is fatal in an evidential or accountability setting.
Quantify with an uncertainty estimate rather than describing change. An area figure with a stated confidence interval is usable in a legal or policy process; a before and after image pair with an arrow on it is not.
Use free medium-resolution imagery for continuous monitoring and task high resolution only on a trigger. Continuous coarse observation with alerting detects events far more reliably than expensive periodic detailed review.
Assess publication harm before releasing coordinates. Precise locations of displaced people, informal settlements, activists and protected species have caused real harm, and generalising the location usually costs the analysis nothing.

Measuring whether it is working

Capability claims should be falsifiable. These are the measures that show whether work on Environmental Intelligence is producing anything, and they are worth baselining before you change process or tooling.

Median time from an environmental event occurring to a validated assessment being delivered to the responder or decision owner.
Proportion of change detections that survived seasonal and sensor-artefact challenge, measured against those withdrawn at review.
Share of products carrying complete provenance, meaning sensor, acquisition dates, processing level and coordinate reference system, without later correction.
Accuracy of remotely derived extent or damage estimates against ground truth or independent assessment where these later become available.
Coverage of monitored sites by an observation cadence adequate to detect the change rate of interest, with gaps explicitly recorded.
Number of findings where responsibility was asserted without non-imagery corroboration, which should be zero.
Proportion of published products that completed a documented publication harm assessment before release.

Beware of measuring volume alone. Indicator counts and report counts rise easily and say little; time-to-attribution, proportion of findings that survive review, and how often a product changed a decision say a great deal.

Common pitfalls

Cloud, haze, shadow and seasonal vegetation cycles produce apparent differences that are artefacts rather than real events
Interpreting imagery without a baseline, so normal industrial variation gets reported as a significant incident
Ignoring acquisition timestamps and time zones, misdating an observed change by a day or more in the reporting
Confusing spatial resolution with certainty, since small objects at ten-metre resolution are inference and not identification
Coordinate reference and co-registration errors that shift features and manufacture false change along scene edges
Attributing cause from appearance alone, when excavation, subsidence and demolition can look very similar from above

Legal and ethical considerations

Open satellite imagery is licensed for reuse but terms vary, and commercial imagery usually restricts redistribution, so check before publishing. Imagery of private property is generally lawful to analyse, but sustained monitoring of individuals or dwellings raises privacy and surveillance concerns, and some jurisdictions restrict imaging of defence sites. Environmental monitoring data is often official record and admissible, though interpretation must be methodologically documented to survive challenge. For environmental-crime findings, preserve original scenes and processing chains, since conclusions without reproducible method carry defamation risk.

Data integrity: no fabrication, no drift, no hallucination

Intelligence that cannot be traced back to a source is not intelligence, it is assertion. Everything in this entry — and everything in the platform behind it — is built on a small number of non-negotiable rules.

Provenance on every record

Every indicator carries the source that supplied it, a first-seen and last-seen timestamp, and a sighting count. Where several feeds report the same artifact, each contribution is recorded separately rather than collapsed, so you can see whether a finding rests on one source or twelve. Source attribution travels with the data into every export, so a recipient can audit a claim without asking you for the working.

Nothing is invented to fill a gap

If the platform has no data for Environmental Intelligence, it says so. Empty is displayed as empty — never padded with plausible-looking placeholder values, sample records or illustrative examples that a reader might mistake for observations. A dashboard with no rows is a true statement about collection coverage, and it is treated as a gap to close, not a blemish to hide.

Scoring is deterministic and reproducible

Threat scores, reputation grades and risk tiers are computed from stated inputs with fixed weights, not estimated. The same inputs always produce the same output, and the formula is visible rather than a black box. Aggregates are cached with an explicit time-to-live so a figure on screen is never silently stale — and when a heavy query exceeds its time budget the platform serves the last known-good value and labels it, rather than inventing a fresh number or hanging.

Where AI is used, and where it is not

Language models summarise and explain. They do not create indicators, assign attribution or manufacture relationships. No IP address, wallet, hash or identity in the platform originates from a model — every one is ingested from a named feed, resolved from a reference dataset, or entered by an analyst with a source recorded. Copilot output is presented as narrative alongside the underlying records, never in place of them, so a reader can always check the summary against the evidence.

Guarding against drift

Enrichment is additive and timestamped rather than overwriting. Reference data — sanctions lists, allocations, taxonomies — is re-synchronised from the authority on a schedule instead of being edited in place, so local copies cannot quietly diverge from the source of truth. Attribution is recorded with a confidence level and the reporting it rests on, and inferred relationships are labelled as inferred. When a source retracts or corrects, the correction propagates rather than leaving a stale assertion behind.

What this means for you

You can put a finding from this platform in front of a regulator, a court, a board or a partner agency and show where each element came from. That is the standard the tooling is built to — because in this work, being confidently wrong is more damaging than being usefully uncertain.

By the numbers

The taxonomy this entry belongs to is not a marketing list — it is the actual structure of the platform: 52 mission domains, 52 intelligence disciplines and 65 data points, each with a live dashboard behind it. Supporting that: 18 indicator types, 14 playbooks, 16 AI skills, 18 export formats and a 30-step automated pipeline.

This particular entry connects directly to 9 data points, 8 mission domains, 1 closely related entries — every one of them a tag you can follow, and a dashboard you can open.

Questions analysts actually ask

Optical or radar for this problem?

Decide on physics and on the observation window you need. Optical is interpretable and better for identifying what something is, but it fails under cloud and at night, which in tropical and monsoon regions can mean months without a usable scene. Radar works regardless of cloud and darkness, is superior for flood extent and for detecting structural change, and coherence analysis reveals damage that optical comparison misses. In practice the strongest workflows use both: radar for reliable detection and timing, optical for interpretation and presentation. If you must choose one for a time-critical event in a cloudy region, choose radar.

How do I avoid false change from seasonality?

Compare like with like and check the archive. Use scenes from the same sensor, similar acquisition geometry and the same time of year, and before concluding anything, look at the same location on the same dates in three or four previous years. Recurrent patterns of flooding, burning, harvest and vegetation flush are the leading source of false findings, and the historical archive answers the question at no cost. Where a same-season comparison is impossible, use an index that is less sensitive to illumination and state the limitation explicitly rather than reporting the change as established.

Is satellite imagery admissible as evidence?

Generally yes, subject to authentication and expert interpretation, and it is used routinely in environmental prosecutions and international accountability processes. What makes it usable is provenance and reproducibility: the scene identifiers, acquisition timestamps, processing level, every processing step applied and the coordinate reference system, so an independent expert can reproduce the product. Expect challenge on the processing choices and on the interpretation rather than on the imagery itself. Pair it with ground evidence, because imagery establishes extent and timing while sampling and documentation establish substance, harm and responsibility.

Can I use free imagery for serious analysis?

For most environmental questions, yes. Free medium-resolution optical and radar data with frequent revisit is better suited to change detection than infrequent very high resolution imagery, because detecting when something changed usually matters more than seeing fine detail. The consistent, calibrated multi-year archives are also what make baseline and seasonal comparison possible. Commercial very high resolution has a specific role: confirming the nature of a detected change, counting discrete objects and supporting publication. The efficient pattern is continuous free monitoring with tasked high resolution only on a trigger.

How do I attribute environmental damage to a company?

Build the chain rather than asserting it. Establish the event and its timing from imagery, then locate it against concession boundaries, land title, mining or discharge permits and facility ownership. Identify the operator through corporate registry research, and check permit conditions and enforcement history. Look for corroborating operational evidence such as vehicle or vessel movement, employment records or company reporting. Where the chain is incomplete, state that the event is established and the responsibility is not, which is a legitimate and useful finding. Never let a spatial coincidence stand in for evidence of causation.

What should I do about publishing precise locations?

Assess the harm first and document the assessment. Precise coordinates for informal settlements, displaced populations, sites monitored by local activists, protected species habitat and unexploded ordnance have led to real harm when published. Options include generalising to a grid cell or an administrative area, delaying publication until people have moved or been warned, and sharing full precision only with responders or legal processes while publishing at coarser resolution. Consult the people at risk or the organisations working with them where that is possible, since they usually know the exposure better than the analyst does.

How often should ongoing sites be monitored?

Match the cadence to the rate of the change you need to catch, not to a reporting calendar. Rapid events such as flooding, fire or a discharge need observation within days and are best handled with automated alerting on free imagery. Slow processes such as deforestation, subsidence or coastal erosion can be assessed monthly or seasonally. Set explicit change thresholds so the system alerts rather than requiring review, and record detection latency, because a monitoring capability that finds an event three weeks late has usually missed the decision it was meant to support.

Standards, frameworks and further reading

Work that references a recognised framework is easier to defend, easier to hand over, and easier for a partner to consume:

OGC standards for geospatial data formats, web services and metadata, which govern interoperability and reproducibility of geospatial products.
ISO 19115 geographic metadata, which governs the provenance information that must accompany a defensible geospatial product.
The Berkeley Protocol on Digital Open Source Investigations, which governs verification, provenance and preservation of imagery used for accountability.
The INSPIRE Directive, which governs spatial data infrastructure and public access to environmental geospatial information in the European Union.
The Aarhus Convention, which governs public access to environmental information and participation in environmental decision making.
The Espoo Convention and environmental impact assessment regimes, which govern the assessment obligations that generate corroborating official documentation.
The Rome Statute and international humanitarian law provisions protecting the natural environment, which govern documentation of environmental harm in conflict.
ISO 14001 environmental management systems, which govern the corporate monitoring records that corroborate or contradict remote observations.

References

Primary sources and authoritative references for this entry. Publishers revise and retire material, so treat the retrieval date as part of the citation and re-check before relying on any of it in a formal product.

Copernicus Earth observation programme — European Union and European Space Agency. Free Sentinel optical and radar imagery and derived environmental services
Copernicus Data Space Ecosystem — European Space Agency. Access and processing platform for Sentinel archives
Earthdata — NASA. Access point for Earth science data across land, fire, atmosphere and hydrology missions
Landsat archive and geospatial data — United States Geological Survey. Long-run calibrated imagery archive and terrain and seismic baselines
Berkeley Protocol on Digital Open Source Investigations — UN Office of the High Commissioner for Human Rights. Standard for verification and preservation of open source imagery evidence
Rapid mapping and damage assessment — UNITAR UNOSAT. Satellite-derived humanitarian damage assessment products and methodology
Forest change monitoring — Global Forest Watch. Near real-time deforestation alerts with concession and ownership overlays
European environmental datasets — European Environment Agency. Land cover, emissions, water quality and protected area data
Geospatial interoperability standards — Open Geospatial Consortium. Formats, services and metadata conventions for geospatial products
Environmental assessments and conflict reporting — UN Environment Programme. Assessments of environmental damage including in conflict settings

Link integrity: every reference above was verified with a live request when this page was generated. Where a publisher had moved or withdrawn a document, the link was repointed at a preserved copy in the Internet Archive and marked as archived. Anything with no reachable copy anywhere had its link removed rather than left to rot — the source is still credited, it simply cannot be linked.

Put it into practice

The Quantus Intel threat intelligence platform operationalises this entry: runs area-of-interest change alerting with multi-sensor corroboration and asset exposure overlays. Explore the platform, or browse the rest of the library by following any tag above.