Your SlideShare is downloading. ×
Spatial@gov conference 2011 denise mc kenzie
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Spatial@gov conference 2011 denise mc kenzie


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Vicmap API & VicGISOpen Source in Practice Denise McKenzie Department of Sustainability and Environment
  • 2. What Government users want….• Tools to suit all requirements – non-expert to GIS specialist• Digital Map requirements – Simple – Vicmap API, basic maps (Google, Bing), visualisation – Mid-Range – Interactive Map, VicGIS, Analysis, Simple data collection – Complex – Spatial Modeling, Analytics, traditional GIS
  • 3. Context WoVG Spatial Services Victorian • Victorian Mapping and Address Service (VMAS) Government • Image Web Server (IWS) Spatial Group • Spatial Datamart (SDM)7 Areas of Spatial • Victorian Spatial Data Library (VSDL) Information • Notification for Editing Services (NES) provision and • Data Publish Service (DPS) application • MyProfile •Acquisition • Data Search Victoria • Maintenance • Catalogue (web services) • Publishing • VicGIS • Discovery • Access • Vicmap API • Presentation • GPSnet • Feedback • Coordinated Imagery Program (CIP) • Custodianship
  • 4. Why build a map API?• Nov 2010 – Google removed Public Sector Mapping Agency (PSMA) spatial data from Google Maps• Replaced by ‘snap shot’ map base from Sensis – quality issues , crowd- sourcing own data updates instead of using authoritative government sources• Risk to government in using incorrect information to display maps • Incompatibility with Govt business requirements • Decision making requires most up to date information • Reputation and liability• “Fit for purpose”
  • 5. example - Cranbourne• status at mid- November: 217 dwellings: – 102 buildings under construction – 79 buildings complete – 36 buildings occupied
  • 6. example - Cranbourne actual progress at April and June 2011 (image supplied by local government)
  • 7. Point Cook Coastal Park• Wetlands missing, RAAF Boundary incorrect, coastline incorrect Proprietary API Vicmap API
  • 8. Vicmap API• Built from Vicmap Framework Data • High quality • Current – weekly updates (total last month - road updates over 900, property/address updates over 12,000) • Authoritative – Custodianship agreements (local government & Land Victoria)• 3 sets of tiles created at 14 zoom scales 1:8mil to 1:800• Vector Data – 16 data layers• Imagery 1:8mil to 1:800 aerial photography (annual update program covering most of the state)• Hybrid of Imagery & Vector Data (transparency)• Tiles currently updated quarterly, future plan to move to incremental updates in line with weekly Vicmap data update
  • 9. VicGIS• Collaboration between 4 Vic Govt Departments• Simple Interface and easy to add more information• Mark up and drawing on maps is simple and easy• Extend the querying of information for analysis and reporting• Allow collaborative approach for sharing information• Low maintenance cost, and adherence to standards• Easy to customise, integrate, extend• Currently 5 instances in Vic Govt – Transmaps (DOT), PlanGIS (DPCD), LandGIS, Vicroads, DSE
  • 10. VicGIS
  • 11. VicGIS Catalogue• Access to both data and webservices (WFS/WMS/WMTS)• Data across departments to be readily available online from a centrally managed environment• Add information sources externally available (eg. BOM)• Allow information to be shared securely and easily• Extend the catalogue to other data providers• Reduce the cost of sharing information
  • 12. Why Open Source?• Open Standards – OGC• Learn through experience - Policy & Strategy Development• Collaboration• Accessibility• Cost effective replication
  • 13. Vicmap API – OpenLayers, GeoServer, GeowebcacheVicGIS – OpenLayers, GeoServerPLM25 – PostGIS (Naomi Withers) Open Source in DSE
  • 14. Open Source Benefits• Compatible with existing systems (ESRI tiles in Geowebcache)• International development community• Local Developer, not bound to a vendor• Short product update cycle – bug resolution• Replicable design, as many machines as we need• Extensible, scalable,• No license costs!
  • 15. Challenges – next steps• Limited by what has been developed, capability• Need to up skill in-house resources• Code Management• Relationship with Open Source Community• Developer collaboration and communication
  • 16. Summary• Vicmap API & VicGIS part of WoVG spatial capability• Connecting presentation capability with non-specialist spatial users• Encourage Open Source Solutions to be further developed• Collaboration opportunities
  • 17. ContactsVicmap APIPeter Debicki – Product Flynn – Manager Customer at ConferenceDenise McKenzie