MAIN ROADS LGA MERGERS (ANI)

Transcription

1 MAIN ROADS LGA MERGERS (ANI) Version 1.0 Final 9/12/2014

2 Document Control Document Purpose The purpose of the LGA Mergers (ANI) is to describe the high-level requirements for the creation of an automated tool that will apply updtes to the IRIS road network. Version Control Certain chapters may include product information provided by component suppliers, and are therefore subject to change without notice. DATE VERSION STATUS DESCRIPTION AUTHOR 14/11/ Draft Initial Draft Wayne Perry 26/11/ Draft Feedback from ANI Jon Mills 02/12/ Draft Feedback from WALGA Wayne Perry 09/12/ Final Initial Release Wayne Perry Related Documents DOCUMENT NAME VERSION PUBLISHED DATE AUTHOR

3 Table of Contents 1. Background Merger Approach Input File Merger Scenarios Scenario 1 - Whole road moved into new LG Scenario 2 - Whole road moved into LG, reversed Scenario 3 - Whole road moved into LG, reversed, joined to existing road Scenario 4 - Whole road moved into LG, joined to existing road Scenario 5 - Road split between 2 shires, split at a new false node Output File

4 1. BACKGROUND In July 2013 the State Government announced a range of proposed changes to local government arrangements in metropolitan Perth with the goal of reducing the number of local governments in Perth. In October 2014 the State Government confirmed the changes to local government arrangements in metropolitan Perth with new local governments to be in place from 1 July The announced changes will take effect under 1 of two mechanisms; Boundary adjustments, or Amalgamations As a result of the boundary changes, there will be 7 LGAs modified to include all or part of another 7 LGAs which will then cease to exist. The proposed amalgamations are for 6 LGAs to merge into 3 new LGAs, with these amalgamations being subject to a vote by the councils and ratepayers as to whether they will proceed. Future amalgamations are proposed that will require legislation to modify the boundaries of the City of Perth, which once complete will allow for the creation of a new Western Suburbs super council to proceed. Local Roads are primarily managed and maintained by the various LGAs around the State and new roads are periodically submitted to Main Roads. The road details are loaded into IRIS (Integrated Road Information System) which allocates each local road with a unique 7 digit road number, comprising a 3 digit LGA identifier and a 4 digit road number. The Road number is sent back to the LGA for referencing in their road asset management systems. The IRIS data on State and Local roads, including the road number is accessed and utilised by approximately fifty other applications within Main Roads. Main Roads have engaged with the West Australian Local Government Association (WALGA) and also with the ARRB Group who provide the ROMAN II road asset management system with which many of the affected LGAs manage their local road network for their business needs. As a result of discussions held with WALGA, ARRB and LGA representatives, a strategy has been agreed whereby MRWA will; identify affected roads decide on appropriate actions such as join roads, split roads or apply direction (SLK reference) changes apply changes to the IRIS load road network supply a translation table for WALGA and ARRB who will work with LGAs to apply the same updates to their individual road asset management systems. Main Roads will build an automated tool to apply road updates to IRIS and to generate an output file identifying the changes applied. 4

5 2. MERGER APPROACH The general approach for the LGA mergers is; Merging LGAs will be allocated a new LGA ID in all instances, regardless of whether the merge has been mandated as a Boundary Change or Amalgamation LGAs in the inner metro network will be assigned a new LGA id in the 100 series LGAs in the outer metro network will be assigned a new LGA id in the 200 series (Currently only Shire of Murray) All Local network road numbers in the affected LGAs will be allocated a new road number, comprising a new 3 digit LGA Id plus a new 4 Digit road number. The new road numbers will start at 1. All Z network road numbers in the affected LGAs will be allocated a new road number, comprising a new 3 digit LGA Id, the letter Z plus a new 3 Digit road number. The new road numbers will start at INPUT FILE An input file will be created by MRWA for use by an automated update tool that will be subsequently developed. This file will be created using a combination of extracts from sql database queries and manual inputs based upon decisions taken as a consequence of the merge scenarios that apply in each instance. The input file will contain at least one reference to every road affected by the LGA mergers. The file will contain the necessary information to determine the appropriate action to be taken by the automated tool. The input file will contain the following fields; Old SLK from Old SLK to Old Carriageway New Carriageway (mandatory if old carriageway specified) Reverse direction flag (Y/N) default N The presence/absence of fields in the input data will allow the code to determine which of the scenarios is being implemented. Note that this is very deliberately operating at an atomic level if a part of is becoming and another part is becoming then this will be two separate entries. If the SLK ranges were not complete then this would be picked up when part of was still left after all of the activities were complete. 5

6 4. MERGER SCENARIOS 4.1 Scenario 1 - Whole road moved into new LG Actions Required Reclassify entire road Output Fields 4.2 Scenario 2 - Whole road moved into LG, reversed Reverse direction flag (Y/N) default N Output Fields Actions Required: Reverse road Reclassify entire road 4.3 Scenario 3 - Whole road moved into LG, reversed, joined to existing road Reverse direction flag (Y/N) default N Actions Required: Reverse road 6

7 Reclassify entire road Rescale route 4.4 Scenario 4 - Whole road moved into LG, joined to existing road Old Carriageway This would only occur if the old road was Single Cway and is coming in as part of a dual cway onto the new road. Not sure if this will occur. New Carriageway (mandatory if old carriageway specified) Actions Required: Reclassify entire road Reclassify individual elements to new cway if necessary Rescale route 4.5 Scenario 5 - Road split between 2 shires, split at a new false node False node could be a river, rail xing etc. Old SLK from Old SLK to Carriageway can also be (optionally) supplied. New Road No Actions Required: Split of appropriate datum Reclassify original elements within slk range into new road OR into a fake road if it needs reversing o Reverse fake road - if required o Reclassify fake road to be part of new road if required Rescale route Note: We need to update the route terminus information. Our recommendation is that this is derived for those roads which will require a change. This text would be based on the intersecting roads (where it s *not* solely a shire boundary), text to indicate LG boundary where that is the only reason that the road ends, or text to indicate a cul-de-sac. 7

8 5. OUTPUT FILE An output file will be generated by the automated tool that provides the information required to effect the same changes to an external road asset management system (such as ROMAN II, AssetFinda, Assetic, Hansen). The output file will contain the following information; Road Name Old SLK from Old SLK to Old Carriageway New SLK from New SLK to New Carriageway Reversed direction flag Adelaide Level 29, Westpac House 91 King William Street Adelaide SA 5000 P Melbourne AU AU HK Level William Street Melbourne VIC 3000 P Intl Hong Kong Level 49, 4911, The Center 99 Queens Road Central, Hong Kong P Canberra Ground Floor 8 Brindabella Circuit Canberra Airport ACT 2609 P Perth AU AU SG 1 Howard Street Perth WA 6000 P Singapore Level 24 1 Raffles Place Singapore P Intl AU Brisbane Level Eagle Street Brisbane QLD 4000 AU Sydney Level Bond Street Sydney NSW 2000 P P