https://grasswiki.osgeo.org/w/index.php?title=Special:NewPages&feed=atom&hidebots=1&hideredirs=1&limit=50&offset=&namespace=0&username=&tagfilter=GRASS-Wiki - New pages [en]2024-03-29T10:14:33ZFrom GRASS-WikiMediaWiki 1.41.0https://grasswiki.osgeo.org/wiki/GRASS_GIS_Basic_DatasetsGRASS GIS Basic Datasets2024-03-07T21:19:53Z<p>Helena: Created page with "==== Background ==== Standardized basic GRASS GIS dataset is an updated, restructured dataset to be used in manual pages, tutorials, courses, code testing, development and OSGeo Live. Localized versions of the dataset support common instructions, tutorials and teaching materials for different regions in the world. Datasets for GRASS7 and GRASS8 * Wiki page with examples and list of existing datasets is at [http://grasswiki.osgeo.org/wiki/GRASS_GIS_Standardized_Sample_..."</p>
<hr />
<div>==== Background ====<br />
<br />
Standardized basic GRASS GIS dataset is an updated, restructured dataset to be used in manual pages, tutorials, courses, code testing, development and OSGeo Live. Localized versions of the dataset support common instructions, tutorials and teaching materials for different regions in the world. <br />
<br />
Datasets for GRASS7 and GRASS8<br />
* Wiki page with examples and list of existing datasets is at [http://grasswiki.osgeo.org/wiki/GRASS_GIS_Standardized_Sample_Datasets GRASS Wiki: GRASS GIS Standardized Sample Datasets].<br />
* Track wiki page with the original discussion for GRASS 7 is at [https://trac.osgeo.org/grass/wiki/SampleDataset GRASS GIS Sample Datasets].<br />
* Download links on GRASS GIS website: [https://grass.osgeo.org/download/data/ GRASS GIS Sample Data]<br />
<br />
==== Common rules ====<br />
<br />
* Names of map layers must be the same for all standardized datasets. No additions to names such as `_10m` or `_wake_county` are allowed. This also implies that names must be in English, national language is not allowed for national standardized datasets (however, if desired, we can can work on a script which would automatically [http://grass.osgeo.org/grass70/manuals/addons/g.rename.many.html rename multiple maps] in dataset and would also find and replace names in documentation and tutorials).<br />
* To keep the basic data set simple, specialized map layers are moved into separate mapsets, for example, statewide data at lower resolutions or high resolution lidar or UAS based data, data time series, etc. <br />
* Description in tables here should be usable as title of the map. Separate details in description, which should not be part of the title, using commas or parentheses. Titles can differ between standardized datasets and can use national language (unlike names).<br />
<br />
==== References ====<br />
<br />
* Petras, V., Petrasova, A., Harmon, B., Meentemeyer, R.K., Mitasova, H. ''[http://www.mdpi.com/2220-9964/4/2/942/pdf Integrating Free and Open Source Solutions into Geospatial Science Education]''. ISPRS International Journal of Geo-Information. 2015, 4, 942-956. [http://dx.doi.org/10.3390/ijgi4020942 doi:10.3390/ijgi4020942] (Contains explanation of usage of the GRASS GIS commands concept to get teaching materials which are easy to maintain.)<br />
<br />
* [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Standardized_Sample_Datasets GRASS GIS Standardized Sample Datasets], 2016. Past examples for North Carolina; Piemonte, Italy, and Czechia.<br />
<br />
* [http://docs.qgis.org/2.8/en/docs/training_manual/foreword/preparing_data.html QGIS Training manual] which uses similar concept and has instructions to create similar dataset to the provided one with the local geospatial data and has a script to replace some values in the teaching material itself.<br />
<br />
==== Funding ====<br />
* NSF POSE II # 2303651 Growing GRASS OSE for Worldwide Access to Multidisciplinary Geospatial Analytics</div>Helenahttps://grasswiki.osgeo.org/wiki/GRASS_Community_Meeting_Prague_2024GRASS Community Meeting Prague 20242024-02-20T20:27:14Z<p>Neteler: /* Agenda */ Discuss mailing list (mailman) vs discourse (forum)</p>
<hr />
<div>{{toc|right}}<br />
The ''GRASS GIS Community Meeting'' for contributors and developers will be happening from '''June 14 to June 19, 2024''' in Prague, Czechia.<br />
<br />
[[File:Prague-Community-Meeting-2023-crop.jpg|500px|frameless|center]]<br />
<br />
== Sponsor us! ==<br />
<br />
We welcome financial contributions to support the meeting and we are looking for sponsors to cover costs such as meals or to help reducing travel and accommodation expenses for GRASS developers who volunteer their time. If you are interested in sponsoring the GRASS Community Meeting, please go to:<br />
<br />
::: '''[https://opencollective.com/osgeo/projects/grass/contribute OpenCollective]'''<br />
<br />
Any surplus at the end of the event will be used for future activities of the GRASS GIS project such as the [[Student Grants|Student Grant program]].<br />
<br />
This GRASS Community Meeting is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet. Community meetings are important opportunities for developers to discuss, fix bugs, plan the direction for the project and work on new features. The developers and other contributors or their employers are donating their valuable time, so it would be great if funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community meeting will be directly contributed back into the GRASS project to the benefit of everyone who uses it. Note that while we have our general plan, we can't accept any earmarked donations, i.e., we can't make any promises for a specific work to be done, please contact specific developers or support commercial providers for that.<br />
<br />
We are grateful to the following sponsors for their support and commitment! <br />
<br />
* U.S. National Science Foundation, award 2303651. (Travel for 5 participants and their time, event venue.)<br />
<br />
[[File:NSF Official logo.png|none|left|200px|alt=Logo of US NSF|U.S. National Science Foundation]]<br />
<br />
* In-kind contributions will be acknowledged here.<br />
* Personal time and/or financial contributions will be acknowledged here.<br />
<br />
== Purpose ==<br />
<br />
The ''GRASS GIS 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 GIS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.<br />
<br />
In this meeting, building on momentum from the 40th birthday meeting, we will continue the revisions of the maintenance processes and infrastructure - a process which highly benefits from the current maintainers being in one place (and time zone). Topics which require highly synchronous collaboration will be included such as Markdown documentation and CMake build transitions. Other contributors are expected to enhance existing tools and their documentation. A [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ press release] gives an overview of last year's event.<br />
<br />
We do require participants to work on GRASS GIS 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.<br />
<br />
For the detailed agenda and individual's plans, see below.<br />
<br />
== Agenda ==<br />
These are some of the identified project priorities:<br />
* Develop the project roadmap to better communicate project vision and priorities.<br />
* Discuss the GRASS GIS integration with QGIS with its maintainers to identify next steps.<br />
* Test the CMake and conda packaging implementations.<br />
* Finalize the HTML to Markdown documentation conversion.<br />
* GSoC students will showcase their projects and seek feedback. We also search for fostering their engagement with community members participating in the meeting and others that want to join online.<br />
* Test and review onboarding documentation for developers, maintainers and other contributors.<br />
* Develop use cases and tutorials on the use and integration of STAC related modules into data processing workflows.<br />
* Get feedback on ongoing GRASS website UX improvements and add missing content. <br />
* Address issues discussed last year about GRASS-R integration: https://github.com/rsbivand/rgrass/discussions/78<br />
* Discuss mailing list (mailman) vs [https://discourse.osgeo.org/ discourse] (forum)<br />
<br />
=== Thursday, June 13 ===<br />
<br />
Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.<br />
<br />
=== Friday, June 14 ===<br />
<br />
* Welcome.<br />
* Refine shared goals.<br />
<br />
=== Saturday, June 15 ===<br />
<br />
=== Sunday, June 16 ===<br />
<br />
=== Monday, June 17 ===<br />
<br />
=== Tuesday, June 18 ===<br />
<br />
=== Wednesday, June 19 ===<br />
<br />
=== Thursday, June 20 ===<br />
<br />
Day of departure.<br />
<br />
== Participation ==<br />
<br />
We are planning for an attendance of 15 people at the same time but you are welcome to sign up regardless of capacity: We will find a space for you. Please add your name here or contact [[User:wenzeslaus|Vaclav Petras]] <tt><wenzeslaus at gmail com></tt>:<br />
<br />
=== In person ===<br />
<br />
{|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;" <br />
!width=50px|'''Number'''<br />
!width=130px|'''Participant '''<br />
!width=100px|'''Country'''<br />
!width=100px|'''Arrival'''<br />
!width=100px|'''Departure'''<br />
!'''Topics'''<br />
!'''Notes'''<br />
|-<br />
|1<br />
| [[User:wenzeslaus|Vaclav Petras]]<br />
| United States <br />
| June 13<br />
| June 20<br />
| review PR, reduce PR queue, Python API topics (also for QGIS and R), funding<br />
|<br />
|-<br />
|2<br />
| [[User:Annakrat|Anna Petrasova]]<br />
| United States <br />
| June 13<br />
| June 20<br />
| grass.jupyter, R and QGIS integration<br />
|<br />
|-<br />
|3<br />
| [[User:Ctwhite|Corey White]]<br />
| United States <br />
| June 13<br />
| June 20<br />
| STAC, JSON outputs, connections with other tools (OpenPlains) <br />
|-<br />
|4<br />
| [[User:Chaedri|Caitlin Haedrich]]<br />
| United States<br />
| June 13<br />
| June 20<br />
| grass.jupyter<br />
|<br />
|-<br />
|5<br />
| [[User:Veroandreo | Vero Andreo]]<br />
| United States<br />
| June 13<br />
| June 20<br />
| STAC, tutorials, website, documentation, contributing guidelines<br />
|<br />
|-<br />
|6<br />
| [[User:florisvdh | Floris Vanderhaeghe]]<br />
| Belgium<br />
| June 13<br />
| June 18 (morning)<br />
| Interfacing GRASS from R (parts of the [https://github.com/rsbivand/rgrass/discussions/78 todo-list])<br />
|<br />
|-<br />
|7<br />
| [[User:martinl | Martin Landa]]<br />
| Czech Republic<br />
| June 14<br />
| June 19<br />
| GUI, Modeler, Markdown, ...<br />
|<br />
|-<br />
|8<br />
| [[User:hellik | Helmut Kudrnovsky]]<br />
| Austria <br />
| June 14<br />
| June 16<br />
| ...<br />
|<br />
|-<br />
|9<br />
| [[User:neteler | Markus Neteler]]<br />
| Germany<br />
| June 14<br />
| June 20<br />
| Infrastructure, Markdown, mailman vs discourse...<br />
|<br />
|-<br />
|}<br />
<br />
If you are arriving or departing on the days of the event, please specify the time, too.<br />
<br />
=== Online ===<br />
<br />
Join our [https://app.gitter.im/#/room/#grassgis_community:gitter.im Gitter chatroom]<br />
<br />
Gitter has a video (and backup will be Zoom).<br />
<br />
Participating virtually:<br />
<br />
{|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;" <br />
!width=50px|'''Number'''<br />
!width=130px|'''Participant '''<br />
!width=100px|'''Country'''<br />
!'''Topics'''<br />
!'''Times, synchronous or fully asynchronous'''<br />
!'''Notes'''<br />
|-<br />
|1<br />
| Be The First<br />
| Your Country<br />
| Your Topic<br />
| When you will be available (timezone, days, times)<br />
|<br />
|-<br />
|}<br />
<br />
== Venue ==<br />
<br />
[[File:Ncsu logo.jpg|240px|frameless|left]]<br />
[https://prague.ncsu.edu/about/ NC State European Center in Prague]<br><br />
Malé náměstí 144/1<br><br />
Praha 1 – 110 00<br><br />
Prague, Czech Republic<br><br />
<br />
[https://en.mapy.cz/s/fohulovaha Map]<br><br />
<br />
Prague, the capital of Czechia (Czech Republic) has an international [http://www.prg.aero/en/ airport]. It's location in the middle of central Europe makes it easily reachable by train, bus or car. The city itself has great public transportation.<br />
<br />
== Accommodation and Costs ==<br />
<br />
''Participation is free of charge''. However, participants should plan for the following costs:<br />
<br />
* Travel<br />
* Lodging<br />
* Food and drink (some may be covered)<br />
<br />
<br />
'''Please note''': The currency in Czech Republic is {{wikipedia|Czech crown}} (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see [https://www.cnb.cz/cs/financni-trhy/devizovy-trh/kurzy-devizoveho-trhu/kurzy-devizoveho-trhu/ current rates]).<br />
<br />
== Individual Preparation ==<br />
<br />
* Bring your own computer<br />
* Bring {{wikipedia|AC adapter|power connector adapter}} if needed (Czech Republic: 230V, 50Hz, {{wikipedia|File:Euro-Flachstecker_2.jpg|Type C Europlugs}} are common and also {{wikipedia|File:French_plug_and_socket.jpg|Type E}})<br />
* 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.<br />
<br />
== FAQ ==<br />
<br />
* ''How was it last time?''<br />
** Splendid! See [[GRASS Community Meeting Prague 2023]]!<br />
* ''Is the meeting just a coding event?''<br />
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project. Committed newcomers are welcome! <br />
* ''Is the GRASS Community Meeting for developers only?''<br />
** No, anybody can help, with testing, checking out bugs and fixes, documentation and more.<br />
* ''Where can I get help and more information about the community meeting?''<br />
** Contact [[User:wenzeslaus|Vaclav Petras]] <tt><wenzeslaus at gmail com></tt>.</div>Wenzeslaushttps://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024GRASS GSoC Ideas 20242024-02-03T04:28:48Z<p>Veroandreo: /* Add EODAG support to GRASS GIS */ add link to test of skills</p>
<hr />
<div><br />
== About ==<br />
<br />
* [https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2024_Ideas The OSGeo GSoC 2024 main page]<br />
* [https://summerofcode.withgoogle.com/ Official GSoC page at Google]<br />
<br />
== Ideas ==<br />
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://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list],[https://github.com/OSGeo/grass/discussions GitHub Discussions], or [https://gitter.im/grassgis/community Gitter].<br />
<br />
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],<br />
[https://trac.osgeo.org/grass/wiki/GSoC/2017 2017],<br />
[https://trac.osgeo.org/grass/wiki/GSoC/2018 2018],<br />
[https://trac.osgeo.org/grass/wiki/GSoC/2019 2019],<br />
[https://trac.osgeo.org/grass/wiki/GSoC/2020 2020],<br />
[https://trac.osgeo.org/grass/wiki/GSoC/2021 2021],<br />
[https://trac.osgeo.org/grass/wiki/GSoC/2022 2022],<br />
[https://trac.osgeo.org/grass/wiki/GSoC/2023 2023])<br />
which have not yet been implemented.<br />
You can also look at accepted GRASS GSoC [https://trac.osgeo.org/grass/wiki/GSoC projects from previous years] for an idea of scope.''<br />
<br />
Include "GRASS GIS" in the title of our idea to easily distinguish ideas and projects inside OSGeo.<br />
<br />
<br />
=== Parallelization of existing tools ===<br />
<br />
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,...<br />
For overview of current state, see [[Raster_Parallelization_with_OpenMP]].<br />
<br />
* Requirements: familiarity with C, OpenMP<br />
* Mentor: Huidae Cho<br />
* Co-mentor: Vaclav Petras, Anna Petrasova<br />
* Project length: 175 or 350 hours (take your pick)<br />
* Rating: medium<br />
* Expected Outcomes: parallelized module or modules, depending on complexity<br />
* Test of skills: suggest/implement solution for https://github.com/OSGeo/grass/issues/2644<br />
<br />
=== Improve GRASS user experience in Jupyter Notebook ===<br />
[[File:Jupyter_interactive_viewshed.png|500px|thumb|right|InteractiveMap in grass.jupyter library]]<br />
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 adding parallelization for rendering, increasing interactivity of displayed data using ipyleaflet (e.g., capture mouse clicks to show information about vector line, pixel), adding API for managing projects and subprojects (i.e., locations/mapsets), simplifing display of attribute data, ...<br />
<br />
* Requirements: Python<br />
* Mentor: Anna Petrasova<br />
* Co-mentor: Vaclav Petras, Helena Mitasova<br />
* Project length: 175 or 350 hours (take your pick)<br />
* Rating: easy to medium<br />
* Expected Outcomes: improved user experience when using GRASS through notebooks<br />
* 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].<br />
<br />
=== Add JSON output to different tools in C ===<br />
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.<br />
* Requirements: C, Python for tests<br />
* Mentor: Vaclav Petras<br />
* Co-mentor: Anna Petrasova, Corey White<br />
* Project length: 175 or 350 hours (take your pick)<br />
* Rating: easy to medium<br />
* Expected Outcomes: one or more (depending on project length and complexity of the tool) tools with well tested JSON output<br />
* Test of skills: Address https://github.com/OSGeo/grass/issues/1044 for r.surf.fractal<br />
<br />
=== Support writing tests with pytest ===<br />
<br />
* 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.<br />
* ''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.<br />
* Using ''pytest'' should lead to tests which feel more like Python scripts and to minimum of testing-specific code.<br />
* 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).<br />
* Two main things needed:<br />
** Create general comparison functions from the ''grass.gunittest'' assert methods so that they can be used with pytest.<br />
** 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 <br />
* Additional things needed:<br />
** Fixture for pytest to set up and tear down a GRASS session in a temporary mapset.<br />
<br />
* Requirements: Python<br />
* Project length: 175 or 350 hours (take your pick)<br />
* Mentor: Vaclav Petras<br />
* Co-mentor: Stefan Blumentrath<br />
* Proposed by: Vaclav Petras<br />
* Rating: easy to medium<br />
* Expected Outcomes: Convenient way of writing tests with pytest<br />
* 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.<br />
<br />
=== New easy-to-use CLI and API for GRASS GIS ===<br />
<br />
* Make running of GRASS GIS modules as easy as it is to run GDAL commands.<br />
** `grass run r.slope.aspect elevation=elevation.tiff slope=slope.tiff aspect=aspect.tiff`<br />
** CLI like GDAL has.<br />
** No GRASS Database, Location, Mapset to deal with.<br />
** No import, export from user perspective.<br />
** Reasonable defaults for things like region.<br />
** CLI and API still allows user to specify any of the above.<br />
* Idea page with details: wiki:GSoC/2021/EasyToUseCliAndApiIdea<br />
* Project length: 350 hours<br />
* Rating: medium<br />
* Requirements:<br />
** Language: Python<br />
** 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.<br />
* Mentors: Vaclav Petras<br />
* Co-mentors: Stefan Blumentrath<br />
* Proposed by: Vaclav Petras<br />
* Expected outcomes: New subcommand which easily runs a GRASS module on GeoTiff and GeoPackage.<br />
* Test and training tasks:<br />
** Solve one of the tickets linked at the idea page.<br />
** Add features to `grass` executable interface:<br />
*** 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).<br />
** Extend `--exec` functionality:<br />
*** Add `--region` to set a temporary computational region for the execution, e.g. `--region="raster=raster_name"`<br />
*** Add `--import-raster=some/file.tiff` which imports (r.import) a raster file (same for vector and similarly for export).<br />
*** Add `--link-raster=some/file.tiff` which links (r.external) a raster file (same for vector and similarly for r.external.out).<br />
<br />
=== STAC (SpatioTemporal Asset Catalog) Integration ===<br />
<br />
Create new import and export capabilities for GRASS GIS which allow users to easily ingest data from STAC catalogs and export locations and mapsets as STAC specs for data discovery within STAC browsers. <br />
<br />
* Requirements: familiar with python, STAC specs<br />
* Mentor: Corey White<br />
* Co-mentor: Vaclav Petras, Anna Petrasova<br />
* Project length: 175 or 350 hours (take your pick)<br />
* Rating: medium<br />
* Expected Outcomes: completion of t.in.stac and t.out.stac<br />
* Test of skills:<br />
** suggest or implement solution for implementing t.out.stac using the prototype STAC spec https://github.com/tomorrownow/grass-stac-extension <br />
** suggest/implement solution for completing https://github.com/OSGeo/grass-addons/pull/802<br />
<br />
=== Add EODAG support to GRASS GIS ===<br />
<br />
[https://eodag.readthedocs.io/en/stable/ EODAG] is a Python library useful to download several satellite datasets from different providers (i.e., USGS, Copernicus, AWS, Planetary Computer, etc.). GRASS has various modules to download satellite data like i.sentinel.download, i.landsat.download, i.modis.download. However, they all use different libraries, some of them no longer maintained. Hence, implementing the use of EODAG as back-end for those tools would be very useful not only in terms of maintenance but also in terms of less code repetition. It would also open the possibility for new tools or a master tool to download other datasets directly from GRASS. <br />
<br />
* Requirements: familiar with Python<br />
* Project length: 175 or 350 hours<br />
* Mentor: Luca Delucchi<br />
* Co-mentor: Veronica Andreo<br />
* Proposed by: Luca Delucchi<br />
* Rating: medium<br />
* Expected Outcomes: 175 hours EODAG core library to be able to download products; 350 library + application at least to i.sentinel.download but hopefully also to i.landsat.download<br />
* Test of skills: https://github.com/OSGeo/grass-addons/issues/1033<br />
<br />
=== GUI: Add space-time datasets support in Data Catalog ===<br />
[[File:GUI_data_tab.png|400px|thumb|right|Data catalog]]<br />
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. <br />
<br />
* Requirements: familiar with Python<br />
* Project length: 175 or 350 hours<br />
* Mentor: Martin Landa<br />
* Co-mentor: Anna Petrasova<br />
* Proposed by: Martin Landa<br />
* Rating: medium<br />
* Expected Outcomes: 175 hours basic support for space-time raster datasets; 350 extended support also for other space-time datasets types (vector, 3D raster)<br />
* Test of skills:<br />
** suggest/implement solution for completing https://github.com/OSGeo/grass/issues/2599<br />
<br />
=== Add {your research idea} to GRASS GIS ===<br />
<br />
* In general, you can propose any topic, but you can specifically propose integrating your research or research idea into GRASS GIS.<br />
* Requirements:<br />
** Language:<br />
*** Depends on the project, often Python, sometimes C.<br />
*** Adding your latest ecological analysis <br />
** Proposal:<br />
*** Discuss relevance to GRASS GIS.<br />
*** Describe technical steps needed for integration.<br />
*** 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.<br />
*** Specify what research was done and what needs to be accomplished in order to have usable product at the end of summer.<br />
*** Specify who will provide the research expertise.<br />
* Project length: 175 or 350 hours (take your pick)<br />
* Rating: from low to hard<br />
* Mentors:<br />
** 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.<br />
** Possible technical mentors: Vaclav Petras, Anna Petrasova<br />
** Research mentors: Bring in an expert from your field, e.g., your academic advisor or project principal investigator (if needed).<br />
* Proposed by: Vaclav Petras<br />
* Expected outcome: Working feature which is integrated and merged at the end of the project.<br />
* Test and training tasks:<br />
** Create a test in Python for an existing tool in the grass-addons repository or in the core grass repository.<br />
<br />
=== Title of idea ===<br />
<br />
Description here<br />
<br />
* Requirements:<br />
* Project length: (175 or 350 hours) <br />
* Mentor: <br />
* Proposed by: <br />
* Rating: <br />
* Expected Outcomes: <br />
* Test of skills: <br />
* Other:<br />
<br />
== Tips for students ==<br />
<br />
* 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].<br />
* 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.<br />
* Follow some good practices in your ideas and proposals:<br />
** Stress why the project would be useful.<br />
** 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.<br />
** Be specific in the implementation (or at least as specific as you can).<br />
** Explain what the final product will look like and how it will work. You can add drawings or mock-ups.<br />
** Explain how the idea relates to existing GRASS GIS functions, features, and needs.<br />
** 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.<br />
* Compile GRASS GIS from source and prepare environment for development:<br />
** Read [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md CONTRIBUTING file] and [https://grasswiki.osgeo.org/wiki/Compile_and_Install compilation instructions].<br />
** If you get stuck with the setup, feel free to consult the [https://lists.osgeo.org/listinfo/grass-user grass-user mailing list].<br />
** Familiarize yourself with wiki:Submitting rules.<br />
* 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. <br />
* Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.<br />
<br />
* 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].<br />
<br />
{{GSoC}}</div>Annakrat