Free and Open Source Desktop GIS Projects and Software: An Analysis

Transcription

1 Free and Open Source Desktop GIS Projects and Software: An Analysis Stefan Steiniger, University of Calgary, Canada Swiss NSF Project: PAGEVIS-LD

2 OrbisGIS MapWindow GRASS igeodesktop Desktop GIS GIS Editor JUMP Thuban udig Kosmo SAGA QGIS OpenJUMP ILWIS GIS Viewer GIS Analyst gvsig udig, Image: Refractions.net OpenJUMP, Image: Uwe Dallüge GRASS GIS, Image: M. Lennert ( Quantum GIS, Image: M. Neteler (pinus.chinju.ac.kr)

3 pictures from: Questions that I want to answer: - What distinguishs Free and Open Source Desktop GIS (FOSGIS) projects from proprietary projects? FOSGIS vs. - Are FOS GIS ready for the Desktop? - Are FOS Desktop GIS becoming a success story?

4 Outline I. What s a Desktop GIS? II. III. IV. FOS Desktop GIS projects a selection Comparing FOS vs. Proprietary (Desktop) GIS Challenges in FOS GIS management V. So what?

5 I. What s a Desktop GIS?

6 Background (I) What does a Desktop GIS look like? a typical user interface a bit like Google Earth or Google Maps

7 Background (II) What can I do with a Desktop GIS? Viewing (exploration) Creation (& extend dataset) Editing (modify dataset) Conflation (integrating datasets from different sources) Transformation (coordinate systems, raster/vector, resampling, ) Query (new views/selections) Analysis (new datasets with new information) Create maps

8 Background (III) So - what is a Desktop GIS? - distinguishing between different types of GIS software by user tasks* - desktop GIS tasks: 1 viewing, 2 creating, 3 editing, 4 storage, 5 conflation, 6 transformation, 7 query, 8 analysis, 9 creating maps - types of desktop GIS:. GIS Viewer: 1,4,7,(9); - or as ESRI says:. GIS Editor: 1-4,(6),7,9;. GIS Analyst: 1-9 A desktop GIS is a mapping software that is installed onto and runs on a personal computer and allows users to display, query, update, and analyse data about geographic locations and the information linked to those locations. ( *Steiniger and Weibel (2009)

9 II. FOS Desktop GIS a selection

10 Background (IV) - since 2002 a number of free Desktop GIS projects started (> 5) - GRASS and OpenMap earlier, but with military background - different foci:. user background: novice, experienced, expert, research. application: data editing, conflation, analysis, viewing. main data type: raster vs. vector. devel. platform: C++, Java, Python, (PhP?) - possible evaluation criteria:. features/functionality. supported (OGC) standards***. documentation*. transparent devel team*. software modular*. developer community*. user community*. license**. support**. platforms & tech. requirements**. useablity. development API *P Ramsey (2004, 2006); ** JO Wagner (2006), ***J Reid (2001)

11 Background (V) 01. GRASS 02. Quantum GIS (QGIS) 03. JUMP GIS family: OpenJUMP SkyJUMP deejump - PirolJUMP 04. udig : (recently joined by/with JGrass team: dedicated to hydro - geomorphology) 05. SAGA 06. MapWindow 07. Thuban : GIS viewer 08. Kalypso 09. gvsig 10. Kosmo 11. OpenMap : GIS ToolKit 12. ILWIS 13. mezogis : GIS viewer 14. Fmaps : (dead) 15. OrbisGIS : under development 16. Puzzle GIS : under development 17. igeodesktop : under development not open source, but free-of-cost: Spatial Commander, Forestry GIS, Google Earth, ArcExplorer, TNTlite, TatukGIS Viewer,

12 GRASS udig ILWIS gvsig Larger Desktop GIS Projects MapWindow OpenJUMP QGIS SAGA

13 Geographic Resource Analysis Support System GRASS user level: gvsig udig experienced research application focus: vector & raster analysis users: worldwide, large community developers: mainly from universities notes: OpenJUMP Larger Desktop GIS Projects oldest FOS GIS, ArcInfo functionality QGIS ILWIS SAGA MapWindow GRASS GIS Image: M. Lennert (

14 Integrated Land and Water Information System GRASS user level: gvsig udig novice research application focus: vector & raster analysis users: several, research (teaching) developers: ITC Enschede (NL), 52 Nord notes: OpenJUMP *1985, Win-based (Visual C++) Larger Desktop GIS Projects QGIS ILWIS SAGA MapWindow ILWIS Image:

15 Map Window GIS MapWindow GIS: GRASS user level: gvsig udig novice research application focus: GIS core/ vector & raster analysis users: worldwide, large developers: lead: Idaho State Univ., worldwide notes: OpenJUMP Windows only,.net Larger Desktop GIS Projects QGIS used by US Env. Protect. Agency ILWIS SAGA MapWindow

16 System for Automated Geo-Scientific Analysis GRASS user level: gvsig udig novice research application focus: Larger Desktop GIS Projects raster analysis (geomorph./hydro.) users: with particular interests developers: original: Univ. Göttingen (GER), now OpenJUMP U. of Hamburg, others notes: MS Visual C++, but Linux too QGIS ILWIS SAGA MapWindow SAGA GIS:

17 Quantum GIS user level: novice research application focus: gvsig udig data viewer & editor, interface to GRASS, tendency to full GIS users: huge community worldwide developers: worldwide, volunteers notes: best marketing OpenJUMP GRASS Larger Desktop GIS Projects QGIS ILWIS Quantum GIS Image: M. Neteler (pinus.chinju.ac.kr) MapWindow SAGA

18 Open Java Unified Mapping Platform udig gvsig OpenJUMP GRASS Larger Desktop GIS Projects QGIS user level: novice research ILWIS application focus: vector data editing, conflation, analys. users: worldwide, public. admin. developers: SAGA MapWindow orig. JUMP: VividSolutions Inc. (CA), now: volunteers worldwide notes: versions: deejump, SkyJUMP,

19 Generalitat Valencia Sistema d Informacio Geografica udig gvsig OpenJUMP GRASS Larger Desktop GIS Projects QGIS user level: novice research ILWIS application focus: ArcView++ users: public administration (ES), research developers: SAGA MapWindow IVER Technologies (ES), univers. notes: strong financial support by governm. non Spanish user base is growing gvsig Image:

20 user friendly Desktop Internet GIS udig gvsig OpenJUMP GRASS Larger Desktop GIS Projects QGIS user level: novice research ILWIS application focus: viewing, editing, analysis (web/data) users: growing comm., worldwide developers: SAGA MapWindow Refractions R. Inc. (CA), Axios (ES), volunteers notes: --- udig Image:

21 III. Comparing FOS vs. Proprietary (Desktop) GIS FOSGIS vs

22 Comparing functionality Task GRASS QGIS ILWIS udig SAGA Open- JUMP Window 9.3 viewing Map gvsig creation editing integration ο Presentation ArcView - maps - charts - ο tables Overlay Analysis - raster Via Via Via Via - Grass JGrass Sextante Sextante - vector ο partly customizat ion Python, Perl Python ILWIS scripts functionality : available, ο : available via plugins, - : not available Groovy Python Jython.Net Jython several

23 Comparing Development & Support Free GIS projects vs. Proprietary GIS Vendors (1): I - Development Drivers. GIS Projects: companies (commercial), authorities, research and individuals. Prop. GIS: companies (commercial), (very) big customers II User Focus. GIS Projects: focus towards particular user groups and tasks. Prop. GIS: focus towards particular businesses & wide appl. field III Development & Shipping models. GIS Projects: (a) all functions out of the box (GRASS, ILWIS, SAGA) (b) core & 3 rd -party plugins (QGIS, OpenJUMP, gvsig). Prop. GIS: rather (a) but (b) GIS extensions exist too

24 Comparing Development & Support Free GIS projects vs. Proprietary GIS Vendors (2): IV - Support. GIS Projects: by companies*, free , free user forums, wikis. Prop. GIS: by companies (paid), forums (paid + free) *FOS GIS support: see also V - Miscellaneous: FOS GIS Projects 1) not yet ready to create nice maps (req. post-processing) 2) documentation is sometimes incomplete, but you can talk to the developers in forums and user lists 3) information needs to be found by user (no marketing) 4) difficult to estimate how projects continue (not market driven)

25 Comparing Licenses Non GIS specific differences of FOS and Proprietary Software Proprietary Software (e.g. Microsoft Office, ArcGIS) OpenSource / Free Software (e.g. OpenOffice, GRASS GIS) + warranty* of developing company on + no license fees product :holds for every company + unrestricted use (e.g. # installations) + components should work together + no update enforcement + usually well documented software + support of open standards - price & maintenance fees - customized development is difficult - support as long as company exists + customization at API level - installation knowhow necessary - training costs** *) BUT: license agreements often exclude warranty **) BUT: user choice to invest in own resources or to buy Based on a comparison by Martin Weis (2005)

26 IV. Management challenges - for volunteer projects

27 Challenges (I) Situation description - OpenJUMP is a volunteer project + supporting companies Lat/Lon, Intevation, ISA Inc. - ca. 4-5 developers + ca. 3-5 contributing users - ca downloads/month - 80 vs. 90 list users (developers vs. users) Challenges technical users project

28 Challenges - Users Challenges technical users project Challenge I Who are the users? What are their needs? What language do they speak? How to develop a roadmap? Challenge II diversity of users roadmap: explore new areas or concentrate on strengths? shipping: all-in-one or plug-in/ extension system

29 Challenges - Project Challenges technical users project Challenge III Participation is based on goodwill Who will do what and who has time for: maintenance of functions, bug fixing, webpage, developing new functions, integrate existing, translate, documentation : RMap? Challenge VI few contributors no 1000 eyeballs: bugs may be undiscovered for a long time documentation is delayed function wish list is long open wiki s

30 Challenges - hosting Challenges technical users project Challenge V Hosting & Distribution Who hosts and manages the source code repository? Who builds the nightly build? Who pays for the massive download traffic? Who hosts wiki and webpage and downloads?

31 navigating in a triangle user & developer wishes known & unknown known unknown doable changes available resources Solutions for small projects: Efficiency use available infrastructures (SourceForge, OSOR Forge); plug-in system with small core vs. all-in one distribution re-use documentation for web & pdf; make user contributions as easy as possible (wiki)???

32 What you can do Or users that pay for the functionality they wish, i.e. are hiring a programmer We need Feedback & Participation! Already 1h/week can make the difference!

33 V. So what? - Ready for the Desktop? - - Become FOS Desktop GIS a success story?

34 Ready for the Enterprise Desktop? FOS Desktop GIS are ready for the (enterprise) desktop! - functionality ArcView TM level and beyond (Editor) has been achieved - support - free: & forums, commercial: companies - several users in public authorities (ESP, GER, CAN, FIN, IT,...) Issues - Finding a/the suitable software with respect to functionality and license restrictions (see thesis by Atle. F. Sveen on FOS GIS selection) - There are switching costs! (i.e.: no free lunch) Benefits - provider independence - cost savings with respect to scale (10+ installations) - easy to add customized functionality

35 Ready for the Research Desktop? FOS Desktop GIS are ready for the (research) desktop! But avoid it if you want to re-invent the wheel want to spent money for licenses you just work on your own PC (no scaling needed) you like black boxes you love the one size fits all principle (what s adaptation?)... you never need what you have done if you move on AND: You are scared that somebody exploits your developments! (..but remember, you could use what others accomplished...)

36 A success story? YES, FOS Desktop GIS had a good start so far and can continue to be successful if: - more people start using it - more people contribute - management issues can be resolved

37 Thank you! icons from: more info: - ( 2 articles) Gary E. Sherman: Desktop GIS: Mapping the Planet with Open Source Tools (2008)

38

39

40 Outline I. Open Source and Free Software A. Terms and Definitions B. 2 Licenses (GPL & LGPL) C. 3 Possible Misconceptions Note: talking about software licensing isn t a piece of cake

41 I. Open Source and Free Software (1) Some terms you may have heard of Open source Free software Freeware LGPL OSS GPL Shareware FOSS commercial software - What does it mean? - Is free software the same as open source software?

42 I. Open Source and Free Software (2) putting (some) of those terms in an order... Free Software Proprietary Software LGPL GPL Freeware Shareware Open Source (OSS)?commercial software? Proprietary = All Software (Free Software + Open Source Software)

43 I. Open Source and Free Software (3) The term free software is clearly defined by the Free Software Foundation ( Free Open Source Software (FOSS) meets 4 Constraints ( 1. The freedom to run the program, for any purpose (freedom 0) 2. The freedom to study how the program works, and adapt it to your needs (freedom 1). 3. The freedom to redistribute copies so you can help your neighbor (freedom 2). 4. The freedom to improve the program, and release your improvements to the public, so that the whole community benefits (freedom 3). Freedoms : not free for download

44 I. Open Source and Free Software (4) open source vs. free software open source: - is a term and brand : Open Source Initiative - OSI: opensource.org) - is an insufficient term : you can look into? But are you allowed to modify and distribute? free software: - free as in freedom not free-beer - guaranty of four user freedoms Do I need to care? yes (distinction of freedom), and no (license terms will tell you)

45 I. Open Source and Free Software (5) free vs. commercial free: - as in freedom - stress on (public) ownership, not on price opposite of free software is proprietary software, not commercial Note: to avoid confusions people use the term Free and Open Source Software (= FOSS)

46 Outline I. Open Source and Free Software A. Terms and Definitions B. 2 Licenses (GPL & LGPL) C. 3 Possible Misconceptions

47 I. Open Source and Free Software (6) - Several OSI and FSF approved licenses exists (large development projects have sometimes own ones) - well known free software licenses: GNU General Public License (GPL full protection of freedoms) GNU Lesser General Public License (LGPL full protection) BSD (Berkeley), XFree86 (MIT), Apache, Mozilla, (limited prot.) (no protection) Btw: What s GNU?

48 I. Open Source and Free Software (7) The GNU General Public License important license terms (of GPL Version 2): allows to run the program for your own purpose ( 0) allows to copy and distribute ( 1) allows to modify the code and to distribute these versions ( 2) allows distribution of the program and modified versions only if source code is attached or available (written offer) for 3 years ( 3) You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee

49 I. Open Source and Free Software (8) What is meant if people say GPL is immune? - The GPL license terms don t allow to change the license of the software, including new and changed parts it musst still be GPL is called copylefting - When GPL software parts (i.e. as a function library) are used by other software, then the license with the stronger restrictions/freedom remains example: ESRI licence + GPL= To avoid the latter effect: Lesser GPL was introduced. LGPL is very similar to GPL, but LGPL libraries can be used by non- GPL licensed software. ( ESRI+LGPL = ) Note: dual-licensing (GPL & proprietary license) is possible, because the developer has still author rights on his work

50 Outline I. Open Source and Free Software A. Terms and Definitions B. 2 Licenses (GPL & LGPL) C. 3 Possible Misconceptions

51 1. Open Source and Free Software (8) Possible Misconceptions about the GPL license*: 1 If I use code licensed under the GPL Do I need to release my changes to the program's source? No - source code must be released only if you distribute the software 2 If I program software and license it under the GPL I have to give the software away for free? No - copies can be sold and download fees raised. What you may pay for is documentation, packaging & support. 3 If I create (new) software (and data) with GPL tools they must be released under the GPL as well? No - programs & data created with open source software are not affected by the GPL. Only programs that inlcude GPL code. *

52 Some people say such things Are those things myths or facts?

53 Why using open source? - Myths Parts of the following are taken from M. Wheatley*: - Myth 1: The attraction is the price tag Wheatley: stability and effectivity may be other factors** - Myth 2: Savings aren t real Wheatley: because you don t pay for every copy of the software you can safe money - Myth 3: There is no support If there is a user base, there is support. For instance for OpenJump GIS offer 2 companies paid support in Germany alone. - Myth 4: It is a legal minefield several off-court arrangements took place; indemnifications are offered; in 2006 GPL proved ist validity as license on a court in Munich (Landgericht I). * M. Wheatley, 2004: The myths of Open Source, ** ACTUATE, 2007: attraction no license fees: 82.8%

54 Why using open source? - Myths Parts of the following are taken from M. Wheatley*: - Myth 5: Open Source isn t for mission-critical applications Wheatley: a banking system (Banca Popolare di Milano) runs with opensource components - Myth 6: Open Source isn t ready for the desktop that s something I hopefully refuted Btw: interesting figures - 50% of OSS projects started by companies with comercial intention* - In Germany 59% of companies use [?] OSS software (US: 48%)** - 80% of OSS developers are IT professionals (96% male )*** *) missing original source **) ACTUATE (2007) ***) Robes et al. (2001), Hertel et al (2003), Open Source Jahrbuch 2006: p

55 History and organization Some Bits of History: Grass GIS* 1978/80 first libraries: US Army Corps of Eng. (CERL). because ArcInfo was to expensive. Fort Hood Inf. Syst. in 1982, Grass 1.0 in 1985,. last release (V4.1) in revival in 1997/1998 (Baylor Univ. & U. of Hannover). relicensing to GPL in 1999 Proj/Proj.4 early 1980, Library for projections by USGS (Evenden 2003) OpenMap GIS toolkit, started 1992 as MATT with DARPA founding OGR/GDAL Library for GIS data format conversion by F. Warmerdam. launch in 1998 FreeGIS.org 99, UMN MapServer 96/97, PostGIS in 00/01, JTS 00/02 Desktop: SAGA 01/2, Thuban 03, JUMP 02/3, QGIS 02/3, udig 04/5 *) Westervelt (2004)

56 Example of a Spatial Data Infrastructure (SDI): End User (e.g. Municipality / NGO) WebMap Server INTERNET GeoPortal Map Viewer Thin Client Map Editor Thick Client Desktop GIS GIS Analyst Data Storage Data Provider Desktop GIS Data Collector (create map..)

57 ... or software from a vendor (ESRI ) perspective Example of a Spatial Data Infrastructure (SDI): End User (e.g. Municipality / NGO) Map Viewer Arc Explorer WebMap Server ArcGIS Server, ArcIMS INTERNET GeoPortal Map Editor ArcGIS X Desktop GIS ArcGIS - ArcInfo Data Storage ArcSDE / Oracle Spatial Desktop GIS ArcGIS - ArcEditor

58 ...or OS GIS projects Example of a SDI with OpenSource Components: End User (e.g. Municipality / NGO) UMN MapServer, GeoServer, Deegree, (MapGuide OpenSource) INTERNET GeoPortal Thin Client: MapBuilder, Mapbender Thick Client: udig, QGIS, Thuban,... GIS Analysis: Data Storage: GRASS GIS + QGIS, PostGIS, Kosmo, gvsig, SAGA,... (H2 spatial) Data Collection: OpenJUMP,

59 types of GIS software:

60 Diversity of GIS software & projects. gvsig Mobile Pilot Web stuff:. OpenLayers (GMaps). MapFish. MapBender. NASA World Wind (GEarth). OSSIM. PostGIS. MySQL Spatial. SpatialLite. H2 Spatial. TerraView. MapServer. GeoServer. MapGuide OS. deegree. GDAL/OGR (data formats). Geotools (all in one). OpenMap. Sextante (raster analysis). JTS Topology Suite / GEOS Non-exhaustive overview of projects in Paul Ramsey (2007)

61 Desktop GIS GRASS QGIS* udig* gvsig ILWIS SAGA JUMP / OpenJUMP Evaluation criterion user level appl. focus platfom standards community support FamiliarU- Vec+Raster, Expert (Res) Analysis Novice- Vec+Raster, FamiliarU Viewing, GRASS-GUI FamiliarU Vector, Web, Viewing FamiliarU- Vec+Raster Expert (Res) goal: ArcView functionality++ Novice- Vec+Raster Expert Analysis GIS core, Expert (Res) V+R, Analysis MapWindow Novice- FamiliarU- Raster, Expert (Res) Analysis Novice- Vec, Editing, Expert (Res) Analysis Linux, Mac (Win) [C] Win,Linux, Mac [C++] Win,Linux, Mac [Java] Win,Linux, Mac [Java] Win [MS Visual C] Grass 6.3: GML (via OGR), WFS, WMS QGIS 0.9: WMS, WFS, SFS (via PostGIS), GML (via OGR) udig 1.1: SFS, WMS, WFS, GML, SLD gvsig 1.0: SFS, WMS, WFS, WCS, WMC, GML WFS,WCS under development Win [.NET] WFS,WCS under development Win,Linux, [C++] Win,Linux, (Mac)[Java] User:ww, large Dev: Universities User: ww, strong Dev: ww, Volunt. Prof., lists (++) Prof., lists (++) User: ww, growing Prof., Dev: Company lists (++) User: ww, strong Dev: Company User: ww. strong Dev: ITC/ 52 Nord User: strong Dev: Idaho S.U.??? User: strong OJ 1.2: SFS, WMS,GML,SLD (WFS/-T plugin) *) strong development activities: application focus may extend, ww = worldwide Dev: UoHamburg Prof., lists (++) Prof., lists (++) Prof., lists (+) Prof., lists (+) User: ww, growing Prof., Dev: ww, Volunt. lists (++) authors ranking

62 Challenges (I) Situation description - OpenJUMP is a volunteer project (+ supporting companies Lat/Lon, Intevation, ISA Inc.) - ca. 4-5 developers + ca. 3-5 contributing users - ca downloads/month - 80 vs. 90 list users (developers vs. users) We achieved a lot, but - Who will fix the bugs and maintains functions? - Who will add new functions and improve the core? - Who writes documentation? - Who maintains the webpage & wiki? we can not enforce anything, since all are volunteers!