13.01.2013 Views

A Local-State Government Spatial Data Sharing Partnership

A Local-State Government Spatial Data Sharing Partnership

A Local-State Government Spatial Data Sharing Partnership

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix4 – Open Ended Questionnaire Responses<br />

100 The work that is done at the Council end is very time consuming which then equates to cost<br />

in a council like this with such a small rate base but such a large area to cover. It’s difficult<br />

when you have to drive over 100 km just to get to a site, to then come back to the office and<br />

resolve the problem and feed in into the workflows of M1 or M2.<br />

The <strong>State</strong> <strong>Government</strong> has put the mechanisms in place, so this exchange works, but then<br />

Councils are left to find the solution that best suites them and there business applications at<br />

their own expense.<br />

The state gov supplies the data to all other gov departments under some other agreement<br />

I'm sure, in particular the Titles Office uses the property addresses supplied by councils, but<br />

then cracks the sods so that councils have to have another MOUE to be able to use the<br />

Titles Searching facility to improve the property matching etc. All councils should not have<br />

been judged based on one Councils misuse of access.<br />

The processing of M2s that are supplied by Councils need to have more money thrown at<br />

them so that they are processed in a much more timely fashion - a greater commitment from<br />

the budget process of the state gov to recognise that the spatial data of the state that<br />

underpins a lot of the gov departments business, needs adequate funding so that people at<br />

council level don’t get disheartened when they see time and time again that things haven’t<br />

been done.<br />

291

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!