<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20231128</CreaDate>
<CreaTime>19520300</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="FALSE">qld_wwbw</itemName>
<nativeExtBox>
<westBL Sync="TRUE">137.993377</westBL>
<eastBL Sync="TRUE">153.533167</eastBL>
<southBL Sync="TRUE">-29.179224</southBL>
<northBL Sync="TRUE">-9.243053</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<imsContentType export="False">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;999999999.99999988&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;10000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;10000&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>20251127</SyncDate>
<SyncTime>16303700</SyncTime>
<ModDate>20251127</ModDate>
<ModTime>16303700</ModTime>
<ArcGISFormat>1.0</ArcGISFormat>
<ArcGISstyle>ISO 19139 Metadata Implementation Specification</ArcGISstyle>
<ArcGISProfile>ISO19139</ArcGISProfile>
<locales>
<locale country="" language="eng"/>
</locales>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
</Esri>
<Binary>
</Binary>
<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>Fish Data Coordinator</rpIndName>
<rpOrgName>Department of Primary Industries</rpOrgName>
<rpPosName>Fisheries and Forestry, Fisheries, Reporting Information and Digital Solutions (RIDS)</rpPosName>
<rpCntInfo>
<cntAddress addressType="">
<city>Brisbane</city>
<adminArea>Queensland</adminArea>
<postCode>4000</postCode>
<country>AU</country>
<eMailAdd>fishdatacoordinator@dpi.qld.gov.au</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdDateSt Sync="TRUE">20251127</mdDateSt>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distFormat>
<formatName Sync="TRUE">Enterprise Geodatabase Feature Class</formatName>
<formatVer>10</formatVer>
</distFormat>
<distributor>
<distorCont>
<rpIndName>DNRMMRRD, Open Data</rpIndName>
<rpOrgName>Department of Natural Resources and Mines, Manufacturing and Regional and Rural Development</rpOrgName>
<rpPosName>Senior Product Officer</rpPosName>
<rpCntInfo>
<cntAddress addressType="">
<eMailAdd>opendata@resources.qld.gov.au</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="005"/>
</role>
</distorCont>
<distorOrdPrc>
<ordInstr>Open the Queensland Spatial Catalogue (QSpatial).
Select the large SEARCH button and all available records are displayed.
Select one of the four filter options provided and then the further options within the filter.
The resultant search is then displayed.
Select your record and complete the order.</ordInstr>
</distorOrdPrc>
<distorFormat>
<formatName>Queensland Spatial Catalogue</formatName>
<formatVer>2.0</formatVer>
<formatSpec>SHP, TAB, FGDB, KMZ</formatSpec>
</distorFormat>
<distorTran>
<unitsODist>Whole of dataset, although clipped areas are available through QSpatial.</unitsODist>
</distorTran>
</distributor>
</distInfo>
<dataIdInfo>
<idCitation>
<resTitle>Queensland waterways for waterway barrier works</resTitle>
<resAltTitle>Queensland waterways for waterway barrier works</resAltTitle>
<date>
<createDate>2025-10-08T00:00:00</createDate>
</date>
<citRespParty>
<rpIndName>DPI, Fisheries and Forestry, Executive Director Fisheries</rpIndName>
<rpOrgName>Department of Primary Industries</rpOrgName>
<rpPosName>Executive Director, Fisheries</rpPosName>
<role>
<RoleCd value="002"/>
</role>
</citRespParty>
<citRespParty>
<rpIndName>Fish Data Coordinator</rpIndName>
<rpOrgName>Department of Primary Industries</rpOrgName>
<rpPosName>Fisheries and Forestry, Fisheries, Reporting Information and Digital Solutions (RIDS)</rpPosName>
<rpCntInfo>
<cntAddress addressType="">
<city>Brisbane</city>
<adminArea>Queensland</adminArea>
<postCode>4000</postCode>
<country>AU</country>
<eMailAdd>fishdatacoordinator@dpi.qld.gov.au</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</citRespParty>
<citRespParty>
<rpIndName>Fish Data Coordinator</rpIndName>
<rpOrgName>DPI, Fisheries and Forestry</rpOrgName>
<rpPosName>Executive Director, Fisheries</rpPosName>
<rpCntInfo>
<cntAddress addressType="">
<city>Brisbane</city>
<adminArea>Queensland</adminArea>
<postCode>4000</postCode>
<country>AU</country>
<eMailAdd>fishdatacoordinator@dpi.qld.gov.au</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="001"/>
</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;Version 3.1 (2025). This dataset contains waterway lines covering the state of Queensland. To aid the user, waterways are depicted as a multi-coloured waterway network, from their upstream limit down to their tidal or wetland conclusion. The colour of a waterway is primarily used to guide users to applicable accepted development work types.This dataset must be used in conjunction with the user guide: https://www.publications.qld.gov.au/dataset/fisheries-queensland-impact-assessment-and-management-resources/resource/a465f32e-f5d5-4f53-bdcf-6962f887c254&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idPurp>The waterways displayed help identify waterways defined by the Fisheries Act 1994 and also the fisheries interest in waterways providing for fish passage (a matter of State environmental significance under the Environmental Offsets Act 2014).</idPurp>
<idCredit>© State of Queensland (Department of Primary Industries) 2025</idCredit>
<idStatus>
<ProgCd value="004"/>
</idStatus>
<idPoC>
<rpIndName>Fish Data Coordinator</rpIndName>
<rpOrgName>DPI, Fisheries and Forestry</rpOrgName>
<rpPosName>Executive Director, Fisheries</rpPosName>
<rpCntInfo>
<cntAddress addressType="">
<city>Brisbane</city>
<adminArea>Queensland</adminArea>
<postCode>4000</postCode>
<country>AU</country>
<eMailAdd>fishdatacoordinator@dpi.qld.gov.au</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="001"/>
</role>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="009"/>
</maintFreq>
<maintCont>
<rpIndName>Fish Data Coordinator</rpIndName>
<rpOrgName>Department of Primary Industries</rpOrgName>
<rpPosName>Fisheries and Forestry, Fisheries, Reporting Information and Digital Solutions (RIDS)</rpPosName>
<rpCntInfo>
<cntAddress addressType="">
<city>Brisbane</city>
<adminArea>Queensland</adminArea>
<country>AU</country>
<eMailAdd>fishdatacoordinator@dpi.qld.gov.au</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</maintCont>
</resMaint>
<placeKeys>
<thesaName>
<resTitle>ANZLIC Search Words</resTitle>
<date>
<createDate>2025-09-11</createDate>
</date>
</thesaName>
<keyword>Queensland</keyword>
</placeKeys>
<themeKeys>
<thesaName>
<resTitle>ANZLIC Search Words</resTitle>
<date>
<createDate>2023-05-24T00:00:00</createDate>
</date>
<resEd>Version 3.0</resEd>
<resEdDate>20230524</resEdDate>
</thesaName>
<keyword>WATER Surface</keyword>
<keyword>WATER Rivers</keyword>
<keyword>FISHERIES Freshwater Planning</keyword>
</themeKeys>
<themeKeys>
<thesaName>
<resTitle>Common Search Terms</resTitle>
<date>
<createDate>2023-05-24</createDate>
</date>
<resEd>Version 3.0</resEd>
<resEdDate>20230524</resEdDate>
</thesaName>
<keyword>River</keyword>
<keyword>Creek</keyword>
<keyword>Stream</keyword>
<keyword>Watercourse</keyword>
<keyword>Drainage feature</keyword>
<keyword>Fish passage</keyword>
<keyword>Waterway barrier works</keyword>
<keyword>SDAP State Code 18</keyword>
</themeKeys>
<searchKeys>
<keyword>Queensland</keyword>
<keyword>WATER Surface</keyword>
<keyword>WATER Rivers</keyword>
<keyword>FISHERIES Freshwater Planning</keyword>
<keyword>River</keyword>
<keyword>Creek</keyword>
<keyword>Stream</keyword>
<keyword>Watercourse</keyword>
<keyword>Drainage feature</keyword>
<keyword>Fish passage</keyword>
<keyword>Waterway barrier works</keyword>
<keyword>SDAP State Code 18</keyword>
</searchKeys>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;Features are derived from the best available data sources. Refer to metadata of source datasets (Watercourse Lines and Canal Lines - Queensland, Queensland Wetland Data Version 5.0 – Wetland Areas 2017 and 1 second SRTM Derived Hydrological Digital Elevation Model (DEM-H) version 1.0 ) for reliability. Version 3.1 was created using version 3 of the Queensland waterways for waterway barrier works dataset.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<resConst>
<LegConsts>
<useLimit>The State of Queensland (Department of Primary Industries)</useLimit>
<useConsts>
<RestrictCd value="006"/>
</useConsts>
</LegConsts>
</resConst>
<resConst>
<LegConsts>
<useLimit>This material is licensed under a &lt;a rel="license" href="http://creativecommons.org/licenses/by/4.0/ "&gt;
Creative Commons - Attribution 4.0 International&lt;/a&gt; licence. &lt;br /&gt;
&lt;a rel="license" href="http://creativecommons.org/licenses/by/4.0/ "&gt;&lt;img alt="Creative Commons License" title="Creative Commons - Attribution 4.0 International License" style="border: 0;" src="https://licensebuttons.net/l/by/4.0/88x31.png " /&gt;&lt;/a&gt;&lt;br /&gt;</useLimit>
<useConsts>
<RestrictCd value="005"/>
</useConsts>
</LegConsts>
</resConst>
<resConst>
<SecConsts>
<class>
<ClasscationCd value="001"/>
</class>
<userNote>Unrestricted to all levels of government and community. Data is available to all government agencies, community groups and individuals. Dataset is available through physical supply and may be made available via web delivery tools, for example, through internet sites.</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>
<createDate>2025-10-08T00:00:00</createDate>
</date>
</identAuth>
<identCode>fishq.qld_wwbw</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>Queensland</exDesc>
</dataExt>
<dataExt>
<exDesc>Bounding Box</exDesc>
<geoEle>
<GeoBndBox>
<exTypeCode>true</exTypeCode>
<westBL>137.993377</westBL>
<eastBL>153.533167</eastBL>
<southBL>-29.179224</southBL>
<northBL>-9.243053</northBL>
</GeoBndBox>
</geoEle>
</dataExt>
<suppInfo>Waterway barrier works are regulated under the Fisheries Act 1994 and the Planning Act 2016 when barriers to fish movement, including partial barriers, are to be installed across waterways. Barrier works include construction, raising, replacement and some maintenance works on structures such as culvert crossings, bed level and low level crossings, weirs and dams, both permanent and temporary.
The definition of 'waterway' under the Fisheries Act is broad and the Queensland-wide data layers have been developed to better delineate this. Waterway barrier works must adhere to the relevant accepted development requirement for a particular work type or be carried out in accordance with a development approval. On the data layers, these waterways are depicted as a coloured network from the upstream limit, downstream to the tidal or wetland conclusion.
These classifications show whether a given waterway barrier works can meet the accepted development requirements or requires a development approval.
The data layers need to be used in conjunction with the user guide "Queensland waterways for waterway barrier works spatial data layer. User guide." and the accepted development requirement document and policies. The relevant documents accessible on the Department of Primary Industries website.
Users should recognise the limitations of the data and ground truth work sites before proceeding.
Features that are not coloured on the data layer may be considered waterways under the Fisheries Act 1994. For operational works on these waterways users can use the accepted development requirements or seek pre-lodgement advice for assessable development. Also barrier works within freshwater wetlands are subject to other State and Federal legislation.
The Queensland Waterways for Waterway Barrier Works mapping consists of two data layers:
1. Queensland waterways for waterway barrier works. This layer contains classified lines of waterways that form the basis for the level of assessment required for any proposed waterway barrier works. All waterways features (polylines) are classified in the "FISH_PASS" field of the feature table to describe the risk of impact. The values are 1: Low, 2: Moderate, 3: High, 4: Major, 5: Major (Tidal).
2. Queensland waterways for waterway barrier works - Tidal. This layer contains areas that define the estuary/tidal habitat that is considered important to fisheries. The estuary/tidal features (polygons) are classified in the "FISH_PASS" field of the feature table to describe the risk of impact with the value of 5: Major (Tidal).</suppInfo>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">137.993377</westBL>
<eastBL Sync="TRUE">153.533167</eastBL>
<northBL Sync="TRUE">-9.243053</northBL>
<southBL Sync="TRUE">-29.179224</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<tpCat>
<TopicCatCd value="012"/>
</tpCat>
<tpCat>
<TopicCatCd value="007"/>
</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>Covers waterways within the state of Queensland that require fish passage. The majority of the data is complete with all data being subject to continual update.</measDesc>
<measResult>
<ConResult>
<conSpec>
<resTitle>Queensland Fisheries, Department of Primary Industries data capture process</resTitle>
<date>
<createDate>2025-10-08T00:00:00</createDate>
</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>The data maintains logical consistency of the source datasets.</measDesc>
<measResult>
<ConResult>
<conSpec>
<resTitle>Queensland Fisheries, Department of Primary Industries data capture process</resTitle>
<date>
<createDate>2025-10-08T00:00:00</createDate>
</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>While every care is taken to ensure the accuracy of the data, all data custodians and/or the State of Queensland makes no representations or warranties about its accuracy, reliability, completeness or suitability for any particular purpose and disclaims all responsibility and all liability (including without limitation, liability in negligence) for all expenses, losses, damages (including indirect or consequential damage) and costs to which the user might incur as a result of the data being inaccurate or incomplete in any way and for any reason.
While the best available data has been used in generating the Queensland Waterways for Waterway Barrier Works dataset, waterways are dynamic systems and in a constant state of change which may not be reflected in the data. The information portrayed is therefore subject to revision.
Where the fitness of the data, in representing the site on the ground, is in question, the burden for ensuring that the appropriate procedures are employed at the site rests solely with the user. Therefore the data should not be the only source for informing the relation of a site to a waterway. Insufficient site-waterway investigations for barrier works by the user may be prosecuted under provisions of the Planning Act 2016 and the Fisheries Act 1994.</measDesc>
<measResult>
<ConResult>
<conSpec>
<resTitle>Queensland Fisheries, Department of Primary Industries data capture process</resTitle>
<date>
<createDate>2025-10-08T00:00:00</createDate>
</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>Attribution is completed in accordance with Qld Department of Primary Industries, Qld waterways mapping methodology.</measDesc>
<measResult>
<ConResult>
<conSpec>
<resTitle>Queensland Fisheries, Department of Primary Industries data capture process</resTitle>
<date>
<createDate>2025-10-08T00:00:00</createDate>
</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>This dataset is GDA2020 compatible. The source data, and therefore the captured features, are georeferenced as GDA94 (horizontal only). The horizontal accuracy of the geo-referencing and/or data collection method for this example is greater than the datum offset between GDA94 and GDA2020 (1.8 meters). The resulting dataset has been nominated as a low-accuracy GDA2020 dataset. As this data has not been directly captured in GDA2020, nor transformed to GDA2020, the resulting data is 'GDA2020 Compatible' not 'GDA2020 Compliant'.
Source datasets:
- Watercourse Lines and Canal Lines - Queensland,
- Queensland Wetland Data Version 5.0 – Wetland Areas 2017,
- 1 second SRTM Derived Hydrological Digital Elevation Model (DEM-H) version 1.0, and
- Queensland waterways for waterway barrier works (Internal) Version 3.0 (2023).
Version 1 (2013).
The source datasets were analysed to produce a fish passage attribute for waterways within Queensland. The waterways are depicted as grey polygons and a multi-coloured waterway network, from their upstream limit down to their tidal or wetland conclusion. The colour of a waterway is primarily used to guide users to applicable accepted development work types.
Version 2 (2016).
Manual and automated update of version 1 Qld Waterways datasets.
Manual - Localised edits of waterways 'centreline' location and fish passage attribute. Limited to a small number of waterways. Updates based on interpretation of aerial imagery and field inspection.
Automated - Waterways with a fish passage attribute of 1 ('Green') that were identified as intersecting the Tidal Waterways dataset had their fish passage attribute transitioned to 2 ('Amber').
Version 3 (2023).
Significant improvements of the accuracy of the input datasets, to reflect the on-ground location of mapped features, has occurred since version 1 of the Queensland Waterways mapping was introduced.
The Qld waterways mapping still provides a fish passage attribute for waterways within Queensland. The waterways are depicted as grey polygons and a multi-coloured waterway network, from their upstream limit down to their tidal or wetland conclusion. The colour of a waterway is primarily used to guide users to applicable accepted development work types.
The original analysis, GIS workflow, that produced version 1 of the Qld Waterways mapping has been automated. The analysis, has also been expanded to accommodate key updates to the input source datasets and to improve the usability of the mapping. This expanded analysis was performed to:
- fully automate the GIS workflow;
- reduce the number of purple waterways in western drainage basins, particularly for braided waterway systems;
- reduce the occurrence of unintended alternating waterway colours; and
- remove segments of isolated green waterways in the upper catchment that are less than 500 m long.
Updating the Qld waterways mapping to match recent and more accurate versions of the data sources will ensure:
- updated mapping more accurately represents the on-ground features that are waterways for waterway barrier works;
- Qld waterways mapping more closely reflects other government mapping sources;
- improved protection and management of waterways and fish habitats; and
- provision of more opportunities to build waterway barrier works in western waterways under accepted development requirements while still providing good outcomes for fish passage.
The following summarises the GIS analysis undertaken to classify waterways with a fish passage attribute that determines its colour:
1. Acquire / source input datasets.
2. Append the CanalLines dataset to the WatercourseLines dataset to form single drainage network.
3. Split the single drainage network into eastern and western datasets based on drainage basins.
4. Clip the elevation model to Queensland and derive average slope values for eastern waterways.
5. Classify eastern waterways with Fish Passage (FP) attribute (colour):
Purple = FP of 4 = Stream order ≥4
Red = FP of 3 = Stream order = 3
Amber = FP of 2 = Stream order = 2
Green = FP of 1 = Stream order = 1 and average slope of segment less than 6%
6. Classify western waterways with Fish Passage (FP) attribute (colour):
Purple = FP of 4 = Stream order ≥5, categorised as a major watercourse
Purple = FP of 4 = Stream order ≥ 5, categorised as a minor watercourse that is completely or partly within a mapped wetland area*
Red = FP of 3 = Stream order ≥ 5, categorised as a minor watercourse that is not completely or partly within a mapped wetland area*
Red = FP of 3 = Stream order = 4
Amber = FP of 2 = Stream order = 3
Green = FP of 1 = Stream order = 2
*Mapped wetland area = any wetland area (polygon) mapped on Queensland Wetland Data Version 5.0 – Wetland Areas 2017 dataset
7. Grey = Tidal waterways = “Estuarine” wetland areas (polygons) from Queensland Wetland Data Version 5.0 – Wetland Areas 2017 dataset
8. Merge eastern and western waterways to form single drainage network.
9. Identification of coastal waterways, green or not displayed, that intersect/connect to the tidal waterways polygons. Reclassified as amber, FP of 2, waterways.
10. Removal of waterways (line features) that overlap tidal waterways (polygon features).
11. Identified that some waterways on islands outside the extent of the elevation model were not assigned a FP attribute. These were examined and deemed appropriate to assign as ‘green’, FP of 1, waterways.
12. Isolated waterway segments within 30m of tidal polygons reclassified as grey
13. Isolated green waterway segments, in the upper catchments, less than 500m in length not displayed.
14. The data from intermediate outputs was curated to create Version 3 Queensland waterways mapping. Version 3.1 (2025).
The amendments were restricted to waterways within the western drainage basins and included removal or reclassification of waterways to streamline requirements for fish passage.
Note: No amendments were made to the polygon v3 'Tidal' Qld waterways mapping layer (fishq.qld_wwbw_tidal)
The key additional GIS analysis performed are as follows:
1. Copy existing 'internal' v3 Qld waterways (line) dataset.
2. Create an updated drainage basin dataset that incorporates the nominated 'western' drainage basins. Attribute each polygon as either 'Eastern' or 'Western'.
3. Within the new amended 'western' drainage basin extent, reclassify waterways fish passage attribute based on the 'Western' waterways classification matrix.
4. Reclassify all western waterways, with SO &gt;=5 and Hierarchy = 'minor' and 'fish_pass' &lt;&gt; 5 attributes, to a RED waterway (fish passage attribute = 3).
Note: The intent of this step is to identify the 'main' channel within the braided waterways present in western drainage basins.
5. The data from intermediate outputs was curated to create Version 3.1 Queensland waterways mapping.</statement>
<dataSource type="">
<srcDesc>Watercourse Lines and Canal Lines - Queensland
Refer to Metadata for details specific to this source data set.</srcDesc>
</dataSource>
<dataSource type="">
<srcDesc>Queensland Wetland Data Version 5.0 – Wetland Areas 2017
Refer to Metadata for details specific to this source data set.</srcDesc>
</dataSource>
<dataSource type="">
<srcDesc>1 second SRTM Derived Hydrological Digital Elevation Model (DEM-H) version 1.0.
Refer to Metadata for details specific to this source data set.</srcDesc>
</dataSource>
</dataLineage>
</dqInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="qld_wwbw">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">2016992</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<refSysInfo>
<RefSystem dimension="">
<refSysID>
<identCode code="4283"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<identVrsn>6.5(3.0.1)</identVrsn>
<idVersion Sync="TRUE">6.5(3.0.1)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<eainfo>
<detailed Name="qld_wwbw">
<enttyp>
<enttypl Sync="FALSE">qld_wwbw</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">2016992</enttypc>
<enttypd>Data object</enttypd>
<enttypds>ESRI</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>
<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">FISH_PASS</attrlabl>
<attalias Sync="TRUE">Fish Passage Attribute</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">5</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The Fish Passage (FP) attribute for waterways is a number that ranges from 1 to 5. All waterways are fish habitat that is protected and managed to maintain fish passage and other fish habitat values.
To aid use of the Queensland waterways mapping, a system of colours has been assigned to waterways to provide easy identification of the FP attribute. The colours green, amber, red, purple and grey are used to depict FP attributes 1 to 5. The mapped colour provides a visual link to enable the use of accepted development requirements that guide management solutions of waterway barrier work types that have been made accepted development.
Regardless of the FP attribute assigned from 1 to 5, the development must incorporate solutions that provide adequate fish passage for the conditions and swimming ability of the weakest swimmers in the fish community present. Although the FP attribute is a number, the magnitude of this value or number does not express relative importance of the fish habitat.</attrdef>
<attrdefs>DAF Fisheries inhouse process</attrdefs>
<attrdomv>
<udom>as shown</udom>
</attrdomv>
<attrdomv>
<edom>
<edomv>1</edomv>
<edomvd>green</edomvd>
<edomvds>Classification of waterways with a fish passage attribute is an in-house DPI Fisheries process captured in python scripts.</edomvds>
</edom>
<edom>
<edomv>2</edomv>
<edomvd>amber</edomvd>
<edomvds>Classification of waterways with a fish passage attribute is an in-house DPI Fisheries process captured in python scripts.</edomvds>
</edom>
<edom>
<edomv>3</edomv>
<edomvd>red</edomvd>
<edomvds>Classification of waterways with a fish passage attribute is an in-house DPI Fisheries process captured in python scripts.</edomvds>
</edom>
<edom>
<edomv>4</edomv>
<edomvd>purple</edomvd>
<edomvds>Classification of waterways with a fish passage attribute is an in-house DPI Fisheries process captured in python scripts.</edomvds>
</edom>
<edom>
<edomv>5</edomv>
<edomvd>grey</edomvd>
<edomvds>Classification of waterways with a fish passage attribute is an in-house DPI Fisheries process captured in python scripts.</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">st_length(shape)</attrlabl>
<attalias Sync="TRUE">st_length(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_wwbw">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="3"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">2016992</efeacnt>
<spindex Sync="TRUE">FALSE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
</metadata>
