National Postcode Boundaries¶
Disclaimer
Overview¶
The National Postcode Boundaries dataset is Australia’s most definitive set of Postcodes developed by Australia Post and Geoscape Australia. The National Postcode Boundaries dataset represents postcodes as both a polygon (postcode boundaries) and a point (postcode centroid). For more information, please refer to the National Postcode Boundaries Product Description. Geoscape welcomes your feedback on the National 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 17 August 2026 with data extracted on 12 August 2026.
This release is a full national data population for the National Postcode Boundaries product, described by the National Postcode Boundaries Product Description.
Any issues that have been identified for this release are described in the Issues section.
Change Notifications¶
Versioning Update (Starting June 2026)¶
Beginning June 2026, all data products will transition to a standardised versioning format: MAJOR-MINOR-EXTRACT (e.g., 004-000-001). This approach provides a clear and consistent structure, making it easier for users to identify product versions and understand update levels at a glance. The change is intended to improve transparency, reduce ambiguity, and support more efficient integration and usage of our data products.
The Postcode Boundaries product will transition to the new versioning format in the November 2026 Release.
Implementation of New Zip File Naming and Packaging Standards (Starting November 2026)¶
As part of ongoing improvements to product consistency and packaging standards, updates to zip file naming conventions and internal packaging structure will be implemented, starting in November 2026 for Postcode Boundaries.
Zip File Naming
Two standard naming patterns will be used, depending on whether an extract contains spatial information:
Spatial Tables:
{PRODUCT-NAME}_{RELEASE YYYYMM}_{REGION}_{CRS}_{FORMAT}_{VERSION MAJOR-MINOR-EXTRACT}.zip
Aspatial (Insights) Tables:
{PRODUCT-NAME}_{RELEASE YYYYMM}_{REGION}_NODATUM_{FORMAT}_{VERSION MAJOR-MINOR-EXTRACT}.zip
Packaging Structure
From the November 2026 release, we will update the folder structure in the Postcode Boundaries product packages. Currently, we provide a contents.txt file and a number of internal folders. The .ZIP file packages will be changed to only contain data files. We intend to apply this change to simplify accessing the data.
Product File Changes
To align the naming of the Australia region product files with the state and territory files, an 'australia_' prefix will be added to the table and layer names for November 2026.
For example:
August 2026 > November 2026
file name:
postcode_boundaries.gdb>australia_postcode_boundaries.gdblayer name:
postcode_boundaries>australia_postcode_boundariesIn GeoJSON, JSON and PSV files, date fields will be changed to be represented as YYYY-MM-DD format (e.g. 2026-03-31) where currently they are provided in DD-MM-YYYY format (e.g. 31-03-2026).
File and Attribute Naming Changes
As part of the standardisation of file naming conventions, file names and attribute names will be updated across the supported spatial formats for November 2026. GDB, GeoJSON, GPKG, SHP and TAB file names and attribute names will use lowercase.
In addition to this, authority table names will be simplified and a region prefix will be added. For example, for the zip file package relating to ACT, the previous table name of ‘Authority_Code_POSTCODE_CLASS_AUT_shp’ will be changed to be ‘act_postcode_class_aut’.
These changes ensure consistent file and attribute naming across all products, reduces complexity, and supports improved automation and user experience.
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.
Some localities serviced by multiple delivery offices have not been assigned postcodes. Examples include Royal National Park and Blue Mountains National Park in NSW.
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¶
Gulf of Carpentaria collapsed to the islands and coastline, dramatically reducing the size of the N/A polygon
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.
Western Australia¶
Remote empty locality of Kupartiya changed to 6770 automatically. Will likely change to 6765 once some address points are added.
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 |
2 |
0 |
0 |
4 |
0 |
0 |
0 |
1 |
7 |
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.