Getting a map off your laptop and onto a URL a commissioner can open on their phone — ward boundaries, complaint locations, project status — without emailing a shapefile nobody can open. Built on Mapbox: a basemap designed in Studio, your own data drawn over it by Mapbox GL JS.
Needed across
What you will be able to answer
The commissioner wants ward-level complaint data on their phone, not a shapefile in an email, and there is no developer on the team. What do you build?
A single HTML page running Mapbox GL JS, pointed at a style you designed in Mapbox Studio with the labels and clutter turned down so the data reads. The ward boundaries go on as a GeoJSON source with a fill layer above it, coloured from a complaint-count property by a data-driven expression rather than by hand, and a click handler puts the ward's numbers in a popup. The complaint points cluster so a few hundred markers stay readable instead of collapsing into one blob. If the boundaries are too heavy to send down in one request over mobile data, they get uploaded to Mapbox as a tileset and served as vector tiles, which happens before the basemap gets any attention at all. Then the page goes onto free static hosting, with the access token restricted to that URL, so what gets shared is a link rather than a file.
One payment
₹99
The videos are free
Course outline
Concept 1
Concept 1 · Why the file on your laptop can't be the thing you send
Concept 2
After: why-web-maps
Spatial data cut into tiles across zoom levels, and why vector tiles are styled in the browser rather than baked into an image.
Video title and channel appear once unlocked.
Concept 3
After: vector-tiles-and-styles
A style started from a template in Studio, with layer visibility and labels turned down so a data layer has room to read.
Video title and channel appear once unlocked.
Concept 4
After: mapbox-studio-basemap
The library pulled in from a CDN, a container the map lives in, and the few lines of JavaScript that turn an empty file into a rendered map.
Video title and channel appear once unlocked.
Concept 5
After: first-mapbox-map
A GeoJSON added as a source, then a fill layer above it — the two-step that catches everyone coming from desktop GIS.
Video title and channel appear once unlocked.
Concept 6
After: mapbox-geojson-source
A property picked, its value range broken into steps, and every polygon coloured from its own number rather than by hand.
Video title and channel appear once unlocked.
Concept 7
After: mapbox-geojson-source
A click bound to one layer, and the properties of whatever feature sits under the cursor read straight out of that click.
Video title and channel appear once unlocked.
Concept 8
After: mapbox-geojson-source
The same complaint points as counted clusters that break apart as you zoom in.
Video title and channel appear once unlocked.
Concept 9
After: data-driven-styling
A heavy boundary file uploaded to Mapbox and served back as vector tiles, plus the simplification that should happen first.
Video title and channel appear once unlocked.
Concept 10
After: first-mapbox-map
A folder of files pushed to a repository, GitHub Pages switched on, ending at a live public link.
Video title and channel appear once unlocked.
18 candidates did not meet the course criteria.
Spatial-data and analytics roles — building GIS systems, remote-sensing pipelines, urban dashboards, and data products for planning clients, authorities, and tech/geospatial firms. Strong demand where planning meets data. Specialisation tags: Urban, Regional, Environmental (cross-cutting).
9 mapped employers
Explore path →