03.09.2014 Views

AGENDA - Sunshine Coast Council

AGENDA - Sunshine Coast Council

AGENDA - Sunshine Coast Council

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Strategy and Planning Committee Agenda 16 February 2011<br />

6. Based on the results of the Acid Sulfate Soil investigation required by the above<br />

condition, formulate an Acid Sulfate Soil Environmental Management Plan (ASS EM<br />

Plan) consistent with Appendix 4 of the SPP2/02 Guideline and the Management<br />

Principles of the Latest Version of the Queensland Acid Sulfate Soils Technical<br />

Manual: Soil Management Guidelines;<br />

7. The development must comply with the Acid Sulfate Soil Environmental Management<br />

Plan required to be submitted by this approval;<br />

1<br />

State Planning Policy 2/02 Planning and Managing Development Involving Acid Sulfate Soils.<br />

2<br />

State Planning Policy 2/02 Guideline: Acid Sulfate Soils<br />

8. Prior to approval of each lot reconfiguration stage or operational works for bulk<br />

earthworks (whichever is sooner), the amount of fill material, source of fill and any<br />

proposed haulage route must be nominated for that stage of development;<br />

9. All roads and frontage works within each stage must be surveyed, designed and<br />

constructed in accordance with the relevant provisions of “Queensland Streets” and<br />

<strong>Council</strong>’s Development Design Planning Scheme Policy and in accordance with the<br />

specific requirements of this approval, including the following:<br />

• Compliance with the cross-sectional requirements for Trunk Collector Roads as<br />

per Drawings PW-01 and PW-02, attached to this approval;<br />

• Minimum requirements for a collector street include a road reserve of 16.0 metres<br />

wide with a 7.5 metre wide carriageway;<br />

• Minimum requirements for a residential access street/access place include a road<br />

reserve of 14.0 metres wide with a 5.5 metre wide carriageway;<br />

• The geometric design of the road system must ensure that the need for on<br />

carriageway speed control devices is limited;<br />

• Provision must be made for on-street visitor parking (indented bays where<br />

necessary), driveway access, pedestrian paths and stormwater treatment<br />

devices, as well as the full range of underground services within the proposed<br />

road reserves. Where necessary, additional road reserve area and/or<br />

carriageway width, in addition to the minimum specified, must be provided to<br />

achieve required clearances to services and ensure vehicle manoeuvring into<br />

driveways clear of on-street parking spaces;<br />

• Provision must be made for on-road cycle lanes on all trunk collector roads and<br />

higher order roads;<br />

10. On-street parking must be provided for all lots, in accordance with the requirements<br />

of Queensland Streets. In particular, indented bays (where necessary) must be<br />

provided clear of turning areas to serve lots adjacent to the end of each Access<br />

Place;<br />

11. Following filling of the site to achieve required minimum levels, resulting road<br />

pavement levels must comply with the maximum road flow depths set out in<br />

Queensland Urban Drainage Manual in the event that the proposed lake system is in<br />

flood and/or a Q100 storm surge event occurs, whilst providing access to allotments<br />

(where permitted) in accordance with <strong>Council</strong>’s standard verge profiles;<br />

12. Where proposed lots are located adjacent to bio-retention basins or other<br />

infrastructure, resulting in constrained lot frontage, an access driveway location must<br />

be nominated on lot reconfiguration proposal plans. Where an access driveway<br />

location is nominated for a lot frontage, no future alternative access will be permitted<br />

for that lot frontage;<br />

Page 81

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!