Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/OSGeo/grass
GRASS GIS - free and open-source geospatial processing engine
https://github.com/OSGeo/grass
arrays data-science earth-observation geospatial geospatial-analysis gis grass-gis hacktoberfest image-processing jupyter machine-learning open-science parallel-computing python raster remote-sensing science spatial timeseries-analysis vector
Last synced: about 2 months ago
JSON representation
GRASS GIS - free and open-source geospatial processing engine
- Host: GitHub
- URL: https://github.com/OSGeo/grass
- Owner: OSGeo
- License: other
- Created: 2019-05-17T16:13:33.000Z (over 5 years ago)
- Default Branch: main
- Last Pushed: 2024-10-29T15:29:11.000Z (about 2 months ago)
- Last Synced: 2024-10-29T17:31:15.319Z (about 2 months ago)
- Topics: arrays, data-science, earth-observation, geospatial, geospatial-analysis, gis, grass-gis, hacktoberfest, image-processing, jupyter, machine-learning, open-science, parallel-computing, python, raster, remote-sensing, science, spatial, timeseries-analysis, vector
- Language: C
- Homepage: https://grass.osgeo.org
- Size: 310 MB
- Stars: 845
- Watchers: 45
- Forks: 307
- Open Issues: 575
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGES
- Contributing: CONTRIBUTING.md
- Funding: .github/FUNDING.yml
- License: COPYING
- Code of conduct: CODE_OF_CONDUCT.md
- Citation: CITATION.cff
- Security: SECURITY.md
- Authors: AUTHORS
Awesome Lists containing this project
- awesome-robotic-tooling - grass - GRASS GIS - free and open source Geographic Information System (GIS). (Simultaneous Localization and Mapping / Vector Map)
README
# GRASS GIS Repository
[](https://travis-ci.com/OSGeo/grass)
[](https://github.com/OSGeo/grass/actions?query=workflow%3A%22GCC+C%2FC%2B%2B+standards+check%22)
[](https://github.com/OSGeo/grass/actions?query=workflow%3A%22Python+code+quality+check%22)
[](https://github.com/OSGeo/grass/actions?query=workflow%3A%22General+linting%22)
[](https://github.com/OSGeo/grass/actions?query=workflow%3AUbuntu)
[](https://github.com/OSGeo/grass/actions?query=workflow%3AOSGeo4W)
[](https://securityscorecards.dev/viewer/?uri=github.com/OSGeo/grass)
[](https://www.bestpractices.dev/projects/2470)
[](https://scan.coverity.com/projects/grass)
[](https://doi.org/10.5281/zenodo.5176030)
[](https://gitter.im/grassgis/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
[](CODE_OF_CONDUCT.md)
## Description
GRASS GIS ([https://grass.osgeo.org/](https://grass.osgeo.org/)) is
a Geographic Information System used for geospatial data management and
analysis, image processing, graphics/map production, spatial modeling, and
visualization.
Launch this repository in Binder and experiment with GRASS's Python API in
Jupyter Notebooks by clicking the button below:
[](https://mybinder.org/v2/gh/OSGeo/grass/main?labpath=doc%2Fnotebooks%2Fjupyter_example.ipynb)
## Contributing
In general: you don't really need write access as you can simply open
a [pull request](https://github.com/OSGeo/grass/pulls) to contribute to
GRASS GIS. See [CONTRIBUTING file](CONTRIBUTING.md) for more details.
How to get write access here
Want to become a core developer? See
[Procedure for gaining Git write access](https://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheGRASScorerepository)
## How to compile GRASS
> See the INSTALL.md file.
Yes, you should really read [INSTALL.md](INSTALL.md). In addition, there are
detailed [compile instructions](https://grasswiki.osgeo.org/wiki/Compile_and_Install)
in the Wiki.
## Docker
Build a docker image using the downloaded source code (run this in the directory
containing the source code):
A. Docker image **without graphical user interface - wxGUI**.
```bash
docker build -t grassgis .
```
A test run (assuming you have the existing GRASS GIS test location; it can be
downloaded from
[here](https://grass.osgeo.org/sampledata/north_carolina/nc_basic_spm_grass7.zip))
```bash
# case 1: launching in the grassdata directory in which the location is stored:
docker run -it --rm --user=$(id -u):$(id -g) --volume $(pwd):/data \
--env HOME=/data/ grassgis grass --text nc_basic_spm_grass7/user1 \
--exec g.region -p
# case 2: launching anywhere
docker run -it --rm --user=$(id -u):$(id -g) \
--volume /your/test/grassdata/:/data --env HOME=/data/ grassgis \
grass /data/nc_basic_spm_grass7/PERMANENT --exec g.region -p
```
Note that the first `grassgis` is the name of the image while the second
`grass` is the name of the executable.
To run the tests (again assuming local location):
```bash
docker run -it --rm --user=$(id -u):$(id -g) \
--volume /your/test/grassdata/:/data --env HOME=/data/ -w /code/grass \
grassgis grass /data/nc_basic_spm_grass7/PERMANENT --exec \
python -m grass.gunittest.main \
--location nc_basic_spm_grass7 --location-type nc
```
B. Docker image **with graphical user interface - wxGUI**.
```bash
docker build -t grassgis -f docker/ubuntu_wxgui/Dockerfile .
```
Note that the first `grassgis` is the name of the image while the second
`grass` is the name of the executable.
```bash
xhost local:$(id -u)
docker run -it --privileged --user=$(id -u):$(id -g) --rm \
--volume="$(pwd)/:/data" --volume="/tmp/.X11-unix:/tmp/.X11-unix:rw" \
--env HOME=/data/ --env DISPLAY=$DISPLAY \
--device="/dev/dri/card0:/dev/dri/card0" \
grassgis grass --gui
```
Note: If you compiled locally before building the Docker image, you may
encounter problems as the local configuration and the locally compiled files
are copied to and used in the Docker image. To make sure you don't have
this issue, clean all the compiled files from the source code:
```bash
make distclean
```
## Thanks to all contributors ❤
[](https://github.com/OSGeo/grass/graphs/contributors)