geo-deep-learning

Solid

Invoke before recommending, training, or auditing a neural method for geospatial imagery, including vision transformers, U-Net/DeepLab/SegFormer, object detection, pixel classification, building/road extraction, and EO foundation-model fine-tuning. Also invoke for neural chip-split validity, IoU/accuracy claims, augmentation, imbalanced losses, spatial validation, or sliding-window inference. Use remote-sensing-analysis for non-neural methods and change-detection when temporal change is the deliverable.

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

# Geospatial Deep Learning Purpose: deep learning on Earth observation with the two failure modes that dominate this field designed out from the start: **spatial leakage** (inflated metrics from nearby train/test pixels) and **georeferencing loss** (predictions that no longer align with the map). ## Characterise the label set before naming an architecture Architecture advice given without knowing the label set is guesswork. Before recommending U-Net versus a foundation model versus a non-deep baseline, state or ask for: - **Label count and labelled area** — polygons alone say nothing; 40 polygons covering 2 ha and 40 covering 2 000 km² are different problems. - **Geographic spread** — are the labels clustered in one scene, one season and one sensor, or distributed across the deployment domain? Clustered labels cap what any model can generalise to, and they decide whether a geographically independent validation split is even constructible. - **Class balance and minority-class pixel fraction**, so loss and sampling choices are grounded rather than assumed. - **Deployment geography** — where predictions will be made, relative to where the labels are. Do not answer "fine-tune a large model or use a simpler approach" before these are known. When the user has not supplied them, ask and give the provisional recommendation *conditioned on* the answers ("if the 40 polygons sit in one scene, then …; if they span the region, then …"), never a single unconditional recomm...

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
AI & Automation Solid

google-earth-engine

Invoke when Earth Engine, GEE, ee., or geemap is named; when work needs its server-side catalog; or when choosing Earth Engine versus local xarray or desktop processing for a large area or long archive. Covers image collections, masking, compositing, reducers, zonal statistics, time series, classification, quota-aware batching, and exports. This is an execution platform skill; combine it with remote-sensing-analysis or change-detection when those skills own the scientific method.

3 Updated yesterday
muend
Data & Documents Solid

geo-data-engineering

Always invoke when geospatial data must be acquired, prepared, repaired, scaled, or moved through a repeatable pipeline. Covers open-data/OSM/STAC acquisition, spatial formats, CRS transforms, quality checks, and batch ETL architecture for growing or recurring joins. Invoke alongside PostGIS for database execution and alongside SWE standards when code is delivered. Do not trigger merely because another specialist reads analysis-ready data.

3 Updated yesterday
muend