Re: [GRASS-dev] GSoC Ideas
On Sun, Mar 3, 2024 at 4:07 PM Luca Delucchi wrote: > Hi Anna, > > On Fri, 1 Mar 2024 at 17:30, Anna Petrášová wrote: > > > > We have already students wanting to work on github issues linked as test > of skills. Martin and Luca, your ideas don't have a test of skills, please > add it there as soon as possible, otherwise we can't really use the idea, > test of skills is required by OSGeo. > > > > Thanks for the reminder, I created this issue > https://github.com/OSGeo/grass-addons/issues/1033, is it doable or too > complicated? > > Sure, that works! > > Thank you > > > > -- > ciao > Luca > > www.lucadelu.org > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
Hi Anna, On Fri, 1 Mar 2024 at 17:30, Anna Petrášová wrote: > > We have already students wanting to work on github issues linked as test of > skills. Martin and Luca, your ideas don't have a test of skills, please add > it there as soon as possible, otherwise we can't really use the idea, test of > skills is required by OSGeo. > Thanks for the reminder, I created this issue https://github.com/OSGeo/grass-addons/issues/1033, is it doable or too complicated? > Thank you > -- ciao Luca www.lucadelu.org ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
Hi Anna, pá 1. 3. 2024 v 17:35 odesílatel Anna Petrášová napsal: > Martin, how about using https://github.com/OSGeo/grass/issues/2599 as a > test? > good idea, thanks for pointing this out. Martin -- Martin Landa https://geomatics.fsv.cvut.cz/en/employees/martin-landa/ http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
Martin, how about using https://github.com/OSGeo/grass/issues/2599 as a test? On Fri, Mar 1, 2024 at 11:29 AM Anna Petrášová wrote: > We have already students wanting to work on github issues linked as test > of skills. Martin and Luca, your ideas don't have a test of skills, please > add it there as soon as possible, otherwise we can't really use the idea, > test of skills is required by OSGeo. > > Thank you > > On Mon, Feb 26, 2024 at 1:32 PM Anna Petrášová > wrote: > >> Good news, OSGeo was accepted [1]. We need to do some advertising now. >> >> [1] https://lists.osgeo.org/pipermail/discuss/2024-February/040113.html >> >> On Sat, Feb 24, 2024 at 9:04 AM Anna Petrášová >> wrote: >> >>> >>> >>> On Fri, Feb 23, 2024, 6:11 PM Martin Landa >>> wrote: >>> Hi, so 3. 2. 2024 v 5:34 odesílatel Anna Petrášová via grass-dev < grass-dev@lists.osgeo.org> napsal: > I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac > wiki, which I think we should be moving away from): > https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 > > It's not updated yet, I plan to add more topics. If you want to mentor > a topic, we can discuss it here. > I add a new topic related to space-time datasets and Data Catalog [1]. Martin >>> >>> Thanks for adding the topic, please also include a test of skills and at >>> least for now assign yourself as a mentor, I can be a co-mentor. >>> >>> Anna >>> [1] https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024#GUI%3A_Add_space-time_datasets_support_in_Data_Catalog -- Martin Landa https://geomatics.fsv.cvut.cz/en/employees/martin-landa/ http://gismentors.cz/mentors/landa >>> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
We have already students wanting to work on github issues linked as test of skills. Martin and Luca, your ideas don't have a test of skills, please add it there as soon as possible, otherwise we can't really use the idea, test of skills is required by OSGeo. Thank you On Mon, Feb 26, 2024 at 1:32 PM Anna Petrášová wrote: > Good news, OSGeo was accepted [1]. We need to do some advertising now. > > [1] https://lists.osgeo.org/pipermail/discuss/2024-February/040113.html > > On Sat, Feb 24, 2024 at 9:04 AM Anna Petrášová > wrote: > >> >> >> On Fri, Feb 23, 2024, 6:11 PM Martin Landa >> wrote: >> >>> Hi, >>> >>> so 3. 2. 2024 v 5:34 odesílatel Anna Petrášová via grass-dev < >>> grass-dev@lists.osgeo.org> napsal: >>> I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki, which I think we should be moving away from): https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 It's not updated yet, I plan to add more topics. If you want to mentor a topic, we can discuss it here. >>> >>> I add a new topic related to space-time datasets and Data Catalog [1]. >>> Martin >>> >> >> Thanks for adding the topic, please also include a test of skills and at >> least for now assign yourself as a mentor, I can be a co-mentor. >> >> Anna >> >>> >>> [1] >>> https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024#GUI%3A_Add_space-time_datasets_support_in_Data_Catalog >>> >>> -- >>> Martin Landa >>> https://geomatics.fsv.cvut.cz/en/employees/martin-landa/ >>> http://gismentors.cz/mentors/landa >>> >> ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
Good news, OSGeo was accepted [1]. We need to do some advertising now. [1] https://lists.osgeo.org/pipermail/discuss/2024-February/040113.html On Sat, Feb 24, 2024 at 9:04 AM Anna Petrášová wrote: > > > On Fri, Feb 23, 2024, 6:11 PM Martin Landa wrote: > >> Hi, >> >> so 3. 2. 2024 v 5:34 odesílatel Anna Petrášová via grass-dev < >> grass-dev@lists.osgeo.org> napsal: >> >>> I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki, >>> which I think we should be moving away from): >>> https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 >>> >>> It's not updated yet, I plan to add more topics. If you want to mentor a >>> topic, we can discuss it here. >>> >> >> I add a new topic related to space-time datasets and Data Catalog [1]. >> Martin >> > > Thanks for adding the topic, please also include a test of skills and at > least for now assign yourself as a mentor, I can be a co-mentor. > > Anna > >> >> [1] >> https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024#GUI%3A_Add_space-time_datasets_support_in_Data_Catalog >> >> -- >> Martin Landa >> https://geomatics.fsv.cvut.cz/en/employees/martin-landa/ >> http://gismentors.cz/mentors/landa >> > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
On Fri, Feb 23, 2024, 6:11 PM Martin Landa wrote: > Hi, > > so 3. 2. 2024 v 5:34 odesílatel Anna Petrášová via grass-dev < > grass-dev@lists.osgeo.org> napsal: > >> I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki, >> which I think we should be moving away from): >> https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 >> >> It's not updated yet, I plan to add more topics. If you want to mentor a >> topic, we can discuss it here. >> > > I add a new topic related to space-time datasets and Data Catalog [1]. > Martin > Thanks for adding the topic, please also include a test of skills and at least for now assign yourself as a mentor, I can be a co-mentor. Anna > > [1] > https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024#GUI%3A_Add_space-time_datasets_support_in_Data_Catalog > > -- > Martin Landa > https://geomatics.fsv.cvut.cz/en/employees/martin-landa/ > http://gismentors.cz/mentors/landa > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
Hi, so 3. 2. 2024 v 5:34 odesílatel Anna Petrášová via grass-dev < grass-dev@lists.osgeo.org> napsal: > I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki, > which I think we should be moving away from): > https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 > > It's not updated yet, I plan to add more topics. If you want to mentor a > topic, we can discuss it here. > I add a new topic related to space-time datasets and Data Catalog [1]. Martin [1] https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024#GUI%3A_Add_space-time_datasets_support_in_Data_Catalog -- Martin Landa https://geomatics.fsv.cvut.cz/en/employees/martin-landa/ http://gismentors.cz/mentors/landa ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
gt; our intro tutorials, including opening a web browser with the chosen > tutorial and adding some layers to the map view; two clicks (+ file > browsing) to have users raster or vector data displayed). > I think Vashek's point was to gently remind you there has been a lot of discussion going on in the past, not to resurrect one of those ideas:) > > Linda, in your paper you wrote: „Since both options were favorably > rated (85% responded positively to the first-run wizard and 74% to > info bars), we decided to implement an info bar as a technically > simpler and more flexible solution.“ The idea of this GSOC proposal > was to implement in some form the second option that would allow to > perform A/B testing with real users. As you (et al.) have done a huge > work with the codebase, now it would be much easier to implement than > some years a go. > I also understand that users want to start working with the software > right away. But here is a catch – most likely nobody will start GRASS > to work with data provided by the demo project. Either they will start > GRASS to do some exercises in a training course / to follow a tutorial > (= download one of sample datasets, add some layer to the map view), > or to work with data they have to solve the analysis problem they are > facing (= create a new project from supplied data, import file, add it > to the map view, display warning about computational region in your > info bar, if imported data were vectors and not raster). If user > cancels the wizard, just fine. Let him enjoy the demo project and > display first time screen also on the next startup iff there is no > project with data in the GISDBASE. This would not interfere with a > big, fat warning if someone tries to import external data into sample > projects (NC, Spearfish, ...) or any other enhancements that could be > done. > I agree with a lot of points you are making but I guess I still don't understand exactly what your suggestion is and how it would make things better and for whom... > Huh, I think I answered most of points from previous emails (except > going into details of potential architecture (thus Anna for wxPython > expertise) or user friendliness (thus Vero)). Thank you to everyone > who read this far and sorry for all unintentional fuss I caused. > Probably Linda you are right – it is too ambitious for an experimental > project that might get tossed away at the end. I see that Anna has > already removed the idea from the wiki, most likely for good. Do not > restore it, let it be so. We can return to this idea at any point > later if we feel need for it. I have plenty to do to fix pointer > juggling bugs in the new module I have almost finished (anisotropic > smoothing). > Māris. > > piektd., 2024. g. 16. febr., plkst. 10:41 — lietotājs Linda Kladivová > () rakstīja: > > > > Hello Māris, > > > > just to add some other info, we did several surveys among GRASS users > about first-time user experience with Anna, Martin and Vashek and we also > tested old and new startup mechanisms in a real environment within the > usability testing - you can have a look at our article: > https://www.mdpi.com/2220-9964/12/9/376. > > > > As Anna has already written, the results of usability testing were > indeed mixed but I would like to emphasize one thing - most of the > usability participants (first-time users) said to me that they simply > expect they will be directly redirected to the main software window where > they can start working without knowing anything about the software. The > current "info bar" solution goes in that direction and although I have to > admit that it has flaws there are ways how to make it better and Anna has > already written some points. > > > > I think it would be nice to focus on how to make the current solution > better (it is definitely doable and even desirable) and not go back to some > alternatives to the old solution. > > Above that, it would be extremely time-consuming to implement any dialog > wizards and at the same time the impact of that "dialog" solution is very > uncertain - one important thing we also learned from surveys and > discussions inside/outside the community is that the one good generally > acceptable solution simply does not exist here - it will always be a > compromise. > > > > Just my two cents. :-) > > Linda > > > > -- Původní e-mail -- > > Od: Maris Nartiss via grass-dev > > Komu: Anna Petrášová , Veronica Andreo < > veroand...@gmail.com> > > Kopie: GRASS-dev > > Datum: 15. 2. 2024 13:04:24 > > Předmět: Re: [GRASS-dev] GSoC Ideas > > > > Hello Anna, Vero. > > I added the welcome s
Re: [GRASS-dev] GSoC Ideas
Hi all, Johnny Come Lately here. Like and subscribe. This thread pretty much reenacted the long discussion in Prague last June. The only conclusion at the time was for this proposal to not jeopardise the work done on the new GUI. It seems that Maris is sticking to that. I hope this proposal can still take shape at some point, if nothing else to understand its implications. On a broader perspective, there is an obvious tension here between ease-of-use and correctness-of-use. A ready-to-use GUI will always be the preferred choice of users, both novice or seasoned (just give me the damn CLI!). But the educational aspect of GRASS should not be disregarded either. As an (other) example of how this tension has concrete implications, I leave below a link to the document by the Australia/New Zealand authority trying to dissuade communities like this one from using the WGS84 datum ensemble. Best. https://www.icsm.gov.au/sites/default/files/GMIWG%20Advisory%20on%20WGS%2084%20and%20Web%20Mapping%20%E2%80%93%2015%20June%202020.pdf -- Luís Sent with Proton Mail secure email. On Friday, 16 February 2024 at 19:42, Maris Nartiss via grass-dev wrote: > Hello all, > although I expected some discussion, I didn't expect a kind of Spanish > Inquisition. To make things easier for me (I still have to type single > handed), I'll try to address all issues in a single email. > > At first we all must agree that coordinate systems, geospatial data > and thus also GIS is hard. We will never have a perfect (the final) > solution or a solution we all can agree on, but it shouldn't stop us > from trying out new things. > > Second – from the GSOC web site: „Google Summer of Code is a global, > online program focused on bringing new contributors into open source > software development.“ It is not „get some code to merge into next > release“ and thus developing an experimental feature still is a good > way how to get familiar with the code base, contributing to os, issues > and features of GRASS. > > Third – we should improve GRASS with a goal of making easy to do „the > right thing“ and to make hard to do „wrong“. We have (and should > keep!) plenty of „shortcuts“ for experienced users who understand what > they do. > > And now let's dive into specifics (in chronological order). > Vero, I meant a first-run wizard, but choose a bad name. Sorry, my > fault. Although I had no fundamental objections against the old > startup screen, there is no need to resurrect it. He's dead, Jim. > > Anna, there were many ideas floating around in Prague caused by the > „location“->„project“ proposal. And you are right, we couldn't agree > > on a single solution (see the first point of this email). At the same > time there were concerns from me and others (IIRC Martin, Luís, > Helmut?) that it is still too easy to continue with a sub-optimal or > outright wrong CRS (location/project structure). Later on (after a few > too many beers) I tried to convince everyone (sorry Linda!) that we > should focus on that “easy to do right“ mantra. At the end we all > agreed (or everyone agreed just to silence me ;-) that we should > continue exploring alternatives and thus was the GSOC proposal. > > Brendan, there's more than one way to skin a cat. > > Anna, the current info bar is just bad for at least two reasons (sorry > Linda, I'm just opinionated). Although you state that most users just > dismiss it, I'll call it a lie – it is not possible to dismiss it at > all! Yeah, I'm just kidding, there is a bug in the code. I rm'ed my > .grass8 to see first start-up experience. See attachment with a cutout > from a full screen window I was presented with – one can not read > whole message or see any buttons as the widget is too small to fit all > of its content. And that's even before the text is translated to > Latvian, German or Finnish that will make the text even longer > (Äteritsiputeritsipuolilautatsijänkä is an actual name of region in > Lapland and makes a good word to test UI). > The info bar has fallen into the old startup window trap – try to > explain GRASS specifics (an important thing!) instead of providing > easy actionable options that all lead to „doing it right“. It is a > TL;DR, and why I should „create new project“ if I already have one > open? Keep in mind attention span of a goldfish (a.k.a. length of a > Tiktok video) we are dealing with. (Has anyone read this far? Let me > know in the comments and don't forget to like and subscribe.) > My idea did not interfere with implementing an offer to create a new > project in import tools if a reprojection from projected to ll project > is detected (I <3 how this sentence rolls-off my tongue) or any other > enhancements that also can (and should) be implemented. > > Vaclav, thanks. I was thinking of something like A1 proposal, but even > simpler (three + 1 buttons) and the same time with a lot of black > magick (e.g. three clicks or less to have everything ready for any of > our
Re: [GRASS-dev] GSoC Ideas
f user cancels the wizard, just fine. Let him enjoy the demo project and display first time screen also on the next startup iff there is no project with data in the GISDBASE. This would not interfere with a big, fat warning if someone tries to import external data into sample projects (NC, Spearfish, ...) or any other enhancements that could be done. Huh, I think I answered most of points from previous emails (except going into details of potential architecture (thus Anna for wxPython expertise) or user friendliness (thus Vero)). Thank you to everyone who read this far and sorry for all unintentional fuss I caused. Probably Linda you are right – it is too ambitious for an experimental project that might get tossed away at the end. I see that Anna has already removed the idea from the wiki, most likely for good. Do not restore it, let it be so. We can return to this idea at any point later if we feel need for it. I have plenty to do to fix pointer juggling bugs in the new module I have almost finished (anisotropic smoothing). Māris. piektd., 2024. g. 16. febr., plkst. 10:41 — lietotājs Linda Kladivová () rakstīja: > > Hello Māris, > > just to add some other info, we did several surveys among GRASS users about > first-time user experience with Anna, Martin and Vashek and we also tested > old and new startup mechanisms in a real environment within the usability > testing - you can have a look at our article: > https://www.mdpi.com/2220-9964/12/9/376. > > As Anna has already written, the results of usability testing were indeed > mixed but I would like to emphasize one thing - most of the usability > participants (first-time users) said to me that they simply expect they will > be directly redirected to the main software window where they can start > working without knowing anything about the software. The current "info bar" > solution goes in that direction and although I have to admit that it has > flaws there are ways how to make it better and Anna has already written some > points. > > I think it would be nice to focus on how to make the current solution better > (it is definitely doable and even desirable) and not go back to some > alternatives to the old solution. > Above that, it would be extremely time-consuming to implement any dialog > wizards and at the same time the impact of that "dialog" solution is very > uncertain - one important thing we also learned from surveys and discussions > inside/outside the community is that the one good generally acceptable > solution simply does not exist here - it will always be a compromise. > > Just my two cents. :-) > Linda > > -- Původní e-mail -- > Od: Maris Nartiss via grass-dev > Komu: Anna Petrášová , Veronica Andreo > > Kopie: GRASS-dev > Datum: 15. 2. 2024 13:04:24 > Předmět: Re: [GRASS-dev] GSoC Ideas > > Hello Anna, Vero. > I added the welcome screen idea we discussed during our Prague > meeting. I think it would be a good GSOC project as it is quite easy > and at the same time will allow to understand if it is the way to go. > Anna, would you be able to be a co-mentor as it is a GUI project? Or > who else could be? > Vero, your user-centric view also would be valuable. > Please edit the wiki accordingly. > > Thanks, > Māris. > > sestd., 2024. g. 3. febr., plkst. 06:34 — lietotājs Anna Petrášová via > grass-dev () rakstīja: > > > > Hi, > > > > I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki, > > which I think we should be moving away from): > > https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 > > > > It's not updated yet, I plan to add more topics. If you want to mentor a > > topic, we can discuss it here. > > > > Anna > > ___ > > grass-dev mailing list > > grass-dev@lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/grass-dev > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
Hello Māris, just to add some other info, we did several surveys among GRASS users about first-time user experience with Anna, Martin and Vashek and we also tested old and new startup mechanisms in a real environment within the usability testing - you can have a look at our article: https://www.mdpi.com/2220- 9964/12/9/376. As Anna has already written, the results of usability testing were indeed mixed but I would like to emphasize one thing - most of the usability participants (first-time users) said to me that they simply expect they will be directly redirected to the main software window where they can start working without knowing anything about the software. The current "info bar" solution goes in that direction and although I have to admit that it has flaws there are ways how to make it better and Anna has already written some points. I think it would be nice to focus on how to make the current solution better (it is definitely doable and even desirable) and not go back to some alternatives to the old solution. Above that, it would be extremely time-consuming to implement any dialog wizards and at the same time the impact of that "dialog" solution is very uncertain - one important thing we also learned from surveys and discussions inside/outside the community is that the one good generally acceptable solution simply does not exist here - it will always be a compromise. Just my two cents. :-) Linda -- Původní e-mail -- Od: Maris Nartiss via grass-dev Komu: Anna Petrášová , Veronica Andreo Kopie: GRASS-dev Datum: 15. 2. 2024 13:04:24 Předmět: Re: [GRASS-dev] GSoC Ideas "Hello Anna, Vero. I added the welcome screen idea we discussed during our Prague meeting. I think it would be a good GSOC project as it is quite easy and at the same time will allow to understand if it is the way to go. Anna, would you be able to be a co-mentor as it is a GUI project? Or who else could be? Vero, your user-centric view also would be valuable. Please edit the wiki accordingly. Thanks, Māris. sestd., 2024. g. 3. febr., plkst. 06:34 — lietotājs Anna Petrášová via grass-dev () rakstīja: > > Hi, > > I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki, which I think we should be moving away from): > https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 > > It's not updated yet, I plan to add more topics. If you want to mentor a topic, we can discuss it here. > > Anna > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev "___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
Seeing the new startup screen idea description, the "Proposals for a new GRASS GIS startup mechanism" wiki page on Trac wiki might be a good read: https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/New_Startup On Thu, 15 Feb 2024 at 14:11, Anna Petrášová via grass-dev < grass-dev@lists.osgeo.org> wrote: > I believe the welcome screen would most likely be dismissed. The other > possible solutions Brendan brings up may be difficult to implement with > wxpython. But we tried to do something similar with Linda using the info > bar, which shows info/buttons for first-time users. She tested that with > mixed results, people often just dismissed it. But I think it could be > further refined. For example, maybe we could move it to map display to make > it more prominent. The other direction is to better detect when users are > doing something likely wrong (import projected data to default project) and > then suggest alternatives. > > On Thu, Feb 15, 2024 at 12:05 PM Brendan wrote: > >> Personally I like the new interface, but Maris' proposal for wizards to >> create new projects sounds helpful. Rather than a startup screen that >> stalls users, there could be temporary icons floating on the map canvas >> that prompt users to create a new project in different ways. Would >> disappear as soon as data is added to the map. A helpful guide/shortcut >> that users could choose to ignore. Still, any startup hints might be >> annoying like Clippy the infamous paperclip. I can find an example from >> other software if the idea is of interest. Or the logo that pops up when >> you start GRASS could have buttons for creating new projects; if a user >> doesn't click on them while GRASS is starting, then it will open in the >> default / previous project. >> Best, Brendan >> >> On Thu, Feb 15, 2024 at 8:35 AM Anna Petrášová via grass-dev < >> grass-dev@lists.osgeo.org> wrote: >> >>> I agree with Vero. I am not sure we had enough time to evaluate the >>> current state yet. I don't remember the details of our discussions, so if >>> you provide a description of what exactly you mean, that would be helpful. >>> In terms of a GSoC project, the main issue I see is that the mentors need >>> to provide clear instructions on what the student should do, especially for >>> this case, and we apparently don't have a consensus here. So I would be >>> willing to mentor it only as long as we develop a plan ahead of time we can >>> all agree on. Given the past experience, I am somewhat skeptical we can all >>> agree on something:) But I'll try to be open to ideas! >>> >>> On Thu, Feb 15, 2024 at 8:12 AM Veronica Andreo >>> wrote: >>> Hi Maris, Would you mind sharing more details on this idea? I'm afraid I was not able to attend/hear the discussion about this welcome screen in Prague. I hope though we do not end up with a new startup screen. It took so much time to reach an agreement and finally remove it. Vero El jue, 15 feb 2024 a las 9:00, Maris Nartiss () escribió: > Hello Anna, Vero. > I added the welcome screen idea we discussed during our Prague > meeting. I think it would be a good GSOC project as it is quite easy > and at the same time will allow to understand if it is the way to go. > Anna, would you be able to be a co-mentor as it is a GUI project? Or > who else could be? > Vero, your user-centric view also would be valuable. > Please edit the wiki accordingly. > > Thanks, > Māris. > > sestd., 2024. g. 3. febr., plkst. 06:34 — lietotājs Anna Petrášová via > grass-dev () rakstīja: > > > > Hi, > > > > I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac > wiki, which I think we should be moving away from): > > https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 > > > > It's not updated yet, I plan to add more topics. If you want to > mentor a topic, we can discuss it here. > > > > Anna > > ___ > > grass-dev mailing list > > grass-dev@lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/grass-dev > -- Dra. Verónica Andreo Investigadora Adjunta de CONICET Instituto Gulich (CONAE - UNC) Centro Espacial Teófilo Tabanera (CETT) Falda del Cañete - Córdoba, Argentina +54 3547 40 int. 1153 https://veroandreo.gitlab.io/ >>> ___ >>> grass-dev mailing list >>> grass-dev@lists.osgeo.org >>> https://lists.osgeo.org/mailman/listinfo/grass-dev >>> >> ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
I believe the welcome screen would most likely be dismissed. The other possible solutions Brendan brings up may be difficult to implement with wxpython. But we tried to do something similar with Linda using the info bar, which shows info/buttons for first-time users. She tested that with mixed results, people often just dismissed it. But I think it could be further refined. For example, maybe we could move it to map display to make it more prominent. The other direction is to better detect when users are doing something likely wrong (import projected data to default project) and then suggest alternatives. On Thu, Feb 15, 2024 at 12:05 PM Brendan wrote: > Personally I like the new interface, but Maris' proposal for wizards to > create new projects sounds helpful. Rather than a startup screen that > stalls users, there could be temporary icons floating on the map canvas > that prompt users to create a new project in different ways. Would > disappear as soon as data is added to the map. A helpful guide/shortcut > that users could choose to ignore. Still, any startup hints might be > annoying like Clippy the infamous paperclip. I can find an example from > other software if the idea is of interest. Or the logo that pops up when > you start GRASS could have buttons for creating new projects; if a user > doesn't click on them while GRASS is starting, then it will open in the > default / previous project. > Best, Brendan > > On Thu, Feb 15, 2024 at 8:35 AM Anna Petrášová via grass-dev < > grass-dev@lists.osgeo.org> wrote: > >> I agree with Vero. I am not sure we had enough time to evaluate the >> current state yet. I don't remember the details of our discussions, so if >> you provide a description of what exactly you mean, that would be helpful. >> In terms of a GSoC project, the main issue I see is that the mentors need >> to provide clear instructions on what the student should do, especially for >> this case, and we apparently don't have a consensus here. So I would be >> willing to mentor it only as long as we develop a plan ahead of time we can >> all agree on. Given the past experience, I am somewhat skeptical we can all >> agree on something:) But I'll try to be open to ideas! >> >> On Thu, Feb 15, 2024 at 8:12 AM Veronica Andreo >> wrote: >> >>> Hi Maris, >>> >>> Would you mind sharing more details on this idea? I'm afraid I was not >>> able to attend/hear the discussion about this welcome screen in Prague. I >>> hope though we do not end up with a new startup screen. It took so much >>> time to reach an agreement and finally remove it. >>> >>> Vero >>> >>> El jue, 15 feb 2024 a las 9:00, Maris Nartiss () >>> escribió: >>> Hello Anna, Vero. I added the welcome screen idea we discussed during our Prague meeting. I think it would be a good GSOC project as it is quite easy and at the same time will allow to understand if it is the way to go. Anna, would you be able to be a co-mentor as it is a GUI project? Or who else could be? Vero, your user-centric view also would be valuable. Please edit the wiki accordingly. Thanks, Māris. sestd., 2024. g. 3. febr., plkst. 06:34 — lietotājs Anna Petrášová via grass-dev () rakstīja: > > Hi, > > I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki, which I think we should be moving away from): > https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 > > It's not updated yet, I plan to add more topics. If you want to mentor a topic, we can discuss it here. > > Anna > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev >>> >>> >>> -- >>> Dra. Verónica Andreo >>> Investigadora Adjunta de CONICET >>> Instituto Gulich (CONAE - UNC) >>> Centro Espacial Teófilo Tabanera (CETT) >>> Falda del Cañete - Córdoba, Argentina >>> +54 3547 40 int. 1153 >>> https://veroandreo.gitlab.io/ >>> >> ___ >> grass-dev mailing list >> grass-dev@lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/grass-dev >> > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
Personally I like the new interface, but Maris' proposal for wizards to create new projects sounds helpful. Rather than a startup screen that stalls users, there could be temporary icons floating on the map canvas that prompt users to create a new project in different ways. Would disappear as soon as data is added to the map. A helpful guide/shortcut that users could choose to ignore. Still, any startup hints might be annoying like Clippy the infamous paperclip. I can find an example from other software if the idea is of interest. Or the logo that pops up when you start GRASS could have buttons for creating new projects; if a user doesn't click on them while GRASS is starting, then it will open in the default / previous project. Best, Brendan On Thu, Feb 15, 2024 at 8:35 AM Anna Petrášová via grass-dev < grass-dev@lists.osgeo.org> wrote: > I agree with Vero. I am not sure we had enough time to evaluate the > current state yet. I don't remember the details of our discussions, so if > you provide a description of what exactly you mean, that would be helpful. > In terms of a GSoC project, the main issue I see is that the mentors need > to provide clear instructions on what the student should do, especially for > this case, and we apparently don't have a consensus here. So I would be > willing to mentor it only as long as we develop a plan ahead of time we can > all agree on. Given the past experience, I am somewhat skeptical we can all > agree on something:) But I'll try to be open to ideas! > > On Thu, Feb 15, 2024 at 8:12 AM Veronica Andreo > wrote: > >> Hi Maris, >> >> Would you mind sharing more details on this idea? I'm afraid I was not >> able to attend/hear the discussion about this welcome screen in Prague. I >> hope though we do not end up with a new startup screen. It took so much >> time to reach an agreement and finally remove it. >> >> Vero >> >> El jue, 15 feb 2024 a las 9:00, Maris Nartiss () >> escribió: >> >>> Hello Anna, Vero. >>> I added the welcome screen idea we discussed during our Prague >>> meeting. I think it would be a good GSOC project as it is quite easy >>> and at the same time will allow to understand if it is the way to go. >>> Anna, would you be able to be a co-mentor as it is a GUI project? Or >>> who else could be? >>> Vero, your user-centric view also would be valuable. >>> Please edit the wiki accordingly. >>> >>> Thanks, >>> Māris. >>> >>> sestd., 2024. g. 3. febr., plkst. 06:34 — lietotājs Anna Petrášová via >>> grass-dev () rakstīja: >>> > >>> > Hi, >>> > >>> > I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac >>> wiki, which I think we should be moving away from): >>> > https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 >>> > >>> > It's not updated yet, I plan to add more topics. If you want to mentor >>> a topic, we can discuss it here. >>> > >>> > Anna >>> > ___ >>> > grass-dev mailing list >>> > grass-dev@lists.osgeo.org >>> > https://lists.osgeo.org/mailman/listinfo/grass-dev >>> >> >> >> -- >> Dra. Verónica Andreo >> Investigadora Adjunta de CONICET >> Instituto Gulich (CONAE - UNC) >> Centro Espacial Teófilo Tabanera (CETT) >> Falda del Cañete - Córdoba, Argentina >> +54 3547 40 int. 1153 >> https://veroandreo.gitlab.io/ >> > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
I agree with Vero. I am not sure we had enough time to evaluate the current state yet. I don't remember the details of our discussions, so if you provide a description of what exactly you mean, that would be helpful. In terms of a GSoC project, the main issue I see is that the mentors need to provide clear instructions on what the student should do, especially for this case, and we apparently don't have a consensus here. So I would be willing to mentor it only as long as we develop a plan ahead of time we can all agree on. Given the past experience, I am somewhat skeptical we can all agree on something:) But I'll try to be open to ideas! On Thu, Feb 15, 2024 at 8:12 AM Veronica Andreo wrote: > Hi Maris, > > Would you mind sharing more details on this idea? I'm afraid I was not > able to attend/hear the discussion about this welcome screen in Prague. I > hope though we do not end up with a new startup screen. It took so much > time to reach an agreement and finally remove it. > > Vero > > El jue, 15 feb 2024 a las 9:00, Maris Nartiss () > escribió: > >> Hello Anna, Vero. >> I added the welcome screen idea we discussed during our Prague >> meeting. I think it would be a good GSOC project as it is quite easy >> and at the same time will allow to understand if it is the way to go. >> Anna, would you be able to be a co-mentor as it is a GUI project? Or >> who else could be? >> Vero, your user-centric view also would be valuable. >> Please edit the wiki accordingly. >> >> Thanks, >> Māris. >> >> sestd., 2024. g. 3. febr., plkst. 06:34 — lietotājs Anna Petrášová via >> grass-dev () rakstīja: >> > >> > Hi, >> > >> > I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki, >> which I think we should be moving away from): >> > https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 >> > >> > It's not updated yet, I plan to add more topics. If you want to mentor >> a topic, we can discuss it here. >> > >> > Anna >> > ___ >> > grass-dev mailing list >> > grass-dev@lists.osgeo.org >> > https://lists.osgeo.org/mailman/listinfo/grass-dev >> > > > -- > Dra. Verónica Andreo > Investigadora Adjunta de CONICET > Instituto Gulich (CONAE - UNC) > Centro Espacial Teófilo Tabanera (CETT) > Falda del Cañete - Córdoba, Argentina > +54 3547 40 int. 1153 > https://veroandreo.gitlab.io/ > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
Hi Maris, Would you mind sharing more details on this idea? I'm afraid I was not able to attend/hear the discussion about this welcome screen in Prague. I hope though we do not end up with a new startup screen. It took so much time to reach an agreement and finally remove it. Vero El jue, 15 feb 2024 a las 9:00, Maris Nartiss () escribió: > Hello Anna, Vero. > I added the welcome screen idea we discussed during our Prague > meeting. I think it would be a good GSOC project as it is quite easy > and at the same time will allow to understand if it is the way to go. > Anna, would you be able to be a co-mentor as it is a GUI project? Or > who else could be? > Vero, your user-centric view also would be valuable. > Please edit the wiki accordingly. > > Thanks, > Māris. > > sestd., 2024. g. 3. febr., plkst. 06:34 — lietotājs Anna Petrášová via > grass-dev () rakstīja: > > > > Hi, > > > > I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki, > which I think we should be moving away from): > > https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 > > > > It's not updated yet, I plan to add more topics. If you want to mentor a > topic, we can discuss it here. > > > > Anna > > ___ > > grass-dev mailing list > > grass-dev@lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/grass-dev > -- Dra. Verónica Andreo Investigadora Adjunta de CONICET Instituto Gulich (CONAE - UNC) Centro Espacial Teófilo Tabanera (CETT) Falda del Cañete - Córdoba, Argentina +54 3547 40 int. 1153 https://veroandreo.gitlab.io/ ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
Hello Anna, Vero. I added the welcome screen idea we discussed during our Prague meeting. I think it would be a good GSOC project as it is quite easy and at the same time will allow to understand if it is the way to go. Anna, would you be able to be a co-mentor as it is a GUI project? Or who else could be? Vero, your user-centric view also would be valuable. Please edit the wiki accordingly. Thanks, Māris. sestd., 2024. g. 3. febr., plkst. 06:34 — lietotājs Anna Petrášová via grass-dev () rakstīja: > > Hi, > > I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki, which > I think we should be moving away from): > https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 > > It's not updated yet, I plan to add more topics. If you want to mentor a > topic, we can discuss it here. > > Anna > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
On Mon, 12 Feb 2024 at 18:08, Markus Neteler wrote: > > On Tue, Feb 6, 2024 at 12:11 AM Luca Delucchi via grass-dev > wrote: > > On Mon, 5 Feb 2024 at 13:33, Veronica Andreo wrote: > > > That would be cool Luca! eodag allows you to download different EO > > > datasets. > > > > > > Do you think of a GSoC project idea to include eodag support for > > > i.sentinel.download, i.landsat.download and i.modis.download or as a new > > > module to download EO data in general? If you are willing to mentor, I > > > can be your second... mainly to test and make annoying questions :) > > > > > > > Yes, the idea could be to add it to i.*.download, I was also thinking > > of having a common library in grass python library as an interface to > > eodag, but I'm not sure if it makes sense... > > > > However I tried to log to the wiki and I'm not able, and password > > recover also didn't work > > Regina has updated the GRASS Wiki again and we have done a series of > tests, fixing plugins and such. > > Please try again, now with your OSGeo-LDAP account. > > A "user merge" may come up. Let me know if it gets blocked so that I can > assist. > It worked properly now, I added the EODAG proposal, I didn't add any test yet but I'll hope to do it ASAP > Markus > ciao Luca www.lucadelu.org ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
On Tue, Feb 6, 2024 at 12:11 AM Luca Delucchi via grass-dev wrote: > On Mon, 5 Feb 2024 at 13:33, Veronica Andreo wrote: > > That would be cool Luca! eodag allows you to download different EO datasets. > > > > Do you think of a GSoC project idea to include eodag support for > > i.sentinel.download, i.landsat.download and i.modis.download or as a new > > module to download EO data in general? If you are willing to mentor, I can > > be your second... mainly to test and make annoying questions :) > > > > Yes, the idea could be to add it to i.*.download, I was also thinking > of having a common library in grass python library as an interface to > eodag, but I'm not sure if it makes sense... > > However I tried to log to the wiki and I'm not able, and password > recover also didn't work Regina has updated the GRASS Wiki again and we have done a series of tests, fixing plugins and such. Please try again, now with your OSGeo-LDAP account. A "user merge" may come up. Let me know if it gets blocked so that I can assist. Markus -- Markus Neteler, PhD https://www.mundialis.de - company https://grass.osgeo.org - FOSS https://neteler.org - freelancing & blog ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
On Mon, 5 Feb 2024 at 13:33, Veronica Andreo wrote: > > That would be cool Luca! eodag allows you to download different EO datasets. > > Do you think of a GSoC project idea to include eodag support for > i.sentinel.download, i.landsat.download and i.modis.download or as a new > module to download EO data in general? If you are willing to mentor, I can be > your second... mainly to test and make annoying questions :) > Yes, the idea could be to add it to i.*.download, I was also thinking of having a common library in grass python library as an interface to eodag, but I'm not sure if it makes sense... However I tried to log to the wiki and I'm not able, and password recover also didn't work > Vero -- ciao Luca www.lucadelu.org ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
I sent the ideas page to OSGeo admins (the deadline is today), although I think we can keep adding topics. Please also fill out this form https://forms.gle/dZDYovvmhrQRah73A if you plan to mentor. Thanks, Anna On Mon, Feb 5, 2024 at 7:33 AM Veronica Andreo wrote: > That would be cool Luca! eodag allows you to download different EO > datasets. > > Do you think of a GSoC project idea to include eodag support for > i.sentinel.download, i.landsat.download and i.modis.download or as a new > module to download EO data in general? If you are willing to mentor, I can > be your second... mainly to test and make annoying questions :) > > Vero > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
That would be cool Luca! eodag allows you to download different EO datasets. Do you think of a GSoC project idea to include eodag support for i.sentinel.download, i.landsat.download and i.modis.download or as a new module to download EO data in general? If you are willing to mentor, I can be your second... mainly to test and make annoying questions :) Vero ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
On Sat, Feb 3, 2024 at 4:39 AM Luca Delucchi wrote: > > > Il sab 3 feb 2024, 05:34 Anna Petrášová via grass-dev < > grass-dev@lists.osgeo.org> ha scritto: > >> Hi, >> >> I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki, >> which I think we should be moving away from): >> https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 >> >> It's not updated yet, I plan to add more topics. If you want to mentor a >> topic, we can discuss it here. >> > > Do you think an interface to eodag library, to download sentinel and > Landsat images for example, could be a topic for gsoc? > I suppose so. As long as somebody (you?) would mentor it, we can add it (including test of skills etc). >> Anna >> > > Best > Luca > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
Il sab 3 feb 2024, 05:34 Anna Petrášová via grass-dev < grass-dev@lists.osgeo.org> ha scritto: > Hi, > > I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki, > which I think we should be moving away from): > https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 > > It's not updated yet, I plan to add more topics. If you want to mentor a > topic, we can discuss it here. > Do you think an interface to eodag library, to download sentinel and Landsat images for example, could be a topic for gsoc? > > Anna > Best Luca ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] GSoC Ideas
Hi, I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki, which I think we should be moving away from): https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 It's not updated yet, I plan to add more topics. If you want to mentor a topic, we can discuss it here. Anna ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC ideas - vector legend, medial axis
Another QGIS plugin effort. http://gis-lab.info/qa/metatools-eng.html#Working_with_FGDC Doug On Thu, Feb 27, 2014 at 12:56 PM, Newcomb, Doug doug_newc...@fws.govwrote: Metadata code reference: https://geo-ide.noaa.gov/wiki/index.php?title=ISO_19115_and_19115-2_CodeList_Dictionaries Doug On Tue, Feb 25, 2014 at 3:36 PM, Antony Scott antony.sc...@gmail.comwrote: Doug/all, First, my apologies for not responding to your earlier nudge. However there's not a great deal to report on the plugin - MapAction remains keen to take it forward, but doesn't have the development resources at the moment to be able to do much about it. We'd be happy to expand on the documentation though, and the osgeo gsoc could be an opportunity to get things moving if people were interested. Certainly our experiences in the Philippines last year underlined our need for better metadata creation and management tools, so it's high on our list of action points for follow up. Look forward to seeing how things develop, and we'll see if there's anything we can contribute. regards Ant Scott On 25 February 2014 12:54, Newcomb, Doug doug_newc...@fws.gov wrote: I had a chat with Antony Scott a while back about a metadata component to this plugin: https://github.com/mapaction/RAMP-QGIS I have not kept up with the progress of the plugin. Doug On Mon, Feb 24, 2014 at 5:53 PM, Hamish hamis...@yahoo.com wrote: Hi, (thanks for the great ideas pages everyone: osgeo gsoc 2014 is accepted and happening!) integrating an existing open source metadata library instead of starting from scratch would be faster and easier to maintain in the long run. :) e.g. try to cooperate with the GeoNetwork and pycsw teams. is qgis doing anything wrt metadata that we could share development with? Hamish -- Doug Newcomb USFWS Raleigh, NC 919-856-4520 ext. 14 doug_newc...@fws.gov - The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats. -- Doug Newcomb USFWS Raleigh, NC 919-856-4520 ext. 14 doug_newc...@fws.gov - The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats. -- Doug Newcomb USFWS Raleigh, NC 919-856-4520 ext. 14 doug_newc...@fws.gov - The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC ideas - vector legend, medial axis
Metadata code reference: https://geo-ide.noaa.gov/wiki/index.php?title=ISO_19115_and_19115-2_CodeList_Dictionaries Doug On Tue, Feb 25, 2014 at 3:36 PM, Antony Scott antony.sc...@gmail.comwrote: Doug/all, First, my apologies for not responding to your earlier nudge. However there's not a great deal to report on the plugin - MapAction remains keen to take it forward, but doesn't have the development resources at the moment to be able to do much about it. We'd be happy to expand on the documentation though, and the osgeo gsoc could be an opportunity to get things moving if people were interested. Certainly our experiences in the Philippines last year underlined our need for better metadata creation and management tools, so it's high on our list of action points for follow up. Look forward to seeing how things develop, and we'll see if there's anything we can contribute. regards Ant Scott On 25 February 2014 12:54, Newcomb, Doug doug_newc...@fws.gov wrote: I had a chat with Antony Scott a while back about a metadata component to this plugin: https://github.com/mapaction/RAMP-QGIS I have not kept up with the progress of the plugin. Doug On Mon, Feb 24, 2014 at 5:53 PM, Hamish hamis...@yahoo.com wrote: Hi, (thanks for the great ideas pages everyone: osgeo gsoc 2014 is accepted and happening!) integrating an existing open source metadata library instead of starting from scratch would be faster and easier to maintain in the long run. :) e.g. try to cooperate with the GeoNetwork and pycsw teams. is qgis doing anything wrt metadata that we could share development with? Hamish -- Doug Newcomb USFWS Raleigh, NC 919-856-4520 ext. 14 doug_newc...@fws.gov - The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats. -- Doug Newcomb USFWS Raleigh, NC 919-856-4520 ext. 14 doug_newc...@fws.gov - The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC ideas - vector legend, medial axis
Hi All, On Mon, Feb 24, 2014 at 8:22 PM, Martin Landa landa.mar...@gmail.comwrote: Hi, 2014-02-24 20:18 GMT+01:00 Tereza Fiedlerová tfiedler...@gmail.com: finally I considered the metadata topic is probably the most appropriate for me. My aim now is to find out as much as I can about it to have better idea what is going on. If you have any additional information or resources I could study, please let me know. Thanks Tereza, I'm glad to hear that. As several hints have already come, I'd suggest to set a page in the trac where we can store all these inputs that otherwise would be difficult to find again. perfect, in this regard I would like to open discussion whether to speak just about metadata (ISO, Inspire) or also about supporting Inspire services (view and download)... Martin, this makes sense, but I'd stick with a target that is reachable within the GSoC. Of course the occasion is suitable to gather all the ideas which can be developed in the future. Thanks, MaDi -- Best regards, Dr. Margherita DI LEO Scientific / technical project officer European Commission - DG JRC Institute for Environment and Sustainability (IES) Via Fermi, 2749 I-21027 Ispra (VA) - Italy - TP 261 Tel. +39 0332 78 3600 margherita.di-...@jrc.ec.europa.eu Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC ideas - vector legend, medial axis
From what I understand, the ISO 19115-1 metadata standard should be finalized shortly. Getting an official copy of the standard for this work ( if they finalize in time) would be useful. Doug On Tue, Feb 25, 2014 at 4:36 AM, Margherita Di Leo dileomargher...@gmail.com wrote: Hi All, On Mon, Feb 24, 2014 at 8:22 PM, Martin Landa landa.mar...@gmail.comwrote: Hi, 2014-02-24 20:18 GMT+01:00 Tereza Fiedlerová tfiedler...@gmail.com: finally I considered the metadata topic is probably the most appropriate for me. My aim now is to find out as much as I can about it to have better idea what is going on. If you have any additional information or resources I could study, please let me know. Thanks Tereza, I'm glad to hear that. As several hints have already come, I'd suggest to set a page in the trac where we can store all these inputs that otherwise would be difficult to find again. perfect, in this regard I would like to open discussion whether to speak just about metadata (ISO, Inspire) or also about supporting Inspire services (view and download)... Martin, this makes sense, but I'd stick with a target that is reachable within the GSoC. Of course the occasion is suitable to gather all the ideas which can be developed in the future. Thanks, MaDi -- Best regards, Dr. Margherita DI LEO Scientific / technical project officer European Commission - DG JRC Institute for Environment and Sustainability (IES) Via Fermi, 2749 I-21027 Ispra (VA) - Italy - TP 261 Tel. +39 0332 78 3600 margherita.di-...@jrc.ec.europa.eu Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev -- Doug Newcomb USFWS Raleigh, NC 919-856-4520 ext. 14 doug_newc...@fws.gov - The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC ideas - vector legend, medial axis
I had a chat with Antony Scott a while back about a metadata component to this plugin: https://github.com/mapaction/RAMP-QGIS I have not kept up with the progress of the plugin. Doug On Mon, Feb 24, 2014 at 5:53 PM, Hamish hamis...@yahoo.com wrote: Hi, (thanks for the great ideas pages everyone: osgeo gsoc 2014 is accepted and happening!) integrating an existing open source metadata library instead of starting from scratch would be faster and easier to maintain in the long run. :) e.g. try to cooperate with the GeoNetwork and pycsw teams. is qgis doing anything wrt metadata that we could share development with? Hamish -- Doug Newcomb USFWS Raleigh, NC 919-856-4520 ext. 14 doug_newc...@fws.gov - The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC ideas - vector legend, medial axis
Hi, finally I considered the metadata topic is probably the most appropriate for me. My aim now is to find out as much as I can about it to have better idea what is going on. If you have any additional information or resources I could study, please let me know. Thanks Tereza On 20 February 2014 09:33, Margherita Di Leo dileomargher...@gmail.comwrote: Hi Tereza! On Thu, Feb 20, 2014 at 9:08 AM, Tereza Fiedlerová tfiedler...@gmail.comwrote: And one more question. Is any of these topics suitable for me if I am not experienced in GRASS at all? Please consider the idea on metadata, that requires a limited knowledge of GRASS I would say -- Best regards, Dr. Margherita DI LEO Scientific / technical project officer European Commission - DG JRC Institute for Environment and Sustainability (IES) Via Fermi, 2749 I-21027 Ispra (VA) - Italy - TP 261 Tel. +39 0332 78 3600 margherita.di-...@jrc.ec.europa.eu Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC ideas - vector legend, medial axis
Hi, 2014-02-24 20:18 GMT+01:00 Tereza Fiedlerová tfiedler...@gmail.com: finally I considered the metadata topic is probably the most appropriate for me. My aim now is to find out as much as I can about it to have better idea what is going on. If you have any additional information or resources I could study, please let me know. Thanks perfect, in this regard I would like to open discussion whether to speak just about metadata (ISO, Inspire) or also about supporting Inspire services (view and download)... Martin ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC ideas - vector legend, medial axis
A good metadata tool that generates ISO compliant xml would be very useful and a substantial accomplishment by itself. Doug On Mon, Feb 24, 2014 at 2:22 PM, Martin Landa landa.mar...@gmail.comwrote: Hi, 2014-02-24 20:18 GMT+01:00 Tereza Fiedlerová tfiedler...@gmail.com: finally I considered the metadata topic is probably the most appropriate for me. My aim now is to find out as much as I can about it to have better idea what is going on. If you have any additional information or resources I could study, please let me know. Thanks perfect, in this regard I would like to open discussion whether to speak just about metadata (ISO, Inspire) or also about supporting Inspire services (view and download)... Martin ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev -- Doug Newcomb USFWS Raleigh, NC 919-856-4520 ext. 14 doug_newc...@fws.gov - The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC ideas - vector legend, medial axis
Hi, (thanks for the great ideas pages everyone: osgeo gsoc 2014 is accepted and happening!) integrating an existing open source metadata library instead of starting from scratch would be faster and easier to maintain in the long run. :) e.g. try to cooperate with the GeoNetwork and pycsw teams. is qgis doing anything wrt metadata that we could share development with? Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC ideas - vector legend, medial axis
Hamish wrote: e.g. try to cooperate with the GeoNetwork and pycsw teams. is qgis doing anything wrt metadata that we could share development with? see also deegree, qgis MetaSearch plugin, and the OSWLib library. Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] GSoC ideas - vector legend, medial axis
Hello, I'm thinking about participating in GSoC this year, if I find some interesting topic. I went through GRASS GSoC ideas. The two most interesting for me are Vector legend and Extracting the medial axis of polygon. I would appreciate if anyone can give me more information to these topics. The first one is maybe described enough and I just need to study that more to understand it better, but still anything more regarding that would be appreciated. The medial axis is not really clear to me. I know what is medial axis, but I would like to know more about desired results. How it should be integrated to GRASS (some new module?). Is it necessary to write it in C (why not python)? Should the result algorithm extract the exact medial axis or the approximation? ... And one more question. Is any of these topics suitable for me if I am not experienced in GRASS at all? Thank you Tereza Fiedlerová ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC ideas - vector legend, medial axis
Hi Tereza! On Thu, Feb 20, 2014 at 9:08 AM, Tereza Fiedlerová tfiedler...@gmail.comwrote: And one more question. Is any of these topics suitable for me if I am not experienced in GRASS at all? Please consider the idea on metadata, that requires a limited knowledge of GRASS I would say -- Best regards, Dr. Margherita DI LEO Scientific / technical project officer European Commission - DG JRC Institute for Environment and Sustainability (IES) Via Fermi, 2749 I-21027 Ispra (VA) - Italy - TP 261 Tel. +39 0332 78 3600 margherita.di-...@jrc.ec.europa.eu Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC ideas - vector legend, medial axis
On Thu, Feb 20, 2014 at 9:08 AM, Tereza Fiedlerová tfiedler...@gmail.com wrote: Hello, I'm thinking about participating in GSoC this year, if I find some interesting topic. I went through GRASS GSoC ideas. The two most interesting for me are Vector legend and Extracting the medial axis of polygon. I would appreciate if anyone can give me more information to these topics. The first one is maybe described enough and I just need to study that more to understand it better, but still anything more regarding that would be appreciated. The medial axis is not really clear to me. I know what is medial axis, but I would like to know more about desired results. How it should be integrated to GRASS (some new module?). Is it necessary to write it in C (why not python)? Should the result algorithm extract the exact medial axis or the approximation? ... A good approximation would be fine. It would be necessary to write in C for efficiency reasons and because C library functions need to be heavily used. Additionally, search structures like balanced binary search trees and min heaps are needed which are already implemented in GRASS as C code. I have already written 2 different C modules trying to extract the medial axis, both are incredibly complex and none of them works properly. I am familiar with GRASS, C, and Python and like to use the easiest approach. In this case I am pretty sure that the easiest and most appropriate approach is using C, not Python. Therefore I would recommend a good knowledge of C and some knowledge of the GRASS C API for this project. Markus M And one more question. Is any of these topics suitable for me if I am not experienced in GRASS at all? Thank you Tereza Fiedlerová ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC ideas - vector legend, medial axis
On Thu, Feb 20, 2014 at 4:06 PM, Markus Metz markus.metz.gisw...@gmail.comwrote: On Thu, Feb 20, 2014 at 9:08 AM, Tereza Fiedlerová tfiedler...@gmail.com wrote: Hello, I'm thinking about participating in GSoC this year, if I find some interesting topic. I went through GRASS GSoC ideas. The two most interesting for me are Vector legend and Extracting the medial axis of polygon. I would appreciate if anyone can give me more information to these topics. The first one is maybe described enough and I just need to study that more to understand it better, but still anything more regarding that would be appreciated. The medial axis is not really clear to me. I know what is medial axis, but I would like to know more about desired results. How it should be integrated to GRASS (some new module?). Is it necessary to write it in C (why not python)? Should the result algorithm extract the exact medial axis or the approximation? ... A good approximation would be fine. It would be necessary to write in C for efficiency reasons and because C library functions need to be heavily used. Additionally, search structures like balanced binary search trees and min heaps are needed which are already implemented in GRASS as C code. I have already written 2 different C modules trying to extract the medial axis, both are incredibly complex and none of them works properly. I am familiar with GRASS, C, and Python and like to use the easiest approach. In this case I am pretty sure that the easiest and most appropriate approach is using C, not Python. Therefore I would recommend a good knowledge of C and some knowledge of the GRASS C API for this project. Markus M Just in case it would be useful (at least for Tereza, it's mostly in Czech): http://web.natur.cuni.cz/~bayertom/Adk/adk7.pdf this is a presentation on straight skeleton algorithm (if medial axis is the same or at least related?). Anna And one more question. Is any of these topics suitable for me if I am not experienced in GRASS at all? Thank you Tereza Fiedlerová ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC ideas - vector legend, medial axis
On Thu, Feb 20, 2014 at 10:47 PM, Anna Petrášová kratocha...@gmail.com wrote: On Thu, Feb 20, 2014 at 4:06 PM, Markus Metz markus.metz.gisw...@gmail.com wrote: On Thu, Feb 20, 2014 at 9:08 AM, Tereza Fiedlerová tfiedler...@gmail.com wrote: Hello, I'm thinking about participating in GSoC this year, if I find some interesting topic. I went through GRASS GSoC ideas. The two most interesting for me are Vector legend and Extracting the medial axis of polygon. I would appreciate if anyone can give me more information to these topics. The first one is maybe described enough and I just need to study that more to understand it better, but still anything more regarding that would be appreciated. The medial axis is not really clear to me. I know what is medial axis, but I would like to know more about desired results. How it should be integrated to GRASS (some new module?). Is it necessary to write it in C (why not python)? Should the result algorithm extract the exact medial axis or the approximation? ... A good approximation would be fine. It would be necessary to write in C for efficiency reasons and because C library functions need to be heavily used. Additionally, search structures like balanced binary search trees and min heaps are needed which are already implemented in GRASS as C code. I have already written 2 different C modules trying to extract the medial axis, both are incredibly complex and none of them works properly. I am familiar with GRASS, C, and Python and like to use the easiest approach. In this case I am pretty sure that the easiest and most appropriate approach is using C, not Python. Therefore I would recommend a good knowledge of C and some knowledge of the GRASS C API for this project. Markus M Just in case it would be useful (at least for Tereza, it's mostly in Czech): http://web.natur.cuni.cz/~bayertom/Adk/adk7.pdf this is a presentation on straight skeleton algorithm (if medial axis is the same or at least related?). A straight skeleton is not the same like a medial axis: only the medial axis is equidistant to the polygon boundaries. Markus M Anna And one more question. Is any of these topics suitable for me if I am not experienced in GRASS at all? Thank you Tereza Fiedlerová ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSOC: ideas
Hi, 2011/3/31 Wolf Bergenheim wolf+gr...@bergenheim.net: On Wed, Mar 30, 2011 at 13:23, Luca Delucchi lucadel...@gmail.com wrote: 2) from the GRASS GSOC ideas WMS and/or TiledMapService and/or WMS-T layer support, is there someone interested to do the mentor? I like this idea, and would be interested in metoring, but I might be a bit busy during the summer, so I'd like to have a co-mentor, if possible. Especially the WMS / WMS-T parts. if needed I would be also co-mentor for this project. Martin -- Martin Landa landa.martin gmail.com * http://geo.fsv.cvut.cz/~landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSOC: ideas
On 31/03/11 00:44, Wolf Bergenheim wrote: Hi Luca, Glad to hear you are thinking of applying :). On Wed, Mar 30, 2011 at 13:23, Luca Delucchi lucadel...@gmail.com mailto:lucadel...@gmail.com wrote: 2) from the GRASS GSOC ideas WMS and/or TiledMapService and/or WMS-T layer support, is there someone interested to do the mentor? I like this idea, and would be interested in metoring, but I might be a bit busy during the summer, so I'd like to have a co-mentor, if possible. Especially the WMS / WMS-T parts. what do you think is more useful / interesting for GRASS project? Isn't MODIS already supported via GDAL? In general I at least feel that it would be interesting to have support for the OGC standards (WMS, WFS and possibly others) in GRASS, But aren't these also already supported via GDAL. If they are, I don't think that much effort should be spent on that in GRASS. See also this thread: http://osgeo-org.1803224.n2.nabble.com/raster-provider-WCS-td5991911.html Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSOC: ideas
Hello Moritz. As I'm the author of this WMS idea I would like to comment on it. It's not about rewrite of r.in.wms but about providing background images in GUI for visual analysis and digitizing. Such implementation should be as user-friendly as possible and thus it's a good question if it should use GDAL or be homebrew. Also wasn't a WMS/WMS-T and tiled source support in GDAL depending on compiled-in Xerces-C? Being able to import data for analysis would be a nice bonus, still WMS was designed for visual use and not for analysis data transfer like WCS does. Maris. 2011/3/31, Moritz Lennert mlenn...@club.worldonline.be: On 31/03/11 00:44, Wolf Bergenheim wrote: Hi Luca, Glad to hear you are thinking of applying :). On Wed, Mar 30, 2011 at 13:23, Luca Delucchi lucadel...@gmail.com mailto:lucadel...@gmail.com wrote: 2) from the GRASS GSOC ideas WMS and/or TiledMapService and/or WMS-T layer support, is there someone interested to do the mentor? I like this idea, and would be interested in metoring, but I might be a bit busy during the summer, so I'd like to have a co-mentor, if possible. Especially the WMS / WMS-T parts. what do you think is more useful / interesting for GRASS project? Isn't MODIS already supported via GDAL? In general I at least feel that it would be interesting to have support for the OGC standards (WMS, WFS and possibly others) in GRASS, But aren't these also already supported via GDAL. If they are, I don't think that much effort should be spent on that in GRASS. See also this thread: http://osgeo-org.1803224.n2.nabble.com/raster-provider-WCS-td5991911.html Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSOC: ideas
On 31/03/11 11:34, Maris Nartiss wrote: Hello Moritz. As I'm the author of this WMS idea I would like to comment on it. It's not about rewrite of r.in.wms but about providing background images in GUI for visual analysis and digitizing. Such implementation should be as user-friendly as possible and thus it's a good question if it should use GDAL or be homebrew. Also wasn't a WMS/WMS-T and tiled source support in GDAL depending on compiled-in Xerces-C? Being able to import data for analysis would be a nice bonus, still WMS was designed for visual use and not for analysis data transfer like WCS does. Isn't that covered by r.external via gdal ? Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSOC: ideas
On Thu, Mar 31, 2011 at 3:18 AM, Hamish hamis...@yahoo.com wrote: Wolf: Isn't MODIS already supported via GDAL? The processed level 3stuff comes in HDF(4) format, which GDAL knows, see http://grass.osgeo.org/wiki/MODIS as for the raw level 1B and level 2 stuff which may come by scan line(?) I seem to recall that was a motivation for adding/ extending the thin plate spine functionality in gdalwarp? but nicer ways of dealing + processing that could be the intention of the module..? anyone using that low level data? Markus? Years ago, we (former CEA, now FEM) sponsored the implementation of thin plate spine functionality in gdalwarp to georectify AVHRR data. The last years, I used moreover higher level MODIS data. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] GSOC: ideas
Hi all, I'd like to participate to GSOC 2011. I have two propose: 1) r.in.modis: a module to import MODIS products with the possibility to create a mosaic. For this module I spoke with Markus N and he can do the mentor 2) from the GRASS GSOC ideas WMS and/or TiledMapService and/or WMS-T layer support, is there someone interested to do the mentor? what do you think is more useful / interesting for GRASS project? -- ciao Luca http://gis.cri.fmach.it/delucchi/ www.lucadelu.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSOC: ideas
Hi Luca, Glad to hear you are thinking of applying :). On Wed, Mar 30, 2011 at 13:23, Luca Delucchi lucadel...@gmail.com wrote: 2) from the GRASS GSOC ideas WMS and/or TiledMapService and/or WMS-T layer support, is there someone interested to do the mentor? I like this idea, and would be interested in metoring, but I might be a bit busy during the summer, so I'd like to have a co-mentor, if possible. Especially the WMS / WMS-T parts. what do you think is more useful / interesting for GRASS project? Isn't MODIS already supported via GDAL? In general I at least feel that it would be interesting to have support for the OGC standards (WMS, WFS and possibly others) in GRASS, but I also feel that it is important to have good support for important data types. Looking forward to reading your application(s)! --Wolf ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSOC: ideas
2011/3/31 Wolf Bergenheim wolf+gr...@bergenheim.net: Hi Luca, Glad to hear you are thinking of applying :). thank Wolf On Wed, Mar 30, 2011 at 13:23, Luca Delucchi lucadel...@gmail.com wrote: 2) from the GRASS GSOC ideas WMS and/or TiledMapService and/or WMS-T layer support, is there someone interested to do the mentor? I like this idea, and would be interested in metoring, but I might be a bit busy during the summer, so I'd like to have a co-mentor, if possible. Especially the WMS / WMS-T parts. Have you already some idea? I spoke with martin about a possibility of use python gdal or owslib (i already use it to download automatically several tiles) what do you think is more useful / interesting for GRASS project? Isn't MODIS already supported via GDAL? yes it's possible use r.in.gdal, but my idea is a module from download to the import. In addition there are some operations before the import specially if you want create and import a mosaic. --Wolf -- regard Luca http://gis.cri.fmach.it/delucchi/ www.lucadelu.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSOC: ideas
Wolf: Isn't MODIS already supported via GDAL? The processed level 3stuff comes in HDF(4) format, which GDAL knows, see http://grass.osgeo.org/wiki/MODIS as for the raw level 1B and level 2 stuff which may come by scan line(?) I seem to recall that was a motivation for adding/ extending the thin plate spine functionality in gdalwarp? but nicer ways of dealing + processing that could be the intention of the module..? anyone using that low level data? Markus? wiki page: The USGS/NASA's MODIS Reprojection Tool (MRT) support reprojection for Level 3 data or MODIS Swath Reprojection Tool for Level 1B or 2 data and can be used to create a GeoTiff. https://lpdaac.usgs.gov/lpdaac/tools/modis_reprojection_tool https://lpdaac.usgs.gov/lpdaac/tools/modis_reprojection_tool_swath Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] gsoc ideas
Hi, OSGeo has been accepted as an organisation for Google Summer of code [1] - congrats! Of course GRASS is going to participate in this program too. In the last years a lot of nice improvements has been done within GSoC [2]. I hope that this year will be successful at least as the last years. Please feel free to put new ideas for GSoC 2011 at the wiki page [3]. Regards, Martin [1] http://lists.osgeo.org/pipermail/discuss/2011-March/008698.html [2] http://trac.osgeo.org/grass/wiki/SoCProjects [3] http://grass.osgeo.org/wiki/GRASS_SoC_Ideas_2011#Ideas -- Martin Landa landa.martin gmail.com * http://geo.fsv.cvut.cz/~landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
