GRASS-GIS / grass-ci
Licence: other
OUTDATED, use https://github.com/OSGeo/grass/ ! Continuous integration for GRASS GIS
Stars: ✭ 27
Programming Languages
Projects that are alternatives of or similar to grass-ci
grass-addons
GRASS GIS Addons Repository (Manuals: https://grass.osgeo.org/grass-stable/manuals/addons/ | Linux-logs: https://grass.osgeo.org/addons/grass8/logs/ | Windows logs: https://wingrass.fsv.cvut.cz/grass82/addons/grass-8.2.0/logs/)
Stars: ✭ 64 (+137.04%)
Mutual labels: osgeo, geospatial-analysis, grass-gis
actinia core
Actinia Core is an open source REST API for scalable, distributed, high performance processing of geographical data that uses mainly GRASS GIS for computational tasks (DOI: https://doi.org/10.5281/zenodo.5879231)
Stars: ✭ 41 (+51.85%)
Mutual labels: geospatial-analysis, grass-gis
Opensource OBIA processing chain
An open-source semi-automated processing chain for urban OBIA classification.
Stars: ✭ 75 (+177.78%)
Mutual labels: grass-gis
Deck.gl
WebGL2 powered visualization framework
Stars: ✭ 9,304 (+34359.26%)
Mutual labels: geospatial-analysis
community-sprints
This repo is used to organize and collaborate in sprints for code projects, hackathons, STAC and metadata specs development
Stars: ✭ 18 (-33.33%)
Mutual labels: geospatial-analysis
uav-lidar-analytics-course
NCSU GIS595/MEA792: UAV/lidar Data Analytics
Stars: ✭ 23 (-14.81%)
Mutual labels: grass-gis
glaes
Geospatial Land Availability for Energy Systems
Stars: ✭ 27 (+0%)
Mutual labels: geospatial-analysis
geospatial-modeling-course
NCSU GIS/MEA582: Geospatial Modeling and Analysis Course
Stars: ✭ 30 (+11.11%)
Mutual labels: grass-gis
Data-Science-Sandbox
Code and resources to serve as a starting point for data science projects.
Stars: ✭ 14 (-48.15%)
Mutual labels: geospatial-analysis
geovoronoi
a package to create and plot Voronoi regions within geographic boundaries
Stars: ✭ 106 (+292.59%)
Mutual labels: geospatial-analysis
python-geospatial-analysis-cookbook
Over 60 recipes to work with topology, overlays and indoor routing
Stars: ✭ 105 (+288.89%)
Mutual labels: geospatial-analysis
2019 egu workshop jupyter notebooks
Short course on interactive analysis of Big Earth Data with Jupyter Notebooks
Stars: ✭ 29 (+7.41%)
Mutual labels: geospatial-analysis
xyz-spaces-python
Manage your XYZ Hub or HERE Data Hub spaces from Python.
Stars: ✭ 29 (+7.41%)
Mutual labels: geospatial-analysis
Awesome Geospatial
Long list of geospatial tools and resources
Stars: ✭ 2,386 (+8737.04%)
Mutual labels: geospatial-analysis
LS CORRIDORS
Simulation of multiple ecological functional corridors
Stars: ✭ 20 (-25.93%)
Mutual labels: grass-gis
leafmap
A Python package for interactive mapping and geospatial analysis with minimal coding in a Jupyter environment
Stars: ✭ 1,299 (+4711.11%)
Mutual labels: geospatial-analysis
gismanager
Publish Your GIS Data(Vector Data) to PostGIS and Geoserver
Stars: ✭ 45 (+66.67%)
Mutual labels: osgeo
deegree3
Official deegree repository providing geospatial core libraries, data access and advanced OGC web service implementations
Stars: ✭ 118 (+337.04%)
Mutual labels: osgeo
GeoParser
Extract and Visualize location from any file
Stars: ✭ 48 (+77.78%)
Mutual labels: geospatial-analysis
GRASS GIS Development Subversion repository ########################################################## How to get write access here? Write access is only granted to developers who agree to abide by RFC2 - Legal aspects of code contributions http://trac.osgeo.org/grass/wiki/RFC/2_LegalAspectsOfCodeContributions and the code submission guidelines http://trac.osgeo.org/grass/wiki/Submitting This needs to be communicated to a GRASS developer. S/he will then possibly propose you to the GRASS Project Steering committee after a period of evaluation. For details, see http://trac.osgeo.org/grass/wiki/RFC Once write access is granted, you, the new developer need to obtain an "osgeo_id" at http://www.osgeo.org/osgeo_userid If you already have an "osgeo_id" but forgot it, search for it at Search at http://www.osgeo.org/cgi-bin/ldap_web_search.py ########################################################## How to compile GRASS: See INSTALL file. Yes, you should really read INSTALL. ########################################################################## How to generate the '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 An online version is available at: https://grass.osgeo.org/programming7/ ## Docker Build using the downloaded source code (in the directory with the source code): docker build -t grassgis77 . A test run (assuming you have existing GRASS GIS location; it can be downloaded from https://grass.osgeo.org/sampledata/north_carolina/nc_basic_spm_grass7.zip) # 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/ grassgis77 \ grass --text nc_spm_08_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/ grassgis77 \ grass /data/nc_basic_spm/PERMANENT --exec g.region -p Note that the first `grassgis77` 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 \ grassgis77 grass /data/nc_basic_spm/PERMANENT --exec \ python -m grass.gunittest.main \ --location nc_basic_spm --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
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].