search

Open-EO / openeo-qgis-plugin

QGIS Plugin to connect and use openEO compliant backends.
Apache License 2.0
17 stars 1 forks source link

Status of the QGIS plugin? #80

Open cbic843 opened 9 months ago

cbic843 commented 9 months ago

Hello, I try to use the plugin, and it doesn't show up the backends providers at first. After checking the code, it seems that it is no more compatible with 1.x version of openeo API. Is there a new version in focus?

arongergely commented 9 months ago

Hi @cbic843, I am working on a new version, hope to make it available soon.

m-mohr commented 2 months ago

@arongergely Did you make progress on this?

arongergely commented 2 months ago

@m-mohr I made a start at rewriting it back in Jan, but then became time poor (lot of projects at work) so had to put it aside. It's been on hold until I can dedicate time to it. Perhaps now as I expect things to quite down soon due to the summer holidays.

arongergely commented 2 months ago

Back then I also tried to secure a project around it so I could have some paid hours to develop it, but sadly it did not go through. So for now it depends on my free time..

m-mohr commented 2 months ago

Thanks for the update, @arongergely. I can relate to that situation, not pressure, I was just curious.

What's the rough funding that would be required? I could also look for funding opportunities then. Thanks.

arongergely commented 2 months ago

Thanks, that would depend on the features we want. Initially discussed stripping it down to a kind of minimum viable plugin, able to run prepared jobs and download/display the output.

But some data browsing / display dialogs could be interesting from the start. Regardless of any funding I think we should get this minimum viable plugin out. (Can always try funding for more features if needed)

Would you be available to talk about this sometime?

m-mohr commented 2 months ago

Yeah, I think connecting to the backend (Basic + OIDC) + visualizations for Collections, Batch Job Results and Secondary Web Services would be sweet. Everything else that the plugin has at this point is not really needed for the QGIS plugin and is a nice to have.

Always happy to talk. What would you want to talk about? Just to make sure: I don't have any specific funding opportunities in mind yet. But if we have a ballpark number for the functionality above, it would probably help to consider it in potential projects. I guess it could be around 10-20k as it's mostly UI work and most API issues should be abstracted away by the openEO Python client.

arongergely commented 2 months ago

Ok, thank you. Don't get me wrong, I am just looking at putting (non-paid) time on it soon because July/Aug may be the best period for me to do that.

What would you want to talk about?

Not funding, more about the set of features and their priority. but we touched on that now already. I am saying their priority because if I do not get to finish them in my free time at least the highest priority (priorities) could be met and we could do a new release.

I guess it could be around 10-20k as it's mostly UI work and most API issues should be abstracted away by the openEO Python client.

Yes it's mostly UI work, but I would also set up unit tests + integration tests (to QGIS) as reasonably possible. Plus some help / docs.

That being said yes between 10-20k would be realistic. Where between, depends on how many features / how fancy.

m-mohr commented 2 months ago

That sounds good to me. As it's your time, I think you should define the priorities based on your use case(s). :-) I'd personally start with batch jobs and then do collections and web services as the last two are very similar. If you want to talk or have any issues during the implementation, please get in touch! Are you by any chance in the CloudNativeGeospatial slack? It would be a good way to keep in touch.

arongergely commented 2 months ago

Are you by any chance in the CloudNativeGeospatial slack?

Thanks, I just joined! Wasn't aware of their slack.