Comparing QGIS and gvSIG?

I use both gvSIG and Qgis. In my view it is VERY difficult to say which one is the best. BOTH are very useful and, most of all, IMHO, they are complementary.

This is the boon of using open source softwares: you can try them without spending anything!

This is my personal list. I am fully aware it is very subjective: please, bear with me...

gvSIG pros:

  • NavTable
  • Sextante In my opinion Sextante algorithms, thanks to Victor Olaya work, are more integrated into gvSIG compared to Grass' algorithms in QGIS (at present, for Qgis, there no one working "seriously" on them); Take a look at these videos: http://www.youtube.com/user/sextantelibrary
  • 3D extension There is an extension for Qgis as well (Qgis globe) but it is not on par with gvSIG.
  • Cad tools are more powerful than Qgis tools: thanks to the OpenCad tool extension. For instance, you can create circles, elipses and so on.
  • On Mobile devices gvSIG is better. There are two projects for this: gvSIG mobile and gvSIG mini. This year for QGIS there is a summer of Code project which tries to fill this gap.
  • The Gui for georeferencing an image looks more professional and intuitive on gvSIG (at least if you have an ESRI background...).
  • Saga algorithms are already integrated into gvSIG (thanks to Sextante).
  • IMHO gvSIG 1.11 is more stable than Qgis 1.7 (at least, I get less crashes on Windows Xp...)

QGIS pros:

  • The Gui is much more flexible (you can move the toolbars easily; create new shortcuts; change the icons on-the-fly and so on);
  • its range of plugins is magnificent: there are literally hundreds of them!
  • working on databases is much more powerful on QGIS. For instance, you can use Spatialite on it. There is a wonderful plugin for it. Even PostGis has a wonderful plugin (PostGis Manager).
  • Raster projection on-the-fly (starting from version 1.7);
  • the Community is mostly English-based, which means that all documentation (e.g. Manual) is written in English first and afterwards translated into other languages. the Developers' mailing list is in English as well. (For gvSIG the first language is Spanish.)
  • You can use R (thanks to: manageR)
  • Python background (which is very useful for Beginners to create new plugins);
  • On Windows, QGIS is portable (no need to have any privilege as administrator to install it).
  • On Mac, QGIS is more integrated than gvSIG (at least there are more developers working on it).

I have much more experience with QGIS, but coincidentally just recently I decided to give gvSIG a try. Below some observations, some of which are different from answers from others. My guess is that this is at least partly related to the platform and perhaps memory configuration (especially if you work on Windows). I am running both on Linux (Ubuntu 11.04). Anyway, some points that come to mind:

Stability

  • From the very limited experience I have with gvSIG (1.11), it seems stable
  • I am currently using QGIS (1.7) a lot and it is very stable in my experience. In a few cases I have experienced problems, but these were always related to one of the experimental plugins (QGIS offers the options to download stable and experimental plugins)

Rendering / displaying maps

  • Both render raster up to 2.4 GB reasonably fast on my machine. But if rendering rasters become slow in QGIS, you have the option to build pyramids, after which rendering will be much faster. I think gvSIG offers such an option too, but I am not sure
  • Both render large shapefiles without much problems.
  • gvSIG offers a much wider selection of fill symbols, and all symbols are highly configurable (this aspect is rapidly improving in QGIS). On the other hand, labeling options in QGIS seem to be more comprehensive

Spatial analysis

  • The integration with Sextante gives the gvSIG user direct access to a very impressive library of raster, vector and database functions, including SAGA functions.
  • QGIS has a fairly large selection of plugins as mentioned above, including one for Sextante integration. Others include a CadTools plugin that provides cad like functions (but as I have never worked with CAD, I cannot judge on quality or
    functionality). A disadvantage is that is is sometimes difficult to find the right plugin and supporting documentation is limited or lacking altogether for a lot of the plugins.

GRASS GIS

  • Both gvSIG (through the Sextante toolbox) and QGIS offer access to a large set of GRASS GIS functions (in QGIS you can access all when using the build in command line)
  • In QGIS you can open and edit GRASS data from any GRASS database, location and mapset (unlike in GRASS GIS itself, you can select simultaneously layers from different locations or even GRASS databases). This is not possible in gvSIG as far as I know (number one reason for me to go for QGIS).

Talking about free softwares, the dynamic of the community could also be an argument of choice for using one or another.

That document benchmarks gvSIG/Qgis and GRASS regarding the community aspects (see english summary of paper here). I would say it is interesting but has to be read with precaution. Taken indicators to analyze the community participation could be discussed! And specifically here, since more and more users use qgis as GRASS GUI.

(And it could be discussed on many others points)

Tags:

Qgis

Gvsig

Recent Posts