Skip to content
Kharita Challenges

Problems

Real geospatial problems, graded automatically. Choose a track, a level and what you want to hand in.

5 of 59 problems

Pick one for me
Track
Spatial Analysis2 problemsPostGIS / SQL5 problemsPython0 problemsRemote Sensing0 problemsCartography2 problemsWeb GIS0 problemsData Management2 problemsGIS Architecture0 problems
Level
Beginner3 problemsIntermediate5 problemsAdvanced6 problemsExpert0 problems
Hand in
SQL5 problemsPython5 problemsGeoJSON4 problemsAnswers9 problemsSchema0 problemsDecisions0 problemsDataset file0 problems
Category
Data preparation1 problemData quality0 problemsSpatial analysis1 problemRaster analysis0 problemsCartography0 problemsDecision support3 problemsGeospatial systems0 problemsWeb delivery0 problems
Sign in to track progress
IntermediateSQLClear all
  1. Not started, Protect the bus stop key during the loadData preparationSQL

    Recover zero-padded stop identifiers before a transport timetable join.

    Data ManagementintermediateDifficulty: intermediate210 XP~40 min7 checks

    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 / SQL
    Open problem
  2. Not started, Redirect the rider at an empty dockDecision supportSQL

    For every station with no bikes, the nearest station that has one, and the walk in metres — with the KNN operator so it stays fast at 799 stations or 79,000.

    PostGIS / SQLintermediateDifficulty: intermediate250 XP~40 min5 checks

    You hand in a spatial SQL query.

    Dataset

    • Santander Cycles docking stations (live snapshot) · Point · 799 features · EPSG:4326

    What you’ll do

    • Filter to stations with no bikes
    • Find each one's nearest stocked station with an index-assisted nearest-neighbour search
    • Report the distance in metres
    KNNLATERALGiSTgeographyperformancetransport
    Open problem
  3. Not started, Where should a waterway survey start?Decision supportSQL

    Screen large global urban footprints for mapped river contact while keeping scale limitations explicit.

    Spatial AnalysisintermediateDifficulty: intermediate320 XP~50 min9 checks

    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 Management
    Open problem
  4. Not started, Which airfields should the response desk check?Decision supportSQL

    Use a metre-based spatial join to identify civil airfields near strong, shallow earthquake epicentres, with the facilities drawn on the map.

    PostGIS / SQLintermediateDifficulty: intermediate260 XP~45 min6 checks

    You hand in a spatial SQL query.

    Datasets

    • Global M5.5+ earthquakes, Jan–Mar 2025 · Point · 86 features · EPSG:4326
    • World airports · Point · 893 features · EPSG:4326

    What you’ll do

    • Filter events by magnitude and depth
    • Join the selected events to civil airfields within 250 km in metres
    • Return traceable, mapped airport points and measured distances
    PostGISearthquake responseairportsgeographyglobalAlso trains Spatial Analysis, Cartography
    Open problem
  5. Not started, Which ports are within 25 km of a capital?Spatial analysisSQL

    ST_DWithin on geography: a proximity join in true metres that the index can still answer.

    PostGIS / SQLintermediateDifficulty: intermediate220 XP~35 min5 checks

    You hand in a spatial SQL query.

    Datasets

    • Populated places · Point · 1,251 features · EPSG:4326
    • Ports · Point · 1,081 features · EPSG:4326

    What you’ll do

    • Write a proximity join with ST_DWithin
    • Measure in metres on SRID 4326 data by casting to geography
    • Keep the predicate in a form the GiST index can serve
    ST_DWithingeographyGiSTproximityglobal
    Open problem