HomePlanning
🏗️

Local Planning Scheme No. 24 Amendment No. 71 — City of Bayswater

🔴 High UrgencyPlanning · Planning Amendment

Approves City of Bayswater Local Planning Scheme amendment modifying Precinct Boundaries plan within Special Control Area No. 10.

Details

Entity
City of Bayswater
Locations
City of Bayswater
Land Description
Lot 10, No. 2-4 Railway Parade, Bayswater; Lots 55, 59, 60, 61, 102, 103, 104, 301 and 302 Clune Street
Notice Date
2 March 2018
Reference Numbers
2-41055596061102103104301302

Notice Text

It is hereby notified for public information, in accordance with section 87 of the Planning and Development Act 2005 that the Minister for Planning approved the City of Bayswater Local Planning Scheme amendment on 16 February 2018 for the purpose of modifying the Precinct Boundaries plan contained within Special Control Area No. 10 by adjusting the common boundary between Precinct A and Precinct B, and modifying the existing Land Use and Development Requirements provisions which apply to Precincts A, B and C of Special Control Area No. 10.

WA Government Gazette No. 29/2018 · 2 March 2018 · Page 29
View Gazette PDF - Page 29
Share𝕏 PostLinkedIn✉ Email

📜 Amendment History - Local Planning Scheme No. 24

View full chain →
Local Planning Scheme No. 24 Amendment No. 84 — Correction

Invalid Date · Corrects an error in a previous notice regarding the Morley Activity Centre zoning table, changing the designation of 'telecommunications infrastructure' from an 'A' use to a 'D' use.

🏗️
Local Planning Scheme No. 24 Amendment No. 84 — Telecommunications Infrastructure

Invalid Date · Approves City of Bayswater Local Planning Scheme amendment to include 'Telecommunications Infrastructure' as a land use.

🏗️
Local Planning Scheme No. 24 Amendment No. 81 — Rezoning Lot 22 Guildford Road

Invalid Date · Approves rezoning of Lot 22, 454 Guildford Road, Bayswater from ‘Medium and High Density Residential R40’ to ‘Medium and High Density Residential R80’ and modifies Special Control Area 8.

🏗️
Local Planning Scheme No. 24 Amendment No. 79 — City of Bayswater

Invalid Date · Approves City of Bayswater Local Planning Scheme amendment to rezone lots and insert Special Control Area 15.

🏗️
Local Planning Scheme No. 24 Amendment No. 61 — Morley Activity Centre

Invalid Date · Approves City of Bayswater Local Planning Scheme amendment to include Morley Activity Centre and rezone the area as ‘Centre’ zone.

🏗️
Local Planning Scheme No. 24 Amendment No. 62 — Multiple Dwellings on R40 Lots

Invalid Date · Approves City of Bayswater Local Planning Scheme amendment to insert new clauses regarding multiple dwellings on R40 lots.

🏗️
Local Planning Scheme No. 24 Amendment No. 98 — Restricted Premises Definition

Invalid Date · Approves City of Bayswater Local Planning Scheme amendment to modify the definition of ‘restricted premises’.

🏗️
Local Planning Scheme No. 24 Amendment No. 96 — City of Bayswater

Invalid Date · Approves the City of Bayswater Local Planning Scheme amendment for rezoning lots in Bedford North.

🏗️
Local Planning Scheme No. 24 Amendment No. 97 — Bedford Rezoning

Invalid Date · Approves City of Bayswater Local Planning Scheme amendment to zone unzoned land in Bedford.

🏗️
Local Planning Scheme No. 24 Amendment No. 94 — City of Bayswater

Invalid Date · Approves rezoning of land in Morley from light industry to medium and high density residential.

🏗️
Local Planning Scheme No. 24 Amendment No. 90 — City of Bayswater

Invalid Date · Rezones land in Maylands from residential to local public open space.

🏗️
Local Planning Scheme No. 24 Amendment No. 89 — Bedford Rezoning

Invalid Date · Approves City of Bayswater Local Planning Scheme amendment to rezone Lot 11 Grand Promenade, Bedford to Mixed Use.

🏗️
Local Planning Scheme No. 24 Amendment No. 85 — Rezoning Lot 11 Embleton

Invalid Date · Rezones lot 11, 10 Burnett Street, Embleton from ‘Public Purpose (Religious Institution)’ and no zone to ‘Residential R50’.

Explore WA Government Data

Search the full archive in the free dashboard, or query programmatically via API.