SUITE 1, LEVEL 2,

SUITE 1, LEVEL 2, 1-17 ELSIE STREET, BURWOOD, NSW 2134

POBOX 240, BURWOOD, NSW 1805

TEL: 9911 9911 FAX:9911 9900

WEBSITE:

DIGITAL 3D DEVELOPMENT APPLICATION MODELSPECIFICATIONS

A digital 3D model is required to be submitted with all developments as follows:

  1. All residential or mixed commercial/residential developments that contain 4 or more dwellings, and/or exceed 2 storeys in height.
  1. Non-residential developments i.e. commercial, institutional, educational that are more than 2 storeys in height.

Required Model Elements

The supplied model should include enough detail to determine a development’s compliance with the relevant planning objectives and strategies.

The digital 3D model must contain the subject building and clearly show all adjoining buildings in block form and if deemed necessary, those buildings opposite the site. Location of windows/balconies of adjacent buildings facing the site are also required to be included in the model.

The model should be a realistic representation of the exterior of the development showing coloured materials without file textures.

All digital 3D models must show all architectural features of the building such as:

  • All protrusions and indents
  • Window and door openings/entry points
  • Balconies and balustrades
  • Awnings and verandahs
  • Blade or fin walls
  • Sun shading devices
  • Roof construction and/or roof features – including roof pitch and all significant features including plant enclosures, service and fire stair protrusions, terraces, flag poles or similar, shade and signage structures
  • Where communal or private open space is proposed on the roof of a building all proposed roof structures, pergolas, stair and lift over runs etc are also to be shown
  • Car parking, vehicle access and egress points
  • Major signage
  • Landscaping features of significance such as large planter boxes should be included, however vegetation should be kept to an absolute minimum. Proposed tree to be in simple shape to define the height and diameter of tree crown and its location
  • Interior detail should be excluded from submitted digital 3D models to optimize file size and loading time
  • Site topography should be modeled from accredited and recent survey based on AHD levels
  • Model should include buildings and works within the site boundary and transition to the public domain.

File Format and Specifications

A digital 3D model of a development must be supplied in one of the following formats:

  • 3DS
  • IGES
  • SKP
  • DWG
  • DXF
  • DWF
  • STP

The digital 3D model file is to be submitted in organized logical layers, e.g. built form, landscape, topography.

If unable to provide a 3D model in the above formats contact Burwood Council to discuss other possible model formats.

  • The digital 3D model file size must be less than 50Mb
  • The model units must be in metres and features must be scaled correctly at a scale of 1:1 – no resized or moved components
  • The pivot/origin point of the digital 3D model must be at the centre of the subject building/development
  • Drawing elements such as text or dimensions should not be included in the submitted digital 3D model
  • The model should not include references to external files.

The digital 3D model file name should include the development address, date of submission and the term “3D Model”.

Example: “1Burwood Road, Burwood 25102013 – 3D Model.3Ds”

Development Application Plans and Documentation

All relevant documents, as required in the Burwood Council Development Application Checklist, should be submitted to Council electronically with the Development Application along with the digital 3D Model as separate PDF files on CD/DVD.

Any modified and amended plans are required to be supported by a modified digital 3D model.

Each document PDF must be named after the document that it contains.

For example:

  • Architectural Plans.pdf
  • Acoustic Report.pdf
  • Statement of Environmental Effects.pdf
  • Traffic Report.pdf
  • Fire Safety.pdf

TRIM No. 14/20278

Digital 3D Development Application Model SpecificationsPage 1 of 2