1 / 30

Improving community safety through Wildfire Mitigation… An Open Source Case Study

Improving community safety through Wildfire Mitigation… An Open Source Case Study. FOSS4G 2009. Alistair Hart, Coordinator GIS Atherton Tablelands Geographic Information Services. Presentation Content. Website functionality Website architecture Why select Open Source?

primo
Download Presentation

Improving community safety through Wildfire Mitigation… An Open Source Case Study

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Improving community safety through Wildfire Mitigation…An Open Source Case Study FOSS4G 2009 Alistair Hart, Coordinator GIS Atherton Tablelands Geographic Information Services

  2. Presentation Content • Website functionality • Website architecture • Why select Open Source? • What issues did we run into? • How did we solve them?

  3. http://wildfire.atgis.com.au Login: foss4g@atgis.com.au Password: foss4g

  4. Where is ATGIS located? Atherton Sydney

  5. Two rules of this web project • This is not a GIS • The rule of least astonishment Why? Target audience… Wildfire hazard management stakeholders • Almost entirely non-spatial professionals • Rural firefighting volunteers (often farmers)

  6. Website Features • User admin console • Create maps online • Layer control (inc. labelling) • Custom layer creation • PHP forms to attribute custom objects • PDF map creation • Custom URL link tool • Download facility • GIS data • Pre-constructed PDF maps • Documents (reports, presentations, etc) • File Exchange • FEEDBACK FORM

  7. http://wildfire.atgis.com.au

  8. http://wildfire.atgis.com.au

  9. http://wildfire.atgis.com.au

  10. http://wildfire.atgis.com.au

  11. http://wildfire.atgis.com.au

  12. http://wildfire.atgis.com.au

  13. http://wildfire.atgis.com.au

  14. PDF Map Creation

  15. Online digitizing function Capacity to add fire trails, water access points, hazards, prescribed burns etc. Can add attributes to each of these objects http://wildfire.atgis.com.au/maps/?k=45,8,48,101,6,5,7,1,12,14,104,16,U411&l=48,101,1,27,28,12,16&x=145.38619&y=-17.37095&z=15

  16. Managing submitted data

  17. Architecture - summary

  18. Classical vendor profile

  19. OS community creativity

  20. Why Free & Open Source? • Startup and ongoing maintenance costs (licensing vs development) • Capital focussed project funding base ($$ for startup but not maintenance) • Reinforcing our ethos of ‘code once, not licence annually’

  21. Why Free & Open Source? • Access to developer skills => Recruit/Contract OS technology skills base generally more abundant than closed source • Capacity to increase scalability across multiple processors and locations at no additional cost • Eg. portable wifi-webmapping service for disaster response

  22. Re-use for low-cost community projects

  23. Re-use for low-cost community projects

  24. What issues did we encounterand how did we solve them? • User support • self-help animated GIF files • online feedback tool • face to face training and telephone support • Speed of information delivery Many users still on dialup internet (~20%) • Performance tuning tile server • OS products – small footprint • Dependency on vendor goodwill (ie. Google) • License terms are dynamic but have shifted in our favour (so far) • Interested in alternatives (eg. Open Layers)

  25. Issues and resolution 2.0 (iR 2.0?) • ‘Deep’ technology stack requires a broad skills base to support • Funding for maintenance (like there is none…) • Commercialisation - converting offering from service based solution, to a solution able to be maintained by end-users (NQWMP 3.0?) • OS acceptance in the public sector

  26. Where to from here? • Functionality enhancements scheduled • Tighter integration with smartphones • Sourcing of appropriate technology stack to manage ongoing maintenance liability (any feedback?) • Review code to ensure sustainable development resource • Another great project… presented at Barcelona!

  27. Questions?

More Related