Zeke, you should try to fix some tickets (as suggested on the GSoC wiki page you linked); see the lists below. Alternatively, for your project, it may be appropriate to implement a small tool for some dataset which is easy to handle for you (e.g. something you used before). Look at the r.modis modules because the idea is very similar to the overall idea of the proposal. Look also at the current sample dataset for GRASS GIS and the idea of generalized sample datasets.
Trivial: https://trac.osgeo.org/grass/query?priority=trivial&status=a ssigned&status=new&status=reopened&max=500&col=id&col=summar y&col=priority&col=status&col=owner&col=type&col=milestone&order=priority Minor: https://trac.osgeo.org/grass/query?priority=minor&status=ass igned&status=new&status=reopened&max=500&col=id&col=summary& col=priority&col=status&col=type&col=owner&col=milestone&order=priority Normal enhancement: https://trac.osgeo.org/grass/query?priority=normal&status=as signed&status=new&status=reopened&type=enhancement&max=500&c ol=id&col=summary&col=priority&col=status&col=type&col=owner &col=milestone&order=priority r.modis: https://grass.osgeo.org/grass72/manuals/addons/r.modis.html Sample datasets: https://trac.osgeo.org/grass/wiki/SampleDataset http://grass.osgeo.org/download/sample-data/ On Tue, Mar 28, 2017 at 6:15 AM, Blumentrath, Stefan < stefan.blumentr...@nina.no> wrote: > I cannot offer to mentor your project, but I could make some shell scripts > available for you, that turn publicly available data into GRASS Locations > and mapsets. > > It is not really much, but depending on the approach you choose they might > be a helpful startingpoint. > I'm willing to (co-)mentor. For the other potential mentors: Having a collection of "shell scripts" is actually a very good qualification for (co-)mentoring this project. Vaclav (Vashek)
_______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
