|
GRASS GIS Developers Forum
|
Mailing list -
Download/CVS -
Help wanted! -
Compiling GRASS -
Programmer's Manual -
Code submission -
Related software
GRASS - Geographic Resources Analysis Support System has been under
continual development since 1982 and has involved a large number of federal
US agencies, universities, and private companies. The core components of
GRASS and the management of the integration of the efforts into GRASS
releases were accomplished by the Construction Engineering Resesarch
Laboratory (CERL) in Champaign, Illinois. It has been estimated that several
million dollars of GRASS software development efforts across the government
have been completed since the 4.1 release. Since 1997 a worldwide network of
developers continue to release new GRASS versions (see
GRASS history).
The strength and success of GRASS relies on the user community. This in
mind, the philosophy of the GRASS Development Team is to encourage users to
develop their own unique tools and applications for GRASS. If you develop
tools and techniques that you feel would benefit other GRASS users, let us
know! We strongly recommend to follow the coding style described in
SUBMITTING file (which you find in the main directory of GRASS source code).
GRASS GIS is developed and supported by a worldwide developers
team [see the incomplete GRASS Developers World Map
(big: 500k)]. As GRASS is growing, we have plenty of opportunities to join
the GRASS development team and improve the powerful GRASS GIS under terms of
GNU General Public License.
Many people have contributed to the GRASS
GIS. Without any one of them, GRASS would not exist in its current form.
The authors of the individual programs are listed at the end of their manual
page in GRASS users manual, however, numerous authors of bug fixes and
enhancements as well as people who have been working on coordination,
integration, documentation and testing are not mentioned. Therefore, this
page is an attempt to acknowledge those who contributed to GRASS
development. Please allow us to extend our most cordial thanks to all of
you. If you contributed to GRASS at any point during it's existence, please
let us know your name and e-mail address so we can add your name here.
Developers Mailing List
Please join our mailing list which shall help and coordinate ongoing
development in GRASS GIS 5.x development. Join the list if you are
programmer
and/or want to follow the development discussion. If you have
questions concerning compilation of the CVS-GRASS, please ask here.
How you can help
- Bug reports: You are kindly requested to report bugs through
our bug tracking form. Our system
keeps you informed about progress on a detected bug.
- Bug fixing: Please assist in fixing known bugs from the GRASS 5 known bugs
list.
- Implementation of wishes: Open wishes are listed in the GRASS
5 wish list.
- Write missing man pages: Help us to write missing man pages. Check against the
existing GRASS 5 man-pages.
- Wanted algorithm: Probably you have already developed an wanted
algorithm which you are willing to share with GIS community? Please
let us know.
Roadmap
See the GRASS Development roadmap
Download the latest GRASS software
To follow GRASS development, get the latest code from CVS server:
Compiling GRASS
Compiling GRASS is only recommended to people with experience (that's why we
also offer precompiled binaries).
The configuration requires a set of installed libraries which are
described in the file REQUIREMENTS.html
file (which you also find in the main directory of the source code tarball).
The compilation is desribed in the INSTALL
file (which you also find in the main directory of the source code tarball).
Some hints are also collected here.
Dear Newbie, please be so kind to search the developers mailing list archive before asking
developers - most questions have been already answered several
times :-)
GRASS 5 Programmer's Manual
- GRASS 5.0/5.3:
- GRASS 5.7:
- GRASS 4.x JAVA interface (code is included in src.garden/grass.java/)
Debugging: hints are collected in documents/debugging.txt (GRASS 5.0/5.3) and
doc/debugging.txt (GRASS 5.7)
in the source code.
Code submission
When developing GRASS software, you may want to share your development with
the GRASS community. There are several ways to probably get your code into
the standard GRASS release. Another option is to host the software on an own
web page, in this case we can add a link to out "GRASS Add-ons" section. We
strongly recommend to follow the coding style described in SUBMITTING file
(which you find in the GRASS source code).
- Coding standards: Check your code against the rules defined in the
'SUBMITTING' file (find it in the main directory of the GRASS source
code and also here). This ensures
a smooth integration into the standard GRASS code base.
- Code submission: Please contact a member of the GRASS Development Team
or write to the development mailing list (see above).
- GRASS Add-on submission: go here (Add-on code
is hosted on your server)
- Alredy submitted code which is not (yet) integrated: OUTGOING
directory
- GRASS CVS write access for developers
GRASS related projects/libraries
Related software
(and software not yet related, but maybe useful
links)