GRASS GIS APIs: Difference between revisions
Jump to navigation
Jump to search
m (Neteler moved page GRASS APIs to GRASS GIS APIs: Please use "GRASS GIS" where possible) |
(cosmetics) |
||
| Line 1: | Line 1: | ||
== Introduction to this document == | == Introduction to this document == | ||
== GRASS Modules as "functions" == | == GRASS GIS Modules as "functions" == | ||
* GRASS has modular structure: each module is a separate program | * GRASS GIS has modular structure: each module is a separate program | ||
* Easy to integrate into any language that allows system calls | * Easy to integrate into any language that allows system calls | ||
| Line 18: | Line 18: | ||
* Direct access to low-level C-functions (via ctypes). | * Direct access to low-level C-functions (via ctypes). | ||
* Direct access to data | * Direct access to data | ||
* Allows writing more complex Python programs than the scripting library | * Allows writing of more complex Python programs than the scripting library | ||
== The C-API == | == The C-API == | ||
* Core library is 30 years | * Core library is being developed for more than 30 years | ||
* Different additional libraries added through time | * Different additional libraries added through time | ||
Revision as of 14:37, 21 January 2015
Introduction to this document
GRASS GIS Modules as "functions"
- GRASS GIS has modular structure: each module is a separate program
- Easy to integrate into any language that allows system calls
The Python scripting library
- Some specific python functions to facilitate calling grass modules and capturing their output
Easy GUI creation in scripts
- Automatic GUI creation based on basic configuration of options
The PyGRASS API using ctypes
- Direct access to low-level C-functions (via ctypes).
- Direct access to data
- Allows writing of more complex Python programs than the scripting library
The C-API
- Core library is being developed for more than 30 years
- Different additional libraries added through time