Transport for London's cycle-hire board is deciding which two boroughs get the next expansion tranche. The bid documents talk about 'coverage' without a number. Before the meeting you have been asked for one table: every borough, how many docking points it holds today, and how dense that supply is per square kilometre — including the boroughs where the answer is zero, because those are the ones bidding.
Produce one feature per borough — all of them, including those with no station — carrying:
name — the boroughdocks_total — the sum of docks over every station inside the boroughdocks_per_km2 — docks_total divided by the borough's area in km²The stations are points and the boroughs are polygons; nothing joins them but geometry. The boroughs file has no area column. Compute the area yourself, in a projected CRS — EPSG:27700 (British National Grid) is what every London dataset is published in, and area in degrees is not area.
Return the borough polygons, in EPSG:4326, ranked densest first.
These are where the teaching is. Read them twice.
Supply-density tables like this one sit under every bike-share, EV-charger and bus-stop equity review a transport authority publishes.
6 scored, 0 informational
One feature per borough, none missing
23%Result carries borough polygons
8%Carries name, docks_total and docks_per_km2
15%Total docking points across all boroughs
23%The densest borough's docks per km²
23%Submitted in EPSG:4326
8%