Problems
Real geospatial problems, graded automatically. Choose a track, a level and what you want to hand in.
- Not started, Protect the bus stop key during the loadData preparationSQLData ManagementintermediateDifficulty: intermediate210 XP~40 min7 checksData ManagementintermediateDifficulty: intermediate
Recover zero-padded stop identifiers before a transport timetable join.
You hand in a spatial SQL query.
Dataset
- Singapore bus stop code staging · Point · 31 features · EPSG:4326
What you’ll do
- Preserve identifier semantics through SQL casting.
- Resolve repeated source rows deterministically.
- Return a clean point layer for the timetable join.
data-preparationsingaporesqlAlso trains PostGIS / SQLOpen problem - Not started, Where should a waterway survey start?Decision supportSQLSpatial AnalysisintermediateDifficulty: intermediate320 XP~50 min9 checksSpatial AnalysisintermediateDifficulty: intermediate
Screen large global urban footprints for mapped river contact while keeping scale limitations explicit.
You hand in a spatial SQL query.
Datasets
- Urban areas · Polygon · 2,143 features · EPSG:4326
- Rivers and lake centrelines · LineString · 461 features · EPSG:4326
What you’ll do
- Apply a spatial join to real river and urban geometry
- Keep zero-contact footprints in the inventory
- Distinguish map-scale contact classes for survey planning
Natural Earthurban waterPostGISspatial screeningcategorical mapglobalAlso trains PostGIS / SQL, Cartography, Data ManagementOpen problem