======== Overview ======== The Indigenous Structure is the Indigenous framework within the Australian Statistical Geography Standard (ASGS). It is designed by the Australian Bureau of Statistics (ABS) for the collection, analysis and dissemination of Aboriginal and Torres Strait Islander peoples statistical information across Australia. It is updated every 5 years for dissemination of ABS Census data. The structure consists of a nested hierarchy of geographic areas that enable data to be analysed and reported at a range of geographic scales. The ABS ASGS 2026 Indigenous Structure product provides spatial representations of these statistical areas together with the associated identifiers, codes and names required for integration with ABS datasets. --------- Use Cases --------- The ABS ASGS 2026 Indigenous Structure supports a wide range of analytical and operational workflows, including: - Demographic and population analysis - Census data integration - Service delivery planning - Infrastructure planning - Socioeconomic analysis - Government reporting - Research and policy development .. figure:: overview/asgs_structure.png :align: center 2026 ASGS ABS Structures, extracted from the ABS Geography Website `ABS Geography Website `_ Detailed attribute definitions and relationships are provided in the data dictionary and data model. Geoscape Australia welcomes your feedback on our products. We also publish regular updates on the development of our products on the Geoscape website ( `www.geoscape.com.au `_ ). ---------------- Product Version ---------------- 1.0 - Major Version: 1 - Minor Version: 0 --------------------------- Product Version Management --------------------------- Versioning is managed through incrementing when there is a change to the product schema or a significant change in data population, these are described further below: - A schema change can affect a major or minor increment to the versioning. - Additive changes (changes that won’t break customers’ ability to work with the data) will be incremented with a minor version increment, an example is the addition of a new attribute. - Removal of attributes or changing the structure of the schema will enact a major change to identify that this requires the attention of all customers and partners. - Where a significant geography of Australia either has a new population of data for an attribute or is populated from a much higher quality source a minor increment will be applied to the product version. Therefore, the major and minor version will not increment with every data update. Published releases will have a name e.g. ‘May 2025’ and will reference a version of the product e.g. ‘1.0’.