All Projects → OSGeo → Grass

OSGeo / Grass

Licence: other
GRASS GIS - free and open source Geographic Information System (GIS)

Programming Languages

c
50402 projects - #5 most used programming language

Projects that are alternatives of or similar to Grass

Geocube
Tool to convert geopandas vector data into rasterized xarray data.
Stars: ✭ 87 (-69.04%)
Mutual labels:  hacktoberfest, vector, raster, gis, geospatial
Python Geospatial
A collection of Python packages for geospatial analysis with binder-ready notebook examples
Stars: ✭ 187 (-33.45%)
Mutual labels:  vector, raster, gis, geospatial
Rioxarray
geospatial xarray extension powered by rasterio
Stars: ✭ 148 (-47.33%)
Mutual labels:  hacktoberfest, raster, gis, geospatial
Geotiff.io
Static website for viewing and analyzing GeoTIFF's in the browser
Stars: ✭ 53 (-81.14%)
Mutual labels:  raster, gis, geospatial
Blendergis
Blender addons to make the bridge between Blender and geographic data
Stars: ✭ 4,642 (+1551.96%)
Mutual labels:  raster, gis, geospatial
Shapefile.jl
Parsing .shp files in Julia
Stars: ✭ 40 (-85.77%)
Mutual labels:  vector, gis, geospatial
Earthenterprise
Google Earth Enterprise - Open Source
Stars: ✭ 2,425 (+762.99%)
Mutual labels:  vector, raster, gis
Mapchete
Tile-based geodata processing using rasterio & Fiona
Stars: ✭ 129 (-54.09%)
Mutual labels:  vector, raster, gis
Geospatial Python CourseV1
This is an collection of blog posts turned into a course format
Stars: ✭ 53 (-81.14%)
Mutual labels:  vector, geospatial, raster
GeoJSON.jl
Utilities for working with GeoJSON data in Julia
Stars: ✭ 46 (-83.63%)
Mutual labels:  vector, geospatial, gis
Datacube Core
Open Data Cube analyses continental scale Earth Observation data through time
Stars: ✭ 285 (+1.42%)
Mutual labels:  hacktoberfest, raster, gis
localtileserver
🌐 dynamic tile server for visualizing rasters in Jupyter with ipyleaflet or folium
Stars: ✭ 190 (-32.38%)
Mutual labels:  geospatial, gis, raster
GDAL.jl
Thin Julia wrapper for GDAL - Geospatial Data Abstraction Library
Stars: ✭ 78 (-72.24%)
Mutual labels:  vector, geospatial, raster
georaster-layer-for-leaflet
Display GeoTIFFs and soon other types of raster on your Leaflet Map
Stars: ✭ 168 (-40.21%)
Mutual labels:  geospatial, gis, raster
earthengine-py-examples
A collection of 300+ examples for using Earth Engine and the geemap Python package
Stars: ✭ 76 (-72.95%)
Mutual labels:  geospatial, gis
pylandtemp
Algorithms for computing global land surface temperature and emissivity from NASA's Landsat satellite images with Python.
Stars: ✭ 110 (-60.85%)
Mutual labels:  geospatial, raster
lonlat bng
A multithreaded Rust library with FFI for converting WGS84 longitude and latitude coordinates into BNG (OSGB36) Eastings and Northings and vice versa (using OSTN15)
Stars: ✭ 20 (-92.88%)
Mutual labels:  geospatial, gis
Julia Geospatial
Examples for a blog series on Geospatial Julia using ArchGDAL
Stars: ✭ 58 (-79.36%)
Mutual labels:  geospatial, raster
pygeoif
Basic implementation of the __geo_interface__
Stars: ✭ 44 (-84.34%)
Mutual labels:  geospatial, gis
rafagas
Daily geospatial links curated by Raf Roset
Stars: ✭ 17 (-93.95%)
Mutual labels:  geospatial, gis

Build Status GCC C/C++ standards check Python code quality check General linting CI OSGeo4W Centos

GRASS GIS Repository

Description

GRASS GIS (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.

How to get write access here

In general: you don't really need write access as you can simply open a pull request to contribute to GRASS GIS. See CONTRIBUTING file for more details.

Want to become a core developer? See Procedure for gaining Git write access

How to compile GRASS

See INSTALL file.

Yes, you should really read INSTALL. In addition, there are detailed compile instructions in the Wiki.

Docker

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

docker build -t grassgis79 .

A test run (assuming you have the existing GRASS GIS test location; it can be downloaded from here)

# 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/ grassgis79 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/ grassgis79 \
        grass /data/nc_basic_spm_grass7/PERMANENT --exec g.region -p

Note that the first grassgis79 is the name of the image while the second grass 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 \
        grassgis79 grass /data/nc_basic_spm_grass7/PERMANENT --exec \
            python -m grass.gunittest.main \
                --location nc_basic_spm_grass7 --location-type nc

Note: If you compiled locally before building the Docker image, you may encounter problems as the local configuration and locally compiled file 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:

make distclean

How to generate the 'Programmer's Manual'

You can generate locally the GRASS GIS Programmer's Manual.

This needs doxygen (http://www.doxygen.org) and optionally Graphviz dot (http://www.research.att.com/sw/tools/graphviz/).

To build the GRASS programmer's documentation, run

make htmldocs

or to generate documentation as single html file (recommended for simple reading)

make htmldocs-single

here. This takes quite some time. The result is in lib/html/index.html which refers to further document repositories in

lib/vector/html/index.html
lib/db/html/index.html
lib/gis/html/index.html

The master file is: ./grasslib.dox where all sub-documents have to be linked into.

To generate the documents in PDF format, run

make pdfdocs
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].