GRASS migration hints: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
Line 49: Line 49:


== External links: Software Comparisons & Thesis ==
== External links: Software Comparisons & Thesis ==
''Some information may be outdated. Note the year of individual resources.''


* Steiniger, S., Hunter, A.J.S., 2013. The 2012 free and open source GIS software map – A guide to facilitate research, development, and adoption. Computers, Environment and Urban Systems 39, 136–150. [http://dx.doi.org/10.1016/j.compenvurbsys.2012.10.003 DOI]
* Steiniger, S., Hunter, A.J.S., 2013. The 2012 free and open source GIS software map – A guide to facilitate research, development, and adoption. Computers, Environment and Urban Systems 39, 136–150. [http://dx.doi.org/10.1016/j.compenvurbsys.2012.10.003 DOI]

Revision as of 17:02, 30 January 2016

Migrating to GRASS

Welcome! There is a lot of help on the web and a wealth of expertise available on the mailing lists and via IRC.

Tips for recent migrants

GIS "The GRASS way"

Interoperability

Collaboration with external software is highly encouraged.

Portability

  • All code POSIX C and generic UNIX compatible
  • Most code MinGW compatible for native MS-Windows

Scriptability

  • GRASS GIS is made up of modular tools specifically designed for easy scriptability in any number of common scripting languages, see GRASS and Shell
  • Interface for direct hooks into higher scripting languages (esp. Python), see GRASS and Python and
  • if "GRASS_BATCH_JOB=/path/to/script.sh" is set GRASS 6+ will run the script as a batch job and exit when it is complete. Start GRASS with the full path to the mapset to avoid the startup menus. See also GRASS and Shell.

Freedom

GRASS GIS Concepts

External links: Software Comparisons & Thesis

Some information may be outdated. Note the year of individual resources.