Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

GRASS - free and open-source geospatial processing engine

License

NotificationsYou must be signed in to change notification settings

OSGeo/grass

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

GCC C/C++ standards checkPython code quality checkGeneral lintingUbuntuOSGeo4WOpenSSF ScorecardOpenSSF Best PracticesCoverityDOIJoin the chat at https://gitter.im/grassgis/communityContributor Covenant

Description

GRASS GIS (https://grass.osgeo.org/) isa Geographic Information System used for geospatial data management andanalysis, image processing, graphics/map production, spatial modeling, andvisualization.

Launch this repository in Binder and experiment with GRASS's Python API inJupyter Notebooks by clicking the button below:

Binder

Contributing

In general: you don't really need write access as you can simply openapull request to contribute toGRASS GIS. SeeCONTRIBUTING file for more details.

How to compile GRASS

See the INSTALL.md file.

Yes, you should really readINSTALL.md. In addition, there aredetailedcompile instructionsin the Wiki.

Docker

Build a docker image using the downloaded source code (run this in the directorycontaining the source code):

A. Docker imagewithout graphical user interface - wxGUI.

docker build -t grassgis.

A test run (assuming you have the existing GRASS GIS test location; it can bedownloaded fromhere)

# 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 anywheredocker 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 firstgrassgis is the name of the image while the secondgrass is the name of the executable.

To run the tests (again assuming local location):

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 imagewith graphical user interface - wxGUI.

docker build -t grassgis -f docker/ubuntu_wxgui/Dockerfile.

Note that the firstgrassgis is the name of the image while the secondgrass is the name of the executable.

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 mayencounter problems as the local configuration and the locally compiled filesare copied to and used in the Docker image. To make sure you don't havethis issue, clean all the compiled files from the source code:

make distclean

Further documents

Thanks to all contributors ❤

GRASS contributors


[8]ページ先頭

©2009-2025 Movatter.jp