State of GRASS GIS: The Dawn of a New Era
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Petras, Vaclav
GRASS GIS is a well established, all-in-one geospatial number cruncher with Python interface, command line, and GUI. This talk will give an overview of new additions and highlight latest updates in version 7.8 and new major version 8.0. Major updates in 7.8 include Python 3 support, transition to PROJ 6+, easier batch processing, virtual raster mosaic, and improved data compression. Version 8.0 completely revamps the first-time user experience in GUI, streamlines how users interact with their data, and supports dark-themes. The development successfully runs on GitHub, several Docker images are available, and there is a growing number of Jupyter Notebooks. This talk gives an overview of the current state of the GRASS GIS project for both users and developers. The focus will be on new releases, specifically the new major version 8, and various updates including Python 3, PROJ, and GitHub transitions.
 We should all know that Gracie is a long-standing project. Backlash will give an update on the project. He's a research software engineer, open source developer and open source advocate. Receives masters in geoinformatics from the Czech Technical University and a PhD in geospatial analytics from North Carolina State University. Backlash is a member of the GRAS GIS development team as well as the project steering committee. So with that, over to you Backlash. I'm sure if you want to scare your screen now. Yeah. Okay. Great. All right. Thank you, though. So I will talk about the state of GRAS GIS and I'm really excited to talk to you about it today because I think we are at the dawn of a new era in GRAS GIS project. As Tom said, my name is Vasa Petraš. Sometimes I go by Vasek and I work at North Carolina State University, United States. But this talk or what I will present is really done by the whole community. So I would like to both acknowledge that and tell you a little bit about the GRAS community. In the community, we sometimes don't really have distinctions between users and developers and in that sense, it's very open. And as you understand when you are part of the OSG or the Phosphorgy community, we include all people who are writing code but also people who are doing documentation or translations. Lastly, in February 2021, we have new elections for the Project Steering Committee and we have a new chair, Veronica Andrej. And the place to meet the community is, of course, online. We have a traditional user mailing list with archives since 1991, which is quite a unique thing. We see increasing usage of GS Stack Exchange and GitHub discussions is a new thing we just enabled. And of course, that doesn't, that's not enough for everybody. So we also have a community of companies who are providing commercial support that includes my employer and C-State University. If you don't see your name here on this list and you think you should be listed here, tell me privately or write to GRAS a deaf mailing list and you will fix that. If you are not familiar with GRAS GS, let me tell you that obviously it's a free and open source, which means that you can use it, modify it, share it any way you want as long as you comply with the GNU GPL license. GRAS GS is split into tools or modules. We have over 500 of these modules in the core version of GRAS GS, which you install and then additional 300 plus add-ons, which you can install and extend your local installation of GRAS by that. GRAS GS has different interfaces, which is you different people or different workflows. There is a Graphical User Interface, Command Line Interface, Python API, and there is also CIP API and libraries for creating really fast processing tools. A lot of people are using GRAS GS through other interfaces like the R package or QGS processing plugin or the GRAS GS plugin in QGS. GRAS GS tries to cover a lot of different data types, including vectors, rasters, but also less common 3D rasters and space time data sets. The algorithms itself in GRAS GS are based on scientific papers or there are scientific papers associated with the tool itself and the tool is or the algorithm is very unique. These references are included in the documentation. We can also see usage of GRAS GS in scientific literature. It's a continuing trend. Now we are also experimenting with Google's color profile for GRAS GS as a project. We have a DOI for GRAS GIS. There is a DOI for GRAS GS as a project and for every release so that it facilitates software site decisions, which is quite a new thing in academic community. One of the big design drivers in GRAS GS is innovating with stability, which means that of course every time we have some improvements that brings changes, but we are trying to introduce breaking changes only when needed. For example, when we have Graphical User Interface and that changes as needed and for Python API we edit that in version 6 and that over time it took over the leading position from Bash as main scripting interface. It measured over the course of version 7 and now we are planning some additions for version 8.2. However, the basic things continue to work in the same way. For example, Raster Algebra, which you would use in GRAS GS version 5 in 2002, the expression would just work fine in version 8, which we are about to release, except for the white space around equals operator, which I think is pretty good. And the other design direction I mentioned already is that GRAS is trying to cover a lot of different things. So in the software when you install it, all the mature tools are already available, they are without additional installation, but you can install additional ones from GRAS at on-server repository if you need that. As for what we are planning for GRAS GS 8, which many people are now expecting, we plan to release it this fall. This is a revised timeline, which is not a surprise, but we are hoping to do it now, finally. And then in spring we hope to release version 8.2, which should include quite exciting results from the Google Summer of Code 2021, which I will mention later on. So what is the new era I am so excited about? Well, we completely changed the first time user experience in GRAS GS. The initial project, which in GRAS GS is called Location, is set up automatically and the user is given suggestions on what to do next. This really means there is no more startup screen. If you use GRAS, you know there was a startup screen, there is no more startup screen. And we plan to go even further in version 8.2. We are now doing refactoring of the code and some preview of a single window interface, and this will be opt-in in version 8.2. If you want to know more about all this, there is a talk by Linda, which is called I Hated the Way GRAS started, so I changed it. So I think this will be a fun talk and you should attend it. But there is even more. We have now a centralized data management tab in the Graphic User Interface. You can do all these things from Command Line or from Python, but now there is a really nice way to do it in the Graphic User Interface. It was possible, but just not that great. Asges now supports Direct Team. If your operating system has a Direct Team, and this is already some old news, but we migrated to GitHub, which meant also migration to Git. We are using PRs for code and issues on GitHub, and we are also leveraging GitHub actions quite a bit. This relates to the fact that now the code is checked against Flake8. We also reformatted our Python code using black just to make it simple. It's just formatted by black, and that's it, which is exactly the black philosophy. And we removed most of GCC and CLN warnings in C code, and we are now checking it for every pull request, and we are running also code queue tests on the pull requests. To improve cloud readiness of grass GIS, we are providing Docker images. We are building them automatically from the source code using GitHub actions for release and for the development version from the main branch. There are different flavors, Alpine, Debian, and Ubuntu. If you think there should be more, please let us know. And here is good too. I think we already got some suggestions on this conference. And another cloud item is the Actinia project, which is a REST API which you can use to do computations in grass GIS in cloud. It's not part of grass GIS, it's a third party project, but it's open source, and it's done by our own Marcus Nettler and his team, and there is a dedicated talk about that as well. And we worked also on HPC-originous grasses used on HPC hyperperformance computing clusters a lot, but now we improved and included some of some recipes to actually build it, and we have a better integration with conda environments, and that's hopefully an ongoing trend, and we'll get even better. I'm not so sure how to think about it or what I feel about this, but we now have a Moscow grassy the hungry cow, and the cow is always hungry for more. So we have actually some more improvements coming in 80. We are replacing the Liblas library with Pdl for our LiDAR point import, and especially for the binning module, which now can do actually much more than the original one, not only thanks to Pdl, but also thanks to the additional point filtering and binning methods we included. We updated our code to support latest Proch and GDEL versions, which means that we have all the great and cool features which Proch and GDEL have, and then we also worked on some of the algorithms in GrassGS. For example, the Voronoi, which is the vector module to generate Voronoi polygons. The module can now create areas, columns, and center lines, which is the violet lines you can see on the picture. Another big addition for 80 is that each raster map will now have a semantic label, which is a metadata item, and that doesn't have to be unique, and that's kind of the problem. The point of it is that each raster can have this label and that can be used in different contexts, and the primary one or the current usage in GrassGS itself is that it is used in image classification to identify individual bands, which then allows us in the classification workflow to train the algorithm on one set of data and then easily port the generated signature files to another scene, or easily use it as a real note, not porting there. They are portable just by themselves. If you don't need to use them or don't want to use them, you can use it without it. So that's again the idea of keeping the things the way they were when it works. And when you are working with GrassGS, you know that usually import data, but you don't have to always do it, you can also just link them, and that's for raster data that's done with our external module, and that now is improved, and it's using more of GDOL features, which allows us to do the imports really fast, or the linking really fast. And for some workflows, that means that the linking takes almost no time. And there is even more coming in 8.2, which should be around spring next year. We have now several of the core raster modules parallelized, specifically parallelized with OpenMP, and that's work done by Aaron, who we were doing during Google Summer of Code on this. And yet another Google Summer of Code work done by Caitlin was on integration of GrassGS with Jupyter Notebooks, and you could of course use GrassGS before with Python and with Jupyter Notebooks, but now we are including a dedicated package or sub-package in GrassGS, which allows you to use it more smoothly, specifically in notebooks, which means easier setup, more intuitive workflow, and also visualization of the data in different ways. You can do classic GrassGS rendering, you can show data on interactive maps, and you can also look at 3D images. And finally for 8.2, we are also including, or rather planning to include, spatial query of projections when you are setting up a new project or a new location, where you will be able to select coordinate reference system spatially rather than just by text search. And we have much more additions by our broader community, which most of these additions are usually in the GrassGS at-hones repository, and that will be something you would install. In addition to the basic GrassGS installation, one is multi-resolution valley-bottom flatness index, another is a tool to create weighted flow accumulation, sub-water chest-3D networks, and you can learn more about this in a workshop or other workshop material, the workshop already happened at this conference, but in the slide there is a link to that material. Yet another thing which will be presented on this conference in a talk is module called R-area create-weight, which is a weighting tool for areas, and there is much more. Here is a list of some of the tools which are helping with automated download import, but also analysis of some of the common datasets like Sentinel, Landsat, USGS datasets, or NETCDF files, and there are two tools which are relevant to that, so you can again get those from the slides, and maybe you have noticed at the bottom of each slide I always included people who worked on that specific feature, here I couldn't fit all the people, I included their institutions, and that's something I would like to actually highlight more, that we have lots of different institutions working together directly or indirectly on GrassGS, and if you are from such an institution, we would like you to invite to contact us and tell us more about how we can better acknowledge you on the website or in presentations like this. As for the team I'm working with at the Center for Geospatial Analytics at NC State University, we are working on an urban growth tool, Futures, we are working on a pathogen and pest spread simulation, ARPOPS spread, and also about yet another interface for interacting with geospatial simulations, Dangerous landscape, and you can get these slides, so you can look at my favorite list of resources, and lastly I would like to invite you to get involved more with GrassGS, you can of course contribute code, as I mentioned for better or worse, we are now on GitHub and everything happens through GitHub, but you can also join a community sprint, you can contribute in many other ways than just code, whether it's translations or documentation, or anything else you can think of. And of course money and employee time donations are important and that's really something that is changing the code and changing how everything looks like, and newly we have also an open collective account, and there's a community sprint which was already mentioned, so you can see us there, and that's all from me, thank you. Great, thank you Vaklav for the great update on what's new and upcoming and the status of the GrassGIS project, and now I'm going to move over to the questions, there's a question here, will the new GUI be available for windgrass? Yes, yes, it will be, it's actually based on the one which you are already using, the one which is internally called WX GUI, so it will be there. In 8.2 it will be an opt-in preview, so you will have to go to MNE and enable it if you want to use it. Great, excellent, there's another question, is there an updated roadmap? Users have reports breaking plugins and current stable release 7.8.5. Right, so the next version 7.8.6 should fix that, that was caused by us renaming all the branches in all the repositories and changing the add-on repository structure for Grass8. So we are not really happy about it, but it should be fixed with the next batch release. Great, good to know. I don't see any other questions in the questions tab, folks are encouraged to provide some questions and Vaklav can address them. I have a couple of questions from my perspective, if that's okay, has there been any work or what the status is on the evolving, on the new OGC API family of specifications in Grass in terms of integrating the new specifications? Right, I'm probably not the best person to ask that question, so I believe that without the answer, it's alright. Okay, no, that's all good. Let's see, another question from the audience, what happens to add-ons coded for version 7.x? Do they need to be modified to be compatible with version 8? Yeah, that's a good question and I think the general answer is no. What we will do is that we will just carry over all the add-ons from the Grass 7 branch in add-ons repository to Grass 8. So if you are a user or a developer of one of these add-ons, after that happens, which will be probably after the release candidate is released for 8.0, you should test it and it should work. If it works with the development version of Grass.js now, it will work with 8.2. There are some changes which are required, which I know of, but somebody is already working on it. I think we are in a good position there. Great. Another question from myself, what is the current situation with Grass or plans or if there's any information on how Grass deals with search and catalogs and metadata and discovering data sense? So usually the general approach in Grass.js is to use an OSG library if there is such library and then the specific things to resolve them in a module or a tool. So for anything which is not purely analytical, we prefer to have it in a separate module or externalized to some library. Nice. Excellent. Another great example of the extensibility of Grass, so that's great. I'm going to look back into the audience for any final question. I think I didn't actually completely answer the question about the roadmap, the 786 version. We plan to release it this fall and hopefully in the next couple of weeks or next month or something like that, although we don't have a set date. Great. I'm just looking out into the audience for any final questions. I think that's everything from now. Any other final comments from you, VatLav, before we break? No, just thank you for sharing. Thank you everybody for listening. Awesome. That's great. So thank you, VatLav. And I'd like to thank all of the speakers this morning. We saw a good example of some exciting projects from OSG. So again, thank you to all the speakers. Thank you for attending this session. And I wish you all a good Phosphor G 2021. Thank you. Thank you.
 We should all know that Gracie is a long-standing project.  Backlash will give an update on the project.  He's a research software engineer, open source developer and open source advocate.  Receives masters in geoinformatics from the Czech Technical University and a PhD in geospatial  analytics from North Carolina State University.  Backlash is a member of the GRAS GIS development team as well as the project steering committee.  So with that, over to you Backlash.  I'm sure if you want to scare your screen now.  Yeah.  Okay.  Great.  All right.  Thank you, though.  So I will talk about the state of GRAS GIS and I'm really excited to talk to you about  it today because I think we are at the dawn of a new era in GRAS GIS project.  As Tom said, my name is Vasa Petraš.  Sometimes I go by Vasek and I work at North Carolina State University, United States.  But this talk or what I will present is really done by the whole community.  So I would like to both acknowledge that and tell you a little bit about the GRAS community.  In the community, we sometimes don't really have distinctions between users and developers  and in that sense, it's very open.  And as you understand when you are part of the OSG or the Phosphorgy community, we include  all people who are writing code but also people who are doing documentation or translations.  Lastly, in February 2021, we have new elections for the Project Steering Committee and we  have a new chair, Veronica Andrej.  And the place to meet the community is, of course, online.  We have a traditional user mailing list with archives since 1991, which is quite a unique  thing.  We see increasing usage of GS Stack Exchange and GitHub discussions is a new thing we just  enabled.  And of course, that doesn't, that's not enough for everybody.  So we also have a community of companies who are providing commercial support that includes  my employer and C-State University.  If you don't see your name here on this list and you think you should be listed here, tell  me privately or write to GRAS a deaf mailing list and you will fix that.  If you are not familiar with GRAS GS, let me tell you that obviously it's a free and  open source, which means that you can use it, modify it, share it any way you want as  long as you comply with the GNU GPL license.  GRAS GS is split into tools or modules.  We have over 500 of these modules in the core version of GRAS GS, which you install and  then additional 300 plus add-ons, which you can install and extend your local installation  of GRAS by that.  GRAS GS has different interfaces, which is you different people or different workflows.  There is a Graphical User Interface, Command Line Interface, Python API, and there is  also CIP API and libraries for creating really fast processing tools.  A lot of people are using GRAS GS through other interfaces like the R package or QGS  processing plugin or the GRAS GS plugin in QGS.  GRAS GS tries to cover a lot of different data types, including vectors, rasters, but  also less common 3D rasters and space time data sets.  The algorithms itself in GRAS GS are based on scientific papers or there are scientific  papers associated with the tool itself and the tool is or the algorithm is very unique.  These references are included in the documentation.  We can also see usage of GRAS GS in scientific literature.  It's a continuing trend.  Now we are also experimenting with Google's color profile for GRAS GS as a project.  We have a DOI for GRAS GIS.  There is a DOI for GRAS GS as a project and for every release so that it facilitates software  site decisions, which is quite a new thing in academic community.  One of the big design drivers in GRAS GS is innovating with stability, which means that  of course every time we have some improvements that brings changes, but we are trying to  introduce breaking changes only when needed.  For example, when we have Graphical User Interface and that changes as needed and for  Python API we edit that in version 6 and that over time it took over the leading position  from Bash as main scripting interface.  It measured over the course of version 7 and now we are planning some additions for version  8.2.  However, the basic things continue to work in the same way.  For example, Raster Algebra, which you would use in GRAS GS version 5 in 2002, the expression  would just work fine in version 8, which we are about to release, except for the white  space around equals operator, which I think is pretty good.  And the other design direction I mentioned already is that GRAS is trying to cover a  lot of different things.  So in the software when you install it, all the mature tools are already available, they  are without additional installation, but you can install additional ones from GRAS at  on-server repository if you need that.  As for what we are planning for GRAS GS 8, which many people are now expecting, we plan  to release it this fall.  This is a revised timeline, which is not a surprise, but we are hoping to do it now,  finally.  And then in spring we hope to release version 8.2, which should include quite exciting results  from the Google Summer of Code 2021, which I will mention later on.  So what is the new era I am so excited about?  Well, we completely changed the first time user experience in GRAS GS.  The initial project, which in GRAS GS is called Location, is set up automatically and the  user is given suggestions on what to do next.  This really means there is no more startup screen.  If you use GRAS, you know there was a startup screen, there is no more startup screen.  And we plan to go even further in version 8.2.  We are now doing refactoring of the code and some preview of a single window interface,  and this will be opt-in in version 8.2.  If you want to know more about all this, there is a talk by Linda, which is called I Hated  the Way GRAS started, so I changed it.  So I think this will be a fun talk and you should attend it.  But there is even more.  We have now a centralized data management tab in the Graphic User Interface.  You can do all these things from Command Line or from Python, but now there is a really  nice way to do it in the Graphic User Interface.  It was possible, but just not that great.  Asges now supports Direct Team.  If your operating system has a Direct Team, and this is already some old news, but we  migrated to GitHub, which meant also migration to Git.  We are using PRs for code and issues on GitHub, and we are also leveraging GitHub actions  quite a bit.  This relates to the fact that now the code is checked against Flake8.  We also reformatted our Python code using black just to make it simple.  It's just formatted by black, and that's it, which is exactly the black philosophy.  And we removed most of GCC and CLN warnings in C code, and we are now checking it for  every pull request, and we are running also code queue tests on the pull requests.  To improve cloud readiness of grass GIS, we are providing Docker images.  We are building them automatically from the source code using GitHub actions for release  and for the development version from the main branch.  There are different flavors, Alpine, Debian, and Ubuntu.  If you think there should be more, please let us know.  And here is good too.  I think we already got some suggestions on this conference.  And another cloud item is the Actinia project, which is a REST API which you can use to do  computations in grass GIS in cloud.  It's not part of grass GIS, it's a third party project, but it's open source, and it's  done by our own Marcus Nettler and his team, and there is a dedicated talk about that as  well.  And we worked also on HPC-originous grasses used on HPC hyperperformance computing clusters  a lot, but now we improved and included some of some recipes to actually build it, and we  have a better integration with conda environments, and that's hopefully an ongoing trend, and  we'll get even better.  I'm not so sure how to think about it or what I feel about this, but we now have a  Moscow grassy the hungry cow, and the cow is always hungry for more.  So we have actually some more improvements coming in 80.  We are replacing the Liblas library with Pdl for our LiDAR point import, and especially  for the binning module, which now can do actually much more than the original one, not only  thanks to Pdl, but also thanks to the additional point filtering and binning methods we included.  We updated our code to support latest Proch and GDEL versions, which means that we have  all the great and cool features which Proch and GDEL have, and then we also worked on  some of the algorithms in GrassGS.  For example, the Voronoi, which is the vector module to generate Voronoi polygons.  The module can now create areas, columns, and center lines, which is the violet lines  you can see on the picture.  Another big addition for 80 is that each raster map will now have a semantic label, which  is a metadata item, and that doesn't have to be unique, and that's kind of the problem.  The point of it is that each raster can have this label and that can be used in different  contexts, and the primary one or the current usage in GrassGS itself is that it is used  in image classification to identify individual bands, which then allows us in the classification  workflow to train the algorithm on one set of data and then easily port the generated  signature files to another scene, or easily use it as a real note, not porting there.  They are portable just by themselves.  If you don't need to use them or don't want to use them, you can use it without it.  So that's again the idea of keeping the things the way they were when it works.  And when you are working with GrassGS, you know that usually import data, but you don't  have to always do it, you can also just link them, and that's for raster data that's done  with our external module, and that now is improved, and it's using more of GDOL features,  which allows us to do the imports really fast, or the linking really fast.  And for some workflows, that means that the linking takes almost no time.  And there is even more coming in 8.2, which should be around spring next year.  We have now several of the core raster modules parallelized, specifically parallelized with  OpenMP, and that's work done by Aaron, who we were doing during Google Summer of Code  on this.  And yet another Google Summer of Code work done by Caitlin was on integration of GrassGS  with Jupyter Notebooks, and you could of course use GrassGS before with Python and with Jupyter  Notebooks, but now we are including a dedicated package or sub-package in GrassGS, which allows  you to use it more smoothly, specifically in notebooks, which means easier setup, more  intuitive workflow, and also visualization of the data in different ways.  You can do classic GrassGS rendering, you can show data on interactive maps, and you  can also look at 3D images.  And finally for 8.2, we are also including, or rather planning to include, spatial query  of projections when you are setting up a new project or a new location, where you will  be able to select coordinate reference system spatially rather than just by text search.  And we have much more additions by our broader community, which most of these additions are  usually in the GrassGS at-hones repository, and that will be something you would install.  In addition to the basic GrassGS installation, one is multi-resolution valley-bottom flatness  index, another is a tool to create weighted flow accumulation, sub-water chest-3D networks,  and you can learn more about this in a workshop or other workshop material, the workshop already  happened at this conference, but in the slide there is a link to that material.  Yet another thing which will be presented on this conference in a talk is module called  R-area create-weight, which is a weighting tool for areas, and there is much more.  Here is a list of some of the tools which are helping with automated download import,  but also analysis of some of the common datasets like Sentinel, Landsat, USGS datasets, or NETCDF  files, and there are two tools which are relevant to that, so you can again get those from the  slides, and maybe you have noticed at the bottom of each slide I always included people  who worked on that specific feature, here I couldn't fit all the people, I included their  institutions, and that's something I would like to actually highlight more, that we have  lots of different institutions working together directly or indirectly on GrassGS, and if  you are from such an institution, we would like you to invite to contact us and tell  us more about how we can better acknowledge you on the website or in presentations like  this.  As for the team I'm working with at the Center for Geospatial Analytics at NC State University,  we are working on an urban growth tool, Futures, we are working on a pathogen and pest spread  simulation, ARPOPS spread, and also about yet another interface for interacting with geospatial  simulations, Dangerous landscape, and you can get these slides, so you can look at my favorite  list of resources, and lastly I would like to invite you to get involved more with GrassGS,  you can of course contribute code, as I mentioned for better or worse, we are now on GitHub  and everything happens through GitHub, but you can also join a community sprint, you  can contribute in many other ways than just code, whether it's translations or documentation,  or anything else you can think of.  And of course money and employee time donations are important and that's really something  that is changing the code and changing how everything looks like, and newly we have also  an open collective account, and there's a community sprint which was already mentioned,  so you can see us there, and that's all from me, thank you.  Great, thank you Vaklav for the great update on what's new and upcoming and the status  of the GrassGIS project, and now I'm going to move over to the questions, there's a question  here, will the new GUI be available for windgrass?  Yes, yes, it will be, it's actually based on the one which you are already using, the  one which is internally called WX GUI, so it will be there.  In 8.2 it will be an opt-in preview, so you will have to go to MNE and enable it if you  want to use it.  Great, excellent, there's another question, is there an updated roadmap?  Users have reports breaking plugins and current stable release 7.8.5.  Right, so the next version 7.8.6 should fix that, that was caused by us renaming all the  branches in all the repositories and changing the add-on repository structure for Grass8.  So we are not really happy about it, but it should be fixed with the next batch release.  Great, good to know.  I don't see any other questions in the questions tab, folks are encouraged to provide some questions  and Vaklav can address them.  I have a couple of questions from my perspective, if that's okay, has there been any work or  what the status is on the evolving, on the new OGC API family of specifications in Grass  in terms of integrating the new specifications?  Right, I'm probably not the best person to ask that question, so I believe that without  the answer, it's alright.  Okay, no, that's all good.  Let's see, another question from the audience, what happens to add-ons coded for version  7.x?  Do they need to be modified to be compatible with version 8?  Yeah, that's a good question and I think the general answer is no.  What we will do is that we will just carry over all the add-ons from the Grass 7 branch  in add-ons repository to Grass 8.  So if you are a user or a developer of one of these add-ons, after that happens, which  will be probably after the release candidate is released for 8.0, you should test it and  it should work.  If it works with the development version of Grass.js now, it will work with 8.2.  There are some changes which are required, which I know of, but somebody is already working  on it.  I think we are in a good position there.  Great.  Another question from myself, what is the current situation with Grass or plans or if there's  any information on how Grass deals with search and catalogs and metadata and discovering  data sense?  So usually the general approach in Grass.js is to use an OSG library if there is such  library and then the specific things to resolve them in a module or a tool.  So for anything which is not purely analytical, we prefer to have it in a separate module or  externalized to some library.  Nice.  Excellent.  Another great example of the extensibility of Grass, so that's great.  I'm going to look back into the audience for any final question.  I think I didn't actually completely answer the question about the roadmap, the 786 version.  We plan to release it this fall and hopefully in the next couple of weeks or next month  or something like that, although we don't have a set date.  Great.  I'm just looking out into the audience for any final questions.  I think that's everything from now.  Any other final comments from you, VatLav, before we break?  No, just thank you for sharing.  Thank you everybody for listening.  Awesome.  That's great.  So thank you, VatLav.  And I'd like to thank all of the speakers this morning.  We saw a good example of some exciting projects from OSG.  So again, thank you to all the speakers.  Thank you for attending this session.  And I wish you all a good Phosphor G 2021.  Thank you.  Thank you.
FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_0_131.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_132_1223.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_1224_1403.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_1404_1811.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_1812_2051.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_2052_3407.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_3408_4775.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_4776_11795.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_11796_11927.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_11928_12359.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_12360_13259.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_13260_13763.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_13764_14003.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_14004_14567.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_14568_17147.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_17148_17867.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_17868_18383.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_18384_19523.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_19524_20219.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_20220_22343.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_22344_23495.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_23496_24371.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_24372_25859.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_25860_26939.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_26940_27119.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_27120_27719.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_27720_28319.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_28320_30311.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_30312_30707.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_30708_30875.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_30876_31067.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_31068_31355.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_31356_31523.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_31524_31883.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_31884_32171.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_32172_32675.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_32676_32891.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_32892_32999.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_33000_42335.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_42336_42443.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_42444_42515.png FOSS4G_-_State_of_GRASS_GIS__The_Dawn_of_a_New_Era_wk3X_Vzp8zg_42516_42632.png