1. Open Source GIS Technology overview Presented by Aaron Racicot – GIS Programmer aaronr@ecotrust.org February 8, 2006

2. Outline  Introduction  Benefits/Limitations of Open Source  Technology Overview - Platforms  Desktop  Server  Embedded devices  Workflows of interest  Cartography - Desktop “paper map” publishing  Cartography - Web map publishing  Modeling - Web-Based real-time decision support  Where is it all going?  Where to go for more info

3. Who am I… B.S. Computer Science Split Personality Environmental advocate Telemark/BC Skier Rafting Guide Portland Mountain Rescue M.S. Environmental Science Open Source advocate Open Source User/Developer Embedded systems developer GIS Programmer

4. Ecotrust - Salmon Nation

5. Why Open Source? “Free software” is a matter of liberty, not price. Free Software!

6. Freedom

7. Benefits/Limitations of Open Source Benefits  Software cost = $0  Source code is available and modifiable  User and development communities flourish  Development cycles are VERY fast Limitations  Total cost is NOT = $0  Many applications are not as polished as the proprietary counterparts  Compatibility with proprietary software can be an issue

8. Software Stacks… Desktop Generic StackFOSS4G StackGrouping ApplicationQGis, Grass, OSSIM, JUMP, UDig User Interface Application Dev. Environment Eclipse, QT, OpenGL High Level UtilitiesGeoTools, PostGISData Serving High Level Scripting Languages PHP, PERL, Python Low Level UtilitiesShplib, GEOS, OGR/GDAL, PostGIS, R-Statistics, GMT Data Processing Low Level Languages C, C++, Java, FortranSystem Software Operating System Linux, Darwin, Cygwin Hardware Drivers 32-64 bit processor drivers Desktop Software Stack

9. OS GIS – Desktop Applications GRASS GIS

10. Software Stacks... Server Server Software Stack Generic StackFOSS4G StackGrouping Client Side BrowserFirefox, Safari, NetscapeUser Interface Client Side Scripting Java Script, Java Applets ~~~~~~~~~~~WEB~~~~~~~~~~~ Server Side Scripting PHP, Python, PERLData Serving High Level UtilitiesMapserver, PCO, Grass Low Level UtilitiesShplib, GEOS, OGR/GDAL, PostGIS, R-Statistics, GMT Data Processing High Level Scripting Languages PHP, PERL, Python Low Level Languages C, C++, Java, FortranSystem Software Operating System/Drivers Linux, Darwin, Cygwin Hardware Drivers32-64 bit processor drivers

11. OS GIS - Server Tools GRASS GIS GDAL/OGR R-Statistics

12. OS GIS Important considerations  Platform support (i.e. UNIX, Linux, Windows, Mac OS)  Speed and efficiency  Data format support  Standards for interoperability (OGC specs) Areas for improvement  Separate packages all with their own strengths  Linking them together is often hard  Write support is often not supported for proprietary formats  Ability to integrate into proprietary systems is limited (i.e. can not link PostGIS database to ArcMap…yet)  Requires multiple installs and maintenance  User interfaces are often the last part of development  Harder to produce traditional “paper maps”

13. Alternatives! ArcReader ArcMap/ArcGIS ArcINFO/ArcGRID ArcPad ArcSDE ArcIMS ArcGIS Server VB, Python UDig,Jump,GRASS,QGis,OSSI M GRASS, OSSIM ???? PostGIS Mapserver GRASS PHP, Python, Perl, C#.net, etc… Viewing Cartography Analysis Devices Database Web Spatial Server Scripting

14. Workflows of Interest Most GIS applications have a similar work flow pattern…  Gather spatially explicit data  Process that data to suit the user needs  Produce outputs useful to the end user

15. Work Flow – Paper Map Publishing Data Gathering Data Formatting Data Processing Map Formatting Map Production User Request User Response

16. Work Flow – What OSGIS is good at Data Gathering Data Formatting Data Processing Map Formatting Map Production User Request User Response Great at data processing but poor at formatting and creating paper maps Paper Map Publishing

17. Example – Paper Map Publishing QGISArcMap

18. Work Flow – Web Map Publishing Map Formatting Map Production Web User Request Web User Response Static Data Storage Web Services

19. Work Flow – What OSGIS is good at Map Formatting Map Production Web User Request Web User Response Static Data Storage Web Services Great at all aspects of traditional web-based mapping Web Map Publishing

20. Examples – Web Map Publishing Custom DHTML/JavaScript Chameleon

21. Examples – Web Map Publishing Ka-Map DM Solutions Cartoweb3 CampToCamp

22. Work Flow – Real-Time Web DST Web User Request Web User Response Static Data Storage Web Services Data Gathering Data Formatting Data Processing Map Formatting Map Production Real-Time Web Decision Support Tools

23. Work Flow – What OSGIS is good at Web User Request Web User Response Static Data Storage Web Services Data Gathering Data Formatting Data Processing Map Formatting Map Production The Problem Is The Arrows! Connecting a web request to server side GIS analysis is tricky Real-Time Web Decision Support Tools

24. Example – Real-Time Web DST Siuslaw Watershed Restoration Initiative

25. Work Flow – Real-Time Web DST Data Gathering Data Formatting Data Processing GRASS Mapserver Mapserver on the front end… GRASS on the back end…

26. Example – OSGIS in use…  QGIS and GRASS as a desktop supplement  QT as an desktop application framework  PostGIS to store vector data layers  Mapserver as a web-based front end  Chameleon Interface as a client side web interface  GRASS as a server side GIS for DST development  OGR/GDAL to pre-process vector and raster data  R-Statistics and GMT for graphing and statistics

27. Example - OCEANSystem Chameleon Mapserver R-Statistics User driven… Web interactive tools… GIS analytical computing… PostGISGRASS

28. Ecotrust Example - OCEANSystem QGIS/GRASS

29. Where is it all going? Integration of OS software across organizations “Google” type interfaces (smooth user experience) –AJAX driven –Streaming media –Seamless datasets Large datasets require more pre-processing Pressure on large private companies to become more responsive to end user needs Integration of OSGIS with proprietary software – required for migration path… Start of services based business…

30. The Future of OSGIS QGIS/GRASS GIS Web-Based Mapserver R-Statistics GMT Fully Integrated Open-Source GIS QGIS/GRASS GIS – Fully functional server GIS doing the heavy lifting. UMN Mapserver – Making data accessible via the web. Geo- spatial server viewed through a web browser. Taking our vision to a growing audience. Adding the analytical glue to make smart decisions based upon sound GIS analysis. Making GIS analysis accessible and affordable

31. Where to go for more info OSGIS  Maptools - http://www.maptools.org  FreeGIS - http://freegis.org/  Open Source GIS - http://opensourcegis.org/ Standards  OGC - http://www.opengeospatial.org/ Desktop  GRASS - http://grass.itc.it/  QGIS - http://qgis.org/  UDIG - http://udig.refractions.net/confluence/display/UDIG/Home  JUMP – http://jump-project.org/  OpenEV - http://openev.sourceforge.net/ Server/Web  Mapserver - http://mapserver.gis.umn.edu/  GRASS - http://grass.itc.it/  PostGIS - http://postgis.refractions.net/ Tools  Remote Sensing - http://remotesensing.org/tiki-index.php  GDAL/OGR - http://gdal.maptools.org/index.html  PROJ.4 - http://proj.maptools.org/

32. The End Tool Screen Shots Follow

33. Backup - GRASS

34. Backup - QGIS

35. Backup - OSSIM

36. Backup - UDIG

37. Backup - JUMP

38. Backup – R-Statistics

39. Backup – PostGIS Geometry WKT Geometry