agentleFS
muendmuend/geoai-skills/skills/geostatistics-interpolation/SKILL.md

geostatistics-interpolation

Skill39 starsChanged 4 months agoMITView on GitHub

Turn scattered point measurements into continuous surfaces with quantified uncertainty: variogram modeling, ordinary/universal/regression kriging, IDW, and spatially honest cross-validation. Use when unobserved values must be estimated from sparse samples such as stations, wells, or soundings. Trigger on "interpolate", "kriging", "variogram", or "IDW"; a named interpolation method is sufficient even when the requested surface is described informally as a heatmap. Do not use for point-density heatmaps, zonal aggregation, or raster resampling without value interpolation.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check anisotropy with directional variograms (0/45/90/135°).

    line 62
  2. Distinctive:

    Never interpolate meaningfully beyond the variogram range from the nearest sample.

    line 68
  3. Distinctive:

    Search neighborhood: 16-32 nearest points typical.

    line 87

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Geostatistics & Interpolation

Purpose: interpolation that reports what it doesn't know. The difference between a professional product and a pretty raster is the uncertainty surface and an honest cross-validation — both are non-optional here.

Method selection

SituationMethod
Dense, smooth phenomenon, quick lookIDW (report power parameter; test 1-3)
Physical phenomenon with spatial structure, need uncertaintyOrdinary kriging (default professional choice)
Clear trend (elevation gradient, coastal effect)Universal kriging or regression kriging on covariates
Strong covariates available (DEM, land cover, distances)Regression kriging / random-forest residual kriging
Categorical targetIndicator kriging
Honeycomb-free tessellation, no extrapolation wantedNatural neighbor

IDW is a reasonable baseline but has no error model and bullseyes around extremes; say so when delivering IDW-only products.

Exploratory phase (before any interpolation)

  • Map the points with values; look for duplicates at identical coordinates (average or offset them — kriging matrices go singular otherwise).
  • Histogram + skew: strongly skewed variables (rainfall, concentrations) usually want a log/normal-score transform; back-transform predictions properly (bias correction for lognormal kriging).
  • Trend check: regress value on x, y, and candidate covariates; visible trend → universal/regression kriging path.
  • Declustering if sampling is preferential (dense where values are high).

Variogram discipline

The variogram is a MODELING decision, not an auto-fit output:

import gstools as gs

bin_center, gamma = gs.vario_estimate((x, y), values, max_dist=dmax)  # dmax ≈ half extent
model = gs.Exponential(dim=2)
model.fit_variogram(bin_center, gamma, nugget=True)
print(model)   # report: nugget, sill, range — plus the fitted plot
  • Max lag ≈ half the domain diameter; ≥30 pairs per bin.
  • Check anisotropy with directional variograms (0/45/90/135°); geological and meteorological fields are often anisotropic — fit an anisotropic model rather than ignoring it.
  • Interpret and report the parameters in words: nugget (measurement error + micro-scale variance), range (correlation distance), sill. A nugget near the sill means the data barely support interpolation — say that honestly.
  • Never interpolate meaningfully beyond the variogram range from the nearest sample; mask or flag those cells.

Kriging execution

from pykrige.ok import OrdinaryKriging

ok = OrdinaryKriging(x, y, values, variogram_model="exponential",
                     variogram_parameters={"sill": s, "range": r, "nugget": n},
                     coordinates_type="euclidean")
z, ss = ok.execute("grid", gridx, gridy)   # ss = kriging VARIANCE — keep it!
  • Work in a projected CRS (kriging distances in degrees are wrong except with explicitly geographic-aware models).
  • Deliver TWO rasters: prediction AND kriging standard deviation (np.sqrt(ss)). The uncertainty map drives where to sample next and where not to trust the map.
  • Search neighborhood: 16-32 nearest points typical; document it.

Validation — leave-one-out and beyond

  • LOOCV for small n: report ME (bias ≈ 0?), RMSE, and standardized RMSE (should be ≈ 1 if kriging variances are honest).
  • For clustered samples, LOOCV flatters; also run spatial block CV (canonical recipe: ml-experiment-standards → references/spatial-cv-protocol.md) and report both.
  • Scatter plot observed vs predicted with 1:1 line; map the CV residuals — spatially clustered residuals mean missing trend/covariate.
  • Compare against the dumb baseline (global mean, IDW): kriging must earn its complexity.

Reporting template

## Surface: <variable>
- n = <>, extent, CRS, transform applied: <log/none>
- Variogram: <model>, nugget/sill/range = <...>, anisotropy: <...>
- Method: <OK/UK/RK + covariates>
- LOOCV: ME <>, RMSE <>, RMSE_std <>; block-CV RMSE <>
- Uncertainty: kriging SD raster delivered; area beyond reliable range masked

Pitfalls checklist

  • Auto-fitted variogram accepted without looking at the plot.
  • Kriging in EPSG:4326 over large extents.
  • Prediction raster delivered without its variance/SD companion.
  • Log-kriging back-transformed by naive exp() (bias!).
  • Extrapolation far beyond the data hull presented at equal confidence.
  • Duplicated station coordinates crashing or silently distorting the fit.

Execution contract

  • Workflow: inspect sampling and transform needs; model spatial dependence; fit candidate surfaces; validate against simple baselines; quantify uncertainty; mask unsupported extrapolation.
  • Decision rules: choose IDW or trend methods for transparent baselines, kriging when a defensible variogram exists, and regression kriging when covariates improve blocked validation.
  • Verification protocol: examine variogram diagnostics, LOOCV and spatial block-CV residuals, baseline uplift, uncertainty calibration, and behavior beyond the sample hull.
  • Failure modes: withhold a confident surface when sampling is too sparse, dependence is absent, duplicates dominate, distance units are invalid, or uncertainty is uncalibrated.
  • Deliverables: prediction surface, uncertainty surface, variogram and parameters, validation table, sampling-support mask, and method limitations.
  • Source freshness: consult the authoritative source registry before relying on package APIs or defaults and record the checked date.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.