GRASS migration hints: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
No edit summary
Line 40: Line 40:


* [[Tips for Arc users|Tips for ArcGIS users]]
* [[Tips for Arc users|Tips for ArcGIS users]]
* [[GIS to GRASS command translation|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)


[[Category:Community]]
[[Category:Community]]

Revision as of 22:25, 19 June 2006

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.


GIS "The GRASS way"

Interoperability

Collaboration with external software is highly encouraged.

  • GDAL/OGR for Import/Export
  • R statistics: GRASS/R interface
  • DXF: v.in.dxf, v.out.dxf
  • Matlab/Octave: r.in.mat, r.out.mat, v.in.mapgen, v.in.ascii, v.out.ascii
  • POVray: r.out.pov, v.out.pov
  • VMRL: p.out.vrml
  • GMT - Generic Mapping Tools for cartography: r.in.bin, r.out.bin
  • Google Earth/KML: v.out.ogr
  • VTK (Paraview, etc): r3.out.vtk, r.out.vtk, v.out.vtk
  • V5D: r3.in.v5d, r3.out.v5d

Portability

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

Scriptability

  • GRASS is made up of modular tools specifically designed for easy scriptability in any number of common scripting languages
  • SWIG interface for direct hooks into higher scripting languages

Freedom


GRASS Concepts


Tips for recent migrants