Eaglepath did not start as software. It started as a way of working: build a GIS database of the constraints along a proposed corridor, model the route options, and show stakeholders how route options were compared and a decision was made. The Eaglepath method was first developed in 1988 to identify transmission line routes, and Pacific Sustainability’s founder has applied earlier versions of the Eaglepath method to transmission lines, gas pipelines, rail corridors and conveyors ever since. The timeline below traces how the method developed.
Where Eaglepath began
The Eaglepath method was originally developed in 1988 to identify transmission line routes.
Major linear projects on a GIS database
Applied to the environmental assessment of a proposed 330 kV transmission line between Armidale, NSW and Springdale, Queensland, coordinating seven specialist studies around a shared GIS database, and to a proposed gas pipeline from a Torres Strait gas field to Townsville built on an ArcInfo GIS database.
Corridor selection with GIS
The approach behind Eaglepath was set out in a conference paper on applying a geographic information system to transmission line corridor selection studies (URPIS 17, Perth).
Remote sensing as an input
A follow-up paper set out how remote sensing could be combined with GIS for environmental impact assessment, widening the data available to describe a corridor.
Grid-based visibility modelling
Grid-based GIS was used to site the structures of a proposed wind farm near Esperance, WA so that visual impact was minimised. Similar computer visibility modelling supported landscape and quarry visual assessments in Western Australia.
Routing programs for transmission lines
A journal paper on routing selection programs for power transmission lines documented the computer-based routing approach.
Pipeline, power station and powerline together
Route selection was used in an environmental review covering a gas pipeline from Karratha to Port Hedland, a gas-fired power station and a 220 kV transmission line from Port Hedland to Newman, with extensive consultation with landholders, shires and interest groups. Environmental approval was received in December 1993.
Sharing the approach
Papers on GIS in environmental consulting were presented at the WALIS and AURISA conferences.
Visual impact for a Townsville powerline
A GIS-based visual impact assessment formed part of the environmental assessment of a proposed transmission line connection to an industrial site in South Townsville, alongside an assessment of a related rail spur.
GIS route models for transmission lines
For a state transmission network operator in Queensland, route selection studies for the Tully to Innisfail and Acland transmission lines compiled a GIS database and developed a GIS model to identify and assess route options. On the Tully to Innisfail study, the model was also used in consultation to show stakeholders how the corridor was selected. A full EIS for a 132 kV transmission line at Millmerran followed in 1999.
Rail corridors
Route selection modelling identified viable rail corridors into the Port of Bundaberg, extending the method from powerlines to rail. The same year, route selection was used in the EIA for a proposed 100 km, 132 kV transmission line from Bulli Creek to Goondiwindi in South West Queensland.
Gas pipelines and network decisions
Route assessment and modelling supported the impact assessment and environmental management plan for 130 km of gas pipeline near Dalby, Queensland. A GIS-based decision support system was also built to optimise the movement of recyclable waste within Queensland.
The Bandanna project, Queensland
Conveyor route selection on the Bandanna project in Queensland, using Pacific Sustainability’s earlier route alignment work built on ArcView. Pacific Sustainability Pty Ltd was established the same year.
Eaglepath desktop software
Those decades of route selection work have now been rebuilt as Eaglepath, a standalone Windows desktop application for pipelines, powerlines, roads and rail, with the 1.10.0 test version now available. It brings together the same steps: build the constraint data, model and compare route options, and document a route selection decision made by you.
Selected projects only. Client names are withheld. Dates are shown as recorded in our project records; where an exact year is not recorded, a period is given.