Local Planning Scheme No. 3 Amendment No. 5 — City of Joondalup
Approves City of Joondalup Local Planning Scheme amendment related to R-codes and development requirements.
Details
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 Joondalup Local Planning Scheme amendment on 13 January 2021 for the purpose of— (a) Delete clause 26 (5) of Modifications of the R-codes, within Part 4 General Development Requirements, and replace it with the following— (5) Clause 5.1.1 of the R-codes Volume 1 is modified by inserting the additional ‘deemed-to-comply’ criteria— C1.5 In Residential areas where dual coding applies, the higher coding may be applied subject to the following— i. Development of single and grouped dwellings which complies with a minimum frontage of 9 metres at the primary street setback; or ii. Development of grouped dwellings on corner lots with frontages to two streets, with rear common property access, which complies with a minimum frontage of 6 metres. (6) Clause 5.4.2 of the R-codes Volume 1 is modified by inserting the additional ‘deemed-to-comply’ criteria— C2.3 For Residential areas with a dual code and the higher code is applied, where a development site shares its southern boundary with any other adjoining property, its shadow cast at midday 21 June shall not exceed the following limits— i. On adjoining sites coded R60 or greater—40% of the site area. ii. On adjoining sites coded R30 to R40 inclusive—35% of the site area. iii. On adjoining sites coded R25 and lower—25% of the site area. iv. Where an adjoining site is subject to a dual density code and the site is yet to be developed to the higher code, the base density code applies for the purposes of determining the maximum amount of shadow cast permitted. v. Buildings orientated to maintain 4 hours per day solar access on 21 June for existing solar collectors on neighbouring sites. vi. Where a development site shares its southern boundary with a lot, and that lot is bound to the north by another lot(s), the limit of shading for the development site set out in clause 26(6)i-iii shall be reduced proportionate to the percentage of the affected property’s northern boundary that the development site abuts. (7) In addition to the Primary Controls Table 2.1 of the R-Codes Volume 2, the following development standards apply— i. Development of multiple dwellings which complies with a minimum site width street boundary of 20 metres; and ii. For Residential areas coded R20/40 multiple dwellings shall comply with the average site area per dwelling requirement specified for a single or grouped dwelling for the applicable density coding under SPP 7.3—Volume 1 unless the site— a. has primary street frontage to a road with scheme reservation classification of Local Distributor Road or Other Regional Road; or b. is located within an 800m walkable catchment, as defined on the Scheme map, from any existing or proposed strategic metropolitan, secondary, or specialised activity centre or railway station on a high frequency rail route; or c. is located with a 400m walkable catchment, as defined on the Scheme map, from any existing or proposed district activity centre. (8) Section 3.2 of the R-Codes Volume 2, is modified by inserting the additional ‘Acceptable Outcomes’ criteria— A 3.2.5 For Residential areas with a dual code and the higher code is applied, where a development site shares its southern boundary with any other adjoining property, its shadow cast at midday 21 June shall not exceed the following limits— i. On adjoining sites coded R60 or greater—40% of the site area. ii. On adjoining sites coded R30 to R40 inclusive—35% of the site area. iii. On adjoining sites coded R25 and lower—25% of the site area. iv. Where an adjoining site is subject to a dual density code and the site is yet to be developed to the higher code, the base density code applies for the purposes of determining the maximum amount of shadow cast permitted. v. Buildings orientated to maintain 4 hours per day solar access on 21 June for existing solar collectors on neighbouring sites. vi. Where a development site shares its southern boundary with a lot, and that lot is bound to the north by another lot(s), the limit of shading for the development site set out in clause 26(8)i-iii shall be reduced proportionate to the percentage of the affected property’s northern boundary that the development site abuts. (b) Update Clause 26 (4) to refer to 26 (7)i, in addition to 26 (5). (c) Renumber Clause 26 and sub clauses where appropriate. (d) Insert the walkable catchments described in 26(7)ii on the Local Planning Scheme Map (as they relate to the Housing Opportunity Areas) and cross reference Clause 26(7)ii within the map legend.
📜 Amendment History - Local Planning Scheme No. 3
View full chain →Invalid Date · Amends the City of Joondalup Local Planning Scheme No. 3 to update land use terms and permissibility for short-term rental accommodation.
Invalid Date · Approves rezoning of land in Currambine from residential to commercial and mixed use.
Invalid Date · Approves City of Joondalup Local Planning Scheme amendment adding design review panel provisions.
Invalid Date · Approves rezoning of portion of Lot 600 Treetop Avenue, Edgewater from 'Residential' to 'Public Purposes' and removes density code.
Invalid Date · Enacts the City of Joondalup Local Planning Scheme No. 3, setting out planning aims, reserves, zones, and development controls.
Invalid Date · Approves City of Joondalup Local Planning Scheme amendment to rezone areas in Marmion.
Invalid Date · Approves City of Joondalup Local Planning Scheme amendment to insert additional use No. 18 and amend the Scheme Map for Lot 847 Tuart Road, Greenwood.
Invalid Date · Rezones land within the MacNaughton Crescent Structure Plan from 'Urban Development' to 'Residential', 'Public Open Space', and 'Local Road' reserves.
Invalid Date · Approves a local planning scheme amendment by the City of Joondalup regarding land use permissibility.
Invalid Date · Corrects an error in a previously published government gazette notice regarding site-specific development standards in Craigie.
Invalid Date · Approves rezoning of Cragie High School site from urban development to residential, public open space, and local road reserves.
Invalid Date · Approves rezoning of land within the Camberwarra Local Structure Plan from 'Urban Development' to 'Residential', 'Public Open Space', and 'Local Road' reserves.
Invalid Date · Approves City of Joondalup Local Planning Scheme No. 3 Amendment No. 6, changing land use permissibility and rezoning land in Cragie.
Invalid Date · Approves rezoning of land bound by Cook Avenue, Ferndene Mews, Willandra Drive and New England Drive from ‘Urban Development’ to ‘Residential’ zone, ‘Public Open Space’ and ‘Local Road’ reserves.
Invalid Date · Reclassifies Cranston Park and Trigonometric Park from ‘Public Open Space’ reserve to ‘Environmental Conservation’ reserve in the City of Joondalup.
Invalid Date · Rezones land within the Kinross Neighbourhood Centre Structure Plan from ‘Centre’ to ‘Commercial’ and ‘Residential’ zones.
Invalid Date · Rezones land within the Currambine Structure Plan from ‘Urban Development’ to ‘Commercial’ and ‘Residential’ zones and applies ‘R20’ and ‘R40’ residential density codes.
Invalid Date · Approves amendment to City of Joondalup Local Planning Scheme No. 3 to rezone land in Woodvale.
Amendment history
Planning
Planning
Planning
Planning
Government
Planning
Planning
Planning
Related notices
Amends the City of Joondalup Local Planning Scheme No. 3 to update land use terms and permissibility for short-term rental accommodation.
Requires landowners in the City of Joondalup to clear firebreaks and remove flammable materials by October 31st to prevent bushfires.
Appoints bush fire control officers for the City of Joondalup.
Prohibits the burning of garden refuse or rubbish within the district of Joondalup at all times during the year.
Explore WA Government Data
Search the full archive in the free dashboard, or query programmatically via API.