Postcode Boundaries¶
Disclaimer
Overview¶
The Postcodes Boundaries dataset is Australia’s most definitive set of Postcodes developed by Australia Post and Geoscape Australia. The Postcode Boundaries dataset represents postcodes as both a polygon (postcode boundaries) and a point (postcode centroid). For more information, please refer to the Postcode Boundaries Product Description. Geoscape welcomes your feedback on the Postcode Boundaries product. We also publish regular product development updates on our website ( www.geoscape.com.au ).
Release Summary¶
This product was released to customers on 19 February 2024 with data extracted on 05 February 2024.
This release is a full national data population for the Postcode Boundaries product, described by the Postcode Boundaries Product Description.
Any issues that have been identified for this release are described in the Issues section.
Change Notifications¶
Esri Shapefile width increase - Cancelled¶
In the previous release report, we mentioned that the width of numeric fields within Esri Shapefiles would increase by one for this current release. A recent bug fix in our packaging application has been applied to make this change not necessary. No change to Shapefile field widths has been applied for this release.
Removal of the ‘Documents’ folder from data packages¶
From November 2023, Geoscape will be progressively moving product descriptions, guides and reports online to https://docs.geoscape.com.au
Commencing with the May 2024 release, data packages will no longer include the Documents folder.
Updates¶
General¶
The QA process highlighted the existence of multi-part Postcode polygons, some of these spanning significant distances.
A small number of gazetted localities were identified that do not currently have postcodes assigned. These will be submitted to postcode allocation and if successful, included in future updates.
A postcode polygon is considered to have changed if its geometry has changed by ‘0.00005’.
A few localities, each of them is serviced by multi-Delivery offices, have not been allocated postcodes, for instance, “Blue mountains National Park” in NSW.
New South Wales¶
Area of postcode 2570 significantly increased by inclusion of locality of BURRAGORANG VALLEY
Northern Territory¶
Marine parks near Darwin have not been allocated postcodes. These are non-delivery areas and will only serve to overstate the total area covered by the postcode and any “per square km” statistics generated from them.
Queensland¶
Some localities in QLD are unable to be allocated postcodes at this time. Examples include “Upland”, “Ward” and “Selwyn”.
Marine parks have not been allocated postcodes. These are non-delivery areas and will only serve to overstate the total area covered by the postcode and any “per square km” statistics generated from them.
South Australia¶
As the South Australian land authorities have not gazetted the north-western part of the state there will not be any postcodes generated on locality basis in this area.
Victoria¶
A minor adjustment to northern boundary of DOCKLANDS changed the shape of 3000 and 3008 slightly.
Future Considerations¶
This section outlines enhancements or changes under consideration, but not planned into a specific release. For further details on future initiatives, please contact Geoscape Support.
Western Australia¶
The North-western coastline has excessive detail and may be simplified in a future release. At this time this area is excluded from topology change comparison. Visual inspection indicates minimal changes to this remote region.
Annex A – Release Counts¶
The volume of updates applied in this release is included in the table below.
TABLE |
ACT |
NSW |
NT |
OT |
QLD |
SA |
TAS |
VIC |
WA |
TOTAL |
---|---|---|---|---|---|---|---|---|---|---|
LOCALITY_POSTCODE |
0 |
8 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
8 |
POSTCODE |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
POSTCODE_POINT |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
POSTCODE_POLYGON |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
Note
Edits to the Postcode Points and Postcode Polygons theme are generally geometry recalculations required after the geometry from associated locality boundaries were edited.