<mdb:MD_Metadata xmlns:cit="http://standards.iso.org/iso/19115/-3/cit/2.0" xmlns:gco="http://standards.iso.org/iso/19115/-3/gco/1.0" xmlns:gex="http://standards.iso.org/iso/19115/-3/gex/1.0" xmlns:lan="http://standards.iso.org/iso/19115/-3/lan/1.0" xmlns:mcc="http://standards.iso.org/iso/19115/-3/mcc/1.0" xmlns:mdb="http://standards.iso.org/iso/19115/-3/mdb/2.0" xmlns:mrd="http://standards.iso.org/iso/19115/-3/mrd/1.0" xmlns:mri="http://standards.iso.org/iso/19115/-3/mri/1.0" xmlns:xlink="http://www.w3.org/1999/xlink">
    <mdb:metadataIdentifier xlink:type="simple">
        <mcc:MD_Identifier>
            <mcc:code>
                <gco:CharacterString>abc17c8b-a79b-4be4-8055-aa3a5dc8ddf9</gco:CharacterString>
            </mcc:code>
            <mcc:codeSpace>
                <gco:CharacterString>urn:uuid</gco:CharacterString>
            </mcc:codeSpace>
        </mcc:MD_Identifier>
    </mdb:metadataIdentifier>
    <mdb:defaultLocale xlink:type="simple">
        <lan:PT_Locale>
            <lan:language>
                <lan:LanguageCode codeList="" codeListValue="en">en</lan:LanguageCode>
            </lan:language>
            <lan:characterEncoding>
                <lan:MD_CharacterSetCode codeList="" codeListValue="UTF-8">UTF-8</lan:MD_CharacterSetCode>
            </lan:characterEncoding>
        </lan:PT_Locale>
    </mdb:defaultLocale>
    <mdb:metadataScope xlink:type="simple">
        <mdb:MD_MetadataScope>
            <mdb:resourceScope>
                <mcc:MD_ScopeCode codeList="" codeListValue="nonGeographicDataset">nonGeographicDataset</mcc:MD_ScopeCode>
            </mdb:resourceScope>
            <mdb:name>
                <gco:CharacterString>nonGeographicDataset</gco:CharacterString>
            </mdb:name>
        </mdb:MD_MetadataScope>
    </mdb:metadataScope>
    <mdb:contact xlink:type="simple" />
    <mdb:dateInfo xlink:type="simple">
        <cit:CI_Date>
            <cit:date>
                <gco:DateTime>2024-06-14T01:18:42</gco:DateTime>
            </cit:date>
            <cit:dateType>
                <cit:CI_DateTypeCode codeList="" codeListValue="creation">creation</cit:CI_DateTypeCode>
            </cit:dateType>
        </cit:CI_Date>
    </mdb:dateInfo>
    <mdb:metadataStandard xlink:type="simple">
        <cit:CI_Citation>
            <cit:title>
                <gco:CharacterString>ISO 19115</gco:CharacterString>
            </cit:title>
            <cit:edition>
                <gco:CharacterString>2016</gco:CharacterString>
            </cit:edition>
        </cit:CI_Citation>
    </mdb:metadataStandard>
    <mdb:identificationInfo xlink:type="simple">
        <mri:MD_DataIdentification>
            <mri:citation xlink:type="simple">
                <cit:CI_Citation>
                    <cit:title>
                        <gco:CharacterString>TCC Traffic Calibration Model 2025</gco:CharacterString>
                    </cit:title>
                    <cit:identifier xlink:type="simple">
                        <mcc:MD_Identifier>
                            <mcc:code>
                                <gco:CharacterString>abc17c8b-a79b-4be4-8055-aa3a5dc8ddf9</gco:CharacterString>
                            </mcc:code>
                        </mcc:MD_Identifier>
                    </cit:identifier>
                </cit:CI_Citation>
            </mri:citation>
            <mri:abstract>
                <gco:CharacterString>Townsville City Council maintains a traffic model for the entire city.

The model is called the Townsville Aimsun Integrated Model (TAIM).

The TAIM is a city-wide mesoscopic model and is Council’s primary planning tool for the analysis of proposed improvement options, upgrades, and interventions on the road network to support growth identified in the Local Government Infrastructure Plan (LGIP). 

The TAIM is calibrated annually against traffic signal information provided by the Department of Transport and Main Roads and provides detailed traffic flow information across the entire city for the calibration year and future year projections in 2026, 2031, 2036, 2041 and Fully Development Scenario (FDS).</gco:CharacterString>
            </mri:abstract>
            <mri:extent xlink:type="simple">
                <gex:EX_Extent>
                    <gex:description>
                        <gco:CharacterString>QLD35084: TOWNSVILLE</gco:CharacterString>
                    </gex:description>
                    <gex:geographicElement xlink:type="simple">
                        <gex:EX_GeographicBoundingBox>
                            <gex:westBoundLongitude>
                                <gco:Decimal>146.8169454</gco:Decimal>
                            </gex:westBoundLongitude>
                            <gex:eastBoundLongitude>
                                <gco:Decimal>146.8169454</gco:Decimal>
                            </gex:eastBoundLongitude>
                            <gex:southBoundLatitude>
                                <gco:Decimal>-19.25984165</gco:Decimal>
                            </gex:southBoundLatitude>
                            <gex:northBoundLatitude>
                                <gco:Decimal>-19.25984165</gco:Decimal>
                            </gex:northBoundLatitude>
                        </gex:EX_GeographicBoundingBox>
                    </gex:geographicElement>
                    <gex:temporalElement xlink:type="simple" />
                    <gex:verticalElement xlink:type="simple" />
                </gex:EX_Extent>
            </mri:extent>
            <mri:additionalDocumentation xlink:type="simple" />
            <mri:descriptiveKeywords xlink:type="simple">
                <mri:MD_Keywords>
                    <mri:keyword>
                        <gco:CharacterString>traffic</gco:CharacterString>
                    </mri:keyword>
                </mri:MD_Keywords>
            </mri:descriptiveKeywords>
            <mri:descriptiveKeywords xlink:type="simple">
                <mri:MD_Keywords>
                    <mri:keyword>
                        <gco:CharacterString>traffic counts</gco:CharacterString>
                    </mri:keyword>
                </mri:MD_Keywords>
            </mri:descriptiveKeywords>
            <mri:descriptiveKeywords xlink:type="simple">
                <mri:MD_Keywords>
                    <mri:keyword>
                        <gco:CharacterString>traffic model</gco:CharacterString>
                    </mri:keyword>
                </mri:MD_Keywords>
            </mri:descriptiveKeywords>
        </mri:MD_DataIdentification>
    </mdb:identificationInfo>
    <mdb:identificationInfo xlink:type="simple">
        <mri:MD_DataIdentification>
            <mri:citation xlink:type="simple">
                <cit:CI_Citation>
                    <cit:title>
                        <gco:CharacterString>TCC Traffic Calibration Model 2025</gco:CharacterString>
                    </cit:title>
                    <cit:presentationForm>
                        <cit:CI_PresentationFormCode codeList="" codeListValue="documentDigital">documentDigital</cit:CI_PresentationFormCode>
                    </cit:presentationForm>
                </cit:CI_Citation>
            </mri:citation>
            <mri:abstract>
                <gco:CharacterString>Townsville City Council maintains a traffic model for the entire city.

The following limitations apply to the Traffic Model:

The Townsville Aimsun Integrated Model (TAIM) is an imperfect representation of traffic information on the road network in the calibration year. The traffic model has been developed using Aimsun traffic modelling software and provides an interpretation of the traffic conditions limited by the modelling processes.

The model has been calibrated against traffic flow data recorded by vehicle detection equipment at approximately 150 signalised intersections comprising over 2175 detection counts, and approximately 150 traffic count sites located across the city.

Model accuracy at any particular location is relative to how close the location is to a calibration point in the model. At a calibration point the model replicates the traffic flows at that location, e.g., at a signalised intersection the model flows and the data recorded by the signals will match in the calibration year. Between calibration points the model becomes less accurate and a process called Dynamic User Equilibrium (DUE) is used to estimate traffic flows based on travel time algorithms.

Townsville City Council accepts no responsibility for damages, if any, suffered by any party because of decisions or actions made based on data extracted from the model.
</gco:CharacterString>
            </mri:abstract>
            <mri:additionalDocumentation xlink:type="simple" />
            <mri:resourceFormat xlink:type="simple">
                <mrd:MD_Format>
                    <mrd:formatSpecificationCitation xlink:type="simple">
                        <cit:CI_Citation>
                            <cit:title>
                                <gco:CharacterString>website link</gco:CharacterString>
                            </cit:title>
                        </cit:CI_Citation>
                    </mrd:formatSpecificationCitation>
                </mrd:MD_Format>
            </mri:resourceFormat>
        </mri:MD_DataIdentification>
    </mdb:identificationInfo>
    <mdb:identificationInfo xlink:type="simple">
        <mri:MD_DataIdentification>
            <mri:citation xlink:type="simple">
                <cit:CI_Citation>
                    <cit:title>
                        <gco:CharacterString>TCC Traffic Forecast Models 2025</gco:CharacterString>
                    </cit:title>
                    <cit:presentationForm>
                        <cit:CI_PresentationFormCode codeList="" codeListValue="documentDigital">documentDigital</cit:CI_PresentationFormCode>
                    </cit:presentationForm>
                </cit:CI_Citation>
            </mri:citation>
            <mri:abstract>
                <gco:CharacterString>Townsville City Council maintains a traffic model for the entire city.

The following limitations apply to the Traffic Forecast Models:

The Townsville Aimsun Integrated Model (TAIM) is an imperfect representation of traffic information on the road network in the calibration year. The traffic model has been developed using Aimsun traffic modelling software and provides an interpretation of the traffic conditions limited by the modelling processes.

The model has been calibrated against traffic flow data recorded by vehicle detection equipment at approximately 150 signalised intersections comprising over 2175 detection counts, and approximately 150 traffic count sites located across the city.

Model accuracy at any particular location is relative to how close the location is to a calibration point in the model. At a calibration point the model replicates the traffic flows at that location, e.g., at a signalised intersection the model flows and the data recorded by the signals will match in the calibration year. Between calibration points the model becomes less accurate and a process called Dynamic User Equilibrium (DUE) is used to estimate traffic flows based on travel time algorithms.

Future year forecast models assume various structural changes to the road network consistent with Townsville City Councils’ review of the Local Government Infrastructure Plan (LGIP) and the Townsville Growth Model. 

Timing of LGIP projects is indicative only and are subject to funding. There is no commitment by Council to implement any infrastructure changes indicated in the traffic forecast models. 

Townsville City Council accepts no responsibility for damages, if any, suffered by any party because of decisions or actions made based on data extracted from the model.
</gco:CharacterString>
            </mri:abstract>
            <mri:additionalDocumentation xlink:type="simple" />
            <mri:resourceFormat xlink:type="simple">
                <mrd:MD_Format>
                    <mrd:formatSpecificationCitation xlink:type="simple">
                        <cit:CI_Citation>
                            <cit:title>
                                <gco:CharacterString>website link</gco:CharacterString>
                            </cit:title>
                        </cit:CI_Citation>
                    </mrd:formatSpecificationCitation>
                </mrd:MD_Format>
            </mri:resourceFormat>
        </mri:MD_DataIdentification>
    </mdb:identificationInfo>
</mdb:MD_Metadata>