Airport data sets
There can be significant and dangerous gaps within the state spatial framework data sets (eg Roads, Addresses, Features). This appears to be due to administrative anomalies associated with how spatial datsets are assembled (in Victoria its always been bottom up with data coming from local governmnets, usually as a sideline in the arrangements for titles, rates, transfers etc.) Many of these are legacies of land management/ownership ...more »
There can be significant and dangerous gaps within the state spatial framework data sets (eg Roads, Addresses, Features). This appears to be due to administrative anomalies associated with how spatial datsets are assembled (in Victoria its always been bottom up with data coming from local governmnets, usually as a sideline in the arrangements for titles, rates, transfers etc.) Many of these are legacies of land management/ownership and leasing arrangements and may also reflect practices of the days before there were digital datasets.
The bottom line is that no matter who owns or operates the land, or is responsible for securty arrangemenst within Airports, when people have mobile phones they can and do dial 000, and the emergency services do receive calls relating to 'privately' manged parts of the State, and may find themselves searching a location, address, feature or road name that does not exist in the state map base.
Sometimes it appears that entities such as private developers, Resort Management Boards, Airports, Parks Management and a multitude of others do not comprehend that they they have obligations to supply data or to act as custodians, and uunfortunately there is no clear legislation on this subject.
Consequently emergency services can be faced with situations where the statewide map data has 'holes' with missing data for some properties, roads or developments within even airports (federal administration), some of which include non-airport functions such as commercial or subleased premises.
It is my view that every organization managing land must be entailed with legal obligations relating to the supply and maintenance of quality spatial data for incorporation into state map files, including all properties, roads, addresses, occupancies. Also, much of the addressing that has been inherited in private developments including airports does not fit with addressing standards (AS/NZS4819). This means the local governmnet in which the Airport sits, and the state map maintainers has no map of which building belongs to which address, and often no property polygons with which to assign numbers. New streets and roads that are created in airports are often never advised to either the local Governmnet or the Stae mapping agencies, as it may never have gone through the state planning process.
We need to ensure that for ALL development we get property polygons overlaid into the property layer, and updates to the properties, that the roads are named and put into the satte Map Transport layer properly.
This requires also good communication process in place with the Airport corporation both from a Council perspective and a state perspective.
« less full details »
Social Web