Problems
Real geospatial problems, graded automatically. Choose a track, a level and what you want to hand in.
- Not started, Build an earthquake contact reconnaissance queueProjectDecision support3 stepsSpatial AnalysisadvancedDifficulty: advanced550 XP~95 min12 checksSpatial AnalysisadvancedDifficulty: advanced
Screen strong shallow events, quantify airfield and settlement proximity, and hand over a traceable contact map.
Worked in 3 steps, each checked before the next one opens.
- Select the event queue · SQL
- Measure contact gaps · Answers
- Hand over the access map · Python
Datasets
- Global M5.5+ earthquakes, Jan–Mar 2025 · Point · 86 features · EPSG:4326
- World airports · Point · 893 features · EPSG:4326
- Populated places · Point · 1,251 features · EPSG:4326
What you’ll do
- Select a reproducible event queue in SQL
- Measure two independent global proximity indicators
- Deliver an auditable access map with an explicit contact-gap distinction
projectUSGSnearest neighbourlogisticsglobalAlso trains Python, Data Management, CartographyOpen project - Not started, Plan a cycle redistribution shiftProjectDecision support3 stepsSpatial AnalysisadvancedDifficulty: advanced600 XP~100 min11 checksSpatial AnalysisadvancedDifficulty: advanced
Classify the dock snapshot, propose bounded bike moves, and size the resulting shift with its unserved stations visible.
Worked in 3 steps, each checked before the next one opens.
- Classify the snapshot · SQL
- Map feasible transfers · GeoJSON
- Size the preliminary shift · Answers
Dataset
- Santander Cycles docking stations (live snapshot) · Point · 799 features · EPSG:4326
What you’ll do
- Classify full and empty active stations in SQL
- Build a bounded nearest-source transfer map
- Size a shift and report unserved empties from the same rules
nearest neighbouroperationscapacityCRStransportLondonAlso trains Data Management, GIS ArchitectureOpen project - Not started, Urban share of each state, in SQLSpatial analysisSQLPostGIS / SQLadvancedDifficulty: advanced
ST_Intersection for the pieces and ST_Area on geography for the metres — the overlay-and-measure pattern inside the database.
You hand in a spatial SQL query.
Datasets
- United States states · Polygon · 51 features · EPSG:4326
- Urban areas · Polygon · 2,143 features · EPSG:4326
What you’ll do
- Overlay polygons with ST_Intersection
- Measure the pieces on geography rather than in degrees
- Aggregate per state, keeping the states with nothing
ST_IntersectiongeographyoverlayGROUP BYland useAlso trains Spatial AnalysisOpen problem - Not started, Which neighborhoods merit a service follow-up?Decision supportSQLPostGIS / SQLadvancedDifficulty: advanced
Join geocoded service requests to neighborhood polygons and map a review share only where the sample supports it.
You hand in a spatial SQL query.
Datasets
- 2020 Neighborhood Tabulation Areas · MultiPolygon · 262 features · EPSG:4326
- NYC 311 sewer requests, 1–7 June 2025 · Point · 408 features · EPSG:4326
What you’ll do
- Join incident locations to neighborhoods with a boundary-inclusive predicate
- Compute elapsed-time review share with a clear denominator
- Suppress very small denominator areas before mapping percentages
NYC 311PostGISspatial joinservice operationsgraduated mapAlso trains Spatial Analysis, Cartography, Data ManagementOpen problem