the Orbiter
5 stops the record says the Orbiter calls at, through 3 suburbs, the 34th most-served route in the stop record. The record files most of the loop's platforms under its two directions, the Orbiter (anticlockwise), 96 stops and the Orbiter (clockwise), 94 stops; the stops on this page are the poles it still files under the plain code.
Where it runs
The line is the driven path Metro’s GTFS feed draws for this number; the dots are the platforms the older stop layer lists. The darker outlines are the suburbs the route threads.
The suburbs it threads
A suburb counts the stops inside its own outline.
The roads it claims
The road each stop’s record names, one route can claim the same road at both ends of town.
Every stop it serves
The record behind this
Every stop comes from Environment Canterbury’s Metro stop layer, the platforms the buses call at and the routes the record says serve each one. The layer sits in ECan’s Beta tree, so the page is as current as the last bake, not as the last timetable. A suburb is the one the stop’s own coordinates fall inside.
Every route in the record is ranked at /buses. This page as markdown: /buses/or.md.
Questions, answered briefly
5 stops on the record through 3 suburbs, Bryndwr, Linwood, Phillipstown. The suburbs are the ones the stops' own coordinates fall inside.
5 in Environment Canterbury’s stop layer, #34 of the routes in the record by stops. The layer is the platforms, not the timetable.
As current as the site’s last bake, the stop list is ECan’s Metro layer (their Beta tree), and the drawn line is the driven path Metro’s GTFS feed publishes for this number.