Query cycle_docks. Exclude temporary. Return one row for every full station (empty_docks=0 and bikes>0) and every empty station (bikes=0), with dock_id, condition (full or empty), bikes, and docks. This queue is the starting point for transfer planning.
These are the input columns your query can read. The Data tab also shows field meanings and sample records.
cycle_docksCurrent sandbox schema| Column | Type |
|---|---|
| id | integer |
| dock_id | text |
| name | text |
| terminal | text |
| docks | integer |
| bikes | integer |
| empty_docks | integer |
| standard_bikes | integer |
| ebikes | integer |
| temporary | boolean |
| snapshot_at | text |
| geom | geometry(Geometry,4326) |
A London cycle-hire operations team has a frozen dock snapshot. It needs a reproducible queue of full and empty stations, a conservative list of short transfer candidates, and a shift summary that states how many empties remain unserved. This is a planning exercise; dispatch would recheck availability and use the street network.
Three handoffs: query the stations needing attention; map candidate moves under the stock and distance rules; then size the shift from those moves and count the empty stations with no move. Work from the frozen snapshot. Great-circle lines are proximity estimates, not drivable routes. Do not call the result a live dispatch order.
These are where the teaching is. Read them twice.
TfL describes morning and evening redistribution patterns and operational vehicles for Santander Cycles (https://tfl.gov.uk/corporate/transparency/freedom-of-information/foi-request-detail?referenceId=FOI-4360-1718). This frozen-snapshot exercise uses straight-line legs and a hypothetical 20-bike van capacity; neither is TfL’s actual route plan or staffing rule.
Each query runs on its own — explore as much as you like. The one marked Answer is what Check hands in.
2 scored, 0 informational
Active stations needing attention
67%Queue identifies a dock and condition
33%