Standard requirements for LEP GIS data. November 2008 Version 1.1



Similar documents
Vermont GIS Parcel Data Standard

Arts Revitalisation Projects and the Planning System. January 2010 Guideline

Guidelines for the use of the OGP P6/11 bin grid GIS data model

The following people addressed Council regarding recommendations 72 and 73: The following people addressed Council regarding recommendations 65 to 71:

How to do it Manual No. 3: ArcMap10 in Remote Desktop mode and Landgate slip files. Jeremy Green

HELCOM Data and Map Service. User Manual

GIS Spatial Data Standards

Wyoming Geographic Information Science Center & Wyoming Game & Fish Department

ACTIVITY CENTRE ZONE MAPPING STYLE GUIDE. Guidelines for producing Framework Plans and Precinct Maps for the Activity Centre Zone

NSW Housing Code A guide to complying development

National Levee Database (NLD) Data Management Tool (DMT) Levee Data Manager User Manual 1.2

SCIMS Online Support Guide

Data access and management

Geomatics Guidance Note 3

GEOGRAPHIC INFORMATION SYSTEMS CERTIFICATION

GIS User Guide. for the. County of Calaveras

CITY OF SUFFOLK, VIRGINIA GIS DATA DISTRIBUTION AND PRICING POLICY

Downloading SSURGO Soil Data from Internet

Using CAD Data in ArcGIS

Guidelines on Information Deliverables for Research Projects in Grand Canyon National Park

BUILDING INFORMATION MODEL (BIM) PROTOCOL

ArcGIS Reference Document

Quick Reference Guide - Native vegetation notification system

Water Sensitive Urban Design and Integrated Water Cycle Management. DA Planning Agreement

Implementing a Coastal Settlement Boundary

Online Data Delivery System

Creating a File Geodatabase

SITE PLAN APPROVAL PROCESS INTRODUCTION

CentralMass DataCommon

Standard 1. Governance for Safety and Quality in Health Service Organisations. Safety and Quality Improvement Guide

Digital Terrain Model Grid Width 10 m DGM10

An Esri White Paper October 2010 Esri Production Mapping Product Library: Spatially Enabled Document Management System

EXPRESSION OF INTEREST DESIGN, DOCUMENTATION AND PROJECT MANAGEMENT UNIT COMPLEX - LOT 8955 PALMERSTON

6 CHAPTER 6 DATA MANAGEMENT

How to use the Service Directory and send ereferrals and other Documents securely

Syllabus Introduction to GIS 120

The format this is requested in contains a. Users should provide the answer in DD/MM/YYYY. The Range for Historic Performance Data be DD/MM/YYYY

DEVLOPMENT APPLICATION PROCEDURES

Australian Standard. Customer satisfaction Guidelines for complaints handling in organizations (ISO 10002:2004, MOD) AS ISO

Board of Surveying and Spatial Information

CHAPTER 13 STATE FRANCHISE FOR CABLE TELEVISION SERVICE SECTION.0100 GENERAL REQUIREMENTS

NatureServe s Environmental Review Tool

How to open a small bar in the city

SWAMP DATA MANAGEMENT PLAN

Geographic Information Systems and Spatial Data in the Service of Flood Management: A Report on an Initiative of the State Emergency Service

LYON COUNTY GEOMOOSE 2 HELP DOCUMENT

HOW TO SET UP A CHILD CARE CENTRE IN MOSMAN

NSW Data & Information Custodianship Policy. June 2013 v1.0

Import and Export User Guide PowerSchool Student Information System

Cookbook 23 September 2013 GIS Analysis Part 1 - A GIS is NOT a Map!

Building Plans: Electronic Submission Process and Requirements

Absolute Software Topup Tax (Year 2 onwards)

{ { { Meeting Date 08/03/10. City of Largo Agenda Item 24. Leland Dicus, P.E., City Engineer

Data Interoperability Extension Tutorial

Create and share a map with GIScloud.com

Prior Notification of Proposed Demolition Validation Checklist

Environmental Impact Assessment of Forestry Projects

Texas Wildfire Risk Assessment Portal (TxWRAP) User Manual. Texas A&M Forest Service

NSW Globe user guide

Local Government Requirements: A Handbook for CHILD CARE PROVIDERS

Cadastral Survey Requirements. Version 7.1 December 2015

[Project Name] NZTA Contract No. [Contract Number] Schedule of Prices

The Land Victoria Lodging Book A guide to dealings Section 4 Subdivision Act 1988

Create a folder on your network drive called DEM. This is where data for the first part of this lesson will be stored.

Assessment and Reporting in Business Studies Stage 6

APLS GIS Data: Classification, Potential Misuse, and Practical Limitations

Preparing a Green Wedge Management Plan

Operative Media. Operative.One. Release Bulk Data Loaders User's Guide. Document Version 1.0

Software: AutoCAD Civil 3D 2014, NRCS C3D 2014 template, ESRI ArcMap. Notation:Button to Press Displayed Text Icon Action {Text to Enter} Menu Item

ArcGIS Data Models Practical Templates for Implementing GIS Projects

GeoEditor User Manual

CITY OF SUBIACO. PLANNING POLICY 1.4 (September 2013) PUBLIC NOTIFICATION OF PLANNING PROPOSALS

TENDER DOCUMENT PROCEDURE FOR MAJOR WORKS CONTRACTS USING AS GENERAL CONDITIONS OF CONTRACT

Finding GIS Data and Preparing it for Use

Creating Figure Ground Maps in ArcMap 10.x: Basic procedures to download, open, manipulate and print spatial data

Getting Started With Mortgage MarketSmart

Geographic Information System Product Distribution Policies. Preface

Guide to Subdivision and Land Development

Australian/New Zealand Standard

Modifying Colors and Symbols in ArcMap

ARIBA Contract Management System. User Guide to Accompany Training

Appendix C - Risk Assessment: Technical Details. Appendix C - Risk Assessment: Technical Details

Transcription:

Standard requirements for LEP GIS data November 2008 Version 1.1

State of New South Wales through the Department of Planning www.planning.nsw.gov.au November 2008 Publication number DOP 08_004 ISBN 978-0-7247-5934-4 Disclaimer: While every reasonable effort has been made to ensure that this document is correct at the time of printing, the State of New South Wales, its agents and employees, disclaim any and all liability to any person in respect of anything or the consequences of anything done or omitted to be done in reliance upon the whole or any part of this document.

Contents Contents...i Introduction... ii 1. Submission of geographic information system (GIS) data...1 1.1. Cadastre base...1 1.2. Export formats...1 1.3. File naming...2 2. GIS data layers to be supplied...3 1. Map index grids (MAP)...3 2. Land application (LAP) clause 1.3...4 3. Land zoning (LZN) clause 2.2...4 4. Additional permissible uses (APU) clause 2.5...5 5. Lot size (LSZ) clause 4.1...5 6. Height of building (HOB) clause4.3...6 7. Floor space ratio (FSR) clause 4.4...7 8. Land reservation acquisition (LRA) clause 5.1...7 9. Public land (PUB) clause 5.2...8 10. Heritage (HER) clause 5.10...8 11. Local provisions flood prone land, foreshore building lines etc....9 3. Procedures for amendments to LEP GIS data...11 4. Contact...13 i NSW Department of Planning 2008

Introduction This document replaces the earlier document: Standard requirements for LEP GIS data September 2007 Version 1.0. A reliable and up-to-date set of the spatial information contained within local environmental plans (LEPs) has been identified as a resource that is critical to the work of planners generally. This document defines data standards for geographic information system (GIS) datasets generated by councils when making their LEP maps. The objective is to ensure that the LEP data fully and accurately reflects the content of the new Standard LEP instrument. Common data standards for state and local government improve efficiencies in the creation and assessment of LEPs. The GIS LEP datasets will initially be used for considering the strategic implications of draft LEPs. Future state and local government electronic planning projects may also rely on the final data set. LEP data will be requested for all draft and final LEPs, in accordance with section 33C of the Environmental Planning and Assessment Act 1979 (EP&A Act). The Department advises, pursuant to the EP&A Act, that the Crown in right of New South Wales holds copyright over all LEPs and this right extends to the associated maps and GIS datasets. As such the Department does not require a licence to use the LEP GIS data. Where consultants are engaged to create LEP data and maps for councils, the requirement for the GIS data to be submitted to the Department should be reflected in the contractual arrangements. The Crown Solicitor s Office (NSW) advises that contractual arrangements with consultants should contain an acknowledgement from the consultant that the work to be undertaken, is undertaken for the purposes of creating an environmental planning instrument under the Environmental Planning and Assessment Act 1979 (NSW) and the Crown in right of New South Wales is the owner of any new copyright subsisting in the work created by the consultant. This document should be read in conjunction with the document Standard technical requirements for local environmental plan maps produced by the Department and made publicly available on the Departments website http://www.planning.nsw.gov.au. Other useful reading includes the Standard Instrument Principal Local Environment Plan made publicly available on the Parliamentary Counsel s Office website at http://www.legislation.nsw.gov.au. To provide feedback on this document please refer to the contact details provided at end of this document. ii NSW Department of Planning 2007

1. Submission of GIS data Council submission under section 64; submission of draft LEP prior to public exhibition the Department of Planning requests the GIS data relating to the LEP be submitted at this stage, along with the written document and PDF maps for assessment by the regional planning teams. Council submission under section 68(4); resubmission of draft LEP post-exhibition and submissions the Department of Planning requests the GIS data relating to the LEP be submitted at this stage, for inclusion in the Department s state-wide LEP dataset. At both stages the completed data sets should be sent to the following email address: LEP@planning.nsw.gov.au. The subject heading should contain the key word GIS and the LEP name. The GIS data should be sent in a separate email to other LEP information such as the written document or the PDF maps. Where email size is > 10Mb in size, the delivery of files must be made via the FTP site. An email should be sent in the same manner as described above, notifying the Department that an upload to the FTP site is intended and requesting site and login details. Where gazetted amendments affect the spatial data of the LEP, the relevant digital GIS data will also need to be submitted to the Department. The procedure will be as for that described above except that the subject heading should contain the keyword GIS, the LEP name and the amendment number. Amendments are discussed in more detail later in this document. Cadastre base It is the Department of Planning s preference that the data and maps for all LEP information layers be constructed from the Department of Lands Cadastre base dataset. When councils submit LEP data based on other cadastres, this results in a misalignment with data from other surrounding LEPs at the Department of Planning where the Department of Lands cadastre will be used for the whole State. The Department is actively engaging with Lands to resolve the issue of cadastral alignment. Until this is resolved, the Department will accept LEP data that uses other cadastres as base data sets. Export formats GIS data should be supplied to the Department as a polygon datasets in shapefile, personal geodatabase or MID/MIF file formats. Other formats may be considered. If this is not possible, please contact the Department via the contact details provided to discuss alternatives. The correct datum and projection to use are cited below. Datum: GDA94 Projection: MGA94_z56, MGA94_z55, MGA94_z54 Where a council area traverses two projection zones the entire area will be projected into that zone where the majority of the area falls. 1 NSW Department of Planning 2008

File naming For consistency the GIS data file naming should follow the convention of naming the folder, directory (or geodatabase) with the LEP name*, and the individual data layers with the three letter map type codes (Refer Figure 5.3 Standard technical requirements for LEP mapping ). For example: Folder (or geodatabase): Wollongong_LEP2007 Data layers: APU FSR HER HOB LAP LRA LSZ LZN MAP PUB etc *All space chars to be replaced with underscores. 2 NSW Department of Planning 2008

2. GIS data layers to be supplied Attribute fields can be in any order but must contain all fields outlined below. 1. Map index grids (MAP) 2. Land application (LAP) clause 1.3* 3. Land zoning (LZN) clause 2.2 4. Additional permissible uses (APU) clause 2.5 5. Lot size (LSZ) clause 4.1 6. Height of building (HOB) clause 4.3 7. Floor space ratio (FSR) clause 4.4 8. Land reservation acquisition (LRA) clause 5.1 9. Public land (PUB) clause 5.2 10. Heritage (HER) clause 5.10 11. Data for any local provisions maps included by councils in their LEP *Clause numbers reference those in the Standard Instrument Principal Local Environmental Plan. 1. Map index grids (MAP) A polygon layer that shows the grids used to create the PDF maps of the LEP, with the map tile IDs assigned by council. The grids should be based on the standard scales at A3 that are identified in the standard technical requirements document (Geographic GDA94 grids for these scales at A3 across the whole State are available from the Department of Planning). LEP_NAME Char 80 Name of LEP MAP_TILE Char 3 ID assigned to the grid by council LEP_TYPE Char 4 Abbreviation for the LEP Type used in the map sheet reference. (Refer Figure 5.2 in Standard technical requirements for LEP mapping ) SCALE Char 3 Abbreviation for the grid scale used in the map sheet reference MAP_TYPE Char 4 Abbreviation for the map type used in the map sheet reference. (Refer Figure 5.3 in Standard technical requirements... ) If the same grids are used for all map types, enter ALL here LEP_NAME LGA_CODE MAP_TILE LEP_TYPE SCALE MAP_TYP E LLEP 2007 9898 001 COM 080 LRA 3 NSW Department of Planning 2008

2. Land application (LAP) clause 1.3 A layer that describes the land to which an LEP applies. If the whole of the LGA is included in the LEP, then the Land Application layer will be the whole LGA. If the LEP relates only to a portion of the LGA such as the city centre, then this feature will show the boundary of the city centre. Within this layer, land should be identified as either Included or Deferred in the LEP. All other datasets provided (except for map index grids) should fall within this boundary. LEP_NAME Char 80 Name of LEP LAP_TYPE Char 10 Deferred, Included LEP_NAME LGA_CODE DATE_ LAP_TYPE LGA Name LEP 2007 9898 23/2/2007 Included LGA Name LEP 2007 9898 23/2/2007 Deferred 3. Land zoning (LZN) clause 2.2 A layer that shows the zoning of all areas included in the LEP. No zoned polygon feature can overlap with another zoned polygon feature. All areas shown as included in the Land Application Map layer must have a zone attributed to them. LEP_NAME Char 80 Name of LEP ZONE_ Char 4 Zone code from the Land Use Table in the Standard LEP instrument or (DM) for deferred matters in the Principal LEP PURPOSE Char 25 The purpose as shown in the Land Zoning Map for zones SP1 and SP2. This field will remain blank for all other zones LEP_NAME LGA_CODE DATE_ ZONE PURPOSE LGA Name LEP 2007 9898 23/2/2007 RU1 LGA Name LEP 2007 9898 23/2/2007 SP1 School 4 NSW Department of Planning 2008

4. Additional permissible uses (APU) clause 2.5 This data relates to specific areas with additional permissible uses noted in Schedule 1 (clause2.5) of the written document. This data has not been requested in map form in the Standard LEP template however, it will need to be provided in GIS format. Can occur over any Included land from the Land Application Map layer. Overlaps can occur where there is more than one additional permissible use for a particular area. Features or groups of features must be attributed with a reference to the notation of the item in Schedule 1 (clause 14) of the written LEP document. Example information from written document: Schedule 1 Additional permitted uses 1 Land at the corner of Crown and Harbour Streets (1) This clause applies to part Lot 143, DP 78910 and Lot 65, DP 12345 (2) The consent authority may consent to development on the land to which this clause applies for the purposes of 2 Land at Rawson Street, Railway Parade (1) This clause applies (2) The consent authority may LEP_NAME Char 80 Name of LEP APU_CODE Char 25 Additional Permissible Uses reference code, from the written instrument LEP_NAME LGA_CODE DATE_ APU_CODE LGA Name LEP 2007 9898 23/2/2007 1 5. Lot size (LSZ) clause 4.1 This layer contains the minium lot size that can result from the subdivision of any lots to which clause 4.1 Minimum subdivision lot size applies. Can occur over any zone without the need for correlation with lots or existing zone allocation. No areas can overlap. Can only occur over Included land from the Land Application Map layer. 5 NSW Department of Planning 2008

LEP_NAME Char 80 Name of LEP LOT_SIZE Integer 10 Minimum lot size (in m2 or ha) UNITS Char 4 m2 or ha SYM_CODE Char 3 Symbol code that will appear as text on the map and the legend. (Refer Appendix A Standard technical requirements for LEP mapping ) INFO_CODE Char 40 Areas where the LEP contains further information about the calculation of Minimum Lot Size based on uses etc. should contain a reference to the written document in this field. Otherwise this field should remain blank. LEP_NAME LGA_ CODE LGA Name LEP 2007 INFO_CO DE DATE_ LOT_SIZE UNITS SYM_ CODE 9898 23/2/2007 420 m2 H Refer to clause 4.1A 6. Height of building (HOB) clause 4.3 The maximum building height allowed for areas of the LGA as described in clause 4.3 of the written document. Areas where further information about the calculation of maximum building heights is included in the written document (e.g. Building height based on use) need to be noted. Can occur over any zone without the need for correlation with lots or existing zone allocation. No areas can overlap. Can only occur over Included land from the Land Application Map layer. LEP_NAME Char 80 Name of LEP MAX_B_H Float Maximum building height in metres UNITS Char 7 m (AHD) or m(rl) SYM_CODE Char 3 Symbol code that will appear as text on the map and the legend. (Refer Appendix A Standard technical requirements for LEP mapping ) INFO_CODE Char 40 Areas where the LEP contains further information about the calculation of variable building heights based on uses etc. should contain a reference to 6 NSW Department of Planning 2008

the written document in this field. Otherwise, this field should remain blank LEP_NAME LGA_ CODE DATE_ MAX_B_ H UNITS SYM_ CODE INFO_ CODE LGA Name LEP 2007 9898 23/2/2007 10 m H Refer to clause 4.3A 7. Floor space ratio (FSR) clause 4.4 The floor space ratio of a building on any land that clause 4.2 Floor Space Ratio applies to. Areas where further information about the calculation of FSRs is included in the written document (e.g. FSR based on use) need to be noted. No areas can overlap. Can occur over any zone without the need for correlation with lots or existing zone allocation. Can only occur over Included land from the Land Application Map layer. LEP_NAME Char80 Name of LEP FSR float Floor Space Ratio (n:1) only include n. 2 decimal places. SYM_CODE Char 3 Symbol code that will appear as text on the map and the legend. (Refer Appendix A Standard technical requirements for LEP mapping ) INFO_CODE Char40 Areas where the LEP contains further information about the calculation of variable FSRs based on uses etc. should contain a reference to the written document in this field. Otherwise, this field should remain blank LEP_NAME LGA_CODE DATE_ FSR SYM_ INFO_CODE CODE LGA Name LEP 2007 9898 23/2/2007 0.62 G Refer to clause 4.4A 8. Land reservation acquisition (LRA) clause 5.1 Data relating to land where the zoned purpose is different to the current use of the land and therefore the land will need to be acquired by the relevant authority. This can include land that is to become roads and open spaces etc. 7 NSW Department of Planning 2008

No areas of Land Reservation Acquisition can overlap. Can only occur over Included land from the Land Application Map layer. Must accord with the zoning information in the LZN data layer. While the list of acquisition types may extend for particular LGA requirements, those that are standard are Classified road, Regional open space, Coastal land protection, Public transport, Local road, Local open space, Schools, Hospitals. LEP_NAME Char80 Name of LEP LRA_TYPE Char 50 Classified road, Regional open space, from list etc AUTHORITY Char 50 Consent authority, RTA etc LEP_NAME LGA_CODE DATE_ LRA_TYPE AUTHORITY LGA Name LEP 2007 9898 23/2/2007 Classified road RTA 9. Public land (PUB) clause 5.2 This polygon data layer identifies public land defined as per the Local Government Act 1993 whether classified as Community or Operational. Can occur over any Included land from the Land Application Map layer. LEP_NAME Char80 Name of LEP CLASSIFIED Char12 Classification under clause 27 Community or Operational LEP_NAME LGA_ CODE DATE_ CLASSIFIED LGA Name LEP 2007 9898 23/2/2007 Community 8 NSW Department of Planning 2008

10. Heritage (HER) clause 5.10 This polygon data layer identifies Heritage Conservation Areas and Heritage Items that are noted in clause 5.10 Schedule 5 of the Standard LEP. Can occur over any Included land from the Land Application Map layer. Where possible to follow cadastral lot boundaries. Could also be building footprints or areas within or on overlapping lots, where substantially different from lot boundaries. H_ID should link to the item reference in Schedule 5.10. Features should have a 1:1 reln with items in the schedule. Heritage type must show if it relates to a Conservation Area or Item. Optionally, can be more specific and also include: Conservation Area Landscape Conservation Area Aboriginal Item Archaeological Item Aboriginal Areas with multiple heritage components that overlap will have individual polygons to represent each type of heritage. Overlapping of polygons within the data set is allowed where different types of heritage significance are present in the same locations. LEP_NAME Char80 Name of LEP H_TYPE Char 50 Conservation Area General Conservation Area Landscape (optional) Conservation Area Aboriginal (optional) Item General Item Archaeological (optional) Item Aboriginal (optional) Item Landscape (optional) H_NAME Char100 Name of heritage area or item as referred to in Schedule 5 of the LEP document H_ID Char20 ID of heritage area (letter) or item (number) as referred to in Schedule 5 of the LEP document SIG Char10 State or local significance LEP_NAME LGA_ DATE_ H_TYPE H_NAME H_I SIG CODE D LGA Name 9898 23/2/2007 Conservation Old town A State LEP 2007 Area - General LGA Name LEP 2007 9898 23/2/2007 Item - General Post Office 15 Local 9 NSW Department of Planning 2008

11. Local provisions flood prone land, foreshore building lines etc Also referred to as Miscellaneous Provisions in the Standard Instrument Principal Local Environment Plan. This GIS data layers used to create any of the local provision maps. This list may include, but is not restricted to, flood prone land (FLD), bush-fire prone land (BPL), foreshore building line (FBL), riparian land (RIP), key sites (KEY), scenic protection (SCP). Can occur over any Included land from the Land Application Map layer. Needs to include the fields LEP_NAME, LGA_CODE and DATE_. Other fields providing necessary information as determined by the council. LEP_NAME Char80 Name of LEP XX XX As determined by council YY YY As determined by council for Key Sites LEP_NAME LGA_ DATE_ KEY_NAME KEY_ID CODE LGA Name LEP 2007 9898 23/2/2007 Old town 1 LGA Name LEP 2007 9898 23/2/2007 Post office 2 10 NSW Department of Planning 2008

70//2384 18//2384 71//2384 17//2384 101//736901 5//511100 4//502298 B//390565 78//2384 10//2384 79//435395 Standard requirements for LEP GIS data 3. Procedures for amendments to LEP GIS data When amendments are made to a local environmental plan that change any of the GIS layers mentioned above, new GIS data for the areas effected will need to be supplied to the Department of Planning in order to update the Department s state wide dataset. This applies for amendments to the standard template local environmental plans as well as new amendments to LEPs created before the introduction of the Standard Template. The amended features should be supplied to the Department in the same format as the initial LEP GIS data supply with the addition of a field to note the name of the amendment. The date field should include the date of the supply of the amendment data. for zone amendment LEP_NAME Char80 Name of LEP being amended DATE_ Date Date that amendment data is submitted (dd/mm/yyyy) ZONE_ Char4 Proposed new zone code from the Land Use Table in the Standard LEP instrument AMENDMENT Integer 4 Amendment number. PURPOSE Char25 The purpose as shown in the Land Zoning Map for zones SP1 and SP2. This field will remain blank for all other zones Example amendment locations (zone layer) 50//2384 10//2384 9//2384 1//877963 8//2384 7//2384 6//2384 2//421541 A//345061 121//717297 3//2384 1031//1049068 3//2198 2//2384 1//523638 2//803120 1//803120 2//2198 B//30046 C//30046 D//30046 E//30046 F//30046 G//30046 2//219035 2//537566 4//219035 5//734703 24//657108 1//571074 103A//396166 1//571076 10//1006145 22//500612 101//1063445 73//2384 15//2384 72//2384 16//2384 87//321677 A//362729 1//357218 B//362729 2//357218 1//600357 21//610232 22//610232 3//357218 2//520980 4//357218 80//435395 1//32459 4//201912 5A//413210 6//2384 7//2384 2//879424 8//2384 9//2384 1//519620 B//352041 1//812739 2//812739 3//812739 4//812739 5//812739 6//812739 2//786541 1061//853476 1//519805 3//529263 5//617288 Road label 108A//410667 110B//163222 B//410114 1//506068 2//506068 1//235490 2//235490 19//219035 96//863997 18//219035 17//219035 2//392534 B//386035 1//249961 1//571073 21//219035 1//228772 20//219035 1//571075 1//583176 C//386035 16//219035 1//836378 2//836378 3//836378 141//871602 142//871602 143//871602 15//219035 Only GIS data for the areas that are changed by the amendment need to be supplied to the Department Road label 3//32805 14//11900 236//62017 12//11900 15//11900 237//62017 111//1045017 100//1011750 1//958563 9//11900 2//958563 8//11900 1//536294 7//11900 6//11900 Road label 1//231887 2//231887 2//536294 5//11900 9//3035 8//3035 7//3035 23//11900 24//11900 4//11900 3//11900 Road label 1//360663 1//48293 1//48223 1//200633 2//20333 1//720797 1//202892 1//832581 3//20333 4//20333 5//20333 2//202892 4//623381 2//548510 2//202875 1//216678 5//812380 8//3035 1//413575 2//216678 6//812380 B//372666 1//28766 2//1032787 3//1032787 3//3035 4//28766 5//28766 6//28766 1//20165 2//20165 3//20165 4//20165 5//20165 61//1074395 111//805840 2//503375 2//3035 1//708846 1//518345 1//654423 1//572283 D//39072 11//1019253 1//534078 2//853181 5//208135 4//208135 3//208135 2//208135 1//25607 2//25607 1//208135 15//546180 16//546180 1//730010 A//163995 1//420240 2//420240 11//749824 9//27069 7//27069 11//749824 5//27069 1//69845 12//749824 3//27069 11 NSW Department of Planning 2008

for amended zone features LEP_NAME LGA_CODE DATE_ ZONE AMENDMENT PURPOSE LGA Name 9898 15/3/2007 RE1 1 LEP 2007 LGA Name LEP 2007 9898 15/3/2007 SP2 1 School for Additional Permissible Uses amendment LEP_NAME Char80 Name of LEP DATE_ Date Date that amendment data is submitted (dd/mm/yyyy) APU_CODE Char25 Additional Permissible Uses reference code, from the amendment to the written instrument AMENDMENT Integer 4 Amendment for an Additional Permissible Uses amendment LEP_NAME AMENDMENT LGA_CODE DATE_ APU_CODE LGA Name LEP 2007 3 9898 15/3/2007 19 12 NSW Department of Planning 2008

4. Contact For further information or comment please contact: GIS Coordinator NSW Department of Planning 23 33 Bridge Street Sydney Post: GPO Box 39 Sydney NSW 2001 Email: LEP@planning.nsw.gov.au General inquiries: Information Centre NSW Department of Planning Ground floor, 23 33 Bridge Street, Sydney Post: GPO Box 39 Sydney NSW 2001 Tel: 02 9228 6333 Fax: 02 9228 6555 Email: information@planning.nsw.gov.au Web: www.planning.nsw.gov.au 13 NSW Department of Planning 2008