GRASS-Wiki - User contributions [en]

GRASS GIS Jupyter notebooks

2026-05-15T17:15:44Z

Annakrat: Remove outdated information

A Jupyter Notebook is a web application that allows you to create and share documents that contain scripts and code, equations, visualizations and explanatory text, combined.

== Get started ==
Read [https://grass.osgeo.org/grass-stable/manuals/jupyter_intro.html GRASS Jupyter Notebooks Introduction].
Try [https://grass-tutorials.osgeo.org/content/tutorials/get_started/fast_track_grass_and_python.html Get started with GRASS & Python in Jupyter Notebooks] official tutorial. Browse additional [https://grass-tutorials.osgeo.org/ tutorials].

== List of selected GRASS Jupyter notebooks ==
Note that the following list is community contributed and the notebooks may contain outdated information and old GRASS API usage. For up-to-date notebooks, see GRASS official [https://grass-tutorials.osgeo.org/ tutorial page].

'''Intro notebooks:'''
* [https://github.com/OSGeo/grass/blob/main/doc/notebooks Official notebooks in OSGeo/grass repo] ([https://mybinder.org/v2/gh/OSGeo/grass/main?urlpath=lab%2Ftree%2Fdoc%2Fnotebooks%2Fjupyter_example.ipynb jupyter_example.ipynb on Binder])
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-foss4g-2022 Unleash the power of GRASS GIS with Jupyter (FOSS4G 2022 workshop)]
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-FOSS4G-2021 GRASS GIS: From Beginner to Power User (FOSS4G 2021 workshop)]
* [https://github.com/wenzeslaus/try-grass-in-jupyter-with-bash wenzeslaus/try-grass-in-jupyter-with-bash] (experimental)
* NSF platform: https://wholetale.org/
** GRASS GIS Introduction, by Anna Petrasova: https://dashboard.wholetale.org/run/63d832bab4a0197e9a9ecdad?tab=files

'''Windows related:'''
* [https://github.com/ncsu-geoforall-lab/GIS714-assignments/blob/main/GRASS_GIS_Foundations/JupyterOnWindows_standalone_Tutorial.ipynb GRASS GIS Jupyter Notebooks on Windows standalone installer tutorial]
* [https://github.com/ncsu-geoforall-lab/GIS714-assignments/blob/main/GRASS_GIS_Foundations/JupyterOnWindows_OSGeo4W_Tutorial.ipynb GRASS GIS Jupyter Notebooks on Windows with OSGeo4W]

'''Mac related:'''
* [https://github.com/ncsu-geoforall-lab/GIS714-assignments/blob/main/GRASS_GIS_Foundations/JupyterOnMac_Tutorial.ipynb GRASS GIS Jupyter Notebooks on Mac]

'''Workbook Collections:'''
* [https://github.com/wenzeslaus/geospatial-modeling-course-jupyter/tree/master/notebooks 14 Jupyter Notebooks for learning geospatial analysis and modeling with GRASS GIS] (Python and command line versions)

'''Species Distribution Modeling:'''
* NSF platform: https://wholetale.org/
** Using satellite data for Species Distribution Modeling with GRASS GIS and R, by Veronica Andreo https://dashboard.wholetale.org/run/64388157b3b74e434bd8f1ac?tab=files

'''Image processing/OBIA:'''
* [https://github.com/veroandreo/foss4g2022_grass4rs GRASS GIS for remote sensing data processing and analysis]
* [https://github.com/neteler/jupyter_sentinel2_grass_gis GRASS GIS 8 and processing of multitemporal EO data]
* [https://github.com/tgrippa/Opensource_OBIA_processing_chain An open-source semi-automated processing chain for urban OBIA classification]

'''Python and PyGRASS:'''
* [https://github.com/zarch/workshop-pygrass Workshop on PyGRASS using IPython notebook]
* [https://github.com/wenzeslaus/foss4g-2022-developing-custom-grass-tools Developing custom GRASS tools (FOSS4G 2022 workshop)]
* [https://github.com/wenzeslaus/python-grass-addon How to write a Python GRASS GIS 7 addon (FOSS4G Europe 2015 workshop)]
* [https://github.com/lucadelu/docker-stacks/tree/geospatial/geospatial-notebook Jupyter Notebook Geospatial Python Stack]

'''R and GRASS GIS:'''
* [https://gist.github.com/joergsteinkamp/43fb13a82aeab9b5c0dcc4433f97f1a6 Simple Opensource GIS examples with GRASS GIS and R]

'''Wildfire Modeling:'''
* [https://github.com/acoiman/wildfire_modeling Wildfire Modeling in Yosemite National Park]

[[Category: Documentation]]
[[Category: Python]]

FUTURES tutorial

2026-05-14T16:46:33Z

Annakrat: small updates

[https://grass.osgeo.org/grass-stable/manuals/addons/r.futures.html r.futures.*] is an implementation of FUTure Urban-Regional Environment Simulation (FUTURES)
which is a model for multilevel simulations of emerging urban-rural landscape structure.
FUTURES produces regional projections of landscape patterns using coupled submodels that integrate nonstationary
drivers of land change: per capita demand (DEMAND submodel), site suitability (POTENTIAL submodel),
and the spatial structure of conversion events (PGA submodel).

This tutorial shows how to prepare data and run the model. You can download [http://fatra.cnr.ncsu.edu/futures/FUTURES_triangle.zip sample dataset] and simulate urban growth
in [https://en.wikipedia.org/wiki/Research_Triangle The Triangle], region in the Piedmont of North Carolina in the United States with rapidly growing cities Raleigh, Durham and Chapel Hill.

= Prerequisites =

This tutorial requires basic knowledge of GRASS GIS. If you haven't used GRASS GIS before, you may want to first go through some of the introductory tutorials or alternative workshops linked from the [[#See also|See also section]].

= Software =
Required software includes:
* GRASS GIS
* addons
** {{AddonCmd|r.futures.simulation}}
** {{AddonCmd|r.futures.potential}}
** {{AddonCmd|r.futures.demand}}
** {{AddonCmd|r.futures.devpressure}}
** {{AddonCmd|r.sample.category}}
* R (≥ 3.0.2) - needed for {{AddonCmd|r.futures.potential}}
* SciPy - useful for {{AddonCmd|r.futures.demand}}

= Input data used in this tutorial =
Download [http://fatra.cnr.ncsu.edu/futures/FUTURES_triangle.zip sample dataset] containing:
* digital elevation model ([http://nationalmap.gov/elevation.html NED])
* [http://www.mrlc.gov/ NLCD] 2001, 2011
* NLCD 1992/2001 Retrofit Land Cover Change Product
* transportation network ([http://www.census.gov/geo/maps-data/data/tiger-line.html TIGER])
* county boundaries ([http://www.census.gov/geo/maps-data/data/tiger-line.html TIGER])
* protected areas ([http://www.conservationgateway.org/ConservationByGeography/NorthAmerica/UnitedStates/edc/reportsdata/terrestrial/secured/Pages/default.aspx Secured Lands])
* cities above 20000 (USGS)
* county population past estimates and future projections ([https://www.osbm.nc.gov/demog/county-projections NC OSBM]) per county (nonspatial)

= Workflow =
Download sample data and unzip it. Create <tt>grassdata</tt> directory on your disk (or use the one you already have) and move there Location <tt>futures_ncspm</tt>.
Launch GRASS GIS and select your <tt>grassdata</tt> directory, Location <tt>futures_ncspm</tt> and Mapset <tt>practice1</tt>.

Install addons:
<source lang="bash">
g.extension r.futures
g.extension r.sample.category
</source>

Close GUI and restart it:
<source lang="bash">
g.gui
</source>

To install the required R packages, go to the command line terminal which was started with GRASS GIS and R:

<source lang="bash">
R
</source>

This starts the R command line where you need to execute the following code (and go through any dialogs about installation if R shows them):

<source lang="R">
install.packages(c("MuMIn", "lme4", "optparse", "rgrass7"))
</source>

== Initial steps and data preparation ==
First we will set computational region of our analyses to an extent covering our study area and so that the cells are aligned with one of our landuse rasters:
<source lang="bash">g.region raster=landuse_2011 -p</source>

We will derive urbanized areas from NLCD dataset for year 1992, 2001 and 2011
by extracting categories category 21 - 24 into a new binary map where developed is 1,
undeveloped 0 and NULL (no data) is area unsuitable for development (water, wetlands, protected areas).
First we will convert protected areas from vector to raster and set
NULLs to zeros (for simpler raster algebra expression in the next step):

<source lang="bash">
v.to.rast input=protected_areas output=protected_areas use=val
r.null map=protected_areas null=0
</source>

And then create rasters of developed/undeveloped areas using raster algebra:

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.mapcalc "urban_1992 = if(landuse_1992 >= 21 && landuse_1992 <= 24, 1, if(landuse_1992 == 11 || landuse_1992 >= 90 || protected_areas, null(), 0))"
r.mapcalc "urban_2001 = if(landuse_2001 >= 21 && landuse_2001 <= 24, 1, if(landuse_2001 == 11 || landuse_2001 >= 90 || protected_areas, null(), 0))"
r.mapcalc "urban_2011 = if(landuse_2011 >= 21 && landuse_2011 <= 24, 1, if(landuse_2011 == 11 || landuse_2011 >= 90 || protected_areas, null(), 0))"
</source>

We will convert vector counties to raster with the values of the FIPS attribute which links to population file:

<source lang="bash">
v.to.rast input=counties type=area use=attr attribute_column=FIPS output=counties
</source>

If we need to run FUTURES only for smaller number of counties, we can extract them based on the identifier:

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
v.to.rast input=counties type=area where="FIPS in (37183, 37101)" use=attr attribute_column=FIPS output=counties_subset
</source>

Before further steps, we will set our working directory so that the input population files and text files
we are going to create are saved in one directory and easily accessible.
You can do that from menu ''Settings'' → ''GRASS working environment'' → ''Change working directory''.
Select (or create) a directory and move there the downloaded files <tt>population_projection.csv</tt> and <tt>population_trend.csv</tt>.

== Potential submodel ==
Module {{AddonCmd|r.futures.potential}} implements POTENTIAL submodel as a part of FUTURES land change model. POTENTIAL is implemented using a set of coefficients that relate a selection of site suitability factors to the probability of a place becoming developed. This is implemented using the parameter table in combination with maps of those site suitability factors (mapped predictors). The coefficients are obtained by conducting multilevel logistic regression in R with package lme4 where the coefficients may vary by county. The best model is selected automatically using dredge function from package [https://cran.r-project.org/web/packages/MuMIn/index.html MuMIn].

First, we will derive couple of predictors.
=== Predictors ===
==== Slope ====
We will derive slope in degrees from digital elevation model using {{cmd|r.slope.aspect}} module:
<source lang="bash">r.slope.aspect elevation=elevation_30m slope=slope</source>

==== Distance from lakes/rivers ====
First we will extract [http://www.mrlc.gov/nlcd11_leg.php category ''Open Water''] from 2011 NLCD dataset:
<source lang="bash">
r.mapcalc "water = if(landuse_2011 == 11, 1, null())"
</source>

Then we compute the distance to water with module {{cmd|r.grow.distance}} and set color table to shades of blue:
<source lang="bash">
r.grow.distance input=water distance=dist_to_water
r.colors -n map=dist_to_water color=blues
</source>

==== Distance from protected areas ====
We will use raster protected of protected areas we already created, but we will set NULL values to zero.
We compute the distance to protected areas with module {{cmd|r.grow.distance}} and set color table from green to red:
<source lang="bash">
r.null map=protected_areas setnull=0
r.grow.distance input=protected_areas distance=dist_to_protected
r.colors map=dist_to_protected color=gyr
</source>

==== Forests ====
We will smooth the transition between forest and other land use, see NLCD [http://www.mrlc.gov/nlcd11_leg.php category ''Open Water'']:
<source lang="bash">
r.mapcalc "forest = if(landuse_2011 >= 41 && landuse_2011 <= 43, 1, 0)"
r.neighbors -c input=forest output=forest_smooth size=15 method=average
r.colors map=forest_smooth color=ndvi
</source>

==== Travel time to cities ====
Here we will compute travel time to cities (> population 20000)
as cumulative cost distance where cost is defined as travel time on roads.
First we specify the speed on different types of roads.
We copy the roads raster into our mapset so that we can change it
by adding a new attribute field <tt>speed</tt>. Then we assign speed values (km/h) based on the type of road:

<source lang="bash">
g.copy vector=roads,myroads
v.db.addcolumn map=myroads columns="speed double precision"
v.db.update map=myroads column=speed value=50 where="MTFCC = 'S1400'"
v.db.update map=myroads column=speed value=100 where="MTFCC IN ('S1100', 'S1200')"
</source>

Now we rasterize the selected road types using the speed values from the attribute table as raster values.

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
v.to.rast input=myroads type=line where="MTFCC IN ('S1100', 'S1200', 'S1400')" output=roads_speed use=attr attribute_column=speed
</source>

We set the rest of the area to low speed and recompute the speed as time to travel through a 30m cell in minutes:

<source lang="bash">
r.null map=roads_speed null=5
r.mapcalc "roads_travel_time = 1.8 / roads_speed"
</source>

Finally we compute the travel time to larger cities using {{cmd|r.cost}}:

<source lang="bash">
r.cost input=roads_travel_time output=travel_time_cities start_points=cities_20000 memory=3000
r.colors map=travel_time_cities color=byr
</source>

==== Road density ====
We will rasterize roads and use moving window analysis ({{cmd|r.neighbors}}) to compute road density:

<source lang="bash">
v.to.rast input=roads output=roads use=val
r.null map=roads null=0
r.neighbors -c input=roads output=road_dens size=25 method=average nprocs=4
</source>

==== Distance to interchanges ====

We will consider TIGER roads of type <tt>Ramp</tt> as interchanges, rasterize them and compute euclidean distance to them:

<source lang="bash">
v.to.rast input=roads type=line where="MTFCC = 'S1630'" output=interchanges use=val
r.grow.distance -m input=interchanges distance=dist_interchanges
</source>

=== Development pressure ===

We compute development pressure with {{AddonCmd|r.futures.devpressure}}. Development pressure is a predictor based on number of neighboring developed cells within search distance, weighted by distance. The development pressure variable plays a special role in the model, allowing for a feedback between predicted change and change in subsequent steps.

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.devpressure -n input=urban_2011 output=devpressure_1 method=gravity size=10 gamma=1 scaling_factor=1
r.futures.devpressure -n input=urban_2011 output=devpressure_0_5 method=gravity size=30 gamma=0.5 scaling_factor=0.1
</source>

When gamma increases, development influence decreases more rapidly with distance.
Size is half the size of the moving window. When gamma is low, local development influences more distant places.
We will derive 2 layers with different gamma and size parameters for the potential statistical model.

=== Rescaling variables ===

First we will look at the ranges of our predictor variables by running a short Python code snippet in Python tab in GUI:

<source lang="python" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
for name in ['slope', 'dist_to_water', 'dist_to_protected', 'forest_smooth', 'travel_time_cities', 'road_dens', 'dist_interchanges', 'devpressure_0_5', 'devpressure_1']:
minmax = grass.raster_info(name)
print name, minmax['min'], minmax['max']
</source>

We will rescale some of our input variables:

<source lang="bash">
r.mapcalc "dist_to_water_km = dist_to_water / 1000"
r.mapcalc "dist_to_protected_km = dist_to_protected / 1000"
r.mapcalc "dist_interchanges_km = dist_interchanges / 1000"
r.mapcalc "road_dens_perc = road_dens * 100"
r.mapcalc "forest_smooth_perc = forest_smooth * 100"
</source>

=== Sampling ===
To sample only in the analyzed counties, we will clip development layer:

<source lang="bash">
r.mapcalc "urban_2011_clip = if(counties, urban_2011)"
</source>

To estimate the number of sampling points, we can use {{cmd|r.report}} to report number of developed/undeveloped cells and their ratio.

<source lang="bash">
r.report map=urban_2011 units=h,c,p
</source>

We will sample the predictors and the response variable with 10000 random points in undeveloped areas and 2000 points in developed area:

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.sample.category input=urban_2011_clip output=sampling sampled=counties,devpressure_0_5,devpressure_1,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,dist_to_protected_km,dist_interchanges_km,travel_time_cities npoints=10000,2000
</source>

The attribute table can be exported as CSV file (not necessary step):

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
v.db.select map=sampling columns=urban_2011_clip,counties,devpressure_0_5,devpressure_1,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,dist_to_protected_km,dist_interchanges_km,travel_time_cities separator=comma file=samples.csv
</source>

=== Development potential ===
Now we find best model for predicting urbanization using {{AddonCmd|r.futures.potential}} which wraps an R script.

We can play with different combinations of predictors, for example:

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.potential input=sampling output=potential.csv columns=devpressure_0_5,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties
r.futures.potential input=sampling output=potential.csv columns=devpressure_1,road_dens_perc,dist_to_water_km,dist_to_protected_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties
</source>

Or we can run R [http://www.inside-r.org/packages/cran/MuMIn/docs/dredge dredge] function to find "best" model. We can specify minimum and maximum number of predictors the final model should use.
<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.potential -d input=sampling output=potential.csv columns=devpressure_1,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,dist_to_protected_km,dist_interchanges_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties min_variables=4 max_variables=7
</source>

You can then open the output file <tt>potential.csv</tt>, which is a CSV file with tabs as separators.

For this tutorial, the final potential is created with:
<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.potential input=sampling output=potential.csv columns=devpressure_1,slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties --o
</source>

== Demand submodel ==
First we will mask out roads so that they don't influence into per capita land demand relation.
<source lang="bash">
v.to.rast input=roads type=line output=roads_mask use=val
r.mask roads_mask -i
</source>

We will use {{AddonCmd|r.futures.demand}} which derives the population vs. development relation. The relation can be linear/logarithmic/logarithmic2/exponential/exponential approach.
Look for examples of the different relations in the manual.

* linear: y = A + Bx
* logarithmic: y = A + Bln(x)
* logarithmic2: y = A + B * ln(x - C)        (requires SciPy)
* exponential: y = Ae^(BX)
* exp_approach: y = (1 - e^(-A(x - B))) + C        (requires SciPy)

The format of the input population CSV files is described in the manual. It is important to have synchronized categories of subregions and the column headers of the CSV files (in our case FIPS number). How to simply generate the list of years (for which demand is computed) is described in {{AddonCmd|r.futures.demand}} manual, for example run this in Python console:

<source lang="python">
','.join([str(i) for i in range(2011, 2036)])
</source>

Then we can create the DEMAND file:
<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.demand development=urban_1992,urban_2001,urban_2011 subregions=counties observed_population=population_trend.csv projected_population=population_projection.csv simulation_times=2011,2012,2013,2014,2015,2016,2017,2018,2019,2020,2021,2022,2023,2024,2025,2026,2027,2028,2029,2030,2031,2032,2033,2034,2035 plot=plot_demand.pdf demand=demand.csv separator=comma
</source>

In your current working directory, you should find files <tt>plot_demand.png</tt> and <tt>demand.csv</tt>.

If you have SciPy installed, you can experiment with other methods for fitting the functions:
<source lang="bash">
r.futures.demand ... method=logarithmic2
r.futures.demand ... method=exp_approach
</source>
If necessary, you can create a set of demand files produced by fitting each method separately and
then pick for each county the method which seems best and manually create a new demand file.

When you are finished, remove the mask as it is not needed for the next steps.
<source lang="bash">
r.mask -r
</source>

== Patch calibration ==
Patch calibration can be a very time consuming computation.
First we derive patches of new development by comparing historical and latest development.
We can run this on the entire area and keep only patches with minimum size 2 cells (1800 = 2 x 30 x 30 m).

<source lang="bash">
r.futures.calib development_start=urban_1992 development_end=urban_2011 subregions=counties patch_sizes=patches.txt patch_threshold=1800 -l
</source>
We obtained a file <tt>patches.txt</tt> (used later in the PGA) - a patch size distribution file - containing sizes of all found patches.

We can look at the distribution of the patch sizes:

<source lang="python">
from matplotlib import pyplot as plt
with open('patches.txt') as f:
patches = [int(patch) for patch in f.readlines()]
plt.hist(patches, 2000)
plt.xlim(0,50)
plt.show()
</source>

At this point, we start the calibration to get best parameters of patch shape
(for this tutorial, this step can be skipped and the suggested parameters are used).
First we select only one county to

<source lang="bash">
v.to.rast input=counties type=area where="FIPS == 37183" use=attr attribute_column=FIPS output=calib_county
g.region raster=calib_county zoom=calib_county
</source>

<source lang="bash"
style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.calib development_start=urban_1992 development_end=urban_2011 subregions=calib_county patch_sizes=patches.txt calibration_results=calib.csv patch_threshold=1800 repeat=5 compactness_mean=0.1,0.3,0.5,0.7,0.9 compactness_range=0.1,0.05 discount_factor=0.1,0.3,0.5,0.7,0.9 predictors=slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities demand=demand.csv devpot_params=potential.csv num_neighbors=4 seed_search=probability development_pressure=devpressure_1 development_pressure_approach=gravity n_dev_neighbourhood=10 gamma=1 scaling_factor=1 --o
</source>

== FUTURES simulation ==
We will switch back to our previous region:
<source lang="bash">
g.region raster=landuse_2011 -p
</source>

Now we have all the inputs necessary for running {{AddonCmd|r.futures.simulation}}:

The entire command is here:
<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.simulation subregions=counties developed=urban_2011 predictors=slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities devpot_params=potential.csv development_pressure=devpressure_1 n_dev_neighbourhood=10 development_pressure_approach=gravity gamma=1 scaling_factor=1 demand=demand.csv discount_factor=0.3 compactness_mean=0.2 compactness_range=0.1 patch_sizes=patches.txt num_neighbors=4 seed_search=probability random_seed=1 output=final output_series=final
</source>

=== Quick description ===
The command parameters and their values:
* raster map of counties with their categories
<code>
... subregions=counties ...
</code>

* raster of developed (1), undeveloped (0) and NULLs for undevelopable areas
<code>
... developed=urban_2011 ...
</code>

* predictors selected with {{AddonCmd|r.futures.potential}} and their coefficients in a <tt>potential.csv</tt> file. The order of predictors must match the order in the file and the categories of the counties must match raster <tt>counties</tt>.
<code>
... predictors=slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities devpot_params=potential.csv ...
</code>

* initial development pressure computed by {{AddonCmd|r.futures.devpressure}}, it's important to set here the same parameters
<code>
... development_pressure=devpressure_1 n_dev_neighbourhood=10 development_pressure_approach=gravity gamma=1 scaling_factor=1 ...
</code>

* per capita land demand computed by {{AddonCmd|r.futures.demand}}, the categories of the counties must match raster <tt>counties</tt>.
<code>
... demand=demand.csv ...
</code>

* patch parameters from the calibration step
<code>
... discount_factor=0.3 compactness_mean=0.4 compactness_range=0.08 patch_sizes=patches.txt ...
</code>

* recommended parameters for patch growing algorithm
<code>
... num_neighbors=4 seed_search=probability ...
</code>

* set random seed for repeatable results or set flag <tt>-s</tt> to generate seed automatically
<code>
... random_seed=1 ...
</code>

* specify final output map and optionally basename for intermediate raster maps
<code>
output=final output_series=final
</code>

=== Scenarios ===

Scenarios involving policies that encourage infill versus sprawl can be explored using the <tt>incentive_power</tt> parameter,
which uses a power function to transform the evenness of the probability gradient in POTENTIAL.

The default value is 1. You can change the power to a number between 0.25 and 4 to test urban sprawl/infill scenarios.
Higher power leads to infill behavior, lower power to urban sprawl.

= Postprocessing =

Follow a [[Creating_animation_from_FUTURES_output_in_GRASS_GIS| tutorial how to make an animation from the results]].

= See also =

* [[From GRASS GIS novice to power user (workshop at FOSS4G Boston 2017)]]
* [[Unleash the power of GRASS GIS at US-IALE 2017]]
* [[Workshop on urban growth modeling with FUTURES]]
* [[R statistics|GRASS GIS and R]]
* [[GRASS Location Wizard]]

[[Category: Tutorial]]
[[Category: FUTURES]]
[[Category: Urban]]

FUTURES tutorial

2026-05-14T16:41:45Z

Annakrat: /* Travel time to cities */

[https://grass.osgeo.org/grass-stable/manuals/addons/r.futures.html r.futures.*] is an implementation of FUTure Urban-Regional Environment Simulation (FUTURES)
which is a model for multilevel simulations of emerging urban-rural landscape structure.
FUTURES produces regional projections of landscape patterns using coupled submodels that integrate nonstationary
drivers of land change: per capita demand (DEMAND submodel), site suitability (POTENTIAL submodel),
and the spatial structure of conversion events (PGA submodel).

This tutorial shows how to prepare data and run the model. You can download [http://fatra.cnr.ncsu.edu/futures/FUTURES_triangle.zip sample dataset] and simulate urban growth
in [https://en.wikipedia.org/wiki/Research_Triangle The Triangle], region in the Piedmont of North Carolina in the United States with rapidly growing cities Raleigh, Durham and Chapel Hill.

= Prerequisites =

This tutorial requires basic knowledge of GRASS GIS. If you haven't used GRASS GIS before, you may want to first go through some of the introductory tutorials or alternative workshops linked from the [[#See also|See also section]].

= Software =
Required software includes:
* GRASS GIS 7
* addons
** {{AddonCmd|r.futures.pga}}
** {{AddonCmd|r.futures.potential}}
** {{AddonCmd|r.futures.demand}}
** {{AddonCmd|r.futures.devpressure}}
** {{AddonCmd|r.sample.category}}
* R (≥ 3.0.2) - needed for {{AddonCmd|r.futures.potential}}
* SciPy - useful for {{AddonCmd|r.futures.demand}}

= Input data used in this tutorial =
Download [http://fatra.cnr.ncsu.edu/futures/FUTURES_triangle.zip sample dataset] containing:
* digital elevation model ([http://nationalmap.gov/elevation.html NED])
* [http://www.mrlc.gov/ NLCD] 2001, 2011
* NLCD 1992/2001 Retrofit Land Cover Change Product
* transportation network ([http://www.census.gov/geo/maps-data/data/tiger-line.html TIGER])
* county boundaries ([http://www.census.gov/geo/maps-data/data/tiger-line.html TIGER])
* protected areas ([http://www.conservationgateway.org/ConservationByGeography/NorthAmerica/UnitedStates/edc/reportsdata/terrestrial/secured/Pages/default.aspx Secured Lands])
* cities above 20000 (USGS)
* county population past estimates and future projections ([https://www.osbm.nc.gov/demog/county-projections NC OSBM]) per county (nonspatial)

= Workflow =
Download sample data and unzip it. Create <tt>grassdata</tt> directory on your disk (or use the one you already have) and move there Location <tt>futures_ncspm</tt>.
Launch GRASS GIS and select your <tt>grassdata</tt> directory, Location <tt>futures_ncspm</tt> and Mapset <tt>practice1</tt>.

Install addons:
<source lang="bash">
g.extension r.futures
g.extension r.sample.category
</source>

Close GUI and restart it:
<source lang="bash">
g.gui
</source>

To install the required R packages, go to the command line terminal which was started with GRASS GIS and R:

<source lang="bash">
R
</source>

This starts the R command line where you need to execute the following code (and go through any dialogs about installation if R shows them):

<source lang="R">
install.packages(c("MuMIn", "lme4", "optparse", "rgrass7"))
</source>

== Initial steps and data preparation ==
First we will set computational region of our analyses to an extent covering our study area and so that the cells are aligned with one of our landuse rasters:
<source lang="bash">g.region raster=landuse_2011 -p</source>

We will derive urbanized areas from NLCD dataset for year 1992, 2001 and 2011
by extracting categories category 21 - 24 into a new binary map where developed is 1,
undeveloped 0 and NULL (no data) is area unsuitable for development (water, wetlands, protected areas).
First we will convert protected areas from vector to raster and set
NULLs to zeros (for simpler raster algebra expression in the next step):

<source lang="bash">
v.to.rast input=protected_areas output=protected_areas use=val
r.null map=protected_areas null=0
</source>

And then create rasters of developed/undeveloped areas using raster algebra:

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.mapcalc "urban_1992 = if(landuse_1992 >= 21 && landuse_1992 <= 24, 1, if(landuse_1992 == 11 || landuse_1992 >= 90 || protected_areas, null(), 0))"
r.mapcalc "urban_2001 = if(landuse_2001 >= 21 && landuse_2001 <= 24, 1, if(landuse_2001 == 11 || landuse_2001 >= 90 || protected_areas, null(), 0))"
r.mapcalc "urban_2011 = if(landuse_2011 >= 21 && landuse_2011 <= 24, 1, if(landuse_2011 == 11 || landuse_2011 >= 90 || protected_areas, null(), 0))"
</source>

We will convert vector counties to raster with the values of the FIPS attribute which links to population file:

<source lang="bash">
v.to.rast input=counties type=area use=attr attribute_column=FIPS output=counties
</source>

If we need to run FUTURES only for smaller number of counties, we can extract them based on the identifier:

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
v.to.rast input=counties type=area where="FIPS in (37183, 37101)" use=attr attribute_column=FIPS output=counties_subset
</source>

Before further steps, we will set our working directory so that the input population files and text files
we are going to create are saved in one directory and easily accessible.
You can do that from menu ''Settings'' → ''GRASS working environment'' → ''Change working directory''.
Select (or create) a directory and move there the downloaded files <tt>population_projection.csv</tt> and <tt>population_trend.csv</tt>.

== Potential submodel ==
Module {{AddonCmd|r.futures.potential}} implements POTENTIAL submodel as a part of FUTURES land change model. POTENTIAL is implemented using a set of coefficients that relate a selection of site suitability factors to the probability of a place becoming developed. This is implemented using the parameter table in combination with maps of those site suitability factors (mapped predictors). The coefficients are obtained by conducting multilevel logistic regression in R with package lme4 where the coefficients may vary by county. The best model is selected automatically using dredge function from package [https://cran.r-project.org/web/packages/MuMIn/index.html MuMIn].

First, we will derive couple of predictors.
=== Predictors ===
==== Slope ====
We will derive slope in degrees from digital elevation model using {{cmd|r.slope.aspect}} module:
<source lang="bash">r.slope.aspect elevation=elevation_30m slope=slope</source>

==== Distance from lakes/rivers ====
First we will extract [http://www.mrlc.gov/nlcd11_leg.php category ''Open Water''] from 2011 NLCD dataset:
<source lang="bash">
r.mapcalc "water = if(landuse_2011 == 11, 1, null())"
</source>

Then we compute the distance to water with module {{cmd|r.grow.distance}} and set color table to shades of blue:
<source lang="bash">
r.grow.distance input=water distance=dist_to_water
r.colors -n map=dist_to_water color=blues
</source>

==== Distance from protected areas ====
We will use raster protected of protected areas we already created, but we will set NULL values to zero.
We compute the distance to protected areas with module {{cmd|r.grow.distance}} and set color table from green to red:
<source lang="bash">
r.null map=protected_areas setnull=0
r.grow.distance input=protected_areas distance=dist_to_protected
r.colors map=dist_to_protected color=gyr
</source>

==== Forests ====
We will smooth the transition between forest and other land use, see NLCD [http://www.mrlc.gov/nlcd11_leg.php category ''Open Water'']:
<source lang="bash">
r.mapcalc "forest = if(landuse_2011 >= 41 && landuse_2011 <= 43, 1, 0)"
r.neighbors -c input=forest output=forest_smooth size=15 method=average
r.colors map=forest_smooth color=ndvi
</source>

==== Travel time to cities ====
Here we will compute travel time to cities (> population 20000)
as cumulative cost distance where cost is defined as travel time on roads.
First we specify the speed on different types of roads.
We copy the roads raster into our mapset so that we can change it
by adding a new attribute field <tt>speed</tt>. Then we assign speed values (km/h) based on the type of road:

<source lang="bash">
g.copy vector=roads,myroads
v.db.addcolumn map=myroads columns="speed double precision"
v.db.update map=myroads column=speed value=50 where="MTFCC = 'S1400'"
v.db.update map=myroads column=speed value=100 where="MTFCC IN ('S1100', 'S1200')"
</source>

Now we rasterize the selected road types using the speed values from the attribute table as raster values.

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
v.to.rast input=myroads type=line where="MTFCC IN ('S1100', 'S1200', 'S1400')" output=roads_speed use=attr attribute_column=speed
</source>

We set the rest of the area to low speed and recompute the speed as time to travel through a 30m cell in minutes:

<source lang="bash">
r.null map=roads_speed null=5
r.mapcalc "roads_travel_time = 1.8 / roads_speed"
</source>

Finally we compute the travel time to larger cities using {{cmd|r.cost}}:

<source lang="bash">
r.cost input=roads_travel_time output=travel_time_cities start_points=cities_20000 memory=3000
r.colors map=travel_time_cities color=byr
</source>

==== Road density ====
We will rasterize roads and use moving window analysis ({{cmd|r.neighbors}}) to compute road density:

<source lang="bash">
v.to.rast input=roads output=roads use=val
r.null map=roads null=0
r.neighbors -c input=roads output=road_dens size=25 method=average
</source>

==== Distance to interchanges ====

We will consider TIGER roads of type <tt>Ramp</tt> as interchanges, rasterize them and compute euclidean distance to them:

<source lang="bash">
v.to.rast input=roads type=line where="MTFCC = 'S1630'" output=interchanges use=val
r.grow.distance -m input=interchanges distance=dist_interchanges
</source>

=== Development pressure ===

We compute development pressure with {{AddonCmd|r.futures.devpressure}}. Development pressure is a predictor based on number of neighboring developed cells within search distance, weighted by distance. The development pressure variable plays a special role in the model, allowing for a feedback between predicted change and change in subsequent steps.

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.devpressure -n input=urban_2011 output=devpressure_1 method=gravity size=10 gamma=1 scaling_factor=1
r.futures.devpressure -n input=urban_2011 output=devpressure_0_5 method=gravity size=30 gamma=0.5 scaling_factor=0.1
</source>

When gamma increases, development influence decreases more rapidly with distance.
Size is half the size of the moving window. When gamma is low, local development influences more distant places.
We will derive 2 layers with different gamma and size parameters for the potential statistical model.

=== Rescaling variables ===

First we will look at the ranges of our predictor variables by running a short Python code snippet in Python tab in GUI:

<source lang="python" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
for name in ['slope', 'dist_to_water', 'dist_to_protected', 'forest_smooth', 'travel_time_cities', 'road_dens', 'dist_interchanges', 'devpressure_0_5', 'devpressure_1']:
minmax = grass.raster_info(name)
print name, minmax['min'], minmax['max']
</source>

We will rescale some of our input variables:

<source lang="bash">
r.mapcalc "dist_to_water_km = dist_to_water / 1000"
r.mapcalc "dist_to_protected_km = dist_to_protected / 1000"
r.mapcalc "dist_interchanges_km = dist_interchanges / 1000"
r.mapcalc "road_dens_perc = road_dens * 100"
r.mapcalc "forest_smooth_perc = forest_smooth * 100"
</source>

=== Sampling ===
To sample only in the analyzed counties, we will clip development layer:

<source lang="bash">
r.mapcalc "urban_2011_clip = if(counties, urban_2011)"
</source>

To estimate the number of sampling points, we can use {{cmd|r.report}} to report number of developed/undeveloped cells and their ratio.

<source lang="bash">
r.report map=urban_2011 units=h,c,p
</source>

We will sample the predictors and the response variable with 10000 random points in undeveloped areas and 2000 points in developed area:

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.sample.category input=urban_2011_clip output=sampling sampled=counties,devpressure_0_5,devpressure_1,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,dist_to_protected_km,dist_interchanges_km,travel_time_cities npoints=10000,2000
</source>

The attribute table can be exported as CSV file (not necessary step):

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
v.db.select map=sampling columns=urban_2011_clip,counties,devpressure_0_5,devpressure_1,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,dist_to_protected_km,dist_interchanges_km,travel_time_cities separator=comma file=samples.csv
</source>

=== Development potential ===
Now we find best model for predicting urbanization using {{AddonCmd|r.futures.potential}} which wraps an R script.

We can play with different combinations of predictors, for example:

<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.potential input=sampling output=potential.csv columns=devpressure_0_5,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties
r.futures.potential input=sampling output=potential.csv columns=devpressure_1,road_dens_perc,dist_to_water_km,dist_to_protected_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties
</source>

Or we can run R [http://www.inside-r.org/packages/cran/MuMIn/docs/dredge dredge] function to find "best" model. We can specify minimum and maximum number of predictors the final model should use.
<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.potential -d input=sampling output=potential.csv columns=devpressure_1,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,dist_to_protected_km,dist_interchanges_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties min_variables=4 max_variables=7
</source>

You can then open the output file <tt>potential.csv</tt>, which is a CSV file with tabs as separators.

For this tutorial, the final potential is created with:
<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.potential input=sampling output=potential.csv columns=devpressure_1,slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties --o
</source>

== Demand submodel ==
First we will mask out roads so that they don't influence into per capita land demand relation.
<source lang="bash">
v.to.rast input=roads type=line output=roads_mask use=val
r.mask roads_mask -i
</source>

We will use {{AddonCmd|r.futures.demand}} which derives the population vs. development relation. The relation can be linear/logarithmic/logarithmic2/exponential/exponential approach.
Look for examples of the different relations in the manual.

* linear: y = A + Bx
* logarithmic: y = A + Bln(x)
* logarithmic2: y = A + B * ln(x - C)        (requires SciPy)
* exponential: y = Ae^(BX)
* exp_approach: y = (1 - e^(-A(x - B))) + C        (requires SciPy)

The format of the input population CSV files is described in the manual. It is important to have synchronized categories of subregions and the column headers of the CSV files (in our case FIPS number). How to simply generate the list of years (for which demand is computed) is described in {{AddonCmd|r.futures.demand}} manual, for example run this in Python console:

<source lang="python">
','.join([str(i) for i in range(2011, 2036)])
</source>

Then we can create the DEMAND file:
<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.demand development=urban_1992,urban_2001,urban_2011 subregions=counties observed_population=population_trend.csv projected_population=population_projection.csv simulation_times=2011,2012,2013,2014,2015,2016,2017,2018,2019,2020,2021,2022,2023,2024,2025,2026,2027,2028,2029,2030,2031,2032,2033,2034,2035 plot=plot_demand.pdf demand=demand.csv separator=comma
</source>

In your current working directory, you should find files <tt>plot_demand.png</tt> and <tt>demand.csv</tt>.

If you have SciPy installed, you can experiment with other methods for fitting the functions:
<source lang="bash">
r.futures.demand ... method=logarithmic2
r.futures.demand ... method=exp_approach
</source>
If necessary, you can create a set of demand files produced by fitting each method separately and
then pick for each county the method which seems best and manually create a new demand file.

When you are finished, remove the mask as it is not needed for the next steps.
<source lang="bash">
r.mask -r
</source>

== Patch calibration ==
Patch calibration can be a very time consuming computation.
First we derive patches of new development by comparing historical and latest development.
We can run this on the entire area and keep only patches with minimum size 2 cells (1800 = 2 x 30 x 30 m).

<source lang="bash">
r.futures.calib development_start=urban_1992 development_end=urban_2011 subregions=counties patch_sizes=patches.txt patch_threshold=1800 -l
</source>
We obtained a file <tt>patches.txt</tt> (used later in the PGA) - a patch size distribution file - containing sizes of all found patches.

We can look at the distribution of the patch sizes:

<source lang="python">
from matplotlib import pyplot as plt
with open('patches.txt') as f:
patches = [int(patch) for patch in f.readlines()]
plt.hist(patches, 2000)
plt.xlim(0,50)
plt.show()
</source>

At this point, we start the calibration to get best parameters of patch shape
(for this tutorial, this step can be skipped and the suggested parameters are used).
First we select only one county to

<source lang="bash">
v.to.rast input=counties type=area where="FIPS == 37183" use=attr attribute_column=FIPS output=calib_county
g.region raster=calib_county zoom=calib_county
</source>

<source lang="bash"
style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.calib development_start=urban_1992 development_end=urban_2011 subregions=calib_county patch_sizes=patches.txt calibration_results=calib.csv patch_threshold=1800 repeat=5 compactness_mean=0.1,0.3,0.5,0.7,0.9 compactness_range=0.1,0.05 discount_factor=0.1,0.3,0.5,0.7,0.9 predictors=slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities demand=demand.csv devpot_params=potential.csv num_neighbors=4 seed_search=2 development_pressure=devpressure_1 development_pressure_approach=gravity n_dev_neighbourhood=10 gamma=1 scaling_factor=1 --o
</source>

== FUTURES simulation ==
We will switch back to our previous region:
<source lang="bash">
g.region raster=landuse_2011 -p
</source>

Now we have all the inputs necessary for running {{AddonCmd|r.futures.pga}}:

The entire command is here:
<source lang="bash" style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
r.futures.pga subregions=counties developed=urban_2011 predictors=slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities devpot_params=potential.csv development_pressure=devpressure_1 n_dev_neighbourhood=10 development_pressure_approach=gravity gamma=1 scaling_factor=1 demand=demand.csv discount_factor=0.3 compactness_mean=0.2 compactness_range=0.1 patch_sizes=patches.txt num_neighbors=4 seed_search=2 random_seed=1 output=final output_series=final
</source>

=== Quick description ===
The command parameters and their values:
* raster map of counties with their categories
<code>
... subregions=counties ...
</code>

* raster of developed (1), undeveloped (0) and NULLs for undevelopable areas
<code>
... developed=urban_2011 ...
</code>

* predictors selected with {{AddonCmd|r.futures.potential}} and their coefficients in a <tt>potential.csv</tt> file. The order of predictors must match the order in the file and the categories of the counties must match raster <tt>counties</tt>.
<code>
... predictors=slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities devpot_params=potential.csv ...
</code>

* initial development pressure computed by {{AddonCmd|r.futures.devpressure}}, it's important to set here the same parameters
<code>
... development_pressure=devpressure_1 n_dev_neighbourhood=10 development_pressure_approach=gravity gamma=1 scaling_factor=1 ...
</code>

* per capita land demand computed by {{AddonCmd|r.futures.demand}}, the categories of the counties must match raster <tt>counties</tt>.
<code>
... demand=demand.csv ...
</code>

* patch parameters from the calibration step
<code>
... discount_factor=0.3 compactness_mean=0.4 compactness_range=0.08 patch_sizes=patches.txt ...
</code>

* recommended parameters for patch growing algorithm
<code>
... num_neighbors=4 seed_search=2 ...
</code>

* set random seed for repeatable results or set flag <tt>-s</tt> to generate seed automatically
<code>
... random_seed=1 ...
</code>

* specify final output map and optionally basename for intermediate raster maps
<code>
output=final output_series=final
</code>

=== Scenarios ===

Scenarios involving policies that encourage infill versus sprawl can be explored using the <tt>incentive_power</tt> parameter,
which uses a power function to transform the evenness of the probability gradient in POTENTIAL.

The default value is 1. You can change the power to a number between 0.25 and 4 to test urban sprawl/infill scenarios.
Higher power leads to infill behavior, lower power to urban sprawl.

= Postprocessing =

Follow a [[Creating_animation_from_FUTURES_output_in_GRASS_GIS| tutorial how to make an animation from the results]].

= See also =

* [[From GRASS GIS novice to power user (workshop at FOSS4G Boston 2017)]]
* [[Unleash the power of GRASS GIS at US-IALE 2017]]
* [[Workshop on urban growth modeling with FUTURES]]
* [[R statistics|GRASS GIS and R]]
* [[GRASS Location Wizard]]

[[Category: Tutorial]]
[[Category: FUTURES]]
[[Category: Urban]]

GRASS Community Meeting San Michele 2026

2026-05-08T16:32:10Z

Annakrat: /* Agenda */

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

{{toc|right}}

The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

Sponsors make the event possible. Learn more about [https://grass.osgeo.org/contribute/sponsoring/ Sponsoring].

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements or likewise. The community meeting is also a get-together where supporters, contributors, power users and developers make decisions and tackle larger problems related to the project, discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. We welcome people committed to improving the GRASS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is being refined.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===

* Hybrid meeting about 8.6.0 with FHS and Jupyter in GUI updates

=== Monday, July 13 ===

* FHS
* Updating the GRASS Roadmap

=== Tuesday, July 14 ===

* GSoC (may be moved to different day)
* GeoAI

=== Wednesday, July 15 ===

* Python API review
* Plan PSC elections

=== Thursday, July 16 ===

* Reducing PR backlog

=== Friday, July 17 ===

* Address issues for 8.6.0 release

=== Saturday, July 18 ===

* Website review

=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topics'''
!'''Notes'''
|-
|1
| [[User:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
|
|
|
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|7
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|8
| [[User:Ctwhite|Corey White]]
| United States
| 11.07.
| 19.07.
| grass.jupyter, documentation, website, reviews, tutorials
|
|-
|}

Registration is free; participants cover their own travel and lodging, often with employer support — thank you. Ideally we'd reimburse everyone, and every [https://numfocus.org/donate-to-grass donation] or [https://grass.osgeo.org/contribute/sponsoring/ employer sponsorship] of the project helps us get closer.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (San Michele all'Adige–Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

== Accommodation and Costs ==

''Registration is free''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]
* Details to be communicated soon.

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''Is this a conference?''
** Talks or presentations may be included, but the purpose is to work together on the project. Among conference formats, the closest comparison would be a participatory workshop.
* ''Is this a hackathon?''
** While there is plenty of intensive coding, the meeting is not competitive. We meet to collaborate.
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users, and developers ''who want to make a meaningful contribution to the project''.
* ''What skills do I need?''
** Coding skills are not required. Contributions to documentation, tutorials, translations, website, and testing are all valuable. Practical help during the meeting, such as coordinating meals, photography, or reporting, is a real contribution too.
* ''Can I attend remotely?''
** The meeting is in-person, but everyone is welcome to use the same week for focused work on the project from wherever they are.
* ''What language is used during the meeting?''
** English is the working language, but you may hear several other languages spoken at the event.
* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.
* ''What if I can't spend time on this?''
** Can you spend money instead? [https://numfocus.org/donate-to-grass Donate to GRASS through NumFOCUS] to help keep the project going.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

GRASS Community Meeting San Michele 2026

2026-05-05T13:23:32Z

Annakrat: /* Participation */

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

{{toc|right}}

The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

Sponsors make the event possible. Learn more about [https://grass.osgeo.org/contribute/sponsoring/ Sponsoring].

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements or likewise. The community meeting is also a get-together where supporters, contributors, power users and developers make decisions and tackle larger problems related to the project, discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. We welcome people committed to improving the GRASS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is forthcoming.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===
=== Monday, July 13 ===
=== Tuesday, July 14 ===
=== Wednesday, July 15 ===
=== Thursday, July 16 ===
=== Friday, July 17 ===
=== Saturday, July 18 ===
=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topics'''
!'''Notes'''
|-
|1
| [[User:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
|
|
|
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|5
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|}

Registration is free; participants cover their own travel and lodging, often with employer support — thank you. Ideally we'd reimburse everyone, and every [https://numfocus.org/donate-to-grass donation] or [https://grass.osgeo.org/contribute/sponsoring/ employer sponsorship] of the project helps us get closer.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (San Michele all'Adige–Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

== Accommodation and Costs ==

''Registration is free''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]
* Details to be communicated soon.

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''Is this a conference?''
** Talks or presentations may be included, but the purpose is to work together on the project. Among conference formats, the closest comparison would be a participatory workshop.
* ''Is this a hackathon?''
** While there is plenty of intensive coding, the meeting is not competitive. We meet to collaborate.
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users, and developers ''who want to make a meaningful contribution to the project''.
* ''What skills do I need?''
** Coding skills are not required. Contributions to documentation, tutorials, translations, website, and testing are all valuable. Practical help during the meeting, such as coordinating meals, photography, or reporting, is a real contribution too.
* ''Can I attend remotely?''
** The meeting is in-person, but everyone is welcome to use the same week for focused work on the project from wherever they are.
* ''What language is used during the meeting?''
** English is the working language, but you may hear several other languages spoken at the event.
* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.
* ''What if I can't spend time on this?''
** Can you spend money instead? [https://numfocus.org/donate-to-grass Donate to GRASS through NumFOCUS] to help keep the project going.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

GRASS GSoC Ideas 2026

2026-05-04T02:31:41Z

Annakrat: Add template for accepted ideas

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== Accepted ideas ==
=== Idea title ===
* Student:
* Mentors:
* [[GRASS_GSoC_2025_Add_JSON_output_to_different_tools_in_C|Example of Wiki page]]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, r.proj, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: Large (350 hours)
* Rating: difficult
* Expected Outcomes: parallelized 2-5 tools, depending on complexity
* Test of skills (one or more):
** Address https://github.com/OSGeo/grass/issues/5776 (carefully read the existing conversation in the issue and linked PR)
** Pick a tool and develop prototype implementation of the parallelization.

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as better symbology handling and adding legend to InteractiveMap and better integration with matplotlib.

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: Large (350 hours)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here] or rewrite some of the functions in grass.jupyter library using the new [https://grass.osgeo.org/grass-devel/manuals/python_intro.html#running-tools Tools API].

=== Add JSON output to different tools ===
There are several tools in GRASS that would benefit from a JSON-formatted output.
Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: Large (350 hours)
* Rating: easy to medium
* Expected Outcomes: 10-20 tools (depending on project length and complexity of the tool) tools with well tested JSON output
* Note: A lot of work on JSON was already done, but there is more! Some of the remaining tools require more design. There are also Python tools (not just C which was the focus previously) and then also the grass-addons repo. Some tools also don't have any machine readable output right now and should. Also current tools which use other tools should use the new JSON as opposed to what they are using now. Preparing a well-reasoned list of tasks is a part of the application.
* Test of skills (pick one or more):
** https://github.com/OSGeo/grass/issues/6968
** https://github.com/OSGeo/grass/issues/6969
** https://github.com/OSGeo/grass/issues/6970

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: Large (350 hours)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== Fix known code defects ===

* Fix code defects (security or code quality) such as those reported by Coverity Scan.
* Mentors: Vaclav Petras
* Co-mentors: Nicklas Larsson
* Proposed by: Vaclav Petras
* Project length: Large (350 hours)
* Rating: medium
* Requirements:
** Language: C
** Proposal: Define milestones which will be used during the evaluation.
* Expected outcomes:
** Reduction of issues by 70-100%.
** New tests for changed code if missing.
* Test and training tasks (complete more than one): Fix e.g., [https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html GCC Static Analysis], [https://clang.llvm.org/docs/ClangStaticAnalyzer.html Clang Static Analyzer] or [https://cppcheck.sourceforge.io Cppcheck] issues.

=== Subcommand CLI for GRASS ===

* Make running of GRASS tools in command line as easy as possible.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
* Project length: Large (350 hours)
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of data and project handling in GRASS. Furthermore, the proposal needs to present, at least, concrete formulation of ideas, identification of missing and existing parts, and new subcommands.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes:
** A subcommand which runs a GRASS tool on GeoTiff and GeoPackage in one step.
** A complete parity with the existing CLI.
** An underlying Python API which will be used to implement the CLI.
* Test and training tasks (complete one or more): Add a subcommand, sub-subcommand, or an option to the experimental interface (with tests).
** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`.
** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).

Current state:

# Reveals the existing subcommands
PYTHONPATH=$(grass --config python-path) python -m grass.app --help
# Allows running subset of commands
grass run --help


=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: Large (350 hours)
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Searchable metadata in Space Time Datasets ===
The temporal framework in GRASS was initially developed almost 15 years ago. Spatio-temporal data has become more widely available since then and new standards emerged like e.g. ''[https://docs.ogc.org/cs/25-004/25-004.html STAC]'' with ''[https://github.com/stac-extensions/stac-extensions.github.io extensions]'', or the ''[https://cfconventions.org/ CF-conventions]''. The aim of this project is to extend the metadata model in the temporal framework to improve discoverability of map datasets registered in TGIS and to allow users to embed extended metadata with the registered maps in a Space Time Dataset in a searchable way. Ideally, the new model is able to account for the standards mentioned above.

See also: https://github.com/OSGeo/grass/issues/1938

* Requirements: Python, SQL, JSON
* Project length: Large (350 hours)
* Mentor: Stefan Blumentrath
* Co-mentor: ???
* Proposed by: Stefan Blumentrath
* Rating: medium
* Expected Outcomes:
** an updated TGIS database model (version 4) that:
*** is oriented on relevant metadata standards (STAC, CF-Convention, ...)
*** allows to use metadata in temporal_where to select relevant elements of Space time datasets
** updated tool to create space time datasets (t.create) in the TGIS database with extended metadata
** updated tool to register map datasets (t.register) in the TGIS database with extended metadata
** Conversion tool for database Upgrades (v3 to v4)
** a new tool to update / modify metadata in the TGIS database
** Storage of timeseries metadata for both C-based and temporal Tools

* Test of skills (e.g.):
** address one or more sub-tasks from https://github.com/OSGeo/grass/issues/3427 (add append-mode to selected new tool(s))
** suggest/implement solution for https://github.com/OSGeo/grass/issues/3394 (more complex task)
** suggest/implement solution for https://github.com/OSGeo/grass/issues/7041

=== Add {your research idea} to GRASS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: Large (350 hours)
* Rating: from low to hard
* Mentors:
** GRASS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS GSoC Ideas 2026

2026-05-04T02:30:26Z

Annakrat: Add template for accepted ideas

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, r.proj, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: Large (350 hours)
* Rating: difficult
* Expected Outcomes: parallelized 2-5 tools, depending on complexity
* Test of skills (one or more):
** Address https://github.com/OSGeo/grass/issues/5776 (carefully read the existing conversation in the issue and linked PR)
** Pick a tool and develop prototype implementation of the parallelization.

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as better symbology handling and adding legend to InteractiveMap and better integration with matplotlib.

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: Large (350 hours)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here] or rewrite some of the functions in grass.jupyter library using the new [https://grass.osgeo.org/grass-devel/manuals/python_intro.html#running-tools Tools API].

=== Add JSON output to different tools ===
There are several tools in GRASS that would benefit from a JSON-formatted output.
Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: Large (350 hours)
* Rating: easy to medium
* Expected Outcomes: 10-20 tools (depending on project length and complexity of the tool) tools with well tested JSON output
* Note: A lot of work on JSON was already done, but there is more! Some of the remaining tools require more design. There are also Python tools (not just C which was the focus previously) and then also the grass-addons repo. Some tools also don't have any machine readable output right now and should. Also current tools which use other tools should use the new JSON as opposed to what they are using now. Preparing a well-reasoned list of tasks is a part of the application.
* Test of skills (pick one or more):
** https://github.com/OSGeo/grass/issues/6968
** https://github.com/OSGeo/grass/issues/6969
** https://github.com/OSGeo/grass/issues/6970

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: Large (350 hours)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== Fix known code defects ===

* Fix code defects (security or code quality) such as those reported by Coverity Scan.
* Mentors: Vaclav Petras
* Co-mentors: Nicklas Larsson
* Proposed by: Vaclav Petras
* Project length: Large (350 hours)
* Rating: medium
* Requirements:
** Language: C
** Proposal: Define milestones which will be used during the evaluation.
* Expected outcomes:
** Reduction of issues by 70-100%.
** New tests for changed code if missing.
* Test and training tasks (complete more than one): Fix e.g., [https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html GCC Static Analysis], [https://clang.llvm.org/docs/ClangStaticAnalyzer.html Clang Static Analyzer] or [https://cppcheck.sourceforge.io Cppcheck] issues.

=== Subcommand CLI for GRASS ===

* Make running of GRASS tools in command line as easy as possible.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
* Project length: Large (350 hours)
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of data and project handling in GRASS. Furthermore, the proposal needs to present, at least, concrete formulation of ideas, identification of missing and existing parts, and new subcommands.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes:
** A subcommand which runs a GRASS tool on GeoTiff and GeoPackage in one step.
** A complete parity with the existing CLI.
** An underlying Python API which will be used to implement the CLI.
* Test and training tasks (complete one or more): Add a subcommand, sub-subcommand, or an option to the experimental interface (with tests).
** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`.
** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).

Current state:

# Reveals the existing subcommands
PYTHONPATH=$(grass --config python-path) python -m grass.app --help
# Allows running subset of commands
grass run --help


=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: Large (350 hours)
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Searchable metadata in Space Time Datasets ===
The temporal framework in GRASS was initially developed almost 15 years ago. Spatio-temporal data has become more widely available since then and new standards emerged like e.g. ''[https://docs.ogc.org/cs/25-004/25-004.html STAC]'' with ''[https://github.com/stac-extensions/stac-extensions.github.io extensions]'', or the ''[https://cfconventions.org/ CF-conventions]''. The aim of this project is to extend the metadata model in the temporal framework to improve discoverability of map datasets registered in TGIS and to allow users to embed extended metadata with the registered maps in a Space Time Dataset in a searchable way. Ideally, the new model is able to account for the standards mentioned above.

See also: https://github.com/OSGeo/grass/issues/1938

* Requirements: Python, SQL, JSON
* Project length: Large (350 hours)
* Mentor: Stefan Blumentrath
* Co-mentor: ???
* Proposed by: Stefan Blumentrath
* Rating: medium
* Expected Outcomes:
** an updated TGIS database model (version 4) that:
*** is oriented on relevant metadata standards (STAC, CF-Convention, ...)
*** allows to use metadata in temporal_where to select relevant elements of Space time datasets
** updated tool to create space time datasets (t.create) in the TGIS database with extended metadata
** updated tool to register map datasets (t.register) in the TGIS database with extended metadata
** Conversion tool for database Upgrades (v3 to v4)
** a new tool to update / modify metadata in the TGIS database
** Storage of timeseries metadata for both C-based and temporal Tools

* Test of skills (e.g.):
** address one or more sub-tasks from https://github.com/OSGeo/grass/issues/3427 (add append-mode to selected new tool(s))
** suggest/implement solution for https://github.com/OSGeo/grass/issues/3394 (more complex task)
** suggest/implement solution for https://github.com/OSGeo/grass/issues/7041

=== Add {your research idea} to GRASS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: Large (350 hours)
* Rating: from low to hard
* Mentors:
** GRASS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS GSoC Ideas 2026

2026-05-04T02:30:17Z

Annakrat: Add template for accepted ideas

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== Accepted ideas ==
=== Accepted idea title ===
* Student:
* Mentors:
* [[GRASS_GSoC_2025_Add_JSON_output_to_different_tools_in_C|Example of Wiki page]]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, r.proj, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: Large (350 hours)
* Rating: difficult
* Expected Outcomes: parallelized 2-5 tools, depending on complexity
* Test of skills (one or more):
** Address https://github.com/OSGeo/grass/issues/5776 (carefully read the existing conversation in the issue and linked PR)
** Pick a tool and develop prototype implementation of the parallelization.

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as better symbology handling and adding legend to InteractiveMap and better integration with matplotlib.

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: Large (350 hours)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here] or rewrite some of the functions in grass.jupyter library using the new [https://grass.osgeo.org/grass-devel/manuals/python_intro.html#running-tools Tools API].

=== Add JSON output to different tools ===
There are several tools in GRASS that would benefit from a JSON-formatted output.
Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: Large (350 hours)
* Rating: easy to medium
* Expected Outcomes: 10-20 tools (depending on project length and complexity of the tool) tools with well tested JSON output
* Note: A lot of work on JSON was already done, but there is more! Some of the remaining tools require more design. There are also Python tools (not just C which was the focus previously) and then also the grass-addons repo. Some tools also don't have any machine readable output right now and should. Also current tools which use other tools should use the new JSON as opposed to what they are using now. Preparing a well-reasoned list of tasks is a part of the application.
* Test of skills (pick one or more):
** https://github.com/OSGeo/grass/issues/6968
** https://github.com/OSGeo/grass/issues/6969
** https://github.com/OSGeo/grass/issues/6970

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: Large (350 hours)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== Fix known code defects ===

* Fix code defects (security or code quality) such as those reported by Coverity Scan.
* Mentors: Vaclav Petras
* Co-mentors: Nicklas Larsson
* Proposed by: Vaclav Petras
* Project length: Large (350 hours)
* Rating: medium
* Requirements:
** Language: C
** Proposal: Define milestones which will be used during the evaluation.
* Expected outcomes:
** Reduction of issues by 70-100%.
** New tests for changed code if missing.
* Test and training tasks (complete more than one): Fix e.g., [https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html GCC Static Analysis], [https://clang.llvm.org/docs/ClangStaticAnalyzer.html Clang Static Analyzer] or [https://cppcheck.sourceforge.io Cppcheck] issues.

=== Subcommand CLI for GRASS ===

* Make running of GRASS tools in command line as easy as possible.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
* Project length: Large (350 hours)
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of data and project handling in GRASS. Furthermore, the proposal needs to present, at least, concrete formulation of ideas, identification of missing and existing parts, and new subcommands.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes:
** A subcommand which runs a GRASS tool on GeoTiff and GeoPackage in one step.
** A complete parity with the existing CLI.
** An underlying Python API which will be used to implement the CLI.
* Test and training tasks (complete one or more): Add a subcommand, sub-subcommand, or an option to the experimental interface (with tests).
** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`.
** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).

Current state:

# Reveals the existing subcommands
PYTHONPATH=$(grass --config python-path) python -m grass.app --help
# Allows running subset of commands
grass run --help


=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: Large (350 hours)
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Searchable metadata in Space Time Datasets ===
The temporal framework in GRASS was initially developed almost 15 years ago. Spatio-temporal data has become more widely available since then and new standards emerged like e.g. ''[https://docs.ogc.org/cs/25-004/25-004.html STAC]'' with ''[https://github.com/stac-extensions/stac-extensions.github.io extensions]'', or the ''[https://cfconventions.org/ CF-conventions]''. The aim of this project is to extend the metadata model in the temporal framework to improve discoverability of map datasets registered in TGIS and to allow users to embed extended metadata with the registered maps in a Space Time Dataset in a searchable way. Ideally, the new model is able to account for the standards mentioned above.

See also: https://github.com/OSGeo/grass/issues/1938

* Requirements: Python, SQL, JSON
* Project length: Large (350 hours)
* Mentor: Stefan Blumentrath
* Co-mentor: ???
* Proposed by: Stefan Blumentrath
* Rating: medium
* Expected Outcomes:
** an updated TGIS database model (version 4) that:
*** is oriented on relevant metadata standards (STAC, CF-Convention, ...)
*** allows to use metadata in temporal_where to select relevant elements of Space time datasets
** updated tool to create space time datasets (t.create) in the TGIS database with extended metadata
** updated tool to register map datasets (t.register) in the TGIS database with extended metadata
** Conversion tool for database Upgrades (v3 to v4)
** a new tool to update / modify metadata in the TGIS database
** Storage of timeseries metadata for both C-based and temporal Tools

* Test of skills (e.g.):
** address one or more sub-tasks from https://github.com/OSGeo/grass/issues/3427 (add append-mode to selected new tool(s))
** suggest/implement solution for https://github.com/OSGeo/grass/issues/3394 (more complex task)
** suggest/implement solution for https://github.com/OSGeo/grass/issues/7041

=== Add {your research idea} to GRASS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: Large (350 hours)
* Rating: from low to hard
* Mentors:
** GRASS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS Community Meeting San Michele 2026

2026-04-15T18:29:41Z

Annakrat:

{{toc|right}}
The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

== Sponsors ==

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements or likewise. The community meeting is also a get-together where supporters, contributors, power users and developers make decisions and tackle larger problems related to the project, discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. We welcome people committed to improving the GRASS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is forthcoming.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===
=== Monday, July 13 ===
=== Tuesday, July 14 ===
=== Wednesday, July 15 ===
=== Thursday, July 16 ===
=== Friday, July 17 ===
=== Saturday, July 18 ===
=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topics'''
!'''Notes'''
|-
|1
| [[User:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
|
|
|
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
|
|
|
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
|
|
|
|
|-
|5
|
|
|
|
|
|
|-
|}

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (San Michele all'Adige–Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

== Accommodation and Costs ==

''Participation is free of charge''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users and developers ''who want to make a meaningful contribution to the project''.
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

GRASS-Wiki

2026-04-15T03:40:27Z

Annakrat: /* Governance */

__NOTOC__

[[Image:grasslogo_vector_small.png|110x123 px|right|link=https://grass.osgeo.org]]

== Welcome to the GRASS Wiki ==

This wiki is used by the GRASS community mainly for '''governance''', '''event planning''', and '''community coordination'''.

Looking for how to use GRASS? Visit our main website and learning resources:

* [https://grass.osgeo.org/ Main GRASS Website]
* [https://grass.osgeo.org/grass-stable/manuals/index.html Documentation & Manuals]
* [https://grass-tutorials.osgeo.org/ Tutorials & Learning Resources]
* [https://grass.osgeo.org/download/ Download GRASS]
* [https://github.com/OSGeo/grass GitHub Repository]

'''Support GRASS development: [https://grass.osgeo.org/contribute/sponsoring/ Donate here]'''

== Governance ==

* [[PSC|Project Steering Committee (PSC)]]
* [[PSC#PSC_meeting_agenda_and_minutes|Meeting Minutes]]
* [[GRASS_Budget_2026|2026 Budget]]

== Latest Events & Planning ==

* [[GRASS Community Meeting San Michele 2026]]
* [[GRASS_GSoC_Ideas_2026|Google Summer of Code 2026]]
* [[Local GRASS Meetup at NC State Center for Geospatial Analytics 2025]]

== Relevant Categories ==
* [[:Category:GSoC|GSoC]]
* [[:Category:Code_Sprint|Code sprints]]
* [[:Category:Workshops|Workshops]]
* [[:Category:Conferences|Conferences]]
* [[:Category:Installation|Installation]]
* [[:Category:Budget|Budget]]
* [[Special:Categories|Further categories]]

GRASS-Wiki

2026-04-15T03:40:07Z

Annakrat: /* Governance */

__NOTOC__

[[Image:grasslogo_vector_small.png|110x123 px|right|link=https://grass.osgeo.org]]

== Welcome to the GRASS Wiki ==

This wiki is used by the GRASS community mainly for '''governance''', '''event planning''', and '''community coordination'''.

Looking for how to use GRASS? Visit our main website and learning resources:

* [https://grass.osgeo.org/ Main GRASS Website]
* [https://grass.osgeo.org/grass-stable/manuals/index.html Documentation & Manuals]
* [https://grass-tutorials.osgeo.org/ Tutorials & Learning Resources]
* [https://grass.osgeo.org/download/ Download GRASS]
* [https://github.com/OSGeo/grass GitHub Repository]

'''Support GRASS development: [https://grass.osgeo.org/contribute/sponsoring/ Donate here]'''

== Governance ==

* [[PSC|Project Steering Committee (PSC)]]
* [[PSC#PSC_meeting_agenda_and_minutes|Meeting Minutes]]
* [[GRASS_GIS_Budget_2026|2026 Budget]]

== Latest Events & Planning ==

* [[GRASS Community Meeting San Michele 2026]]
* [[GRASS_GSoC_Ideas_2026|Google Summer of Code 2026]]
* [[Local GRASS Meetup at NC State Center for Geospatial Analytics 2025]]

== Relevant Categories ==
* [[:Category:GSoC|GSoC]]
* [[:Category:Code_Sprint|Code sprints]]
* [[:Category:Workshops|Workshops]]
* [[:Category:Conferences|Conferences]]
* [[:Category:Installation|Installation]]
* [[:Category:Budget|Budget]]
* [[Special:Categories|Further categories]]

GRASS-Wiki

2026-04-15T03:38:50Z

Annakrat: /* Latest Events & Planning */

__NOTOC__

[[Image:grasslogo_vector_small.png|110x123 px|right|link=https://grass.osgeo.org]]

== Welcome to the GRASS Wiki ==

This wiki is used by the GRASS community mainly for '''governance''', '''event planning''', and '''community coordination'''.

Looking for how to use GRASS? Visit our main website and learning resources:

* [https://grass.osgeo.org/ Main GRASS Website]
* [https://grass.osgeo.org/grass-stable/manuals/index.html Documentation & Manuals]
* [https://grass-tutorials.osgeo.org/ Tutorials & Learning Resources]
* [https://grass.osgeo.org/download/ Download GRASS]
* [https://github.com/OSGeo/grass GitHub Repository]

'''Support GRASS development: [https://grass.osgeo.org/contribute/sponsoring/ Donate here]'''

== Governance ==

* [[PSC|Project Steering Committee (PSC)]]
* [[PSC#PSC_meeting_agenda_and_minutes|Meeting Minutes]]
* [[GRASS_GIS_Budget_2025|2025 Budget]]

== Latest Events & Planning ==

* [[GRASS Community Meeting San Michele 2026]]
* [[GRASS_GSoC_Ideas_2026|Google Summer of Code 2026]]
* [[Local GRASS Meetup at NC State Center for Geospatial Analytics 2025]]

== Relevant Categories ==
* [[:Category:GSoC|GSoC]]
* [[:Category:Code_Sprint|Code sprints]]
* [[:Category:Workshops|Workshops]]
* [[:Category:Conferences|Conferences]]
* [[:Category:Installation|Installation]]
* [[:Category:Budget|Budget]]
* [[Special:Categories|Further categories]]

GRASS Community Meeting San Michele 2026

2026-04-15T03:36:11Z

Annakrat: /* Participation */

{{toc|right}}
The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 to June 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

== Sponsors ==

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements or likewise. The community meeting is also a get-together where supporters, contributors, power users and developers make decisions and tackle larger problems related to the project, discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. We welcome people committed to improving the GRASS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is forthcoming.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===
=== Monday, July 13 ===
=== Tuesday, July 14 ===
=== Wednesday, July 15 ===
=== Thursday, July 16 ===
=== Friday, July 17 ===
=== Saturday, July 18 ===
=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topics'''
!'''Notes'''
|-
|1
| [[User:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
|
|
|
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
|
|
|
|
|-
|4
|
|
|
|
|
|
|-
|}

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (San Michele all'Adige–Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

== Accommodation and Costs ==

''Participation is free of charge''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users and developers ''who want to make a meaningful contribution to the project''.
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

GRASS Community Meeting San Michele 2026

2026-04-15T03:34:08Z

Annakrat: add image

{{toc|right}}
The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 to June 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

== Sponsors ==

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements or likewise. The community meeting is also a get-together where supporters, contributors, power users and developers make decisions and tackle larger problems related to the project, discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. We welcome people committed to improving the GRASS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is forthcoming.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===
=== Monday, July 13 ===
=== Tuesday, July 14 ===
=== Wednesday, July 15 ===
=== Thursday, July 16 ===
=== Friday, July 17 ===
=== Saturday, July 18 ===
=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topics'''
!'''Notes'''
|-
|1
| [[User:wenzeslaus|Vaclav Petras]]
| United States
|
|
|
|
|-
|2
| [[User:Annakrat|Anna Petrasova]]
| United States
|
|
|
|
|-
|3
|
|
|
|
|
|
|-
|}

If you are arriving or departing on the days of the event, please specify the time, too.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (San Michele all'Adige–Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

== Accommodation and Costs ==

''Participation is free of charge''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users and developers ''who want to make a meaningful contribution to the project''.
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

File:Sanmichele.png

2026-04-15T03:28:00Z

Annakrat: Images capturing San Michele all'Adige for community meeting promo. Source is personal photos.

== Summary ==
Images capturing San Michele all'Adige for community meeting promo. Source is personal photos.

GRASS Community Meeting San Michele 2026

2026-04-15T02:59:24Z

Annakrat: wrong year

{{toc|right}}
The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 to June 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements or likewise. The community meeting is also a get-together where supporters, contributors, power users and developers make decisions and tackle larger problems related to the project, discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. We welcome people committed to improving the GRASS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is forthcoming.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===
=== Monday, July 13 ===
=== Tuesday, July 14 ===
=== Wednesday, July 15 ===
=== Thursday, July 16 ===
=== Friday, July 17 ===
=== Saturday, July 18 ===
=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topics'''
!'''Notes'''
|-
|1
| [[User:wenzeslaus|Vaclav Petras]]
| United States
|
|
|
|
|-
|2
| [[User:Annakrat|Anna Petrasova]]
| United States
|
|
|
|
|-
|3
|
|
|
|
|
|
|-
|}

If you are arriving or departing on the days of the event, please specify the time, too.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (San Michele all'Adige–Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

== Accommodation and Costs ==

''Participation is free of charge''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users and developers ''who want to make a meaningful contribution to the project''.
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

GRASS Community Meeting San Michele 2026

2026-04-15T02:58:58Z

Annakrat: Initial page

{{toc|right}}
The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 to June 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements or likewise. The community meeting is also a get-together where supporters, contributors, power users and developers make decisions and tackle larger problems related to the project, discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. We welcome people committed to improving the GRASS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is forthcoming.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===
=== Monday, July 13 ===
=== Tuesday, July 14 ===
=== Wednesday, July 15 ===
=== Thursday, July 16 ===
=== Friday, July 17 ===
=== Saturday, July 18 ===
=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topics'''
!'''Notes'''
|-
|1
| [[User:wenzeslaus|Vaclav Petras]]
| United States
|
|
|
|
|-
|2
| [[User:Annakrat|Anna Petrasova]]
| United States
|
|
|
|
|-
|3
|
|
|
|
|
|
|-
|}

If you are arriving or departing on the days of the event, please specify the time, too.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (San Michele all'Adige–Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

== Accommodation and Costs ==

''Participation is free of charge''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users and developers ''who want to make a meaningful contribution to the project''.
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2024]]

PSC Meeting 2026-02-13

2026-02-19T19:01:49Z

Annakrat: /* Minutes */ add link, remove one level of bullet points

== Participants ==

* Anna
* Vashek
* Nicklas
* Markus
* Paulo
* Linda
* Helli
* Huidae
* Vero
* Luca (guest)

== Agenda ==

The topics proposed are:

* Annual budget request submitted to OSGeo
* Community Meeting - San Michele: date, planning, budget requests
* Releases
* GSoC
* [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md#ai-use-policy AI policy]
* Plan PSC elections/role changes for later this year (some of us have been in PSC since Feb 2021)
* Budget
** Where are we at time?
** Fundraising efforts

== Minutes ==

1. Budget
* OSGeo:
** The annual budget request was submitted. See https://wiki.osgeo.org/wiki/GRASS_Budget_2026. OSGeo has allocated $1,600 of the $2,000 originally requested. Budget for swags should be requested from the Marketing Committee, which is why they cut 400 USD.
* Numfocus
** Their interface for money is not as transparent as OpenCollective; there’s no public view of the contributors or the money we have in their bucket
** We've been with them for a year now, and they are still not our fiscal hosts in Redbubble and OpenCollective. They are also going through a transition.

2. Community Meeting - San Michele
* OSGeo allocated 2500 USD, originally requested 5500 USD. See: https://wiki.osgeo.org/wiki/GRASS_Community_Meeting_2026:_Budget.
* By the beginning of March, Luca will meet FEM director, and we should then have an idea if we can stay at Convito in San Michele, so everything happens in San Michele, or if not, we search for university options in Trento, i.e., working rooms and housing.
* [Action] Create a wiki for the event.
* [Action] FOSSGIS e.V. request: will be handled by MN based on the one from [https://www.fossgis.de/wiki/Förderanträge/GRASS_GIS_Community_Meeting_2024 2024]

3. Annual report 2025
* Published as a [https://grass.osgeo.org/news/2025_12_31_annual_report/ news item] on the website
* It also served to meet the OSGeo requirement for budget request
* Nice new writing style with mentions to people actually doing things, as well as funding

4. Releases
* MN, NL, and Edouard had a branching session
* New 8.5 branch: https://github.com/OSGeo/grass/tree/releasebranch_8_5
* Waiting for Martin Landa to create the branch on Windows server
* Jupyter integration should be ready soon and will be backported to 8.5, to be part of the release.
* CMake is mostly functional, even for addons (those that were added), but documentation cannot yet be built with CMake.
* NL requested us to test CMake: https://grasswiki.osgeo.org/wiki/Compile_and_Install_With_CMake
* HC: Fixing issues in CMake for Windows.
* FHS is not ready yet; there's a big PR waiting for after the release.
* Conda: HC is working on a conda package for Windows.
* Documentation: Materials for Mkdocs style is retiring, we should transition to a supported theme. Just maybe not for the 8.5 release.

5. GSoC
* First year we participate under Numfocus if they are accepted
* We don’t know how many students we’ll get; it’s not clear how it works with Numfocus (is there a GSoC liaison/responsible person as in OSGeo?)

6. GRASS website
* There's a new version of packages and dependencies soon to be deployed
* Build to be moved to github-actions. Then the artifact has to be uploaded to OSGeo server (limitation: it needs a token that expires yearly).
* Corey to be added to the list of GRASS people with access to the OSGeo server
** [Action] VP will invite him, then create the SAC ticket needed
* conda missing from the download page, [https://github.com/OSGeo/grass-website/issues/601 issue] created
* download logos were broken for > half a year (?) and nobody realized this, [https://github.com/OSGeo/grass-website/issues/602 issue] created

7. AI policy
* Included in the main repo: https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md#ai-use-policy
* Simple - straightforward criteria that people might actually read, sort of guarantee/reference to close bad/meaningless PRs.
* Anna wrote it in response to the huge amount of PRs we are getting lately that are clearly created with AI, with no further understanding of GRASS.
* Many PRs are about tests, but they are not meaningful tests. It would be interesting to have instructions to create tests, so that contributors can train AI with instructions and create better tests.
** Corey is preparing instructions for Copilot, so it has context for code writing/reviewing.

8. PSC elections
* Some PSC members have been in PSC since Feb 2021, and as we decided back then, [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20210203#Electiondebrief mandates should last max 6 years].
* [Action] Start planning by July, during the Community Meeting.

9. Mailman
* Move translation, grass-gui and grass-stats lists to read-only mode; make a last post saying we are closing it, and ask SAC to do so (keeping their archives).

[[Category:PSC]]

GRASS GSoC Ideas 2026

2026-02-03T18:15:31Z

Annakrat: /* Ideas */ make all project sizes large

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, r.proj, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: Large (350 hours)
* Rating: difficult
* Expected Outcomes: parallelized 2-5 tools, depending on complexity
* Test of skills (one or more):
** Address https://github.com/OSGeo/grass/issues/5776 (carefully read the existing conversation in the issue and linked PR)
** Pick a tool and develop prototype implementation of the parallelization.

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as better symbology handling and adding legend to InteractiveMap and better integration with matplotlib.

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: Large (350 hours)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here] or rewrite some of the functions in grass.jupyter library using the new [https://grass.osgeo.org/grass-devel/manuals/python_intro.html#running-tools Tools API].

=== Add JSON output to different tools ===
There are several tools in GRASS that would benefit from a JSON-formatted output.
Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: Large (350 hours)
* Rating: easy to medium
* Expected Outcomes: 10-20 tools (depending on project length and complexity of the tool) tools with well tested JSON output
* Test of skills (pick one or more):
** https://github.com/OSGeo/grass/issues/6968
** https://github.com/OSGeo/grass/issues/6969
** https://github.com/OSGeo/grass/issues/6970

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: Large (350 hours)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== Fix known code defects ===

* Fix code defects (security or code quality) such as those reported by Coverity Scan.
* Mentors: Vaclav Petras
* Co-mentors: ?
* Proposed by: Vaclav Petras
* Project length: Large (350 hours)
* Rating: medium
* Requirements:
** Language: C
** Proposal: Define milestones which will be used during the evaluation.
* Expected outcomes:
** Reduction of issues by 70-100%.
** New tests for changed code if missing.
* Test and training tasks (complete more than one): Fix cppcheck issue.

=== Subcommand CLI for GRASS ===

* Make running of GRASS tools in command line as easy as possible.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
* Project length: Large (350 hours)
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of data and project handling in GRASS. Furthermore, the proposal needs to present, at least, concrete formulation of ideas, identification of missing and existing parts, and new subcommands.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes:
** A subcommand which runs a GRASS tool on GeoTiff and GeoPackage in one step.
** A complete parity with the existing CLI.
** An underlying Python API which will be used to implement the CLI.
* Test and training tasks (complete one or more): Add a subcommand, sub-subcommand, or an option to the experimental interface (with tests).
** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`.
** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).

Current state:

# Reveals the existing subcommands
PYTHONPATH=$(grass --config python-path) python -m grass.app --help
# Allows running subset of commands
grass run --help



=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: Large (350 hours)
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Add {your research idea} to GRASS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: Large (350 hours)
* Rating: from low to hard
* Mentors:
** GRASS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS GSoC Ideas 2026

2026-01-29T17:58:06Z

Annakrat: /* Improve GRASS user experience in Jupyter Notebook */

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, r.proj, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: 175 or 350 hours (take your pick)
* Rating: difficult
* Expected Outcomes: parallelized 2-5 tools, depending on complexity
* Test of skills (one or more):
** Address https://github.com/OSGeo/grass/issues/5776 (carefully read the existing conversation in the issue and linked PR)
** Pick a tool and develop prototype implementation of the parallelization.

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as better symbology handling and adding legend to InteractiveMap and better integration with matplotlib.

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here] or rewrite some of the functions in grass.jupyter library using the new [https://grass.osgeo.org/grass-devel/manuals/python_intro.html#running-tools Tools API].

=== Add JSON output to different tools ===
There are several tools in GRASS that would benefit from a JSON-formatted output.
Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: 10-20 tools (depending on project length and complexity of the tool) tools with well tested JSON output
* Test of skills (pick one or more):
** https://github.com/OSGeo/grass/issues/6968
** https://github.com/OSGeo/grass/issues/6969
** https://github.com/OSGeo/grass/issues/6970

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: 175 or 350 hours (take your pick)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== Fix known code defects ===

* Fix code defects (security or code quality) such as those reported by Coverity Scan.
* Mentors: Vaclav Petras
* Co-mentors: ?
* Proposed by: Vaclav Petras
* Project length: 175 or 350 hours (flexible)
* Rating: medium
* Requirements:
** Language: C
** Proposal: Define milestones which will be used during the evaluation.
* Expected outcomes:
** Reduction of issues by 70-100%.
** New tests for changed code if missing.
* Test and training tasks (complete more than one): Fix cppcheck issue.

=== Subcommand CLI for GRASS ===

* Make running of GRASS tools in command line as easy as possible.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
* Project length: 350 hours
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of data and project handling in GRASS. Furthermore, the proposal needs to present, at least, concrete formulation of ideas, identification of missing and existing parts, and new subcommands.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes:
** A subcommand which runs a GRASS tool on GeoTiff and GeoPackage in one step.
** A complete parity with the existing CLI.
** An underlying Python API which will be used to implement the CLI.
* Test and training tasks (complete one or more): Add a subcommand, sub-subcommand, or an option to the experimental interface (with tests).
** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`.
** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).

Current state:

# Reveals the existing subcommands
PYTHONPATH=$(grass --config python-path) python -m grass.app --help
# Allows running subset of commands
grass run --help



=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: 175 or 350 hours
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Add {your research idea} to GRASS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: 175 or 350 hours (take your pick)
* Rating: from low to hard
* Mentors:
** GRASS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS GSoC Ideas 2026

2026-01-26T04:26:15Z

Annakrat: /* Improve GRASS user experience in Jupyter Notebook */

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, r.proj, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: 175 or 350 hours (take your pick)
* Rating: difficult
* Expected Outcomes: parallelized 2-5 tools, depending on complexity
* Test of skills (one or more):
** Address https://github.com/OSGeo/grass/issues/5776 (carefully read the existing conversation in the issue and linked PR)
** Pick a tool and develop prototype implementation of the parallelization.

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as better symbology handling and adding legend to InteractiveMap and better integration with matplotlib.

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here].

=== Add JSON output to different tools ===
There are several tools in GRASS that would benefit from a JSON-formatted output.
Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: 10-20 tools (depending on project length and complexity of the tool) tools with well tested JSON output
* Test of skills (pick one or more):
** https://github.com/OSGeo/grass/issues/6968
** https://github.com/OSGeo/grass/issues/6969
** https://github.com/OSGeo/grass/issues/6970

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: 175 or 350 hours (take your pick)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== Fix known code defects ===

* Fix code defects (security or code quality) such as those reported by Coverity Scan.
* Mentors: Vaclav Petras
* Co-mentors: ?
* Proposed by: Vaclav Petras
* Project length: 175 or 350 hours (flexible)
* Rating: medium
* Requirements:
** Language: C
** Proposal: Define milestones which will be used during the evaluation.
* Expected outcomes:
** Reduction of issues by 70-100%.
** New tests for changed code if missing.
* Test and training tasks (complete more than one): Fix cppcheck issue.

=== Subcommand CLI for GRASS ===

* Make running of GRASS tools in command line as easy as possible.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
* Project length: 350 hours
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of data and project handling in GRASS. Furthermore, the proposal needs to present, at least, concrete formulation of ideas, identification of missing and existing parts, and new subcommands.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes:
** A subcommand which runs a GRASS tool on GeoTiff and GeoPackage in one step.
** A complete parity with the existing CLI.
** An underlying Python API which will be used to implement the CLI.
* Test and training tasks (complete one or more): Add a subcommand, sub-subcommand, or an option to the experimental interface (with tests).
** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`.
** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).

Current state:

# Reveals the existing subcommands
PYTHONPATH=$(grass --config python-path) python -m grass.app --help
# Allows running subset of commands
grass run --help



=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: 175 or 350 hours
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Add {your research idea} to GRASS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: 175 or 350 hours (take your pick)
* Rating: from low to hard
* Mentors:
** GRASS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS GSoC Ideas 2026

2026-01-26T04:15:24Z

Annakrat: /* Parallelization of existing tools */

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, r.proj, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: 175 or 350 hours (take your pick)
* Rating: difficult
* Expected Outcomes: parallelized 2-5 tools, depending on complexity
* Test of skills (one or more):
** Address https://github.com/OSGeo/grass/issues/5776 (carefully read the existing conversation in the issue and linked PR)
** Pick a tool and develop prototype implementation of the parallelization.

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as increasing interactivity of displayed data using ipyleaflet, adding API for managing projects and subprojects (i.e., locations/mapsets), creating GUI for commands, ...

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: https://github.com/OSGeo/grass/issues/3276, or write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here].

=== Add JSON output to different tools ===
There are several tools in GRASS that would benefit from a JSON-formatted output.
Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: 10-20 tools (depending on project length and complexity of the tool) tools with well tested JSON output
* Test of skills (pick one or more):
** https://github.com/OSGeo/grass/issues/6968
** https://github.com/OSGeo/grass/issues/6969
** https://github.com/OSGeo/grass/issues/6970

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: 175 or 350 hours (take your pick)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== Fix known code defects ===

* Fix code defects (security or code quality) such as those reported by Coverity Scan.
* Mentors: Vaclav Petras
* Co-mentors: ?
* Proposed by: Vaclav Petras
* Project length: 175 or 350 hours (flexible)
* Rating: medium
* Requirements:
** Language: C
** Proposal: Define milestones which will be used during the evaluation.
* Expected outcomes:
** Reduction of issues by 70-100%.
** New tests for changed code if missing.
* Test and training tasks (complete more than one): Fix cppcheck issue.

=== Subcommand CLI for GRASS ===

* Make running of GRASS tools in command line as easy as possible.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
* Project length: 350 hours
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of data and project handling in GRASS. Furthermore, the proposal needs to present, at least, concrete formulation of ideas, identification of missing and existing parts, and new subcommands.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes:
** A subcommand which runs a GRASS tool on GeoTiff and GeoPackage in one step.
** A complete parity with the existing CLI.
** An underlying Python API which will be used to implement the CLI.
* Test and training tasks (complete one or more): Add a subcommand, sub-subcommand, or an option to the experimental interface (with tests).
** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`.
** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).

Current state:

# Reveals the existing subcommands
PYTHONPATH=$(grass --config python-path) python -m grass.app --help
# Allows running subset of commands
grass run --help



=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: 175 or 350 hours
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Add {your research idea} to GRASS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: 175 or 350 hours (take your pick)
* Rating: from low to hard
* Mentors:
** GRASS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS GSoC Ideas 2026

2026-01-26T03:52:07Z

Annakrat: /* Add JSON output to different tools in C */

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.horizon, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: 175 or 350 hours (take your pick)
* Rating: medium
* Expected Outcomes: parallelized module or modules, depending on complexity

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as increasing interactivity of displayed data using ipyleaflet, adding API for managing projects and subprojects (i.e., locations/mapsets), creating GUI for commands, ...

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: https://github.com/OSGeo/grass/issues/3276, or write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here].

=== Add JSON output to different tools ===
There are several tools in GRASS that would benefit from a JSON-formatted output.
Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: 10-20 tools (depending on project length and complexity of the tool) tools with well tested JSON output
* Test of skills (pick one or more):
** https://github.com/OSGeo/grass/issues/6968
** https://github.com/OSGeo/grass/issues/6969
** https://github.com/OSGeo/grass/issues/6970

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: 175 or 350 hours (take your pick)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== Fix known code defects ===

* Fix code defects (security or code quality) such as those reported by Coverity Scan.
* Mentors: Vaclav Petras
* Co-mentors: ?
* Proposed by: Vaclav Petras
* Project length: 175 or 350 hours (flexible)
* Rating: medium
* Requirements:
** Language: C
** Proposal: Define milestones which will be used during the evaluation.
* Expected outcomes:
** Reduction of issues by 70-100%.
** New tests for changed code if missing.
* Test and training tasks (complete more than one): Fix cppcheck issue.

=== Subcommand CLI for GRASS ===

* Make running of GRASS tools in command line as easy as possible.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
* Project length: 350 hours
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of data and project handling in GRASS. Furthermore, the proposal needs to present, at least, concrete formulation of ideas, identification of missing and existing parts, and new subcommands.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes:
** A subcommand which runs a GRASS tool on GeoTiff and GeoPackage in one step.
** A complete parity with the existing CLI.
** An underlying Python API which will be used to implement the CLI.
* Test and training tasks (complete one or more): Add a subcommand, sub-subcommand, or an option to the experimental interface (with tests).
** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`.
** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).

Current state:

# Reveals the existing subcommands
PYTHONPATH=$(grass --config python-path) python -m grass.app --help
# Allows running subset of commands
grass run --help



=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: 175 or 350 hours
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Add {your research idea} to GRASS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: 175 or 350 hours (take your pick)
* Rating: from low to hard
* Mentors:
** GRASS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS GSoC Ideas 2026

2026-01-21T20:15:14Z

Annakrat: /* AI Tool Usage Policy */

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.
* Disclose AI usage: If you use AI tools in your proposal or code contributions, please disclose the extent to which you used them (e.g., for brainstorming, proofreading, code suggestions, etc.).

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.horizon, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: 175 or 350 hours (take your pick)
* Rating: medium
* Expected Outcomes: parallelized module or modules, depending on complexity

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as increasing interactivity of displayed data using ipyleaflet, adding API for managing projects and subprojects (i.e., locations/mapsets), creating GUI for commands, ...

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: https://github.com/OSGeo/grass/issues/3276, or write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here].

=== Add JSON output to different tools in C ===
There are several tools in GRASS that would benefit from a JSON-formatted output, see [https://github.com/OSGeo/grass/issues/3020 this issue for a list of tools]. Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python for tests
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: one or more (depending on project length and complexity of the tool) tools with well tested JSON output
* Test of skills: Address https://github.com/OSGeo/grass/issues/1044 for r.surf.fractal

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: 175 or 350 hours (take your pick)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== New easy-to-use CLI and API for GRASS GIS ===

* Make running of GRASS GIS modules as easy as it is to run GDAL commands.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
** CLI like GDAL has.
** No GRASS Database, Location, Mapset to deal with.
** No import, export from user perspective.
** Reasonable defaults for things like region.
** CLI and API still allows user to specify any of the above.
* Idea page with details: wiki:GSoC/2021/EasyToUseCliAndApiIdea
* Project length: 350 hours
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of the GRASS GIS Database structure and significantly extend on text below in terms of more concrete formulation of ideas and identification of missing and existing parts.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes: New subcommand which easily runs a GRASS module on GeoTiff and GeoPackage.
* Test and training tasks:
** Solve one of the tickets linked at the idea page.
** Add features to `grass` executable interface:
*** Make it possible to associate `*.gxw` files with `grass` executable (#1204) or at least add `--gui-workspace` or preferably just recognize it in the command line (distinguish it from database/location/mapset).
** Extend `--exec` functionality:
*** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`
*** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
*** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).



=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: 175 or 350 hours
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Add {your research idea} to GRASS GIS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS GIS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS GIS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: 175 or 350 hours (take your pick)
* Rating: from low to hard
* Mentors:
** GRASS GIS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS-Wiki

2026-01-21T20:12:59Z

Annakrat: /* Welcome to the GRASS Wiki */

__NOTOC__

[[Image:grasslogo_vector_small.png|110x123 px|right|link=https://grass.osgeo.org]]

== Welcome to the GRASS Wiki ==

This wiki is used by the GRASS community mainly for '''governance''', '''event planning''', and '''community coordination'''.

Looking for how to use GRASS? Visit our main website and learning resources:

* [https://grass.osgeo.org/ Main GRASS Website]
* [https://grass.osgeo.org/grass-stable/manuals/index.html Documentation & Manuals]
* [https://grass-tutorials.osgeo.org/ Tutorials & Learning Resources]
* [https://grass.osgeo.org/download/ Download GRASS]
* [https://github.com/OSGeo/grass GitHub Repository]

'''Support GRASS development: [https://grass.osgeo.org/contribute/sponsoring/ Donate here]'''

== Governance ==

* [[PSC|Project Steering Committee (PSC)]]
* [[PSC#PSC_meeting_agenda_and_minutes|Meeting Minutes]]
* [[GRASS_GIS_Budget_2025|2025 Budget]]

== Latest Events & Planning ==

* [[GRASS_GSoC_Ideas_2026|Google Summer of Code 2026]]
* [[Local GRASS Meetup at NC State Center for Geospatial Analytics 2025]]
* [[GRASS_Developer_Summit_Raleigh_2025|GRASS Developer Summit in Raleigh 2025]]

== Relevant Categories ==
* [[:Category:GSoC|GSoC]]
* [[:Category:Code_Sprint|Code sprints]]
* [[:Category:Workshops|Workshops]]
* [[:Category:Conferences|Conferences]]
* [[:Category:Installation|Installation]]
* [[:Category:Budget|Budget]]
* [[Special:Categories|Further categories]]

GRASS-Wiki

2026-01-21T20:12:04Z

Annakrat: /* Latest Events & Planning */

__NOTOC__

[[Image:grasslogo_vector_small.png|110x123 px|right|link=https://grass.osgeo.org]]

== Welcome to the GRASS Wiki ==

This wiki is used by the GRASS community mainly for '''governance''', '''event planning''', and '''community coordination'''.

Looking for how to use GRASS? Visit our main website and learning resources:

* [https://grass.osgeo.org/ Main GRASS Website]
* [https://grass.osgeo.org/grass84/manuals/index.html Documentation & Manuals]
* [https://grass-tutorials.osgeo.org/ Tutorials & Learning Resources]
* [https://grass.osgeo.org/download/ Download GRASS]
* [https://github.com/OSGeo/grass GitHub Repository]

'''Support GRASS development: [https://grass.osgeo.org/contribute/sponsoring/ Donate here]'''

== Governance ==

* [[PSC|Project Steering Committee (PSC)]]
* [[PSC#PSC_meeting_agenda_and_minutes|Meeting Minutes]]
* [[GRASS_GIS_Budget_2025|2025 Budget]]

== Latest Events & Planning ==

* [[GRASS_GSoC_Ideas_2026|Google Summer of Code 2026]]
* [[Local GRASS Meetup at NC State Center for Geospatial Analytics 2025]]
* [[GRASS_Developer_Summit_Raleigh_2025|GRASS Developer Summit in Raleigh 2025]]

== Relevant Categories ==
* [[:Category:GSoC|GSoC]]
* [[:Category:Code_Sprint|Code sprints]]
* [[:Category:Workshops|Workshops]]
* [[:Category:Conferences|Conferences]]
* [[:Category:Installation|Installation]]
* [[:Category:Budget|Budget]]
* [[Special:Categories|Further categories]]

GRASS GSoC Ideas 2026

2026-01-21T20:11:07Z

Annakrat: /* AI Policy */

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== AI Tool Usage Policy ==
We acknowledge that applicants may use AI tools (like ChatGPT, Copilot, etc.) to assist with proposal writing and coding. However:

* Your proposal should reflect your own understanding and voice. AI-generated "slop" (overly generic or regurgitated content) is easy to spot and will hurt your application.
* We evaluate applications primarily on GitHub contributions and communication with the GRASS community, not just proposal polish.
* Show us you understand the project through high-quality pull requests on GitHub.

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.horizon, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: 175 or 350 hours (take your pick)
* Rating: medium
* Expected Outcomes: parallelized module or modules, depending on complexity

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as increasing interactivity of displayed data using ipyleaflet, adding API for managing projects and subprojects (i.e., locations/mapsets), creating GUI for commands, ...

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: https://github.com/OSGeo/grass/issues/3276, or write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here].

=== Add JSON output to different tools in C ===
There are several tools in GRASS that would benefit from a JSON-formatted output, see [https://github.com/OSGeo/grass/issues/3020 this issue for a list of tools]. Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python for tests
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: one or more (depending on project length and complexity of the tool) tools with well tested JSON output
* Test of skills: Address https://github.com/OSGeo/grass/issues/1044 for r.surf.fractal

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: 175 or 350 hours (take your pick)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== New easy-to-use CLI and API for GRASS GIS ===

* Make running of GRASS GIS modules as easy as it is to run GDAL commands.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
** CLI like GDAL has.
** No GRASS Database, Location, Mapset to deal with.
** No import, export from user perspective.
** Reasonable defaults for things like region.
** CLI and API still allows user to specify any of the above.
* Idea page with details: wiki:GSoC/2021/EasyToUseCliAndApiIdea
* Project length: 350 hours
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of the GRASS GIS Database structure and significantly extend on text below in terms of more concrete formulation of ideas and identification of missing and existing parts.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes: New subcommand which easily runs a GRASS module on GeoTiff and GeoPackage.
* Test and training tasks:
** Solve one of the tickets linked at the idea page.
** Add features to `grass` executable interface:
*** Make it possible to associate `*.gxw` files with `grass` executable (#1204) or at least add `--gui-workspace` or preferably just recognize it in the command line (distinguish it from database/location/mapset).
** Extend `--exec` functionality:
*** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`
*** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
*** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).



=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: 175 or 350 hours
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Add {your research idea} to GRASS GIS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS GIS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS GIS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: 175 or 350 hours (take your pick)
* Rating: from low to hard
* Mentors:
** GRASS GIS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS GSoC Ideas 2026

2026-01-21T16:09:17Z

Annakrat:

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== AI Policy ==
TBD

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers], [https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.horizon, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: 175 or 350 hours (take your pick)
* Rating: medium
* Expected Outcomes: parallelized module or modules, depending on complexity

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as increasing interactivity of displayed data using ipyleaflet, adding API for managing projects and subprojects (i.e., locations/mapsets), creating GUI for commands, ...

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: https://github.com/OSGeo/grass/issues/3276, or write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here].

=== Add JSON output to different tools in C ===
There are several tools in GRASS that would benefit from a JSON-formatted output, see [https://github.com/OSGeo/grass/issues/3020 this issue for a list of tools]. Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python for tests
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: one or more (depending on project length and complexity of the tool) tools with well tested JSON output
* Test of skills: Address https://github.com/OSGeo/grass/issues/1044 for r.surf.fractal

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: 175 or 350 hours (take your pick)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== New easy-to-use CLI and API for GRASS GIS ===

* Make running of GRASS GIS modules as easy as it is to run GDAL commands.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
** CLI like GDAL has.
** No GRASS Database, Location, Mapset to deal with.
** No import, export from user perspective.
** Reasonable defaults for things like region.
** CLI and API still allows user to specify any of the above.
* Idea page with details: wiki:GSoC/2021/EasyToUseCliAndApiIdea
* Project length: 350 hours
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of the GRASS GIS Database structure and significantly extend on text below in terms of more concrete formulation of ideas and identification of missing and existing parts.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes: New subcommand which easily runs a GRASS module on GeoTiff and GeoPackage.
* Test and training tasks:
** Solve one of the tickets linked at the idea page.
** Add features to `grass` executable interface:
*** Make it possible to associate `*.gxw` files with `grass` executable (#1204) or at least add `--gui-workspace` or preferably just recognize it in the command line (distinguish it from database/location/mapset).
** Extend `--exec` functionality:
*** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`
*** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
*** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).



=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: 175 or 350 hours
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Add {your research idea} to GRASS GIS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS GIS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS GIS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: 175 or 350 hours (take your pick)
* Rating: from low to hard
* Mentors:
** GRASS GIS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* Follow official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

GRASS GSoC Ideas 2026

2026-01-21T15:55:00Z

Annakrat: Create 2026 page

== About ==
Important: While we are still an OSGeo project, we changed our fiscal sponsor to [https://numfocus.org/ NumFOCUS].

''As a result, GRASS participates in GSoC under the [https://numfocus.org/ NumFOCUS] umbrella organization.''

Read more about our governance [https://grass.osgeo.org/about/governance/ on GRASS website].

* [https://numfocus.org/programs/google-summer-code The NumFOCUS GSoC main page]
* [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines for contributors].
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers],[https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

Include "GRASS" in the title of our idea to easily distinguish ideas and projects inside NumFOCUS.

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.horizon, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: 175 or 350 hours (take your pick)
* Rating: medium
* Expected Outcomes: parallelized module or modules, depending on complexity

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as increasing interactivity of displayed data using ipyleaflet, adding API for managing projects and subprojects (i.e., locations/mapsets), creating GUI for commands, ...

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: https://github.com/OSGeo/grass/issues/3276, or write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here].

=== Add JSON output to different tools in C ===
There are several tools in GRASS that would benefit from a JSON-formatted output, see [https://github.com/OSGeo/grass/issues/3020 this issue for a list of tools]. Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python for tests
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: one or more (depending on project length and complexity of the tool) tools with well tested JSON output
* Test of skills: Address https://github.com/OSGeo/grass/issues/1044 for r.surf.fractal

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: 175 or 350 hours (take your pick)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== New easy-to-use CLI and API for GRASS GIS ===

* Make running of GRASS GIS modules as easy as it is to run GDAL commands.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
** CLI like GDAL has.
** No GRASS Database, Location, Mapset to deal with.
** No import, export from user perspective.
** Reasonable defaults for things like region.
** CLI and API still allows user to specify any of the above.
* Idea page with details: wiki:GSoC/2021/EasyToUseCliAndApiIdea
* Project length: 350 hours
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of the GRASS GIS Database structure and significantly extend on text below in terms of more concrete formulation of ideas and identification of missing and existing parts.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes: New subcommand which easily runs a GRASS module on GeoTiff and GeoPackage.
* Test and training tasks:
** Solve one of the tickets linked at the idea page.
** Add features to `grass` executable interface:
*** Make it possible to associate `*.gxw` files with `grass` executable (#1204) or at least add `--gui-workspace` or preferably just recognize it in the command line (distinguish it from database/location/mapset).
** Extend `--exec` functionality:
*** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`
*** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
*** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).



=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: 175 or 350 hours
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Add {your research idea} to GRASS GIS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS GIS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS GIS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: 175 or 350 hours (take your pick)
* Rating: from low to hard
* Mentors:
** GRASS GIS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==
* See the official [https://github.com/numfocus/gsoc/blob/master/CONTRIBUTING-contributors.md NumFOCUS guidelines].
* If you have your own ideas we encourage you to propose them. Explain them on the [https://discourse.osgeo.org/c/grass/developer/61 on our Discourse].
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file].
* Prove your worth by being active on the [https://discourse.osgeo.org/c/grass/developer/61 GRASS Discourse] or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

{{GSoC}}

PSC Meeting 2025-11-14

2025-12-16T17:30:31Z

Annakrat: /* Minutes */

== Participants ==

* Anna Petrasova
* Huidae Cho
* Linda Karlovska
* Markus Neteler
* Nicklas Larsson
* Paulo van Breugel
* Vaclav Petras
* Veronica Andreo

== Agenda ==

The topics proposed are:

* Report from NumFOCUS Project Summit (VP)
* GRASS Wiki under DDOS attack, see https://discourse.osgeo.org/t/grass-wiki-under-ddos-attack/150717
* New wiki page: [[Organizing GRASS Contributor Events]]
* GRASS Meeting 2026 - Luca's proposal
* Upcoming releases:
** Release 8.4.2 (due to relevant [https://github.com/OSGeo/grass/compare/8.4.1...releasebranch_8_4 fixes]; the branch-CI is also functional again) - [https://github.com/OSGeo/grass/milestone/27 milestone]
** Release 8.5.0 - [https://github.com/OSGeo/grass/milestone/22 milestone]
* Reimburse Alen for stickers he bought to take to NZ

== Minutes ==

* Report from NumFOCUS Project Summit:
** VP participated of the NumFOCUS projects summit; there were not many other projects attending.
** There are calls for small grants (USD 10K per project per year), that we should apply for, and ideally use them for development.
** It seems we need to apply as a project, but it is not clear who submits. In any case, the person interested in the money should lead the effort. See: https://numfocus.org/programs/small-development-grants.
** We had a meeting with them on Tue 18th, but AP will ask them to move it because neither VP nor VA can attend. New date: Dec 10th, 2025.

* GRASS wiki under attack by botnet:
** MN set up countermeasures on the server, instructions to be dumped in our infrastructure shared doc
** Not everyone has access to that doc, so we shall review and discuss our shared folder and files access “policy”.

* New wiki page on organizing GRASS events:
** https://grasswiki.osgeo.org/wiki/Organizing_GRASS_Contributor_Events

* GRASS meeting San Michele 2026:
** See [https://lists.osgeo.org/pipermail/grass-psc/2025-September/003054.html Luca's proposal].
** Nicklas is not available for any of the proposed dates.
** For AP and VP any of the dates are fine.
** Paulo: 50% with the second date.
** HC: probably the second date.
** MN and VA: any date fine for now.
** Linda: new baby coming! Congrats!

* Release 8.4.2:
** VP and MN will agree on a date soon to do the release together.
** Edouard will be invited, too.

* Release 8.5:
** It will have CMake in the source code as experimental feature to try for users who compile code themselves (but extensions won’t work for them).
** FHS won’t work with CMake yet.
** It’s a matter of communication about what’s there in the source code. Binaries will be with autotools, so addons will work.
** Blockers: there’s an issue with r.blend and something with r.patch with vrt and nprocs > 1 (the latter found by Metz, but still unreported)
** New python API, VP will call for a webinar on it by mid-dec, to show how it works and collect some feedback, too.
** JSON stuff and mkdocs is in good shape to go.
** Jupyter notebook PR needs to be reviewed, it does not work in windows, but this is not a blocker, we can mark it as experimental.
** Drop support for PROJ < 8 and GDAL < 3? Nicklas created issues to get feedback, it could be done before the release. See [https://github.com/OSGeo/grass/issues/6628 #6628] and [https://github.com/OSGeo/grass/issues/6629 #6629].

* Motion proposed and passed to reimburse Alen for the stickers. VP will contact Michael Smith, so Alen gets reimbursed.

* Plan extraordinary meeting - PSC + Luca to plan 2026 budget + community meeting when the call for OSGeo budget is out.
** VP proposal: include an item to promote GRASS in other than FOSS4G conferences.

[[Category:PSC]]

GRASS Developer Summit Raleigh 2025

2025-09-22T18:33:24Z

Annakrat: /* Venue */ fix typo to test watching this page

{{toc|right}}
The main meeting of the GRASS Project in 2025 is a 6-day '''GRASS Developer Summit''' to be held at North Carolina State University from '''Monday, May 19th through Saturday, May 24th''' in Raleigh, North Carolina, USA.

Quick links: [[#GRASS_Lightning_Talks_&_Reception|Lightning Talks]] | [[Talk:GRASS_Developer_Summit_Raleigh_2025#Participant_reports|Participant reports]] | [[Talk:GRASS_Developer_Summit_Raleigh_2025#Detailed_Schedule|Schedule]] | [[#Sponsors|Sponsors]] | [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ Press release]

[[File:Grass developer summit 2025 group picture.jpg|frameless|center|800px|NCSU venue and organizers|alt=Group of smiling people in GRASS t-shirts at stairs outside of a building]]

[[File:NCSU developer summit venue 2025 collage.jpg|thumb|Venue and area]]

== Sponsors ==

[[File:NSF Official logo.png|none|left|200px|alt=Logo of US NSF|U.S. National Science Foundation]] [[File:Bohannan_Huston_Inc_Logo.png|none|left|400px|alt=Logo of Bohannan Huston, Inc.|Bohannan Huston, Inc.]]

* U.S. National Science Foundation, award [https://www.nsf.gov/awardsearch/showAward?AWD_ID=2303651 2303651]: Planning, preparation, event venue, participant travel

* [https://bhinc.com/ Bohannan Huston, Inc.]: 2,000 USD

* Lightning Talks & Reception sponsor: [https://geospatial.ncsu.edu/ Center for Geospatial Analytics], North Carolina State University: Venue, technology, reception

* Individual contributors at [https://opencollective.com/grass/contribute/grass-developer-summit-2025-84759/ Open Collective]

'''Why should you become a sponsor?''' While all major parts of this event are supported by the NSF POSE award mentioned above, we welcome any additional support for ancillary costs associated with the event, as not everything can be covered, for good reasons, by the U.S. federal funding.

To sponsor the event, use [https://opencollective.com/osgeo/projects/grass/contribute/grass-developer-summit-2025-84759/checkout Open Collective] or contact [[User:wenzeslaus|Vaclav Petras]] <tt><wenzeslaus at gmail com></tt> for invoicing options.

== Purpose ==

The purpose of this in-person Developer Summit is to identify challenges in the adoption of GRASS as a geoprocessing engine and to foster the growth of the contributor community by connecting new and experienced developers. Attendees will contribute their unique skills to GRASS, evaluate the progress of the project, and participate in long-term planning for GRASS. The goal of the event is to generate actionable feedback for future improvements and to prepare the ground for expanding the geoprocessing capabilities of GRASS.

== Agenda ==

Each day will consist of a block of scheduled sessions (tentative topics below), a block of self-organized sessions (determined by the attendees and organizers), three business meals (breakfast, lunch, and dinner), and dedicated time for attendees to individually contribute to the project by coding, documenting, testing, or making other improvements.

See [[Talk:GRASS_Developer_Summit_Raleigh_2025#Detailed_Schedule|Detailed Agenda for each day]] on Discussion page.

Overview:
* '''Day 1 (Monday, May 19):''' What to expect from the event, contributing to GRASS using Git and GitHub, making your first contribution.
* '''Day 2 (Tuesday, May 20):''' Introduction to writing GRASS tools, interfacing with QGIS (gathering user feedback, testing, discussing with developers, developing action items).
* '''Day 3 (Wednesday, May 21):''' Introduction to non-coding contributions, deep dive into new documentation, natural language translation and internationalization (procedures, glossaries, code customization, translation).
* '''Day 4 (Thursday, May 22):''' Project vision, computational engine (missing features, documentation, user groups), lightning talks for external audience followed by reception at the Center for Geospatial Analytics at NC State.
* '''Day 5 (Friday, May 23):''' Project Steering Committee meeting, interfacing with R (gathering user feedback, testing, discussing with developers, developing action items).
* '''Day 6 (Saturday, May 24):''' NSF POSE project evaluation, contributor community feedback, charting the project's future course.

General daily schedule:
* '''Breakfast (8-9am):''' Start the day, meet people, and plan your personal agenda for the day.
* '''Morning opening sessions (9-10am):''' Introductions to contributing, the project, and its vision, program for the day.
* '''Self-organized feedback sessions (11-noon):''' Three impromptu 20-minute sessions to gather feedback on a topic (10-minute presentation and 10-minute discussion).
* '''Lunch (noon-1pm):''' Eat, drink, and continue the discussion from the feedback sessions.
* '''Focus time (10-11am and 1-5pm):''' Time to work on your laptop, whiteboard solutions with a group, or anything in between.
* '''Dinner (evening):''' Evaluate the day's accomplishments, plan and prioritize for the next few days.

You don't have to participate in all discussions or contribute to all topics. You are welcome to pick and choose the ones that are more relevant to your interests and expertise. The rest of the time you are free to work on your own contributions to GRASS. While the main language of communication at the event will be English, participants are welcome to use other languages as they see fit. Currently, native speakers of eight languages other than English have confirmed their participation.

== GRASS Lightning Talks & Reception ==

Hosted and co-sponsored by Center for Geospatial Analytics at NC State University and the US National Science Foundation, '''GRASS Lightning Talks & Reception''' on Thursday, May 22nd will feature speakers from mundialis, Natrx, Bohannan Huston, government, and academia, showcasing real-world applications of GRASS. We’ll kick things off at 4:00 PM with a series of fast-paced talks. A reception will follow at 5:00 PM, offering time to connect with researchers, government professionals, and industry collaborators.

* Host: Vaclav Petras, North Carolina State University
* Markus Metz & Markus Neteler, mundialis, ''Optimizing Urban Infrastructure: Automated Trench Planning with GRASS'' (presented by Vaclav Petras)
* Anna Petrasova, North Carolina State University, ''Scaling Up Urban Growth Projections with FUTURES''
* Verónica Andreo, CONICET – Instituto Gulich, ''GRASS-fed Species Distribution Models''
* Rob Dzur, Bohannan Huston, Inc., ''Going with the Flow: How GRASS Helps Us Navigate Elevation-Derived Hydrography (EDH) Breakthroughs''
* Nick Brady, Natrx, ''Distributed GRASS for Erosion Assessments''
* Huidae Cho, New Mexico State University, ''Continental-Scale Hydrologic Modeling Using GRASS''
* Gregory Power, Town of Cary, ''Using GRASS for Open Data Pipelines''
* Doug Newcomb, ''Hydro Flattening Impounded Water Bodies from LiDAR Point Cloud Data''
* Caitlin Haedrich, North Carolina State University, ''Modeling Agricultural Runoff with Tangible Landscape and GRASS''

== Venue ==

[[File:std_dataset_nc_shaded_elevation.png|thumb|Elevation in the NC sample dataset]]

[[File:Ncsu logo.jpg|240px|frameless|left]]
[https://www.ncsu.edu/ NC State University, Raleigh, North Carolina, USA] 

The developer summit is hosted on the NC State University campus, taking advantage of modern facilities including [https://studentcenters.ncsu.edu/location/talley/ Talley Student Union], [https://www.lib.ncsu.edu/hunt Hunt Library] and the [https://cnr.ncsu.edu/geospatial/ Center for Geospatial Analytics].

Recommended accommodation for its proximity and accomodation used for sponsored participants is Aloft Raleigh, 2100 Hillsborough St, Raleigh, NC 27607. Contact organizers for a possibility of using a negotiated lower rate.

Fun fact: Raleigh in North Carolina is the home of the famous GRASS [https://grass.osgeo.org/download/data/#NorthCarolinaDataset North Carolina sample dataset].

== Participation ==

Registration is now open. Please, help us plan better by filling out the registration form as soon as you decide to come:

[https://forms.gle/q6zzsGeHo2YkUVnx5 Summit registration form.]

We are expecting over [[Talk:GRASS_Developer_Summit_Raleigh_2025#Participant_reports|30 people]]!

== FAQ ==

* ''How these events look like?''
** See [[GRASS Community Meeting Prague 2024]] and [[GRASS Community Meeting Prague 2023]] for last two events which were both great!
* ''Is the meeting focused on coding?''
** The focus is contributing to the project. The project is build on contributions in the form of code, documentation, translations, promotion and more.
* ''Is the meeting for developers only?''
** No, anybody can help, with testing, checking out bugs and fixes, documentation and more. The goal is to develop GRASS and make it easier to develop workflows and software on top of GRASS.
* ''Do I have to be a contributor to come?''
** You don't make contributions prior to the meeting, but the goal is to improve the project, so we ask that you discuss and plan your contributions before coming to the meeting. If you are a committed newcomer, contact us and we will gladly find a way for you to meaningfully contribute.
* ''Where can I get help and more information about the event?''
** Contact [[User:wenzeslaus|Vaclav (Vashek) Petras]] <tt><wenzeslaus at gmail com></tt>.

== Organizing Committee ==

* Vaclav Petras, North Carolina State University, Center for Geospatial Analytics ''as a Chair''
* Anna Petrasova, North Carolina State University, Center for Geospatial Analytics ''as a Developer Representative''
* Corey White, North Carolina State University, Center for Geospatial Analytics ''as a Contributor Representative''
* Lois Utt, North Carolina State University, Center for Geospatial Analytics ''as a NC State University Liaison''
* Sarah White, North Carolina State University ''as a Program and Design Consultant''
* Doug Newcomb, U.S. Fish and Wildlife Service ''as a User Representative''
* Huidae Cho, New Mexico State University ''as an Representative of US Participants''
* Veronica Andreo, CONICET, Argentina ''as a Representative of International Participants''

[[Category: Code Sprint]]
[[Category: Conferences]]
[[Category: 2025]]

GRASS GSoC 2025 Add JSON output to different tools in C

2025-08-20T14:19:11Z

Annakrat: add category gsoc

{| class="wikitable"
| '''Student Name''' || Nishant Bansal
|-
| '''Organization''' || [https://www.osgeo.org/ OSGeo - Open Source Geospatial Foundation]
|-
| '''Mentor Name''' || Anna Petrasova, Corey White, Vaclav Petras
|-
| '''GitHub Fork''' || [https://github.com/NishantBansal2003/grass View Repo]
|-
| '''GSoC proposal''' || [https://docs.google.com/document/d/1ZPQ9RXU7b_RUDmBmAMeK7ZjFAV1WC7Urd1Zlz678jyw/edit?tab=t.0#heading=h.z6ne0og04bp5 View Proposal]
|}

= Abstract =
Currently, most GRASS tools produce data in plain text by default. This means that users who want to process the output in Python need to create custom parsing code. To make this easier, several modules could be improved by oﬀering JSON as an alternative output format. Recently, the Parson library was added to the GRASS codebase to support JSON output in addition to plain text. Building on the advancements made during the last GSoC, my project aims to expand JSON output capabilities to more tools using the Parson library. I will also work on making the JSON structure introduced in the previous GSoC more useful and consistent. Additionally, I plan to add support for SHELL and CSV output formats to the relevant tools where appropriate.

= Goal =

# Working with mentors to finalize the structure of the JSON output.
# Adding an option to choose the output format (plain text or JSON) for each updated tool.
# Make the JSON structure introduced during the last GSoC more useful and consistent across tools.
# Developing Python test cases to ensure that the JSON output works correctly and to avoid future issues.
# Providing basic documentation and example JSON outputs for each modified tool.
# Adding support for SHELL and CSV output formats to the relevant tools where appropriate.
# Develop simple examples demonstrating how to use JSON output in a data science workflow, such as reading JSON data into pandas or python.

= Timeline =
{| class="wikitable"
!Period !! Timeline !! Tasks !! Status
|-
| Bonding Period
||
May 8 - June 1
||
# Reviewed the work done during the last GSoC to stabilize the JSON output.
# Discussed the priority tools for adding JSON support.
# Read GRASS documentation to add Python and JSON examples to the documentation.
||
OK OK OK
|-
| rowspan="13" | Official Coding Period
|-
| '''Week 1''' (June 2 - June 8) ||
# Add JSON support for g.mapset [https://github.com/OSGeo/grass/pull/5810 #5810]
# Fix uninitialized zone_value in r.univar [https://github.com/OSGeo/grass/pull/5821 #5821]
# Add JSON support for r.what.color [https://github.com/OSGeo/grass/pull/5822 #5822]
# Update test file in r.info [https://github.com/OSGeo/grass/pull/5842 #5842]
# Improve interface for r.info [https://github.com/OSGeo/grass/pull/5859 #5859]
||
OK OK OK OK OK
|-
| '''Week 2''' (June 9 - June 15) ||
# Add JSON support for g.version [https://github.com/OSGeo/grass/pull/5863 #5863]
# Add JSON support for i.group [https://github.com/OSGeo/grass/pull/5870 #5870]
# Add test file in r.stats [https://github.com/OSGeo/grass/pull/5879 #5879]
# Add tests for JSON output in r.stats [https://github.com/OSGeo/grass/pull/5892 #5892]
||
OK OK OK OK
|-
| '''Week 3''' (June 16 - June 22) ||
# Update the JSON output schema of v.distance [https://github.com/OSGeo/grass/pull/5898 #5898]
# Fix uninitialized window variable in r.stats [https://github.com/OSGeo/grass/pull/5900 #5900]
# Add test file in g.list [https://github.com/OSGeo/grass/pull/5906 #5906]
# Add JSON support for g.list [https://github.com/OSGeo/grass/pull/5921 #5921]
# Update the JSON output schema of g.region [https://github.com/OSGeo/grass/pull/5929 #5929]
||
OK OK OK OK OK
|-
| '''Week 4''' (June 23 - June 29) ||
# Update the JSON output schema of v.to.db [https://github.com/OSGeo/grass/pull/5946 #5946]
# Update the JSON output schema of r.profile [https://github.com/OSGeo/grass/pull/5962 #5962]
# Add SHELL and CSV output support for r.univar [https://github.com/OSGeo/grass/pull/5966 #5966]
||
OK OK OK
|-
| '''Week 5''' (June 30 - July 6) ||
# Add test file in r.regression.line [https://github.com/OSGeo/grass/pull/5990 #5990]
# Add JSON support for r.regression.line [https://github.com/OSGeo/grass/pull/5993 #5993]
# Add test file in r.stats.quantile [https://github.com/OSGeo/grass/pull/6002 #6002]
# Add JSON support for r.stats.quantile [https://github.com/OSGeo/grass/pull/6007 #6007]
# Add test file in r.volume [https://github.com/OSGeo/grass/pull/6027 #6027]
# Add JSON support for r.volume [https://github.com/OSGeo/grass/pull/6036 #6036]
||
OK OK OK OK OK OK
|-
| '''Week 6''' (July 7 - July 13) ||
# Add JSON support for db.columns [https://github.com/OSGeo/grass/pull/6042 #6042]
# Add test file in m.measure [https://github.com/OSGeo/grass/pull/6051 #6051]
# Add test file in db.connect [https://github.com/OSGeo/grass/pull/6052 #6052]
# Add JSON support for m.measure [https://github.com/OSGeo/grass/pull/6053 #6053]
# Add JSON support for db.connect [https://github.com/OSGeo/grass/pull/6059 #6059]
||
OK OK OK OK OK
|-
| '''Week 7''' (July 14 - July 20) ||
# Add test file in r.regression.multi [https://github.com/OSGeo/grass/pull/6066 #6066]
# Add test file in v.db.connect [https://github.com/OSGeo/grass/pull/6067 #6067]
# Add JSON support for r.regression.multi [https://github.com/OSGeo/grass/pull/6075 #6075]
# Add JSON support for v.db.connect [https://github.com/OSGeo/grass/pull/6077 #6077]
||
OK OK OK OK
|-
| '''Week 8''' (July 21 - July 27) ||
# Add JSON support for g.findfile [https://github.com/OSGeo/grass/pull/6091 #6091]
# Add test file in r3.info [https://github.com/OSGeo/grass/pull/6098 #6098]
# Add JSON support for r3.info [https://github.com/OSGeo/grass/pull/6103 #6103]
# Add test file in v.what.rast [https://github.com/OSGeo/grass/pull/6109 #6109]
||
OK OK OK OK
|-
| '''Week 9''' (July 28 - August 3) ||
# Update format to CSV instead of shell in v.category [https://github.com/OSGeo/grass/pull/6132 #6132]
# Add CSV output support to r.stats [https://github.com/OSGeo/grass/pull/6133 #6133]
# Add CSV headers to r.volume [https://github.com/OSGeo/grass/pull/6134 #6134]
# Add JSON support for v.what.rast [https://github.com/OSGeo/grass/pull/6140 #6140]
# Add CSV output support to r.profile [https://github.com/OSGeo/grass/pull/6145 #6145]
# Update test cases in r.distance [https://github.com/OSGeo/grass/pull/6150 #6150]
||
OK OK OK OK OK OK
|-
| '''Week 10''' (August 4 - August 10) ||
# Address review comments on my open PRs.
||
OK
|-
| '''Week 11''' (August 11 - August 17) ||
# Add JSON and CSV support for r.distance [https://github.com/OSGeo/grass/pull/6204 #6204]
# Add more test cases in v.class [https://github.com/OSGeo/grass/pull/6205 #6205]
# Add JSON and CSV support for v.class [https://github.com/OSGeo/grass/pull/6210 #6210]
||
OK OK OK
|-
| '''Week 12''' (August 18 - August 24) || ||
|-
| rowspan="2" | Evaluation Period
|-
| August 25 - September 1 || ||
|}

= Reports =
== Community Bonding Period ==

'''What did I get done this week?'''
* Introduced myself on the [https://discourse.osgeo.org/t/gsoc-2025-introduction-nishant-bansal/147005 OSGeo Discourse mailing list].
* Created both my [https://wiki.osgeo.org/wiki/User:Nishantbansal2003 personal Wiki page] and the [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2025_Add_JSON_output_to_different_tools_in_C project Wiki page], adding all necessary project-related information.
* Read GRASS documentation to support the addition of Python and JSON examples.
* Worked on the following pull requests:
** [https://github.com/OSGeo/grass/pull/5688 #5688]
** [https://github.com/OSGeo/grass/pull/5773 #5773]
** [https://github.com/OSGeo/grass/pull/5775 #5775]
** [https://github.com/OSGeo/grass/pull/5784 #5784]
** [https://github.com/OSGeo/grass/pull/5785 #5785]

'''What do I plan on doing next week?'''
* Add JSON output support to the g.mapset and r.what.color modules.
* If time permits, I will begin improving the r.info interface: [https://github.com/OSGeo/grass/issues/5793 Issue #5793]

'''Am I blocked on anything?'''
* No, I am not currently blocked on anything.

'''Project Discussions and Meetings'''
* '''14 May 2025''': Introductory meeting discussing JSON support and overall project milestones.
* '''21 May 2025''': Introduction with fellow developers. Discussed priority tools, adding Python/Pandas examples, and approaches for finalizing the JSON schema for each module.

== Week-1 ==

'''What did I get done this week?'''
* '''g.mapset''': Added JSON output support, now you can use -p and -l flags to get JSON-formatted results.
* '''r.univar''': Fixed a bug causing an uninitialized zone_value.
* '''r.what.color''': Implemented JSON output support. (See PR [https://github.com/OSGeo/grass/pull/5822 #5822])
* '''r.info (regression tests)''': To maintain backward compatibility while updating its interface, I added strong regression tests.
* '''r.info (interface improvements)''': Began improving the module’s interface. (See PR [https://github.com/OSGeo/grass/pull/5859 #5859])

'''What do I plan on doing next week?'''
* Address review comments on my open PRs.
* Add JSON output support to g.version (see issue [https://github.com/OSGeo/grass/issues/5816 #5816]).
* Add JSON output support to i.group (see issue [https://github.com/OSGeo/grass/issues/5815 #5815]).
* If time permits, write tests for r.stats (see issue [https://github.com/OSGeo/grass/issues/5814 #5814]).

'''Am I blocked on anything?'''
* No, I am not currently blocked on anything.

== Week-2 ==

'''What did I get done this week?'''
* '''g.version''': Implemented JSON output support. (See PR [https://github.com/OSGeo/grass/pull/5863 #5863])
* '''i.group''': Implemented JSON output support. (See PR [https://github.com/OSGeo/grass/pull/5870 #5870])
* '''r.stats (regression tests)''': To maintain backward compatibility while adding JSON format, I added strong regression tests.
* '''r.stats''': Added tests for JSON output; this uncovered a bug, which was fixed alongside.

'''What do I plan on doing next week?'''
* Address review comments on my open PRs.
* Update JSON output format of v.distance (see issue [https://github.com/OSGeo/grass/issues/5846 #5846]).
* Add JSON output support to g.list (see issue [https://github.com/OSGeo/grass/issues/5848 #5848]).
* If time permits, fix the JSON output format of g.region (see issue [https://github.com/OSGeo/grass/issues/5828 #5828]).

'''Am I blocked on anything?'''
* No, I am not currently blocked on anything.

== Week-3 ==

'''What did I get done this week?'''
* '''v.distance''': Updated the JSON output schema. (See PR [https://github.com/OSGeo/grass/pull/5898 #5898])
* '''r.stats''': Fixed a bug causing an uninitialized <code>window</code> variable.
* '''g.list (regression tests)''': To maintain backward compatibility while adding JSON format, I added strong regression tests.
* '''g.list''': Implemented JSON output support. (See PR [https://github.com/OSGeo/grass/pull/5921 #5921])
* '''g.region''': Updated the JSON output schema. (See PR [https://github.com/OSGeo/grass/pull/5929 #5929])

'''What do I plan on doing next week?'''
* Address review comments on my open PRs.
* Update JSON output format of v.to.db (see issue [https://github.com/OSGeo/grass/pull/5711 #5711]).
* Update JSON output format and documentation of r.profile (see issue [https://github.com/OSGeo/grass/pull/5834 #5834]).
* If time permits, add shell and csv output formats to r.univar (see issue [https://github.com/OSGeo/grass/pull/5824 #5824]).

'''Am I blocked on anything?'''
* No, I am not currently blocked on anything.

== Week-4 ==

'''What did I get done this week?'''
* '''v.to.db''': Updated the JSON output schema. (See PR [https://github.com/OSGeo/grass/pull/5946 #5946])
* '''r.profile''': Updated the JSON output schema. (See PR [https://github.com/OSGeo/grass/pull/5962 #5962])
* '''r.univar''': Implemented SHELL and CSV output support. (See PR [https://github.com/OSGeo/grass/pull/5966 #5966])

'''What do I plan on doing next week?'''
* Add JSON output support to r.regression.line (see issue [https://github.com/OSGeo/grass/pull/5950 #5950]).
* Add JSON output support to r.stats.quantile (see issue [https://github.com/OSGeo/grass/pull/5951 #5951]).
* Add JSON output support to r.volume (see issue [https://github.com/OSGeo/grass/pull/5949 #5949]).

'''Am I blocked on anything?'''
* No, I am not currently blocked on anything.

== Week-5 ==

'''What did I get done this week?'''
* '''r.regression.line (regression tests)''': To maintain backward compatibility while adding JSON format, I added strong regression tests.
* '''r.regression.line''': Implemented JSON output support. (See PR [https://github.com/OSGeo/grass/pull/5993 #5993])
* '''r.stats.quantile (regression tests)''': To maintain backward compatibility while adding JSON format, I added strong regression tests.
* '''r.stats.quantile''': Implemented JSON output support. (See PR [https://github.com/OSGeo/grass/pull/6007 #6007])
* '''r.volume (regression tests)''': To maintain backward compatibility while adding JSON format, I added strong regression tests.
* '''r.volume''': Implemented JSON output support. (See PR [https://github.com/OSGeo/grass/pull/6036 #6036])

'''What do I plan on doing next week?'''
* Add JSON output support to m.measure (see issue [https://github.com/OSGeo/grass/pull/6006 #6006]).
* Add JSON output support to db.columns (see issue [https://github.com/OSGeo/grass/pull/6008 #6008]).
* Add JSON output support to db.connect (see issue [https://github.com/OSGeo/grass/pull/6009 #6009]).

'''Am I blocked on anything?'''
* No, I am not currently blocked on anything.

== Week-6 ==

'''What did I get done this week?'''
* '''db.columns''': Implemented JSON output support. (See PR [https://github.com/OSGeo/grass/pull/6042 #6042])
* '''m.measure (regression tests)''': To maintain backward compatibility while adding JSON format, I added strong regression tests.
* '''db.connect (regression tests)''': To maintain backward compatibility while adding JSON format, I added strong regression tests.
* '''m.measure''': Implemented JSON output support. (See PR [https://github.com/OSGeo/grass/pull/6053 #6053])
* '''db.connect''': Implemented JSON output support. (See PR [https://github.com/OSGeo/grass/pull/6059 #6059])

'''What do I plan on doing next week?'''
* Add JSON output support to v.db.connect (see issue [https://github.com/OSGeo/grass/pull/6014 #6014]).
* Add JSON output support to r.regression.multi (see issue [https://github.com/OSGeo/grass/pull/6010 #6010]).
* If time permits, add JSON output support to g.findfile (see issue [https://github.com/OSGeo/grass/pull/6005 #6005]).
* If time permits, add JSON output support to r3.info (see issue [https://github.com/OSGeo/grass/pull/5995 #5995]).

'''Am I blocked on anything?'''
* No, I am not currently blocked on anything.

== Week-7 ==

'''What did I get done this week?'''
* '''r.regression.multi (regression tests)''': To maintain backward compatibility while adding JSON format, I added strong regression tests.
* '''v.db.connect (regression tests)''': To maintain backward compatibility while adding JSON format, I added strong regression tests.
* '''r.regression.multi''': Implemented JSON output support. (See PR [https://github.com/OSGeo/grass/pull/6075 #6075])
* '''v.db.connect''': Implemented JSON output support. (See PR [https://github.com/OSGeo/grass/pull/6077 #6077])

'''What do I plan on doing next week?'''
* Address review comments on my open PRs.
* Add JSON output support to g.findfile (see issue [https://github.com/OSGeo/grass/pull/6005 #6005]).
* Add JSON output support to r3.info (see issue [https://github.com/OSGeo/grass/pull/5995 #5995]).
* If time permits, add JSON output support to v.what.rast (see issue [https://github.com/OSGeo/grass/pull/6024 #6024]).

'''Am I blocked on anything?'''
* No, I am not currently blocked on anything.

== Week-8 ==

'''What did I get done this week?'''
* '''g.findfile''': Implemented JSON output support. (See PR [https://github.com/OSGeo/grass/pull/6091 #6091])
* '''r3.info (regression tests)''': Added regression tests to ensure backward compatibility with new JSON support and fixed a flag-handling bug.
* '''r3.info''': Implemented JSON output support. (See PR [https://github.com/OSGeo/grass/pull/6103 #6103])
* '''v.what.rast (regression tests)''': Added regression tests to ensure backward compatibility with new JSON support and fixed a sorting bug.

'''What do I plan on doing next week?'''
* Address review comments on my open PRs.
* Add JSON output support to v.what.rast (see issue [https://github.com/OSGeo/grass/pull/6024 #6024]).
* Update format to CSV instead of shell in v.category (see issue [https://github.com/OSGeo/grass/pull/6025 #6025]).
* Add CSV output support to r.stats (see issue [https://github.com/OSGeo/grass/issues/5835 #5835]).
* If time permits, add CSV output support to r.profile (see issue [https://github.com/OSGeo/grass/issues/5958 #5958]).
* If time permits, add CSV headers to r.volume (see issue [https://github.com/OSGeo/grass/issues/6049 #6049]).

'''Am I blocked on anything?'''
* No, I don’t have any blockers this week. However, I’ll be a little busy with some personal work from August 3 to August 10, so I’ll try to complete next week’s tasks this week itself.

== Week-9 ==

'''What did I get done this week?'''
* '''v.category''': Updated format to CSV instead of shell. (See PR [https://github.com/OSGeo/grass/pull/6132 #6132])
* '''r.stats''': Implemented CSV output support. (See PR [https://github.com/OSGeo/grass/pull/6133 #6133])
* '''r.volume''': Implemented CSV column headers support. (See PR [https://github.com/OSGeo/grass/pull/6134 #6134])
* '''v.what.rast''': Implemented JSON output support. (See PR [https://github.com/OSGeo/grass/pull/6140 #6140])
* '''r.profile''': Implemented CSV output support. (See PR [https://github.com/OSGeo/grass/pull/6145 #6145])
* '''r.distance (regression tests)''': Updated regression tests to ensure backward compatibility with new JSON support. (See PR [https://github.com/OSGeo/grass/pull/6150 #6150])

'''What do I plan on doing next week?'''
* I’ll be a bit busy with some personal work from August 3 to 10, so I completed next week’s tasks last week itself. I’ve already informed my mentors about my limited availability.

'''Am I blocked on anything?'''
* Yes, I’ll be a bit busy with some personal work from August 3 to 10.

== Week-10 ==

'''What did I get done this week?'''
* This week I was busy with some personal work, so I did not complete any additional tasks. However, I had already finished this week’s tasks last week. This week, I mostly focused on handling reviews for those PRs.

'''What do I plan on doing next week?'''
* Add JSON output support to r.distance (see issue [https://github.com/OSGeo/grass/issues/6135 #6135]).
* Add JSON output support to v.class (see issue [https://github.com/OSGeo/grass/issues/6136 #6136]).

'''Am I blocked on anything?'''
* No, I am not currently blocked on anything.

== Week-11 ==

'''What did I get done this week?'''
* '''r.distance''': Implemented JSON and CSV output support. (See PR [https://github.com/OSGeo/grass/pull/6204 #6204])
* '''v.class''': Updated regression tests to ensure backward compatibility with new JSON support and fixed a out-of-bounds bug. (See PR [https://github.com/OSGeo/grass/pull/6205 #6205])
* '''v.class''': Implemented JSON and CSV output support. (See PR [https://github.com/OSGeo/grass/pull/6210 #6210])

'''What do I plan on doing next week?'''
* Address review comments on my open PRs.
* Discuss next week’s tasks with my mentors, if no issues are assigned, I’ll identify tools that currently lack JSON support and evaluate which ones are feasible to add it to.
* Write the final GSoC report summarizing the work completed, changes merged, and next steps.

'''Am I blocked on anything?'''
* No, I am not currently blocked on anything.

= Log of Pull Requests =
Below is a list of pull requests submitted to the GRASS repository during GSoC 2025:
{| class="wikitable"
!Pull Request !! Description !! Date !! Status
|-
| [https://github.com/OSGeo/grass/pull/5688 #5688] || r.univar: Fix JSON structure || May 20, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5773 #5773] || r.what.color: Add test file || May 25, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5775 #5775] || g.mapset: Add test file || May 26, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5784 #5784] || r.info: Add Python example || May 28, 2025 || Closed
|-
| [https://github.com/OSGeo/grass/pull/5785 #5785] || g.region: Add Python example || May 28, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5810 #5810] || g.mapset: Add JSON support || June 2, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5821 #5821] || r.univar: Fix uninitialized zone_value || June 3, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5822 #5822] || r.what.color: Add JSON support || June 3, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5842 #5842] || r.info: Update test file || June 5, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5859 #5859] || r.info: Improve interface || June 7, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5863 #5863] || g.version: Add JSON support || June 9, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5870 #5870] || i.group: Add JSON support || June 10, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5879 #5879] || r.stats: Add test file || June 12, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5892 #5892] || r.stats: Add tests for JSON output || June 14, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5898 #5898] || v.distance: Update JSON format || June 16, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5900 #5900] || r.stats: fix uninitialised window value || June 17, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5906 #5906] || g.list: Add test file || June 17, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5921 #5921] || g.list: Add JSON support || June 20, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5929 #5929] || g.region: Update JSON format || June 21, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5946 #5946] || v.to.db: Update JSON format || June 23, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5962 #5962] || r.profile: Update JSON format || June 25, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5966 #5966] || r.univar: Add shell and CSV format || June 25, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5990 #5990] || r.regression.line: Add test file || June 30, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/5993 #5993] || r.regression.line: Add JSON support || June 30, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6002 #6002] || r.stats.quantile: Add test file || July 1, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6007 #6007] || r.stats.quantile: Add JSON support || July 1, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6027 #6027] || r.volume: Add test file || July 4, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6036 #6036] || r.volume: Add JSON support || July 6, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6042 #6042] || db.columns: Add JSON support || July 7, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6051 #6051] || m.measure: Add test file || July 10, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6052 #6052] || db.connect: Add test file || July 10, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6053 #6053] || m.measure: Add JSON support || July 11, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6059 #6059] || db.connect: Add JSON support || July 12, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6066 #6066] || r.regression.multi: Add test file || July 15, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6067 #6067] || v.db.connect: Add test file || July 15, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6075 #6075] || r.regression.multi: Add JSON support || July 18, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6077 #6077] || v.db.connect: Add JSON support || July 19, 2025 || Open
|-
| [https://github.com/OSGeo/grass/pull/6091 #6091] || g.findfile: Add JSON support || July 21, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6098 #6098] || r3.info: Add test file || July 22, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6103 #6103] || r3.info: Add JSON support || July 23, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6109 #6109] || v.what.rast: Add test file || July 24, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6132 #6132] || v.category: Use CSV format instead of shell format || July 28, 2025 || Open
|-
| [https://github.com/OSGeo/grass/pull/6133 #6133] || r.stats: add CSV support || July 28, 2025 || Open
|-
| [https://github.com/OSGeo/grass/pull/6134 #6134] || r.volume: add csv column headers || July 28, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6140 #6140] || v.what.rast: Add JSON support || July 29, 2025 || Open
|-
| [https://github.com/OSGeo/grass/pull/6145 #6145] || r.profile: Add CSV support || July 30, 2025 || Open
|-
| [https://github.com/OSGeo/grass/pull/6150 #6150] || r.distance: Update existing test cases || August 1, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6204 #6204] || r.distance: Add JSON and CSV support || August 12, 2025 || Open
|-
| [https://github.com/OSGeo/grass/pull/6205 #6205] || v.class: Add more test cases and fix out-of-bounds bug || August 12, 2025 || Merged
|-
| [https://github.com/OSGeo/grass/pull/6210 #6210] || v.class: Add JSON and CSV support || August 15, 2025 || Open
|}

{{GSoC}}

GRASS GSoC Ideas 2025

2025-08-20T14:18:28Z

Annakrat: accepted ideas

== About ==

* [https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2025_Ideas The OSGeo GSoC 2025 main page]
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== Accepted ideas ==
=== Add JSON output to different GRASS tools in C ===
* Student: Nishant Bansal
* Mentors: Anna Petrasova, Vaclav Petras and Corey White
* [[GRASS_GSoC_2025_Add_JSON_output_to_different_tools_in_C|Wiki page]]

== Ideas ==
If you are a student you can suggest a new idea or pick up an existing one. In any case write about it to [https://discourse.osgeo.org/c/grass/developer/61 OSGeo Discourse forum for GRASS developers],[https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].

You are invited as well to have a close look at ideas from previous years ([https://trac.osgeo.org/grass/wiki/GSoC/2014 2014], [https://trac.osgeo.org/grass/wiki/GSoC/2015 2015], [https://trac.osgeo.org/grass/wiki/GSoC/2016 2016],
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])
which have not yet been implemented.
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''

Include "GRASS GIS" in the title of our idea to easily distinguish ideas and projects inside OSGeo.

=== Parallelization of existing tools ===

There are several tools that would benefit from parallelization with OpenMP, e.g. r.texture, r.horizon, r.fill.stats, r/v.surf.idw, r.viewshed, v.to.rast, r.grow.distance, v.surf.bspline, ...
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].

* Requirements: familiarity with C, OpenMP
* Mentor: Huidae Cho
* Co-mentor: Vaclav Petras, Anna Petrasova
* Project length: 175 or 350 hours (take your pick)
* Rating: medium
* Expected Outcomes: parallelized module or modules, depending on complexity
* Test of skills: suggest/implement solution for https://github.com/OSGeo/grass/issues/2644

=== Improve GRASS user experience in Jupyter Notebook ===
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]
Python package [https://grass.osgeo.org/grass-stable/manuals/libpython/grass.jupyter.html grass.jupyter] was developed during [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS GSoC 2021] to simplify running GRASS from Jupyter Notebooks and displaying data. This project could focus on adding features such as increasing interactivity of displayed data using ipyleaflet, adding API for managing projects and subprojects (i.e., locations/mapsets), creating GUI for commands, ...

* Requirements: Python
* Mentor: Anna Petrasova
* Co-mentor: Vaclav Petras, Helena Mitasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: improved user experience when using GRASS through notebooks
* Test of skills: https://github.com/OSGeo/grass/issues/3276, or write a test for [https://github.com/OSGeo/grass/tree/main/python/grass/jupyter grass.jupyter library] using python unittest or pytest, more info [https://grass.osgeo.org/grass-devel/manuals/libpython/gunittest_testing.html here].

=== Add JSON output to different tools in C ===
There are several tools in GRASS that would benefit from a JSON-formatted output, see [https://github.com/OSGeo/grass/issues/3020 this issue for a list of tools]. Besides adding the JSON output, the work would also include adding tests and basic documentation.
* Requirements: C, Python for tests
* Mentor: Vaclav Petras
* Co-mentor: Anna Petrasova, Corey White
* Project length: 175 or 350 hours (take your pick)
* Rating: easy to medium
* Expected Outcomes: one or more (depending on project length and complexity of the tool) tools with well tested JSON output
* Test of skills: Address https://github.com/OSGeo/grass/issues/1044 for r.surf.fractal

=== Support writing tests with pytest ===

* The current testing framework, ''[https://grass.osgeo.org/grass-stable/manuals/libpython/gunittest.html grass.gunittest]'', was written before migration to Git/GitHub and when long free runs in 3rd party services were unthinkable. Additionally, some no longer relevant goals were prioritized, such as independence on the current code, detailed custom HTML reports, success tracking over time, and high specialization towards GRASS-specifics.
* ''grass.gunittest'' is based on Python ''unittest'' package and many projects since then migrated to //pytest//, e.g., GDAL and Numpy. While ''unittest'' is inspired by Java's JUnit, ''pytest'' is designed to support writing small, readable tests, and uses plain `assert` statements instead of many different assert methods.
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.
* An example issue of ''grass.gunittest'' is that it doesn't work well with tests of the main GRASS executable (prominence of `grass ... --exec` is yet another new thing which changed since ''grass.gunittest'' was designed).
* Two main things needed:
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.
** Current grass.script.setup.init function and grass.script.core.create_location function don't work well in the context of a pytest test function. More
* Additional things needed:
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.

* Requirements: Python
* Project length: 175 or 350 hours (take your pick)
* Mentor: Vaclav Petras
* Co-mentor: Stefan Blumentrath
* Proposed by: Vaclav Petras
* Rating: easy to medium
* Expected Outcomes: Convenient way of writing tests with pytest
* Test of skills: Fix failing tests and/or write new tests (more is better). Alternatively, addressing a smaller problem in the testing framework is a good task, too.

=== New easy-to-use CLI and API for GRASS GIS ===

* Make running of GRASS GIS modules as easy as it is to run GDAL commands.
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`
** CLI like GDAL has.
** No GRASS Database, Location, Mapset to deal with.
** No import, export from user perspective.
** Reasonable defaults for things like region.
** CLI and API still allows user to specify any of the above.
* Idea page with details: wiki:GSoC/2021/EasyToUseCliAndApiIdea
* Project length: 350 hours
* Rating: medium
* Requirements:
** Language: Python
** Proposal: Student needs to show sufficient understanding of the GRASS GIS Database structure and significantly extend on text below in terms of more concrete formulation of ideas and identification of missing and existing parts.
* Mentors: Vaclav Petras
* Co-mentors: Stefan Blumentrath, Corey White
* Proposed by: Vaclav Petras
* Expected outcomes: New subcommand which easily runs a GRASS module on GeoTiff and GeoPackage.
* Test and training tasks:
** Solve one of the tickets linked at the idea page.
** Add features to `grass` executable interface:
*** Make it possible to associate `*.gxw` files with `grass` executable (#1204) or at least add `--gui-workspace` or preferably just recognize it in the command line (distinguish it from database/location/mapset).
** Extend `--exec` functionality:
*** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`
*** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).
*** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).



=== GUI: Add space-time datasets support in Data Catalog ===
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]
Currently GRASS Data Catalog shows only raster and vector maps. The goal of this project is to add support for space-time datasets. It is mainly space-time raster datasets. In the next phase of the project support for other types of space-time datasets (vector and 3D raster) could be added. Besides displaying space-time datasets in the layer tree, it is also about adding the equivalent functionality currently available for raster and vector layers from the context menu.

* Requirements: familiar with Python
* Project length: 175 or 350 hours
* Mentor: Martin Landa
* Co-mentor: Anna Petrasova
* Proposed by: Martin Landa
* Rating: medium
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)
* Test of skills:
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599

=== Add {your research idea} to GRASS GIS ===

* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS GIS.
* Requirements:
** Language:
*** Depends on the project, often Python, sometimes C.
*** Adding your latest ecological analysis
** Proposal:
*** Discuss relevance to GRASS GIS.
*** Describe technical steps needed for integration.
*** Describe whether it is an addition of a tool (module) or a change in one of the libraries. If it is a tool, specify if it should be included in the core grass repository or in grass-addons repository and why.
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.
*** Specify who will provide the research expertise.
* Project length: 175 or 350 hours (take your pick)
* Rating: from low to hard
* Mentors:
** GRASS GIS project will provide technical mentors, but it is up to the applicant to ensure the research part is mentored well. An exception may be granted to applicants which can demonstrate that the research is finished or that they have enough expertise themselves.
** Possible technical mentors: Vaclav Petras, Anna Petrasova
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).
* Proposed by: Vaclav Petras
* Expected outcome: Working feature which is integrated and merged at the end of the project.
* Test and training tasks:
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.

=== Title of idea ===

Description here

* Requirements:
* Project length: (175 or 350 hours)
* Mentor:
* Proposed by:
* Rating:
* Expected Outcomes:
* Test of skills:
* Other:

== Tips for students ==

* If you have your own ideas we encourage you to propose them. Explain them on the [https://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list].
* If you like some idea here or from previous yeas, write about it on [https://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list] and any ideas of your own which could improve it.
* Follow some good practices in your ideas and proposals:
** Stress why the project would be useful.
** Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
** Be specific in the implementation (or at least as specific as you can).
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.
** Explain how the idea relates to existing GRASS GIS functions, features, and needs.
** Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
* Compile GRASS GIS from source and prepare environment for development:
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file] and [https://grasswiki.osgeo.org/wiki/Compile_and_Install compilation instructions].
** If you get stuck with the setup, feel free to consult the [https://lists.osgeo.org/listinfo/grass-user grass-user mailing list].
** Familiarize yourself with wiki:Submitting rules.
* Prove your worth by being active on the GRASS mailing lists ([https://lists.osgeo.org/listinfo/grass-user grass-user], [https://lists.osgeo.org/listinfo/grass-dev grass-dev]) or other channels ([https://github.com/OSGeo/grass/discussions GitHub Discussions], [https://gitter.im/grassgis/community Gitter]), fix some [https://github.com/OSGeo/grass/issues bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. Do this before start you apply to GSoC.
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

* Every year GRASS GIS hopes to participate and participates in GSoC as part of the [https://www.osgeo.org/ OSGeo Foundation]'s GSoC program umbrella. See the official OSGeo template for application details and other important information at the [https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students OSGeo Recommendations for Students].

{{GSoC}}

NSF POSE Project 2023-2025 Timeline

2025-06-05T20:04:23Z

Annakrat: /* Y2 4th quarter report (06/25 - 08/25) */

[[File:NSF_grant_announcement.png|500px|right|none]]

To inform GRASS community about the work done as part of the award [https://www.nsf.gov/awardsearch/showAward?AWD_ID=2303651 2303651] from the U.S. National Science Foundation (NSF) to enhance GRASS ecosystem, the following report summarizes the progress and outcomes in quarterly reports and presents the roadmap for the project.

The two main goals of the project are: 1) to facilitate the adoption of GRASS GIS as a key geoprocessing engine by a growing number of researchers and geospatial practitioners in academia, governments, and industry; and 2) to expand and diversify the developer community, especially through supporting next-generation scientists to gain expertise to maintain and innovate GRASS software.

Principal investigators and senior personnel:

* Helena Mitasova, North Carolina State University (Principal Investigator)
* Vaclav Petras, North Carolina State University (Co-Principal Investigator)
* Anna Petrasova, North Carolina State University (Co-Principal Investigator)
* C Michael Barton, Arizona State University (Co-Principal Investigator)
* Huidae Cho, New Mexico State University (Co-Principal Investigator)
* Giuseppe Amatulli, Yale (Senior Personnel)

Other personnel who is joining for the execution of the grant is listed below when relevant.

== Y1 1st quarter report (09/23 - 11/23) ==
=== Project Announcements and Communication ===
* Announcement on [https://grass.osgeo.org/news/2023_09_06_nsf_grant_awarded/ GRASS website].
* Info session to explain the POSE Project ([https://lists.osgeo.org/pipermail/grass-user/2023-September/083423.html Announcement on GRASS user mailing list], 2 sessions for different time zones).
* Collected statistics from GitHub, X and others and set up automated collection for GitHub.

=== Conference Presentations ===
* [https://petrasovaa.github.io/FUTURES-CONUS-talk/foss4gNA2023.html#/ Parallelization Tips for Geoprocessing with GRASS GIS] by Anna Petrasova at FOSS4GNA, October 2023.
* [https://wenzeslaus.github.io/grass-gis-talks/foss4gna2023.html#/ GRASS GIS: Not What You Think] by Vaclav Petras at FOSS4GNA, October 2023.
* [https://docs.google.com/presentation/d/1D-Fh1cLSPINyeXdVaxlakrE9IjB8kK5lIw3D12yX1bk Computational Notebooks for Reproducible Geospatial Computation in Research and Education] by Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/HuidaeCho/grass-gis-talk-foss4g-asia-2023 State of GRASS GIS: 40 Years Strong and Counting] by Huidae Cho at FOSS4G Asia, November 2023.

=== Training and Workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-foss4gna-2023 Unlock the power of GRASS GIS] by Anna Petrasova and Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/develop-tools-with-grass-foss4gna-2023 Develop Geospatial Workflows and Custom Tools with GRASS GIS] by Vaclav Petras and Corey White at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/grass-workshop-gis-week-2023 Big Data Computing with GRASS GIS] by Anna Petrasova and Vaclav Petras at NC State GIS week, November 2023.
* [https://github.com/ncsu-geoforall-lab/grass-gis-on-hpc-henry2/blob/8564c72e9b8929c9ef4d25ada1ef36b569991221/docs/tutorial.md GIS Week Workshop: High Performance Computing for Geospatial Analysis (GRASS GIS part)] by Vaclav Petras (main lecture lead by Andrew Petersen from NCSU OIT) at NC State GIS week, November 2023.
* [https://spatial-ecology.net/docs/build/html/COURSESAROUNDTHEWORLD/course_geocomp_ml_04-05_2024.html Geocomputation and Machine Learning for Environmental Applications] training course [https://spatial-ecology.net/course-geocomputation-machine-learning-for-environmental-applications-intermediate-level-2024/ announced]. GRASS GIS part led by Giuseppe Amatulli is free of charge thanks to the support by NSF.

=== Community Sprint Participation ===
Anna Petrasova and Vaclav Petras remotely participated in [https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2023 OSGeo 2023 code sprint] doing PR reviews and maintenance of GRASS GIS code, documentation, and website.

=== Mentoring Program ===
* Started a development-oriented mentoring program [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ announced] with details available on a [https://grasswiki.osgeo.org/wiki/Mentoring_Program wiki page].
* Program now has 4 participants (from 12 responses) supported by email and video calls.
* Program already resulted in improvements to GRASS GIS core and addons:
** merged PR: [https://github.com/OSGeo/grass/pull/3206 grass.script: ensure memmap content is flushed before writing to a raster]
** radar addon toolset PR: [https://github.com/OSGeo/grass-addons/pull/949 Add i.saocom and i.sar toolsets]
Mentoring Program is a new effort started and so-far performed only by the POSE team.

=== Student Grants Program ===
Student grants [https://grass.osgeo.org/news/2023_11_09_student_grants_announced/ announced] with topics at a [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants wiki page]. Student Grants Program is an existing effort which the POSE team participates in.

=== Working Groups ===

Four [https://grasswiki.osgeo.org/wiki/Working_Groups working groups] created (scope, wiki page, coordinator, and a list of people for each).

=== Citations ===

* GRASS GIS Google Scholar [https://scholar.google.com/citations?user=gJ0ZB0cAAAAJ account] updated with more complete records.
* A [https://forms.gle/cDEvMJu7d6nvxLKn9 form] was created to collect new and missing records.
* Profile link added to GRASS website [https://grass.osgeo.org/contribute/ Contribute] and [https://grass.osgeo.org/about/citation/ Citation] page.

== Y1 2nd quarter report (12/23 - 02/24) ==
=== NSF I-Corps program ===
Corey White, Vaclav Petras, and Anna Petrasova participated in a 4-week long intensive mandatory training that draws on the methods, customer discovery, and curriculum of the [https://new.nsf.gov/funding/initiatives/i-corps NSF Innovation Corps] and applies them to open-source projects.

The program included conducting 70+ 30-minute interviews with both GRASS users and non-users to better shape the future path of GRASS GIS and the POSE project. So far, the interviews focused on educators, companies, researchers, influencers and it focused more on non-users than users.

Next steps, include processing the collected qualitative data, developing possible future directions for sustainability of the project, discussing these with the Project Steering Committee, the core team of developers, and the broader community.

=== Mentoring Program ===
The development oriented [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ mentoring program] welcomed 5 new participants from various institutions including universities, USGS, US Army Corps of Engineers, and local municipalities. The discussed topics covered developing workflows for topography and network analysis, environmental modeling, and geophysics. Participants were supported by email and video calls.

=== Conference Presentations ===
* [https://agu.confex.com/agu/fm23/meetingapp.cgi/Paper/1342418 Modeling vegetated stream buffer impacts on water depth and discharge at the watershed scale with GRASS GIS and Jupyter Notebooks] by Caitlin Haedrich at AGU, December 2023.
* [https://agu.confex.com/agu/fm23/meetingapp.cgi/Paper/1420596 OpenPlains: A Web-Based Platform to Democratize Geospatial Participatory Modeling on the Cloud] by Corey White at AGU, December 2023.

=== Presentations and Workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-vanderbilt-2024 Intro to GRASS GIS] by Vaclav Petras and Anna Petrasova was remotely delivered to geographers at Vanderbilt University in February 2024. The workshop was developed in Jupyter Lab and run using [https://wholetale.org WholeTale] online platform.
* [https://github.com/tomorrownow/intro-to-geoprocessing-workshop Introduction to GRASS GIS Geospatial Processing] by Corey White at [https://smathhacks.ncssm.edu/ SMathHacks hackathon], March 2nd (supported also by Veronica Andreo and Vaclav Petras). SMathHacks is the annual 36-hour hackathon hosted by the NC School of Science and Math, open to all North Carolina students. Students collaborate to build innovative software projects, explore new technologies, and have fun along the way. The workshop was delivered in person with students using [https://colab.research.google.com/ Google Colab].

=== Student Grant Program ===
Linda Karlovska participates in the [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants Student Grant program] with her project [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation Easy command history navigation through the History browser panel] mentored by Anna Petrasova (POSE team) and Martin Landa (FCE CTU). Student Grants Program is an existing effort which the POSE team participates in by mentoring.

=== Code Security ===
Vaclav Petras mentors four students who create code security improvements in their NCSU class ''CSC 472: Cybersecurity Practicum''. So far, the students created two PRs which were successfully merged:
* [https://github.com/OSGeo/grass/pull/3444 grass.script: Change insecure mktemp to NamedTemporaryFile #3444]
* [https://github.com/OSGeo/grass/pull/3451 utils: fixed shell vulnerability in mkrest.py #3451]

Two other PRs are open and more work is underway to do first steps for new approach to a more secure code.

=== Localized Basic Datasets ===
* NCSU and ASU teams worked on localized versions of GRASS basic data set following the [https://grass.osgeo.org/sampledata/north_carolina/nc_basic_spm_grass7.zip North Carolina basic data set example], preparing Flagstaff, Arizona and Nepal draft version with basic layers

== Y1 3rd quarter report (03/24 - 05/24) ==

=== Mentoring Activities ===
The mentoring program form received 2 new responses and mentors were actively working with 3 mentees.
It resulted in fixes in [https://github.com/OSGeo/grass-addons/pull/1042 v.transects] and [https://github.com/OSGeo/grass-addons/pull/1077 r.accumulate].

Linda Kladivova finished her project developing [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation History browser] in the GRASS GUI as part of the GRASS Student Grant Program. Mentor's time was covered by POSE.

GRASS GIS has [https://grass.osgeo.org/news/2024_05_27_gsoc_2024_students/ 3 students this year for Google Summer of Code]. Time spent managing GSoC for GRASS GIS was covered by POSE.

The topics covered by GSoC projects are:
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_EODAG_Support Add EODAG support to GRASS GIS]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Improve_user_experience_in_Jupyter_Notebooks Improve GRASS user experience in Jupyter Notebook]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Add_JSON_output Add JSON output to different GRASS tools in C]

=== Presentations, Workshops, Event Planning ===
* [https://github.com/ncsu-geoforall-lab/tngic-2024 GRASS 101: From GUI Clicks to Writing Scripts (TNGIC 2024)] by Veronica Andreo and Caitlin Haedrich
* [https://github.com/ncsu-geoforall-lab/csdms-grass-2024 Coastal evolution analysis and inundation modeling with GRASS GIS (CSDMS Workshop 2024)] by Caitlin Haedrich and Pratikshya Regmi, see also [https://cnr.ncsu.edu/geospatial/news/2024/06/03/students-teach-grass-gis-for-coastal-hazard-analysis/ blog post with images]

* Organization of [[GRASS Community Meeting Prague 2024]] and budget planning by Vaclav Petras

=== CMake transition ===
Ongoing work on [https://github.com/OSGeo/grass/pull/3621 CMake compilation] was partially covered by POSE.

=== Code Quality and Security ===

Code quality improvements in Python code:
* [https://github.com/OSGeo/grass/pull/3541 PR addressing Flake8 E501] (long lines in 158 files not fixable by automated tools)
* [https://github.com/OSGeo/grass/pull/3535 PR addressing Flake8 E401] (unused imports)

Vaclav Petras mentored a team of four students who create code security improvements in their NCSU class ''CSC 472: Cybersecurity Practicum''. The team created 12 PRs which were successfully merged, 7 additional experimental PRs (not merged) and 2 PRs which are still open at this time. Specifically, the team achieved the following:

* With the involvement and help from the other contributors, the team introduced Bandit and Coverity Scan as additional code scanning tools for Python and C, respectively.
* The team analyzed issues reported CodeQL, Bandit, and Coverity Scan and reported on relevance of different issues to the project (report privately shared with the GRASS Development Team).
* Vulnerability Triage Guide (also privately shared with the GRASS Development Team).
* The team also developed a [https://github.com/OSGeo/grass/security/policy security policy] for the project.
* The vulnerability reporting and security advisories were enabled based on the team recommendations.
* The team fixed several specific security issues in the code:
** [https://github.com/OSGeo/grass/pull/3469 packaging: Use subprocess instead of os.popen for change log creation #3469] (merged)
** [https://github.com/OSGeo/grass/pull/3549 lib raster: fixed security vulnerabilities and weaknesses #3549] (merged)
** [https://github.com/OSGeo/grass/pull/3451 utils: fixed shell vulnerability in mkrest.py #3451] (merged)
** [https://github.com/OSGeo/grass/pull/3444 grass.script: Change insecure mktemp to NamedTemporaryFile #3444] (merged)
** [https://github.com/OSGeo/grass/pull/3551 lib/psdriver: Fix issues with wrong type of arguments to printf #3551] (PR open)
** [https://github.com/OSGeo/grass/pull/3452 g.region/r.to.rast3elev: fixed scanf error to recognize EOF as a possible return value #3452] (PR open)

=== Documentation ===
* Documentation and Education Working Group met and planned the development of new tutorials. Veronica Andreo met other GRASS developers and contributors to coordinate further tutorials development.
* Development of new [https://github.com/ncsu-geoforall-lab/tutorials tutorials] in progress, topics include:
** Getting started with GRASS GIS
** GRASS GIS in Google Colab
** GRASS GIS and Python
** GRASS GIS and R
** GRASS R and Python comparison
** Making plots in GRASS GIS
* New [https://github.com/OSGeo/grass/blob/main/doc/development/style_guide.md GRASS Programming Style Guide]
* [https://github.com/petrasovaa/cookiecutter-grass-addon New addon template powered by Cookiecutter]
* Analysis of options names and functionality in plotting tools:
** [https://github.com/OSGeo/grass-addons/issues/1071 Addons for plotting: Standardize parameters and flags]

=== Communication and outreach ===

* Creation of 4 news post in the [https://grass.osgeo.org/news/ GRASS website]
* Social media:
** [https://twitter.com/GRASSGIS Twitter]: 9 new posts/threads
** [https://fosstodon.org/@grassgis Fosstodon]: 9 new posts/threads

=== Other sustainability activities ===
* [https://github.com/OSGeo/grass/blob/main/CODE_OF_CONDUCT.md Code of Conduct added to the main repository]
* [https://github.com/OSGeo/grass/blob/main/.github/ISSUE_TEMPLATE/bug_report.md revised Issue template]
* New [https://github.com/OSGeo/grass/pull/3673 RFC for a Release Policy]
* Revised [https://github.com/OSGeo/grass/pull/2815 RFC for Release Procedure]
* WIP: GRASS GIS Roadmap
* [https://github.com/OSGeo/grass-website/issues/414 GRASS website: ongoing restructuring]
* [[PSC]] page moved from trac wiki to media wiki

== Y1 4th quarter report (06/24 - 08/24) ==

=== Mentoring Activities ===
The mentoring program form received 3 new responses and mentors were actively working with 3 mentees.
Results include parallelization of r.texture, r.horizon, improved grass.benchmarking library and a new tutorial on lidar data.

GSoC successfully completed their projects:
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_EODAG_Support Add EODAG support to GRASS GIS]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Improve_user_experience_in_Jupyter_Notebooks Improve GRASS user experience in Jupyter Notebook]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Add_JSON_output Add JSON output to different GRASS tools in C]

Time spent by mentoring was covered by NSF.

=== Presentations, Workshops, Event Planning ===

* [https://veroandreo.github.io/grass_foss4geu_2024/ Let's combine GRASS, Python and R: Satellite time series data for species distribution modeling]. Workshop by Veronica Andreo. FOSS4G Europe 2024, Tartu.
* [https://veroandreo.github.io/grass-gis-talks/foss4gEU2024.html#/ Status of GRASS GIS project]. Talk by Veronica Andreo. FOSS4G Europe 2024, Tartu.
* [https://veroandreo.github.io/grass-gis-talks/useR2024.html#/ Boost Spatial Data Science Workflows with GRASS GIS and R]. Talk by Veronica Andreo. useR Conference 2024, Salzburg.
* [https://ncsu-geoforall-lab.github.io/usdoi-webinar/notebooks/grass_jupyter.html Geoprocessing with GRASS GIS and Jupyter Notebooks]. Webinar by Corey White. U.S. DOI, August 2024, NCSU.
* [[GRASS Community Meeting Prague 2024]]

* [https://spatial-ecology.net/docs/build/html/COURSESAROUNDTHEWORLD/course_GEO-OPEN-HACK-2024_06_2024.html GEO-OPEN-HACK-2024: Big Geospatial Data Hackathon with Open Infrastructure and Tools] training course delivered ([https://iiasa.ac.at/events/jun-2024/geo-open-hack-2024-big-geospatial-data-hackathon-with-open-infrastructure-and-tools announcement]). The GRASS material has been developed as part of the NSF grant.

* Planning GRASS Dev summit 2025 at NCSU

* Planning AGU (4 abstract submitted), AGU booth for GRASS GIS reserved and payed

* Submitted workshop, talk and keynote to FOSS4G 2024 - Brazil.

=== CMake transition ===
Ongoing work on [https://github.com/OSGeo/grass/pull/3621 CMake compilation] was partially covered by POSE.

=== Code Quality and Security ===

* Code quality improvements in Python code:
** [https://github.com/OSGeo/grass/pull/3763 Flake8 W605 Invalid escape sequence #3763]
** [https://github.com/OSGeo/grass/pull/3926 Flake8 E741 Do not use variables named 'I', 'O', or 'l' in wxGUI code #3926]
** [https://github.com/OSGeo/grass/pull/3928 Flake8 E741 for the rest of code base #3928]
** [https://github.com/OSGeo/grass/pull/4200 grass.temporal: Flake8 F841 Local variable assigned to but never used #4200]
** [https://github.com/OSGeo/grass/pull/4113 grass.pygrass: Remove unused arg in ctypes.CFUNCTYPE #4113]
** [https://github.com/OSGeo/grass/pull/4206 t.rast.to.vect: Fix passing column parameter to r.to.vect, fix flake8 F841 #4206]

* Code quality and security improvements in C and C++ code are in 36 PRs with fixes for more than 25 tools, specifically in:
** raster: r.path, r.out.mpeg, r.out.png, r.in.xyz, r.terraflow, r.statistics, r.spreadpath, r.sim.water, r.sim.erosion, r.object.geometry, r.coin
** imagery: i.atcorr, i.aster.toar, i.ortho.photo, i.landsat.acca, i.segment, i.smap
** display: d.linegraph, d.legend.vect, d.histogram, d.labels
** raster 3D: r3.in.v5d, r3.info, r3.mapcalc
** other: lib/gis, lib/vector/diglib, g.findfile, g.setproj, ps.map, lib/cdhc

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShubhamDesai+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ ShubhamDesai], [https://github.com/OSGeo/grass/pulls?q=author%3Amshukuno+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ Makiko Shukunobe], [https://github.com/OSGeo/grass/pulls?q=author%3Aymdatta+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ ymdatta]

Several reviewers, not supported by the NSF POSE project, played crucial role not only in reviewing, but also in determining the right fixes.

Fixed issues were reported by Flake8, Coverity Scan, and Cppcheck.

=== Tests ===

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShreshth-Malik+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ Shreshth-Malik]

=== Documentation ===

* Veronica Andreo met some GRASS developers and contributors to follow up on tutorials development.
* 7 new [https://github.com/ncsu-geoforall-lab/tutorials tutorials] on time series:
** Management and visualization
** Aggregation
** Algebra
** Accumulation
** Gap filling
** Querying raster time series with vectors
** Subset, import and export
* Tutorial on how to set up Jupyter and GRASS in Windows
* New [https://github.com/OSGeo/grass-tutorials repository] under OSGeo organization to host the upcoming quarto based website for GRASS tutorials
* PR template created - [https://github.com/OSGeo/grass/community GitHub Community Standards] all checked complete

=== Communication and outreach ===

* Creation of 4 news posts in the [https://grass.osgeo.org/news/ GRASS website]
* Social media:
** [https://twitter.com/GRASSGIS Twitter]: 25 new posts
** [https://fosstodon.org/@grassgis Fosstodon]: 25 new posts
* New GRASS GIS LinkedIn page at: [https://www.linkedin.com/company/grass-gis/ https://www.linkedin.com/company/grass-gis/]
* Requested transition of [https://discourse.osgeo.org/t/osgeo-3255-migrate-grass-dev-mailing-list-to-discourse/49796 grass-dev mailing list to discourse.osgeo.org]
* Set up GRASS GIS swag shop on Redbubble

=== Governance ===
* [https://grass.osgeo.org/about/roadmap/ Roadmap] and [https://grass.osgeo.org/about/governance/ Governance] pages added to the website
* PSC elections:
** Documented criteria to define people entitled to vote
** Documented procedure to compile the list of voters
** Elections [https://www.mail-archive.com/grass-user@lists.osgeo.org/msg41102.html announcement] sent out

== Y2 1st quarter report (09/24 - 11/24) ==

=== Presentations and Workshops ===
FOSS4GNA 2024 in St. Louis, Missouri:

* Vaclav Petras. State of GRASS GIS. FOSS4G NA St. Louis, September 9-11, 2024 ([https://wenzeslaus.github.io/grass-gis-talks/foss4gna2024.html slides])
* Huidae Cho. Evolution of GRASS GIS. FOSS4G NA St. Louis, September 9-11, 2024 ([https://htmlpreview.github.io/?https://github.com/HuidaeCho/grass-talks/blob/main/foss4g-na-2024.html slides])
* Huidae Cho. An OpenMP Algorithm for Delineating a Large Number of Watersheds. FOSS4G NA St. Louis, September 9-11, 2024
* Corey T. White. Developing Web-Applications with GRASS GIS. Workshop. FOSS4G NA St. Louis, September 9-11, 2024
* Corey T. White. GRASS GIS as a Geospatial Computational Engine. FOSS4G NA St. Louis, September 9-11, 2024

=== Communication and outreach ===
* Transition of grass-dev mailing list to [https://discourse.osgeo.org/c/grass/developer/61 discourse.osgeo.org] finished.

=== Code Quality and Security ===
* Python code quality issues addressed in more than 70 PRs, reducing the list of per-file ignores by more than 60%.
* Code quality and security improvements in C and C++ code are in more than 80 PRs.
* In total, these changes improve more than 60 tools, specifically:
** raster: r.water.outlet, r.watershed, r.mfilter, r.to.vect, r.in.poly, r.carve, r.thin, r.fill.dir, r.clump, r.in.gridatb, r.out.png, r.in.wms, r.viewshed, r.fillnulls, r.in.srtm, r.in.pdal, r.in.xyz
** vector: v.out.dxf, v.build.polylines, v.external.out, v.net, v.univar, v.in.ascii, v.delaunay, v.hull , v.net.timetable, v.kernel, v.to.db, v.colors, v.rectify, v.reclass, v.generalize, v.transform, v.vol.rst, v.cluster, v.to.3d, v.out.ogr, v.external, v.in.dwg, v.report, v.unpack, v.import
** imagery: i.topo.corr, i.attcorr, i.ortho.photo, i.segment, i.rectify, i.topo.corr, i.panshrapen
** display: d.vect, d.mon, d.frame, d.rast.edit
** other: GUI, grass main executable, g.proj, g.version, db.out.ogr, ps.map, r3.in.v5d, r3.in.v5d, lib/vector/Vlib, lib/ogsf, lib/gis, lib/db, lib/lidar, lib/linkm, grass.temporal, grass.script

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShubhamDesai+is%3Apr+is%3Aclosed+merged%3A2024-09-01..2024-11-30+base%3Amain+sort%3Aupdated-desc+ ShubhamDesai], [https://github.com/OSGeo/grass/pulls?q=author%3Aymdatta+is%3Apr+is%3Aclosed+merged%3A2024-09-01..2024-11-30+base%3Amain+sort%3Aupdated-desc+ ymdatta],
[https://github.com/OSGeo/grass/pulls?q=author%3Aarohanajit+is%3Apr+is%3Aclosed+merged%3A2024-09-01..2024-11-30+base%3Amain+sort%3Aupdated-desc+ Arohan Ajit]

Several reviewers, not supported by the NSF POSE project, played crucial role not only in reviewing, but also in determining the right fixes. The NSF POSE project personnel focused on fixing issues reported by Flake8, Coverity Scan, and Cppcheck, however also Ruff and Pylint are utilized in GRASS GIS thanks to other contributors.

A configure file for Cppcheck is now included in the repository highlighting the level of compliance and aiding contributors in local analysis and subsequent implementation of fixes ([https://github.com/OSGeo/grass/pull/4766 PR #4766]).

Finally, we created a new public GitHub project in the OSGeo GitHub organization for [https://github.com/orgs/OSGeo/projects/11 GRASS GIS Security] to track and communicate progress on the security front with 147 resolved items and 8 in-progress items at the time of writing.

=== Documentation, both Internal and External ===

* To improve indexing of GRASS GIS manual pages, we revised our current sitemap ([https://github.com/OSGeo/grass-website/pull/482 grass-website/pull/482)]), added a updated sitemap to Google Search Console and Bing, fixed robots.txt, and triggered and re-triggered the indexing many times to make Google consume the new content. While before, some searches gave outdated documentation, experimental websites, or unofficial resources only, now the official website and stable documentation is returned as the first search result.
* All older manuals, including version 6.4 and 6.5, are now available (restored) so that search engines can consume them and old links and indices continue to work. They now newly contain the canonical URLs so that search engines understand the structure and don't penalize duplicate content.
* On OSGeo server which hosts GRASS GIS website, we replaced some of the redirects in Apache by local soft links so that URL like grass.osgeo.org/grass-stable stay as is for both humans and machines and don't redirect to specific version (easier to copy-paste from a browser URL bar and easier for search engine to understand what is the page to show).
* We implemented the necessary changes into the cronjobs and did overall updates to enable build of the server-side documentation jobs locally for testing purposes. The most relevant PRs are:
** [https://github.com/OSGeo/grass-addons/pull/1241 Inject canonical URLs into older manual pages (SEO) #1241]
** [https://github.com/OSGeo/grass-addons/pull/1173 Fix red new version box injection and script documentation #1173]
** [https://github.com/OSGeo/grass-addons/pull/1215 Expand script to run stand-alone #1215]
* We advanced the [https://github.com/orgs/OSGeo/projects/9 GRASS Markdown Documentation project].
* New and better wording for intro to imagery tools: [https://github.com/OSGeo/grass/pull/4536 Add intro text to imageryintro.html #4536]
* List of GRASS GIS profiles on different websites is now in an internal PSC document.
* Documentation of all the internal infrastructure, especially that of grass.osgeo.org server, is now in an internal PSC document.
* We painstakingly identified and described all maintenance procedures performed by Markus Neteler in OSGeo SAC capacity for GRASS GIS and as a contributor to GRASS GIS for better work distribution.
* Most of the work on the documentation was done through a contract with Markus Neteler with additional help from Martin Landa for the transition to Markdown.

=== Mentoring Activities ===
Mentors were actively working with 3 mentees.

=== Event Planning and Organizing ===

[[File:Raleigh_2016_11_05.jpg|500px|thumb|right|alt=Rooms, tables and large open space|Smaller space utilized in the past for a local GRASS GIS meetup in Hunt library at NC State University campus (photos are from a [[GRASS GIS Raleigh meetups 2016|2016 meetup]])]]

We are planning and organizing GRASS GIS Developer Summit in Raleigh, NC, USA at North Carolina State University.

* High-demand spaces reserved at NCSU (some since May 2024, other since September 2024).
* A [https://discourse.osgeo.org/t/grass-dev-save-the-date-grass-developer-summit-raleigh-2025/85540 save-the-date post for grass-dev], interest form, and first round of additional invites. (Date established earlier in spring 2024 by NSF POSE team after a survey of PSC members and Core Development Team members.)
* We addressed participant's visa needs based on the responses to the interest form.
* We formed the initial Organizing Committee formed and rough event agenda created.
* Page created: [[GRASS Developer Summit Raleigh 2025]].

== Y2 2nd quarter report (12/24 - 02/25) ==

=== Presentations, Workshops, Event Planning ===

[[File:GRASS GIS booth AGU24.jpg|500px|thumb|right|alt=GRASS GIS booth at AGU24|GRASS GIS booth at AGU24, Washington, DC]]

AGU24 Annual Meeting, Washington, DC, USA:
* GRASS GIS booth in the Exhibit Hall with a banner, new flyers, and a Tangible Landscape setup to demonstrate some of the capabilities of GRASS GIS (Monday afternoon - Thursday morning)
* GRASS GIS for Advanced Earth Systems Analysis and Modeling (eLightning) by Vaclav Petras
* Perspectives from an Open Source Geospatial Modeling Platform Maintainer (poster) by Anna Petrasova
* GRASS GIS Is FAIR: Its Evolution Towards Open Science (poster) by Huidae Cho
* GRASS GIS as a Platform for Dissemination of Reusable Geocomputational Research (poster) by Vaclav Petras

Beyond the GIS Map: Open Source Tools for Geospatial Research, Workshop at the Institute for Social Science Research Arizona State University. 11 December 2024
* Michael Barton and Eunice Villaseñor Iribe, instructors
* Topics
** Introduction to GRASS
** Modeling Terrain in GRASS
** Modeling Movement in GRASS
** Remote Sensing With GRASS

Physically-based hydrologic modeling using GRASS GIS r.topmodel, Workshop at New Mexico State University. January 31, 2025, 1pm-5pm.
* Instructor: Huidae Cho
* Assistant: Nelson Kandel
* Participants: 17
* Topics
** Introduction to GRASS
** Hydrologic Modeling Using GRASS
** Model Calibration and Validation

=== Code Quality and Security ===

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShubhamDesai+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ ShubhamDesai], [https://github.com/OSGeo/grass/pulls?q=author%3Aarohanajit+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ Arohan Ajit]

=== Tests ===

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShreshth-Malik+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ Shreshth-Malik], [https://github.com/OSGeo/grass/pulls?q=author%3Ajayneel-shah18+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ jayneel-shah18]

=== Documentation and Tutorials ===
We finalized and prepared for launch Quarto-based tutorial website editable through GitHub. OSGeo provided a new domain [https://grass-tutorials.osgeo.org/ grass-tutorials.osgeo.org]. Initial set of tutorials were created by Veronica Andreo when she was part of the NSF POSE team (some tutorials will be finalized and released later). Anna Petrasova did the reviews, curation, posts for external tutorials, and transition from list of tutorials at the main website.

We did a major push to create Markdown files in the source code and enable the compilation of documentation for mkdocs. We also configured the mkdocs and revised the Markdown syntax in the files.

=== Communication and outreach ===

Renewed [https://www.youtube.com/@grass-gis Youtube channel @grass-gis] by adding playlists, organizing videos, and updating branding.

=== Governance ===
Submitted application for GRASS GIS to join NumFocus.

=== Event Planning and Organizing ===

* Created draft of schedule, agenda, and budget.
* Identified participants eligible for travel support.
** While the meeting is open to anyone, the NSF-funded travel support is based on priorities set in the NSF POSE project for the Developer Summit.
** Specifically, we are inviting individuals identified based on the following criteria (in this order; moving to the next group if there is still available places):
*** Top 20 contributors to OSGeo/grass in the last two years (2023-2024), but not a bot or NSF POSE personnel (contributing only within NSF POSE). (After exclusions, this is less than 10 people.)
*** PSC member before or after 2024 elections, but not NSF POSE personnel at the time of the meeting. (With PSC members currently contributing code as well, this is only a couple of people after exclusions.)
*** Active participant in one of the mentoring programs. (Participant demonstrated the activity by attending meetings, reporting progress, or submitting code for feedback or review.)
*** Contributors to connections and interfaces prioritized in or during the NSF POSE project:
**** R packages (2 slots for active contributors or maintainers determined by previously established contacts in the given community through their activity on a relevant code base.)
**** GRASS GIS code in QGIS (2 slots for active contributors or maintainers determined by previously established contacts in the given community through their activity on a relevant code base.)
*** Contributors in "write" teams for OSGeo/grass, OSGeo/grass-addons, OSGeo/grass-website, and OSGeo/grass-tutorials repositories. (Almost all fall into one of the above groups.)
*** Contributors to closely related projects, specifically actinia, the GRASS GDAL driver, and the GRASS GeoServer datastore.
* Sent individual invites to participants eligible for travel support. (ongoing)

== Y2 3rd quarter report (03/25 - 05/25) ==

=== Governance ===
* GRASS accepted NumFOCUS (more steps to make it official)

=== Presentations, Workshops, Event Planning ===
* Beyond the GIS Map: Open Source Tools for Geospatial Research, Workshop at the Institute for Social Science Research Arizona State University. 25 March 2025
** Michael Barton and Eunice Villaseñor Iribe, instructors
** Topics: Introduction, Modeling Terrain, Modeling Movement, Remote Sensing with GRASS
* IALE-NA: [https://github.com/ncsu-geoforall-lab/iale-2025-workshop-tl Building Geospatial Models in GRASS: From Python Workflows to Tangible Landscape], April 15th, hosted by the Center for Geospatial Analytics
** Anna Petrasova and Caitlin Haedrich
** 20 participants

* [[GRASS_Developer_Summit_Raleigh_2025]] (see the page for details)

== Y2 4th quarter report (06/25 - 08/25) ==

=== Governance ===
* GRASS onboarding with NumFOCUS

=== Presentations, Workshops, Event Planning ===
* Geomorphometry workshop - Corey White and Caitlin Haedrich

=== Documentation and Tutorials ===
* contributed tutorials
** fasterRaster by Adam Smith
** Intro to RS by Michael Barton
** Time series tutorials by Veronica Andreo

=== Mentoring ===
* new addons:
** r.earthworks by Brendan Harmon
** r.gravity.correction by David Farris
** r.curvenumber by Abdullah Azzam
** improvements to r.hydro.flatten by Doug Newcomb
* Xarray backend for GRASS by Laurent Courty
* GSoC: Adding JSON to tool output

== Roadmap ==
;Mentoring program (fall 2023 - summer 2025)
:Free developer-oriented mentoring program to support researchers and software developers to integrate GRASS GIS into their workflows and contribute to GRASS GIS.

; Streamline contributor onboarding (spring 2024 - fall 2024)
: Includes updating and creating guidelines for code and non-code contributions.

; Streamline user onboarding (spring 2024 - fall 2024)
: Includes modernizing tool documentation, developing tutorials.
: Creating sample datasets for localized tutorials.
: Developing online training materials for big data processing.

; Training sessions (fall 2023 - summer 2025)
: Local training sessions (at universities and conferences) introducing GRASS GIS to students and researchers.
: Training program for big data processing delivered online.

; Engaging industry partners and user (January 2024 - August 2025)
: Identify and engage industry partners to gather feedback and to start industry partnership program.

; Conferences
: Presence (talks, workshops, networking) at FOSS4GNA 2023, FOSS4G Asia 2023, AGU 2023, CSDMD 2024, FOSS4G Europe 2024, FOSS4G 2024, AGU 2024

; Community sprints
: Virtual or in-person participation in OSGeo community sprints, GRASS GIS community sprints

; Software distribution (January 2024 - May 2025)
: Transition to CMake build system
: Develop conda package

;Simplify maintenance of GRASS integrations with QGIS and R (2024-2025)
: Virtual meetings with QGIS and R developers and GRASS GIS developers (spring 2024).
: Identify and implement improvements to the integration.

;Improve code quality, security, and quality assurance
: Code quality (Flake8, Pylint, Cppcheck), first half of 2024.
: Security (CodeQL), second half of 2024.
: Quality assurance (better pytest integration), second half of 2024.

; In-person developer summit (May 19 - May 24, 2025)
: Hosted by NC State University, Raleigh, NC, USA.
: Identify additional challenges for adoption of GRASS GIS as geoprocessing engine.
: Long-term planning beyond the POSE project.

== Acknowledgements ==

The funding is provided by the U.S. National Science Foundation, award 2303651.
[[File:NSF Official logo.png|frameless|left]]

[[Category: Community]]
[[Category: Conferences‏‎]]
[[Category: 2023]]
[[Category: 2024]]
[[Category: 2025]]

NSF POSE Project 2023-2025 Timeline

2025-06-05T20:03:37Z

Annakrat: /* Y2 4th quarter report (06/25 - 08/25) */

[[File:NSF_grant_announcement.png|500px|right|none]]

To inform GRASS community about the work done as part of the award [https://www.nsf.gov/awardsearch/showAward?AWD_ID=2303651 2303651] from the U.S. National Science Foundation (NSF) to enhance GRASS ecosystem, the following report summarizes the progress and outcomes in quarterly reports and presents the roadmap for the project.

The two main goals of the project are: 1) to facilitate the adoption of GRASS GIS as a key geoprocessing engine by a growing number of researchers and geospatial practitioners in academia, governments, and industry; and 2) to expand and diversify the developer community, especially through supporting next-generation scientists to gain expertise to maintain and innovate GRASS software.

Principal investigators and senior personnel:

* Helena Mitasova, North Carolina State University (Principal Investigator)
* Vaclav Petras, North Carolina State University (Co-Principal Investigator)
* Anna Petrasova, North Carolina State University (Co-Principal Investigator)
* C Michael Barton, Arizona State University (Co-Principal Investigator)
* Huidae Cho, New Mexico State University (Co-Principal Investigator)
* Giuseppe Amatulli, Yale (Senior Personnel)

Other personnel who is joining for the execution of the grant is listed below when relevant.

== Y1 1st quarter report (09/23 - 11/23) ==
=== Project Announcements and Communication ===
* Announcement on [https://grass.osgeo.org/news/2023_09_06_nsf_grant_awarded/ GRASS website].
* Info session to explain the POSE Project ([https://lists.osgeo.org/pipermail/grass-user/2023-September/083423.html Announcement on GRASS user mailing list], 2 sessions for different time zones).
* Collected statistics from GitHub, X and others and set up automated collection for GitHub.

=== Conference Presentations ===
* [https://petrasovaa.github.io/FUTURES-CONUS-talk/foss4gNA2023.html#/ Parallelization Tips for Geoprocessing with GRASS GIS] by Anna Petrasova at FOSS4GNA, October 2023.
* [https://wenzeslaus.github.io/grass-gis-talks/foss4gna2023.html#/ GRASS GIS: Not What You Think] by Vaclav Petras at FOSS4GNA, October 2023.
* [https://docs.google.com/presentation/d/1D-Fh1cLSPINyeXdVaxlakrE9IjB8kK5lIw3D12yX1bk Computational Notebooks for Reproducible Geospatial Computation in Research and Education] by Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/HuidaeCho/grass-gis-talk-foss4g-asia-2023 State of GRASS GIS: 40 Years Strong and Counting] by Huidae Cho at FOSS4G Asia, November 2023.

=== Training and Workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-foss4gna-2023 Unlock the power of GRASS GIS] by Anna Petrasova and Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/develop-tools-with-grass-foss4gna-2023 Develop Geospatial Workflows and Custom Tools with GRASS GIS] by Vaclav Petras and Corey White at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/grass-workshop-gis-week-2023 Big Data Computing with GRASS GIS] by Anna Petrasova and Vaclav Petras at NC State GIS week, November 2023.
* [https://github.com/ncsu-geoforall-lab/grass-gis-on-hpc-henry2/blob/8564c72e9b8929c9ef4d25ada1ef36b569991221/docs/tutorial.md GIS Week Workshop: High Performance Computing for Geospatial Analysis (GRASS GIS part)] by Vaclav Petras (main lecture lead by Andrew Petersen from NCSU OIT) at NC State GIS week, November 2023.
* [https://spatial-ecology.net/docs/build/html/COURSESAROUNDTHEWORLD/course_geocomp_ml_04-05_2024.html Geocomputation and Machine Learning for Environmental Applications] training course [https://spatial-ecology.net/course-geocomputation-machine-learning-for-environmental-applications-intermediate-level-2024/ announced]. GRASS GIS part led by Giuseppe Amatulli is free of charge thanks to the support by NSF.

=== Community Sprint Participation ===
Anna Petrasova and Vaclav Petras remotely participated in [https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2023 OSGeo 2023 code sprint] doing PR reviews and maintenance of GRASS GIS code, documentation, and website.

=== Mentoring Program ===
* Started a development-oriented mentoring program [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ announced] with details available on a [https://grasswiki.osgeo.org/wiki/Mentoring_Program wiki page].
* Program now has 4 participants (from 12 responses) supported by email and video calls.
* Program already resulted in improvements to GRASS GIS core and addons:
** merged PR: [https://github.com/OSGeo/grass/pull/3206 grass.script: ensure memmap content is flushed before writing to a raster]
** radar addon toolset PR: [https://github.com/OSGeo/grass-addons/pull/949 Add i.saocom and i.sar toolsets]
Mentoring Program is a new effort started and so-far performed only by the POSE team.

=== Student Grants Program ===
Student grants [https://grass.osgeo.org/news/2023_11_09_student_grants_announced/ announced] with topics at a [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants wiki page]. Student Grants Program is an existing effort which the POSE team participates in.

=== Working Groups ===

Four [https://grasswiki.osgeo.org/wiki/Working_Groups working groups] created (scope, wiki page, coordinator, and a list of people for each).

=== Citations ===

* GRASS GIS Google Scholar [https://scholar.google.com/citations?user=gJ0ZB0cAAAAJ account] updated with more complete records.
* A [https://forms.gle/cDEvMJu7d6nvxLKn9 form] was created to collect new and missing records.
* Profile link added to GRASS website [https://grass.osgeo.org/contribute/ Contribute] and [https://grass.osgeo.org/about/citation/ Citation] page.

== Y1 2nd quarter report (12/23 - 02/24) ==
=== NSF I-Corps program ===
Corey White, Vaclav Petras, and Anna Petrasova participated in a 4-week long intensive mandatory training that draws on the methods, customer discovery, and curriculum of the [https://new.nsf.gov/funding/initiatives/i-corps NSF Innovation Corps] and applies them to open-source projects.

The program included conducting 70+ 30-minute interviews with both GRASS users and non-users to better shape the future path of GRASS GIS and the POSE project. So far, the interviews focused on educators, companies, researchers, influencers and it focused more on non-users than users.

Next steps, include processing the collected qualitative data, developing possible future directions for sustainability of the project, discussing these with the Project Steering Committee, the core team of developers, and the broader community.

=== Mentoring Program ===
The development oriented [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ mentoring program] welcomed 5 new participants from various institutions including universities, USGS, US Army Corps of Engineers, and local municipalities. The discussed topics covered developing workflows for topography and network analysis, environmental modeling, and geophysics. Participants were supported by email and video calls.

=== Conference Presentations ===
* [https://agu.confex.com/agu/fm23/meetingapp.cgi/Paper/1342418 Modeling vegetated stream buffer impacts on water depth and discharge at the watershed scale with GRASS GIS and Jupyter Notebooks] by Caitlin Haedrich at AGU, December 2023.
* [https://agu.confex.com/agu/fm23/meetingapp.cgi/Paper/1420596 OpenPlains: A Web-Based Platform to Democratize Geospatial Participatory Modeling on the Cloud] by Corey White at AGU, December 2023.

=== Presentations and Workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-vanderbilt-2024 Intro to GRASS GIS] by Vaclav Petras and Anna Petrasova was remotely delivered to geographers at Vanderbilt University in February 2024. The workshop was developed in Jupyter Lab and run using [https://wholetale.org WholeTale] online platform.
* [https://github.com/tomorrownow/intro-to-geoprocessing-workshop Introduction to GRASS GIS Geospatial Processing] by Corey White at [https://smathhacks.ncssm.edu/ SMathHacks hackathon], March 2nd (supported also by Veronica Andreo and Vaclav Petras). SMathHacks is the annual 36-hour hackathon hosted by the NC School of Science and Math, open to all North Carolina students. Students collaborate to build innovative software projects, explore new technologies, and have fun along the way. The workshop was delivered in person with students using [https://colab.research.google.com/ Google Colab].

=== Student Grant Program ===
Linda Karlovska participates in the [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants Student Grant program] with her project [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation Easy command history navigation through the History browser panel] mentored by Anna Petrasova (POSE team) and Martin Landa (FCE CTU). Student Grants Program is an existing effort which the POSE team participates in by mentoring.

=== Code Security ===
Vaclav Petras mentors four students who create code security improvements in their NCSU class ''CSC 472: Cybersecurity Practicum''. So far, the students created two PRs which were successfully merged:
* [https://github.com/OSGeo/grass/pull/3444 grass.script: Change insecure mktemp to NamedTemporaryFile #3444]
* [https://github.com/OSGeo/grass/pull/3451 utils: fixed shell vulnerability in mkrest.py #3451]

Two other PRs are open and more work is underway to do first steps for new approach to a more secure code.

=== Localized Basic Datasets ===
* NCSU and ASU teams worked on localized versions of GRASS basic data set following the [https://grass.osgeo.org/sampledata/north_carolina/nc_basic_spm_grass7.zip North Carolina basic data set example], preparing Flagstaff, Arizona and Nepal draft version with basic layers

== Y1 3rd quarter report (03/24 - 05/24) ==

=== Mentoring Activities ===
The mentoring program form received 2 new responses and mentors were actively working with 3 mentees.
It resulted in fixes in [https://github.com/OSGeo/grass-addons/pull/1042 v.transects] and [https://github.com/OSGeo/grass-addons/pull/1077 r.accumulate].

Linda Kladivova finished her project developing [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation History browser] in the GRASS GUI as part of the GRASS Student Grant Program. Mentor's time was covered by POSE.

GRASS GIS has [https://grass.osgeo.org/news/2024_05_27_gsoc_2024_students/ 3 students this year for Google Summer of Code]. Time spent managing GSoC for GRASS GIS was covered by POSE.

The topics covered by GSoC projects are:
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_EODAG_Support Add EODAG support to GRASS GIS]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Improve_user_experience_in_Jupyter_Notebooks Improve GRASS user experience in Jupyter Notebook]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Add_JSON_output Add JSON output to different GRASS tools in C]

=== Presentations, Workshops, Event Planning ===
* [https://github.com/ncsu-geoforall-lab/tngic-2024 GRASS 101: From GUI Clicks to Writing Scripts (TNGIC 2024)] by Veronica Andreo and Caitlin Haedrich
* [https://github.com/ncsu-geoforall-lab/csdms-grass-2024 Coastal evolution analysis and inundation modeling with GRASS GIS (CSDMS Workshop 2024)] by Caitlin Haedrich and Pratikshya Regmi, see also [https://cnr.ncsu.edu/geospatial/news/2024/06/03/students-teach-grass-gis-for-coastal-hazard-analysis/ blog post with images]

* Organization of [[GRASS Community Meeting Prague 2024]] and budget planning by Vaclav Petras

=== CMake transition ===
Ongoing work on [https://github.com/OSGeo/grass/pull/3621 CMake compilation] was partially covered by POSE.

=== Code Quality and Security ===

Code quality improvements in Python code:
* [https://github.com/OSGeo/grass/pull/3541 PR addressing Flake8 E501] (long lines in 158 files not fixable by automated tools)
* [https://github.com/OSGeo/grass/pull/3535 PR addressing Flake8 E401] (unused imports)

Vaclav Petras mentored a team of four students who create code security improvements in their NCSU class ''CSC 472: Cybersecurity Practicum''. The team created 12 PRs which were successfully merged, 7 additional experimental PRs (not merged) and 2 PRs which are still open at this time. Specifically, the team achieved the following:

* With the involvement and help from the other contributors, the team introduced Bandit and Coverity Scan as additional code scanning tools for Python and C, respectively.
* The team analyzed issues reported CodeQL, Bandit, and Coverity Scan and reported on relevance of different issues to the project (report privately shared with the GRASS Development Team).
* Vulnerability Triage Guide (also privately shared with the GRASS Development Team).
* The team also developed a [https://github.com/OSGeo/grass/security/policy security policy] for the project.
* The vulnerability reporting and security advisories were enabled based on the team recommendations.
* The team fixed several specific security issues in the code:
** [https://github.com/OSGeo/grass/pull/3469 packaging: Use subprocess instead of os.popen for change log creation #3469] (merged)
** [https://github.com/OSGeo/grass/pull/3549 lib raster: fixed security vulnerabilities and weaknesses #3549] (merged)
** [https://github.com/OSGeo/grass/pull/3451 utils: fixed shell vulnerability in mkrest.py #3451] (merged)
** [https://github.com/OSGeo/grass/pull/3444 grass.script: Change insecure mktemp to NamedTemporaryFile #3444] (merged)
** [https://github.com/OSGeo/grass/pull/3551 lib/psdriver: Fix issues with wrong type of arguments to printf #3551] (PR open)
** [https://github.com/OSGeo/grass/pull/3452 g.region/r.to.rast3elev: fixed scanf error to recognize EOF as a possible return value #3452] (PR open)

=== Documentation ===
* Documentation and Education Working Group met and planned the development of new tutorials. Veronica Andreo met other GRASS developers and contributors to coordinate further tutorials development.
* Development of new [https://github.com/ncsu-geoforall-lab/tutorials tutorials] in progress, topics include:
** Getting started with GRASS GIS
** GRASS GIS in Google Colab
** GRASS GIS and Python
** GRASS GIS and R
** GRASS R and Python comparison
** Making plots in GRASS GIS
* New [https://github.com/OSGeo/grass/blob/main/doc/development/style_guide.md GRASS Programming Style Guide]
* [https://github.com/petrasovaa/cookiecutter-grass-addon New addon template powered by Cookiecutter]
* Analysis of options names and functionality in plotting tools:
** [https://github.com/OSGeo/grass-addons/issues/1071 Addons for plotting: Standardize parameters and flags]

=== Communication and outreach ===

* Creation of 4 news post in the [https://grass.osgeo.org/news/ GRASS website]
* Social media:
** [https://twitter.com/GRASSGIS Twitter]: 9 new posts/threads
** [https://fosstodon.org/@grassgis Fosstodon]: 9 new posts/threads

=== Other sustainability activities ===
* [https://github.com/OSGeo/grass/blob/main/CODE_OF_CONDUCT.md Code of Conduct added to the main repository]
* [https://github.com/OSGeo/grass/blob/main/.github/ISSUE_TEMPLATE/bug_report.md revised Issue template]
* New [https://github.com/OSGeo/grass/pull/3673 RFC for a Release Policy]
* Revised [https://github.com/OSGeo/grass/pull/2815 RFC for Release Procedure]
* WIP: GRASS GIS Roadmap
* [https://github.com/OSGeo/grass-website/issues/414 GRASS website: ongoing restructuring]
* [[PSC]] page moved from trac wiki to media wiki

== Y1 4th quarter report (06/24 - 08/24) ==

=== Mentoring Activities ===
The mentoring program form received 3 new responses and mentors were actively working with 3 mentees.
Results include parallelization of r.texture, r.horizon, improved grass.benchmarking library and a new tutorial on lidar data.

GSoC successfully completed their projects:
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_EODAG_Support Add EODAG support to GRASS GIS]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Improve_user_experience_in_Jupyter_Notebooks Improve GRASS user experience in Jupyter Notebook]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Add_JSON_output Add JSON output to different GRASS tools in C]

Time spent by mentoring was covered by NSF.

=== Presentations, Workshops, Event Planning ===

* [https://veroandreo.github.io/grass_foss4geu_2024/ Let's combine GRASS, Python and R: Satellite time series data for species distribution modeling]. Workshop by Veronica Andreo. FOSS4G Europe 2024, Tartu.
* [https://veroandreo.github.io/grass-gis-talks/foss4gEU2024.html#/ Status of GRASS GIS project]. Talk by Veronica Andreo. FOSS4G Europe 2024, Tartu.
* [https://veroandreo.github.io/grass-gis-talks/useR2024.html#/ Boost Spatial Data Science Workflows with GRASS GIS and R]. Talk by Veronica Andreo. useR Conference 2024, Salzburg.
* [https://ncsu-geoforall-lab.github.io/usdoi-webinar/notebooks/grass_jupyter.html Geoprocessing with GRASS GIS and Jupyter Notebooks]. Webinar by Corey White. U.S. DOI, August 2024, NCSU.
* [[GRASS Community Meeting Prague 2024]]

* [https://spatial-ecology.net/docs/build/html/COURSESAROUNDTHEWORLD/course_GEO-OPEN-HACK-2024_06_2024.html GEO-OPEN-HACK-2024: Big Geospatial Data Hackathon with Open Infrastructure and Tools] training course delivered ([https://iiasa.ac.at/events/jun-2024/geo-open-hack-2024-big-geospatial-data-hackathon-with-open-infrastructure-and-tools announcement]). The GRASS material has been developed as part of the NSF grant.

* Planning GRASS Dev summit 2025 at NCSU

* Planning AGU (4 abstract submitted), AGU booth for GRASS GIS reserved and payed

* Submitted workshop, talk and keynote to FOSS4G 2024 - Brazil.

=== CMake transition ===
Ongoing work on [https://github.com/OSGeo/grass/pull/3621 CMake compilation] was partially covered by POSE.

=== Code Quality and Security ===

* Code quality improvements in Python code:
** [https://github.com/OSGeo/grass/pull/3763 Flake8 W605 Invalid escape sequence #3763]
** [https://github.com/OSGeo/grass/pull/3926 Flake8 E741 Do not use variables named 'I', 'O', or 'l' in wxGUI code #3926]
** [https://github.com/OSGeo/grass/pull/3928 Flake8 E741 for the rest of code base #3928]
** [https://github.com/OSGeo/grass/pull/4200 grass.temporal: Flake8 F841 Local variable assigned to but never used #4200]
** [https://github.com/OSGeo/grass/pull/4113 grass.pygrass: Remove unused arg in ctypes.CFUNCTYPE #4113]
** [https://github.com/OSGeo/grass/pull/4206 t.rast.to.vect: Fix passing column parameter to r.to.vect, fix flake8 F841 #4206]

* Code quality and security improvements in C and C++ code are in 36 PRs with fixes for more than 25 tools, specifically in:
** raster: r.path, r.out.mpeg, r.out.png, r.in.xyz, r.terraflow, r.statistics, r.spreadpath, r.sim.water, r.sim.erosion, r.object.geometry, r.coin
** imagery: i.atcorr, i.aster.toar, i.ortho.photo, i.landsat.acca, i.segment, i.smap
** display: d.linegraph, d.legend.vect, d.histogram, d.labels
** raster 3D: r3.in.v5d, r3.info, r3.mapcalc
** other: lib/gis, lib/vector/diglib, g.findfile, g.setproj, ps.map, lib/cdhc

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShubhamDesai+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ ShubhamDesai], [https://github.com/OSGeo/grass/pulls?q=author%3Amshukuno+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ Makiko Shukunobe], [https://github.com/OSGeo/grass/pulls?q=author%3Aymdatta+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ ymdatta]

Several reviewers, not supported by the NSF POSE project, played crucial role not only in reviewing, but also in determining the right fixes.

Fixed issues were reported by Flake8, Coverity Scan, and Cppcheck.

=== Tests ===

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShreshth-Malik+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ Shreshth-Malik]

=== Documentation ===

* Veronica Andreo met some GRASS developers and contributors to follow up on tutorials development.
* 7 new [https://github.com/ncsu-geoforall-lab/tutorials tutorials] on time series:
** Management and visualization
** Aggregation
** Algebra
** Accumulation
** Gap filling
** Querying raster time series with vectors
** Subset, import and export
* Tutorial on how to set up Jupyter and GRASS in Windows
* New [https://github.com/OSGeo/grass-tutorials repository] under OSGeo organization to host the upcoming quarto based website for GRASS tutorials
* PR template created - [https://github.com/OSGeo/grass/community GitHub Community Standards] all checked complete

=== Communication and outreach ===

* Creation of 4 news posts in the [https://grass.osgeo.org/news/ GRASS website]
* Social media:
** [https://twitter.com/GRASSGIS Twitter]: 25 new posts
** [https://fosstodon.org/@grassgis Fosstodon]: 25 new posts
* New GRASS GIS LinkedIn page at: [https://www.linkedin.com/company/grass-gis/ https://www.linkedin.com/company/grass-gis/]
* Requested transition of [https://discourse.osgeo.org/t/osgeo-3255-migrate-grass-dev-mailing-list-to-discourse/49796 grass-dev mailing list to discourse.osgeo.org]
* Set up GRASS GIS swag shop on Redbubble

=== Governance ===
* [https://grass.osgeo.org/about/roadmap/ Roadmap] and [https://grass.osgeo.org/about/governance/ Governance] pages added to the website
* PSC elections:
** Documented criteria to define people entitled to vote
** Documented procedure to compile the list of voters
** Elections [https://www.mail-archive.com/grass-user@lists.osgeo.org/msg41102.html announcement] sent out

== Y2 1st quarter report (09/24 - 11/24) ==

=== Presentations and Workshops ===
FOSS4GNA 2024 in St. Louis, Missouri:

* Vaclav Petras. State of GRASS GIS. FOSS4G NA St. Louis, September 9-11, 2024 ([https://wenzeslaus.github.io/grass-gis-talks/foss4gna2024.html slides])
* Huidae Cho. Evolution of GRASS GIS. FOSS4G NA St. Louis, September 9-11, 2024 ([https://htmlpreview.github.io/?https://github.com/HuidaeCho/grass-talks/blob/main/foss4g-na-2024.html slides])
* Huidae Cho. An OpenMP Algorithm for Delineating a Large Number of Watersheds. FOSS4G NA St. Louis, September 9-11, 2024
* Corey T. White. Developing Web-Applications with GRASS GIS. Workshop. FOSS4G NA St. Louis, September 9-11, 2024
* Corey T. White. GRASS GIS as a Geospatial Computational Engine. FOSS4G NA St. Louis, September 9-11, 2024

=== Communication and outreach ===
* Transition of grass-dev mailing list to [https://discourse.osgeo.org/c/grass/developer/61 discourse.osgeo.org] finished.

=== Code Quality and Security ===
* Python code quality issues addressed in more than 70 PRs, reducing the list of per-file ignores by more than 60%.
* Code quality and security improvements in C and C++ code are in more than 80 PRs.
* In total, these changes improve more than 60 tools, specifically:
** raster: r.water.outlet, r.watershed, r.mfilter, r.to.vect, r.in.poly, r.carve, r.thin, r.fill.dir, r.clump, r.in.gridatb, r.out.png, r.in.wms, r.viewshed, r.fillnulls, r.in.srtm, r.in.pdal, r.in.xyz
** vector: v.out.dxf, v.build.polylines, v.external.out, v.net, v.univar, v.in.ascii, v.delaunay, v.hull , v.net.timetable, v.kernel, v.to.db, v.colors, v.rectify, v.reclass, v.generalize, v.transform, v.vol.rst, v.cluster, v.to.3d, v.out.ogr, v.external, v.in.dwg, v.report, v.unpack, v.import
** imagery: i.topo.corr, i.attcorr, i.ortho.photo, i.segment, i.rectify, i.topo.corr, i.panshrapen
** display: d.vect, d.mon, d.frame, d.rast.edit
** other: GUI, grass main executable, g.proj, g.version, db.out.ogr, ps.map, r3.in.v5d, r3.in.v5d, lib/vector/Vlib, lib/ogsf, lib/gis, lib/db, lib/lidar, lib/linkm, grass.temporal, grass.script

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShubhamDesai+is%3Apr+is%3Aclosed+merged%3A2024-09-01..2024-11-30+base%3Amain+sort%3Aupdated-desc+ ShubhamDesai], [https://github.com/OSGeo/grass/pulls?q=author%3Aymdatta+is%3Apr+is%3Aclosed+merged%3A2024-09-01..2024-11-30+base%3Amain+sort%3Aupdated-desc+ ymdatta],
[https://github.com/OSGeo/grass/pulls?q=author%3Aarohanajit+is%3Apr+is%3Aclosed+merged%3A2024-09-01..2024-11-30+base%3Amain+sort%3Aupdated-desc+ Arohan Ajit]

Several reviewers, not supported by the NSF POSE project, played crucial role not only in reviewing, but also in determining the right fixes. The NSF POSE project personnel focused on fixing issues reported by Flake8, Coverity Scan, and Cppcheck, however also Ruff and Pylint are utilized in GRASS GIS thanks to other contributors.

A configure file for Cppcheck is now included in the repository highlighting the level of compliance and aiding contributors in local analysis and subsequent implementation of fixes ([https://github.com/OSGeo/grass/pull/4766 PR #4766]).

Finally, we created a new public GitHub project in the OSGeo GitHub organization for [https://github.com/orgs/OSGeo/projects/11 GRASS GIS Security] to track and communicate progress on the security front with 147 resolved items and 8 in-progress items at the time of writing.

=== Documentation, both Internal and External ===

* To improve indexing of GRASS GIS manual pages, we revised our current sitemap ([https://github.com/OSGeo/grass-website/pull/482 grass-website/pull/482)]), added a updated sitemap to Google Search Console and Bing, fixed robots.txt, and triggered and re-triggered the indexing many times to make Google consume the new content. While before, some searches gave outdated documentation, experimental websites, or unofficial resources only, now the official website and stable documentation is returned as the first search result.
* All older manuals, including version 6.4 and 6.5, are now available (restored) so that search engines can consume them and old links and indices continue to work. They now newly contain the canonical URLs so that search engines understand the structure and don't penalize duplicate content.
* On OSGeo server which hosts GRASS GIS website, we replaced some of the redirects in Apache by local soft links so that URL like grass.osgeo.org/grass-stable stay as is for both humans and machines and don't redirect to specific version (easier to copy-paste from a browser URL bar and easier for search engine to understand what is the page to show).
* We implemented the necessary changes into the cronjobs and did overall updates to enable build of the server-side documentation jobs locally for testing purposes. The most relevant PRs are:
** [https://github.com/OSGeo/grass-addons/pull/1241 Inject canonical URLs into older manual pages (SEO) #1241]
** [https://github.com/OSGeo/grass-addons/pull/1173 Fix red new version box injection and script documentation #1173]
** [https://github.com/OSGeo/grass-addons/pull/1215 Expand script to run stand-alone #1215]
* We advanced the [https://github.com/orgs/OSGeo/projects/9 GRASS Markdown Documentation project].
* New and better wording for intro to imagery tools: [https://github.com/OSGeo/grass/pull/4536 Add intro text to imageryintro.html #4536]
* List of GRASS GIS profiles on different websites is now in an internal PSC document.
* Documentation of all the internal infrastructure, especially that of grass.osgeo.org server, is now in an internal PSC document.
* We painstakingly identified and described all maintenance procedures performed by Markus Neteler in OSGeo SAC capacity for GRASS GIS and as a contributor to GRASS GIS for better work distribution.
* Most of the work on the documentation was done through a contract with Markus Neteler with additional help from Martin Landa for the transition to Markdown.

=== Mentoring Activities ===
Mentors were actively working with 3 mentees.

=== Event Planning and Organizing ===

[[File:Raleigh_2016_11_05.jpg|500px|thumb|right|alt=Rooms, tables and large open space|Smaller space utilized in the past for a local GRASS GIS meetup in Hunt library at NC State University campus (photos are from a [[GRASS GIS Raleigh meetups 2016|2016 meetup]])]]

We are planning and organizing GRASS GIS Developer Summit in Raleigh, NC, USA at North Carolina State University.

* High-demand spaces reserved at NCSU (some since May 2024, other since September 2024).
* A [https://discourse.osgeo.org/t/grass-dev-save-the-date-grass-developer-summit-raleigh-2025/85540 save-the-date post for grass-dev], interest form, and first round of additional invites. (Date established earlier in spring 2024 by NSF POSE team after a survey of PSC members and Core Development Team members.)
* We addressed participant's visa needs based on the responses to the interest form.
* We formed the initial Organizing Committee formed and rough event agenda created.
* Page created: [[GRASS Developer Summit Raleigh 2025]].

== Y2 2nd quarter report (12/24 - 02/25) ==

=== Presentations, Workshops, Event Planning ===

[[File:GRASS GIS booth AGU24.jpg|500px|thumb|right|alt=GRASS GIS booth at AGU24|GRASS GIS booth at AGU24, Washington, DC]]

AGU24 Annual Meeting, Washington, DC, USA:
* GRASS GIS booth in the Exhibit Hall with a banner, new flyers, and a Tangible Landscape setup to demonstrate some of the capabilities of GRASS GIS (Monday afternoon - Thursday morning)
* GRASS GIS for Advanced Earth Systems Analysis and Modeling (eLightning) by Vaclav Petras
* Perspectives from an Open Source Geospatial Modeling Platform Maintainer (poster) by Anna Petrasova
* GRASS GIS Is FAIR: Its Evolution Towards Open Science (poster) by Huidae Cho
* GRASS GIS as a Platform for Dissemination of Reusable Geocomputational Research (poster) by Vaclav Petras

Beyond the GIS Map: Open Source Tools for Geospatial Research, Workshop at the Institute for Social Science Research Arizona State University. 11 December 2024
* Michael Barton and Eunice Villaseñor Iribe, instructors
* Topics
** Introduction to GRASS
** Modeling Terrain in GRASS
** Modeling Movement in GRASS
** Remote Sensing With GRASS

Physically-based hydrologic modeling using GRASS GIS r.topmodel, Workshop at New Mexico State University. January 31, 2025, 1pm-5pm.
* Instructor: Huidae Cho
* Assistant: Nelson Kandel
* Participants: 17
* Topics
** Introduction to GRASS
** Hydrologic Modeling Using GRASS
** Model Calibration and Validation

=== Code Quality and Security ===

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShubhamDesai+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ ShubhamDesai], [https://github.com/OSGeo/grass/pulls?q=author%3Aarohanajit+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ Arohan Ajit]

=== Tests ===

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShreshth-Malik+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ Shreshth-Malik], [https://github.com/OSGeo/grass/pulls?q=author%3Ajayneel-shah18+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ jayneel-shah18]

=== Documentation and Tutorials ===
We finalized and prepared for launch Quarto-based tutorial website editable through GitHub. OSGeo provided a new domain [https://grass-tutorials.osgeo.org/ grass-tutorials.osgeo.org]. Initial set of tutorials were created by Veronica Andreo when she was part of the NSF POSE team (some tutorials will be finalized and released later). Anna Petrasova did the reviews, curation, posts for external tutorials, and transition from list of tutorials at the main website.

We did a major push to create Markdown files in the source code and enable the compilation of documentation for mkdocs. We also configured the mkdocs and revised the Markdown syntax in the files.

=== Communication and outreach ===

Renewed [https://www.youtube.com/@grass-gis Youtube channel @grass-gis] by adding playlists, organizing videos, and updating branding.

=== Governance ===
Submitted application for GRASS GIS to join NumFocus.

=== Event Planning and Organizing ===

* Created draft of schedule, agenda, and budget.
* Identified participants eligible for travel support.
** While the meeting is open to anyone, the NSF-funded travel support is based on priorities set in the NSF POSE project for the Developer Summit.
** Specifically, we are inviting individuals identified based on the following criteria (in this order; moving to the next group if there is still available places):
*** Top 20 contributors to OSGeo/grass in the last two years (2023-2024), but not a bot or NSF POSE personnel (contributing only within NSF POSE). (After exclusions, this is less than 10 people.)
*** PSC member before or after 2024 elections, but not NSF POSE personnel at the time of the meeting. (With PSC members currently contributing code as well, this is only a couple of people after exclusions.)
*** Active participant in one of the mentoring programs. (Participant demonstrated the activity by attending meetings, reporting progress, or submitting code for feedback or review.)
*** Contributors to connections and interfaces prioritized in or during the NSF POSE project:
**** R packages (2 slots for active contributors or maintainers determined by previously established contacts in the given community through their activity on a relevant code base.)
**** GRASS GIS code in QGIS (2 slots for active contributors or maintainers determined by previously established contacts in the given community through their activity on a relevant code base.)
*** Contributors in "write" teams for OSGeo/grass, OSGeo/grass-addons, OSGeo/grass-website, and OSGeo/grass-tutorials repositories. (Almost all fall into one of the above groups.)
*** Contributors to closely related projects, specifically actinia, the GRASS GDAL driver, and the GRASS GeoServer datastore.
* Sent individual invites to participants eligible for travel support. (ongoing)

== Y2 3rd quarter report (03/25 - 05/25) ==

=== Governance ===
* GRASS accepted NumFOCUS (more steps to make it official)

=== Presentations, Workshops, Event Planning ===
* Beyond the GIS Map: Open Source Tools for Geospatial Research, Workshop at the Institute for Social Science Research Arizona State University. 25 March 2025
** Michael Barton and Eunice Villaseñor Iribe, instructors
** Topics: Introduction, Modeling Terrain, Modeling Movement, Remote Sensing with GRASS
* IALE-NA: [https://github.com/ncsu-geoforall-lab/iale-2025-workshop-tl Building Geospatial Models in GRASS: From Python Workflows to Tangible Landscape], April 15th, hosted by the Center for Geospatial Analytics
** Anna Petrasova and Caitlin Haedrich
** 20 participants

* [[GRASS_Developer_Summit_Raleigh_2025]] (see the page for details)

== Y2 4th quarter report (06/25 - 08/25) ==

=== Governance ===
* GRASS onboarding with NumFOCUS

=== Presentations, Workshops, Event Planning ===
* Geomorphometry workshop - Corey White and Caitlin Haedrich

=== Documentation and Tutorials ===
* contributed tutorials
** fasterRaster by Adam Smith
** Intro to RS by Michael Barton
** Time series tutorials by Veronica Andreo

=== Mentoring ===
* new addons:
** r.earthworks by Brendan Harmon
** r.gravity.correction by David Farris
** r.curvenumber by Abdullah Azzam
** improvements to r.hydro.flatten by Doug Newcomb
* Xarray backend for GRASS by Laurent Courty

== Roadmap ==
;Mentoring program (fall 2023 - summer 2025)
:Free developer-oriented mentoring program to support researchers and software developers to integrate GRASS GIS into their workflows and contribute to GRASS GIS.

; Streamline contributor onboarding (spring 2024 - fall 2024)
: Includes updating and creating guidelines for code and non-code contributions.

; Streamline user onboarding (spring 2024 - fall 2024)
: Includes modernizing tool documentation, developing tutorials.
: Creating sample datasets for localized tutorials.
: Developing online training materials for big data processing.

; Training sessions (fall 2023 - summer 2025)
: Local training sessions (at universities and conferences) introducing GRASS GIS to students and researchers.
: Training program for big data processing delivered online.

; Engaging industry partners and user (January 2024 - August 2025)
: Identify and engage industry partners to gather feedback and to start industry partnership program.

; Conferences
: Presence (talks, workshops, networking) at FOSS4GNA 2023, FOSS4G Asia 2023, AGU 2023, CSDMD 2024, FOSS4G Europe 2024, FOSS4G 2024, AGU 2024

; Community sprints
: Virtual or in-person participation in OSGeo community sprints, GRASS GIS community sprints

; Software distribution (January 2024 - May 2025)
: Transition to CMake build system
: Develop conda package

;Simplify maintenance of GRASS integrations with QGIS and R (2024-2025)
: Virtual meetings with QGIS and R developers and GRASS GIS developers (spring 2024).
: Identify and implement improvements to the integration.

;Improve code quality, security, and quality assurance
: Code quality (Flake8, Pylint, Cppcheck), first half of 2024.
: Security (CodeQL), second half of 2024.
: Quality assurance (better pytest integration), second half of 2024.

; In-person developer summit (May 19 - May 24, 2025)
: Hosted by NC State University, Raleigh, NC, USA.
: Identify additional challenges for adoption of GRASS GIS as geoprocessing engine.
: Long-term planning beyond the POSE project.

== Acknowledgements ==

The funding is provided by the U.S. National Science Foundation, award 2303651.
[[File:NSF Official logo.png|frameless|left]]

[[Category: Community]]
[[Category: Conferences‏‎]]
[[Category: 2023]]
[[Category: 2024]]
[[Category: 2025]]

NSF POSE Project 2023-2025 Timeline

2025-06-05T19:55:12Z

Annakrat: /* Y2 4th quarter report (06/25 - 08/25) */

[[File:NSF_grant_announcement.png|500px|right|none]]

To inform GRASS community about the work done as part of the award [https://www.nsf.gov/awardsearch/showAward?AWD_ID=2303651 2303651] from the U.S. National Science Foundation (NSF) to enhance GRASS ecosystem, the following report summarizes the progress and outcomes in quarterly reports and presents the roadmap for the project.

The two main goals of the project are: 1) to facilitate the adoption of GRASS GIS as a key geoprocessing engine by a growing number of researchers and geospatial practitioners in academia, governments, and industry; and 2) to expand and diversify the developer community, especially through supporting next-generation scientists to gain expertise to maintain and innovate GRASS software.

Principal investigators and senior personnel:

* Helena Mitasova, North Carolina State University (Principal Investigator)
* Vaclav Petras, North Carolina State University (Co-Principal Investigator)
* Anna Petrasova, North Carolina State University (Co-Principal Investigator)
* C Michael Barton, Arizona State University (Co-Principal Investigator)
* Huidae Cho, New Mexico State University (Co-Principal Investigator)
* Giuseppe Amatulli, Yale (Senior Personnel)

Other personnel who is joining for the execution of the grant is listed below when relevant.

== Y1 1st quarter report (09/23 - 11/23) ==
=== Project Announcements and Communication ===
* Announcement on [https://grass.osgeo.org/news/2023_09_06_nsf_grant_awarded/ GRASS website].
* Info session to explain the POSE Project ([https://lists.osgeo.org/pipermail/grass-user/2023-September/083423.html Announcement on GRASS user mailing list], 2 sessions for different time zones).
* Collected statistics from GitHub, X and others and set up automated collection for GitHub.

=== Conference Presentations ===
* [https://petrasovaa.github.io/FUTURES-CONUS-talk/foss4gNA2023.html#/ Parallelization Tips for Geoprocessing with GRASS GIS] by Anna Petrasova at FOSS4GNA, October 2023.
* [https://wenzeslaus.github.io/grass-gis-talks/foss4gna2023.html#/ GRASS GIS: Not What You Think] by Vaclav Petras at FOSS4GNA, October 2023.
* [https://docs.google.com/presentation/d/1D-Fh1cLSPINyeXdVaxlakrE9IjB8kK5lIw3D12yX1bk Computational Notebooks for Reproducible Geospatial Computation in Research and Education] by Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/HuidaeCho/grass-gis-talk-foss4g-asia-2023 State of GRASS GIS: 40 Years Strong and Counting] by Huidae Cho at FOSS4G Asia, November 2023.

=== Training and Workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-foss4gna-2023 Unlock the power of GRASS GIS] by Anna Petrasova and Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/develop-tools-with-grass-foss4gna-2023 Develop Geospatial Workflows and Custom Tools with GRASS GIS] by Vaclav Petras and Corey White at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/grass-workshop-gis-week-2023 Big Data Computing with GRASS GIS] by Anna Petrasova and Vaclav Petras at NC State GIS week, November 2023.
* [https://github.com/ncsu-geoforall-lab/grass-gis-on-hpc-henry2/blob/8564c72e9b8929c9ef4d25ada1ef36b569991221/docs/tutorial.md GIS Week Workshop: High Performance Computing for Geospatial Analysis (GRASS GIS part)] by Vaclav Petras (main lecture lead by Andrew Petersen from NCSU OIT) at NC State GIS week, November 2023.
* [https://spatial-ecology.net/docs/build/html/COURSESAROUNDTHEWORLD/course_geocomp_ml_04-05_2024.html Geocomputation and Machine Learning for Environmental Applications] training course [https://spatial-ecology.net/course-geocomputation-machine-learning-for-environmental-applications-intermediate-level-2024/ announced]. GRASS GIS part led by Giuseppe Amatulli is free of charge thanks to the support by NSF.

=== Community Sprint Participation ===
Anna Petrasova and Vaclav Petras remotely participated in [https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2023 OSGeo 2023 code sprint] doing PR reviews and maintenance of GRASS GIS code, documentation, and website.

=== Mentoring Program ===
* Started a development-oriented mentoring program [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ announced] with details available on a [https://grasswiki.osgeo.org/wiki/Mentoring_Program wiki page].
* Program now has 4 participants (from 12 responses) supported by email and video calls.
* Program already resulted in improvements to GRASS GIS core and addons:
** merged PR: [https://github.com/OSGeo/grass/pull/3206 grass.script: ensure memmap content is flushed before writing to a raster]
** radar addon toolset PR: [https://github.com/OSGeo/grass-addons/pull/949 Add i.saocom and i.sar toolsets]
Mentoring Program is a new effort started and so-far performed only by the POSE team.

=== Student Grants Program ===
Student grants [https://grass.osgeo.org/news/2023_11_09_student_grants_announced/ announced] with topics at a [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants wiki page]. Student Grants Program is an existing effort which the POSE team participates in.

=== Working Groups ===

Four [https://grasswiki.osgeo.org/wiki/Working_Groups working groups] created (scope, wiki page, coordinator, and a list of people for each).

=== Citations ===

* GRASS GIS Google Scholar [https://scholar.google.com/citations?user=gJ0ZB0cAAAAJ account] updated with more complete records.
* A [https://forms.gle/cDEvMJu7d6nvxLKn9 form] was created to collect new and missing records.
* Profile link added to GRASS website [https://grass.osgeo.org/contribute/ Contribute] and [https://grass.osgeo.org/about/citation/ Citation] page.

== Y1 2nd quarter report (12/23 - 02/24) ==
=== NSF I-Corps program ===
Corey White, Vaclav Petras, and Anna Petrasova participated in a 4-week long intensive mandatory training that draws on the methods, customer discovery, and curriculum of the [https://new.nsf.gov/funding/initiatives/i-corps NSF Innovation Corps] and applies them to open-source projects.

The program included conducting 70+ 30-minute interviews with both GRASS users and non-users to better shape the future path of GRASS GIS and the POSE project. So far, the interviews focused on educators, companies, researchers, influencers and it focused more on non-users than users.

Next steps, include processing the collected qualitative data, developing possible future directions for sustainability of the project, discussing these with the Project Steering Committee, the core team of developers, and the broader community.

=== Mentoring Program ===
The development oriented [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ mentoring program] welcomed 5 new participants from various institutions including universities, USGS, US Army Corps of Engineers, and local municipalities. The discussed topics covered developing workflows for topography and network analysis, environmental modeling, and geophysics. Participants were supported by email and video calls.

=== Conference Presentations ===
* [https://agu.confex.com/agu/fm23/meetingapp.cgi/Paper/1342418 Modeling vegetated stream buffer impacts on water depth and discharge at the watershed scale with GRASS GIS and Jupyter Notebooks] by Caitlin Haedrich at AGU, December 2023.
* [https://agu.confex.com/agu/fm23/meetingapp.cgi/Paper/1420596 OpenPlains: A Web-Based Platform to Democratize Geospatial Participatory Modeling on the Cloud] by Corey White at AGU, December 2023.

=== Presentations and Workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-vanderbilt-2024 Intro to GRASS GIS] by Vaclav Petras and Anna Petrasova was remotely delivered to geographers at Vanderbilt University in February 2024. The workshop was developed in Jupyter Lab and run using [https://wholetale.org WholeTale] online platform.
* [https://github.com/tomorrownow/intro-to-geoprocessing-workshop Introduction to GRASS GIS Geospatial Processing] by Corey White at [https://smathhacks.ncssm.edu/ SMathHacks hackathon], March 2nd (supported also by Veronica Andreo and Vaclav Petras). SMathHacks is the annual 36-hour hackathon hosted by the NC School of Science and Math, open to all North Carolina students. Students collaborate to build innovative software projects, explore new technologies, and have fun along the way. The workshop was delivered in person with students using [https://colab.research.google.com/ Google Colab].

=== Student Grant Program ===
Linda Karlovska participates in the [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants Student Grant program] with her project [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation Easy command history navigation through the History browser panel] mentored by Anna Petrasova (POSE team) and Martin Landa (FCE CTU). Student Grants Program is an existing effort which the POSE team participates in by mentoring.

=== Code Security ===
Vaclav Petras mentors four students who create code security improvements in their NCSU class ''CSC 472: Cybersecurity Practicum''. So far, the students created two PRs which were successfully merged:
* [https://github.com/OSGeo/grass/pull/3444 grass.script: Change insecure mktemp to NamedTemporaryFile #3444]
* [https://github.com/OSGeo/grass/pull/3451 utils: fixed shell vulnerability in mkrest.py #3451]

Two other PRs are open and more work is underway to do first steps for new approach to a more secure code.

=== Localized Basic Datasets ===
* NCSU and ASU teams worked on localized versions of GRASS basic data set following the [https://grass.osgeo.org/sampledata/north_carolina/nc_basic_spm_grass7.zip North Carolina basic data set example], preparing Flagstaff, Arizona and Nepal draft version with basic layers

== Y1 3rd quarter report (03/24 - 05/24) ==

=== Mentoring Activities ===
The mentoring program form received 2 new responses and mentors were actively working with 3 mentees.
It resulted in fixes in [https://github.com/OSGeo/grass-addons/pull/1042 v.transects] and [https://github.com/OSGeo/grass-addons/pull/1077 r.accumulate].

Linda Kladivova finished her project developing [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation History browser] in the GRASS GUI as part of the GRASS Student Grant Program. Mentor's time was covered by POSE.

GRASS GIS has [https://grass.osgeo.org/news/2024_05_27_gsoc_2024_students/ 3 students this year for Google Summer of Code]. Time spent managing GSoC for GRASS GIS was covered by POSE.

The topics covered by GSoC projects are:
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_EODAG_Support Add EODAG support to GRASS GIS]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Improve_user_experience_in_Jupyter_Notebooks Improve GRASS user experience in Jupyter Notebook]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Add_JSON_output Add JSON output to different GRASS tools in C]

=== Presentations, Workshops, Event Planning ===
* [https://github.com/ncsu-geoforall-lab/tngic-2024 GRASS 101: From GUI Clicks to Writing Scripts (TNGIC 2024)] by Veronica Andreo and Caitlin Haedrich
* [https://github.com/ncsu-geoforall-lab/csdms-grass-2024 Coastal evolution analysis and inundation modeling with GRASS GIS (CSDMS Workshop 2024)] by Caitlin Haedrich and Pratikshya Regmi, see also [https://cnr.ncsu.edu/geospatial/news/2024/06/03/students-teach-grass-gis-for-coastal-hazard-analysis/ blog post with images]

* Organization of [[GRASS Community Meeting Prague 2024]] and budget planning by Vaclav Petras

=== CMake transition ===
Ongoing work on [https://github.com/OSGeo/grass/pull/3621 CMake compilation] was partially covered by POSE.

=== Code Quality and Security ===

Code quality improvements in Python code:
* [https://github.com/OSGeo/grass/pull/3541 PR addressing Flake8 E501] (long lines in 158 files not fixable by automated tools)
* [https://github.com/OSGeo/grass/pull/3535 PR addressing Flake8 E401] (unused imports)

Vaclav Petras mentored a team of four students who create code security improvements in their NCSU class ''CSC 472: Cybersecurity Practicum''. The team created 12 PRs which were successfully merged, 7 additional experimental PRs (not merged) and 2 PRs which are still open at this time. Specifically, the team achieved the following:

* With the involvement and help from the other contributors, the team introduced Bandit and Coverity Scan as additional code scanning tools for Python and C, respectively.
* The team analyzed issues reported CodeQL, Bandit, and Coverity Scan and reported on relevance of different issues to the project (report privately shared with the GRASS Development Team).
* Vulnerability Triage Guide (also privately shared with the GRASS Development Team).
* The team also developed a [https://github.com/OSGeo/grass/security/policy security policy] for the project.
* The vulnerability reporting and security advisories were enabled based on the team recommendations.
* The team fixed several specific security issues in the code:
** [https://github.com/OSGeo/grass/pull/3469 packaging: Use subprocess instead of os.popen for change log creation #3469] (merged)
** [https://github.com/OSGeo/grass/pull/3549 lib raster: fixed security vulnerabilities and weaknesses #3549] (merged)
** [https://github.com/OSGeo/grass/pull/3451 utils: fixed shell vulnerability in mkrest.py #3451] (merged)
** [https://github.com/OSGeo/grass/pull/3444 grass.script: Change insecure mktemp to NamedTemporaryFile #3444] (merged)
** [https://github.com/OSGeo/grass/pull/3551 lib/psdriver: Fix issues with wrong type of arguments to printf #3551] (PR open)
** [https://github.com/OSGeo/grass/pull/3452 g.region/r.to.rast3elev: fixed scanf error to recognize EOF as a possible return value #3452] (PR open)

=== Documentation ===
* Documentation and Education Working Group met and planned the development of new tutorials. Veronica Andreo met other GRASS developers and contributors to coordinate further tutorials development.
* Development of new [https://github.com/ncsu-geoforall-lab/tutorials tutorials] in progress, topics include:
** Getting started with GRASS GIS
** GRASS GIS in Google Colab
** GRASS GIS and Python
** GRASS GIS and R
** GRASS R and Python comparison
** Making plots in GRASS GIS
* New [https://github.com/OSGeo/grass/blob/main/doc/development/style_guide.md GRASS Programming Style Guide]
* [https://github.com/petrasovaa/cookiecutter-grass-addon New addon template powered by Cookiecutter]
* Analysis of options names and functionality in plotting tools:
** [https://github.com/OSGeo/grass-addons/issues/1071 Addons for plotting: Standardize parameters and flags]

=== Communication and outreach ===

* Creation of 4 news post in the [https://grass.osgeo.org/news/ GRASS website]
* Social media:
** [https://twitter.com/GRASSGIS Twitter]: 9 new posts/threads
** [https://fosstodon.org/@grassgis Fosstodon]: 9 new posts/threads

=== Other sustainability activities ===
* [https://github.com/OSGeo/grass/blob/main/CODE_OF_CONDUCT.md Code of Conduct added to the main repository]
* [https://github.com/OSGeo/grass/blob/main/.github/ISSUE_TEMPLATE/bug_report.md revised Issue template]
* New [https://github.com/OSGeo/grass/pull/3673 RFC for a Release Policy]
* Revised [https://github.com/OSGeo/grass/pull/2815 RFC for Release Procedure]
* WIP: GRASS GIS Roadmap
* [https://github.com/OSGeo/grass-website/issues/414 GRASS website: ongoing restructuring]
* [[PSC]] page moved from trac wiki to media wiki

== Y1 4th quarter report (06/24 - 08/24) ==

=== Mentoring Activities ===
The mentoring program form received 3 new responses and mentors were actively working with 3 mentees.
Results include parallelization of r.texture, r.horizon, improved grass.benchmarking library and a new tutorial on lidar data.

GSoC successfully completed their projects:
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_EODAG_Support Add EODAG support to GRASS GIS]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Improve_user_experience_in_Jupyter_Notebooks Improve GRASS user experience in Jupyter Notebook]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Add_JSON_output Add JSON output to different GRASS tools in C]

Time spent by mentoring was covered by NSF.

=== Presentations, Workshops, Event Planning ===

* [https://veroandreo.github.io/grass_foss4geu_2024/ Let's combine GRASS, Python and R: Satellite time series data for species distribution modeling]. Workshop by Veronica Andreo. FOSS4G Europe 2024, Tartu.
* [https://veroandreo.github.io/grass-gis-talks/foss4gEU2024.html#/ Status of GRASS GIS project]. Talk by Veronica Andreo. FOSS4G Europe 2024, Tartu.
* [https://veroandreo.github.io/grass-gis-talks/useR2024.html#/ Boost Spatial Data Science Workflows with GRASS GIS and R]. Talk by Veronica Andreo. useR Conference 2024, Salzburg.
* [https://ncsu-geoforall-lab.github.io/usdoi-webinar/notebooks/grass_jupyter.html Geoprocessing with GRASS GIS and Jupyter Notebooks]. Webinar by Corey White. U.S. DOI, August 2024, NCSU.
* [[GRASS Community Meeting Prague 2024]]

* [https://spatial-ecology.net/docs/build/html/COURSESAROUNDTHEWORLD/course_GEO-OPEN-HACK-2024_06_2024.html GEO-OPEN-HACK-2024: Big Geospatial Data Hackathon with Open Infrastructure and Tools] training course delivered ([https://iiasa.ac.at/events/jun-2024/geo-open-hack-2024-big-geospatial-data-hackathon-with-open-infrastructure-and-tools announcement]). The GRASS material has been developed as part of the NSF grant.

* Planning GRASS Dev summit 2025 at NCSU

* Planning AGU (4 abstract submitted), AGU booth for GRASS GIS reserved and payed

* Submitted workshop, talk and keynote to FOSS4G 2024 - Brazil.

=== CMake transition ===
Ongoing work on [https://github.com/OSGeo/grass/pull/3621 CMake compilation] was partially covered by POSE.

=== Code Quality and Security ===

* Code quality improvements in Python code:
** [https://github.com/OSGeo/grass/pull/3763 Flake8 W605 Invalid escape sequence #3763]
** [https://github.com/OSGeo/grass/pull/3926 Flake8 E741 Do not use variables named 'I', 'O', or 'l' in wxGUI code #3926]
** [https://github.com/OSGeo/grass/pull/3928 Flake8 E741 for the rest of code base #3928]
** [https://github.com/OSGeo/grass/pull/4200 grass.temporal: Flake8 F841 Local variable assigned to but never used #4200]
** [https://github.com/OSGeo/grass/pull/4113 grass.pygrass: Remove unused arg in ctypes.CFUNCTYPE #4113]
** [https://github.com/OSGeo/grass/pull/4206 t.rast.to.vect: Fix passing column parameter to r.to.vect, fix flake8 F841 #4206]

* Code quality and security improvements in C and C++ code are in 36 PRs with fixes for more than 25 tools, specifically in:
** raster: r.path, r.out.mpeg, r.out.png, r.in.xyz, r.terraflow, r.statistics, r.spreadpath, r.sim.water, r.sim.erosion, r.object.geometry, r.coin
** imagery: i.atcorr, i.aster.toar, i.ortho.photo, i.landsat.acca, i.segment, i.smap
** display: d.linegraph, d.legend.vect, d.histogram, d.labels
** raster 3D: r3.in.v5d, r3.info, r3.mapcalc
** other: lib/gis, lib/vector/diglib, g.findfile, g.setproj, ps.map, lib/cdhc

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShubhamDesai+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ ShubhamDesai], [https://github.com/OSGeo/grass/pulls?q=author%3Amshukuno+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ Makiko Shukunobe], [https://github.com/OSGeo/grass/pulls?q=author%3Aymdatta+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ ymdatta]

Several reviewers, not supported by the NSF POSE project, played crucial role not only in reviewing, but also in determining the right fixes.

Fixed issues were reported by Flake8, Coverity Scan, and Cppcheck.

=== Tests ===

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShreshth-Malik+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ Shreshth-Malik]

=== Documentation ===

* Veronica Andreo met some GRASS developers and contributors to follow up on tutorials development.
* 7 new [https://github.com/ncsu-geoforall-lab/tutorials tutorials] on time series:
** Management and visualization
** Aggregation
** Algebra
** Accumulation
** Gap filling
** Querying raster time series with vectors
** Subset, import and export
* Tutorial on how to set up Jupyter and GRASS in Windows
* New [https://github.com/OSGeo/grass-tutorials repository] under OSGeo organization to host the upcoming quarto based website for GRASS tutorials
* PR template created - [https://github.com/OSGeo/grass/community GitHub Community Standards] all checked complete

=== Communication and outreach ===

* Creation of 4 news posts in the [https://grass.osgeo.org/news/ GRASS website]
* Social media:
** [https://twitter.com/GRASSGIS Twitter]: 25 new posts
** [https://fosstodon.org/@grassgis Fosstodon]: 25 new posts
* New GRASS GIS LinkedIn page at: [https://www.linkedin.com/company/grass-gis/ https://www.linkedin.com/company/grass-gis/]
* Requested transition of [https://discourse.osgeo.org/t/osgeo-3255-migrate-grass-dev-mailing-list-to-discourse/49796 grass-dev mailing list to discourse.osgeo.org]
* Set up GRASS GIS swag shop on Redbubble

=== Governance ===
* [https://grass.osgeo.org/about/roadmap/ Roadmap] and [https://grass.osgeo.org/about/governance/ Governance] pages added to the website
* PSC elections:
** Documented criteria to define people entitled to vote
** Documented procedure to compile the list of voters
** Elections [https://www.mail-archive.com/grass-user@lists.osgeo.org/msg41102.html announcement] sent out

== Y2 1st quarter report (09/24 - 11/24) ==

=== Presentations and Workshops ===
FOSS4GNA 2024 in St. Louis, Missouri:

* Vaclav Petras. State of GRASS GIS. FOSS4G NA St. Louis, September 9-11, 2024 ([https://wenzeslaus.github.io/grass-gis-talks/foss4gna2024.html slides])
* Huidae Cho. Evolution of GRASS GIS. FOSS4G NA St. Louis, September 9-11, 2024 ([https://htmlpreview.github.io/?https://github.com/HuidaeCho/grass-talks/blob/main/foss4g-na-2024.html slides])
* Huidae Cho. An OpenMP Algorithm for Delineating a Large Number of Watersheds. FOSS4G NA St. Louis, September 9-11, 2024
* Corey T. White. Developing Web-Applications with GRASS GIS. Workshop. FOSS4G NA St. Louis, September 9-11, 2024
* Corey T. White. GRASS GIS as a Geospatial Computational Engine. FOSS4G NA St. Louis, September 9-11, 2024

=== Communication and outreach ===
* Transition of grass-dev mailing list to [https://discourse.osgeo.org/c/grass/developer/61 discourse.osgeo.org] finished.

=== Code Quality and Security ===
* Python code quality issues addressed in more than 70 PRs, reducing the list of per-file ignores by more than 60%.
* Code quality and security improvements in C and C++ code are in more than 80 PRs.
* In total, these changes improve more than 60 tools, specifically:
** raster: r.water.outlet, r.watershed, r.mfilter, r.to.vect, r.in.poly, r.carve, r.thin, r.fill.dir, r.clump, r.in.gridatb, r.out.png, r.in.wms, r.viewshed, r.fillnulls, r.in.srtm, r.in.pdal, r.in.xyz
** vector: v.out.dxf, v.build.polylines, v.external.out, v.net, v.univar, v.in.ascii, v.delaunay, v.hull , v.net.timetable, v.kernel, v.to.db, v.colors, v.rectify, v.reclass, v.generalize, v.transform, v.vol.rst, v.cluster, v.to.3d, v.out.ogr, v.external, v.in.dwg, v.report, v.unpack, v.import
** imagery: i.topo.corr, i.attcorr, i.ortho.photo, i.segment, i.rectify, i.topo.corr, i.panshrapen
** display: d.vect, d.mon, d.frame, d.rast.edit
** other: GUI, grass main executable, g.proj, g.version, db.out.ogr, ps.map, r3.in.v5d, r3.in.v5d, lib/vector/Vlib, lib/ogsf, lib/gis, lib/db, lib/lidar, lib/linkm, grass.temporal, grass.script

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShubhamDesai+is%3Apr+is%3Aclosed+merged%3A2024-09-01..2024-11-30+base%3Amain+sort%3Aupdated-desc+ ShubhamDesai], [https://github.com/OSGeo/grass/pulls?q=author%3Aymdatta+is%3Apr+is%3Aclosed+merged%3A2024-09-01..2024-11-30+base%3Amain+sort%3Aupdated-desc+ ymdatta],
[https://github.com/OSGeo/grass/pulls?q=author%3Aarohanajit+is%3Apr+is%3Aclosed+merged%3A2024-09-01..2024-11-30+base%3Amain+sort%3Aupdated-desc+ Arohan Ajit]

Several reviewers, not supported by the NSF POSE project, played crucial role not only in reviewing, but also in determining the right fixes. The NSF POSE project personnel focused on fixing issues reported by Flake8, Coverity Scan, and Cppcheck, however also Ruff and Pylint are utilized in GRASS GIS thanks to other contributors.

A configure file for Cppcheck is now included in the repository highlighting the level of compliance and aiding contributors in local analysis and subsequent implementation of fixes ([https://github.com/OSGeo/grass/pull/4766 PR #4766]).

Finally, we created a new public GitHub project in the OSGeo GitHub organization for [https://github.com/orgs/OSGeo/projects/11 GRASS GIS Security] to track and communicate progress on the security front with 147 resolved items and 8 in-progress items at the time of writing.

=== Documentation, both Internal and External ===

* To improve indexing of GRASS GIS manual pages, we revised our current sitemap ([https://github.com/OSGeo/grass-website/pull/482 grass-website/pull/482)]), added a updated sitemap to Google Search Console and Bing, fixed robots.txt, and triggered and re-triggered the indexing many times to make Google consume the new content. While before, some searches gave outdated documentation, experimental websites, or unofficial resources only, now the official website and stable documentation is returned as the first search result.
* All older manuals, including version 6.4 and 6.5, are now available (restored) so that search engines can consume them and old links and indices continue to work. They now newly contain the canonical URLs so that search engines understand the structure and don't penalize duplicate content.
* On OSGeo server which hosts GRASS GIS website, we replaced some of the redirects in Apache by local soft links so that URL like grass.osgeo.org/grass-stable stay as is for both humans and machines and don't redirect to specific version (easier to copy-paste from a browser URL bar and easier for search engine to understand what is the page to show).
* We implemented the necessary changes into the cronjobs and did overall updates to enable build of the server-side documentation jobs locally for testing purposes. The most relevant PRs are:
** [https://github.com/OSGeo/grass-addons/pull/1241 Inject canonical URLs into older manual pages (SEO) #1241]
** [https://github.com/OSGeo/grass-addons/pull/1173 Fix red new version box injection and script documentation #1173]
** [https://github.com/OSGeo/grass-addons/pull/1215 Expand script to run stand-alone #1215]
* We advanced the [https://github.com/orgs/OSGeo/projects/9 GRASS Markdown Documentation project].
* New and better wording for intro to imagery tools: [https://github.com/OSGeo/grass/pull/4536 Add intro text to imageryintro.html #4536]
* List of GRASS GIS profiles on different websites is now in an internal PSC document.
* Documentation of all the internal infrastructure, especially that of grass.osgeo.org server, is now in an internal PSC document.
* We painstakingly identified and described all maintenance procedures performed by Markus Neteler in OSGeo SAC capacity for GRASS GIS and as a contributor to GRASS GIS for better work distribution.
* Most of the work on the documentation was done through a contract with Markus Neteler with additional help from Martin Landa for the transition to Markdown.

=== Mentoring Activities ===
Mentors were actively working with 3 mentees.

=== Event Planning and Organizing ===

[[File:Raleigh_2016_11_05.jpg|500px|thumb|right|alt=Rooms, tables and large open space|Smaller space utilized in the past for a local GRASS GIS meetup in Hunt library at NC State University campus (photos are from a [[GRASS GIS Raleigh meetups 2016|2016 meetup]])]]

We are planning and organizing GRASS GIS Developer Summit in Raleigh, NC, USA at North Carolina State University.

* High-demand spaces reserved at NCSU (some since May 2024, other since September 2024).
* A [https://discourse.osgeo.org/t/grass-dev-save-the-date-grass-developer-summit-raleigh-2025/85540 save-the-date post for grass-dev], interest form, and first round of additional invites. (Date established earlier in spring 2024 by NSF POSE team after a survey of PSC members and Core Development Team members.)
* We addressed participant's visa needs based on the responses to the interest form.
* We formed the initial Organizing Committee formed and rough event agenda created.
* Page created: [[GRASS Developer Summit Raleigh 2025]].

== Y2 2nd quarter report (12/24 - 02/25) ==

=== Presentations, Workshops, Event Planning ===

[[File:GRASS GIS booth AGU24.jpg|500px|thumb|right|alt=GRASS GIS booth at AGU24|GRASS GIS booth at AGU24, Washington, DC]]

AGU24 Annual Meeting, Washington, DC, USA:
* GRASS GIS booth in the Exhibit Hall with a banner, new flyers, and a Tangible Landscape setup to demonstrate some of the capabilities of GRASS GIS (Monday afternoon - Thursday morning)
* GRASS GIS for Advanced Earth Systems Analysis and Modeling (eLightning) by Vaclav Petras
* Perspectives from an Open Source Geospatial Modeling Platform Maintainer (poster) by Anna Petrasova
* GRASS GIS Is FAIR: Its Evolution Towards Open Science (poster) by Huidae Cho
* GRASS GIS as a Platform for Dissemination of Reusable Geocomputational Research (poster) by Vaclav Petras

Beyond the GIS Map: Open Source Tools for Geospatial Research, Workshop at the Institute for Social Science Research Arizona State University. 11 December 2024
* Michael Barton and Eunice Villaseñor Iribe, instructors
* Topics
** Introduction to GRASS
** Modeling Terrain in GRASS
** Modeling Movement in GRASS
** Remote Sensing With GRASS

Physically-based hydrologic modeling using GRASS GIS r.topmodel, Workshop at New Mexico State University. January 31, 2025, 1pm-5pm.
* Instructor: Huidae Cho
* Assistant: Nelson Kandel
* Participants: 17
* Topics
** Introduction to GRASS
** Hydrologic Modeling Using GRASS
** Model Calibration and Validation

=== Code Quality and Security ===

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShubhamDesai+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ ShubhamDesai], [https://github.com/OSGeo/grass/pulls?q=author%3Aarohanajit+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ Arohan Ajit]

=== Tests ===

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShreshth-Malik+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ Shreshth-Malik], [https://github.com/OSGeo/grass/pulls?q=author%3Ajayneel-shah18+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ jayneel-shah18]

=== Documentation and Tutorials ===
We finalized and prepared for launch Quarto-based tutorial website editable through GitHub. OSGeo provided a new domain [https://grass-tutorials.osgeo.org/ grass-tutorials.osgeo.org]. Initial set of tutorials were created by Veronica Andreo when she was part of the NSF POSE team (some tutorials will be finalized and released later). Anna Petrasova did the reviews, curation, posts for external tutorials, and transition from list of tutorials at the main website.

We did a major push to create Markdown files in the source code and enable the compilation of documentation for mkdocs. We also configured the mkdocs and revised the Markdown syntax in the files.

=== Communication and outreach ===

Renewed [https://www.youtube.com/@grass-gis Youtube channel @grass-gis] by adding playlists, organizing videos, and updating branding.

=== Governance ===
Submitted application for GRASS GIS to join NumFocus.

=== Event Planning and Organizing ===

* Created draft of schedule, agenda, and budget.
* Identified participants eligible for travel support.
** While the meeting is open to anyone, the NSF-funded travel support is based on priorities set in the NSF POSE project for the Developer Summit.
** Specifically, we are inviting individuals identified based on the following criteria (in this order; moving to the next group if there is still available places):
*** Top 20 contributors to OSGeo/grass in the last two years (2023-2024), but not a bot or NSF POSE personnel (contributing only within NSF POSE). (After exclusions, this is less than 10 people.)
*** PSC member before or after 2024 elections, but not NSF POSE personnel at the time of the meeting. (With PSC members currently contributing code as well, this is only a couple of people after exclusions.)
*** Active participant in one of the mentoring programs. (Participant demonstrated the activity by attending meetings, reporting progress, or submitting code for feedback or review.)
*** Contributors to connections and interfaces prioritized in or during the NSF POSE project:
**** R packages (2 slots for active contributors or maintainers determined by previously established contacts in the given community through their activity on a relevant code base.)
**** GRASS GIS code in QGIS (2 slots for active contributors or maintainers determined by previously established contacts in the given community through their activity on a relevant code base.)
*** Contributors in "write" teams for OSGeo/grass, OSGeo/grass-addons, OSGeo/grass-website, and OSGeo/grass-tutorials repositories. (Almost all fall into one of the above groups.)
*** Contributors to closely related projects, specifically actinia, the GRASS GDAL driver, and the GRASS GeoServer datastore.
* Sent individual invites to participants eligible for travel support. (ongoing)

== Y2 3rd quarter report (03/25 - 05/25) ==

=== Governance ===
* GRASS accepted NumFOCUS (more steps to make it official)

=== Presentations, Workshops, Event Planning ===
* Beyond the GIS Map: Open Source Tools for Geospatial Research, Workshop at the Institute for Social Science Research Arizona State University. 25 March 2025
** Michael Barton and Eunice Villaseñor Iribe, instructors
** Topics: Introduction, Modeling Terrain, Modeling Movement, Remote Sensing with GRASS
* IALE-NA: [https://github.com/ncsu-geoforall-lab/iale-2025-workshop-tl Building Geospatial Models in GRASS: From Python Workflows to Tangible Landscape], April 15th, hosted by the Center for Geospatial Analytics
** Anna Petrasova and Caitlin Haedrich
** 20 participants

* [[GRASS_Developer_Summit_Raleigh_2025]] (see the page for details)

== Y2 4th quarter report (06/25 - 08/25) ==

=== Governance ===
* GRASS onboarding with NumFOCUS

=== Presentations, Workshops, Event Planning ===
* Geomorphometry workshop - Corey White and Caitlin Haedrich

== Roadmap ==
;Mentoring program (fall 2023 - summer 2025)
:Free developer-oriented mentoring program to support researchers and software developers to integrate GRASS GIS into their workflows and contribute to GRASS GIS.

; Streamline contributor onboarding (spring 2024 - fall 2024)
: Includes updating and creating guidelines for code and non-code contributions.

; Streamline user onboarding (spring 2024 - fall 2024)
: Includes modernizing tool documentation, developing tutorials.
: Creating sample datasets for localized tutorials.
: Developing online training materials for big data processing.

; Training sessions (fall 2023 - summer 2025)
: Local training sessions (at universities and conferences) introducing GRASS GIS to students and researchers.
: Training program for big data processing delivered online.

; Engaging industry partners and user (January 2024 - August 2025)
: Identify and engage industry partners to gather feedback and to start industry partnership program.

; Conferences
: Presence (talks, workshops, networking) at FOSS4GNA 2023, FOSS4G Asia 2023, AGU 2023, CSDMD 2024, FOSS4G Europe 2024, FOSS4G 2024, AGU 2024

; Community sprints
: Virtual or in-person participation in OSGeo community sprints, GRASS GIS community sprints

; Software distribution (January 2024 - May 2025)
: Transition to CMake build system
: Develop conda package

;Simplify maintenance of GRASS integrations with QGIS and R (2024-2025)
: Virtual meetings with QGIS and R developers and GRASS GIS developers (spring 2024).
: Identify and implement improvements to the integration.

;Improve code quality, security, and quality assurance
: Code quality (Flake8, Pylint, Cppcheck), first half of 2024.
: Security (CodeQL), second half of 2024.
: Quality assurance (better pytest integration), second half of 2024.

; In-person developer summit (May 19 - May 24, 2025)
: Hosted by NC State University, Raleigh, NC, USA.
: Identify additional challenges for adoption of GRASS GIS as geoprocessing engine.
: Long-term planning beyond the POSE project.

== Acknowledgements ==

The funding is provided by the U.S. National Science Foundation, award 2303651.
[[File:NSF Official logo.png|frameless|left]]

[[Category: Community]]
[[Category: Conferences‏‎]]
[[Category: 2023]]
[[Category: 2024]]
[[Category: 2025]]

NSF POSE Project 2023-2025 Timeline

2025-06-05T19:53:29Z

Annakrat:

[[File:NSF_grant_announcement.png|500px|right|none]]

To inform GRASS community about the work done as part of the award [https://www.nsf.gov/awardsearch/showAward?AWD_ID=2303651 2303651] from the U.S. National Science Foundation (NSF) to enhance GRASS ecosystem, the following report summarizes the progress and outcomes in quarterly reports and presents the roadmap for the project.

The two main goals of the project are: 1) to facilitate the adoption of GRASS GIS as a key geoprocessing engine by a growing number of researchers and geospatial practitioners in academia, governments, and industry; and 2) to expand and diversify the developer community, especially through supporting next-generation scientists to gain expertise to maintain and innovate GRASS software.

Principal investigators and senior personnel:

* Helena Mitasova, North Carolina State University (Principal Investigator)
* Vaclav Petras, North Carolina State University (Co-Principal Investigator)
* Anna Petrasova, North Carolina State University (Co-Principal Investigator)
* C Michael Barton, Arizona State University (Co-Principal Investigator)
* Huidae Cho, New Mexico State University (Co-Principal Investigator)
* Giuseppe Amatulli, Yale (Senior Personnel)

Other personnel who is joining for the execution of the grant is listed below when relevant.

== Y1 1st quarter report (09/23 - 11/23) ==
=== Project Announcements and Communication ===
* Announcement on [https://grass.osgeo.org/news/2023_09_06_nsf_grant_awarded/ GRASS website].
* Info session to explain the POSE Project ([https://lists.osgeo.org/pipermail/grass-user/2023-September/083423.html Announcement on GRASS user mailing list], 2 sessions for different time zones).
* Collected statistics from GitHub, X and others and set up automated collection for GitHub.

=== Conference Presentations ===
* [https://petrasovaa.github.io/FUTURES-CONUS-talk/foss4gNA2023.html#/ Parallelization Tips for Geoprocessing with GRASS GIS] by Anna Petrasova at FOSS4GNA, October 2023.
* [https://wenzeslaus.github.io/grass-gis-talks/foss4gna2023.html#/ GRASS GIS: Not What You Think] by Vaclav Petras at FOSS4GNA, October 2023.
* [https://docs.google.com/presentation/d/1D-Fh1cLSPINyeXdVaxlakrE9IjB8kK5lIw3D12yX1bk Computational Notebooks for Reproducible Geospatial Computation in Research and Education] by Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/HuidaeCho/grass-gis-talk-foss4g-asia-2023 State of GRASS GIS: 40 Years Strong and Counting] by Huidae Cho at FOSS4G Asia, November 2023.

=== Training and Workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-foss4gna-2023 Unlock the power of GRASS GIS] by Anna Petrasova and Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/develop-tools-with-grass-foss4gna-2023 Develop Geospatial Workflows and Custom Tools with GRASS GIS] by Vaclav Petras and Corey White at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/grass-workshop-gis-week-2023 Big Data Computing with GRASS GIS] by Anna Petrasova and Vaclav Petras at NC State GIS week, November 2023.
* [https://github.com/ncsu-geoforall-lab/grass-gis-on-hpc-henry2/blob/8564c72e9b8929c9ef4d25ada1ef36b569991221/docs/tutorial.md GIS Week Workshop: High Performance Computing for Geospatial Analysis (GRASS GIS part)] by Vaclav Petras (main lecture lead by Andrew Petersen from NCSU OIT) at NC State GIS week, November 2023.
* [https://spatial-ecology.net/docs/build/html/COURSESAROUNDTHEWORLD/course_geocomp_ml_04-05_2024.html Geocomputation and Machine Learning for Environmental Applications] training course [https://spatial-ecology.net/course-geocomputation-machine-learning-for-environmental-applications-intermediate-level-2024/ announced]. GRASS GIS part led by Giuseppe Amatulli is free of charge thanks to the support by NSF.

=== Community Sprint Participation ===
Anna Petrasova and Vaclav Petras remotely participated in [https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2023 OSGeo 2023 code sprint] doing PR reviews and maintenance of GRASS GIS code, documentation, and website.

=== Mentoring Program ===
* Started a development-oriented mentoring program [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ announced] with details available on a [https://grasswiki.osgeo.org/wiki/Mentoring_Program wiki page].
* Program now has 4 participants (from 12 responses) supported by email and video calls.
* Program already resulted in improvements to GRASS GIS core and addons:
** merged PR: [https://github.com/OSGeo/grass/pull/3206 grass.script: ensure memmap content is flushed before writing to a raster]
** radar addon toolset PR: [https://github.com/OSGeo/grass-addons/pull/949 Add i.saocom and i.sar toolsets]
Mentoring Program is a new effort started and so-far performed only by the POSE team.

=== Student Grants Program ===
Student grants [https://grass.osgeo.org/news/2023_11_09_student_grants_announced/ announced] with topics at a [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants wiki page]. Student Grants Program is an existing effort which the POSE team participates in.

=== Working Groups ===

Four [https://grasswiki.osgeo.org/wiki/Working_Groups working groups] created (scope, wiki page, coordinator, and a list of people for each).

=== Citations ===

* GRASS GIS Google Scholar [https://scholar.google.com/citations?user=gJ0ZB0cAAAAJ account] updated with more complete records.
* A [https://forms.gle/cDEvMJu7d6nvxLKn9 form] was created to collect new and missing records.
* Profile link added to GRASS website [https://grass.osgeo.org/contribute/ Contribute] and [https://grass.osgeo.org/about/citation/ Citation] page.

== Y1 2nd quarter report (12/23 - 02/24) ==
=== NSF I-Corps program ===
Corey White, Vaclav Petras, and Anna Petrasova participated in a 4-week long intensive mandatory training that draws on the methods, customer discovery, and curriculum of the [https://new.nsf.gov/funding/initiatives/i-corps NSF Innovation Corps] and applies them to open-source projects.

The program included conducting 70+ 30-minute interviews with both GRASS users and non-users to better shape the future path of GRASS GIS and the POSE project. So far, the interviews focused on educators, companies, researchers, influencers and it focused more on non-users than users.

Next steps, include processing the collected qualitative data, developing possible future directions for sustainability of the project, discussing these with the Project Steering Committee, the core team of developers, and the broader community.

=== Mentoring Program ===
The development oriented [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ mentoring program] welcomed 5 new participants from various institutions including universities, USGS, US Army Corps of Engineers, and local municipalities. The discussed topics covered developing workflows for topography and network analysis, environmental modeling, and geophysics. Participants were supported by email and video calls.

=== Conference Presentations ===
* [https://agu.confex.com/agu/fm23/meetingapp.cgi/Paper/1342418 Modeling vegetated stream buffer impacts on water depth and discharge at the watershed scale with GRASS GIS and Jupyter Notebooks] by Caitlin Haedrich at AGU, December 2023.
* [https://agu.confex.com/agu/fm23/meetingapp.cgi/Paper/1420596 OpenPlains: A Web-Based Platform to Democratize Geospatial Participatory Modeling on the Cloud] by Corey White at AGU, December 2023.

=== Presentations and Workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-vanderbilt-2024 Intro to GRASS GIS] by Vaclav Petras and Anna Petrasova was remotely delivered to geographers at Vanderbilt University in February 2024. The workshop was developed in Jupyter Lab and run using [https://wholetale.org WholeTale] online platform.
* [https://github.com/tomorrownow/intro-to-geoprocessing-workshop Introduction to GRASS GIS Geospatial Processing] by Corey White at [https://smathhacks.ncssm.edu/ SMathHacks hackathon], March 2nd (supported also by Veronica Andreo and Vaclav Petras). SMathHacks is the annual 36-hour hackathon hosted by the NC School of Science and Math, open to all North Carolina students. Students collaborate to build innovative software projects, explore new technologies, and have fun along the way. The workshop was delivered in person with students using [https://colab.research.google.com/ Google Colab].

=== Student Grant Program ===
Linda Karlovska participates in the [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants Student Grant program] with her project [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation Easy command history navigation through the History browser panel] mentored by Anna Petrasova (POSE team) and Martin Landa (FCE CTU). Student Grants Program is an existing effort which the POSE team participates in by mentoring.

=== Code Security ===
Vaclav Petras mentors four students who create code security improvements in their NCSU class ''CSC 472: Cybersecurity Practicum''. So far, the students created two PRs which were successfully merged:
* [https://github.com/OSGeo/grass/pull/3444 grass.script: Change insecure mktemp to NamedTemporaryFile #3444]
* [https://github.com/OSGeo/grass/pull/3451 utils: fixed shell vulnerability in mkrest.py #3451]

Two other PRs are open and more work is underway to do first steps for new approach to a more secure code.

=== Localized Basic Datasets ===
* NCSU and ASU teams worked on localized versions of GRASS basic data set following the [https://grass.osgeo.org/sampledata/north_carolina/nc_basic_spm_grass7.zip North Carolina basic data set example], preparing Flagstaff, Arizona and Nepal draft version with basic layers

== Y1 3rd quarter report (03/24 - 05/24) ==

=== Mentoring Activities ===
The mentoring program form received 2 new responses and mentors were actively working with 3 mentees.
It resulted in fixes in [https://github.com/OSGeo/grass-addons/pull/1042 v.transects] and [https://github.com/OSGeo/grass-addons/pull/1077 r.accumulate].

Linda Kladivova finished her project developing [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation History browser] in the GRASS GUI as part of the GRASS Student Grant Program. Mentor's time was covered by POSE.

GRASS GIS has [https://grass.osgeo.org/news/2024_05_27_gsoc_2024_students/ 3 students this year for Google Summer of Code]. Time spent managing GSoC for GRASS GIS was covered by POSE.

The topics covered by GSoC projects are:
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_EODAG_Support Add EODAG support to GRASS GIS]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Improve_user_experience_in_Jupyter_Notebooks Improve GRASS user experience in Jupyter Notebook]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Add_JSON_output Add JSON output to different GRASS tools in C]

=== Presentations, Workshops, Event Planning ===
* [https://github.com/ncsu-geoforall-lab/tngic-2024 GRASS 101: From GUI Clicks to Writing Scripts (TNGIC 2024)] by Veronica Andreo and Caitlin Haedrich
* [https://github.com/ncsu-geoforall-lab/csdms-grass-2024 Coastal evolution analysis and inundation modeling with GRASS GIS (CSDMS Workshop 2024)] by Caitlin Haedrich and Pratikshya Regmi, see also [https://cnr.ncsu.edu/geospatial/news/2024/06/03/students-teach-grass-gis-for-coastal-hazard-analysis/ blog post with images]

* Organization of [[GRASS Community Meeting Prague 2024]] and budget planning by Vaclav Petras

=== CMake transition ===
Ongoing work on [https://github.com/OSGeo/grass/pull/3621 CMake compilation] was partially covered by POSE.

=== Code Quality and Security ===

Code quality improvements in Python code:
* [https://github.com/OSGeo/grass/pull/3541 PR addressing Flake8 E501] (long lines in 158 files not fixable by automated tools)
* [https://github.com/OSGeo/grass/pull/3535 PR addressing Flake8 E401] (unused imports)

Vaclav Petras mentored a team of four students who create code security improvements in their NCSU class ''CSC 472: Cybersecurity Practicum''. The team created 12 PRs which were successfully merged, 7 additional experimental PRs (not merged) and 2 PRs which are still open at this time. Specifically, the team achieved the following:

* With the involvement and help from the other contributors, the team introduced Bandit and Coverity Scan as additional code scanning tools for Python and C, respectively.
* The team analyzed issues reported CodeQL, Bandit, and Coverity Scan and reported on relevance of different issues to the project (report privately shared with the GRASS Development Team).
* Vulnerability Triage Guide (also privately shared with the GRASS Development Team).
* The team also developed a [https://github.com/OSGeo/grass/security/policy security policy] for the project.
* The vulnerability reporting and security advisories were enabled based on the team recommendations.
* The team fixed several specific security issues in the code:
** [https://github.com/OSGeo/grass/pull/3469 packaging: Use subprocess instead of os.popen for change log creation #3469] (merged)
** [https://github.com/OSGeo/grass/pull/3549 lib raster: fixed security vulnerabilities and weaknesses #3549] (merged)
** [https://github.com/OSGeo/grass/pull/3451 utils: fixed shell vulnerability in mkrest.py #3451] (merged)
** [https://github.com/OSGeo/grass/pull/3444 grass.script: Change insecure mktemp to NamedTemporaryFile #3444] (merged)
** [https://github.com/OSGeo/grass/pull/3551 lib/psdriver: Fix issues with wrong type of arguments to printf #3551] (PR open)
** [https://github.com/OSGeo/grass/pull/3452 g.region/r.to.rast3elev: fixed scanf error to recognize EOF as a possible return value #3452] (PR open)

=== Documentation ===
* Documentation and Education Working Group met and planned the development of new tutorials. Veronica Andreo met other GRASS developers and contributors to coordinate further tutorials development.
* Development of new [https://github.com/ncsu-geoforall-lab/tutorials tutorials] in progress, topics include:
** Getting started with GRASS GIS
** GRASS GIS in Google Colab
** GRASS GIS and Python
** GRASS GIS and R
** GRASS R and Python comparison
** Making plots in GRASS GIS
* New [https://github.com/OSGeo/grass/blob/main/doc/development/style_guide.md GRASS Programming Style Guide]
* [https://github.com/petrasovaa/cookiecutter-grass-addon New addon template powered by Cookiecutter]
* Analysis of options names and functionality in plotting tools:
** [https://github.com/OSGeo/grass-addons/issues/1071 Addons for plotting: Standardize parameters and flags]

=== Communication and outreach ===

* Creation of 4 news post in the [https://grass.osgeo.org/news/ GRASS website]
* Social media:
** [https://twitter.com/GRASSGIS Twitter]: 9 new posts/threads
** [https://fosstodon.org/@grassgis Fosstodon]: 9 new posts/threads

=== Other sustainability activities ===
* [https://github.com/OSGeo/grass/blob/main/CODE_OF_CONDUCT.md Code of Conduct added to the main repository]
* [https://github.com/OSGeo/grass/blob/main/.github/ISSUE_TEMPLATE/bug_report.md revised Issue template]
* New [https://github.com/OSGeo/grass/pull/3673 RFC for a Release Policy]
* Revised [https://github.com/OSGeo/grass/pull/2815 RFC for Release Procedure]
* WIP: GRASS GIS Roadmap
* [https://github.com/OSGeo/grass-website/issues/414 GRASS website: ongoing restructuring]
* [[PSC]] page moved from trac wiki to media wiki

== Y1 4th quarter report (06/24 - 08/24) ==

=== Mentoring Activities ===
The mentoring program form received 3 new responses and mentors were actively working with 3 mentees.
Results include parallelization of r.texture, r.horizon, improved grass.benchmarking library and a new tutorial on lidar data.

GSoC successfully completed their projects:
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_EODAG_Support Add EODAG support to GRASS GIS]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Improve_user_experience_in_Jupyter_Notebooks Improve GRASS user experience in Jupyter Notebook]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Add_JSON_output Add JSON output to different GRASS tools in C]

Time spent by mentoring was covered by NSF.

=== Presentations, Workshops, Event Planning ===

* [https://veroandreo.github.io/grass_foss4geu_2024/ Let's combine GRASS, Python and R: Satellite time series data for species distribution modeling]. Workshop by Veronica Andreo. FOSS4G Europe 2024, Tartu.
* [https://veroandreo.github.io/grass-gis-talks/foss4gEU2024.html#/ Status of GRASS GIS project]. Talk by Veronica Andreo. FOSS4G Europe 2024, Tartu.
* [https://veroandreo.github.io/grass-gis-talks/useR2024.html#/ Boost Spatial Data Science Workflows with GRASS GIS and R]. Talk by Veronica Andreo. useR Conference 2024, Salzburg.
* [https://ncsu-geoforall-lab.github.io/usdoi-webinar/notebooks/grass_jupyter.html Geoprocessing with GRASS GIS and Jupyter Notebooks]. Webinar by Corey White. U.S. DOI, August 2024, NCSU.
* [[GRASS Community Meeting Prague 2024]]

* [https://spatial-ecology.net/docs/build/html/COURSESAROUNDTHEWORLD/course_GEO-OPEN-HACK-2024_06_2024.html GEO-OPEN-HACK-2024: Big Geospatial Data Hackathon with Open Infrastructure and Tools] training course delivered ([https://iiasa.ac.at/events/jun-2024/geo-open-hack-2024-big-geospatial-data-hackathon-with-open-infrastructure-and-tools announcement]). The GRASS material has been developed as part of the NSF grant.

* Planning GRASS Dev summit 2025 at NCSU

* Planning AGU (4 abstract submitted), AGU booth for GRASS GIS reserved and payed

* Submitted workshop, talk and keynote to FOSS4G 2024 - Brazil.

=== CMake transition ===
Ongoing work on [https://github.com/OSGeo/grass/pull/3621 CMake compilation] was partially covered by POSE.

=== Code Quality and Security ===

* Code quality improvements in Python code:
** [https://github.com/OSGeo/grass/pull/3763 Flake8 W605 Invalid escape sequence #3763]
** [https://github.com/OSGeo/grass/pull/3926 Flake8 E741 Do not use variables named 'I', 'O', or 'l' in wxGUI code #3926]
** [https://github.com/OSGeo/grass/pull/3928 Flake8 E741 for the rest of code base #3928]
** [https://github.com/OSGeo/grass/pull/4200 grass.temporal: Flake8 F841 Local variable assigned to but never used #4200]
** [https://github.com/OSGeo/grass/pull/4113 grass.pygrass: Remove unused arg in ctypes.CFUNCTYPE #4113]
** [https://github.com/OSGeo/grass/pull/4206 t.rast.to.vect: Fix passing column parameter to r.to.vect, fix flake8 F841 #4206]

* Code quality and security improvements in C and C++ code are in 36 PRs with fixes for more than 25 tools, specifically in:
** raster: r.path, r.out.mpeg, r.out.png, r.in.xyz, r.terraflow, r.statistics, r.spreadpath, r.sim.water, r.sim.erosion, r.object.geometry, r.coin
** imagery: i.atcorr, i.aster.toar, i.ortho.photo, i.landsat.acca, i.segment, i.smap
** display: d.linegraph, d.legend.vect, d.histogram, d.labels
** raster 3D: r3.in.v5d, r3.info, r3.mapcalc
** other: lib/gis, lib/vector/diglib, g.findfile, g.setproj, ps.map, lib/cdhc

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShubhamDesai+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ ShubhamDesai], [https://github.com/OSGeo/grass/pulls?q=author%3Amshukuno+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ Makiko Shukunobe], [https://github.com/OSGeo/grass/pulls?q=author%3Aymdatta+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ ymdatta]

Several reviewers, not supported by the NSF POSE project, played crucial role not only in reviewing, but also in determining the right fixes.

Fixed issues were reported by Flake8, Coverity Scan, and Cppcheck.

=== Tests ===

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShreshth-Malik+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ Shreshth-Malik]

=== Documentation ===

* Veronica Andreo met some GRASS developers and contributors to follow up on tutorials development.
* 7 new [https://github.com/ncsu-geoforall-lab/tutorials tutorials] on time series:
** Management and visualization
** Aggregation
** Algebra
** Accumulation
** Gap filling
** Querying raster time series with vectors
** Subset, import and export
* Tutorial on how to set up Jupyter and GRASS in Windows
* New [https://github.com/OSGeo/grass-tutorials repository] under OSGeo organization to host the upcoming quarto based website for GRASS tutorials
* PR template created - [https://github.com/OSGeo/grass/community GitHub Community Standards] all checked complete

=== Communication and outreach ===

* Creation of 4 news posts in the [https://grass.osgeo.org/news/ GRASS website]
* Social media:
** [https://twitter.com/GRASSGIS Twitter]: 25 new posts
** [https://fosstodon.org/@grassgis Fosstodon]: 25 new posts
* New GRASS GIS LinkedIn page at: [https://www.linkedin.com/company/grass-gis/ https://www.linkedin.com/company/grass-gis/]
* Requested transition of [https://discourse.osgeo.org/t/osgeo-3255-migrate-grass-dev-mailing-list-to-discourse/49796 grass-dev mailing list to discourse.osgeo.org]
* Set up GRASS GIS swag shop on Redbubble

=== Governance ===
* [https://grass.osgeo.org/about/roadmap/ Roadmap] and [https://grass.osgeo.org/about/governance/ Governance] pages added to the website
* PSC elections:
** Documented criteria to define people entitled to vote
** Documented procedure to compile the list of voters
** Elections [https://www.mail-archive.com/grass-user@lists.osgeo.org/msg41102.html announcement] sent out

== Y2 1st quarter report (09/24 - 11/24) ==

=== Presentations and Workshops ===
FOSS4GNA 2024 in St. Louis, Missouri:

* Vaclav Petras. State of GRASS GIS. FOSS4G NA St. Louis, September 9-11, 2024 ([https://wenzeslaus.github.io/grass-gis-talks/foss4gna2024.html slides])
* Huidae Cho. Evolution of GRASS GIS. FOSS4G NA St. Louis, September 9-11, 2024 ([https://htmlpreview.github.io/?https://github.com/HuidaeCho/grass-talks/blob/main/foss4g-na-2024.html slides])
* Huidae Cho. An OpenMP Algorithm for Delineating a Large Number of Watersheds. FOSS4G NA St. Louis, September 9-11, 2024
* Corey T. White. Developing Web-Applications with GRASS GIS. Workshop. FOSS4G NA St. Louis, September 9-11, 2024
* Corey T. White. GRASS GIS as a Geospatial Computational Engine. FOSS4G NA St. Louis, September 9-11, 2024

=== Communication and outreach ===
* Transition of grass-dev mailing list to [https://discourse.osgeo.org/c/grass/developer/61 discourse.osgeo.org] finished.

=== Code Quality and Security ===
* Python code quality issues addressed in more than 70 PRs, reducing the list of per-file ignores by more than 60%.
* Code quality and security improvements in C and C++ code are in more than 80 PRs.
* In total, these changes improve more than 60 tools, specifically:
** raster: r.water.outlet, r.watershed, r.mfilter, r.to.vect, r.in.poly, r.carve, r.thin, r.fill.dir, r.clump, r.in.gridatb, r.out.png, r.in.wms, r.viewshed, r.fillnulls, r.in.srtm, r.in.pdal, r.in.xyz
** vector: v.out.dxf, v.build.polylines, v.external.out, v.net, v.univar, v.in.ascii, v.delaunay, v.hull , v.net.timetable, v.kernel, v.to.db, v.colors, v.rectify, v.reclass, v.generalize, v.transform, v.vol.rst, v.cluster, v.to.3d, v.out.ogr, v.external, v.in.dwg, v.report, v.unpack, v.import
** imagery: i.topo.corr, i.attcorr, i.ortho.photo, i.segment, i.rectify, i.topo.corr, i.panshrapen
** display: d.vect, d.mon, d.frame, d.rast.edit
** other: GUI, grass main executable, g.proj, g.version, db.out.ogr, ps.map, r3.in.v5d, r3.in.v5d, lib/vector/Vlib, lib/ogsf, lib/gis, lib/db, lib/lidar, lib/linkm, grass.temporal, grass.script

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShubhamDesai+is%3Apr+is%3Aclosed+merged%3A2024-09-01..2024-11-30+base%3Amain+sort%3Aupdated-desc+ ShubhamDesai], [https://github.com/OSGeo/grass/pulls?q=author%3Aymdatta+is%3Apr+is%3Aclosed+merged%3A2024-09-01..2024-11-30+base%3Amain+sort%3Aupdated-desc+ ymdatta],
[https://github.com/OSGeo/grass/pulls?q=author%3Aarohanajit+is%3Apr+is%3Aclosed+merged%3A2024-09-01..2024-11-30+base%3Amain+sort%3Aupdated-desc+ Arohan Ajit]

Several reviewers, not supported by the NSF POSE project, played crucial role not only in reviewing, but also in determining the right fixes. The NSF POSE project personnel focused on fixing issues reported by Flake8, Coverity Scan, and Cppcheck, however also Ruff and Pylint are utilized in GRASS GIS thanks to other contributors.

A configure file for Cppcheck is now included in the repository highlighting the level of compliance and aiding contributors in local analysis and subsequent implementation of fixes ([https://github.com/OSGeo/grass/pull/4766 PR #4766]).

Finally, we created a new public GitHub project in the OSGeo GitHub organization for [https://github.com/orgs/OSGeo/projects/11 GRASS GIS Security] to track and communicate progress on the security front with 147 resolved items and 8 in-progress items at the time of writing.

=== Documentation, both Internal and External ===

* To improve indexing of GRASS GIS manual pages, we revised our current sitemap ([https://github.com/OSGeo/grass-website/pull/482 grass-website/pull/482)]), added a updated sitemap to Google Search Console and Bing, fixed robots.txt, and triggered and re-triggered the indexing many times to make Google consume the new content. While before, some searches gave outdated documentation, experimental websites, or unofficial resources only, now the official website and stable documentation is returned as the first search result.
* All older manuals, including version 6.4 and 6.5, are now available (restored) so that search engines can consume them and old links and indices continue to work. They now newly contain the canonical URLs so that search engines understand the structure and don't penalize duplicate content.
* On OSGeo server which hosts GRASS GIS website, we replaced some of the redirects in Apache by local soft links so that URL like grass.osgeo.org/grass-stable stay as is for both humans and machines and don't redirect to specific version (easier to copy-paste from a browser URL bar and easier for search engine to understand what is the page to show).
* We implemented the necessary changes into the cronjobs and did overall updates to enable build of the server-side documentation jobs locally for testing purposes. The most relevant PRs are:
** [https://github.com/OSGeo/grass-addons/pull/1241 Inject canonical URLs into older manual pages (SEO) #1241]
** [https://github.com/OSGeo/grass-addons/pull/1173 Fix red new version box injection and script documentation #1173]
** [https://github.com/OSGeo/grass-addons/pull/1215 Expand script to run stand-alone #1215]
* We advanced the [https://github.com/orgs/OSGeo/projects/9 GRASS Markdown Documentation project].
* New and better wording for intro to imagery tools: [https://github.com/OSGeo/grass/pull/4536 Add intro text to imageryintro.html #4536]
* List of GRASS GIS profiles on different websites is now in an internal PSC document.
* Documentation of all the internal infrastructure, especially that of grass.osgeo.org server, is now in an internal PSC document.
* We painstakingly identified and described all maintenance procedures performed by Markus Neteler in OSGeo SAC capacity for GRASS GIS and as a contributor to GRASS GIS for better work distribution.
* Most of the work on the documentation was done through a contract with Markus Neteler with additional help from Martin Landa for the transition to Markdown.

=== Mentoring Activities ===
Mentors were actively working with 3 mentees.

=== Event Planning and Organizing ===

[[File:Raleigh_2016_11_05.jpg|500px|thumb|right|alt=Rooms, tables and large open space|Smaller space utilized in the past for a local GRASS GIS meetup in Hunt library at NC State University campus (photos are from a [[GRASS GIS Raleigh meetups 2016|2016 meetup]])]]

We are planning and organizing GRASS GIS Developer Summit in Raleigh, NC, USA at North Carolina State University.

* High-demand spaces reserved at NCSU (some since May 2024, other since September 2024).
* A [https://discourse.osgeo.org/t/grass-dev-save-the-date-grass-developer-summit-raleigh-2025/85540 save-the-date post for grass-dev], interest form, and first round of additional invites. (Date established earlier in spring 2024 by NSF POSE team after a survey of PSC members and Core Development Team members.)
* We addressed participant's visa needs based on the responses to the interest form.
* We formed the initial Organizing Committee formed and rough event agenda created.
* Page created: [[GRASS Developer Summit Raleigh 2025]].

== Y2 2nd quarter report (12/24 - 02/25) ==

=== Presentations, Workshops, Event Planning ===

[[File:GRASS GIS booth AGU24.jpg|500px|thumb|right|alt=GRASS GIS booth at AGU24|GRASS GIS booth at AGU24, Washington, DC]]

AGU24 Annual Meeting, Washington, DC, USA:
* GRASS GIS booth in the Exhibit Hall with a banner, new flyers, and a Tangible Landscape setup to demonstrate some of the capabilities of GRASS GIS (Monday afternoon - Thursday morning)
* GRASS GIS for Advanced Earth Systems Analysis and Modeling (eLightning) by Vaclav Petras
* Perspectives from an Open Source Geospatial Modeling Platform Maintainer (poster) by Anna Petrasova
* GRASS GIS Is FAIR: Its Evolution Towards Open Science (poster) by Huidae Cho
* GRASS GIS as a Platform for Dissemination of Reusable Geocomputational Research (poster) by Vaclav Petras

Beyond the GIS Map: Open Source Tools for Geospatial Research, Workshop at the Institute for Social Science Research Arizona State University. 11 December 2024
* Michael Barton and Eunice Villaseñor Iribe, instructors
* Topics
** Introduction to GRASS
** Modeling Terrain in GRASS
** Modeling Movement in GRASS
** Remote Sensing With GRASS

Physically-based hydrologic modeling using GRASS GIS r.topmodel, Workshop at New Mexico State University. January 31, 2025, 1pm-5pm.
* Instructor: Huidae Cho
* Assistant: Nelson Kandel
* Participants: 17
* Topics
** Introduction to GRASS
** Hydrologic Modeling Using GRASS
** Model Calibration and Validation

=== Code Quality and Security ===

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShubhamDesai+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ ShubhamDesai], [https://github.com/OSGeo/grass/pulls?q=author%3Aarohanajit+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ Arohan Ajit]

=== Tests ===

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShreshth-Malik+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ Shreshth-Malik], [https://github.com/OSGeo/grass/pulls?q=author%3Ajayneel-shah18+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ jayneel-shah18]

=== Documentation and Tutorials ===
We finalized and prepared for launch Quarto-based tutorial website editable through GitHub. OSGeo provided a new domain [https://grass-tutorials.osgeo.org/ grass-tutorials.osgeo.org]. Initial set of tutorials were created by Veronica Andreo when she was part of the NSF POSE team (some tutorials will be finalized and released later). Anna Petrasova did the reviews, curation, posts for external tutorials, and transition from list of tutorials at the main website.

We did a major push to create Markdown files in the source code and enable the compilation of documentation for mkdocs. We also configured the mkdocs and revised the Markdown syntax in the files.

=== Communication and outreach ===

Renewed [https://www.youtube.com/@grass-gis Youtube channel @grass-gis] by adding playlists, organizing videos, and updating branding.

=== Governance ===
Submitted application for GRASS GIS to join NumFocus.

=== Event Planning and Organizing ===

* Created draft of schedule, agenda, and budget.
* Identified participants eligible for travel support.
** While the meeting is open to anyone, the NSF-funded travel support is based on priorities set in the NSF POSE project for the Developer Summit.
** Specifically, we are inviting individuals identified based on the following criteria (in this order; moving to the next group if there is still available places):
*** Top 20 contributors to OSGeo/grass in the last two years (2023-2024), but not a bot or NSF POSE personnel (contributing only within NSF POSE). (After exclusions, this is less than 10 people.)
*** PSC member before or after 2024 elections, but not NSF POSE personnel at the time of the meeting. (With PSC members currently contributing code as well, this is only a couple of people after exclusions.)
*** Active participant in one of the mentoring programs. (Participant demonstrated the activity by attending meetings, reporting progress, or submitting code for feedback or review.)
*** Contributors to connections and interfaces prioritized in or during the NSF POSE project:
**** R packages (2 slots for active contributors or maintainers determined by previously established contacts in the given community through their activity on a relevant code base.)
**** GRASS GIS code in QGIS (2 slots for active contributors or maintainers determined by previously established contacts in the given community through their activity on a relevant code base.)
*** Contributors in "write" teams for OSGeo/grass, OSGeo/grass-addons, OSGeo/grass-website, and OSGeo/grass-tutorials repositories. (Almost all fall into one of the above groups.)
*** Contributors to closely related projects, specifically actinia, the GRASS GDAL driver, and the GRASS GeoServer datastore.
* Sent individual invites to participants eligible for travel support. (ongoing)

== Y2 3rd quarter report (03/25 - 05/25) ==

=== Governance ===
* GRASS accepted NumFOCUS (more steps to make it official)

=== Presentations, Workshops, Event Planning ===
* Beyond the GIS Map: Open Source Tools for Geospatial Research, Workshop at the Institute for Social Science Research Arizona State University. 25 March 2025
** Michael Barton and Eunice Villaseñor Iribe, instructors
** Topics: Introduction, Modeling Terrain, Modeling Movement, Remote Sensing with GRASS
* IALE-NA: [https://github.com/ncsu-geoforall-lab/iale-2025-workshop-tl Building Geospatial Models in GRASS: From Python Workflows to Tangible Landscape], April 15th, hosted by the Center for Geospatial Analytics
** Anna Petrasova and Caitlin Haedrich
** 20 participants

* [[GRASS_Developer_Summit_Raleigh_2025]] (see the page for details)

== Y2 4th quarter report (06/25 - 08/25) ==

== Roadmap ==
;Mentoring program (fall 2023 - summer 2025)
:Free developer-oriented mentoring program to support researchers and software developers to integrate GRASS GIS into their workflows and contribute to GRASS GIS.

; Streamline contributor onboarding (spring 2024 - fall 2024)
: Includes updating and creating guidelines for code and non-code contributions.

; Streamline user onboarding (spring 2024 - fall 2024)
: Includes modernizing tool documentation, developing tutorials.
: Creating sample datasets for localized tutorials.
: Developing online training materials for big data processing.

; Training sessions (fall 2023 - summer 2025)
: Local training sessions (at universities and conferences) introducing GRASS GIS to students and researchers.
: Training program for big data processing delivered online.

; Engaging industry partners and user (January 2024 - August 2025)
: Identify and engage industry partners to gather feedback and to start industry partnership program.

; Conferences
: Presence (talks, workshops, networking) at FOSS4GNA 2023, FOSS4G Asia 2023, AGU 2023, CSDMD 2024, FOSS4G Europe 2024, FOSS4G 2024, AGU 2024

; Community sprints
: Virtual or in-person participation in OSGeo community sprints, GRASS GIS community sprints

; Software distribution (January 2024 - May 2025)
: Transition to CMake build system
: Develop conda package

;Simplify maintenance of GRASS integrations with QGIS and R (2024-2025)
: Virtual meetings with QGIS and R developers and GRASS GIS developers (spring 2024).
: Identify and implement improvements to the integration.

;Improve code quality, security, and quality assurance
: Code quality (Flake8, Pylint, Cppcheck), first half of 2024.
: Security (CodeQL), second half of 2024.
: Quality assurance (better pytest integration), second half of 2024.

; In-person developer summit (May 19 - May 24, 2025)
: Hosted by NC State University, Raleigh, NC, USA.
: Identify additional challenges for adoption of GRASS GIS as geoprocessing engine.
: Long-term planning beyond the POSE project.

== Acknowledgements ==

The funding is provided by the U.S. National Science Foundation, award 2303651.
[[File:NSF Official logo.png|frameless|left]]

[[Category: Community]]
[[Category: Conferences‏‎]]
[[Category: 2023]]
[[Category: 2024]]
[[Category: 2025]]

NSF POSE Project 2023-2025 Timeline

2025-06-05T19:52:03Z

Annakrat:

[[File:NSF_grant_announcement.png|500px|right|none]]

To inform GRASS community about the work done as part of the award [https://www.nsf.gov/awardsearch/showAward?AWD_ID=2303651 2303651] from the U.S. National Science Foundation (NSF) to enhance GRASS ecosystem, the following report summarizes the progress and outcomes in quarterly reports and presents the roadmap for the project.

The two main goals of the project are: 1) to facilitate the adoption of GRASS GIS as a key geoprocessing engine by a growing number of researchers and geospatial practitioners in academia, governments, and industry; and 2) to expand and diversify the developer community, especially through supporting next-generation scientists to gain expertise to maintain and innovate GRASS software.

Principal investigators and senior personnel:

* Helena Mitasova, North Carolina State University (Principal Investigator)
* Vaclav Petras, North Carolina State University (Co-Principal Investigator)
* Anna Petrasova, North Carolina State University (Co-Principal Investigator)
* C Michael Barton, Arizona State University (Co-Principal Investigator)
* Huidae Cho, New Mexico State University (Co-Principal Investigator)
* Giuseppe Amatulli, Yale (Senior Personnel)

Other personnel who is joining for the execution of the grant is listed below when relevant.

== Y1 1st quarter report (09/23 - 11/23) ==
=== Project Announcements and Communication ===
* Announcement on [https://grass.osgeo.org/news/2023_09_06_nsf_grant_awarded/ GRASS website].
* Info session to explain the POSE Project ([https://lists.osgeo.org/pipermail/grass-user/2023-September/083423.html Announcement on GRASS user mailing list], 2 sessions for different time zones).
* Collected statistics from GitHub, X and others and set up automated collection for GitHub.

=== Conference Presentations ===
* [https://petrasovaa.github.io/FUTURES-CONUS-talk/foss4gNA2023.html#/ Parallelization Tips for Geoprocessing with GRASS GIS] by Anna Petrasova at FOSS4GNA, October 2023.
* [https://wenzeslaus.github.io/grass-gis-talks/foss4gna2023.html#/ GRASS GIS: Not What You Think] by Vaclav Petras at FOSS4GNA, October 2023.
* [https://docs.google.com/presentation/d/1D-Fh1cLSPINyeXdVaxlakrE9IjB8kK5lIw3D12yX1bk Computational Notebooks for Reproducible Geospatial Computation in Research and Education] by Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/HuidaeCho/grass-gis-talk-foss4g-asia-2023 State of GRASS GIS: 40 Years Strong and Counting] by Huidae Cho at FOSS4G Asia, November 2023.

=== Training and Workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-foss4gna-2023 Unlock the power of GRASS GIS] by Anna Petrasova and Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/develop-tools-with-grass-foss4gna-2023 Develop Geospatial Workflows and Custom Tools with GRASS GIS] by Vaclav Petras and Corey White at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/grass-workshop-gis-week-2023 Big Data Computing with GRASS GIS] by Anna Petrasova and Vaclav Petras at NC State GIS week, November 2023.
* [https://github.com/ncsu-geoforall-lab/grass-gis-on-hpc-henry2/blob/8564c72e9b8929c9ef4d25ada1ef36b569991221/docs/tutorial.md GIS Week Workshop: High Performance Computing for Geospatial Analysis (GRASS GIS part)] by Vaclav Petras (main lecture lead by Andrew Petersen from NCSU OIT) at NC State GIS week, November 2023.
* [https://spatial-ecology.net/docs/build/html/COURSESAROUNDTHEWORLD/course_geocomp_ml_04-05_2024.html Geocomputation and Machine Learning for Environmental Applications] training course [https://spatial-ecology.net/course-geocomputation-machine-learning-for-environmental-applications-intermediate-level-2024/ announced]. GRASS GIS part led by Giuseppe Amatulli is free of charge thanks to the support by NSF.

=== Community Sprint Participation ===
Anna Petrasova and Vaclav Petras remotely participated in [https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2023 OSGeo 2023 code sprint] doing PR reviews and maintenance of GRASS GIS code, documentation, and website.

=== Mentoring Program ===
* Started a development-oriented mentoring program [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ announced] with details available on a [https://grasswiki.osgeo.org/wiki/Mentoring_Program wiki page].
* Program now has 4 participants (from 12 responses) supported by email and video calls.
* Program already resulted in improvements to GRASS GIS core and addons:
** merged PR: [https://github.com/OSGeo/grass/pull/3206 grass.script: ensure memmap content is flushed before writing to a raster]
** radar addon toolset PR: [https://github.com/OSGeo/grass-addons/pull/949 Add i.saocom and i.sar toolsets]
Mentoring Program is a new effort started and so-far performed only by the POSE team.

=== Student Grants Program ===
Student grants [https://grass.osgeo.org/news/2023_11_09_student_grants_announced/ announced] with topics at a [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants wiki page]. Student Grants Program is an existing effort which the POSE team participates in.

=== Working Groups ===

Four [https://grasswiki.osgeo.org/wiki/Working_Groups working groups] created (scope, wiki page, coordinator, and a list of people for each).

=== Citations ===

* GRASS GIS Google Scholar [https://scholar.google.com/citations?user=gJ0ZB0cAAAAJ account] updated with more complete records.
* A [https://forms.gle/cDEvMJu7d6nvxLKn9 form] was created to collect new and missing records.
* Profile link added to GRASS website [https://grass.osgeo.org/contribute/ Contribute] and [https://grass.osgeo.org/about/citation/ Citation] page.

== Y1 2nd quarter report (12/23 - 02/24) ==
=== NSF I-Corps program ===
Corey White, Vaclav Petras, and Anna Petrasova participated in a 4-week long intensive mandatory training that draws on the methods, customer discovery, and curriculum of the [https://new.nsf.gov/funding/initiatives/i-corps NSF Innovation Corps] and applies them to open-source projects.

The program included conducting 70+ 30-minute interviews with both GRASS users and non-users to better shape the future path of GRASS GIS and the POSE project. So far, the interviews focused on educators, companies, researchers, influencers and it focused more on non-users than users.

Next steps, include processing the collected qualitative data, developing possible future directions for sustainability of the project, discussing these with the Project Steering Committee, the core team of developers, and the broader community.

=== Mentoring Program ===
The development oriented [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ mentoring program] welcomed 5 new participants from various institutions including universities, USGS, US Army Corps of Engineers, and local municipalities. The discussed topics covered developing workflows for topography and network analysis, environmental modeling, and geophysics. Participants were supported by email and video calls.

=== Conference Presentations ===
* [https://agu.confex.com/agu/fm23/meetingapp.cgi/Paper/1342418 Modeling vegetated stream buffer impacts on water depth and discharge at the watershed scale with GRASS GIS and Jupyter Notebooks] by Caitlin Haedrich at AGU, December 2023.
* [https://agu.confex.com/agu/fm23/meetingapp.cgi/Paper/1420596 OpenPlains: A Web-Based Platform to Democratize Geospatial Participatory Modeling on the Cloud] by Corey White at AGU, December 2023.

=== Presentations and Workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-vanderbilt-2024 Intro to GRASS GIS] by Vaclav Petras and Anna Petrasova was remotely delivered to geographers at Vanderbilt University in February 2024. The workshop was developed in Jupyter Lab and run using [https://wholetale.org WholeTale] online platform.
* [https://github.com/tomorrownow/intro-to-geoprocessing-workshop Introduction to GRASS GIS Geospatial Processing] by Corey White at [https://smathhacks.ncssm.edu/ SMathHacks hackathon], March 2nd (supported also by Veronica Andreo and Vaclav Petras). SMathHacks is the annual 36-hour hackathon hosted by the NC School of Science and Math, open to all North Carolina students. Students collaborate to build innovative software projects, explore new technologies, and have fun along the way. The workshop was delivered in person with students using [https://colab.research.google.com/ Google Colab].

=== Student Grant Program ===
Linda Karlovska participates in the [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants Student Grant program] with her project [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation Easy command history navigation through the History browser panel] mentored by Anna Petrasova (POSE team) and Martin Landa (FCE CTU). Student Grants Program is an existing effort which the POSE team participates in by mentoring.

=== Code Security ===
Vaclav Petras mentors four students who create code security improvements in their NCSU class ''CSC 472: Cybersecurity Practicum''. So far, the students created two PRs which were successfully merged:
* [https://github.com/OSGeo/grass/pull/3444 grass.script: Change insecure mktemp to NamedTemporaryFile #3444]
* [https://github.com/OSGeo/grass/pull/3451 utils: fixed shell vulnerability in mkrest.py #3451]

Two other PRs are open and more work is underway to do first steps for new approach to a more secure code.

=== Localized Basic Datasets ===
* NCSU and ASU teams worked on localized versions of GRASS basic data set following the [https://grass.osgeo.org/sampledata/north_carolina/nc_basic_spm_grass7.zip North Carolina basic data set example], preparing Flagstaff, Arizona and Nepal draft version with basic layers

== Y1 3rd quarter report (03/24 - 05/24) ==

=== Mentoring Activities ===
The mentoring program form received 2 new responses and mentors were actively working with 3 mentees.
It resulted in fixes in [https://github.com/OSGeo/grass-addons/pull/1042 v.transects] and [https://github.com/OSGeo/grass-addons/pull/1077 r.accumulate].

Linda Kladivova finished her project developing [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation History browser] in the GRASS GUI as part of the GRASS Student Grant Program. Mentor's time was covered by POSE.

GRASS GIS has [https://grass.osgeo.org/news/2024_05_27_gsoc_2024_students/ 3 students this year for Google Summer of Code]. Time spent managing GSoC for GRASS GIS was covered by POSE.

The topics covered by GSoC projects are:
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_EODAG_Support Add EODAG support to GRASS GIS]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Improve_user_experience_in_Jupyter_Notebooks Improve GRASS user experience in Jupyter Notebook]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Add_JSON_output Add JSON output to different GRASS tools in C]

=== Presentations, Workshops, Event Planning ===
* [https://github.com/ncsu-geoforall-lab/tngic-2024 GRASS 101: From GUI Clicks to Writing Scripts (TNGIC 2024)] by Veronica Andreo and Caitlin Haedrich
* [https://github.com/ncsu-geoforall-lab/csdms-grass-2024 Coastal evolution analysis and inundation modeling with GRASS GIS (CSDMS Workshop 2024)] by Caitlin Haedrich and Pratikshya Regmi, see also [https://cnr.ncsu.edu/geospatial/news/2024/06/03/students-teach-grass-gis-for-coastal-hazard-analysis/ blog post with images]

* Organization of [[GRASS Community Meeting Prague 2024]] and budget planning by Vaclav Petras

=== CMake transition ===
Ongoing work on [https://github.com/OSGeo/grass/pull/3621 CMake compilation] was partially covered by POSE.

=== Code Quality and Security ===

Code quality improvements in Python code:
* [https://github.com/OSGeo/grass/pull/3541 PR addressing Flake8 E501] (long lines in 158 files not fixable by automated tools)
* [https://github.com/OSGeo/grass/pull/3535 PR addressing Flake8 E401] (unused imports)

Vaclav Petras mentored a team of four students who create code security improvements in their NCSU class ''CSC 472: Cybersecurity Practicum''. The team created 12 PRs which were successfully merged, 7 additional experimental PRs (not merged) and 2 PRs which are still open at this time. Specifically, the team achieved the following:

* With the involvement and help from the other contributors, the team introduced Bandit and Coverity Scan as additional code scanning tools for Python and C, respectively.
* The team analyzed issues reported CodeQL, Bandit, and Coverity Scan and reported on relevance of different issues to the project (report privately shared with the GRASS Development Team).
* Vulnerability Triage Guide (also privately shared with the GRASS Development Team).
* The team also developed a [https://github.com/OSGeo/grass/security/policy security policy] for the project.
* The vulnerability reporting and security advisories were enabled based on the team recommendations.
* The team fixed several specific security issues in the code:
** [https://github.com/OSGeo/grass/pull/3469 packaging: Use subprocess instead of os.popen for change log creation #3469] (merged)
** [https://github.com/OSGeo/grass/pull/3549 lib raster: fixed security vulnerabilities and weaknesses #3549] (merged)
** [https://github.com/OSGeo/grass/pull/3451 utils: fixed shell vulnerability in mkrest.py #3451] (merged)
** [https://github.com/OSGeo/grass/pull/3444 grass.script: Change insecure mktemp to NamedTemporaryFile #3444] (merged)
** [https://github.com/OSGeo/grass/pull/3551 lib/psdriver: Fix issues with wrong type of arguments to printf #3551] (PR open)
** [https://github.com/OSGeo/grass/pull/3452 g.region/r.to.rast3elev: fixed scanf error to recognize EOF as a possible return value #3452] (PR open)

=== Documentation ===
* Documentation and Education Working Group met and planned the development of new tutorials. Veronica Andreo met other GRASS developers and contributors to coordinate further tutorials development.
* Development of new [https://github.com/ncsu-geoforall-lab/tutorials tutorials] in progress, topics include:
** Getting started with GRASS GIS
** GRASS GIS in Google Colab
** GRASS GIS and Python
** GRASS GIS and R
** GRASS R and Python comparison
** Making plots in GRASS GIS
* New [https://github.com/OSGeo/grass/blob/main/doc/development/style_guide.md GRASS Programming Style Guide]
* [https://github.com/petrasovaa/cookiecutter-grass-addon New addon template powered by Cookiecutter]
* Analysis of options names and functionality in plotting tools:
** [https://github.com/OSGeo/grass-addons/issues/1071 Addons for plotting: Standardize parameters and flags]

=== Communication and outreach ===

* Creation of 4 news post in the [https://grass.osgeo.org/news/ GRASS website]
* Social media:
** [https://twitter.com/GRASSGIS Twitter]: 9 new posts/threads
** [https://fosstodon.org/@grassgis Fosstodon]: 9 new posts/threads

=== Other sustainability activities ===
* [https://github.com/OSGeo/grass/blob/main/CODE_OF_CONDUCT.md Code of Conduct added to the main repository]
* [https://github.com/OSGeo/grass/blob/main/.github/ISSUE_TEMPLATE/bug_report.md revised Issue template]
* New [https://github.com/OSGeo/grass/pull/3673 RFC for a Release Policy]
* Revised [https://github.com/OSGeo/grass/pull/2815 RFC for Release Procedure]
* WIP: GRASS GIS Roadmap
* [https://github.com/OSGeo/grass-website/issues/414 GRASS website: ongoing restructuring]
* [[PSC]] page moved from trac wiki to media wiki

== Y1 4th quarter report (06/24 - 08/24) ==

=== Mentoring Activities ===
The mentoring program form received 3 new responses and mentors were actively working with 3 mentees.
Results include parallelization of r.texture, r.horizon, improved grass.benchmarking library and a new tutorial on lidar data.

GSoC successfully completed their projects:
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_EODAG_Support Add EODAG support to GRASS GIS]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Improve_user_experience_in_Jupyter_Notebooks Improve GRASS user experience in Jupyter Notebook]
* [https://grasswiki.osgeo.org/wiki/GRASS_GSoC_2024_Add_JSON_output Add JSON output to different GRASS tools in C]

Time spent by mentoring was covered by NSF.

=== Presentations, Workshops, Event Planning ===

* [https://veroandreo.github.io/grass_foss4geu_2024/ Let's combine GRASS, Python and R: Satellite time series data for species distribution modeling]. Workshop by Veronica Andreo. FOSS4G Europe 2024, Tartu.
* [https://veroandreo.github.io/grass-gis-talks/foss4gEU2024.html#/ Status of GRASS GIS project]. Talk by Veronica Andreo. FOSS4G Europe 2024, Tartu.
* [https://veroandreo.github.io/grass-gis-talks/useR2024.html#/ Boost Spatial Data Science Workflows with GRASS GIS and R]. Talk by Veronica Andreo. useR Conference 2024, Salzburg.
* [https://ncsu-geoforall-lab.github.io/usdoi-webinar/notebooks/grass_jupyter.html Geoprocessing with GRASS GIS and Jupyter Notebooks]. Webinar by Corey White. U.S. DOI, August 2024, NCSU.
* [[GRASS Community Meeting Prague 2024]]

* [https://spatial-ecology.net/docs/build/html/COURSESAROUNDTHEWORLD/course_GEO-OPEN-HACK-2024_06_2024.html GEO-OPEN-HACK-2024: Big Geospatial Data Hackathon with Open Infrastructure and Tools] training course delivered ([https://iiasa.ac.at/events/jun-2024/geo-open-hack-2024-big-geospatial-data-hackathon-with-open-infrastructure-and-tools announcement]). The GRASS material has been developed as part of the NSF grant.

* Planning GRASS Dev summit 2025 at NCSU

* Planning AGU (4 abstract submitted), AGU booth for GRASS GIS reserved and payed

* Submitted workshop, talk and keynote to FOSS4G 2024 - Brazil.

=== CMake transition ===
Ongoing work on [https://github.com/OSGeo/grass/pull/3621 CMake compilation] was partially covered by POSE.

=== Code Quality and Security ===

* Code quality improvements in Python code:
** [https://github.com/OSGeo/grass/pull/3763 Flake8 W605 Invalid escape sequence #3763]
** [https://github.com/OSGeo/grass/pull/3926 Flake8 E741 Do not use variables named 'I', 'O', or 'l' in wxGUI code #3926]
** [https://github.com/OSGeo/grass/pull/3928 Flake8 E741 for the rest of code base #3928]
** [https://github.com/OSGeo/grass/pull/4200 grass.temporal: Flake8 F841 Local variable assigned to but never used #4200]
** [https://github.com/OSGeo/grass/pull/4113 grass.pygrass: Remove unused arg in ctypes.CFUNCTYPE #4113]
** [https://github.com/OSGeo/grass/pull/4206 t.rast.to.vect: Fix passing column parameter to r.to.vect, fix flake8 F841 #4206]

* Code quality and security improvements in C and C++ code are in 36 PRs with fixes for more than 25 tools, specifically in:
** raster: r.path, r.out.mpeg, r.out.png, r.in.xyz, r.terraflow, r.statistics, r.spreadpath, r.sim.water, r.sim.erosion, r.object.geometry, r.coin
** imagery: i.atcorr, i.aster.toar, i.ortho.photo, i.landsat.acca, i.segment, i.smap
** display: d.linegraph, d.legend.vect, d.histogram, d.labels
** raster 3D: r3.in.v5d, r3.info, r3.mapcalc
** other: lib/gis, lib/vector/diglib, g.findfile, g.setproj, ps.map, lib/cdhc

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShubhamDesai+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ ShubhamDesai], [https://github.com/OSGeo/grass/pulls?q=author%3Amshukuno+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ Makiko Shukunobe], [https://github.com/OSGeo/grass/pulls?q=author%3Aymdatta+is%3Apr+is%3Aclosed+merged%3A2024-06-01..2024-08-31+base%3Amain+sort%3Aupdated-desc+ ymdatta]

Several reviewers, not supported by the NSF POSE project, played crucial role not only in reviewing, but also in determining the right fixes.

Fixed issues were reported by Flake8, Coverity Scan, and Cppcheck.

=== Tests ===

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShreshth-Malik+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ Shreshth-Malik]

=== Documentation ===

* Veronica Andreo met some GRASS developers and contributors to follow up on tutorials development.
* 7 new [https://github.com/ncsu-geoforall-lab/tutorials tutorials] on time series:
** Management and visualization
** Aggregation
** Algebra
** Accumulation
** Gap filling
** Querying raster time series with vectors
** Subset, import and export
* Tutorial on how to set up Jupyter and GRASS in Windows
* New [https://github.com/OSGeo/grass-tutorials repository] under OSGeo organization to host the upcoming quarto based website for GRASS tutorials
* PR template created - [https://github.com/OSGeo/grass/community GitHub Community Standards] all checked complete

=== Communication and outreach ===

* Creation of 4 news posts in the [https://grass.osgeo.org/news/ GRASS website]
* Social media:
** [https://twitter.com/GRASSGIS Twitter]: 25 new posts
** [https://fosstodon.org/@grassgis Fosstodon]: 25 new posts
* New GRASS GIS LinkedIn page at: [https://www.linkedin.com/company/grass-gis/ https://www.linkedin.com/company/grass-gis/]
* Requested transition of [https://discourse.osgeo.org/t/osgeo-3255-migrate-grass-dev-mailing-list-to-discourse/49796 grass-dev mailing list to discourse.osgeo.org]
* Set up GRASS GIS swag shop on Redbubble

=== Governance ===
* [https://grass.osgeo.org/about/roadmap/ Roadmap] and [https://grass.osgeo.org/about/governance/ Governance] pages added to the website
* PSC elections:
** Documented criteria to define people entitled to vote
** Documented procedure to compile the list of voters
** Elections [https://www.mail-archive.com/grass-user@lists.osgeo.org/msg41102.html announcement] sent out

== Y2 1st quarter report (09/24 - 11/24) ==

=== Presentations and Workshops ===
FOSS4GNA 2024 in St. Louis, Missouri:

* Vaclav Petras. State of GRASS GIS. FOSS4G NA St. Louis, September 9-11, 2024 ([https://wenzeslaus.github.io/grass-gis-talks/foss4gna2024.html slides])
* Huidae Cho. Evolution of GRASS GIS. FOSS4G NA St. Louis, September 9-11, 2024 ([https://htmlpreview.github.io/?https://github.com/HuidaeCho/grass-talks/blob/main/foss4g-na-2024.html slides])
* Huidae Cho. An OpenMP Algorithm for Delineating a Large Number of Watersheds. FOSS4G NA St. Louis, September 9-11, 2024
* Corey T. White. Developing Web-Applications with GRASS GIS. Workshop. FOSS4G NA St. Louis, September 9-11, 2024
* Corey T. White. GRASS GIS as a Geospatial Computational Engine. FOSS4G NA St. Louis, September 9-11, 2024

=== Communication and outreach ===
* Transition of grass-dev mailing list to [https://discourse.osgeo.org/c/grass/developer/61 discourse.osgeo.org] finished.

=== Code Quality and Security ===
* Python code quality issues addressed in more than 70 PRs, reducing the list of per-file ignores by more than 60%.
* Code quality and security improvements in C and C++ code are in more than 80 PRs.
* In total, these changes improve more than 60 tools, specifically:
** raster: r.water.outlet, r.watershed, r.mfilter, r.to.vect, r.in.poly, r.carve, r.thin, r.fill.dir, r.clump, r.in.gridatb, r.out.png, r.in.wms, r.viewshed, r.fillnulls, r.in.srtm, r.in.pdal, r.in.xyz
** vector: v.out.dxf, v.build.polylines, v.external.out, v.net, v.univar, v.in.ascii, v.delaunay, v.hull , v.net.timetable, v.kernel, v.to.db, v.colors, v.rectify, v.reclass, v.generalize, v.transform, v.vol.rst, v.cluster, v.to.3d, v.out.ogr, v.external, v.in.dwg, v.report, v.unpack, v.import
** imagery: i.topo.corr, i.attcorr, i.ortho.photo, i.segment, i.rectify, i.topo.corr, i.panshrapen
** display: d.vect, d.mon, d.frame, d.rast.edit
** other: GUI, grass main executable, g.proj, g.version, db.out.ogr, ps.map, r3.in.v5d, r3.in.v5d, lib/vector/Vlib, lib/ogsf, lib/gis, lib/db, lib/lidar, lib/linkm, grass.temporal, grass.script

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShubhamDesai+is%3Apr+is%3Aclosed+merged%3A2024-09-01..2024-11-30+base%3Amain+sort%3Aupdated-desc+ ShubhamDesai], [https://github.com/OSGeo/grass/pulls?q=author%3Aymdatta+is%3Apr+is%3Aclosed+merged%3A2024-09-01..2024-11-30+base%3Amain+sort%3Aupdated-desc+ ymdatta],
[https://github.com/OSGeo/grass/pulls?q=author%3Aarohanajit+is%3Apr+is%3Aclosed+merged%3A2024-09-01..2024-11-30+base%3Amain+sort%3Aupdated-desc+ Arohan Ajit]

Several reviewers, not supported by the NSF POSE project, played crucial role not only in reviewing, but also in determining the right fixes. The NSF POSE project personnel focused on fixing issues reported by Flake8, Coverity Scan, and Cppcheck, however also Ruff and Pylint are utilized in GRASS GIS thanks to other contributors.

A configure file for Cppcheck is now included in the repository highlighting the level of compliance and aiding contributors in local analysis and subsequent implementation of fixes ([https://github.com/OSGeo/grass/pull/4766 PR #4766]).

Finally, we created a new public GitHub project in the OSGeo GitHub organization for [https://github.com/orgs/OSGeo/projects/11 GRASS GIS Security] to track and communicate progress on the security front with 147 resolved items and 8 in-progress items at the time of writing.

=== Documentation, both Internal and External ===

* To improve indexing of GRASS GIS manual pages, we revised our current sitemap ([https://github.com/OSGeo/grass-website/pull/482 grass-website/pull/482)]), added a updated sitemap to Google Search Console and Bing, fixed robots.txt, and triggered and re-triggered the indexing many times to make Google consume the new content. While before, some searches gave outdated documentation, experimental websites, or unofficial resources only, now the official website and stable documentation is returned as the first search result.
* All older manuals, including version 6.4 and 6.5, are now available (restored) so that search engines can consume them and old links and indices continue to work. They now newly contain the canonical URLs so that search engines understand the structure and don't penalize duplicate content.
* On OSGeo server which hosts GRASS GIS website, we replaced some of the redirects in Apache by local soft links so that URL like grass.osgeo.org/grass-stable stay as is for both humans and machines and don't redirect to specific version (easier to copy-paste from a browser URL bar and easier for search engine to understand what is the page to show).
* We implemented the necessary changes into the cronjobs and did overall updates to enable build of the server-side documentation jobs locally for testing purposes. The most relevant PRs are:
** [https://github.com/OSGeo/grass-addons/pull/1241 Inject canonical URLs into older manual pages (SEO) #1241]
** [https://github.com/OSGeo/grass-addons/pull/1173 Fix red new version box injection and script documentation #1173]
** [https://github.com/OSGeo/grass-addons/pull/1215 Expand script to run stand-alone #1215]
* We advanced the [https://github.com/orgs/OSGeo/projects/9 GRASS Markdown Documentation project].
* New and better wording for intro to imagery tools: [https://github.com/OSGeo/grass/pull/4536 Add intro text to imageryintro.html #4536]
* List of GRASS GIS profiles on different websites is now in an internal PSC document.
* Documentation of all the internal infrastructure, especially that of grass.osgeo.org server, is now in an internal PSC document.
* We painstakingly identified and described all maintenance procedures performed by Markus Neteler in OSGeo SAC capacity for GRASS GIS and as a contributor to GRASS GIS for better work distribution.
* Most of the work on the documentation was done through a contract with Markus Neteler with additional help from Martin Landa for the transition to Markdown.

=== Mentoring Activities ===
Mentors were actively working with 3 mentees.

=== Event Planning and Organizing ===

[[File:Raleigh_2016_11_05.jpg|500px|thumb|right|alt=Rooms, tables and large open space|Smaller space utilized in the past for a local GRASS GIS meetup in Hunt library at NC State University campus (photos are from a [[GRASS GIS Raleigh meetups 2016|2016 meetup]])]]

We are planning and organizing GRASS GIS Developer Summit in Raleigh, NC, USA at North Carolina State University.

* High-demand spaces reserved at NCSU (some since May 2024, other since September 2024).
* A [https://discourse.osgeo.org/t/grass-dev-save-the-date-grass-developer-summit-raleigh-2025/85540 save-the-date post for grass-dev], interest form, and first round of additional invites. (Date established earlier in spring 2024 by NSF POSE team after a survey of PSC members and Core Development Team members.)
* We addressed participant's visa needs based on the responses to the interest form.
* We formed the initial Organizing Committee formed and rough event agenda created.
* Page created: [[GRASS Developer Summit Raleigh 2025]].

== Y2 2nd quarter report (12/24 - 02/25) ==

=== Presentations, Workshops, Event Planning ===

[[File:GRASS GIS booth AGU24.jpg|500px|thumb|right|alt=GRASS GIS booth at AGU24|GRASS GIS booth at AGU24, Washington, DC]]

AGU24 Annual Meeting, Washington, DC, USA:
* GRASS GIS booth in the Exhibit Hall with a banner, new flyers, and a Tangible Landscape setup to demonstrate some of the capabilities of GRASS GIS (Monday afternoon - Thursday morning)
* GRASS GIS for Advanced Earth Systems Analysis and Modeling (eLightning) by Vaclav Petras
* Perspectives from an Open Source Geospatial Modeling Platform Maintainer (poster) by Anna Petrasova
* GRASS GIS Is FAIR: Its Evolution Towards Open Science (poster) by Huidae Cho
* GRASS GIS as a Platform for Dissemination of Reusable Geocomputational Research (poster) by Vaclav Petras

Beyond the GIS Map: Open Source Tools for Geospatial Research, Workshop at the Institute for Social Science Research Arizona State University. 11 December 2024
* Michael Barton and Eunice Villaseñor Iribe, instructors
* Topics
** Introduction to GRASS
** Modeling Terrain in GRASS
** Modeling Movement in GRASS
** Remote Sensing With GRASS

Physically-based hydrologic modeling using GRASS GIS r.topmodel, Workshop at New Mexico State University. January 31, 2025, 1pm-5pm.
* Instructor: Huidae Cho
* Assistant: Nelson Kandel
* Participants: 17
* Topics
** Introduction to GRASS
** Hydrologic Modeling Using GRASS
** Model Calibration and Validation

=== Code Quality and Security ===

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShubhamDesai+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ ShubhamDesai], [https://github.com/OSGeo/grass/pulls?q=author%3Aarohanajit+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ Arohan Ajit]

=== Tests ===

Changes by author: [https://github.com/OSGeo/grass/pulls?q=author%3AShreshth-Malik+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ Shreshth-Malik], [https://github.com/OSGeo/grass/pulls?q=author%3Ajayneel-shah18+is%3Apr+is%3Aclosed+merged%3A2024-12-01..2025-02-28+base%3Amain+sort%3Aupdated-desc+ jayneel-shah18]

=== Documentation and Tutorials ===
We finalized and prepared for launch Quarto-based tutorial website editable through GitHub. OSGeo provided a new domain [https://grass-tutorials.osgeo.org/ grass-tutorials.osgeo.org]. Initial set of tutorials were created by Veronica Andreo when she was part of the NSF POSE team (some tutorials will be finalized and released later). Anna Petrasova did the reviews, curation, posts for external tutorials, and transition from list of tutorials at the main website.

We did a major push to create Markdown files in the source code and enable the compilation of documentation for mkdocs. We also configured the mkdocs and revised the Markdown syntax in the files.

=== Communication and outreach ===

Renewed [https://www.youtube.com/@grass-gis Youtube channel @grass-gis] by adding playlists, organizing videos, and updating branding.

=== Governance ===
Submitted application for GRASS GIS to join NumFocus.

=== Event Planning and Organizing ===

* Created draft of schedule, agenda, and budget.
* Identified participants eligible for travel support.
** While the meeting is open to anyone, the NSF-funded travel support is based on priorities set in the NSF POSE project for the Developer Summit.
** Specifically, we are inviting individuals identified based on the following criteria (in this order; moving to the next group if there is still available places):
*** Top 20 contributors to OSGeo/grass in the last two years (2023-2024), but not a bot or NSF POSE personnel (contributing only within NSF POSE). (After exclusions, this is less than 10 people.)
*** PSC member before or after 2024 elections, but not NSF POSE personnel at the time of the meeting. (With PSC members currently contributing code as well, this is only a couple of people after exclusions.)
*** Active participant in one of the mentoring programs. (Participant demonstrated the activity by attending meetings, reporting progress, or submitting code for feedback or review.)
*** Contributors to connections and interfaces prioritized in or during the NSF POSE project:
**** R packages (2 slots for active contributors or maintainers determined by previously established contacts in the given community through their activity on a relevant code base.)
**** GRASS GIS code in QGIS (2 slots for active contributors or maintainers determined by previously established contacts in the given community through their activity on a relevant code base.)
*** Contributors in "write" teams for OSGeo/grass, OSGeo/grass-addons, OSGeo/grass-website, and OSGeo/grass-tutorials repositories. (Almost all fall into one of the above groups.)
*** Contributors to closely related projects, specifically actinia, the GRASS GDAL driver, and the GRASS GeoServer datastore.
* Sent individual invites to participants eligible for travel support. (ongoing)

== Y2 3rd quarter report (03/25 - 05/25) ==
* [[GRASS_Developer_Summit_Raleigh_2025]]

== Y2 4th quarter report (06/25 - 08/25) ==

=== Governance ===
* GRASS accepted NumFOCUS (more steps to make it official)

=== Presentations, Workshops, Event Planning ===
* Beyond the GIS Map: Open Source Tools for Geospatial Research, Workshop at the Institute for Social Science Research Arizona State University. 25 March 2025
** Michael Barton and Eunice Villaseñor Iribe, instructors
** Topics: Introduction, Modeling Terrain, Modeling Movement, Remote Sensing with GRASS
* IALE-NA: [https://github.com/ncsu-geoforall-lab/iale-2025-workshop-tl Building Geospatial Models in GRASS: From Python Workflows to Tangible Landscape], April 15th, hosted by the Center for Geospatial Analytics
** Anna Petrasova and Caitlin Haedrich
** 20 participants

== Roadmap ==
;Mentoring program (fall 2023 - summer 2025)
:Free developer-oriented mentoring program to support researchers and software developers to integrate GRASS GIS into their workflows and contribute to GRASS GIS.

; Streamline contributor onboarding (spring 2024 - fall 2024)
: Includes updating and creating guidelines for code and non-code contributions.

; Streamline user onboarding (spring 2024 - fall 2024)
: Includes modernizing tool documentation, developing tutorials.
: Creating sample datasets for localized tutorials.
: Developing online training materials for big data processing.

; Training sessions (fall 2023 - summer 2025)
: Local training sessions (at universities and conferences) introducing GRASS GIS to students and researchers.
: Training program for big data processing delivered online.

; Engaging industry partners and user (January 2024 - August 2025)
: Identify and engage industry partners to gather feedback and to start industry partnership program.

; Conferences
: Presence (talks, workshops, networking) at FOSS4GNA 2023, FOSS4G Asia 2023, AGU 2023, CSDMD 2024, FOSS4G Europe 2024, FOSS4G 2024, AGU 2024

; Community sprints
: Virtual or in-person participation in OSGeo community sprints, GRASS GIS community sprints

; Software distribution (January 2024 - May 2025)
: Transition to CMake build system
: Develop conda package

;Simplify maintenance of GRASS integrations with QGIS and R (2024-2025)
: Virtual meetings with QGIS and R developers and GRASS GIS developers (spring 2024).
: Identify and implement improvements to the integration.

;Improve code quality, security, and quality assurance
: Code quality (Flake8, Pylint, Cppcheck), first half of 2024.
: Security (CodeQL), second half of 2024.
: Quality assurance (better pytest integration), second half of 2024.

; In-person developer summit (May 19 - May 24, 2025)
: Hosted by NC State University, Raleigh, NC, USA.
: Identify additional challenges for adoption of GRASS GIS as geoprocessing engine.
: Long-term planning beyond the POSE project.

== Acknowledgements ==

The funding is provided by the U.S. National Science Foundation, award 2303651.
[[File:NSF Official logo.png|frameless|left]]

[[Category: Community]]
[[Category: Conferences‏‎]]
[[Category: 2023]]
[[Category: 2024]]
[[Category: 2025]]

Talk:GRASS Developer Summit Raleigh 2025

2025-05-24T03:04:33Z

Annakrat: /* Anna Petrasova | NC State University */

{{toc|right}}

Quick links: [[GRASS Developer Summit Raleigh 2025|Meeting page]] | [[#Participant_reports|Reports]] | [[GRASS_Developer_Summit_Raleigh_2025#Sponsors|Sponsors]]

== Organizing Team ==

* Initial planning: Vaclav Petras, Anna Petrasova, Veronica Andreo, Corey White, Lois Utt, Sarah White, Doug Newcomb, Huidae Cho, Veronica Andreo ([[GRASS_Developer_Summit_Raleigh_2025#Organizing_Committee|Organizing Committee]])
* Budget: Vaclav Petras, Lois Utt, Anna Petrasova
* Raising support: Helena Mitasova, Vaclav Petras, Anna Petrasova, Michael Barton, Giuseppe Amatulli ([[NSF POSE Project 2023-2025 Timeline|NSF POSE project]] proposal authors)
* Travel: Lois Utt
* Venue: Vaclav Petras, Lois Utt
* Meals: Lois Utt, Sarah White, Vaclav Petras, Corey White, Anna Petrasova
* Agenda: Vaclav Petras, Huidae Cho, Anna Petrasova
* Wiki page: Vaclav Petras, Anna Petrasova
* Swag: Sarah White, Vaclav Petras, Anna Petrasova, Corey White
* Promotion, invitations, and social media: Vaclav Petras, Sarah White, Corey White, John Vogler
* Lightning talks organization: Vaclav Petras, Zachary Arcaro, John Vogler
* Lightning talk speakers: Vaclav Petras (welcome), Markus Metz and Markus Neteler (talk presented by Vaclav Petras), Anna Petrasova, Veronica Andreo, Robert Dzur, Nick Brady, Huidae Cho, Gregory Power, Doug Newcomb, Caitlin Haedrich
* Photography: Caitlin Haedrich, Māris Nartišs, Pratikshya Regmi
* Portrait photography: Riya, Caitlin Haedrich, Natalie Trso

== Detailed Schedule ==

=== Day 1, Monday, May 19 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Contributing to GRASS. Getting started. Is it easy to contribute?''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-9:00 || Breakfast || Catered breakfast on site. Meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || What to expect from the event, contributing to GRASS using Git and GitHub, making your first contribution.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || i.hyper: Integrating Hyperspectral Imagery Processing into GRASS - Alen Mangafić
|-
| 11:20-11:40 || Self-organized feedback sessions ||
|-
| 11:40-12:00 || Self-organized feedback sessions || Project Image - Vaclav Petras
|-
| 12:00-13:00 || Lunch || Catered food on site.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || We will walk to [https://www.trophybrewing.com/brewing-pizza Trophy Brewing & Pizza] ([https://maps.app.goo.gl/ggnZ7EvXbWqDUmvP9 directions], 30 min walk from Talley)
|}

=== Day 2, Tuesday, May 20 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topics: ''Hydrology and Interfacing with R and QGIS (gathering user feedback, testing, discussing with developers, developing action items)''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-9:00 || Breakfast || Breakfast on site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Introduction to writing GRASS tools, program for the day.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || fasterRaster R package - Adam Smith
|-
| 11:20-11:40 || Self-organized feedback sessions || Hydography90m + Geocomputation Courses - Giuseppe
|-
| 11:40-12:00 || Self-organized feedback sessions || Flood modelling with grass and itzi ([https://itzi.org]) - Laurent Courty
|-
| 12:00-13:00 || Lunch || [https://maps.app.goo.gl/womSkce9DrE8CTnR8 Case dining hall]
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/CQiWoCAQNt1ymZkb7 Served in Jordan Hall at the Center for Geospatial Analytics], evaluate the day's accomplishments, plan and prioritize for the next few days.
|}

=== Day 3, Wednesday, May 21 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Non-coding contributions, natural language translation, and internationalization.''

{| class="wikitable"
! Time !! Slot !!
|-
| 7:00-9:00 || Breakfast || [https://maps.app.goo.gl/eZ8VK8Mx6TjMt9NP8 Case dining hall]
|-
| 9:00-10:00 || Morning opening sessions || Introduction to non-coding contributions, tutorials, contributing examples, natural language translation and internationalization (procedures, glossaries, code customization, translation).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Easier access to GRASS tools - Vaclav Petras
|-
| 11:20-11:40 || Self-organized feedback sessions ||
|-
| 11:40-12:00 || Self-organized feedback sessions || GRASS backend for xarray and temporal framework global variables ([https://github.com/OSGeo/grass/issues/629]) - Laurent Courty
|-
| 12:00-13:00 || Lunch || Served on site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/1E39eySMVaxYJUUS8 Picnic at Pullen Park, shelter #3. In case of bad weather, dinner at the Center for Geospatial Analytics.
|}

=== Day 4, Thursday, May 22 ===

Location: Center for Geospatial Analytics, Jordan Hall, 2800 Faucette Drive ([https://www.google.com/maps/search/Jordan+Hall/@35.7816832,-78.6772765,18z/data=!3m1!4b1?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: 5103 (straight from the two elevators, at the end of the hallway)

Highlighted topic: ''Project vision and computational engine use case.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || On site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Project vision and the computational engine use case (missing features, documentation, user groups).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || NSF POSE I-Corps Interviews - Corey White
|-
| 11:20-11:40 || Self-organized feedback session || YAIT - Yet Another Interface to Tools - Vaclav Petras
|-
| 11:40-12:00 || Self-organized feedback session || Modernizing Color Tables (Brendan)
|-
| 12:00-13:00 || Lunch || On site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-16:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 16:00-17:00 || Lightning talks || Fast-paced talks, showcasing applications of GRASS, room 5111.
|-
| 18:00 || Reception || Connect with researchers, government professionals, and industry collaborators, rooms 5111 and 5119.
|}

=== Day 5, Friday, May 23 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topic: ''GRASS project's future course.''

{| class="wikitable"
! Time !! Slot !!
|-
| 7:45-8:15 || Breakfast || '''Hotel Aloft (2nd floor).''' Search for Lois!
|-
| 9:00-10:00 || Morning opening sessions || GRASS project's future course.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-12:00 || PSC meeting || Project Steering Committee meets (public).
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Rescheduled for Saturday

|-
| 12:00-13:00 || Lunch || Walk to [https://maps.app.goo.gl/kHVHY62QxTd6wHKd9 On the Oval Culinary Creations]. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || Dinner on your own. Corey White will organize trip to downtown. Bus 41 from Hunt library to hotel and then walk.
|}

=== Day 6, Saturday, May 24 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

'''Take bus 41 at 8.30 from Aloft.'''

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topics: ''NSF POSE project evaluation.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-10:00 || Breakfast || We will have breakfast (yogurt, granola, pastries) at [https://maps.app.goo.gl/EwzNxeovv4rTivjK9 Lake Raleigh]. Feel free to bring your own coffee.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || GRASS tools: core and additional functionality (MartinL)
|-
| 12:00-13:00 || Lunch || Pizza. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || Player's Retreat.
|}

== Daily tasks for participants ==

* List all the things you are working on in the Participant reports section below. Update the list each day. Include things you work on with other people.
* If you want to discuss something with the whole group, add yourself to a Self-organized feedback sessions slot in the schedule above or tell Vaclav (Vashek) Petras.
* For people with triage access and above: If you are or will be working on an issue or on a PR which is not originally submitted by you, assign yourself to the issue or PR. (You can unassign yourself later if you change your mind.)

== Participant reports ==

Per-person reports from the meeting.

=== Giuseppe Amatulli | Yale University ===

* Testing r.watershed and r.stream.* for handling large datasets
* Running r.flowaccumulation at global level using water direction from hydrography90m
* Preparing the grass tutorial material for the https://www.geomorphometry2025.org/ conference

=== Veronica Andreo | CONICET - Instituto Gulich ===

* [https://github.com/veroandreo?tab=overview&from=2025-05-12&to=2025-05-24 GitHub contributions]
* Enhanced the website footer.
* Sync icons on the Tutorials website footer to those on the main website.
* Fix descriptions and their display on the tutorials website.
* Fix GRASS page on OSGeo website [https://www.osgeo.org/projects/grass-gis/]
** Changed logo, removed GIS from the name, fixed old links.
* Social media posts.
* Discussion about hyperspectral with Alen and Anna.
* Expand the GRASS acronym on the home page.
* Remove GIS from GRASS name on the website.
* Review tutorials by Huidae and Adam Smith.
* Add external tutorials by Huidae and the one from FOSS4G 2024.
* Started adding the time series tutorials.
* Add lightbox class in get-started tutorials so images can be clicked on.
* GRASS PSC admin stuff.
* Participated of the PSC meeting.
* Talk to Tonis Kardi from FOSS4G EU LOC to have a "State of GRASS" talk in the program. Alen will be presenting.
* Gave a lightning talk: GRASS-fed species distribution models.
* Discussed with Corey and Mimi about tutorials.

=== Abdullah Azzam | New Mexico State University ===

* Created first PR; fixed broken links on the website [https://github.com/OSGeo/grass-website/pull/538 #538]
* Pushed a new GRASS Addon ''r.curvenumber'' [https://github.com/OSGeo/grass-addons/pull/1403 #1403]

=== Michael Barton | Arizona State University ===

* POSE related activities

=== Laura Belica | NC State University ===

* have been working on developing a workflow-tool tutorial template that facilitates GRASS learners who tend to 'jump in' or have a 'choose your own adventure' approach to learning GRASS (i.e., want to use their data for their study area for their objective from the start). The structure of the tutorial template is a concise, basic, general description/instructions of the workflow with optional links to pertinent explanatory/deeper dive content (e.g., plain language explainers of the tool, options, defaults, etc.) in a variety of formats (e.g., captioned images, short tool demo videos (30 sec to 2 min)) in addition to the more comprehensive resources available (e.g. documentation, examples, tutorials). The main motivation for this approach is to help new and occasional GRASS users avoid some of the common pitfalls and to learn how to find workarounds for some of the unanticipated challenges they may encounter with their specific datasets or use cases so that they can learn as they go. Another motivation for this approach is to facilitate the translation, extension, and updating of workflow tutorials by the community over time (e.g., providing audio and closed captioning for one of the tool-demo videos in another language, replacing an outdated GUI demo with one for the current release, or incorporating a new add-on as an option in the workflow).

* my focus this week is on developing a draft/test tutorial (in Quarto) for a standard hydrological modelling workflow that begins with the crucial pre-work of how to figure out the appropriate project/location, etc. as well as considerations of some of the downstream impacts of resolution, extent, region etc. It may not be ready for sharing by the end of the week, but suggestions and advice are welcomed in advance.

19 May
* discussed a novice user issue with 'moving' vector data from one location to another with Vero and learned a neat GUI option
* revised and added workflow tutorial text

=== Shonil Sateesh Bhide | NC State University ===

* CI optimization

=== Huidae Cho | New Mexico State University ===

* CMake, conda, CI, Mentoring

Monday 5/19
* [https://github.com/OSGeo/grass/pull/5680 CMake: Recognize conda installation path at runtime]: Replaced by [https://github.com/HuidaeCho/grass-conda/blob/master/recipe/post-link.sh conda post-link.sh]
* CMake and Conda Testing on Linux
* CMake Testing on Windows
* Mentoring: Chung-Yuan, Abdullah

Tuesday 5/20
* [https://github.com/OSGeo/grass/pull/5712 CMake: Define custom complex types for MSVC LAPACKE]
* [https://github.com/OSGeo/grass/pull/5713 CMake: Fix build output directories for MSVC]
* CMake and Conda Testing on Linux
* CMake Testing on Windows

Wednesday 5/21
* Translation Talk
* Translation Discussion with Edouard
* Flow Direction Meeting with Ondrej, Ondrej's Student, Martin, and Markus Metz
* CMake and Conda Testing on Linux
* CMake Testing on Windows
* Mentoring: Chung-Yuan, Abdullah

Thursday 5/22
* [https://github.com/OSGeo/grass/pull/5740 CMake: Fix the parameter is incorrect: . error for MSVC]
* Lightning Talk
* CMake and Conda Testing on Linux
* CMake Testing on Windows
* CI: Discussion with Edouard
* Mentoring: Chung-Yuan, Abdullah

=== Edouard Choinière ===

* Quick ideas, way too much for a week: Helping others (may take a reasonable part of the time), managing CI, setting up localization template updating workflow, backporting tool? Pytest/coverage improvements? Discuss and design other projects, to work on during the year. Open to change on other priorities once there, anything that is useful. Maybe make a little progress on high dpi GUI, especially on Windows.

* Weekend before sprint:
** Clear up Renovate PRs to not use CI time during the sprint, reviewing and merging: [https://github.com/OSGeo/grass/pull/5664 #5664], [https://github.com/OSGeo/grass/pull/5665 #5665], [https://github.com/OSGeo/grass/pull/5666 #5666], [https://github.com/OSGeo/grass/pull/5667 #5667], [https://github.com/OSGeo/grass/pull/5668 #5668]
** PR to avoid some CI run time for the sprint: [https://github.com/OSGeo/grass/pull/5670 #5670]
** Reviewed open PRs for PRs that were mergeable before the sprint, updated outdated PRs to avoid having it needing CI time during sprint. Only ended up merging [https://github.com/OSGeo/grass/pull/5658 #5658], but another reviewed one that might still need changes: [https://github.com/OSGeo/grass/pull/5628 #5628]
* Monday May 19, 2025:
** PR got merged: [https://github.com/OSGeo/grass/pull/5670 #5670],[https://github.com/OSGeo/grass/pull/5550 #5550]
** Reviewed PRs: [https://github.com/OSGeo/grass/pull/5671 #5671], [https://github.com/OSGeo/grass/pull/5672 #5672]
** Discussions:
*** Shonil Sateesh Bhid & Shuham on their CI & pytest work and project.
*** Māris Nartišs about a potential issue and improvement for it. Will be discussed in the security reporting tab, also allowing to test the security vulnerability reporting process. + Research on existing solutions
** Reviewed: [https://github.com/OSGeo/grass/pull/5682 #5682], [https://github.com/OSGeo/grass/pull/5660 #5660],
** Reviewed, edited and merged: [https://github.com/OSGeo/grass/pull/3672 #3672]
** Discussed/helped user for: [https://github.com/OSGeo/grass/pull/5678 #5678] and [https://github.com/OSGeo/grass/pull/5684 #5684]
** Long discussion and vision planning for windows scripting with Vaclav, concerning [https://github.com/OSGeo/grass/pull/5624 #5624]. Tested alternatives and tried the consequences of that PR. This older PR finally got merged.
** Created PRs for NSIS installer: [https://github.com/OSGeo/grass/pull/5685 #5685] and also [https://github.com/OSGeo/grass/pull/5686 #5686], which should address [https://github.com/OSGeo/grass/issues/5663 #5663]. Still needs to test it.
** Agreed on convention for titles with Vaclav, unblocking [https://github.com/OSGeo/grass/pull/5341 #5341]
** Found a name with Ondrej and finally merged older PRs of an external contributor [https://github.com/OSGeo/grass/pull/5473 #5473] and [https://github.com/OSGeo/grass/pull/5474 #5474]
* Thursday May 20, 2025:
** Reviewed: [https://github.com/OSGeo/grass/pull/5695 #5695]
** Merged PRs: [https://github.com/OSGeo/grass/pull/5673 #5673], [https://github.com/OSGeo/grass/pull/5691 #5691], [https://github.com/OSGeo/grass/pull/5690 #5690], [https://github.com/OSGeo/grass/pull/5684 #5684],
** Discussed with author of [https://github.com/OSGeo/grass/pull/5660 #5660] and [https://github.com/OSGeo/grass/issues/5659 #5659] about rgb/hsl bug and tests for help.
** Worked with Corey to adjust markdown links for new markdownlint rule, finishing up [https://github.com/OSGeo/grass/pull/5669 #5669]
** Created PRs: [https://github.com/OSGeo/grass/pull/5692 #5692], [https://github.com/OSGeo/grass/pull/5694 #5694], [https://github.com/OSGeo/grass/pull/5689 #5689]
* Wednesday May 21, 2025:
** Created a new set of GitHub rulesets for the required checks, applied with Vaclav. One of them is separated in order to increase velocity during the sprint
** Reviewed the branch protection rules for grass-addons repo with Vaclav. Creating rulesets will be possible after the sprint with the info collected.
** Reviewed the security reporting settings and secret scanning settings with Vaclav for the main grass repo.
** Got shown by Huidae Cho how to update the translation files, and reviewed Weblate settings. No settings changed, but a backup stored for 30 days was kept.
** Created a first implementation of a translation file update workflow
** Tested out the two NSIS installer PRs, the first one, for installing the VC runtime earlier doesn't work as expected, and after more research I don't know enough to fix it. The second PR with High-DPI improvement was correct and got merged [https://github.com/OSGeo/grass/pull/5685 #5685]
** Helped a student set up a grass installation on WSL with conda.
** PRs created: [https://github.com/OSGeo/grass/pull/5736 #5736], [https://github.com/OSGeo/grass/pull/5734 #5734]
** My PRs that got merged: [https://github.com/OSGeo/grass/pull/5685 #5685], [https://github.com/OSGeo/grass/pull/5341 #5341], [https://github.com/OSGeo/grass/pull/5689 #5689]
** Reviewed and merged multiple PRs, restarting failed required checks of the previous night.

=== Laurent Courty ===

* Objectives: An xarray backend for GRASS STRDS. Fixing related issues
* May 20
** Presented itzi
** Uploaded arm64 wheels to PyPI for MacOS and Linux ([https://pypi.org/project/itzi/#files])
** Discussed with other developers about issue #629
* May 21
** Uploaded xarray-grass to PyPI
** Added CI tests to xarray-grass
** Discussed with the group about the xarray-grass backend
** Discussed with the group about solving mapset switching in the temporal framework (issue #629)
** Created PR #5735 to address issue #629
* May 22
** Fix bug in PR #5735

=== Robert S. Dzur | Bohannan Huston, Inc. ===

* r.in.pdal

=== David W. Farris | East Carolina University ===

* A tool to calculate gravity terrain corrections

=== Neel Ghoshal | NC State University ===
• LLM for helping users find tools 
5/19 
• Learnt how to PR (#5674) 
• Setup GRASS on system 
• Found small issue with compilation document 
• Discussed about the possible use case of LLM for helping users find tools 
5/20 
• Learnt about cookie cutter 
• Set up wsl on system 
• Compiled GRASS 
• Listed data sources for LLM training 
5/21 
• Extracted tool information from Markdown files 
• Started off with data cleaning 
5/22 
• Worked on LLM setup 
5/23 
• Ran and finetuned a basic test LLM model for extracted data 

=== Caitlin Haedrich | NC State University ===

* Event photographs, food coordination
* git/github mentoring
* GRASS mentoring
* Lightning Talk preparation
* Preparing workshop for [https://www.geomorphometry2025.org/ Geomorphometry2025]

=== Brendan Harmon | Louisiana State University ===

* Developing ([https://github.com/baharmon/r.earthworks r.earthworks]) addon & tutorials
* [https://github.com/baharmon?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]

=== Linda Karlovska | Czech Technical University in Prague ===

* Fix uninitialized variables in DOutFile() method: ([https://github.com/OSGeo/grass/pull/5650 PR])
* Update figures related to GUI: ([https://github.com/OSGeo/grass/pull/5651 PR])

Working on integration of the Jupyter notebooks to GUI (work for the whole week :-))

=== Martin Landa | Czech Technical University in Prague ===

* Tutorial: GISMentors courses updated ([https://github.com/OSGeo/grass-tutorials/pull/45 PR])
* libgis: G__usage_markdown() include tool label in metadata if defined ([https://github.com/OSGeo/grass/pull/5677 PR])
* PyGRASS: Module description property not defined always ([https://github.com/OSGeo/grass/pull/5681 PR])
* Website: OpenGeoLabs commercial support ([https://github.com/OSGeo/grass-website/pull/537 PR])
* v.select: create output also when no features found ([https://github.com/OSGeo/grass/pull/5696 PR])
* wxGUI: avoid creating nested list of errors (Graphical modeler) ([https://github.com/OSGeo/grass/pull/5700 PR])
* wxGUI/gmodeler: refactor - move ModelParamDialog to dialogs.py ([https://github.com/OSGeo/grass/pull/5715 PR])
* GUI: make Python editor dockable ([https://github.com/OSGeo/grass/pull/5733 PR])
* r.relief: module label changed to description ([https://github.com/OSGeo/grass/pull/5741 PR])
* GUI: propagate previously defined where option value ([https://github.com/OSGeo/grass/pull/5747 PR])
* GUI: always show 'Close dialog on finish' option ([https://github.com/OSGeo/grass/pull/5751 PR])
* GUI: do not remove parameter value on dialog update event ([https://github.com/OSGeo/grass/pull/5760 PR])
* documentation: add miscellaneous tools too full index (markdown) ([https://github.com/OSGeo/grass/pull/5761 PR])

=== Nicklas Larsson | Hungarian National Museum ===

Planned work: CMake build system; perhaps Conda recipe

[https://github.com/nilason?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]

* Preparation for CMake build conforming to Filesystem Hierarchy Standard (FHS), resolving resource paths for both the current and FHS in code. In collaboration with Huidae Cho and with important input from Vaclav Petras ([https://github.com/OSGeo/grass/pull/5630 PR5630])

* Helped young students in build configuration and debugging techniques.

* Discussion with several participants on solutions to publish a GRASS package to Conda-forge.

=== Chung-Yuan Liang ===

* parallelize some modules, improve testing

=== Andres Lucero | Bohannan Huston Inc ===

* r.in.pdal

=== Alen Mangafić | Geodetic Institute of Slovenia ===
Monday May 19
* Presentationf of i.hyper, add-on which offers hyperspectral data support in GRASS.
* Architecture of the multi-module addon
Tuesday May 20
* i.hyper.import module: importing EnMAP imagery as 3D raster map
* i.hyper.preproc module: draft
Wednesday May 21
* fixing the i.hyper.import module
* i.hyper.preproc module: implementing Savitzky-Golay filter

=== Helena Mitasova | NC State University ===

* standardized data set and related tutorials
* documentation for interpolation tools
* collaborate/coordinate/discuss hydrology tools (analytics, simulations, soil properties inputs)
* assist with wiki cleanup if needed

Monday May 19
* investigated issues with v.surf.rst documentation in source code, tested and identified fixes needed
* discussed coupling GRASS with Blender versus potree for 3D object rendering with Brendan, Anna and Caitlin (for TL activities and other applications)
* discussed soil data for runoff estimation and other hydro topics, to be worked on on day 2

Tuesday May 20
* worked with Corey on fixing v.surf.rst documentation, discussed ideas for improvements and for documentation / tutorial for cross-valiadation
* discussed suggestions for graphics and examples to be inculded in v.surf.rst docs with Michelle
* discussed new developments in hydrology tools
* experimented with basic/standardized versus specialized data sets for documentation and tutorials

Wednesday May 21
* explored existing tutorials, emailed Paulo about finishing the one on interpolation
* tested NM basic data set with GIS582 class assignment (very cool)
* discussed design of Jnotebooks that would work with various localized data with Caitlin

Thursday May 22
* discussed needed capabilities for a more advanced color ramp processing tool with Brendan
* added further ideas to basic dataset document after talking to Vero - we just need standardized names for the localized tutorials to work
* discussed infiltration fix pull request for r.sim.water with Anna - more work is needed

=== Michael Mulqueen | MassGIS ===

* depth to water, hydro from lidar, etc

=== Māris Nartišs ===

* Taking photos of the event
* Introduced a new GRASS core module r.smooth.edgepreserve
* Discussed architecture of hyperspectral data import and per-processing tool
* Discussed testing and organizing AI modules downloading data from internet
* Prepared and gave a presentation on code preparation for translations (best practice)
* Debugging translation file updating with Edouard
* Changed default multiprocessor setting to always use maximum number of available threads
* Unified max process setting handling in all modules that use default parser parameter
* Discovered and supervised fixing a bug in r.univar parallelization code
* Discussing requirements for raster data reading parallelization (GRASS 9)

=== Ondřej Pešek | Czech Technical University in Prague ===

* [https://github.com/pesekon2?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* Refactoring, fixing, improving, discussing g.gui.gmodeler
* Discussing hyperspectral with Alen Mangafic
* Discussing jupyter in single GUI with Linda Karlovska
* PyGRASS
* Docs
* CQ
* Reviewing PRs, PR archeology

=== Vaclav (Vashek) Petras | NC State University ===

* [https://github.com/wenzeslaus?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* My focus: Getting feedback and ideas for computational engine use case, APIs, funding.
* Summit organizing
* Implementing rebranding on GitHub (repos, teams)
* Feedback session on project image
* Feedback session on easier access to tools
* Discussed LLMs with Neel Ghoshal, Riya
* Discussed session setupp Martin Landa
* Discussed conda with Nicklas Larsson
* Discussed hyperspectral with Alen Mangafić, Veronica Andreo, and Anna Petrasova
* Discussed code for new smoothing tool, integer overflows, translations with Māris Nartišs
* Compared setup of GRASS session and project in fasterRaster, QGIS, and GRASS itself with Adam Smith
* Discussed potential of Pixi for packaging or compilation with Gregory Power
* Discussed itzi model distribution issues with Laurent Courty
* Discussed r.horizon parallelization with Chung-Yuan Liang and Anna Petrasova
* Answered coding and setup questions for Neel Ghoshal, Abdullah Azzam, and Alen Mangafić

=== Anna Petrasova | NC State University ===

* [https://github.com/petrasovaa?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* plan: mentoring, documentation
* Monday
** discussing hyperspectral implementation with Alen
** helping mentee David Farris implementing his gravity correction addon
* Tuesday
** delivered intro to creating an addon, documentation
** mentoring Alen, Abdullah
** discussing bug in i.his.rgb with Jayneel
** reviews
* Wednesday
** discuss and demonstrate tutorials page
** mentoring Alen, Jayneel
** call with GSoC student
* Thursday
** lightning talk
** discussing openmp implementations for r.horizon, r.mapcalc, default thread number
* Friday
** grass repo README
** reviews

=== Gregory Power | Town of Cary ===

* Documentation

=== Pratikshya Regmi | NC State University ===

* Event photographs and videos
* Opened a pull request to change GRASS GIS to GRASS on the documentation (this was my first contribution to GRASS)
* Worked on preparing the mock document for LLM RAG
* Wrote a tutorial to Visualize Contour Lines with a Color Gradient with Folium.

=== Riya | Indian Institute of Technology, Roorkee ===

* I am currently thinking of developing an AI Agent for the grass jupyter library which will help the users with mathematical calculations done in GIS.

=== Jayneel Shah | NC State University ===

* improve the test coverage of imagery modules.

=== Krishna Prasad Sheshadri ===

*

=== Adam Smith | Missouri Botanical Garden ===

Overall: R package fasterRaster (fielding bug reports, adding features)

Monday:
* Assessed scope of fasterRaster issue [https://github.com/adamlilith/fasterRaster/issues/83 83]

Tuesday:
* Created a PR for fasterRaster tutorial on GRASS tutorials page.
* Improved handling of addons, including autodetect and installing when needed, enabling easier creation of addon-dependent methods.
* Presented *fasterRaster* package to group.

Wednesday:
* Created fasterRaster methods for neighborhood matrices, terrain ruggedness index, and multivariate environmental similarity

=== Michelle (Mimi) Stephens | ERDC ===

* Previous work: coupling R and Python scripts for computational analysis in GRASS.
* Current work: Running through GRASS commands to create visual outputs that can be added to the new GRASS 8.5 manual pages - r.mapcalc, v.surf.rst, examples with topographic parameters, LinkedIn requests.
* Tutorial for Windows users to install a WSL2 Linux environment. Creates a conda environment with wxpython, installs GRASS without requiring OSGeo installer. Fast, simple, and minimal install. Resolves various issues encountered in government due to automatic Windows updates, cyber security, vpn routing, user preference, and isolated distro can be completely removed if needed. -> Motivation for WSL2 - wanted more hands-on practice with Unix command line tools for HPC; Docker not allowed, but miniforge and Apptainer are on ERDC's HPC; able to install grass via command line (only on internet-capable HPC systems); AND - For other users that always wanted a more native feel to their grass instance!
* Future work: Presenting on GRASS in JUNE at CERLCON.

=== Corey White | NC State University ===

* JSON, mentoring

=== Doug Newcomb | Semi Retired Cartographer ===

* Discussed hydroflattening method
* Discussed direct point cloud input to v.surf.rst
* Learning git procedures by updating branding (GRASS GIS to GRASS) for raster commands
Tuesday
* Continued updating branding for raster commands
* Started working on tutorial for r.hydro.flatten
Wednesday
* Finalized Data set for for r.hydro.flatten
* Worked on Lightning Talk for Thursday
Thursday
* Continued work on r.hydro.flatten tutorial
* Gave lightning talk on r.hydro.flatten
Friday
* Worked with Rob Dzur on r.hydro.flatten workflow.
* Explored the possibility of using r.resample.bspline for areas with high standard deviation ranges.

* Worked with Rob Dzur on identifying workflow for implimenting USGS GMI, https://www.usgs.gov/ngp-standards-and-specifications/elevation-derived-hydrography-data-acquisition-specifications-16 , in GRASS and connected Rob with USGS contact for GMI.

=== Natalie Trso | Balance Geo LLC ===

* r.sim.water

== Guests and remote participants ==

=== Luís de Sousa | University of Lisbon ===

* Review outstanding PRs
* Prepare GRASS sessions for the OpenGeoHub Summer School

=== Markus Neteler | mundialis ===

* Support full automation of new GRASS manual pages deployment on server (upload artifacts from GitHub to OSGeo servers (grass and download))
* Source code license documentation: Using SPDX License IDs ({{GH-Issues|4190}})
* Support Wiki cleanup
* [https://github.com/neteler?tab=overview&from=2025-05-19&to=2025-05-24 GitHub contributions]

=== Nishant Bansal | Indian Institute of Technology, Varanasi ===

* Review the previous work on JSON during last year’s GSoC, including enhancements and the addition of JSON output support to other modules.

Talk:GRASS Developer Summit Raleigh 2025

2025-05-24T03:00:41Z

Annakrat: /* Day 6, Saturday, May 24 */

{{toc|right}}

Quick links: [[GRASS Developer Summit Raleigh 2025|Meeting page]] | [[#Participant_reports|Reports]] | [[GRASS_Developer_Summit_Raleigh_2025#Sponsors|Sponsors]]

== Organizing Team ==

* Initial planning: Vaclav Petras, Anna Petrasova, Veronica Andreo, Corey White, Lois Utt, Sarah White, Doug Newcomb, Huidae Cho, Veronica Andreo ([[GRASS_Developer_Summit_Raleigh_2025#Organizing_Committee|Organizing Committee]])
* Budget: Vaclav Petras, Lois Utt, Anna Petrasova
* Raising support: Helena Mitasova, Vaclav Petras, Anna Petrasova, Michael Barton, Giuseppe Amatulli ([[NSF POSE Project 2023-2025 Timeline|NSF POSE project]] proposal authors)
* Travel: Lois Utt
* Venue: Vaclav Petras, Lois Utt
* Meals: Lois Utt, Sarah White, Vaclav Petras, Corey White, Anna Petrasova
* Agenda: Vaclav Petras, Huidae Cho, Anna Petrasova
* Wiki page: Vaclav Petras, Anna Petrasova
* Swag: Sarah White, Vaclav Petras, Anna Petrasova, Corey White
* Promotion, invitations, and social media: Vaclav Petras, Sarah White, Corey White, John Vogler
* Lightning talks organization: Vaclav Petras, Zachary Arcaro, John Vogler
* Lightning talk speakers: Vaclav Petras (welcome), Markus Metz and Markus Neteler (talk presented by Vaclav Petras), Anna Petrasova, Veronica Andreo, Robert Dzur, Nick Brady, Huidae Cho, Gregory Power, Doug Newcomb, Caitlin Haedrich
* Photography: Caitlin Haedrich, Māris Nartišs, Pratikshya Regmi
* Portrait photography: Riya, Caitlin Haedrich, Natalie Trso

== Detailed Schedule ==

=== Day 1, Monday, May 19 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Contributing to GRASS. Getting started. Is it easy to contribute?''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-9:00 || Breakfast || Catered breakfast on site. Meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || What to expect from the event, contributing to GRASS using Git and GitHub, making your first contribution.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || i.hyper: Integrating Hyperspectral Imagery Processing into GRASS - Alen Mangafić
|-
| 11:20-11:40 || Self-organized feedback sessions ||
|-
| 11:40-12:00 || Self-organized feedback sessions || Project Image - Vaclav Petras
|-
| 12:00-13:00 || Lunch || Catered food on site.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || We will walk to [https://www.trophybrewing.com/brewing-pizza Trophy Brewing & Pizza] ([https://maps.app.goo.gl/ggnZ7EvXbWqDUmvP9 directions], 30 min walk from Talley)
|}

=== Day 2, Tuesday, May 20 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topics: ''Hydrology and Interfacing with R and QGIS (gathering user feedback, testing, discussing with developers, developing action items)''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-9:00 || Breakfast || Breakfast on site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Introduction to writing GRASS tools, program for the day.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || fasterRaster R package - Adam Smith
|-
| 11:20-11:40 || Self-organized feedback sessions || Hydography90m + Geocomputation Courses - Giuseppe
|-
| 11:40-12:00 || Self-organized feedback sessions || Flood modelling with grass and itzi ([https://itzi.org]) - Laurent Courty
|-
| 12:00-13:00 || Lunch || [https://maps.app.goo.gl/womSkce9DrE8CTnR8 Case dining hall]
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/CQiWoCAQNt1ymZkb7 Served in Jordan Hall at the Center for Geospatial Analytics], evaluate the day's accomplishments, plan and prioritize for the next few days.
|}

=== Day 3, Wednesday, May 21 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Non-coding contributions, natural language translation, and internationalization.''

{| class="wikitable"
! Time !! Slot !!
|-
| 7:00-9:00 || Breakfast || [https://maps.app.goo.gl/eZ8VK8Mx6TjMt9NP8 Case dining hall]
|-
| 9:00-10:00 || Morning opening sessions || Introduction to non-coding contributions, tutorials, contributing examples, natural language translation and internationalization (procedures, glossaries, code customization, translation).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Easier access to GRASS tools - Vaclav Petras
|-
| 11:20-11:40 || Self-organized feedback sessions ||
|-
| 11:40-12:00 || Self-organized feedback sessions || GRASS backend for xarray and temporal framework global variables ([https://github.com/OSGeo/grass/issues/629]) - Laurent Courty
|-
| 12:00-13:00 || Lunch || Served on site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/1E39eySMVaxYJUUS8 Picnic at Pullen Park, shelter #3. In case of bad weather, dinner at the Center for Geospatial Analytics.
|}

=== Day 4, Thursday, May 22 ===

Location: Center for Geospatial Analytics, Jordan Hall, 2800 Faucette Drive ([https://www.google.com/maps/search/Jordan+Hall/@35.7816832,-78.6772765,18z/data=!3m1!4b1?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: 5103 (straight from the two elevators, at the end of the hallway)

Highlighted topic: ''Project vision and computational engine use case.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || On site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Project vision and the computational engine use case (missing features, documentation, user groups).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || NSF POSE I-Corps Interviews - Corey White
|-
| 11:20-11:40 || Self-organized feedback session || YAIT - Yet Another Interface to Tools - Vaclav Petras
|-
| 11:40-12:00 || Self-organized feedback session || Modernizing Color Tables (Brendan)
|-
| 12:00-13:00 || Lunch || On site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-16:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 16:00-17:00 || Lightning talks || Fast-paced talks, showcasing applications of GRASS, room 5111.
|-
| 18:00 || Reception || Connect with researchers, government professionals, and industry collaborators, rooms 5111 and 5119.
|}

=== Day 5, Friday, May 23 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topic: ''GRASS project's future course.''

{| class="wikitable"
! Time !! Slot !!
|-
| 7:45-8:15 || Breakfast || '''Hotel Aloft (2nd floor).''' Search for Lois!
|-
| 9:00-10:00 || Morning opening sessions || GRASS project's future course.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-12:00 || PSC meeting || Project Steering Committee meets (public).
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Rescheduled for Saturday

|-
| 12:00-13:00 || Lunch || Walk to [https://maps.app.goo.gl/kHVHY62QxTd6wHKd9 On the Oval Culinary Creations]. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || Dinner on your own. Corey White will organize trip to downtown. Bus 41 from Hunt library to hotel and then walk.
|}

=== Day 6, Saturday, May 24 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

'''Take bus 41 at 8.30 from Aloft.'''

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topics: ''NSF POSE project evaluation.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-10:00 || Breakfast || We will have breakfast (yogurt, granola, pastries) at [https://maps.app.goo.gl/EwzNxeovv4rTivjK9 Lake Raleigh]. Feel free to bring your own coffee.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || GRASS tools: core and additional functionality (MartinL)
|-
| 12:00-13:00 || Lunch || Pizza. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || Player's Retreat.
|}

== Daily tasks for participants ==

* List all the things you are working on in the Participant reports section below. Update the list each day. Include things you work on with other people.
* If you want to discuss something with the whole group, add yourself to a Self-organized feedback sessions slot in the schedule above or tell Vaclav (Vashek) Petras.
* For people with triage access and above: If you are or will be working on an issue or on a PR which is not originally submitted by you, assign yourself to the issue or PR. (You can unassign yourself later if you change your mind.)

== Participant reports ==

Per-person reports from the meeting.

=== Giuseppe Amatulli | Yale University ===

* Testing r.watershed and r.stream.* for handling large datasets
* Running r.flowaccumulation at global level using water direction from hydrography90m
* Preparing the grass tutorial material for the https://www.geomorphometry2025.org/ conference

=== Veronica Andreo | CONICET - Instituto Gulich ===

* [https://github.com/veroandreo?tab=overview&from=2025-05-12&to=2025-05-24 GitHub contributions]
* Enhanced the website footer.
* Sync icons on the Tutorials website footer to those on the main website.
* Fix descriptions and their display on the tutorials website.
* Fix GRASS page on OSGeo website [https://www.osgeo.org/projects/grass-gis/]
** Changed logo, removed GIS from the name, fixed old links.
* Social media posts.
* Discussion about hyperspectral with Alen and Anna.
* Expand the GRASS acronym on the home page.
* Remove GIS from GRASS name on the website.
* Review tutorials by Huidae and Adam Smith.
* Add external tutorials by Huidae and the one from FOSS4G 2024.
* Started adding the time series tutorials.
* Add lightbox class in get-started tutorials so images can be clicked on.
* GRASS PSC admin stuff.
* Participated of the PSC meeting.
* Talk to Tonis Kardi from FOSS4G EU LOC to have a "State of GRASS" talk in the program. Alen will be presenting.
* Gave a lightning talk: GRASS-fed species distribution models.
* Discussed with Corey and Mimi about tutorials.

=== Abdullah Azzam | New Mexico State University ===

* Created first PR; fixed broken links on the website [https://github.com/OSGeo/grass-website/pull/538 #538]
* Pushed a new GRASS Addon ''r.curvenumber'' [https://github.com/OSGeo/grass-addons/pull/1403 #1403]

=== Michael Barton | Arizona State University ===

* POSE related activities

=== Laura Belica | NC State University ===

* have been working on developing a workflow-tool tutorial template that facilitates GRASS learners who tend to 'jump in' or have a 'choose your own adventure' approach to learning GRASS (i.e., want to use their data for their study area for their objective from the start). The structure of the tutorial template is a concise, basic, general description/instructions of the workflow with optional links to pertinent explanatory/deeper dive content (e.g., plain language explainers of the tool, options, defaults, etc.) in a variety of formats (e.g., captioned images, short tool demo videos (30 sec to 2 min)) in addition to the more comprehensive resources available (e.g. documentation, examples, tutorials). The main motivation for this approach is to help new and occasional GRASS users avoid some of the common pitfalls and to learn how to find workarounds for some of the unanticipated challenges they may encounter with their specific datasets or use cases so that they can learn as they go. Another motivation for this approach is to facilitate the translation, extension, and updating of workflow tutorials by the community over time (e.g., providing audio and closed captioning for one of the tool-demo videos in another language, replacing an outdated GUI demo with one for the current release, or incorporating a new add-on as an option in the workflow).

* my focus this week is on developing a draft/test tutorial (in Quarto) for a standard hydrological modelling workflow that begins with the crucial pre-work of how to figure out the appropriate project/location, etc. as well as considerations of some of the downstream impacts of resolution, extent, region etc. It may not be ready for sharing by the end of the week, but suggestions and advice are welcomed in advance.

19 May
* discussed a novice user issue with 'moving' vector data from one location to another with Vero and learned a neat GUI option
* revised and added workflow tutorial text

=== Shonil Sateesh Bhide | NC State University ===

* CI optimization

=== Huidae Cho | New Mexico State University ===

* CMake, conda, CI, Mentoring

Monday 5/19
* [https://github.com/OSGeo/grass/pull/5680 CMake: Recognize conda installation path at runtime]: Replaced by [https://github.com/HuidaeCho/grass-conda/blob/master/recipe/post-link.sh conda post-link.sh]
* CMake and Conda Testing on Linux
* CMake Testing on Windows
* Mentoring: Chung-Yuan, Abdullah

Tuesday 5/20
* [https://github.com/OSGeo/grass/pull/5712 CMake: Define custom complex types for MSVC LAPACKE]
* [https://github.com/OSGeo/grass/pull/5713 CMake: Fix build output directories for MSVC]
* CMake and Conda Testing on Linux
* CMake Testing on Windows

Wednesday 5/21
* Translation Talk
* Translation Discussion with Edouard
* Flow Direction Meeting with Ondrej, Ondrej's Student, Martin, and Markus Metz
* CMake and Conda Testing on Linux
* CMake Testing on Windows
* Mentoring: Chung-Yuan, Abdullah

Thursday 5/22
* [https://github.com/OSGeo/grass/pull/5740 CMake: Fix the parameter is incorrect: . error for MSVC]
* Lightning Talk
* CMake and Conda Testing on Linux
* CMake Testing on Windows
* CI: Discussion with Edouard
* Mentoring: Chung-Yuan, Abdullah

=== Edouard Choinière ===

* Quick ideas, way too much for a week: Helping others (may take a reasonable part of the time), managing CI, setting up localization template updating workflow, backporting tool? Pytest/coverage improvements? Discuss and design other projects, to work on during the year. Open to change on other priorities once there, anything that is useful. Maybe make a little progress on high dpi GUI, especially on Windows.

* Weekend before sprint:
** Clear up Renovate PRs to not use CI time during the sprint, reviewing and merging: [https://github.com/OSGeo/grass/pull/5664 #5664], [https://github.com/OSGeo/grass/pull/5665 #5665], [https://github.com/OSGeo/grass/pull/5666 #5666], [https://github.com/OSGeo/grass/pull/5667 #5667], [https://github.com/OSGeo/grass/pull/5668 #5668]
** PR to avoid some CI run time for the sprint: [https://github.com/OSGeo/grass/pull/5670 #5670]
** Reviewed open PRs for PRs that were mergeable before the sprint, updated outdated PRs to avoid having it needing CI time during sprint. Only ended up merging [https://github.com/OSGeo/grass/pull/5658 #5658], but another reviewed one that might still need changes: [https://github.com/OSGeo/grass/pull/5628 #5628]
* Monday May 19, 2025:
** PR got merged: [https://github.com/OSGeo/grass/pull/5670 #5670],[https://github.com/OSGeo/grass/pull/5550 #5550]
** Reviewed PRs: [https://github.com/OSGeo/grass/pull/5671 #5671], [https://github.com/OSGeo/grass/pull/5672 #5672]
** Discussions:
*** Shonil Sateesh Bhid & Shuham on their CI & pytest work and project.
*** Māris Nartišs about a potential issue and improvement for it. Will be discussed in the security reporting tab, also allowing to test the security vulnerability reporting process. + Research on existing solutions
** Reviewed: [https://github.com/OSGeo/grass/pull/5682 #5682], [https://github.com/OSGeo/grass/pull/5660 #5660],
** Reviewed, edited and merged: [https://github.com/OSGeo/grass/pull/3672 #3672]
** Discussed/helped user for: [https://github.com/OSGeo/grass/pull/5678 #5678] and [https://github.com/OSGeo/grass/pull/5684 #5684]
** Long discussion and vision planning for windows scripting with Vaclav, concerning [https://github.com/OSGeo/grass/pull/5624 #5624]. Tested alternatives and tried the consequences of that PR. This older PR finally got merged.
** Created PRs for NSIS installer: [https://github.com/OSGeo/grass/pull/5685 #5685] and also [https://github.com/OSGeo/grass/pull/5686 #5686], which should address [https://github.com/OSGeo/grass/issues/5663 #5663]. Still needs to test it.
** Agreed on convention for titles with Vaclav, unblocking [https://github.com/OSGeo/grass/pull/5341 #5341]
** Found a name with Ondrej and finally merged older PRs of an external contributor [https://github.com/OSGeo/grass/pull/5473 #5473] and [https://github.com/OSGeo/grass/pull/5474 #5474]
* Thursday May 20, 2025:
** Reviewed: [https://github.com/OSGeo/grass/pull/5695 #5695]
** Merged PRs: [https://github.com/OSGeo/grass/pull/5673 #5673], [https://github.com/OSGeo/grass/pull/5691 #5691], [https://github.com/OSGeo/grass/pull/5690 #5690], [https://github.com/OSGeo/grass/pull/5684 #5684],
** Discussed with author of [https://github.com/OSGeo/grass/pull/5660 #5660] and [https://github.com/OSGeo/grass/issues/5659 #5659] about rgb/hsl bug and tests for help.
** Worked with Corey to adjust markdown links for new markdownlint rule, finishing up [https://github.com/OSGeo/grass/pull/5669 #5669]
** Created PRs: [https://github.com/OSGeo/grass/pull/5692 #5692], [https://github.com/OSGeo/grass/pull/5694 #5694], [https://github.com/OSGeo/grass/pull/5689 #5689]
* Wednesday May 21, 2025:
** Created a new set of GitHub rulesets for the required checks, applied with Vaclav. One of them is separated in order to increase velocity during the sprint
** Reviewed the branch protection rules for grass-addons repo with Vaclav. Creating rulesets will be possible after the sprint with the info collected.
** Reviewed the security reporting settings and secret scanning settings with Vaclav for the main grass repo.
** Got shown by Huidae Cho how to update the translation files, and reviewed Weblate settings. No settings changed, but a backup stored for 30 days was kept.
** Created a first implementation of a translation file update workflow
** Tested out the two NSIS installer PRs, the first one, for installing the VC runtime earlier doesn't work as expected, and after more research I don't know enough to fix it. The second PR with High-DPI improvement was correct and got merged [https://github.com/OSGeo/grass/pull/5685 #5685]
** Helped a student set up a grass installation on WSL with conda.
** PRs created: [https://github.com/OSGeo/grass/pull/5736 #5736], [https://github.com/OSGeo/grass/pull/5734 #5734]
** My PRs that got merged: [https://github.com/OSGeo/grass/pull/5685 #5685], [https://github.com/OSGeo/grass/pull/5341 #5341], [https://github.com/OSGeo/grass/pull/5689 #5689]
** Reviewed and merged multiple PRs, restarting failed required checks of the previous night.

=== Laurent Courty ===

* Objectives: An xarray backend for GRASS STRDS. Fixing related issues
* May 20
** Presented itzi
** Uploaded arm64 wheels to PyPI for MacOS and Linux ([https://pypi.org/project/itzi/#files])
** Discussed with other developers about issue #629
* May 21
** Uploaded xarray-grass to PyPI
** Added CI tests to xarray-grass
** Discussed with the group about the xarray-grass backend
** Discussed with the group about solving mapset switching in the temporal framework (issue #629)
** Created PR #5735 to address issue #629
* May 22
** Fix bug in PR #5735

=== Robert S. Dzur | Bohannan Huston, Inc. ===

* r.in.pdal

=== David W. Farris | East Carolina University ===

* A tool to calculate gravity terrain corrections

=== Neel Ghoshal | NC State University ===
• LLM for helping users find tools 
5/19 
• Learnt how to PR (#5674) 
• Setup GRASS on system 
• Found small issue with compilation document 
• Discussed about the possible use case of LLM for helping users find tools 
5/20 
• Learnt about cookie cutter 
• Set up wsl on system 
• Compiled GRASS 
• Listed data sources for LLM training 
5/21 
• Extracted tool information from Markdown files 
• Started off with data cleaning 
5/22 
• Worked on LLM setup 
5/23 
• Ran and finetuned a basic test LLM model for extracted data 

=== Caitlin Haedrich | NC State University ===

* Event photographs, food coordination
* git/github mentoring
* GRASS mentoring
* Lightning Talk preparation
* Preparing workshop for [https://www.geomorphometry2025.org/ Geomorphometry2025]

=== Brendan Harmon | Louisiana State University ===

* Developing ([https://github.com/baharmon/r.earthworks r.earthworks]) addon & tutorials
* [https://github.com/baharmon?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]

=== Linda Karlovska | Czech Technical University in Prague ===

* Fix uninitialized variables in DOutFile() method: ([https://github.com/OSGeo/grass/pull/5650 PR])
* Update figures related to GUI: ([https://github.com/OSGeo/grass/pull/5651 PR])

Working on integration of the Jupyter notebooks to GUI (work for the whole week :-))

=== Martin Landa | Czech Technical University in Prague ===

* Tutorial: GISMentors courses updated ([https://github.com/OSGeo/grass-tutorials/pull/45 PR])
* libgis: G__usage_markdown() include tool label in metadata if defined ([https://github.com/OSGeo/grass/pull/5677 PR])
* PyGRASS: Module description property not defined always ([https://github.com/OSGeo/grass/pull/5681 PR])
* Website: OpenGeoLabs commercial support ([https://github.com/OSGeo/grass-website/pull/537 PR])
* v.select: create output also when no features found ([https://github.com/OSGeo/grass/pull/5696 PR])
* wxGUI: avoid creating nested list of errors (Graphical modeler) ([https://github.com/OSGeo/grass/pull/5700 PR])
* wxGUI/gmodeler: refactor - move ModelParamDialog to dialogs.py ([https://github.com/OSGeo/grass/pull/5715 PR])
* GUI: make Python editor dockable ([https://github.com/OSGeo/grass/pull/5733 PR])
* r.relief: module label changed to description ([https://github.com/OSGeo/grass/pull/5741 PR])
* GUI: propagate previously defined where option value ([https://github.com/OSGeo/grass/pull/5747 PR])
* GUI: always show 'Close dialog on finish' option ([https://github.com/OSGeo/grass/pull/5751 PR])
* GUI: do not remove parameter value on dialog update event ([https://github.com/OSGeo/grass/pull/5760 PR])
* documentation: add miscellaneous tools too full index (markdown) ([https://github.com/OSGeo/grass/pull/5761 PR])

=== Nicklas Larsson | Hungarian National Museum ===

Planned work: CMake build system; perhaps Conda recipe

[https://github.com/nilason?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]

* Preparation for CMake build conforming to Filesystem Hierarchy Standard (FHS), resolving resource paths for both the current and FHS in code. In collaboration with Huidae Cho and with important input from Vaclav Petras ([https://github.com/OSGeo/grass/pull/5630 PR5630])

* Helped young students in build configuration and debugging techniques.

* Discussion with several participants on solutions to publish a GRASS package to Conda-forge.

=== Chung-Yuan Liang ===

* parallelize some modules, improve testing

=== Andres Lucero | Bohannan Huston Inc ===

* r.in.pdal

=== Alen Mangafić | Geodetic Institute of Slovenia ===
Monday May 19
* Presentationf of i.hyper, add-on which offers hyperspectral data support in GRASS.
* Architecture of the multi-module addon
Tuesday May 20
* i.hyper.import module: importing EnMAP imagery as 3D raster map
* i.hyper.preproc module: draft
Wednesday May 21
* fixing the i.hyper.import module
* i.hyper.preproc module: implementing Savitzky-Golay filter

=== Helena Mitasova | NC State University ===

* standardized data set and related tutorials
* documentation for interpolation tools
* collaborate/coordinate/discuss hydrology tools (analytics, simulations, soil properties inputs)
* assist with wiki cleanup if needed

Monday May 19
* investigated issues with v.surf.rst documentation in source code, tested and identified fixes needed
* discussed coupling GRASS with Blender versus potree for 3D object rendering with Brendan, Anna and Caitlin (for TL activities and other applications)
* discussed soil data for runoff estimation and other hydro topics, to be worked on on day 2

Tuesday May 20
* worked with Corey on fixing v.surf.rst documentation, discussed ideas for improvements and for documentation / tutorial for cross-valiadation
* discussed suggestions for graphics and examples to be inculded in v.surf.rst docs with Michelle
* discussed new developments in hydrology tools
* experimented with basic/standardized versus specialized data sets for documentation and tutorials

Wednesday May 21
* explored existing tutorials, emailed Paulo about finishing the one on interpolation
* tested NM basic data set with GIS582 class assignment (very cool)
* discussed design of Jnotebooks that would work with various localized data with Caitlin

Thursday May 22
* discussed needed capabilities for a more advanced color ramp processing tool with Brendan
* added further ideas to basic dataset document after talking to Vero - we just need standardized names for the localized tutorials to work
* discussed infiltration fix pull request for r.sim.water with Anna - more work is needed

=== Michael Mulqueen | MassGIS ===

* depth to water, hydro from lidar, etc

=== Māris Nartišs ===

* Taking photos of the event
* Introduced a new GRASS core module r.smooth.edgepreserve
* Discussed architecture of hyperspectral data import and per-processing tool
* Discussed testing and organizing AI modules downloading data from internet
* Prepared and gave a presentation on code preparation for translations (best practice)
* Debugging translation file updating with Edouard
* Changed default multiprocessor setting to always use maximum number of available threads
* Unified max process setting handling in all modules that use default parser parameter
* Discovered and supervised fixing a bug in r.univar parallelization code
* Discussing requirements for raster data reading parallelization (GRASS 9)

=== Ondřej Pešek | Czech Technical University in Prague ===

* [https://github.com/pesekon2?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* Refactoring, fixing, improving, discussing g.gui.gmodeler
* Discussing hyperspectral with Alen Mangafic
* Discussing jupyter in single GUI with Linda Karlovska
* PyGRASS
* Docs
* CQ
* Reviewing PRs, PR archeology

=== Vaclav (Vashek) Petras | NC State University ===

* [https://github.com/wenzeslaus?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* My focus: Getting feedback and ideas for computational engine use case, APIs, funding.
* Summit organizing
* Implementing rebranding on GitHub (repos, teams)
* Feedback session on project image
* Feedback session on easier access to tools
* Discussed LLMs with Neel Ghoshal, Riya
* Discussed session setupp Martin Landa
* Discussed conda with Nicklas Larsson
* Discussed hyperspectral with Alen Mangafić, Veronica Andreo, and Anna Petrasova
* Discussed code for new smoothing tool, integer overflows, translations with Māris Nartišs
* Compared setup of GRASS session and project in fasterRaster, QGIS, and GRASS itself with Adam Smith
* Discussed potential of Pixi for packaging or compilation with Gregory Power
* Discussed itzi model distribution issues with Laurent Courty
* Discussed r.horizon parallelization with Chung-Yuan Liang and Anna Petrasova
* Answered coding and setup questions for Neel Ghoshal, Abdullah Azzam, and Alen Mangafić

=== Anna Petrasova | NC State University ===

* [https://github.com/petrasovaa?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* plan: mentoring, documentation
* Monday
** discussing hyperspectral implementation with Alen
** helping mentee David Farris implementing his gravity correction addon
* Tuesday
** delivered intro to creating an addon, documentation
** mentoring Alen, Abdullah
** discussing bug in i.his.rgb with Jayneel
** reviews
* Wednesday
** discuss and demonstrate tutorials page
** mentoring Alen, Jayneel
* call with GSoC student
* Thursday
* Friday
** grass repo README
** reviews

=== Gregory Power | Town of Cary ===

* Documentation

=== Pratikshya Regmi | NC State University ===

* Event photographs and videos
* Opened a pull request to change GRASS GIS to GRASS on the documentation (this was my first contribution to GRASS)
* Worked on preparing the mock document for LLM RAG
* Wrote a tutorial to Visualize Contour Lines with a Color Gradient with Folium.

=== Riya | Indian Institute of Technology, Roorkee ===

* I am currently thinking of developing an AI Agent for the grass jupyter library which will help the users with mathematical calculations done in GIS.

=== Jayneel Shah | NC State University ===

* improve the test coverage of imagery modules.

=== Krishna Prasad Sheshadri ===

*

=== Adam Smith | Missouri Botanical Garden ===

Overall: R package fasterRaster (fielding bug reports, adding features)

Monday:
* Assessed scope of fasterRaster issue [https://github.com/adamlilith/fasterRaster/issues/83 83]

Tuesday:
* Created a PR for fasterRaster tutorial on GRASS tutorials page.
* Improved handling of addons, including autodetect and installing when needed, enabling easier creation of addon-dependent methods.
* Presented *fasterRaster* package to group.

Wednesday:
* Created fasterRaster methods for neighborhood matrices, terrain ruggedness index, and multivariate environmental similarity

=== Michelle (Mimi) Stephens | ERDC ===

* Previous work: coupling R and Python scripts for computational analysis in GRASS.
* Current work: Running through GRASS commands to create visual outputs that can be added to the new GRASS 8.5 manual pages - r.mapcalc, v.surf.rst, examples with topographic parameters, LinkedIn requests.
* Tutorial for Windows users to install a WSL2 Linux environment. Creates a conda environment with wxpython, installs GRASS without requiring OSGeo installer. Fast, simple, and minimal install. Resolves various issues encountered in government due to automatic Windows updates, cyber security, vpn routing, user preference, and isolated distro can be completely removed if needed. -> Motivation for WSL2 - wanted more hands-on practice with Unix command line tools for HPC; Docker not allowed, but miniforge and Apptainer are on ERDC's HPC; able to install grass via command line (only on internet-capable HPC systems); AND - For other users that always wanted a more native feel to their grass instance!
* Future work: Presenting on GRASS in JUNE at CERLCON.

=== Corey White | NC State University ===

* JSON, mentoring

=== Doug Newcomb | Semi Retired Cartographer ===

* Discussed hydroflattening method
* Discussed direct point cloud input to v.surf.rst
* Learning git procedures by updating branding (GRASS GIS to GRASS) for raster commands
Tuesday
* Continued updating branding for raster commands
* Started working on tutorial for r.hydro.flatten
Wednesday
* Finalized Data set for for r.hydro.flatten
* Worked on Lightning Talk for Thursday
Thursday
* Continued work on r.hydro.flatten tutorial
* Gave lightning talk on r.hydro.flatten
Friday
* Worked with Rob Dzur on r.hydro.flatten workflow.
* Explored the possibility of using r.resample.bspline for areas with high standard deviation ranges.

* Worked with Rob Dzur on identifying workflow for implimenting USGS GMI, https://www.usgs.gov/ngp-standards-and-specifications/elevation-derived-hydrography-data-acquisition-specifications-16 , in GRASS and connected Rob with USGS contact for GMI.

=== Natalie Trso | Balance Geo LLC ===

* r.sim.water

== Guests and remote participants ==

=== Luís de Sousa | University of Lisbon ===

* Review outstanding PRs
* Prepare GRASS sessions for the OpenGeoHub Summer School

=== Markus Neteler | mundialis ===

* Support full automation of new GRASS manual pages deployment on server (upload artifacts from GitHub to OSGeo servers (grass and download))
* Source code license documentation: Using SPDX License IDs ({{GH-Issues|4190}})
* Support Wiki cleanup
* [https://github.com/neteler?tab=overview&from=2025-05-19&to=2025-05-24 GitHub contributions]

=== Nishant Bansal | Indian Institute of Technology, Varanasi ===

* Review the previous work on JSON during last year’s GSoC, including enhancements and the addition of JSON output support to other modules.

Talk:GRASS Developer Summit Raleigh 2025

2025-05-23T21:18:56Z

Annakrat: /* Anna Petrasova | NC State University */

{{toc|right}}

Quick links: [[GRASS Developer Summit Raleigh 2025|Meeting page]] | [[#Participant_reports|Reports]] | [[GRASS_Developer_Summit_Raleigh_2025#Sponsors|Sponsors]]

== Organizing Team ==

* Initial planning: Vaclav Petras, Anna Petrasova, Veronica Andreo, Corey White, Lois Utt, Sarah White, Doug Newcomb, Huidae Cho, Veronica Andreo ([[GRASS_Developer_Summit_Raleigh_2025#Organizing_Committee|Organizing Committee]])
* Budget: Vaclav Petras, Lois Utt, Anna Petrasova
* Raising support: Helena Mitasova, Vaclav Petras, Anna Petrasova, Michael Barton, Giuseppe Amatulli ([[NSF POSE Project 2023-2025 Timeline|NSF POSE project]] proposal authors)
* Travel: Lois Utt
* Venue: Vaclav Petras, Lois Utt
* Meals: Lois Utt, Sarah White, Vaclav Petras, Corey White, Anna Petrasova
* Agenda: Vaclav Petras, Huidae Cho, Anna Petrasova
* Wiki page: Vaclav Petras, Anna Petrasova
* Swag: Sarah White, Vaclav Petras, Anna Petrasova, Corey White
* Promotion, invitations, and social media: Vaclav Petras, Sarah White, Corey White, John Vogler
* Lightning talks organization: Vaclav Petras, Zachary Arcaro, John Vogler
* Lightning talk speakers: Vaclav Petras (welcome), Markus Metz and Markus Neteler (talk presented by Vaclav Petras), Anna Petrasova, Veronica Andreo, Robert Dzur, Nick Brady, Huidae Cho, Gregory Power, Doug Newcomb, Caitlin Haedrich
* Photography: Caitlin Haedrich, Māris Nartišs, Pratikshya Regmi
* Portrait photography: Riya, Caitlin Haedrich, Natalie Trso

== Detailed Schedule ==

=== Day 1, Monday, May 19 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Contributing to GRASS. Getting started. Is it easy to contribute?''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-9:00 || Breakfast || Catered breakfast on site. Meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || What to expect from the event, contributing to GRASS using Git and GitHub, making your first contribution.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || i.hyper: Integrating Hyperspectral Imagery Processing into GRASS - Alen Mangafić
|-
| 11:20-11:40 || Self-organized feedback sessions ||
|-
| 11:40-12:00 || Self-organized feedback sessions || Project Image - Vaclav Petras
|-
| 12:00-13:00 || Lunch || Catered food on site.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || We will walk to [https://www.trophybrewing.com/brewing-pizza Trophy Brewing & Pizza] ([https://maps.app.goo.gl/ggnZ7EvXbWqDUmvP9 directions], 30 min walk from Talley)
|}

=== Day 2, Tuesday, May 20 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topics: ''Hydrology and Interfacing with R and QGIS (gathering user feedback, testing, discussing with developers, developing action items)''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-9:00 || Breakfast || Breakfast on site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Introduction to writing GRASS tools, program for the day.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || fasterRaster R package - Adam Smith
|-
| 11:20-11:40 || Self-organized feedback sessions || Hydography90m + Geocomputation Courses - Giuseppe
|-
| 11:40-12:00 || Self-organized feedback sessions || Flood modelling with grass and itzi ([https://itzi.org]) - Laurent Courty
|-
| 12:00-13:00 || Lunch || [https://maps.app.goo.gl/womSkce9DrE8CTnR8 Case dining hall]
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/CQiWoCAQNt1ymZkb7 Served in Jordan Hall at the Center for Geospatial Analytics], evaluate the day's accomplishments, plan and prioritize for the next few days.
|}

=== Day 3, Wednesday, May 21 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Non-coding contributions, natural language translation, and internationalization.''

{| class="wikitable"
! Time !! Slot !!
|-
| 7:00-9:00 || Breakfast || [https://maps.app.goo.gl/eZ8VK8Mx6TjMt9NP8 Case dining hall]
|-
| 9:00-10:00 || Morning opening sessions || Introduction to non-coding contributions, tutorials, contributing examples, natural language translation and internationalization (procedures, glossaries, code customization, translation).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Easier access to GRASS tools - Vaclav Petras
|-
| 11:20-11:40 || Self-organized feedback sessions ||
|-
| 11:40-12:00 || Self-organized feedback sessions || GRASS backend for xarray and temporal framework global variables ([https://github.com/OSGeo/grass/issues/629]) - Laurent Courty
|-
| 12:00-13:00 || Lunch || Served on site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/1E39eySMVaxYJUUS8 Picnic at Pullen Park, shelter #3. In case of bad weather, dinner at the Center for Geospatial Analytics.
|}

=== Day 4, Thursday, May 22 ===

Location: Center for Geospatial Analytics, Jordan Hall, 2800 Faucette Drive ([https://www.google.com/maps/search/Jordan+Hall/@35.7816832,-78.6772765,18z/data=!3m1!4b1?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: 5103 (straight from the two elevators, at the end of the hallway)

Highlighted topic: ''Project vision and computational engine use case.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || On site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Project vision and the computational engine use case (missing features, documentation, user groups).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || NSF POSE I-Corps Interviews - Corey White
|-
| 11:20-11:40 || Self-organized feedback session || YAIT - Yet Another Interface to Tools - Vaclav Petras
|-
| 11:40-12:00 || Self-organized feedback session || Modernizing Color Tables (Brendan)
|-
| 12:00-13:00 || Lunch || On site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-16:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 16:00-17:00 || Lightning talks || Fast-paced talks, showcasing applications of GRASS, room 5111.
|-
| 18:00 || Reception || Connect with researchers, government professionals, and industry collaborators, rooms 5111 and 5119.
|}

=== Day 5, Friday, May 23 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topic: ''GRASS project's future course.''

{| class="wikitable"
! Time !! Slot !!
|-
| 7:45-8:15 || Breakfast || '''Hotel Aloft (2nd floor).''' Search for Lois!
|-
| 9:00-10:00 || Morning opening sessions || GRASS project's future course.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-12:00 || PSC meeting || Project Steering Committee meets (public).
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Rescheduled for Saturday

|-
| 12:00-13:00 || Lunch || Walk to [https://maps.app.goo.gl/kHVHY62QxTd6wHKd9 On the Oval Culinary Creations]. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || Dinner on your own. Corey White will organize trip to downtown. Bus 41 from Hunt library to hotel and then walk.
|}

=== Day 6, Saturday, May 24 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topics: ''NSF POSE project evaluation.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-8:30 || Breakfast || We will have pastries at [https://maps.app.goo.gl/EwzNxeovv4rTivjK9 Lake Raleigh]. Feel free to bring your own coffee.
|-
| 8:30-10:00 || Hike || Library opens at 10AM.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || GRASS tools: core and additional functionality (MartinL)
|-
| 12:00-13:00 || Lunch || TBA. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || TBA.
|}

== Daily tasks for participants ==

* List all the things you are working on in the Participant reports section below. Update the list each day. Include things you work on with other people.
* If you want to discuss something with the whole group, add yourself to a Self-organized feedback sessions slot in the schedule above or tell Vaclav (Vashek) Petras.
* For people with triage access and above: If you are or will be working on an issue or on a PR which is not originally submitted by you, assign yourself to the issue or PR. (You can unassign yourself later if you change your mind.)

== Participant reports ==

Per-person reports from the meeting.

=== Giuseppe Amatulli | Yale University ===

* Testing r.watershed and r.stream.* for handling large datasets
* Running r.flowaccumulation at global level using water direction from hydrography90m
* Preparing the grass tutorial material for the https://www.geomorphometry2025.org/ conference

=== Veronica Andreo | CONICET - Instituto Gulich ===

* [https://github.com/veroandreo?tab=overview&from=2025-05-12&to=2025-05-24 GitHub contributions]
* Enhanced the website footer.
* Sync icons on the Tutorials website footer to those on the main website.
* Fix descriptions and their display on the tutorials website.
* Fix GRASS page on OSGeo website [https://www.osgeo.org/projects/grass-gis/]
** Changed logo, removed GIS from the name, fixed old links.
* Social media posts.
* Discussion about hyperspectral with Alen and Anna.
* Expand the GRASS acronym on the home page.
* Remove GIS from GRASS name on the website.
* Review tutorials by Huidae and Adam Smith.
* Add external tutorials by Huidae and the one from FOSS4G 2024.
* Started adding the time series tutorials.
* Add lightbox class in get-started tutorials so images can be clicked on.
* GRASS PSC admin stuff.
* Participated of the PSC meeting.
* Talk to Tonis Kardi from FOSS4G EU LOC to have a "State of GRASS" talk in the program. Alen will be presenting.
* Gave a lightning talk: GRASS-fed species distribution models.
* Discussed with Corey and Mimi about tutorials.

=== Abdullah Azzam | New Mexico State University ===

* Created first PR; fixed broken links on the website [https://github.com/OSGeo/grass-website/pull/538 #538]
* Pushed a new GRASS Addon ''r.curvenumber'' [https://github.com/OSGeo/grass-addons/pull/1403 #1403]

=== Michael Barton | Arizona State University ===

* POSE related activities

=== Laura Belica | NC State University ===

* have been working on developing a workflow-tool tutorial template that facilitates GRASS learners who tend to 'jump in' or have a 'choose your own adventure' approach to learning GRASS (i.e., want to use their data for their study area for their objective from the start). The structure of the tutorial template is a concise, basic, general description/instructions of the workflow with optional links to pertinent explanatory/deeper dive content (e.g., plain language explainers of the tool, options, defaults, etc.) in a variety of formats (e.g., captioned images, short tool demo videos (30 sec to 2 min)) in addition to the more comprehensive resources available (e.g. documentation, examples, tutorials). The main motivation for this approach is to help new and occasional GRASS users avoid some of the common pitfalls and to learn how to find workarounds for some of the unanticipated challenges they may encounter with their specific datasets or use cases so that they can learn as they go. Another motivation for this approach is to facilitate the translation, extension, and updating of workflow tutorials by the community over time (e.g., providing audio and closed captioning for one of the tool-demo videos in another language, replacing an outdated GUI demo with one for the current release, or incorporating a new add-on as an option in the workflow).

* my focus this week is on developing a draft/test tutorial (in Quarto) for a standard hydrological modelling workflow that begins with the crucial pre-work of how to figure out the appropriate project/location, etc. as well as considerations of some of the downstream impacts of resolution, extent, region etc. It may not be ready for sharing by the end of the week, but suggestions and advice are welcomed in advance.

19 May
* discussed a novice user issue with 'moving' vector data from one location to another with Vero and learned a neat GUI option
* revised and added workflow tutorial text

=== Shonil Sateesh Bhide | NC State University ===

* CI optimization

=== Huidae Cho | New Mexico State University ===

* CMake, conda, CI, Mentoring

Monday 5/19
* [https://github.com/OSGeo/grass/pull/5680 CMake: Recognize conda installation path at runtime]: Replaced by [https://github.com/HuidaeCho/grass-conda/blob/master/recipe/post-link.sh conda post-link.sh]
* CMake and Conda Testing on Linux
* CMake Testing on Windows
* Mentoring: Chung-Yuan, Abdullah

Tuesday 5/20
* [https://github.com/OSGeo/grass/pull/5712 CMake: Define custom complex types for MSVC LAPACKE]
* [https://github.com/OSGeo/grass/pull/5713 CMake: Fix build output directories for MSVC]
* CMake and Conda Testing on Linux
* CMake Testing on Windows

Wednesday 5/21
* Translation Talk
* Translation Discussion with Edouard
* Flow Direction Meeting with Ondrej, Ondrej's Student, Martin, and Markus Metz
* CMake and Conda Testing on Linux
* CMake Testing on Windows
* Mentoring: Chung-Yuan, Abdullah

Thursday 5/22
* [https://github.com/OSGeo/grass/pull/5740 CMake: Fix the parameter is incorrect: . error for MSVC]
* Lightning Talk
* CMake and Conda Testing on Linux
* CMake Testing on Windows
* CI: Discussion with Edouard
* Mentoring: Chung-Yuan, Abdullah

=== Edouard Choinière ===

* Quick ideas, way too much for a week: Helping others (may take a reasonable part of the time), managing CI, setting up localization template updating workflow, backporting tool? Pytest/coverage improvements? Discuss and design other projects, to work on during the year. Open to change on other priorities once there, anything that is useful. Maybe make a little progress on high dpi GUI, especially on Windows.

* Weekend before sprint:
** Clear up Renovate PRs to not use CI time during the sprint, reviewing and merging: [https://github.com/OSGeo/grass/pull/5664 #5664], [https://github.com/OSGeo/grass/pull/5665 #5665], [https://github.com/OSGeo/grass/pull/5666 #5666], [https://github.com/OSGeo/grass/pull/5667 #5667], [https://github.com/OSGeo/grass/pull/5668 #5668]
** PR to avoid some CI run time for the sprint: [https://github.com/OSGeo/grass/pull/5670 #5670]
** Reviewed open PRs for PRs that were mergeable before the sprint, updated outdated PRs to avoid having it needing CI time during sprint. Only ended up merging [https://github.com/OSGeo/grass/pull/5658 #5658], but another reviewed one that might still need changes: [https://github.com/OSGeo/grass/pull/5628 #5628]
* Monday May 19, 2025:
** PR got merged: [https://github.com/OSGeo/grass/pull/5670 #5670],[https://github.com/OSGeo/grass/pull/5550 #5550]
** Reviewed PRs: [https://github.com/OSGeo/grass/pull/5671 #5671], [https://github.com/OSGeo/grass/pull/5672 #5672]
** Discussions:
*** Shonil Sateesh Bhid & Shuham on their CI & pytest work and project.
*** Māris Nartišs about a potential issue and improvement for it. Will be discussed in the security reporting tab, also allowing to test the security vulnerability reporting process. + Research on existing solutions
** Reviewed: [https://github.com/OSGeo/grass/pull/5682 #5682], [https://github.com/OSGeo/grass/pull/5660 #5660],
** Reviewed, edited and merged: [https://github.com/OSGeo/grass/pull/3672 #3672]
** Discussed/helped user for: [https://github.com/OSGeo/grass/pull/5678 #5678] and [https://github.com/OSGeo/grass/pull/5684 #5684]
** Long discussion and vision planning for windows scripting with Vaclav, concerning [https://github.com/OSGeo/grass/pull/5624 #5624]. Tested alternatives and tried the consequences of that PR. This older PR finally got merged.
** Created PRs for NSIS installer: [https://github.com/OSGeo/grass/pull/5685 #5685] and also [https://github.com/OSGeo/grass/pull/5686 #5686], which should address [https://github.com/OSGeo/grass/issues/5663 #5663]. Still needs to test it.
** Agreed on convention for titles with Vaclav, unblocking [https://github.com/OSGeo/grass/pull/5341 #5341]
** Found a name with Ondrej and finally merged older PRs of an external contributor [https://github.com/OSGeo/grass/pull/5473 #5473] and [https://github.com/OSGeo/grass/pull/5474 #5474]
* Thursday May 20, 2025:
** Reviewed: [https://github.com/OSGeo/grass/pull/5695 #5695]
** Merged PRs: [https://github.com/OSGeo/grass/pull/5673 #5673], [https://github.com/OSGeo/grass/pull/5691 #5691], [https://github.com/OSGeo/grass/pull/5690 #5690], [https://github.com/OSGeo/grass/pull/5684 #5684],
** Discussed with author of [https://github.com/OSGeo/grass/pull/5660 #5660] and [https://github.com/OSGeo/grass/issues/5659 #5659] about rgb/hsl bug and tests for help.
** Worked with Corey to adjust markdown links for new markdownlint rule, finishing up [https://github.com/OSGeo/grass/pull/5669 #5669]
** Created PRs: [https://github.com/OSGeo/grass/pull/5692 #5692], [https://github.com/OSGeo/grass/pull/5694 #5694], [https://github.com/OSGeo/grass/pull/5689 #5689]
* Wednesday May 21, 2025:
** Created a new set of GitHub rulesets for the required checks, applied with Vaclav. One of them is separated in order to increase velocity during the sprint
** Reviewed the branch protection rules for grass-addons repo with Vaclav. Creating rulesets will be possible after the sprint with the info collected.
** Reviewed the security reporting settings and secret scanning settings with Vaclav for the main grass repo.
** Got shown by Huidae Cho how to update the translation files, and reviewed Weblate settings. No settings changed, but a backup stored for 30 days was kept.
** Created a first implementation of a translation file update workflow
** Tested out the two NSIS installer PRs, the first one, for installing the VC runtime earlier doesn't work as expected, and after more research I don't know enough to fix it. The second PR with High-DPI improvement was correct and got merged [https://github.com/OSGeo/grass/pull/5685 #5685]
** Helped a student set up a grass installation on WSL with conda.
** PRs created: [https://github.com/OSGeo/grass/pull/5736 #5736], [https://github.com/OSGeo/grass/pull/5734 #5734]
** My PRs that got merged: [https://github.com/OSGeo/grass/pull/5685 #5685], [https://github.com/OSGeo/grass/pull/5341 #5341], [https://github.com/OSGeo/grass/pull/5689 #5689]
** Reviewed and merged multiple PRs, restarting failed required checks of the previous night.

=== Laurent Courty ===

* Objectives: An xarray backend for GRASS STRDS. Fixing related issues
* May 20
** Presented itzi
** Uploaded arm64 wheels to PyPI for MacOS and Linux ([https://pypi.org/project/itzi/#files])
** Discussed with other developers about issue #629
* May 21
** Uploaded xarray-grass to PyPI
** Added CI tests to xarray-grass
** Discussed with the group about the xarray-grass backend
** Discussed with the group about solving mapset switching in the temporal framework (issue #629)
** Created PR #5735 to address issue #629
* May 22
** Fix bug in PR #5735

=== Robert S. Dzur | Bohannan Huston, Inc. ===

* r.in.pdal

=== David W. Farris | East Carolina University ===

* A tool to calculate gravity terrain corrections

=== Neel Ghoshal | NC State University ===
• LLM for helping users find tools 
5/19 
• Learnt how to PR (#5674) 
• Setup GRASS on system 
• Found small issue with compilation document 
• Discussed about the possible use case of LLM for helping users find tools 
5/20 
• Learnt about cookie cutter 
• Set up wsl on system 
• Compiled GRASS 
• Listed data sources for LLM training 
5/21 
• Extracted tool information from Markdown files 
• Started off with data cleaning 
5/22 
• Worked on LLM setup 
5/23 
• Ran and finetuned a basic test LLM model for extracted data 

=== Caitlin Haedrich | NC State University ===

* Event photographs, food coordination
* git/github mentoring
* GRASS mentoring
* Lightning Talk preparation
* Preparing workshop for [https://www.geomorphometry2025.org/ Geomorphometry2025]

=== Brendan Harmon | Louisiana State University ===

* Developing ([https://github.com/baharmon/r.earthworks r.earthworks]) addon & tutorials
* [https://github.com/baharmon?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]

=== Linda Karlovska | Czech Technical University in Prague ===

* Fix uninitialized variables in DOutFile() method: ([https://github.com/OSGeo/grass/pull/5650 PR])
* Update figures related to GUI: ([https://github.com/OSGeo/grass/pull/5651 PR])

Working on integration of the Jupyter notebooks to GUI (work for the whole week :-))

=== Martin Landa | Czech Technical University in Prague ===

* Tutorial: GISMentors courses updated ([https://github.com/OSGeo/grass-tutorials/pull/45 PR])
* libgis: G__usage_markdown() include tool label in metadata if defined ([https://github.com/OSGeo/grass/pull/5677 PR])
* PyGRASS: Module description property not defined always ([https://github.com/OSGeo/grass/pull/5681 PR])
* Website: OpenGeoLabs commercial support ([https://github.com/OSGeo/grass-website/pull/537 PR])
* v.select: create output also when no features found ([https://github.com/OSGeo/grass/pull/5696 PR])
* wxGUI: avoid creating nested list of errors (Graphical modeler) ([https://github.com/OSGeo/grass/pull/5700 PR])
* wxGUI/gmodeler: refactor - move ModelParamDialog to dialogs.py ([https://github.com/OSGeo/grass/pull/5715 PR])
* GUI: make Python editor dockable ([https://github.com/OSGeo/grass/pull/5733 PR])
* r.relief: module label changed to description ([https://github.com/OSGeo/grass/pull/5741 PR])
* GUI: propagate previously defined where option value ([https://github.com/OSGeo/grass/pull/5747 PR])
* GUI: always show 'Close dialog on finish' option ([https://github.com/OSGeo/grass/pull/5751 PR])
* GUI: do not remove parameter value on dialog update event ([https://github.com/OSGeo/grass/pull/5760 PR])

=== Nicklas Larsson | Hungarian National Museum ===

Planned work: CMake build system; perhaps Conda recipe

[https://github.com/nilason?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]

* Preparation for CMake build conforming to Filesystem Hierarchy Standard (FHS), resolving resource paths for both the current and FHS in code. In collaboration with Huidae Cho and with important input from Vaclav Petras ([https://github.com/OSGeo/grass/pull/5630 PR5630])

* Helped young students in build configuration and debugging techniques.

* Discussion with several participants on solutions to publish a GRASS package to Conda-forge.

=== Chung-Yuan Liang ===

* parallelize some modules, improve testing

=== Andres Lucero | Bohannan Huston Inc ===

* r.in.pdal

=== Alen Mangafić | Geodetic Institute of Slovenia ===
Monday May 19
* Presentationf of i.hyper, add-on which offers hyperspectral data support in GRASS.
* Architecture of the multi-module addon
Tuesday May 20
* i.hyper.import module: importing EnMAP imagery as 3D raster map
* i.hyper.preproc module: draft
Wednesday May 21
* fixing the i.hyper.import module
* i.hyper.preproc module: implementing Savitzky-Golay filter

=== Helena Mitasova | NC State University ===

* standardized data set and related tutorials
* documentation for interpolation tools
* collaborate/coordinate/discuss hydrology tools (analytics, simulations, soil properties inputs)
* assist with wiki cleanup if needed

Monday May 19
* investigated issues with v.surf.rst documentation in source code, tested and identified fixes needed
* discussed coupling GRASS with Blender versus potree for 3D object rendering with Brendan, Anna and Caitlin (for TL activities and other applications)
* discussed soil data for runoff estimation and other hydro topics, to be worked on on day 2

Tuesday May 20
* worked with Corey on fixing v.surf.rst documentation, discussed ideas for improvements and for documentation / tutorial for cross-valiadation
* discussed suggestions for graphics and examples to be inculded in v.surf.rst docs with Michelle
* discussed new developments in hydrology tools
* experimented with basic/standardized versus specialized data sets for documentation and tutorials

Wednesday May 21
* explored existing tutorials, emailed Paulo about finishing the one on interpolation
* tested NM basic data set with GIS582 class assignment (very cool)
* discussed design of Jnotebooks that would work with various localized data with Caitlin

Thursday May 22
* discussed needed capabilities for a more advanced color ramp processing tool with Brendan
* added further ideas to basic dataset document after talking to Vero - we just need standardized names for the localized tutorials to work
* discussed infiltration fix pull request for r.sim.water with Anna - more work is needed

=== Michael Mulqueen | MassGIS ===

* depth to water, hydro from lidar, etc

=== Māris Nartišs ===

* Taking photos of the event
* Introduced a new GRASS core module r.smooth.edgepreserve
* Discussed architecture of hyperspectral data import and per-processing tool
* Discussed testing and organizing AI modules downloading data from internet
* Prepared and gave a presentation on code preparation for translations (best practice)
* Debugging translation file updating with Edouard
* Changed default multiprocessor setting to always use maximum number of available threads
* Unified max process setting handling in all modules that use default parser parameter
* Discovered and supervised fixing a bug in r.univar parallelization code
* Discussing requirements for raster data reading parallelization (GRASS 9)

=== Ondřej Pešek | Czech Technical University in Prague ===

* [https://github.com/pesekon2?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* Refactoring, fixing, improving, discussing g.gui.gmodeler
* Discussing hyperspectral with Alen Mangafic
* Discussing jupyter in single GUI with Linda Karlovska
* PyGRASS
* Docs
* CQ
* Reviewing PRs, PR archeology

=== Vaclav (Vashek) Petras | NC State University ===

* [https://github.com/wenzeslaus?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* My focus: Getting feedback and ideas for computational engine use case, APIs, funding.
* Summit organizing
* Implementing rebranding on GitHub (repos, teams)
* Feedback session on project image
* Feedback session on easier access to tools
* Discussed LLMs with Neel Ghoshal, Riya
* Discussed session setupp Martin Landa
* Discussed conda with Nicklas Larsson
* Discussed hyperspectral with Alen Mangafić, Veronica Andreo, and Anna Petrasova
* Discussed code for new smoothing tool, integer overflows, translations with Māris Nartišs
* Compared setup of GRASS session and project in fasterRaster, QGIS, and GRASS itself with Adam Smith
* Discussed potential of Pixi for packaging or compilation with Gregory Power
* Discussed itzi model distribution issues with Laurent Courty
* Discussed r.horizon parallelization with Chung-Yuan Liang and Anna Petrasova
* Answered coding and setup questions for Neel Ghoshal, Abdullah Azzam, and Alen Mangafić

=== Anna Petrasova | NC State University ===

* [https://github.com/petrasovaa?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* plan: mentoring, documentation
* Monday
** discussing hyperspectral implementation with Alen
** helping mentee David Farris implementing his gravity correction addon
* Tuesday
** delivered intro to creating an addon, documentation
** mentoring Alen, Abdullah
** discussing bug in i.his.rgb with Jayneel
** reviews
* Wednesday
** discuss and demonstrate tutorials page
** mentoring Alen, Jayneel
* call with GSoC student
* Thursday
* Friday
** grass repo README
** reviews

=== Gregory Power | Town of Cary ===

* Documentation

=== Pratikshya Regmi | NC State University ===

* Event photographs and videos
* Opened a pull request to change GRASS GIS to GRASS on the documentation (this was my first contribution to GRASS)
* Worked on preparing the mock document for LLM RAG
* Wrote a tutorial to Visualize Contour Lines with a Color Gradient with Folium.

=== Riya | Indian Institute of Technology, Roorkee ===

* I am currently thinking of developing an AI Agent for the grass jupyter library which will help the users with mathematical calculations done in GIS.

=== Jayneel Shah | NC State University ===

* improve the test coverage of imagery modules.

=== Krishna Prasad Sheshadri ===

*

=== Adam Smith | Missouri Botanical Garden ===

Overall: R package fasterRaster (fielding bug reports, adding features)

Monday:
* Assessed scope of fasterRaster issue [https://github.com/adamlilith/fasterRaster/issues/83 83]

Tuesday:
* Created a PR for fasterRaster tutorial on GRASS tutorials page.
* Improved handling of addons, including autodetect and installing when needed, enabling easier creation of addon-dependent methods.
* Presented *fasterRaster* package to group.

Wednesday:
* Created fasterRaster methods for neighborhood matrices, terrain ruggedness index, and multivariate environmental similarity

=== Michelle (Mimi) Stephens | ERDC ===

* Previous work: coupling R and Python scripts for computational analysis in GRASS.
* Current work: Running through GRASS commands to create visual outputs that can be added to the new GRASS 8.5 manual pages - r.mapcalc, v.surf.rst, examples with topographic parameters, LinkedIn requests.
* Tutorial for Windows users to install a WSL2 Linux environment. Creates a conda environment with wxpython, installs GRASS without requiring OSGeo installer. Fast, simple, and minimal install. Resolves various issues encountered in government due to automatic Windows updates, cyber security, vpn routing, user preference, and isolated distro can be completely removed if needed. -> Motivation for WSL2 - wanted more hands-on practice with Unix command line tools for HPC; Docker not allowed, but miniforge and Apptainer are on ERDC's HPC; able to install grass via command line (only on internet-capable HPC systems); AND - For other users that always wanted a more native feel to their grass instance!
* Future work: Presenting on GRASS in JUNE at CERLCON.

=== Corey White | NC State University ===

* JSON, mentoring

=== Doug Newcomb | Semi Retired Cartographer ===

* Discussed hydroflattening method
* Discussed direct point cloud input to v.surf.rst
* Learning git procedures by updating branding (GRASS GIS to GRASS) for raster commands
Tuesday
* Continued updating branding for raster commands
* Started working on tutorial for r.hydro.flatten

=== Natalie Trso | Balance Geo LLC ===

* r.sim.water

== Guests and remote participants ==

=== Luís de Sousa | University of Lisbon ===

* Review outstanding PRs
* Prepare GRASS sessions for the OpenGeoHub Summer School

=== Markus Neteler | mundialis ===

* Support full automation of new GRASS manual pages deployment on server (upload artifacts from GitHub to OSGeo servers (grass and download))
* Source code license documentation: Using SPDX License IDs ({{GH-Issues|4190}})
* Support Wiki cleanup
* [https://github.com/neteler?tab=overview&from=2025-05-19&to=2025-05-24 GitHub contributions]

=== Nishant Bansal | Indian Institute of Technology, Varanasi ===

* Review the previous work on JSON during last year’s GSoC, including enhancements and the addition of JSON output support to other modules.

Talk:GRASS Developer Summit Raleigh 2025

2025-05-23T21:17:47Z

Annakrat: /* Day 6, Saturday, May 24 */

{{toc|right}}

Quick links: [[GRASS Developer Summit Raleigh 2025|Meeting page]] | [[#Participant_reports|Reports]] | [[GRASS_Developer_Summit_Raleigh_2025#Sponsors|Sponsors]]

== Organizing Team ==

* Initial planning: Vaclav Petras, Anna Petrasova, Veronica Andreo, Corey White, Lois Utt, Sarah White, Doug Newcomb, Huidae Cho, Veronica Andreo ([[GRASS_Developer_Summit_Raleigh_2025#Organizing_Committee|Organizing Committee]])
* Budget: Vaclav Petras, Lois Utt, Anna Petrasova
* Raising support: Helena Mitasova, Vaclav Petras, Anna Petrasova, Michael Barton, Giuseppe Amatulli ([[NSF POSE Project 2023-2025 Timeline|NSF POSE project]] proposal authors)
* Travel: Lois Utt
* Venue: Vaclav Petras, Lois Utt
* Meals: Lois Utt, Sarah White, Vaclav Petras, Corey White, Anna Petrasova
* Agenda: Vaclav Petras, Huidae Cho, Anna Petrasova
* Wiki page: Vaclav Petras, Anna Petrasova
* Swag: Sarah White, Vaclav Petras, Anna Petrasova, Corey White
* Promotion, invitations, and social media: Vaclav Petras, Sarah White, Corey White, John Vogler
* Lightning talks organization: Vaclav Petras, Zachary Arcaro, John Vogler
* Lightning talk speakers: Vaclav Petras (welcome), Markus Metz and Markus Neteler (talk presented by Vaclav Petras), Anna Petrasova, Veronica Andreo, Robert Dzur, Nick Brady, Huidae Cho, Gregory Power, Doug Newcomb, Caitlin Haedrich
* Photography: Caitlin Haedrich, Māris Nartišs, Pratikshya Regmi
* Portrait photography: Riya, Caitlin Haedrich, Natalie Trso

== Detailed Schedule ==

=== Day 1, Monday, May 19 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Contributing to GRASS. Getting started. Is it easy to contribute?''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-9:00 || Breakfast || Catered breakfast on site. Meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || What to expect from the event, contributing to GRASS using Git and GitHub, making your first contribution.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || i.hyper: Integrating Hyperspectral Imagery Processing into GRASS - Alen Mangafić
|-
| 11:20-11:40 || Self-organized feedback sessions ||
|-
| 11:40-12:00 || Self-organized feedback sessions || Project Image - Vaclav Petras
|-
| 12:00-13:00 || Lunch || Catered food on site.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || We will walk to [https://www.trophybrewing.com/brewing-pizza Trophy Brewing & Pizza] ([https://maps.app.goo.gl/ggnZ7EvXbWqDUmvP9 directions], 30 min walk from Talley)
|}

=== Day 2, Tuesday, May 20 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topics: ''Hydrology and Interfacing with R and QGIS (gathering user feedback, testing, discussing with developers, developing action items)''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-9:00 || Breakfast || Breakfast on site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Introduction to writing GRASS tools, program for the day.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || fasterRaster R package - Adam Smith
|-
| 11:20-11:40 || Self-organized feedback sessions || Hydography90m + Geocomputation Courses - Giuseppe
|-
| 11:40-12:00 || Self-organized feedback sessions || Flood modelling with grass and itzi ([https://itzi.org]) - Laurent Courty
|-
| 12:00-13:00 || Lunch || [https://maps.app.goo.gl/womSkce9DrE8CTnR8 Case dining hall]
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/CQiWoCAQNt1ymZkb7 Served in Jordan Hall at the Center for Geospatial Analytics], evaluate the day's accomplishments, plan and prioritize for the next few days.
|}

=== Day 3, Wednesday, May 21 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Non-coding contributions, natural language translation, and internationalization.''

{| class="wikitable"
! Time !! Slot !!
|-
| 7:00-9:00 || Breakfast || [https://maps.app.goo.gl/eZ8VK8Mx6TjMt9NP8 Case dining hall]
|-
| 9:00-10:00 || Morning opening sessions || Introduction to non-coding contributions, tutorials, contributing examples, natural language translation and internationalization (procedures, glossaries, code customization, translation).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Easier access to GRASS tools - Vaclav Petras
|-
| 11:20-11:40 || Self-organized feedback sessions ||
|-
| 11:40-12:00 || Self-organized feedback sessions || GRASS backend for xarray and temporal framework global variables ([https://github.com/OSGeo/grass/issues/629]) - Laurent Courty
|-
| 12:00-13:00 || Lunch || Served on site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/1E39eySMVaxYJUUS8 Picnic at Pullen Park, shelter #3. In case of bad weather, dinner at the Center for Geospatial Analytics.
|}

=== Day 4, Thursday, May 22 ===

Location: Center for Geospatial Analytics, Jordan Hall, 2800 Faucette Drive ([https://www.google.com/maps/search/Jordan+Hall/@35.7816832,-78.6772765,18z/data=!3m1!4b1?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: 5103 (straight from the two elevators, at the end of the hallway)

Highlighted topic: ''Project vision and computational engine use case.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || On site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Project vision and the computational engine use case (missing features, documentation, user groups).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || NSF POSE I-Corps Interviews - Corey White
|-
| 11:20-11:40 || Self-organized feedback session || YAIT - Yet Another Interface to Tools - Vaclav Petras
|-
| 11:40-12:00 || Self-organized feedback session || Modernizing Color Tables (Brendan)
|-
| 12:00-13:00 || Lunch || On site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-16:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 16:00-17:00 || Lightning talks || Fast-paced talks, showcasing applications of GRASS, room 5111.
|-
| 18:00 || Reception || Connect with researchers, government professionals, and industry collaborators, rooms 5111 and 5119.
|}

=== Day 5, Friday, May 23 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topic: ''GRASS project's future course.''

{| class="wikitable"
! Time !! Slot !!
|-
| 7:45-8:15 || Breakfast || '''Hotel Aloft (2nd floor).''' Search for Lois!
|-
| 9:00-10:00 || Morning opening sessions || GRASS project's future course.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-12:00 || PSC meeting || Project Steering Committee meets (public).
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Rescheduled for Saturday

|-
| 12:00-13:00 || Lunch || Walk to [https://maps.app.goo.gl/kHVHY62QxTd6wHKd9 On the Oval Culinary Creations]. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || Dinner on your own. Corey White will organize trip to downtown. Bus 41 from Hunt library to hotel and then walk.
|}

=== Day 6, Saturday, May 24 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topics: ''NSF POSE project evaluation.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-8:30 || Breakfast || We will have pastries at [https://maps.app.goo.gl/EwzNxeovv4rTivjK9 Lake Raleigh]. Feel free to bring your own coffee.
|-
| 8:30-10:00 || Hike || Library opens at 10AM.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || GRASS tools: core and additional functionality (MartinL)
|-
| 12:00-13:00 || Lunch || TBA. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || TBA.
|}

== Daily tasks for participants ==

* List all the things you are working on in the Participant reports section below. Update the list each day. Include things you work on with other people.
* If you want to discuss something with the whole group, add yourself to a Self-organized feedback sessions slot in the schedule above or tell Vaclav (Vashek) Petras.
* For people with triage access and above: If you are or will be working on an issue or on a PR which is not originally submitted by you, assign yourself to the issue or PR. (You can unassign yourself later if you change your mind.)

== Participant reports ==

Per-person reports from the meeting.

=== Giuseppe Amatulli | Yale University ===

* Testing r.watershed and r.stream.* for handling large datasets
* Running r.flowaccumulation at global level using water direction from hydrography90m
* Preparing the grass tutorial material for the https://www.geomorphometry2025.org/ conference

=== Veronica Andreo | CONICET - Instituto Gulich ===

* [https://github.com/veroandreo?tab=overview&from=2025-05-12&to=2025-05-24 GitHub contributions]
* Enhanced the website footer.
* Sync icons on the Tutorials website footer to those on the main website.
* Fix descriptions and their display on the tutorials website.
* Fix GRASS page on OSGeo website [https://www.osgeo.org/projects/grass-gis/]
** Changed logo, removed GIS from the name, fixed old links.
* Social media posts.
* Discussion about hyperspectral with Alen and Anna.
* Expand the GRASS acronym on the home page.
* Remove GIS from GRASS name on the website.
* Review tutorials by Huidae and Adam Smith.
* Add external tutorials by Huidae and the one from FOSS4G 2024.
* Started adding the time series tutorials.
* Add lightbox class in get-started tutorials so images can be clicked on.
* GRASS PSC admin stuff.
* Participated of the PSC meeting.
* Talk to Tonis Kardi from FOSS4G EU LOC to have a "State of GRASS" talk in the program. Alen will be presenting.
* Gave a lightning talk: GRASS-fed species distribution models.
* Discussed with Corey and Mimi about tutorials.

=== Abdullah Azzam | New Mexico State University ===

* Created first PR; fixed broken links on the website [https://github.com/OSGeo/grass-website/pull/538 #538]
* Pushed a new GRASS Addon ''r.curvenumber'' [https://github.com/OSGeo/grass-addons/pull/1403 #1403]

=== Michael Barton | Arizona State University ===

* POSE related activities

=== Laura Belica | NC State University ===

* have been working on developing a workflow-tool tutorial template that facilitates GRASS learners who tend to 'jump in' or have a 'choose your own adventure' approach to learning GRASS (i.e., want to use their data for their study area for their objective from the start). The structure of the tutorial template is a concise, basic, general description/instructions of the workflow with optional links to pertinent explanatory/deeper dive content (e.g., plain language explainers of the tool, options, defaults, etc.) in a variety of formats (e.g., captioned images, short tool demo videos (30 sec to 2 min)) in addition to the more comprehensive resources available (e.g. documentation, examples, tutorials). The main motivation for this approach is to help new and occasional GRASS users avoid some of the common pitfalls and to learn how to find workarounds for some of the unanticipated challenges they may encounter with their specific datasets or use cases so that they can learn as they go. Another motivation for this approach is to facilitate the translation, extension, and updating of workflow tutorials by the community over time (e.g., providing audio and closed captioning for one of the tool-demo videos in another language, replacing an outdated GUI demo with one for the current release, or incorporating a new add-on as an option in the workflow).

* my focus this week is on developing a draft/test tutorial (in Quarto) for a standard hydrological modelling workflow that begins with the crucial pre-work of how to figure out the appropriate project/location, etc. as well as considerations of some of the downstream impacts of resolution, extent, region etc. It may not be ready for sharing by the end of the week, but suggestions and advice are welcomed in advance.

19 May
* discussed a novice user issue with 'moving' vector data from one location to another with Vero and learned a neat GUI option
* revised and added workflow tutorial text

=== Shonil Sateesh Bhide | NC State University ===

* CI optimization

=== Huidae Cho | New Mexico State University ===

* CMake, conda, CI, Mentoring

Monday 5/19
* [https://github.com/OSGeo/grass/pull/5680 CMake: Recognize conda installation path at runtime]: Replaced by [https://github.com/HuidaeCho/grass-conda/blob/master/recipe/post-link.sh conda post-link.sh]
* CMake and Conda Testing on Linux
* CMake Testing on Windows
* Mentoring: Chung-Yuan, Abdullah

Tuesday 5/20
* [https://github.com/OSGeo/grass/pull/5712 CMake: Define custom complex types for MSVC LAPACKE]
* [https://github.com/OSGeo/grass/pull/5713 CMake: Fix build output directories for MSVC]
* CMake and Conda Testing on Linux
* CMake Testing on Windows

Wednesday 5/21
* Translation Talk
* Translation Discussion with Edouard
* Flow Direction Meeting with Ondrej, Ondrej's Student, Martin, and Markus Metz
* CMake and Conda Testing on Linux
* CMake Testing on Windows
* Mentoring: Chung-Yuan, Abdullah

Thursday 5/22
* [https://github.com/OSGeo/grass/pull/5740 CMake: Fix the parameter is incorrect: . error for MSVC]
* Lightning Talk
* CMake and Conda Testing on Linux
* CMake Testing on Windows
* CI: Discussion with Edouard
* Mentoring: Chung-Yuan, Abdullah

=== Edouard Choinière ===

* Quick ideas, way too much for a week: Helping others (may take a reasonable part of the time), managing CI, setting up localization template updating workflow, backporting tool? Pytest/coverage improvements? Discuss and design other projects, to work on during the year. Open to change on other priorities once there, anything that is useful. Maybe make a little progress on high dpi GUI, especially on Windows.

* Weekend before sprint:
** Clear up Renovate PRs to not use CI time during the sprint, reviewing and merging: [https://github.com/OSGeo/grass/pull/5664 #5664], [https://github.com/OSGeo/grass/pull/5665 #5665], [https://github.com/OSGeo/grass/pull/5666 #5666], [https://github.com/OSGeo/grass/pull/5667 #5667], [https://github.com/OSGeo/grass/pull/5668 #5668]
** PR to avoid some CI run time for the sprint: [https://github.com/OSGeo/grass/pull/5670 #5670]
** Reviewed open PRs for PRs that were mergeable before the sprint, updated outdated PRs to avoid having it needing CI time during sprint. Only ended up merging [https://github.com/OSGeo/grass/pull/5658 #5658], but another reviewed one that might still need changes: [https://github.com/OSGeo/grass/pull/5628 #5628]
* Monday May 19, 2025:
** PR got merged: [https://github.com/OSGeo/grass/pull/5670 #5670],[https://github.com/OSGeo/grass/pull/5550 #5550]
** Reviewed PRs: [https://github.com/OSGeo/grass/pull/5671 #5671], [https://github.com/OSGeo/grass/pull/5672 #5672]
** Discussions:
*** Shonil Sateesh Bhid & Shuham on their CI & pytest work and project.
*** Māris Nartišs about a potential issue and improvement for it. Will be discussed in the security reporting tab, also allowing to test the security vulnerability reporting process. + Research on existing solutions
** Reviewed: [https://github.com/OSGeo/grass/pull/5682 #5682], [https://github.com/OSGeo/grass/pull/5660 #5660],
** Reviewed, edited and merged: [https://github.com/OSGeo/grass/pull/3672 #3672]
** Discussed/helped user for: [https://github.com/OSGeo/grass/pull/5678 #5678] and [https://github.com/OSGeo/grass/pull/5684 #5684]
** Long discussion and vision planning for windows scripting with Vaclav, concerning [https://github.com/OSGeo/grass/pull/5624 #5624]. Tested alternatives and tried the consequences of that PR. This older PR finally got merged.
** Created PRs for NSIS installer: [https://github.com/OSGeo/grass/pull/5685 #5685] and also [https://github.com/OSGeo/grass/pull/5686 #5686], which should address [https://github.com/OSGeo/grass/issues/5663 #5663]. Still needs to test it.
** Agreed on convention for titles with Vaclav, unblocking [https://github.com/OSGeo/grass/pull/5341 #5341]
** Found a name with Ondrej and finally merged older PRs of an external contributor [https://github.com/OSGeo/grass/pull/5473 #5473] and [https://github.com/OSGeo/grass/pull/5474 #5474]
* Thursday May 20, 2025:
** Reviewed: [https://github.com/OSGeo/grass/pull/5695 #5695]
** Merged PRs: [https://github.com/OSGeo/grass/pull/5673 #5673], [https://github.com/OSGeo/grass/pull/5691 #5691], [https://github.com/OSGeo/grass/pull/5690 #5690], [https://github.com/OSGeo/grass/pull/5684 #5684],
** Discussed with author of [https://github.com/OSGeo/grass/pull/5660 #5660] and [https://github.com/OSGeo/grass/issues/5659 #5659] about rgb/hsl bug and tests for help.
** Worked with Corey to adjust markdown links for new markdownlint rule, finishing up [https://github.com/OSGeo/grass/pull/5669 #5669]
** Created PRs: [https://github.com/OSGeo/grass/pull/5692 #5692], [https://github.com/OSGeo/grass/pull/5694 #5694], [https://github.com/OSGeo/grass/pull/5689 #5689]
* Wednesday May 21, 2025:
** Created a new set of GitHub rulesets for the required checks, applied with Vaclav. One of them is separated in order to increase velocity during the sprint
** Reviewed the branch protection rules for grass-addons repo with Vaclav. Creating rulesets will be possible after the sprint with the info collected.
** Reviewed the security reporting settings and secret scanning settings with Vaclav for the main grass repo.
** Got shown by Huidae Cho how to update the translation files, and reviewed Weblate settings. No settings changed, but a backup stored for 30 days was kept.
** Created a first implementation of a translation file update workflow
** Tested out the two NSIS installer PRs, the first one, for installing the VC runtime earlier doesn't work as expected, and after more research I don't know enough to fix it. The second PR with High-DPI improvement was correct and got merged [https://github.com/OSGeo/grass/pull/5685 #5685]
** Helped a student set up a grass installation on WSL with conda.
** PRs created: [https://github.com/OSGeo/grass/pull/5736 #5736], [https://github.com/OSGeo/grass/pull/5734 #5734]
** My PRs that got merged: [https://github.com/OSGeo/grass/pull/5685 #5685], [https://github.com/OSGeo/grass/pull/5341 #5341], [https://github.com/OSGeo/grass/pull/5689 #5689]
** Reviewed and merged multiple PRs, restarting failed required checks of the previous night.

=== Laurent Courty ===

* Objectives: An xarray backend for GRASS STRDS. Fixing related issues
* May 20
** Presented itzi
** Uploaded arm64 wheels to PyPI for MacOS and Linux ([https://pypi.org/project/itzi/#files])
** Discussed with other developers about issue #629
* May 21
** Uploaded xarray-grass to PyPI
** Added CI tests to xarray-grass
** Discussed with the group about the xarray-grass backend
** Discussed with the group about solving mapset switching in the temporal framework (issue #629)
** Created PR #5735 to address issue #629
* May 22
** Fix bug in PR #5735

=== Robert S. Dzur | Bohannan Huston, Inc. ===

* r.in.pdal

=== David W. Farris | East Carolina University ===

* A tool to calculate gravity terrain corrections

=== Neel Ghoshal | NC State University ===
• LLM for helping users find tools 
5/19 
• Learnt how to PR (#5674) 
• Setup GRASS on system 
• Found small issue with compilation document 
• Discussed about the possible use case of LLM for helping users find tools 
5/20 
• Learnt about cookie cutter 
• Set up wsl on system 
• Compiled GRASS 
• Listed data sources for LLM training 
5/21 
• Extracted tool information from Markdown files 
• Started off with data cleaning 
5/22 
• Worked on LLM setup 
5/23 
• Ran and finetuned a basic test LLM model for extracted data 

=== Caitlin Haedrich | NC State University ===

* Event photographs, food coordination
* git/github mentoring
* GRASS mentoring
* Lightning Talk preparation
* Preparing workshop for [https://www.geomorphometry2025.org/ Geomorphometry2025]

=== Brendan Harmon | Louisiana State University ===

* Developing ([https://github.com/baharmon/r.earthworks r.earthworks]) addon & tutorials
* [https://github.com/baharmon?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]

=== Linda Karlovska | Czech Technical University in Prague ===

* Fix uninitialized variables in DOutFile() method: ([https://github.com/OSGeo/grass/pull/5650 PR])
* Update figures related to GUI: ([https://github.com/OSGeo/grass/pull/5651 PR])

Working on integration of the Jupyter notebooks to GUI (work for the whole week :-))

=== Martin Landa | Czech Technical University in Prague ===

* Tutorial: GISMentors courses updated ([https://github.com/OSGeo/grass-tutorials/pull/45 PR])
* libgis: G__usage_markdown() include tool label in metadata if defined ([https://github.com/OSGeo/grass/pull/5677 PR])
* PyGRASS: Module description property not defined always ([https://github.com/OSGeo/grass/pull/5681 PR])
* Website: OpenGeoLabs commercial support ([https://github.com/OSGeo/grass-website/pull/537 PR])
* v.select: create output also when no features found ([https://github.com/OSGeo/grass/pull/5696 PR])
* wxGUI: avoid creating nested list of errors (Graphical modeler) ([https://github.com/OSGeo/grass/pull/5700 PR])
* wxGUI/gmodeler: refactor - move ModelParamDialog to dialogs.py ([https://github.com/OSGeo/grass/pull/5715 PR])
* GUI: make Python editor dockable ([https://github.com/OSGeo/grass/pull/5733 PR])
* r.relief: module label changed to description ([https://github.com/OSGeo/grass/pull/5741 PR])
* GUI: propagate previously defined where option value ([https://github.com/OSGeo/grass/pull/5747 PR])
* GUI: always show 'Close dialog on finish' option ([https://github.com/OSGeo/grass/pull/5751 PR])
* GUI: do not remove parameter value on dialog update event ([https://github.com/OSGeo/grass/pull/5760 PR])

=== Nicklas Larsson | Hungarian National Museum ===

Planned work: CMake build system; perhaps Conda recipe

[https://github.com/nilason?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]

* Preparation for CMake build conforming to Filesystem Hierarchy Standard (FHS), resolving resource paths for both the current and FHS in code. In collaboration with Huidae Cho and with important input from Vaclav Petras ([https://github.com/OSGeo/grass/pull/5630 PR5630])

* Helped young students in build configuration and debugging techniques.

* Discussion with several participants on solutions to publish a GRASS package to Conda-forge.

=== Chung-Yuan Liang ===

* parallelize some modules, improve testing

=== Andres Lucero | Bohannan Huston Inc ===

* r.in.pdal

=== Alen Mangafić | Geodetic Institute of Slovenia ===
Monday May 19
* Presentationf of i.hyper, add-on which offers hyperspectral data support in GRASS.
* Architecture of the multi-module addon
Tuesday May 20
* i.hyper.import module: importing EnMAP imagery as 3D raster map
* i.hyper.preproc module: draft
Wednesday May 21
* fixing the i.hyper.import module
* i.hyper.preproc module: implementing Savitzky-Golay filter

=== Helena Mitasova | NC State University ===

* standardized data set and related tutorials
* documentation for interpolation tools
* collaborate/coordinate/discuss hydrology tools (analytics, simulations, soil properties inputs)
* assist with wiki cleanup if needed

Monday May 19
* investigated issues with v.surf.rst documentation in source code, tested and identified fixes needed
* discussed coupling GRASS with Blender versus potree for 3D object rendering with Brendan, Anna and Caitlin (for TL activities and other applications)
* discussed soil data for runoff estimation and other hydro topics, to be worked on on day 2

Tuesday May 20
* worked with Corey on fixing v.surf.rst documentation, discussed ideas for improvements and for documentation / tutorial for cross-valiadation
* discussed suggestions for graphics and examples to be inculded in v.surf.rst docs with Michelle
* discussed new developments in hydrology tools
* experimented with basic/standardized versus specialized data sets for documentation and tutorials

Wednesday May 21
* explored existing tutorials, emailed Paulo about finishing the one on interpolation
* tested NM basic data set with GIS582 class assignment (very cool)
* discussed design of Jnotebooks that would work with various localized data with Caitlin

Thursday May 22
* discussed needed capabilities for a more advanced color ramp processing tool with Brendan
* added further ideas to basic dataset document after talking to Vero - we just need standardized names for the localized tutorials to work
* discussed infiltration fix pull request for r.sim.water with Anna - more work is needed

=== Michael Mulqueen | MassGIS ===

* depth to water, hydro from lidar, etc

=== Māris Nartišs ===

* Taking photos of the event
* Introduced a new GRASS core module r.smooth.edgepreserve
* Discussed architecture of hyperspectral data import and per-processing tool
* Discussed testing and organizing AI modules downloading data from internet
* Prepared and gave a presentation on code preparation for translations (best practice)
* Debugging translation file updating with Edouard
* Changed default multiprocessor setting to always use maximum number of available threads
* Unified max process setting handling in all modules that use default parser parameter
* Discovered and supervised fixing a bug in r.univar parallelization code
* Discussing requirements for raster data reading parallelization (GRASS 9)

=== Ondřej Pešek | Czech Technical University in Prague ===

* [https://github.com/pesekon2?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* Refactoring, fixing, improving, discussing g.gui.gmodeler
* Discussing hyperspectral with Alen Mangafic
* Discussing jupyter in single GUI with Linda Karlovska
* PyGRASS
* Docs
* CQ
* Reviewing PRs, PR archeology

=== Vaclav (Vashek) Petras | NC State University ===

* [https://github.com/wenzeslaus?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* My focus: Getting feedback and ideas for computational engine use case, APIs, funding.
* Summit organizing
* Implementing rebranding on GitHub (repos, teams)
* Feedback session on project image
* Feedback session on easier access to tools
* Discussed LLMs with Neel Ghoshal, Riya
* Discussed session setupp Martin Landa
* Discussed conda with Nicklas Larsson
* Discussed hyperspectral with Alen Mangafić, Veronica Andreo, and Anna Petrasova
* Discussed code for new smoothing tool, integer overflows, translations with Māris Nartišs
* Compared setup of GRASS session and project in fasterRaster, QGIS, and GRASS itself with Adam Smith
* Discussed potential of Pixi for packaging or compilation with Gregory Power
* Discussed itzi model distribution issues with Laurent Courty
* Discussed r.horizon parallelization with Chung-Yuan Liang and Anna Petrasova
* Answered coding and setup questions for Neel Ghoshal, Abdullah Azzam, and Alen Mangafić

=== Anna Petrasova | NC State University ===

* [https://github.com/petrasovaa?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* plan: mentoring, documentation
* Monday
** discussing hyperspectral implementation with Alen
** helping mentee David Farris implementing his gravity correction addon
* Tuesday
** delivered intro to creating an addon, documentation
** mentoring Alen, Abdullah
** discussing bug in i.his.rgb with Jayneel
** reviews
* Wednesday
** discuss and demonstrate tutorials page
** mentoring Alen, Jayneel
* call with GSoC student

=== Gregory Power | Town of Cary ===

* Documentation

=== Pratikshya Regmi | NC State University ===

* Event photographs and videos
* Opened a pull request to change GRASS GIS to GRASS on the documentation (this was my first contribution to GRASS)
* Worked on preparing the mock document for LLM RAG
* Wrote a tutorial to Visualize Contour Lines with a Color Gradient with Folium.

=== Riya | Indian Institute of Technology, Roorkee ===

* I am currently thinking of developing an AI Agent for the grass jupyter library which will help the users with mathematical calculations done in GIS.

=== Jayneel Shah | NC State University ===

* improve the test coverage of imagery modules.

=== Krishna Prasad Sheshadri ===

*

=== Adam Smith | Missouri Botanical Garden ===

Overall: R package fasterRaster (fielding bug reports, adding features)

Monday:
* Assessed scope of fasterRaster issue [https://github.com/adamlilith/fasterRaster/issues/83 83]

Tuesday:
* Created a PR for fasterRaster tutorial on GRASS tutorials page.
* Improved handling of addons, including autodetect and installing when needed, enabling easier creation of addon-dependent methods.
* Presented *fasterRaster* package to group.

Wednesday:
* Created fasterRaster methods for neighborhood matrices, terrain ruggedness index, and multivariate environmental similarity

=== Michelle (Mimi) Stephens | ERDC ===

* Previous work: coupling R and Python scripts for computational analysis in GRASS.
* Current work: Running through GRASS commands to create visual outputs that can be added to the new GRASS 8.5 manual pages - r.mapcalc, v.surf.rst, examples with topographic parameters, LinkedIn requests.
* Tutorial for Windows users to install a WSL2 Linux environment. Creates a conda environment with wxpython, installs GRASS without requiring OSGeo installer. Fast, simple, and minimal install. Resolves various issues encountered in government due to automatic Windows updates, cyber security, vpn routing, user preference, and isolated distro can be completely removed if needed. -> Motivation for WSL2 - wanted more hands-on practice with Unix command line tools for HPC; Docker not allowed, but miniforge and Apptainer are on ERDC's HPC; able to install grass via command line (only on internet-capable HPC systems); AND - For other users that always wanted a more native feel to their grass instance!
* Future work: Presenting on GRASS in JUNE at CERLCON.

=== Corey White | NC State University ===

* JSON, mentoring

=== Doug Newcomb | Semi Retired Cartographer ===

* Discussed hydroflattening method
* Discussed direct point cloud input to v.surf.rst
* Learning git procedures by updating branding (GRASS GIS to GRASS) for raster commands
Tuesday
* Continued updating branding for raster commands
* Started working on tutorial for r.hydro.flatten

=== Natalie Trso | Balance Geo LLC ===

* r.sim.water

== Guests and remote participants ==

=== Luís de Sousa | University of Lisbon ===

* Review outstanding PRs
* Prepare GRASS sessions for the OpenGeoHub Summer School

=== Markus Neteler | mundialis ===

* Support full automation of new GRASS manual pages deployment on server (upload artifacts from GitHub to OSGeo servers (grass and download))
* Source code license documentation: Using SPDX License IDs ({{GH-Issues|4190}})
* Support Wiki cleanup
* [https://github.com/neteler?tab=overview&from=2025-05-19&to=2025-05-24 GitHub contributions]

=== Nishant Bansal | Indian Institute of Technology, Varanasi ===

* Review the previous work on JSON during last year’s GSoC, including enhancements and the addition of JSON output support to other modules.

Talk:GRASS Developer Summit Raleigh 2025

2025-05-21T18:45:41Z

Annakrat: /* Anna Petrasova | NC State University */

{{toc|right}}

Quick links: [[GRASS Developer Summit Raleigh 2025|Meeting page]] | [[#Participant_reports|Reports]] | [[GRASS_Developer_Summit_Raleigh_2025#Sponsors|Sponsors]]

== Organizing Team ==

* Initial planning: Vaclav Petras, Anna Petrasova, Veronica Andreo, Corey White, Lois Utt, Sarah White, Doug Newcomb, Huidae Cho, Veronica Andreo ([[GRASS_Developer_Summit_Raleigh_2025#Organizing_Committee|Organizing Committee]])
* Budget: Vaclav Petras, Lois Utt, Anna Petrasova
* Raising support: Helena Mitasova, Vaclav Petras, Anna Petrasova, Michael Barton, Giuseppe Amatulli ([[NSF POSE Project 2023-2025 Timeline|NSF POSE project]] proposal authors)
* Travel: Lois Utt
* Venue: Vaclav Petras, Lois Utt
* Meals: Lois Utt, Sarah White, Vaclav Petras, Corey White, Anna Petrasova
* Agenda: Vaclav Petras, Huidae Cho, Anna Petrasova
* Wiki page: Vaclav Petras, Anna Petrasova
* Swag: Sarah White, Vaclav Petras, Anna Petrasova, Corey White
* Promotion, invitations, and social media: Vaclav Petras, Sarah White, Corey White, John Vogler
* Lightning talks organization: Vaclav Petras, Zachary Arcaro, John Vogler
* Lightning talk speakers: Vaclav Petras (welcome), Markus Metz and Markus Neteler (talk presented by Vaclav Petras), Anna Petrasova, Veronica Andreo, Robert Dzur, Nick Brady, Huidae Cho, Gregory Power, Doug Newcomb, Caitlin Haedrich
* Photography: Caitlin Haedrich, Māris Nartišs, Pratikshya Regmi

== Detailed Schedule ==

=== Day 1, Monday, May 19 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Contributing to GRASS. Getting started. Is it easy to contribute?''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-9:00 || Breakfast || Catered breakfast on site. Meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || What to expect from the event, contributing to GRASS using Git and GitHub, making your first contribution.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || i.hyper: Integrating Hyperspectral Imagery Processing into GRASS - Alen Mangafić
|-
| 11:20-11:40 || Self-organized feedback sessions ||
|-
| 11:40-12:00 || Self-organized feedback sessions || Project Image - Vaclav Petras
|-
| 12:00-13:00 || Lunch || Catered food on site.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || We will walk to [https://www.trophybrewing.com/brewing-pizza Trophy Brewing & Pizza] ([https://maps.app.goo.gl/ggnZ7EvXbWqDUmvP9 directions], 30 min walk from Talley)
|}

=== Day 2, Tuesday, May 20 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topics: ''Hydrology and Interfacing with R and QGIS (gathering user feedback, testing, discussing with developers, developing action items)''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-9:00 || Breakfast || Breakfast on site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Introduction to writing GRASS tools, program for the day.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || fasterRaster R package - Adam Smith
|-
| 11:20-11:40 || Self-organized feedback sessions || Hydography90m + Geocomputation Courses - Giuseppe
|-
| 11:40-12:00 || Self-organized feedback sessions || Flood modelling with grass and itzi ([https://itzi.org]) - Laurent Courty
|-
| 12:00-13:00 || Lunch || [https://maps.app.goo.gl/womSkce9DrE8CTnR8 Case dining hall]
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/CQiWoCAQNt1ymZkb7 Served in Jordan Hall at the Center for Geospatial Analytics], evaluate the day's accomplishments, plan and prioritize for the next few days.
|}

=== Day 3, Wednesday, May 21 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Non-coding contributions, natural language translation, and internationalization.''

{| class="wikitable"
! Time !! Slot !!
|-
| 7:00-9:00 || Breakfast || [https://maps.app.goo.gl/eZ8VK8Mx6TjMt9NP8 Case dining hall]
|-
| 9:00-10:00 || Morning opening sessions || Introduction to non-coding contributions, tutorials, contributing examples, natural language translation and internationalization (procedures, glossaries, code customization, translation).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Easier access to GRASS tools - Vaclav Petras
|-
| 11:20-11:40 || Self-organized feedback sessions ||
|-
| 11:40-12:00 || Self-organized feedback sessions || GRASS backend for xarray and temporal framework global variables ([https://github.com/OSGeo/grass/issues/629]) - Laurent Courty
|-
| 12:00-13:00 || Lunch || Served on site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/1E39eySMVaxYJUUS8 Picnic at Pullen Park, shelter #3. In case of bad weather, dinner at the Center for Geospatial Analytics.
|}

=== Day 4, Thursday, May 22 ===

Location: Center for Geospatial Analytics, Jordan Hall, 2800 Faucette Drive ([https://www.google.com/maps/search/Jordan+Hall/@35.7816832,-78.6772765,18z/data=!3m1!4b1?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: 5103 (straight from the two elevators, at the end of the hallway)

Highlighted topic: ''Project vision and computational engine use case.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || On site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Project vision and the computational engine use case (missing features, documentation, user groups).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Modernizing Color Tables (Brendan)
|-
| 12:00-13:00 || Lunch || On site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-16:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 16:00-17:00 || Lightning talks || Fast-paced talks, showcasing applications of GRASS, room 5111.
|-
| 18:00 || Reception || Connect with researchers, government professionals, and industry collaborators, rooms 5111 and 5119.
|}

=== Day 5, Friday, May 23 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topic: ''GRASS project's future course.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || On site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || GRASS project's future course.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 10:00-11:00 || PSC meeting || Project Steering Committee meets (public).
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Your topic here
|-
| 12:00-13:00 || Lunch || Walk to [https://maps.app.goo.gl/kHVHY62QxTd6wHKd9 On the Oval Culinary Creatins]. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || Dinner on your own. Corey White will organize trip to downtown. Bus 41 from Hunt library to hotel and then walk.
|}

=== Day 6, Saturday, May 24 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topics: ''NSF POSE project evaluation.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || TBA. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || NSF POSE project evaluation, contributor community feedback.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Your topic here
|-
| 12:00-13:00 || Lunch || TBA. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || TBA.
|}

== Daily tasks for participants ==

* List all the things you are working on in the Participant reports section below. Update the list each day. Include things you work on with other people.
* If you want to discuss something with the whole group, add yourself to a Self-organized feedback sessions slot in the schedule above or tell Vaclav (Vashek) Petras.
* For people with triage access and above: If you are or will be working on an issue or on a PR which is not originally submitted by you, assign yourself to the issue or PR. (You can unassign yourself later if you change your mind.)

== Participant reports ==

Per-person reports from the meeting.

=== Giuseppe Amatulli | Yale University ===

* Testing r.watershed and r.stream.* for handling large datasets
* Running r.flowaccumulation at global level using water direction from hydrography90m
* Preparing the grass tutorial material for the https://www.geomorphometry2025.org/ conference

=== Veronica Andreo | CONICET - Instituto Gulich ===

* [https://github.com/veroandreo?tab=overview&from=2025-05-12&to=2025-05-24 GitHub contributions]
* Website footer enhancement
* Sync icons on the Tutorials website footer to those on the main website
* Fix descriptions and their display in the tutorials website
* Fix GRASS page on OSGeo website [https://www.osgeo.org/projects/grass-gis/]
** Changed logo, removed GIS from the name, fixed old links
* Social media posts
* Discussion about hyperspectral with Alen and Anna
* Expand the GRASS acronym on the home page
* Remove GIS from GRASS name on the website
* Review tutorials by Huidae and Adam Smith
* GRASS PSC admin

=== Abdullah Azzam | New Mexico State University ===

* r.runoff

=== Michael Barton | Arizona State University ===

* POSE related activities

=== Laura Belica | NC State University ===

* have been working on developing a workflow-tool tutorial template that facilitates GRASS learners who tend to 'jump in' or have a 'choose your own adventure' approach to learning GRASS (i.e., want to use their data for their study area for their objective from the start). The structure of the tutorial template is a concise, basic, general description/instructions of the workflow with optional links to pertinent explanatory/deeper dive content (e.g., plain language explainers of the tool, options, defaults, etc.) in a variety of formats (e.g., captioned images, short tool demo videos (30 sec to 2 min)) in addition to the more comprehensive resources available (e.g. documentation, examples, tutorials). The main motivation for this approach is to help new and occasional GRASS users avoid some of the common pitfalls and to learn how to find workarounds for some of the unanticipated challenges they may encounter with their specific datasets or use cases so that they can learn as they go. Another motivation for this approach is to facilitate the translation, extension, and updating of workflow tutorials by the community over time (e.g., providing audio and closed captioning for one of the tool-demo videos in another language, replacing an outdated GUI demo with one for the current release, or incorporating a new add-on as an option in the workflow).

* my focus this week is on developing a draft/test tutorial (in Quarto) for a standard hydrological modelling workflow that begins with the crucial pre-work of how to figure out the appropriate project/location, etc. as well as considerations of some of the downstream impacts of resolution, extent, region etc. It may not be ready for sharing by the end of the week, but suggestions and advice are welcomed in advance.

19 May
* discussed a novice user issue with 'moving' vector data from one location to another with Vero and learned a neat GUI option
* revised and added workflow tutorial text

=== Shonil Sateesh Bhide | NC State University ===

* CI optimization

=== Huidae Cho | New Mexico State University ===

* CMake, conda, CI, Mentoring

=== Edouard Choinière ===

* Quick ideas, way too much for a week: Helping others (may take a reasonable part of the time), managing CI, setting up localization template updating workflow, backporting tool? Pytest/coverage improvements? Discuss and design other projects, to work on during the year. Open to change on other priorities once there, anything that is useful. Maybe make a little progress on high dpi GUI, especially on Windows.

* Weekend before sprint:
** Clear up Renovate PRs to not use CI time during the sprint, reviewing and merging: [https://github.com/OSGeo/grass/pull/5664 #5664], [https://github.com/OSGeo/grass/pull/5665 #5665], [https://github.com/OSGeo/grass/pull/5666 #5666], [https://github.com/OSGeo/grass/pull/5667 #5667], [https://github.com/OSGeo/grass/pull/5668 #5668]
** PR to avoid some CI run time for the sprint: [https://github.com/OSGeo/grass/pull/5670 #5670]
** Reviewed open PRs for PRs that were mergeable before the sprint, updated outdated PRs to avoid having it needing CI time during sprint. Only ended up merging [https://github.com/OSGeo/grass/pull/5658 #5658], but another reviewed one that might still need changes: [https://github.com/OSGeo/grass/pull/5628 #5628]
* Monday May 19, 2025:
** PR got merged: [https://github.com/OSGeo/grass/pull/5670 #5670],[https://github.com/OSGeo/grass/pull/5550 #5550]
** Reviewed PRs: [https://github.com/OSGeo/grass/pull/5671 #5671], [https://github.com/OSGeo/grass/pull/5672 #5672]
** Discussions:
*** Shonil Sateesh Bhid & Shuham on their CI & pytest work and project.
*** Māris Nartišs about a potential issue and improvement for it. Will be discussed in the security reporting tab, also allowing to test the security vulnerability reporting process. + Research on existing solutions
** Reviewed: [https://github.com/OSGeo/grass/pull/5682 #5682], [https://github.com/OSGeo/grass/pull/5660 #5660],
** Reviewed, edited and merged: [https://github.com/OSGeo/grass/pull/3672 #3672]
** Discussed/helped user for: [https://github.com/OSGeo/grass/pull/5678 #5678] and [https://github.com/OSGeo/grass/pull/5684 #5684]
** Long discussion and vision planning for windows scripting with Vaclav, concerning [https://github.com/OSGeo/grass/pull/5624 #5624]. Tested alternatives and tried the consequences of that PR. This older PR finally got merged.
** Created PRs for NSIS installer: [https://github.com/OSGeo/grass/pull/5685 #5685] and also [https://github.com/OSGeo/grass/pull/5686 #5686], which should address [https://github.com/OSGeo/grass/issues/5663 #5663]. Still needs to test it.
** Agreed on convention for titles with Vaclav, unblocking [https://github.com/OSGeo/grass/pull/5341 #5341]
** Found a name with Ondrej and finally merged older PRs of an external contributor [https://github.com/OSGeo/grass/pull/5473 #5473] and [https://github.com/OSGeo/grass/pull/5474 #5474]
* Thursday May 20, 2025:
** Reviewed: [https://github.com/OSGeo/grass/pull/5695 #5695]
** Merged PRs: [https://github.com/OSGeo/grass/pull/5673 #5673], [https://github.com/OSGeo/grass/pull/5691 #5691], [https://github.com/OSGeo/grass/pull/5690 #5690], [https://github.com/OSGeo/grass/pull/5684 #5684],
** Discussed with author of [https://github.com/OSGeo/grass/pull/5660 #5660] and [https://github.com/OSGeo/grass/issues/5659 #5659] about rgb/hsl bug and tests for help.
** Worked with Corey to adjust markdown links for new markdownlint rule, finishing up [https://github.com/OSGeo/grass/pull/5669 #5669]
** Created PRs: [https://github.com/OSGeo/grass/pull/5692 #5692], [https://github.com/OSGeo/grass/pull/5694 #5694], [https://github.com/OSGeo/grass/pull/5689 #5689]

=== Laurent Courty ===

* Objectives: An xarray backend for GRASS STRDS. Fixing related issues
* May 20
** Presented itzi
** Uploaded arm64 wheels to PyPI for MacOS and Linux ([https://pypi.org/project/itzi/#files])
** Discussed with other developers about issue #629
* May 21
** Uploaded xarray-grass to PyPI
** Added CI tests to xarray-grass
** Discussed with the group about the xarray-grass backend
** Discussed with the group about solving mapset switching in the temporal framework

=== Robert S. Dzur | Bohannan Huston, Inc. ===

* r.in.pdal

=== David W. Farris | East Carolina University ===

* A tool to calculate gravity terrain corrections

=== Neel Ghoshal | NC State University ===
• LLM for helping users find tools 
5/19 
• Learnt how to PR (#5674) 
• Setup GRASS on system 
• Found small issue with compilation document 
• Discussed about the possible use case of LLM for helping users find tools 
5/20 
• Learnt about cookie cutter 
• Set up wsl on system 
• Compiled GRASS 
• Listed data sources for LLM training 

=== Caitlin Haedrich | NC State University ===

* Event photographs
* git/github mentoring
* Lightning Talk preparation
* Preparing workshop for [https://www.geomorphometry2025.org/ Geomorphometry2025]

=== Brendan Harmon | Louisiana State University ===

* Developing ([https://github.com/baharmon/r.earthworks r.earthworks]) addon & tutorials
* [https://github.com/baharmon?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]

=== Linda Karlovska | Czech Technical University in Prague ===

* Fix uninitialized variables in DOutFile() method: ([https://github.com/OSGeo/grass/pull/5650 PR])
* Update figures related to GUI: ([https://github.com/OSGeo/grass/pull/5651 PR])

Working on integration of the Jupyter notebooks to GUI (work for the whole week :-))

=== Martin Landa | Czech Technical University in Prague ===

* Tutorial: GISMentors courses updated ([https://github.com/OSGeo/grass-tutorials/pull/45 PR])
* libgis: G__usage_markdown() include tool label in metadata if defined ([https://github.com/OSGeo/grass/pull/5677 PR])
* PyGRASS: Module description property not defined always ([https://github.com/OSGeo/grass/pull/5681 PR])
* Website: OpenGeoLabs commercial support ([https://github.com/OSGeo/grass-website/pull/537 PR])
* v.select: create output also when no features found ([https://github.com/OSGeo/grass/pull/5696 PR])
* wxGUI: avoid creating nested list of errors (Graphical modeler) ([https://github.com/OSGeo/grass/pull/5700 PR])
* wxGUI/gmodeler: refactor - move ModelParamDialog to dialogs.py ([https://github.com/OSGeo/grass/pull/5715 PR])

=== Nicklas Larsson | Hungarian National Museum ===

* CMake build system; perhaps Conda recipe

=== Chung-Yuan Liang ===

* parallelize some modules, improve testing

=== Andres Lucero | Bohannan Huston Inc ===

* r.in.pdal

=== Alen Mangafić | Geodetic Institute of Slovenia ===
Monday May 19
* Presentationf of i.hyper, add-on which offers hyperspectral data support in GRASS.
* Architecture of the multi-module addon
Tuesday May 20
* i.hyper.import module: importing EnMAP imagery as 3D raster map
* i.hyper.explore module: RGB, CIR and SWIR visualization from 3D hyperspectral raster map.

=== Helena Mitasova | NC State University ===

* standardized data set and related tutorials
* documentation for interpolation tools
* collaborate/coordinate/discuss hydrology tools (analytics, simulations, soil properties inputs)
* assist with wiki cleanup if needed

Monday May 19
* investigated issues with v.surf.rst documentation in source code, tested and identified fixes needed
* discussed coupling GRASS with Blender versus potree for 3D object rendering with Brendan, Anna and Caitlin (for TL activities and other applications)
* discussed soil data for runoff estimation and other hydro topics, to be worked on on day 2

Tuesday May 20
* worked with Corey on fixing v.surf.rst documentation, discussed ideas for improvements and for documentation / tutorial for cross-valiadation
* discussed suggestions for graphics and examples to be inculded in v.surf.rst docs with Michelle
* discussed new developments in hydrology tools
* experimented with basic/standardized versus specialized data sets for documentation and tutorials

=== Michael Mulqueen | MassGIS ===

* depth to water, hydro from lidar, etc

=== Māris Nartišs ===

* Worked on a new raster data analysis tool r.smooth for inclusion into GRASS core
* Discussed architecture of hyperspectral data import and per-processing tool
* Discussed testing and organizing AI modules downloading data from internet
* Prepared and gave a presentation on code preparation for translations (best practice)

=== Ondřej Pešek | Czech Technical University in Prague ===

* [https://github.com/pesekon2?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* Refactoring, fixing, improving, discussing g.gui.gmodeler
* Discussing hyperspectral with Alen Mangafic
* Discussing jupyter in single GUI with Linda Karlovska
* PyGRASS
* Docs
* CQ
* Reviewing PRs, PR archeology

=== Vaclav (Vashek) Petras | NC State University ===

* [https://github.com/wenzeslaus?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* My focus: Getting feedback and ideas for computational engine use case, APIs, funding.
* Summit organizing
* Implementing rebranding on GitHub (repos, teams)
* Feedback session on project image
* Feedback session on easier access to tools
* Discussed LLMs with Neel Ghoshal, Riya
* Discussed session setupp Martin Landa
* Discussed conda with Nicklas Larsson
* Discussed hyperspectral with Alen Mangafić, Veronica Andreo, and Anna Petrasova
* Discussed code for new smoothing tool, integer overflows, translations with Māris Nartišs
* Compared setup of GRASS session and project in fasterRaster, QGIS, and GRASS itself with Adam Smith
* Discussed potential of Pixi for packaging or compilation with Gregory Power
* Discussed itzi model distribution issues with Laurent Courty
* Discussed r.horizon parallelization with Chung-Yuan Liang and Anna Petrasova
* Answered coding and setup questions for Neel Ghoshal, Abdullah Azzam, and Alen Mangafić

=== Anna Petrasova | NC State University ===

* [https://github.com/petrasovaa?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* plan: mentoring, documentation
* Monday
** discussing hyperspectral implementation with Alen
** helping mentee David Farris implementing his gravity correction addon
* Tuesday
** delivered intro to creating an addon, documentation
** mentoring Alen, Abdullah
** discussing bug in i.his.rgb with Jayneel
** reviews
* Wednesday
** discuss and demonstrate tutorials page
** mentoring Alen, Jayneel
* call with GSoC student

=== Gregory Power | Town of Cary ===

* Documentation

=== Pratikshya Regmi | NC State University ===

* Event photographs and videos
* Opened a pull request to change GRASS GIS to GRASS on the documentation (this was my first contribution to GRASS)
* Worked on preparing the mock document for LLM RAG
* Write a tutorial to Visualize Contour Lines with a Color Gradient with Folium.

=== Riya | Indian Institute of Technology, Roorkee ===

* I am currently thinking of developing an AI Agent for the grass jupyter library which will help the users with mathematical calculations done in GIS.

=== Jayneel Shah | NC State University ===

* improve the test coverage of imagery modules.

=== Krishna Prasad Sheshadri ===

*

=== Adam Smith | Missouri Botanical Garden ===

Overall: R package fasterRaster (fielding bug reports, adding features)

Monday:
* Assessed scope of fasterRaster issue [https://github.com/adamlilith/fasterRaster/issues/83 83]

Tuesday:
* Created a PR for fasterRaster tutorial on GRASS tutorials page.
* Improved handling of addons, including autodetect and installing when needed, enabling easier creation of addon-dependent methods.
* Presented *fasterRaster* package to group.

=== Michelle (Mimi) Stephens | ERDC ===

* Previous work: coupling R and Python scripts for computational analysis in GRASS.
* Current work: Running through GRASS commands to create visual outputs that can be added to the new GRASS 8.5 manual pages.
* Future work: Presenting on GRASS in JUNE at CERLCON.

=== Corey White | NC State University ===

* JSON, mentoring

=== Doug Newcomb | Semi Retired Cartographer ===

* Discussed hydroflattening method
* Discussed direct point cloud input to v.surf.rst
* Learning git procedures by updating branding (GRASS GIS to GRASS) for raster commands
Tuesday
* Continued updating branding for raster commands
* Started working on tutorial for r.hydro.flatten

=== Natalie Trso | Balance Geo LLC ===

* r.sim.water

== Guests and remote participants ==

=== Luís de Sousa | University of Lisbon ===

* Review outstanding PRs
* Prepare GRASS sessions for the OpenGeoHub Summer School

=== Markus Neteler | mundialis ===

* Support full automation of new GRASS manual pages deployment on server (upload artifacts from GitHub to OSGeo servers (grass and download))
* Source code license documentation: Using SPDX License IDs ({{GH-Issues|4190}})
* Support Wiki cleanup
* [https://github.com/neteler?tab=overview&from=2025-05-19&to=2025-05-24 GitHub contributions]

=== Nishant Bansal | Indian Institute of Technology, Varanasi ===

* Review the previous work on JSON during last year’s GSoC, including enhancements and the addition of JSON output support to other modules.

Talk:GRASS Developer Summit Raleigh 2025

2025-05-21T13:43:25Z

Annakrat: /* Day 3, Wednesday, May 21 */

{{toc|right}}

Quick links: [[GRASS Developer Summit Raleigh 2025|Meeting page]] | [[#Participant_reports|Reports]] | [[GRASS_Developer_Summit_Raleigh_2025#Sponsors|Sponsors]]

== Organizing Team ==

* Initial planning: Vaclav Petras, Anna Petrasova, Veronica Andreo, Corey White, Lois Utt, Sarah White, Doug Newcomb, Huidae Cho, Veronica Andreo ([[GRASS_Developer_Summit_Raleigh_2025#Organizing_Committee|Organizing Committee]])
* Budget: Vaclav Petras, Lois Utt, Anna Petrasova
* Raising support: Helena Mitasova, Vaclav Petras, Anna Petrasova, Michael Barton, Giuseppe Amatulli ([[NSF POSE Project 2023-2025 Timeline|NSF POSE project]] proposal authors)
* Travel: Lois Utt
* Venue: Vaclav Petras, Lois Utt
* Meals: Lois Utt, Sarah White, Vaclav Petras, Corey White, Anna Petrasova
* Agenda: Vaclav Petras, Huidae Cho, Anna Petrasova
* Wiki page: Vaclav Petras, Anna Petrasova
* Swag: Sarah White, Vaclav Petras, Anna Petrasova, Corey White
* Promotion, invitations, and social media: Vaclav Petras, Sarah White, Corey White, John Vogler
* Lightning talks organization: Vaclav Petras, Zachary Arcaro, John Vogler
* Lightning talk speakers: Vaclav Petras (welcome), Markus Metz and Markus Neteler (talk presented by Vaclav Petras), Anna Petrasova, Veronica Andreo, Robert Dzur, Nick Brady, Huidae Cho, Gregory Power, Doug Newcomb, Caitlin Haedrich
* Photography: Caitlin Haedrich, Māris Nartišs, Pratikshya Regmi

== Detailed Schedule ==

=== Day 1, Monday, May 19 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Contributing to GRASS. Getting started. Is it easy to contribute?''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-9:00 || Breakfast || Catered breakfast on site. Meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || What to expect from the event, contributing to GRASS using Git and GitHub, making your first contribution.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || i.hyper: Integrating Hyperspectral Imagery Processing into GRASS - Alen Mangafić
|-
| 11:20-11:40 || Self-organized feedback sessions ||
|-
| 11:40-12:00 || Self-organized feedback sessions || Project Image - Vaclav Petras
|-
| 12:00-13:00 || Lunch || Catered food on site.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || We will walk to [https://www.trophybrewing.com/brewing-pizza Trophy Brewing & Pizza] ([https://maps.app.goo.gl/ggnZ7EvXbWqDUmvP9 directions], 30 min walk from Talley)
|}

=== Day 2, Tuesday, May 20 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topics: ''Hydrology and Interfacing with R and QGIS (gathering user feedback, testing, discussing with developers, developing action items)''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-9:00 || Breakfast || Breakfast on site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Introduction to writing GRASS tools, program for the day.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || fasterRaster R package - Adam Smith
|-
| 11:20-11:40 || Self-organized feedback sessions || Hydography90m + Geocomputation Courses - Giuseppe
|-
| 11:40-12:00 || Self-organized feedback sessions || Flood modelling with grass and itzi ([https://itzi.org]) - Laurent Courty
|-
| 12:00-13:00 || Lunch || [https://maps.app.goo.gl/womSkce9DrE8CTnR8 Case dining hall]
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/CQiWoCAQNt1ymZkb7 Served in Jordan Hall at the Center for Geospatial Analytics], evaluate the day's accomplishments, plan and prioritize for the next few days.
|}

=== Day 3, Wednesday, May 21 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Non-coding contributions, natural language translation, and internationalization.''

{| class="wikitable"
! Time !! Slot !!
|-
| 7:00-9:00 || Breakfast || [https://maps.app.goo.gl/eZ8VK8Mx6TjMt9NP8 Case dining hall]
|-
| 9:00-10:00 || Morning opening sessions || Introduction to non-coding contributions, tutorials, contributing examples, natural language translation and internationalization (procedures, glossaries, code customization, translation).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Easier access to GRASS tools - Vaclav Petras
|-
| 11:20-11:40 || Self-organized feedback sessions || Temporal framework global variables ([https://github.com/OSGeo/grass/issues/629]) - Laurent Courty
|-
| 11:40-12:00 || Self-organized feedback sessions ||
|-
| 12:00-13:00 || Lunch || Served on site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/1E39eySMVaxYJUUS8 Picnic at Pullen Park, shelter #3. In case of bad weather, dinner at the Center for Geospatial Analytics.
|}

=== Day 4, Thursday, May 22 ===

Location: Center for Geospatial Analytics, Jordan Hall, 2800 Faucette Drive ([https://www.google.com/maps/search/Jordan+Hall/@35.7816832,-78.6772765,18z/data=!3m1!4b1?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: 5103 (straight from the two elevators, at the end of the hallway)

Highlighted topic: ''Project vision and computational engine use case.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || On site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Project vision and the computational engine use case (missing features, documentation, user groups).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Modernizing Color Tables (Brendan)
|-
| 12:00-13:00 || Lunch || On site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-16:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 16:00-17:00 || Lightning talks || Fast-paced talks, showcasing applications of GRASS, room 5111.
|-
| 18:00 || Reception || Connect with researchers, government professionals, and industry collaborators, rooms 5111 and 5119.
|}

=== Day 5, Friday, May 23 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topic: ''GRASS project's future course.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || On site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || GRASS project's future course.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 10:00-11:00 || PSC meeting || Project Steering Committee meets (public).
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Your topic here
|-
| 12:00-13:00 || Lunch || Walk to [https://maps.app.goo.gl/kHVHY62QxTd6wHKd9 On the Oval Culinary Creatins]. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || Dinner on your own. Corey White will organize trip to downtown. Bus 41 from Hunt library to hotel and then walk.
|}

=== Day 6, Saturday, May 24 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topics: ''NSF POSE project evaluation.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || TBA. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || NSF POSE project evaluation, contributor community feedback.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Your topic here
|-
| 12:00-13:00 || Lunch || TBA. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || TBA.
|}

== Daily tasks for participants ==

* List all the things you are working on in the Participant reports section below. Update the list each day. Include things you work on with other people.
* If you want to discuss something with the whole group, add yourself to a Self-organized feedback sessions slot in the schedule above or tell Vaclav (Vashek) Petras.
* For people with triage access and above: If you are or will be working on an issue or on a PR which is not originally submitted by you, assign yourself to the issue or PR. (You can unassign yourself later if you change your mind.)

== Participant reports ==

Per-person reports from the meeting.

=== Giuseppe Amatulli | Yale University ===

* Testing r.watershed and r.stream for handling large datasets

=== Veronica Andreo | CONICET - Instituto Gulich ===

* [https://github.com/veroandreo?tab=overview&from=2025-05-12&to=2025-05-24 GitHub contributions]
* Website footer enhancement
* Sync icons on the Tutorials website footer to those on the main website
* Fix descriptions and their display in the tutorials website
* Fix GRASS page on OSGeo website [https://www.osgeo.org/projects/grass-gis/]
** Changed logo, removed GIS from the name, fixed old links
* Social media posts
* Discussion about hyperspectral with Alen and Anna
* Expand the GRASS acronym on the home page
* Remove GIS from GRASS name on the website
* Review tutorials by Huidae and Adam Smith
* GRASS PSC admin

=== Abdullah Azzam | New Mexico State University ===

* r.runoff

=== Michael Barton | Arizona State University ===

* POSE related activities

=== Laura Belica | NC State University ===

* have been working on developing a workflow-tool tutorial template that facilitates GRASS learners who tend to 'jump in' or have a 'choose your own adventure' approach to learning GRASS (i.e., want to use their data for their study area for their objective from the start). The structure of the tutorial template is a concise, basic, general description/instructions of the workflow with optional links to pertinent explanatory/deeper dive content (e.g., plain language explainers of the tool, options, defaults, etc.) in a variety of formats (e.g., captioned images, short tool demo videos (30 sec to 2 min)) in addition to the more comprehensive resources available (e.g. documentation, examples, tutorials). The main motivation for this approach is to help new and occasional GRASS users avoid some of the common pitfalls and to learn how to find workarounds for some of the unanticipated challenges they may encounter with their specific datasets or use cases so that they can learn as they go. Another motivation for this approach is to facilitate the translation, extension, and updating of workflow tutorials by the community over time (e.g., providing audio and closed captioning for one of the tool-demo videos in another language, replacing an outdated GUI demo with one for the current release, or incorporating a new add-on as an option in the workflow).

* my focus this week is on developing a draft/test tutorial (in Quarto) for a standard hydrological modelling workflow that begins with the crucial pre-work of how to figure out the appropriate project/location, etc. as well as considerations of some of the downstream impacts of resolution, extent, region etc. It may not be ready for sharing by the end of the week, but suggestions and advice are welcomed in advance.

19 May
* discussed a novice user issue with 'moving' vector data from one location to another with Vero and learned a neat GUI option
* revised and added workflow tutorial text

=== Shonil Sateesh Bhide | NC State University ===

* CI optimization

=== Huidae Cho | New Mexico State University ===

* CMake, conda, CI, Mentoring

=== Edouard Choinière ===

* Quick ideas, way too much for a week: Helping others (may take a reasonable part of the time), managing CI, setting up localization template updating workflow, backporting tool? Pytest/coverage improvements? Discuss and design other projects, to work on during the year. Open to change on other priorities once there, anything that is useful. Maybe make a little progress on high dpi GUI, especially on Windows.

* Weekend before sprint:
** Clear up Renovate PRs to not use CI time during the sprint, reviewing and merging: [https://github.com/OSGeo/grass/pull/5664 #5664], [https://github.com/OSGeo/grass/pull/5665 #5665], [https://github.com/OSGeo/grass/pull/5666 #5666], [https://github.com/OSGeo/grass/pull/5667 #5667], [https://github.com/OSGeo/grass/pull/5668 #5668]
** PR to avoid some CI run time for the sprint: [https://github.com/OSGeo/grass/pull/5670 #5670]
** Reviewed open PRs for PRs that were mergeable before the sprint, updated outdated PRs to avoid having it needing CI time during sprint. Only ended up merging [https://github.com/OSGeo/grass/pull/5658 #5658], but another reviewed one that might still need changes: [https://github.com/OSGeo/grass/pull/5628 #5628]
* Monday May 19, 2025:
** PR got merged: [https://github.com/OSGeo/grass/pull/5670 #5670],[https://github.com/OSGeo/grass/pull/5550 #5550]
** Reviewed PRs: [https://github.com/OSGeo/grass/pull/5671 #5671], [https://github.com/OSGeo/grass/pull/5672 #5672]
** Discussions:
*** Shonil Sateesh Bhid & Shuham on their CI & pytest work and project.
*** Māris Nartišs about a potential issue and improvement for it. Will be discussed in the security reporting tab, also allowing to test the security vulnerability reporting process. + Research on existing solutions
** Reviewed: [https://github.com/OSGeo/grass/pull/5682 #5682], [https://github.com/OSGeo/grass/pull/5660 #5660],
** Reviewed, edited and merged: [https://github.com/OSGeo/grass/pull/3672 #3672]
** Discussed/helped user for: [https://github.com/OSGeo/grass/pull/5678 #5678] and [https://github.com/OSGeo/grass/pull/5684 #5684]
** Long discussion and vision planning for windows scripting with Vaclav, concerning [https://github.com/OSGeo/grass/pull/5624 #5624]. Tested alternatives and tried the consequences of that PR. This older PR finally got merged.
** Created PRs for NSIS installer: [https://github.com/OSGeo/grass/pull/5685 #5685] and also [https://github.com/OSGeo/grass/pull/5686 #5686], which should address [https://github.com/OSGeo/grass/issues/5663 #5663]. Still needs to test it.
** Agreed on convention for titles with Vaclav, unblocking [https://github.com/OSGeo/grass/pull/5341 #5341]
** Found a name with Ondrej and finally merged older PRs of an external contributor [https://github.com/OSGeo/grass/pull/5473 #5473] and [https://github.com/OSGeo/grass/pull/5474 #5474]
* Thursday May 20, 2025:
** Reviewed: [https://github.com/OSGeo/grass/pull/5695 #5695]
** Merged PRs: [https://github.com/OSGeo/grass/pull/5673 #5673], [https://github.com/OSGeo/grass/pull/5691 #5691], [https://github.com/OSGeo/grass/pull/5690 #5690], [https://github.com/OSGeo/grass/pull/5684 #5684],
** Discussed with author of [https://github.com/OSGeo/grass/pull/5660 #5660] and [https://github.com/OSGeo/grass/issues/5659 #5659] about rgb/hsl bug and tests for help.
** Worked with Corey to adjust markdown links for new markdownlint rule, finishing up [https://github.com/OSGeo/grass/pull/5669 #5669]
** Created PRs: [https://github.com/OSGeo/grass/pull/5692 #5692], [https://github.com/OSGeo/grass/pull/5694 #5694], [https://github.com/OSGeo/grass/pull/5689 #5689]

=== Laurent Courty ===

* An xarray backend for GRASS STRDS. Fixing related issues
* Presented itzi
* Uploaded arm64 wheels to PyPI for MacOS and Linux ([https://pypi.org/project/itzi/#files])

=== Robert S. Dzur | Bohannan Huston, Inc. ===

* r.in.pdal

=== David W. Farris | East Carolina University ===

* A tool to calculate gravity terrain corrections

=== Neel Ghoshal | NC State University ===
• LLM for helping users find tools 
5/19 
• Learnt how to PR (#5674) 
• Setup GRASS on system 
• Found small issue with compilation document 
• Discussed about the possible use case of LLM for helping users find tools 
5/20 
• Learnt about cookie cutter 
• Set up wsl on system 
• Compiled GRASS 
• Listed data sources for LLM training 

=== Caitlin Haedrich | NC State University ===

* Event photographs
* git/github mentoring

=== Brendan Harmon | Louisiana State University ===

* Developing ([https://github.com/baharmon/r.earthworks r.earthworks]) addon & tutorials
* [https://github.com/baharmon?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]

=== Linda Karlovska | Czech Technical University in Prague ===

* I plan to work on GUI enhancements, particularly the Jupyter-style interactive page for enhanced scripting and visualization.

=== Martin Landa | Czech Technical University in Prague ===

* Tutorial: GISMentors courses updated ([https://github.com/OSGeo/grass-tutorials/pull/45 PR])
* libgis: G__usage_markdown() include tool label in metadata if defined ([https://github.com/OSGeo/grass/pull/5677 PR])
* PyGRASS: Module description property not defined always ([https://github.com/OSGeo/grass/pull/5681 PR])
* Website: OpenGeoLabs commercial support ([https://github.com/OSGeo/grass-website/pull/537 PR])
* v.select: create output also when no features found ([https://github.com/OSGeo/grass/pull/5696 PR])
* wxGUI: avoid creating nested list of errors (Graphical modeler) ([https://github.com/OSGeo/grass/pull/5700 PR])
* wxGUI/gmodeler: refactor - move ModelParamDialog to dialogs.py ([https://github.com/OSGeo/grass/pull/5715 PR])

=== Nicklas Larsson | Hungarian National Museum ===

* CMake build system; perhaps Conda recipe

=== Chung-Yuan Liang ===

* parallelize some modules, improve testing

=== Andres Lucero | Bohannan Huston Inc ===

* r.in.pdal

=== Alen Mangafić | Geodetic Institute of Slovenia ===
Monday May 19
* Presentationf of i.hyper, add-on which offers hyperspectral data support in GRASS.
* Architecture of the multi-module addon
Tuesday May 20
* i.hyper.import module: importing EnMAP imagery as 3D raster map
* i.hyper.explore module: RGB, CIR and SWIR visualization from 3D hyperspectral raster map.

=== Helena Mitasova | NC State University ===

* standardized data set and related tutorials
* documentation for interpolation tools
* collaborate/coordinate/discuss hydrology tools (analytics, simulations, soil properties inputs)
* assist with wiki cleanup if needed

Monday May 19
* investigated issues with v.surf.rst documentation in source code, tested and identified fixes needed
* discussed coupling GRASS with Blender versus potree for 3D object rendering with Brendan, Anna and Caitlin (for TL activities and other applications)
* discussed soil data for runoff estimation and other hydro topics, to be worked on on day 2

Tuesday May 20
* worked with Corey on fixing v.surf.rst documentation, discussed ideas for improvements and for documentation / tutorial for cross-valiadation
* discussed suggestions for graphics and examples to be inculded in v.surf.rst docs with Michelle
* discussed new developments in hydrology tools
* experimented with basic/standardized versus specialized data sets for documentation and tutorials

=== Michael Mulqueen | MassGIS ===

* depth to water, hydro from lidar, etc

=== Māris Nartišs ===

* Preparing a new raster data analysis tool r.smooth for inclusion into GRASS core
* Discussing architecture of hyperspectral data import and per-processing tool

=== Ondřej Pešek | Czech Technical University in Prague ===

* Many things to fix/improve in g.gui.gmodeler, finally finish an addon for CNNs in GRASS

=== Vaclav (Vashek) Petras | NC State University ===

* [https://github.com/wenzeslaus?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* My focus: Getting feedback and ideas for computational engine use case, APIs, funding.
* Summit organizing
* Implementing rebranding on GitHub (repos, teams)
* Feedback session on project image
* Feedback session on easier access to tools
* Discussed LLMs with Neel Ghoshal, Riya
* Discussed session setupp Martin Landa
* Discussed conda with Nicklas Larsson
* Discussed hyperspectral with Alen Mangafić, Veronica Andreo, and Anna Petrasova
* Discussed code for new smoothing tool, integer overflows, translations with Māris Nartišs
* Compared setup of GRASS session and project in fasterRaster, QGIS, and GRASS itself with Adam Smith
* Discussed potential of Pixi for packaging or compilation with Gregory Power
* Discussed itzi model distribution issues with Laurent Courty
* Discussed r.horizon parallelization with Chung-Yuan Liang and Anna Petrasova
* Answered coding and setup questions for Neel Ghoshal, Abdullah Azzam, and Alen Mangafić

=== Anna Petrasova | NC State University ===

* [https://github.com/petrasovaa?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* plan: mentoring, documentation
* Monday
** discussing hyperspectral implementation with Alen
** helping mentee David Farris implementing his gravity correction addon
* Tuesday
** delivered intro to creating an addon, documentation
** mentoring Alen, Abdullah
** discussing bug in i.his.rgb with Jayneel
** reviews

=== Gregory Power | Town of Cary ===

* Documentation

=== Pratikshya Regmi | NC State University ===

* I plan to showcase my work on integrating LLM and GRASS GIS.

=== Riya | Indian Institute of Technology, Roorkee ===

* I am currently thinking of developing an AI Agent for the grass jupyter library which will help the users with mathematical calculations done in GIS.

=== Jayneel Shah | NC State University ===

* improve the test coverage of imagery modules.

=== Krishna Prasad Sheshadri ===

*

=== Adam Smith | Missouri Botanical Garden ===

Overall: R package fasterRaster (fielding bug reports, adding features)

Monday:
* Assessed scope of fasterRaster issue [https://github.com/adamlilith/fasterRaster/issues/83 83]

Tuesday:
* Created a PR for fasterRaster tutorial on GRASS tutorials page.
* Improved handling of addons, including autodetect and installing when needed, enabling easier creation of addon-dependent methods.
* Presented *fasterRaster* package to group.

=== Michelle (Mimi) Stephens | ERDC ===

* Previous work: coupling R and Python scripts for computational analysis in GRASS.
* Current work: Running through GRASS commands to create visual outputs that can be added to the new GRASS 8.5 manual pages.
* Future work: Presenting on GRASS in JUNE at CERLCON.

=== Corey White | NC State University ===

* JSON, mentoring

=== Doug Newcomb | Semi Retired Cartographer ===

* Discussed hydroflattening method
* Discussed direct point cloud input to v.surf.rst
* Learning git procedures by updating branding (GRASS GIS to GRASS) for raster commands
Tuesday
* Continued updating branding for raster commands
* Started working on tutorial for r.hydro.flatten

== Guests and remote participants ==

=== Luís de Sousa | University of Lisbon ===

* Review outstanding PRs
* Prepare GRASS sessions for the OpenGeoHub Summer School

=== Markus Neteler | mundialis ===

* Support full automation of new GRASS manual pages deployment on server (upload artifacts from GitHub to OSGeo servers (grass and download))
* Source code license documentation: Using SPDX License IDs ({{GH-Issues|4190}})
* Support Wiki cleanup
* [https://github.com/neteler?tab=overview&from=2025-05-19&to=2025-05-24 GitHub contributions]

=== Nishant Bansal | Indian Institute of Technology, Varanasi ===

* Review the previous work on JSON during last year’s GSoC, including enhancements and the addition of JSON output support to other modules.

Talk:GRASS Developer Summit Raleigh 2025

2025-05-21T02:22:21Z

Annakrat: /* Anna Petrasova | NC State University */

{{toc|right}}

Quick links: [[GRASS Developer Summit Raleigh 2025|Meeting page]] | [[#Participant_reports|Reports]] | [[GRASS_Developer_Summit_Raleigh_2025#Sponsors|Sponsors]]

== Organizing Team ==

* Initial planning: Vaclav Petras, Anna Petrasova, Veronica Andreo, Corey White, Lois Utt, Sarah White, Doug Newcomb, Huidae Cho, Veronica Andreo ([[GRASS_Developer_Summit_Raleigh_2025#Organizing_Committee|Organizing Committee]])
* Budget: Vaclav Petras, Lois Utt, Anna Petrasova
* Raising support: Helena Mitasova, Vaclav Petras, Anna Petrasova, Michael Barton, Giuseppe Amatulli ([[NSF POSE Project 2023-2025 Timeline|NSF POSE project]] proposal authors)
* Travel: Lois Utt
* Venue: Vaclav Petras, Lois Utt
* Meals: Lois Utt, Sarah White, Vaclav Petras, Corey White, Anna Petrasova
* Agenda: Vaclav Petras, Huidae Cho, Anna Petrasova
* Wiki page: Vaclav Petras, Anna Petrasova
* Swag: Sarah White, Vaclav Petras, Anna Petrasova, Corey White
* Promotion, invitations, and social media: Vaclav Petras, Sarah White, Corey White, John Vogler
* Lightning talks organization: Vaclav Petras, Zachary Arcaro, John Vogler
* Lightning talk speakers: Vaclav Petras (welcome), Markus Metz and Markus Neteler (talk presented by Vaclav Petras), Anna Petrasova, Veronica Andreo, Robert Dzur, Nick Brady, Huidae Cho, Gregory Power, Doug Newcomb, Caitlin Haedrich
* Photography: Caitlin Haedrich, Māris Nartišs, Pratikshya Regmi

== Detailed Schedule ==

=== Day 1, Monday, May 19 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Contributing to GRASS. Getting started. Is it easy to contribute?''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-9:00 || Breakfast || Catered breakfast on site. Meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || What to expect from the event, contributing to GRASS using Git and GitHub, making your first contribution.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || i.hyper: Integrating Hyperspectral Imagery Processing into GRASS - Alen Mangafić
|-
| 11:20-11:40 || Self-organized feedback sessions ||
|-
| 11:40-12:00 || Self-organized feedback sessions || Project Image - Vaclav Petras
|-
| 12:00-13:00 || Lunch || Catered food on site.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || We will walk to [https://www.trophybrewing.com/brewing-pizza Trophy Brewing & Pizza] ([https://maps.app.goo.gl/ggnZ7EvXbWqDUmvP9 directions], 30 min walk from Talley)
|}

=== Day 2, Tuesday, May 20 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topics: ''Hydrology and Interfacing with R and QGIS (gathering user feedback, testing, discussing with developers, developing action items)''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:30-9:00 || Breakfast || Breakfast on site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Introduction to writing GRASS tools, program for the day.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || fasterRaster R package - Adam Smith
|-
| 11:20-11:40 || Self-organized feedback sessions || Hydography90m + Geocomputation Courses - Giuseppe
|-
| 11:40-12:00 || Self-organized feedback sessions || Flood modelling with grass and itzi ([https://itzi.org]) - Laurent Courty
|-
| 12:00-13:00 || Lunch || [https://maps.app.goo.gl/womSkce9DrE8CTnR8 Case dining hall]
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/CQiWoCAQNt1ymZkb7 Served in Jordan Hall at the Center for Geospatial Analytics], evaluate the day's accomplishments, plan and prioritize for the next few days.
|}

=== Day 3, Wednesday, May 21 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Non-coding contributions, natural language translation, and internationalization.''

{| class="wikitable"
! Time !! Slot !!
|-
| 7:00-9:00 || Breakfast || [https://maps.app.goo.gl/eZ8VK8Mx6TjMt9NP8 Case dining hall]
|-
| 9:00-10:00 || Morning opening sessions || Introduction to non-coding contributions, deep dive into new documentation, natural language translation and internationalization (procedures, glossaries, code customization, translation).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Easier access to GRASS tools - Vaclav Petras
|-
| 11:20-11:40 || Self-organized feedback sessions || Temporal framework global variables ([https://github.com/OSGeo/grass/issues/629]) - Laurent Courty
|-
| 11:40-12:00 || Self-organized feedback sessions || GSoC call
|-
| 12:00-13:00 || Lunch || Served on site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/1E39eySMVaxYJUUS8 Picnic at Pullen Park, shelter #3. In case of bad weather, dinner at the Center for Geospatial Analytics.
|}

=== Day 4, Thursday, May 22 ===

Location: Center for Geospatial Analytics, Jordan Hall, 2800 Faucette Drive ([https://www.google.com/maps/search/Jordan+Hall/@35.7816832,-78.6772765,18z/data=!3m1!4b1?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: 5103 (straight from the two elevators, at the end of the hallway)

Highlighted topic: ''Project vision and computational engine use case.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || On site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Project vision and the computational engine use case (missing features, documentation, user groups).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Modernizing Color Tables (Brendan)
|-
| 12:00-13:00 || Lunch || On site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-16:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 16:00-17:00 || Lightning talks || Fast-paced talks, showcasing applications of GRASS, room 5111.
|-
| 18:00 || Reception || Connect with researchers, government professionals, and industry collaborators, rooms 5111 and 5119.
|}

=== Day 5, Friday, May 23 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topic: ''GRASS project's future course.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || On site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || GRASS project's future course.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 10:00-11:00 || PSC meeting || Project Steering Committee meets (public).
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Your topic here
|-
| 12:00-13:00 || Lunch || Walk to [https://maps.app.goo.gl/kHVHY62QxTd6wHKd9 On the Oval Culinary Creatins]. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || Dinner on your own. Corey White will organize trip to downtown. Bus 41 from Hunt library to hotel and then walk.
|}

=== Day 6, Saturday, May 24 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topics: ''NSF POSE project evaluation.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || TBA. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || NSF POSE project evaluation, contributor community feedback.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Your topic here
|-
| 12:00-13:00 || Lunch || TBA. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || TBA.
|}

== Daily tasks for participants ==

* List all the things you are working on in the Participant reports section below. Update the list each day. Include things you work on with other people.
* If you want to discuss something with the whole group, add yourself to a Self-organized feedback sessions slot in the schedule above or tell Vaclav (Vashek) Petras.
* For people with triage access and above: If you are or will be working on an issue or on a PR which is not originally submitted by you, assign yourself to the issue or PR. (You can unassign yourself later if you change your mind.)

== Participant reports ==

Per-person reports from the meeting.

=== Giuseppe Amatulli | Yale University ===

* Testing r.watershed and r.stream for handling large datasets

=== Veronica Andreo | CONICET - Instituto Gulich ===

* [https://github.com/veroandreo?tab=overview&from=2025-05-12&to=2025-05-24 GitHub contributions]
* Website footer enhancement
* Sync icons on the Tutorials website footer to those on the main website
* Fix descriptions and their display in the tutorials website
* Fix GRASS page on OSGeo website [https://www.osgeo.org/projects/grass-gis/]
** Changed logo, removed GIS from the name, fixed old links
* Social media posts
* Discussion about hyperspectral with Alen and Anna
* Expand the GRASS acronym on the home page
* Remove GIS from GRASS name on the website
* Review tutorials by Huidae and Adam Smith
* GRASS PSC admin

=== Abdullah Azzam | New Mexico State University ===

* r.runoff

=== Michael Barton | Arizona State University ===

* POSE related activities

=== Laura Belica | NC State University ===

* have been working on developing a workflow-tool tutorial template that facilitates GRASS learners who tend to 'jump in' or have a 'choose your own adventure' approach to learning GRASS (i.e., want to use their data for their study area for their objective from the start). The structure of the tutorial template is a concise, basic, general description/instructions of the workflow with optional links to pertinent explanatory/deeper dive content (e.g., plain language explainers of the tool, options, defaults, etc.) in a variety of formats (e.g., captioned images, short tool demo videos (30 sec to 2 min)) in addition to the more comprehensive resources available (e.g. documentation, examples, tutorials). The main motivation for this approach is to help new and occasional GRASS users avoid some of the common pitfalls and to learn how to find workarounds for some of the unanticipated challenges they may encounter with their specific datasets or use cases so that they can learn as they go. Another motivation for this approach is to facilitate the translation, extension, and updating of workflow tutorials by the community over time (e.g., providing audio and closed captioning for one of the tool-demo videos in another language, replacing an outdated GUI demo with one for the current release, or incorporating a new add-on as an option in the workflow).

* my focus this week is on developing a draft/test tutorial (in Quarto) for a standard hydrological modelling workflow that begins with the crucial pre-work of how to figure out the appropriate project/location, etc. as well as considerations of some of the downstream impacts of resolution, extent, region etc. It may not be ready for sharing by the end of the week, but suggestions and advice are welcomed in advance.

19 May
* discussed a novice user issue with 'moving' vector data from one location to another with Vero and learned a neat GUI option
* revised and added workflow tutorial text

=== Shonil Sateesh Bhide | NC State University ===

* CI optimization

=== Huidae Cho | New Mexico State University ===

* CMake, conda, CI, Mentoring

=== Edouard Choinière ===

* Quick ideas, way too much for a week: Helping others (may take a reasonable part of the time), managing CI, setting up localization template updating workflow, backporting tool? Pytest/coverage improvements? Discuss and design other projects, to work on during the year. Open to change on other priorities once there, anything that is useful. Maybe make a little progress on high dpi GUI, especially on Windows.

* Weekend before sprint:
** Clear up Renovate PRs to not use CI time during the sprint, reviewing and merging: [https://github.com/OSGeo/grass/pull/5664 #5664], [https://github.com/OSGeo/grass/pull/5665 #5665], [https://github.com/OSGeo/grass/pull/5666 #5666], [https://github.com/OSGeo/grass/pull/5667 #5667], [https://github.com/OSGeo/grass/pull/5668 #5668]
** PR to avoid some CI run time for the sprint: [https://github.com/OSGeo/grass/pull/5670 #5670]
** Reviewed open PRs for PRs that were mergeable before the sprint, updated outdated PRs to avoid having it needing CI time during sprint. Only ended up merging [https://github.com/OSGeo/grass/pull/5658 #5658], but another reviewed one that might still need changes: [https://github.com/OSGeo/grass/pull/5628 #5628]
* Monday May 19, 2025:
** PR got merged: [https://github.com/OSGeo/grass/pull/5670 #5670],[https://github.com/OSGeo/grass/pull/5550 #5550]
** Reviewed PRs: [https://github.com/OSGeo/grass/pull/5671 #5671], [https://github.com/OSGeo/grass/pull/5672 #5672]
** Discussions:
*** Shonil Sateesh Bhid & Shuham on their CI & pytest work and project.
*** Māris Nartišs about a potential issue and improvement for it. Will be discussed in the security reporting tab, also allowing to test the security vulnerability reporting process. + Research on existing solutions
** Reviewed: [https://github.com/OSGeo/grass/pull/5682 #5682], [https://github.com/OSGeo/grass/pull/5660 #5660],
** Reviewed, edited and merged: [https://github.com/OSGeo/grass/pull/3672 #3672]
** Discussed/helped user for: [https://github.com/OSGeo/grass/pull/5678 #5678] and [https://github.com/OSGeo/grass/pull/5684 #5684]
** Long discussion and vision planning for windows scripting with Vaclav, concerning [https://github.com/OSGeo/grass/pull/5624 #5624]. Tested alternatives and tried the consequences of that PR. This older PR finally got merged.
** Created PRs for NSIS installer: [https://github.com/OSGeo/grass/pull/5685 #5685] and also [https://github.com/OSGeo/grass/pull/5686 #5686], which should address [https://github.com/OSGeo/grass/issues/5663 #5663]. Still needs to test it.
** Agreed on convention for titles with Vaclav, unblocking [https://github.com/OSGeo/grass/pull/5341 #5341]
** Found a name with Ondrej and finally merged older PRs of an external contributor [https://github.com/OSGeo/grass/pull/5473 #5473] and [https://github.com/OSGeo/grass/pull/5474 #5474]
* Thursday May 20, 2025:
** Reviewed: [https://github.com/OSGeo/grass/pull/5695 #5695]
** Merged PRs: [https://github.com/OSGeo/grass/pull/5673 #5673], [https://github.com/OSGeo/grass/pull/5691 #5691], [https://github.com/OSGeo/grass/pull/5690 #5690], [https://github.com/OSGeo/grass/pull/5684 #5684],
** Discussed with author of [https://github.com/OSGeo/grass/pull/5660 #5660] and [https://github.com/OSGeo/grass/issues/5659 #5659] about rgb/hsl bug and tests for help.
** Worked with Corey to adjust markdown links for new markdownlint rule, finishing up [https://github.com/OSGeo/grass/pull/5669 #5669]
** Created PRs: [https://github.com/OSGeo/grass/pull/5692 #5692], [https://github.com/OSGeo/grass/pull/5694 #5694], [https://github.com/OSGeo/grass/pull/5689 #5689]

=== Laurent Courty ===

* An xarray backend for GRASS STRDS. Fixing related issues
* Presented itzi
* Uploaded arm64 wheels to PyPI for MacOS and Linux ([https://pypi.org/project/itzi/#files])

=== Robert S. Dzur | Bohannan Huston, Inc. ===

* r.in.pdal

=== David W. Farris | East Carolina University ===

* A tool to calculate gravity terrain corrections

=== Neel Ghoshal | NC State University ===
• LLM for helping users find tools 
5/19 
• Learnt how to PR (#5674) 
• Setup GRASS on system 
• Found small issue with compilation document 
• Discussed about the possible use case of LLM for helping users find tools 
5/20 
• Learnt about cookie cutter 
• Set up wsl on system 
• Compiled GRASS 
• Listed data sources for LLM training 

=== Caitlin Haedrich | NC State University ===

* Event photographs
* git/github mentoring

=== Brendan Harmon | Louisiana State University ===

* Developing ([https://github.com/baharmon/r.earthworks r.earthworks]) addon & tutorials
* [https://github.com/baharmon?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]

=== Linda Karlovska | Czech Technical University in Prague ===

* I plan to work on GUI enhancements, particularly the Jupyter-style interactive page for enhanced scripting and visualization.

=== Martin Landa | Czech Technical University in Prague ===

* Tutorial: GISMentors courses updated ([https://github.com/OSGeo/grass-tutorials/pull/45 PR])
* libgis: G__usage_markdown() include tool label in metadata if defined ([https://github.com/OSGeo/grass/pull/5677 PR])
* PyGRASS: Module description property not defined always ([https://github.com/OSGeo/grass/pull/5681 PR])
* Website: OpenGeoLabs commercial support ([https://github.com/OSGeo/grass-website/pull/537 PR])
* v.select: create output also when no features found ([https://github.com/OSGeo/grass/pull/5696 PR])
* wxGUI: avoid creating nested list of errors (Graphical modeler) ([https://github.com/OSGeo/grass/pull/5700 PR])

=== Nicklas Larsson | Hungarian National Museum ===

* CMake build system; perhaps Conda recipe

=== Chung-Yuan Liang ===

* parallelize some modules, improve testing

=== Andres Lucero | Bohannan Huston Inc ===

* r.in.pdal

=== Alen Mangafić | Geodetic Institute of Slovenia ===
Monday May 19
* Presentationf of i.hyper, add-on which offers hyperspectral data support in GRASS.
* Architecture of the multi-module addon
Tuesday May 20
* i.hyper.import module: importing EnMAP imagery as 3D raster map
* i.hyper.explore module: RGB, CIR and SWIR visualization from 3D hyperspectral raster map.

=== Helena Mitasova | NC State University ===

* standardized data set and related tutorials
* documentation for interpolation tools
* collaborate/coordinate/discuss hydrology tools (analytics, simulations, soil properties inputs)
* assist with wiki cleanup if needed

Monday May 19
* investigated issues with v.surf.rst documentation in source code, tested and identified fixes needed
* discussed coupling GRASS with Blender versus potree for 3D object rendering with Brendan, Anna and Caitlin (for TL activities and other applications)
* discussed soil data for runoff estimation and other hydro topics, to be worked on on day 2

Tuesday May 20
* worked with Corey on fixing v.surf.rst documentation, discussed ideas for improvements and for documentation / tutorial for cross-valiadation
* discussed suggestions for graphics and examples to be inculded in v.surf.rst docs with Michelle
* discussed new developments in hydrology tools
* experimented with basic/standardized versus specialized data sets for documentation and tutorials

=== Michael Mulqueen | MassGIS ===

* depth to water, hydro from lidar, etc

=== Māris Nartišs ===

* Preparing a new raster data analysis tool r.smooth for inclusion into GRASS core
* Discussing architecture of hyperspectral data import and per-processing tool

=== Ondřej Pešek | Czech Technical University in Prague ===

* Many things to fix/improve in g.gui.gmodeler, finally finish an addon for CNNs in GRASS

=== Vaclav (Vashek) Petras | NC State University ===

* [https://github.com/wenzeslaus?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* computational engine, APIs, funding, summit organization

=== Anna Petrasova | NC State University ===

* [https://github.com/petrasovaa?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* plan: mentoring, documentation
* Monday
** discussing hyperspectral implementation with Alen
** helping mentee David Farris implementing his gravity correction addon
* Tuesday
** delivered intro to creating an addon, documentation
** mentoring Alen, Abdullah
** discussing bug in i.his.rgb with Jayneel
** reviews

=== Gregory Power | Town of Cary ===

* Documentation

=== Pratikshya Regmi | NC State University ===

* I plan to showcase my work on integrating LLM and GRASS GIS.

=== Riya | Indian Institute of Technology, Roorkee ===

* I am currently thinking of developing an AI Agent for the grass jupyter library which will help the users with mathematical calculations done in GIS.

=== Jayneel Shah | NC State University ===

* improve the test coverage of imagery modules.

=== Krishna Prasad Sheshadri ===

*

=== Adam Smith | Missouri Botanical Garden ===

* R package fasterRaster (fielding bug reports, adding features)

Monday: Assessed scope of fasterRaster issue [https://github.com/adamlilith/fasterRaster/issues/83 83]

=== Michelle (Mimi) Stephens | ERDC ===

* Previous work: coupling R and Python scripts for computational analysis in GRASS.
* Current work: Running through GRASS commands to create visual outputs that can be added to the new GRASS 8.5 manual pages.
* Future work: Presenting on GRASS in JUNE at CERLCON.

=== Corey White | NC State University ===

* JSON, mentoring

=== Doug Newcomb | Semi Retired Cartographer ===

* Discussed hydroflattening method
* Discussed direct point cloud input to v.surf.rst
* Learning git procedures by updating branding (GRASS GIS to GRASS) for raster commands

== Guests and remote participants ==

=== Luís de Sousa | University of Lisbon ===

* Review outstanding PRs
* Prepare GRASS sessions for the OpenGeoHub Summer School

=== Markus Neteler | mundialis ===

* Support full automation of new GRASS manual pages deployment on server (upload artifacts from GitHub to OSGeo servers (grass and download))
* Source code license documentation: Using SPDX License IDs ({{GH-Issues|4190}})
* Support Wiki cleanup
* [https://github.com/neteler?tab=overview&from=2025-05-19&to=2025-05-24 GitHub contributions]

=== Nishant Bansal | Indian Institute of Technology, Varanasi ===

* Review the previous work on JSON during last year’s GSoC, including enhancements and the addition of JSON output support to other modules.

Talk:GRASS Developer Summit Raleigh 2025

2025-05-20T15:26:32Z

Annakrat: /* Anna Petrasova | NC State University */

PSC

2025-05-15T20:26:55Z

Annakrat: /* 2025 */

= GRASS Project Steering Committee (PSC) =
The Project Steering Committee plays a pivotal role in the governance and operational direction of GRASS GIS.
The PSC meets regularly to discuss organizational and financial aspects of the GRASS project and maintains the [[#PSC meeting agenda and minutes]].
The PSC is responsible for granting write access to new core developers and approving RFCs ([https://github.com/OSGeo/grass/tree/main/doc/development/rfc Request For Comments]).
The PSC has its own public [http://lists.osgeo.org/mailman/listinfo/grass-psc mailing list] where [[#Motions]] are passed.

== Members ==

* '''[https://veroandreo.gitlab.io Verónica Andreo]''', (veroandreo * gmail.com), National Research Council (CONICET) - Argentinian Space Agency (CONAE), AR - Chair
*'''[https://ecodiv.earth/about.html Paulo van Breugel]''', (p.vanbreugel * gmail com), HAS green academy, NL
*'''[https://idea.isnew.info/ Huidae Cho]''', (grass4u * gmail com), New Mexico State University, USA
*'''[https://geomatics.fsv.cvut.cz/en/employees/linda-karlovska/ Linda Karlovská]''', (linda.karlovska * seznam cz), Czech Technical University in Prague, CZ
*'''[https://www.osgeo.org/member/kudrnovsky/ Helmut Kudrnovsky]''', (hellik * web de), Environment Agency Austria, Vienna, AT
*'''Nicklas Larsson''', (n_larsson * yahoo com), Hungarian National Museum, HU
*'''[https://www.mundialis.de/neteler/ Markus Neteler]''', (neteler * osgeo org), mundialis, Bonn, DE
*'''[https://cnr.ncsu.edu/geospatial/people/vaclav-petras/ Vaclav Petráš]''', (wenzeslaus * gmail com), CGA, North Carolina State University, Raleigh NC, USA
*'''[https://cnr.ncsu.edu/geospatial/people/anna-petrasova Anna Petrášová]''', (kratochanna * gmail com). CGA, North Carolina State University, Raleigh NC, USA

== PSC meeting agenda and minutes ==
<div style="column-count:4">
* [[PSC Meeting 2025-05-09]]
* [[PSC Meeting 2025-02-14]]
* [[PSC Meeting 2024-11-22]]
* [[PSC Meeting 2024-11-08]]
* [[PSC Meeting 2024-08-09]]
* [[PSC Meeting 2024-06-14]]
* [[PSC Meeting 2024-05-10]]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20240209 PSC Meeting 2024-02-09]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20231110 PSC Meeting 2023-11-10]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20230811 PSC Meeting 2023-08-11]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20230512 PSC Meeting 2023-05-12]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20230210 PSC Meeting 2023-02-10]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20221111 PSC Meeting 2022-11-11]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20220812 PSC Meeting 2022-08-12]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20220513 PSC Meeting 2022-05-13]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20220211 PSC Meeting 2022-02-11]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20211112 PSC Meeting 2021-11-12]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20210729 PSC Meeting 2021-07-29]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20210511 PSC Meeting 2021-05-11]
* [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20210203 PSC Meeting 2021-02-03]
</div>

== Motions ==

Motions are approved at meetings or on the grass-psc mailing list. Listed motions are approved unless otherwise noted.

=== 2025 ===
* Join NumFOCUS by signing Fiscal Sponsorship Agreement, signed by AP, VP, LK, VA, MN, which is the majority of PSC (5 out of 9, NumFOCUS required 5)
* Adopt new logo and branding (3 Apr 2025, [https://lists.osgeo.org/pipermail/grass-psc/2025-March/002995.html email], [https://github.com/OSGeo/grass-website/pull/506 PR])
* Use GRASS as a project name (26 Feb 2025, [https://lists.osgeo.org/pipermail/grass-psc/2025-February/002970.html email])

=== 2024 ===

* Approve and adopt [https://github.com/OSGeo/grass/pull/4566 C++17 Standard Support RFC] (28 Nov 2024)
* Apply for NumFOCUS membership (8 Nov 2024, [[PSC_Meeting_2024-11-08|meeting]])
* Pay Publer's business plan for one year, 3 accounts and test. Use GRASS budget sitting at OSGeo (8 Nov 2024, [[PSC_Meeting_2024-11-08|meeting]])
* Approve Linda's student grant final report and issue second payment (27 May 2024)
* Support Letter for LoC of FOSS4G 2025 Hiroshima (wording approved, 10 May 2024)
* GitHub write access to Linda Karlovska as a new core developer (granted, 26 Jan 2024)

=== 2023 ===

* Approve Linda's student grant proposal and issue first payment (27 Dec 2023)
* Github write access to Edouard Choinière as a new core developer (granted, 18 Dec 2023)
* Appoint Vaclav Petras as new treasurer (5 Dec 2023)
* Approve and adopt [https://github.com/OSGeo/grass/blob/main/doc/development/rfc/version_numbering.md RFC: Version Numbering] (5 Jun 2023)
* Approve and adopt RFC: Python Language Support (5 Jun 2023)
* Approve Linda's student grant final report (16 Mar 2023)
* Appoint Markus Neteler as new treasurer (19 Jan 2023)

=== 2022 ===

* Approve Linda's proposal for GRASS mini grant (19 Nov 2022)
* Approve final report of Caitlin Haedrich's mini grant (30 Apr 2022)
* Approve final report of Linda Kladivova's mini grant (10 Mar 2022)
* Approve mini grant for Caitlin Haedrich (6 Jan 2022)

=== 2021 ===

* Approve mini grant for Linda Kladivova (21 Dec 2021)
* [https://trac.osgeo.org/grass/wiki/RFC/7_LanguageStandardsSupport RFC 7: Language Standards Support] (approved, 29 Mar 2021)
* Approving of Veronica Andreo as GRASS GIS PSC chair (approved, 3 Feb 2021) - See [https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20210203 minutes Feb 3, 2021]
* PSC mandates will last 6 years with 1/2 of PSC elected every 3 years (approved, 3 Feb 2021)
* PSC roles and tasks will be also renewed every 3 years (approved, 3 Feb 2021)
* When a PSC member steps down, s/he might be replaced by the next person in the previous election results ranking (approved, 3 Feb 2021)

=== 2020 ===

* [https://trac.osgeo.org/grass/wiki/PSC/Election2020 Elections 2020]
* GitHub write access to Nicklas Larsson as a new core developer (granted, 24 Dec 2020)
* GitHub write access to Tomáš Zigo as a new core developer (granted, 29 Nov 2020)
* Second payment for new GRASS GIS Hugo based web site (approved, 1 Oct 2020)
* First payment for new GRASS GIS Hugo based web site (approved, 25 Feb 2020)
* Prague 2019 Community Sprint Reimbursements (approved, 14 Jan 2020)

For older motions, see [https://trac.osgeo.org/grass/wiki/PSC/Motions the list of motions] from 2006 to 2020.

== Resources ==

*[http://lists.osgeo.org/mailman/listinfo/grass-psc PSC mailing list]
*[https://github.com/OSGeo/grass/tree/main/doc/development/rfc RFCs]

== Elections ==

* [[PSC Election 2024]] (completed in Oct. 2024)
*[https://trac.osgeo.org/grass/wiki/PSC/Election2020 PSC Election 2020] (completed in Jan. 2021)
*[https://trac.osgeo.org/grass/wiki/PSC/Election2016 PSC Election 2016] (completed in Aug. 2016)
*[https://trac.osgeo.org/grass/wiki/PSC/Election2012 PSC Election 2012] (completed in Nov. 2012)
*[https://trac.osgeo.org/grass/wiki/PSC/Creation2006 PSC created in 2006]

== Former PSC members ==

Period 2020-2024:

*'''Michael Barton''', USA
*'''Martin Landa''', Czech Republic
*'''Helena Mitasova''', USA

Period 2021-2023:

*'''Moritz Lennert''', Belgium (stepped down in 2023, replaced by '''Helmut Kudrnovsky''', Austria)

Period 2016-2020:

*'''Michael Barton''', USA
*'''Margherita Di Leo''', Italy (dileomargherita * gmail com). [http://forest.jrc.ec.europa.eu/team/person/35/detail/ Home Page] European Commission, Joint Research Centre (JRC), IT
*'''Martin Landa''', Czech Republic
*'''Moritz Lennert''', Belgium
*'''Peter Löwe''', Germany (peter DOT loewe AT gmx DOT de) [https://wiki.osgeo.org/wiki/User:Peter_Loewe Home page]. TIB Hannover, DE
*'''Helena Mitasova''', USA
*'''Markus Neteler (chair)''', Italy
*'''Anna Petrášová''', USA
*'''Vaclav Petras''', USA

Period 2012-2016:

*'''Michael Barton''', USA
*'''Hamish Bowman''', New Zealand
*'''Massimiliano Cannata''', Switzerland
*'''Moritz Lennert''', Belgium
*'''Margherita Di Leo''', Italy
*'''Martin Landa''', Czech Republic
*'''Markus Metz''', Germany
*'''Helena Mitasova''', USA
*'''Scott Mitchell''', Canada
*'''Markus Neteler (chair)''', Italy

Period 2006-2012:

*'''Michael Barton, USA
*'''Dylan Beaudette''' USA
*'''Hamish Bowman, New Zealand
*'''Massimiliano Cannata, Switzerland
*'''Brad Douglas''' (rez * touchofmadness com), USA
*'''Paul Kelly''' (paul-grass stjohnspoint co uk), UK
*'''Helena Mitasova, USA
*'''Scott Mitchell, Canada
*'''Markus Neteler (chair), Italy
*'''Maciej Sieczka''' (msieczka * sieczka org) [http://www.sieczka.org Home page], PL

=== Former chair persons ===

*Period 2016-2020: '''Markus Neteler''', Germany (neteler * osgeo org) [https://www.mundialis.de/neteler/ Home page]. mundialis, Bonn, DE
*Period 2012-2016: '''Markus Neteler''', Germany (neteler * osgeo org) [https://wiki.osgeo.org/wiki/Markus_Neteler Home page]. Trento, IT
*Period 2006-2012: '''Markus Neteler''', Germany (neteler * osgeo org) [https://wiki.osgeo.org/wiki/Markus_Neteler Home page]. Trento, IT

[[Category:PSC]]

GRASS-Wiki

2025-05-15T17:54:32Z

Annakrat: /* Welcome to the GRASS Wiki */

__NOTOC__

[[Image:grasslogo_vector_small.png|110x123 px|right|link=https://grass.osgeo.org]]

= Welcome to the GRASS Wiki =

This wiki is used by the GRASS community mainly for '''governance''', '''event planning''', and '''community coordination'''.

Looking for how to use GRASS? Visit our main website and learning resources:

* [https://grass.osgeo.org/ Main GRASS Website]
* [https://grass.osgeo.org/grass84/manuals/index.html Documentation & Manuals]
* [https://grass-tutorials.osgeo.org/ Tutorials & Learning Resources]
* [https://grass.osgeo.org/download/ Download GRASS]
* [https://github.com/OSGeo/grass GitHub Repository]

'''Support GRASS development: [https://grass.osgeo.org/contribute/sponsoring/ Donate here]'''

== Governance ==

* [[PSC|Project Steering Committee (PSC)]]
* [[PSC#PSC_meeting_agenda_and_minutes|Meeting Minutes]]
* [[GRASS_GIS_Budget_2025|2025 Budget]]

== Latest Events & Planning ==

* [[GRASS_Developer_Summit_Raleigh_2025|GRASS Developer Summit in Raleigh 2025]]
* [[GRASS_GSoC_Ideas_2025|Google Summer of Code 2025]]

== Relevant Categories ==
* [[:Category:GSoC|GSoC]]
* [[:Category:Code_Sprint|Code sprints]]
* [[:Category:Workshops|Workshops]]
* [[:Category:Conferences|Conferences]]
* [[:Category:Budget|Budget]]

Talk:GRASS Developer Summit Raleigh 2025

2025-05-14T19:07:46Z

Annakrat: /* Day 3, Wednesday, May 21 */

GRASS-Wiki

2025-05-13T18:20:42Z

Annakrat: remove box

__NOTOC__

[[Image:grasslogo_vector_small.png|110x123 px|right|link=https://grass.osgeo.org]]

= Welcome to the GRASS Wiki =

This wiki is used by the GRASS community mainly for '''governance''', '''event planning''', and '''community coordination'''.

Looking for how to use GRASS? Visit our main website and learning resources:

* 🌐 [https://grass.osgeo.org/ Main GRASS Website]
* 📚 [https://grass.osgeo.org/grass84/manuals/index.html Documentation & Manuals]
* 🎓 [https://grass-tutorials.osgeo.org/ Tutorials & Learning Resources]
* ⬇️ [https://grass.osgeo.org/download/ Download GRASS]
* 🛠️ [https://github.com/OSGeo/grass GitHub Repository]

'''💚 Support GRASS development: [https://grass.osgeo.org/contribute/sponsoring/ Donate here]'''💚

== Governance ==

* [[PSC|Project Steering Committee (PSC)]]
* [[PSC#PSC_meeting_agenda_and_minutes|Meeting Minutes]]
* [[GRASS_GIS_Budget_2025|2025 Budget]]

== Latest Events & Planning ==

* [[GRASS_Developer_Summit_Raleigh_2025|GRASS Developer Summit in Raleigh 2025]]
* [[GRASS_GSoC_Ideas_2025|Google Summer of Code 2025]]

== Relevant Categories ==
* [[:Category:GSoC|GSoC]]
* [[:Category:Code_Sprint|Code sprints]]
* [[:Category:Workshops|Workshops]]
* [[:Category:Conferences|Conferences]]
* [[:Category:Budget|Budget]]