This document summarizes a presentation about making QGIS more enterprise-ready. It discusses simplifying the QGIS interface for non-GIS users, managing styles and data across an organization, auditing data for changes and compliance through PostgreSQL triggers, and providing dynamic feedback on invalid data entry to improve data quality. The presentation includes demos of these concepts.

1. @astuntech
Going Enterprise
QGIS & PostGIS
QGIS UK South East User Group
Bish Bash Bosh
2nd April 2014 Mike Saunt

2. @astuntech
Agenda
● Who is this guy?
● What is and why an Enterprise solution?
● Providing a simplified QGIS
● Saving styles
● Managing Data
● Data Entry feedback
Going Enterprise

3. @astuntech
Who is this guy?
● Used to work for MapInfo (moons ago)
● Setup Astun Technology 9 years ago
● Used to be pretty Technical
● Open Source
○ Enterprise Support
○ Training
○ Mentoring etc
● Passionate about Open

4. @astuntech
What is & Why Enterprise?
● Provide business value to the organisation
● Means for anyone to access GIS
● Access & share centralised data
● Have data made available
○ to the GIS
○ from the GIS
● Auditing for compliance
○ When was this data created?
○ Who by?

5. @astuntech
What is & Why Enterprise?

6. @astuntech
What is & Why Enterprise

7. @astuntech
What is & Why Enterprise?
Security
Auditing
Scalability
Sharing

8. @astuntech
Keeping QGIS simple
Scenario - Non GIS users
Goals
● Provide access to GI data
● Save money
○ Minimize training
● Get a better ROI
○ People actually using GIS

9. @astuntech
Keeping QGIS simple
47 tools11tools
11 menus (with ~100 with one click)

10. @astuntech
Keeping QGIS simple
● Use Settings -> Customization

11. @astuntech
Keeping QGIS simple

12. @astuntech
Keeping QGIS simple
● Live Demo!
○ Customize
○ Save to custom .ini file
○ Create Shortcut to use
■ Linux
● “qgis -z cust.ini”
■ Windows
● “c:blahblahqgis.exe --customizationfile cust.ini”
Note: Create a full.ini first incase you lose your settings menu item

13. @astuntech
Enterprise Styling
● Is .qml and now new .qlr but...
● Share data with complex classifications:
○ Census data themed & classified
○ Compare Apples with Apples
● Setup complex classifications
○ Similar to QML but multiple versions
DEMO

14. @astuntech
Auditing of Data
DB Manager plugin
● ‘standard’ auditing shipped with v2.2

15. @astuntech
Auditing of Data
DB Manager plugin
● wants to change your database (not best)

16. @astuntech
Auditing of Data
Using standard PostgreSQL
● doesn’t change your data
● generic TRIGGER
○ a trigger happens when something happens to data
○ generic - same code can apply to multiple tables
● possible to snapshot data from previous date
● simple to configure
SELECT audit.audit_table(‘tablename');
DEMO

17. @astuntech
Auditing of Data
Promising QGIS plugin
● snappy name of
○ Postgres 91 with Auditor
● allows to cycle back and restore

18. @astuntech
Auditing of Data
Promising QGIS plugin

19. @astuntech
Auditing of Data
Promising QGIS plugin

20. @astuntech
Managing Data
Quality Control
● Pesky users digitize incorrectly
Give feedback
● Don’t interrupt their workflow
● Allow them to see issues and correct
● Auditable by Team Leader
Solution
● Dynamic Invalid data view

21. @astuntech
Managing Data
Database view
● Allows for a dynamic SQL of the data
● PostGIS has ST_IsValid(geometry)
○ returns true or false
● Also has ST_IsValidReason(geometry)
○ returns textual description
DEMO

22. @astuntech
Thank you
One last thing...
Did I tell you?