GRASS migration hints: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
No edit summary
(+GRASS 7 hints)
Line 9: Line 9:
* [[GIS to GRASS command translation|Whatever-GIS-Software to GRASS command translation table and discussion]]
* [[GIS to GRASS command translation|Whatever-GIS-Software to GRASS command translation table and discussion]]
* GRASS 4 and 5 users: [[GRASS Module Porting List]] (check here if you don't find a certain command in GRASS 6)
* GRASS 4 and 5 users: [[GRASS Module Porting List]] (check here if you don't find a certain command in GRASS 6)
* GRASS 7 users: [http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures List of new features in GRASS 7] (new names, options, etc.; check here if you don't find a certain command or module parameter)


== GIS "The GRASS way" ==
== GIS "The GRASS way" ==

Revision as of 05:50, 11 May 2013

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 Concepts

Software Comparisons & Thesis