Skip to main content

Reinstate footpath on Boundary St, Brisbane City

View on the council website (opens in a new tab)
Status: CLOSED, finished
Signatures: 12
Closed: 18 Oct 2020
Principal petitioner: Belinda Ward
ePetition number: 940

The petition

Residents draw to the attention of Council that a section of the footpath along the northern side of Boundary Street, Brisbane City, between Ivory Street and Ivory Lane was removed in 2017 as part of Council’s project to reconfigure the intersection of Boundary Street and Ivory Street. Kerb ramps assisting people to cross Boundary Street by the most direct route were also removed at that time. Despite this, many people continue to walk this way, as evidenced by the path worn through the grass.

The alternative footpath on Boundary Street provides a less direct route to the Story Bridge, New Farm Riverwalk, and Howard Smith Wharves. It is quite narrow in places, and contends with several driveway crossings. Since the opening of the commercial precinct at Howard Smith Wharves, there has been a substantial increase in the number of vehicles using Boundary Street (including stopping by the kerb), which makes it inconvenient, difficult and sometimes dangerous for people to cross Boundary Street mid-block.

Your petitioners therefore request that a footpath be reinstated along the northern side of Boundary Street, and that a crossing be provided at the intersection with Ivory Street. We further request that any future intersection “improvement” or “upgrade” projects in Brisbane be carefully reviewed to ensure they are not to the detriment of people using active transport – particularly in high-use pedestrian zones, in proximity to public transport, and on primary cycle routes.

Council response

In June 2017, Council completed works to facilitate improved access through the Ivory Street and Boundary Street intersection to assist in addressing access, safety and congestion issues. As part of the works, a new crossing point was provided on Boundary Street with new kerb ramps and connection to the existing footpath.

Council received a petition in 2018 requesting the reinstatement of the footpath along the northern side of Boundary Street. In response to that petition, Council committed to undertaking a traffic and pedestrian study to review the overall performance of the intersection, including pedestrian movements.

The pedestrian counts referenced in the study highlighted significant pedestrian volumes crossing east to west over Boundary Street. However, the volumes conflicted with previous pedestrian counts on record and, as such, new counts were requested in November 2020. The survey indicated 154 pedestrians crossed Boundary Street, at its intersection with Ivory Street, in the 13 hour survey period.

The use of this location to cross the road is noted. However, only a signalised crossing could be considered at this location and analysis shows that the signal phasing required for a signalised pedestrian crossing could lead to queuing back onto the Story Bridge. An unsignalised crossing at the intersection is unable to be supported, as it would create safety risks due to limited sight lines and multiple conflicting vehicle movements.

Your feedback about disruption to active transport has been noted. Council takes every care to ensure disruptions to existing travel paths are minimised. In this instance, the modified crossing point requires a diversion of less than 70 m, which allows pedestrians to cross Boundary Street away from the intersection and improves sight lines for all road users. As such, Council considers that the localised changes are justified and have improved safety.

For these reasons, there are no plans to install a new pedestrian crossing at the intersection or extend the existing footpath on Boundary Street. However, to further guide pedestrians to use the crossing point on the northern side of Boundary Street, south of the Ivory Street intersection, Council will investigate the installation of infrastructure, such as low-level vegetation or pedestrian fencing.

Comments · 0

Loading...

Loading comments...