<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20210115</CreaDate>
<CreaTime>11105600</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<ArcGISstyle>ISO 19139 Metadata Implementation Specification</ArcGISstyle>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="FALSE">qld_postcode_boundaries</itemName>
<nativeExtBox>
<westBL Sync="TRUE">137.502675</westBL>
<eastBL Sync="TRUE">153.551940</eastBL>
<southBL Sync="TRUE">-29.179266</southBL>
<northBL Sync="TRUE">-9.087991</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<imsContentType>002</imsContentType>
</itemProps>
<coordRef>
<type Sync="TRUE">Geographic</type>
<geogcsn Sync="TRUE">GCS_GDA_1994</geogcsn>
<csUnits Sync="TRUE">Angular Unit: Degree (0.017453)</csUnits>
<peXml Sync="TRUE">&lt;GeographicCoordinateSystem xsi:type='typens:GeographicCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.1.0'&gt;&lt;WKT&gt;GEOGCS[&amp;quot;GCS_GDA_1994&amp;quot;,DATUM[&amp;quot;D_GDA_1994&amp;quot;,SPHEROID[&amp;quot;GRS_1980&amp;quot;,6378137.0,298.257222101]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433],AUTHORITY[&amp;quot;EPSG&amp;quot;,4283]]&lt;/WKT&gt;&lt;XOrigin&gt;-400&lt;/XOrigin&gt;&lt;YOrigin&gt;-400&lt;/YOrigin&gt;&lt;XYScale&gt;1111948722.2222199&lt;/XYScale&gt;&lt;ZOrigin&gt;0&lt;/ZOrigin&gt;&lt;ZScale&gt;1&lt;/ZScale&gt;&lt;MOrigin&gt;0&lt;/MOrigin&gt;&lt;MScale&gt;1&lt;/MScale&gt;&lt;XYTolerance&gt;8.98315284119521e-09&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.001&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.001&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;LeftLongitude&gt;-180&lt;/LeftLongitude&gt;&lt;WKID&gt;4283&lt;/WKID&gt;&lt;LatestWKID&gt;4283&lt;/LatestWKID&gt;&lt;/GeographicCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<SyncDate>20250710</SyncDate>
<SyncTime>09454100</SyncTime>
<ModDate>20250710</ModDate>
<ModTime>09454100</ModTime>
<ArcGISProfile>ISO19139</ArcGISProfile>
<locales>
<locale country="" language="eng"/>
</locales>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
</Esri>
<Binary/>
<mdFileID>CD56EF37-B23E-4AAF-8FA6-88B04BCE67D0</mdFileID>
<mdLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="AUS"/>
</mdLang>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<mdContact>
<rpIndName>Natural Resources and Mines, Manufacturing, Regional and Rural Development Principal Spatial Information Officer</rpIndName>
<rpOrgName>Department of Natural Resources and Mines, Manufacturing, Regional and Rural Development</rpOrgName>
<rpPosName>Principal Spatial Information Officer</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum tddtty="">(07) 3330 4738</voiceNum>
</cntPhone>
<cntAddress addressType="">
<eMailAdd>SISDTopoDataManagement@resources.qld.gov.au</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdDateSt Sync="TRUE">20250710</mdDateSt>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distFormat>
<formatName Sync="TRUE">Enterprise Geodatabase Feature Class</formatName>
<formatVer>1</formatVer>
</distFormat>
</distInfo>
<dataIdInfo>
<idCitation>
<resTitle>Postcode boundaries - Queensland</resTitle>
<date>
<pubDate>2018-08-27T00:00:00</pubDate>
<reviseDate>2025-05-19T00:00:00</reviseDate>
</date>
<citRespParty>
<rpIndName>Natural Resources and Mines, Manufacturing, Regional and Rural Development, NR, SI, ED</rpIndName>
<rpOrgName>Department of Natural Resources and Mines, Manufacturing, Regional and Rural Development</rpOrgName>
<rpPosName>Executive Director, Spatial Information</rpPosName>
<role>
<RoleCd value="002"/>
</role>
</citRespParty>
<citRespParty>
<rpIndName>Natural Resources and Mines, Manufacturing, Regional and Rural Development, Georesources, SI, SD, MAN Geospatial Data</rpIndName>
<rpOrgName>Department of Natural Resources and Mines, Manufacturing, Regional and Rural Development</rpOrgName>
<rpPosName>Manager, Spatial Data, Spatial Information</rpPosName>
<role>
<RoleCd value="001"/>
</role>
</citRespParty>
<citRespParty>
<rpIndName>Natural Resources and Mines, Manufacturing, Regional and Rural Development, Georesources, SI, SD, MAN Topographic Data Management</rpIndName>
<rpOrgName>Department of Natural Resources and Mines, Manufacturing, Regional and Rural Development</rpOrgName>
<rpPosName>Manager, Spatial Data, Spatial Information</rpPosName>
<role>
<RoleCd value="008"/>
</role>
</citRespParty>
<citRespParty>
<rpIndName>PSMA Australia</rpIndName>
<rpOrgName>PSMA Australia Limited</rpOrgName>
<rpPosName>Product Support</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(02) 6260 9000</voiceNum>
</cntPhone>
<cntAddress>
<eMailAdd>support@psma.com.au</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpIndName>Natural Resources and Mines, Manufacturing, Regional and Rural Development, Georesources, SI, SD, Principal Spatial Information Officer</rpIndName>
<rpOrgName>Department of Natural Resources and Mines, Manufacturing, Regional and Rural Development</rpOrgName>
<rpPosName>Principal Spatial Information Officer</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum tddtty="">(07) 3330 4738</voiceNum>
</cntPhone>
<cntAddress addressType="">
<eMailAdd>SISDTopoDataManagement@resources.qld.gov.au</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
</idCitation>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;The Postcode Boundaries dataset is the definitive set of postcodes developed by Australia Post and Geoscape (formally PSMA) Australia.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idPurp>This dataset provides the definitive postcode dataset for the entire Queensland extent – see Extent below. It has been developed jointly by Geoscape (formally PSMA) Australia and Australia Post to support the spatial analysis and visualisation of postcode areas.</idPurp>
<idCredit>© Geoscape (formally PSMA) Australia Limited 2025
www.geoscape.com.au/legal/data-copyright-and-disclaimer/</idCredit>
<idStatus>
<ProgCd value="001"/>
</idStatus>
<idPoC>
<rpIndName>PSMA Australia</rpIndName>
<rpOrgName>PSMA Australia Limited</rpOrgName>
<rpPosName>Product Support</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum tddtty="">(02) 6260 9000</voiceNum>
</cntPhone>
<cntAddress addressType="">
<eMailAdd>support@psma.com.au</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="006"/>
</role>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="009"/>
</maintFreq>
<maintNote>Geoscape Australia releases updates to all datasets every quarter in the months of February, May, August and November. The Postcode Boundaries dataset is updated as deemed necessary by Australia Post. Geoscape Australia’s data maintenance occurs for existing objects with changed geometry and/or attributes, as well as data for new objects within the release time period.</maintNote>
<maintCont>
<rpIndName>Resources, Senior Spatial Information Officer</rpIndName>
<rpOrgName>Department of Resources</rpOrgName>
<rpPosName>Senior Spatial Information Officer</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(07) 3330 4738</voiceNum>
</cntPhone>
<cntAddress>
<eMailAdd>SISDTopoDataManagement@resources.qld.gov.au</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</maintCont>
</resMaint>
<placeKeys>
<thesaName>
<resTitle>ANZLIC Search Words</resTitle>
<date>
<pubDate>2007-08-01</pubDate>
</date>
</thesaName>
<keyword>Queensland</keyword>
</placeKeys>
<themeKeys>
<thesaName>
<resTitle>ANZLIC Search Words</resTitle>
<date>
<pubDate>2007-08-01</pubDate>
</date>
</thesaName>
<keyword>BOUNDARIES</keyword>
</themeKeys>
<themeKeys>
<thesaName>
<resTitle>Common Search Terms</resTitle>
<date>
<pubDate>2016-02-05</pubDate>
</date>
</thesaName>
<keyword>postcode</keyword>
</themeKeys>
<searchKeys>
<keyword>Queensland</keyword>
<keyword>BOUNDARIES</keyword>
<keyword>postcode</keyword>
</searchKeys>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;Users must acknowledge that the Geoscape (formally PSMA) Data does not on its own constitute Personal Information. The user agrees: • not to do any act or engage in any practice using the Geoscape (formally PSMA) Data or a value added reseller product (VAR Product) that would breach the Privacy Act 1988 (Cth); • to comply with any direction of Geoscape (formally PSMA) Distribution or Geoscape (formally PSMA) to observe any recommendation of the Privacy Commissioner relating to acts or practices of the user that the Privacy Commissioner considers to be in breach of the obligations in this clause.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<resConst>
<LegConsts>
<useLimit>Geoscape Australia Limited</useLimit>
<useConsts>
<RestrictCd value="006"/>
</useConsts>
</LegConsts>
</resConst>
<resConst>
<LegConsts>
<useLimit>Original information restricted to within Queensland Government agencies, but value-added products can be produced and distributed outside the Department</useLimit>
<useConsts>
<RestrictCd value="005"/>
</useConsts>
</LegConsts>
</resConst>
<resConst>
<SecConsts>
<class>
<ClasscationCd value="002"/>
</class>
<userNote>Restricted to within Queensland Government agencies. Data is available for use by Queensland Government agencies under a signed license agreement. Data is available through physical supply and may be made available to registered users via web delivery tools, for example, through an access controlled internet site like the NRM RIS Portal.</userNote>
<classSys>ISO 19115 (mapped from Qld Govt Information Security Standard IS18)</classSys>
</SecConsts>
</resConst>
<aggrInfo>
<aggrDSIdent>
<identAuth>
<resTitle>Spatial Information Resource (SIR) Feature Class</resTitle>
<date>
<pubDate>2018-08-27</pubDate>
<reviseDate>2023-08-31</reviseDate>
</date>
</identAuth>
<identCode>PROP.QLD_POSTCODE_BOUNDARIES</identCode>
</aggrDSIdent>
<assocType>
<AscTypeCd value="004"/>
</assocType>
</aggrInfo>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<dataLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="AUS"/>
</dataLang>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<envirDesc Sync="FALSE">Esri ArcGIS 13.1.5.41833</envirDesc>
<dataExt>
<exDesc>Bounding Box</exDesc>
</dataExt>
<dataExt>
<geoEle>
<GeoBndBox>
<exTypeCode>true</exTypeCode>
<westBL>137.502675</westBL>
<eastBL>153.55185</eastBL>
<southBL>-29.179266</southBL>
<northBL>-9.087991</northBL>
</GeoBndBox>
</geoEle>
</dataExt>
<suppInfo>The Postcode Boundaries dataset is the definitive set of postcodes developed by Australia Post and Geoscape Australia. It includes two data layers, postcode boundaries (polygon data) and postcode centroids (point data).
Postcodes are allocated to geographic areas to facilitate the efficient processing and delivery of mail to customers. The current four-digit numeric postcode system was introduced in 1967 in association with the first mechanised mail processing centre in Australia. The Postcode Boundaries in most cases are an aggregation of Geoscape’s Suburbs/Localities boundaries for each postcode.
The government land administration agencies in each state and territory are responsible for gazetting locality names and boundary positions. Postcodes are commonly allocated to localities officially gazetted by land agencies. In the majority of circumstances, a postcode covers an area comprising of more than one locality. The decision as to whether a new postcode or an existing postcode is to be allocated to a locality is based on operational efficiency. Issues that underpin the decision are critically analysed; these include the configuration of the Australia Post network, transportation connections and delivery arrangements.
</suppInfo>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">137.502675</westBL>
<eastBL Sync="TRUE">153.551940</eastBL>
<northBL Sync="TRUE">-9.087991</northBL>
<southBL Sync="TRUE">-29.179266</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<tpCat>
<TopicCatCd value="003"/>
</tpCat>
</dataIdInfo>
<mdMaint>
<maintFreq>
<MaintFreqCd value="009"/>
</maintFreq>
</mdMaint>
<mdConst>
<SecConsts>
<useLimit>Public</useLimit>
<class>
<ClasscationCd value="001"/>
</class>
<classSys>Metadata Access Level</classSys>
</SecConsts>
</mdConst>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<report dimension="" type="DQCompOm">
<measDesc>Completeness is an assessment of the extent and range of the dataset with regard to completeness of coverage, completeness of classification and completeness of verification.
Attribute completeness
All attributes for each object are populated.
Temporal accuracy is applicable to most of the current release.
Quality scope
Polygon and point geometry accuracy and attribute accuracy for all included areas.</measDesc>
<measResult>
<ConResult>
<conSpec>
<resTitle>Geoscape data capture process</resTitle>
<date>
<pubDate>2017-01-24</pubDate>
</date>
</conSpec>
<conExpl>The data is to a standard determined as fit for the purpose for which it was collected.</conExpl>
<conPass>true</conPass>
</ConResult>
</measResult>
</report>
<report dimension="" type="DQConcConsis">
<measDesc>Logical consistency is a measure of the degree to which data complies with the technical specification. The allowable error in logical consistency previously ranged from 3% to 5%. The test procedures are a mixture of software scripts and onscreen visual checks.
The data structure has been tested for conformance with the data model. The following have been tested and confirmed to conform:
• File names
• Attribute names
• Attribute lengths
• Attribute types
• Attribute domains
• Attribute order in file
• Object type
• Compulsory attributes populated.
The data been thoroughly tested and is free of the following topological errors:
• Pseudo nodes
• Overlaps
• Bowties and other self intersections
• Duplicate features
• Incomplete polygons
• Gaps (voids and slivers) between polygons
• Object continuity at sheet edges and borders.</measDesc>
<measResult>
<ConResult>
<conSpec>
<resTitle>Geoscape data capture process</resTitle>
<date>
<pubDate>2017-01-24</pubDate>
</date>
</conSpec>
<conExpl>The data is to a standard determined as fit for the purpose for which it was collected.</conExpl>
<conPass>true</conPass>
</ConResult>
</measResult>
</report>
<report dimension="" type="DQAbsExtPosAcc">
<measDesc>Positional accuracy is an assessment of the closeness of the location of the spatial objects in relation to their true positions on the earth’s surface.
The positional accuracy includes:
• a horizontal accuracy assessment
• a vertical accuracy assessment
The horizontal and vertical positional accuracy are the assessed accuracy after all transformations have been carried out.
Relative spatial accuracy of the Administrative Boundaries dataset (i.e. Suburbs/Localities) used in the construction of postcodes reflects that of the source data.
Note
The accuracy of geometric representation is given by the difference between the position of the geometric representation of an object and its absolute position, as measured with respect to the geodetic network.</measDesc>
<measResult>
<ConResult>
<conSpec>
<resTitle>Geoscape data capture process</resTitle>
<date>
<pubDate>2017-01-24</pubDate>
</date>
</conSpec>
<conExpl>The data is to a standard determined as fit for the purpose for which it was collected.</conExpl>
<conPass>true</conPass>
</ConResult>
</measResult>
</report>
<report dimension="" type="DQNonQuanAttAcc">
<measDesc>Attribute accuracy is an assessment of the reliability of values assigned to features in the dataset in relation to their true ‘real world’ values.
Key attributes (postcode and the unique identifier) have a high degree of accuracy in the order of 99.09% and are reflective of the operational needs of Australia Post. Other attributes derived from the processing of supplied data may have a lower degree of accuracy but less than previously released data. The postcode allocated to an area may not be the same postcode as published by Australia Post through their website or other sources, as the postcode is some cases is based on the most commonly used postcode for addresses in a given area. All attribute accuracies are dependent on the data accuracy supplied to Geoscape Australia.
For this product, feature and attribute accuracy is a measure of the degree to which the features and attribute values of spatial objects agree with the information on the source material. The allowable error in attribute accuracy was previously up to 5%.
A precise attribute accuracy assessment may not always be possible. In these cases an intuitive estimate of the expected attribute accuracy or the likely maximum error based on previous experience is acceptable.
The postcode allocated to a gazetted suburb/locality is the most commonly used postcode, in a small number of cases the postcode is different to the postcode published by Australia Post on their website. These cases are due to changes to locality boundary or locality name, where the postcode remains the same for delivery purposes.</measDesc>
<measResult>
<ConResult>
<conSpec>
<resTitle>Geoscape data capture process</resTitle>
<date>
<pubDate>2017-01-24</pubDate>
</date>
</conSpec>
<conExpl>The data is to a standard determined as fit for the purpose for which it was collected.</conExpl>
<conPass>true</conPass>
</ConResult>
</measResult>
</report>
<report dimension="" type="DQTopConsis">
<measDesc>Topological consistency is the measure of how features spatially relate to other features within and across themes. Topological inconsistencies are identified using a combination of automated rules, and visual analysis. Where topological inconsistencies are identified they are notified back to the supplier organisation for remediation at source. Some minor topological inconsistencies are corrected during product processing using automated rules. The level of topological consistency is dependent on the data supplied to Geoscape.
During product processing there is no attempt to enforce topological consistency across state and territory borders. Cross border topological consistency is a complex issue and Geoscape continues to engage the Federal, State, and Territory governments of Australia to improve the topological consistency of spatial datasets across these borders.</measDesc>
<measResult>
<ConResult>
<conSpec>
<resTitle>Geoscape data capture process</resTitle>
<date>
<pubDate>2020-11-01</pubDate>
</date>
</conSpec>
<conExpl>The data is to a standard determined as fit for the purpose for which it was collected.</conExpl>
<conPass>true</conPass>
</ConResult>
</measResult>
</report>
<dataLineage>
<statement>All suburb/locality data used for the polygon geometry in postcodes is captured by the state and territory governments through appropriate agencies. The digital suburb/locality boundaries and their legal identifiers have been derived from the cadastre data from each Australian state and territory jurisdiction.
The postcodes are provided by Australia Post and are required to facilitate the efficient processing and delivery of mail to customers. Any areas that do not have postcode boundaries (e.g. NW South Australia) are consistent with the coverage of gazetted suburbs/localities boundaries. None of the gazetted suburb/locality boundaries have been changed with the exception of the suburb of Melbourne, which is split into two separate areas for the allocation of different postcodes (3000 and 3004).
A decision as to whether a new postcode or an existing postcode is to be allocated to a suburb/locality is based on operational efficiency. Issues that underpin the decision are critically analysed; these include the configuration of the Australia Post network, transportation connections and delivery arrangements. Australia Post will only allocate a postcode where there are deliveries within an area and where there is no conflict with the allocation of other postcodes by Australia Post. It is ultimately Australia Post’s decision on whether an area is allocated a postcode. Australia Post will allocate ‘NA’ as a postcode where they are unable to resolve the allocation of a postcode to a gazetted suburb/locality boundary, even though they may have identified a postcode for the name (e.g. GALIWINKU, NT). The postcodes for Australia Post postal services that use specific suburbs/localities, such as Post Office Boxes (e.g. EAST PERTH, WA 6892) are not captured in the Postcode Boundaries product.</statement>
</dataLineage>
</dqInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="qld_postcode_boundaries">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">436</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<refSysInfo>
<RefSystem dimension="">
<refSysID>
<identCode code="4283"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">6.5(3.0.1)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<eainfo>
<detailed Name="qld_postcode_boundaries">
<enttyp>
<enttypl Sync="FALSE">qld_postcode_boundaries</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">436</enttypc>
<enttypd>Postcode Boundaries Product Description</enttypd>
<enttypds>Geoscape Australia</enttypds>
</enttyp>
<attr>
<attrlabl Sync="TRUE">OBJECTID</attrlabl>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Internal feature number.</attrdef>
<attrdefs Sync="TRUE">ESRI</attrdefs>
<attrdomv>
<udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape</attrlabl>
<attalias Sync="TRUE">Shape</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Feature geometry.</attrdef>
<attrdefs Sync="TRUE">ESRI</attrdefs>
<attrdomv>
<udom Sync="TRUE">Coordinates defining the features.</udom>
</attrdomv>
</attr>
<subtype>
<stname Sync="TRUE">Connector</stname>
<stcode Sync="TRUE">1</stcode>
<stfield>
<stfldnm Sync="TRUE">FEATURETYPE</stfldnm>
<stflddv Sync="TRUE">Connector</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">TYPE</stfldnm>
<stflddv Sync="TRUE">2</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PERENNIALITY</stfldnm>
<stflddd>
<domname Sync="TRUE">dm_PerennialityMultScle</domname>
<domdesc Sync="TRUE">Perennialty which may be populated</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Duplicate</splttype>
<domfldtp Sync="TRUE">String</domfldtp>
<domowner Sync="TRUE">NAT</domowner>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">HIERARCHY</stfldnm>
<stflddd>
<domname Sync="TRUE">dm_HierarchyMultScle</domname>
<domdesc Sync="TRUE">Hierarchy which may be populated</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Duplicate</splttype>
<domfldtp Sync="TRUE">String</domfldtp>
<domowner Sync="TRUE">NAT</domowner>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">UPPERSCALE</stfldnm>
<stflddd>
<domname Sync="TRUE">dm_UpperScaleMultScle</domname>
<domdesc Sync="TRUE">Upper Scale of Data Utilisation</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Duplicate</splttype>
<domfldtp Sync="TRUE">Integer</domfldtp>
<domowner Sync="TRUE">BUILT</domowner>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">USCERTAINTY</stfldnm>
<stflddd>
<domname Sync="TRUE">dm_USCertaintyMultScle</domname>
<domdesc Sync="TRUE">Upper Scale Certainity</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Duplicate</splttype>
<domfldtp Sync="TRUE">String</domfldtp>
<domowner Sync="TRUE">BUILT</domowner>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOL100K</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOL100K_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOL250K</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOL250K_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOLWAC1MIL</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOLWAC1Mil_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOL2_5MIL</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOL2_5Mil_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOL5MIL</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOL5Mil_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOL10MIL</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOL10Mil_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
</subtype>
<subtype>
<stname Sync="TRUE">Watercourse</stname>
<stcode Sync="TRUE">2</stcode>
<stfield>
<stfldnm Sync="TRUE">FEATURETYPE</stfldnm>
<stflddv Sync="TRUE">Watercourse</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">TYPE</stfldnm>
<stflddv Sync="TRUE">2</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PERENNIALITY</stfldnm>
<stflddd>
<domname Sync="TRUE">dm_PerennialityMultScle</domname>
<domdesc Sync="TRUE">Perennialty which may be populated</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Duplicate</splttype>
<domfldtp Sync="TRUE">String</domfldtp>
<domowner Sync="TRUE">NAT</domowner>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">HIERARCHY</stfldnm>
<stflddd>
<domname Sync="TRUE">dm_HierarchyMultScle</domname>
<domdesc Sync="TRUE">Hierarchy which may be populated</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Duplicate</splttype>
<domfldtp Sync="TRUE">String</domfldtp>
<domowner Sync="TRUE">NAT</domowner>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">UPPERSCALE</stfldnm>
<stflddd>
<domname Sync="TRUE">dm_UpperScaleMultScle</domname>
<domdesc Sync="TRUE">Upper Scale of Data Utilisation</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Duplicate</splttype>
<domfldtp Sync="TRUE">Integer</domfldtp>
<domowner Sync="TRUE">BUILT</domowner>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">USCERTAINTY</stfldnm>
<stflddd>
<domname Sync="TRUE">dm_USCertaintyMultScle</domname>
<domdesc Sync="TRUE">Upper Scale Certainity</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Duplicate</splttype>
<domfldtp Sync="TRUE">String</domfldtp>
<domowner Sync="TRUE">BUILT</domowner>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOL100K</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOL100K_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOL250K</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOL250K_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOLWAC1MIL</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOLWAC1Mil_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOL2_5MIL</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOL2_5Mil_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOL5MIL</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOL5Mil_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOL10MIL</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOL10Mil_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
</subtype>
<subtype>
<stname Sync="TRUE">DEMConnector</stname>
<stcode Sync="TRUE">3</stcode>
<stfield>
<stfldnm Sync="TRUE">FEATURETYPE</stfldnm>
<stflddv Sync="TRUE">DEM Connector</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">TYPE</stfldnm>
<stflddv Sync="TRUE">2</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PERENNIALITY</stfldnm>
<stflddd>
<domname Sync="TRUE">dm_PerennialityMultScle</domname>
<domdesc Sync="TRUE">Perennialty which may be populated</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Duplicate</splttype>
<domfldtp Sync="TRUE">String</domfldtp>
<domowner Sync="TRUE">NAT</domowner>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">HIERARCHY</stfldnm>
<stflddd>
<domname Sync="TRUE">dm_HierarchyMultScle</domname>
<domdesc Sync="TRUE">Hierarchy which may be populated</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Duplicate</splttype>
<domfldtp Sync="TRUE">String</domfldtp>
<domowner Sync="TRUE">NAT</domowner>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">UPPERSCALE</stfldnm>
<stflddd>
<domname Sync="TRUE">dm_UpperScaleMultScle</domname>
<domdesc Sync="TRUE">Upper Scale of Data Utilisation</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Duplicate</splttype>
<domfldtp Sync="TRUE">Integer</domfldtp>
<domowner Sync="TRUE">BUILT</domowner>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">USCERTAINTY</stfldnm>
<stflddd>
<domname Sync="TRUE">dm_USCertaintyMultScle</domname>
<domdesc Sync="TRUE">Upper Scale Certainity</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Duplicate</splttype>
<domfldtp Sync="TRUE">String</domfldtp>
<domowner Sync="TRUE">BUILT</domowner>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOL100K</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOL100K_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOL250K</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOL250K_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOLWAC1MIL</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOLWAC1Mil_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOL2_5MIL</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOL2_5Mil_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOL5MIL</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOL5Mil_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">SYMBOL10MIL</stfldnm>
<stflddd>
<domname Sync="TRUE">SYMBOL10Mil_WatercourseLines_Rules</domname>
<domdesc Sync="TRUE">Representation rules</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">NAT</domowner>
<domfldtp Sync="TRUE">Integer</domfldtp>
</stflddd>
</stfield>
</subtype>
<attr>
<attrlabl Sync="TRUE">PC_PLY_PID</attrlabl>
<attalias Sync="TRUE">PC_PLY_PID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">15</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The Persistent Identifier is unique to the real world feature this record represents.</attrdef>
<attrdefs>Geoscape Australia</attrdefs>
<attrdomv>
<udom>The Persistent Identifier is unique to the real world feature this record represents.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">DT_CREATE</attrlabl>
<attalias Sync="TRUE">DT_CREATE</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Date this record was created.</attrdef>
<attrdefs>Geoscape Australia</attrdefs>
<attrdomv>
<udom>Date this record was created.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">DT_RETIRE</attrlabl>
<attalias Sync="TRUE">DT_RETIRE</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Date this record was retired.</attrdef>
<attrdefs>Geoscape Australia</attrdefs>
<attrdomv>
<udom>Date this record was retired.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">PC_PID</attrlabl>
<attalias Sync="TRUE">PC_PID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">15</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>postcode persistent id</attrdef>
<attrdefs>Geoscape Australia</attrdefs>
<attrdomv>
<udom>postcode persistent id</udom>
</attrdomv>
</attr>
<subtype>
<stname Sync="TRUE">Culvert</stname>
<stcode Sync="TRUE">4</stcode>
<stfield>
<stfldnm Sync="TRUE">FEATURETYPE</stfldnm>
<stflddv Sync="TRUE">Culvert</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">TYPE</stfldnm>
<stflddv Sync="TRUE">2</stflddv>
</stfield>
</subtype>
<attr>
<attrlabl Sync="TRUE">st_area(shape)</attrlabl>
<attalias Sync="TRUE">st_area(shape)</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">st_perimeter(shape)</attrlabl>
<attalias Sync="TRUE">st_perimeter(shape)</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
</detailed>
</eainfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="qld_postcode_boundaries">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="4"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">436</efeacnt>
<spindex Sync="TRUE">FALSE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
</metadata>
