change-detection

Solid

Invoke whenever the primary question is what, where, or how much changed between times, including two-scene comparisons, deforestation, urban growth, disaster damage, and parcel-change audits. Covers bi-temporal differencing, post-classification comparison, adjusted area, and time-series trend/break analysis (BFAST/LandTrendr/CCDC-style). Invoke even when seasons, sensors, or processing levels are not comparable; diagnosing an invalid comparison is part of change analysis. Use remote-sensing-analysis for single-date preparation and add google-earth-engine only when GEE executes the work.

AI & Automation 3 stars 0 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 79/100

Stars 20%
20
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Change Detection & Spatio-temporal Analysis Purpose: separate real surface change from the four great impostors — misregistration, radiometric drift, phenology, and classification error. Every method below exists to control one of them; skipping the controls produces confident maps of nothing. ## Preconditions (where change detection is won or lost) 1. **Co-registration**: sub-pixel alignment between dates (AROSICS or manual tie-points). Half a pixel of shift creates edge-shaped phantom change everywhere. Verify: flicker-compare crisp features. 2. **Radiometric consistency**: same processing level (surface reflectance), same sensor if possible; if mixing sensors, harmonize (e.g., Landsat↔Sentinel-2 HLS) or use relative normalization (PIFs). 3. **Same season / phenological stage** for bi-temporal work — a May vs September pair "detects" summer. If season can't be matched, use composites or time-series methods instead. 4. **Cloud/shadow masks intersected across dates**; analyze only mutually valid pixels and report that coverage %. ## Method selection | Situation | Method | |---|---| | Two dates, continuous "how much" | Index differencing (ΔNDVI, ΔNBR...) with statistical thresholding | | Two dates, categorical "from-what-to-what" | Post-classification comparison (only with strong classifiers) | | Two dates, multivariate robust | Change vector analysis (CVA); MAD/iMAD for sensor-robust detection | | Dense stack, gradual + abrupt | Trend + break analy...

Details

Author
muend
Repository
muend/geoai-skills
Created
1 weeks ago
Last Updated
yesterday
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

remote-sensing-analysis

Always invoke for classical analysis, classification, validation, or comparability of satellite, aerial, or drone imagery. This skill owns sensor/product/processing-level harmonization, including multi-date inputs; add change-detection only after comparable observations exist. Covers spectral indices, masking, compositing, SAR, land cover, and accuracy assessment. Route neural methods to geo-deep-learning and planetary server-side execution to google-earth-engine.

3 Updated yesterday
muend
Data & Documents Listed

change-impact-analysis

Perform deployment-phase Change Impact Analysis for any repository. Given changed files (or auto-detected via git), builds a directed dependency graph, reverse-BFS traverses it to find every directly and transitively affected module, validates API contracts (OpenAPI/GraphQL/Protobuf) for breaking changes, maps files to CODEOWNERS, and computes a deterministic 0-100 deployment risk score (LOW/MEDIUM/ HIGH/CRITICAL). Produces an Impact Report, machine-readable JSON, and a Deployment Checklist. Trigger on: change impact analysis, analyse/analyze this PR, what is affected by this change, deployment risk, blast radius, what tests are needed, who owns this code, is it safe to deploy, breaking changes, impacted APIs, regression areas, or a list of changed files with "what will break". No API key required.

1 Updated 1 weeks ago
sarveshtalele
AI & Automation Listed

tracking-citation-diffs

Use when tracking how AI-engine citations of your site change over time and tying each change to the commit that caused it — "did my last PR win or lose citations?", "why did ChatGPT stop citing us?", "daily GEO citation diff", "citation regression", "which commit moved our AI visibility". Runs the GEO Diff Bot — diffs two geo-check snapshots and correlates each gained/lost citation to the content commit(s) in the window, or flags it as an external (model/competitor/crawl) shift when nothing in your repo changed. Pairs with the geo-check MCP (geo_track) which produces the snapshots. Mature-phase monitoring, not one-shot audit.

0 Updated 4 days ago
benskamps