Report
A series of public information sessions conducted by PWS on their ‘Next Iconic Walk Project’ in the Tyndall Range have now concluded.
Many detailed computer-generated images of each node were provided. For the first time, these make clear the sheer number of structures proposed at each node, and resultant impact on a currently wild landscape. Structures include a large building containing bunks, kitchen and dining facilities, a “lounge”, a viewing deck, separate accommodation “pods” for clients who are prepared to pay more for private sleeping quarters, a separate toilet block and separate staff accommodation.
The displays confirmed the locations of the shelters to be placed near the halfway point of each day’s walk to provide the clients somewhere to shelter from the rain. They also confirmed that the southern node has been moved to Lake Mary from its previously proposed location on top of a knoll below Mt Geikie which seemed ludicrously impractical.
PWS has previously indicated the nodes have been selected to offer spectacular views (and hence concomitant visibility for the structures), and that the architecture will also contribute to the “wow” factor. This represents a change in design philosophy; previous PWS lodges elsewhere have made at least some attempt to blend into the landscape.
The TNPA has previously argued that the opening of the new track will facilitate an unplanned trampled pad forming from Huntley Lookout to the summit of Mt Tyndall but discussion at the information session reminded us that that, in addition to Mt Tyndall, an ‘Abel’ coveted by many bushwalkers, there are two other Abels in the area; Mts Geikie and Sedgwick. The new track will also facilitate access to these; more unplanned pad development seems inevitable!
TNPA remains of the view that the Tyndall Range is an inappropriate location for the proposed walk development and that the expenditure of the $40 million budget on other options could have benefited West Coast tourism just as much, or more. For more background on the issue see here and here.
