20.01.2015 Views

Draft National Wind Farm Development Guidelines - July 2010

Draft National Wind Farm Development Guidelines - July 2010

Draft National Wind Farm Development Guidelines - July 2010

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

Recording the occurrence and outcome of consultation activities is necessary at all<br />

stages; however, an output of this stage could be a consultation report or chapter in the<br />

planning application document which should outline:<br />

• Parties consulted<br />

• Consultation activities undertaken<br />

• Nature of feedback<br />

• Key outcomes of consultation (i.e. design amendments).<br />

Once the planning application has been lodged, the relevant authority may require 5 that<br />

the wind farm developer, in addition to any statutory public exhibition and consultation<br />

requirements, ensure that the community and stakeholders are:<br />

• Aware of the planning application lodgement<br />

• Provided details on how to view the documentation<br />

• Provided details on opportunities to comment on the documentation.<br />

The duration and manner in which statutory public comment can occur will be<br />

determined and coordinated by the relevant authority, under the planning legislation<br />

requirements of the relevant jurisdiction. Despite this, it remains the responsibility of the<br />

developer to ensure that the community and stakeholders are given adequate access to<br />

associated documentation and notice of the planning application lodgement. This is<br />

required to facilitate community input in the planning assessment process.<br />

Technical Area Community Inputs<br />

A number of opportunities may be available for local community members to be involved<br />

in the landscape assessment process. Identification and description of community<br />

landscape values and key views, description of potential visual and landscape impacts,<br />

and development of mitigation measures should benefit from input from key community<br />

stakeholders (particularly those within close proximity to the site).<br />

Dialogue with potentially affected stakeholder agencies may be initiated for the<br />

electromagnetic interference assessment. These stakeholders may include agencies such<br />

as the Bureau of Meteorology, Department of Defence, telecommunication companies<br />

and Air Services Australia.<br />

Furthermore, noise and shadow flicker results should be communicated to relevant<br />

stakeholders. Specifically, the outcomes of background noise monitoring should be<br />

provided to stakeholders who hosted noise loggers on their property (at a minimum). Noise<br />

and shadow flicker compliance with necessary guidelines should be determined at this<br />

stage, and the opportunity should be provided for neighbouring landowners to comment<br />

further on any identified impacts.<br />

Further detail on technical area community inputs can be found under noise (page 54),<br />

landscape (pages 82-86 and 88), birds and bats (page 125) and electromagnetic<br />

interference (page 177-179).<br />

A.6.4 Construction<br />

Planning & Consultation<br />

Once again review and revision of the detailed Communication & Consultation Plan, or<br />

preparation of a new plan, should be undertaken at the beginning of this phase. This plan<br />

should identify construction activity notification measures and handling processes for<br />

complaints and enquiries.<br />

5 This is at the discretion of the approving body, based on the relevant statutory requirements within<br />

the relevant state or local government jurisdiction.<br />

<strong>Draft</strong> <strong>National</strong> <strong>Wind</strong> <strong>Farm</strong> <strong>Development</strong> <strong>Guidelines</strong> – 2 <strong>July</strong> <strong>2010</strong> Page 31

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

Saved successfully!

Ooh no, something went wrong!