Problems
Real geospatial problems, graded automatically. Choose a track, a level and what you want to hand in.
- Not started, Why a cloud-optimised GeoTIFF is cheap to serveWeb deliveryAnswersGIS ArchitectureintermediateDifficulty: intermediate200 XP~30 min4 checksGIS ArchitectureintermediateDifficulty: intermediate
Read a COG's internal structure — tiles, overviews, bytes — and turn it into the numbers a tile server's capacity plan rests on.
You hand in your answers as values.
Datasets
- Greater London land cover 2021 (ESA WorldCover 10 m) · Raster · EPSG:4326
- Greater London, Sentinel-2 red and NIR, 11 July 2025 · Raster · EPSG:32630
What you’ll do
- Read a GeoTIFF's block size and overview structure
- Count internal tiles from dimensions and block size
- Relate the structure to what a tile request costs
COGGeoTIFFtile servercapacity planningrasterAlso trains Web GISOpen problem - Not started, Polling a live feed: what does it cost per day?Web deliveryAnswersGIS ArchitectureadvancedDifficulty: advanced280 XP~35 min3 checksGIS ArchitectureadvancedDifficulty: advanced
Size the transfer cost of a live layer from the file as served — uncompressed, gzipped, and per day at scale — before choosing between polling and push.
You hand in your answers as values.
Dataset
- Santander Cycles docking stations (live snapshot) · Point · 799 features · EPSG:4326
What you’ll do
- Measure a payload as served rather than as re-encoded
- Quantify what transport compression buys
- Extrapolate a polling design to a daily transfer figure
capacity planningpollinggzippayloadarchitectureAlso trains Web GISOpen problem