Proposal for GSoC 2025: AI-Powered Natural Language Interface for GRASS GIS

Hi Anna,

I hope you are doing well. I wanted to kindly ask if you could take a look at this pull request I’ve created: https://github.com/petrasovaa/grass/pull/2. It’s based on the task you mentioned, and I’d greatly appreciate your feedback.

Thank you for your time!

Best regards,
Sachinta

Your PR has 5000+ changed files…

Oh, I’m sorry, that was a mistake. Here is the correct one: https://github.com/petrasovaa/grass/pull/1.

I’m really sorry for the inconvenience that occurred.

This is cool idea. I think it should be possible to abstract away the exact backend model used and either run on a local instance or indeed use a remotely run model (e.g. in a university or company where users would share the same model). This way I don’t think that OSGeo would need to host anyting, but instead it would be up to the user or admins to decide what to run where, and the chat interface would simply connect to whatever is specified, or maybe start a local instance if nothing is provided. @Sachin-NK do you think this sounds feasible?

@Sachin-NK do think that the module could be written in such a way that the user doesn’t need to set up anything to start a local model, or would that require a one-time setup?

Also regarding the knowledge base, can it work on a SQLite which is perhaps more friendly to a self-contained solution (no need to install a DB server). Perhaps there could be multiple options again?

That sounds like a great approach! The chat interface could easily connect to a specified model, and if none is set, it could just start a local instance on its own. That way, users have flexibility without extra steps.

A simple setup script could make sure everything runs smoothly from the start, so there’s no manual configuration needed. Does this align with what you had in mind? :blush:

but I’m still having some trouble fixing my task. When I tested it manually using the same input file, the output seemed correct on my end. However, the reviewer found that it still doesn’t work properly.

Since we’re using the same input file, I’m trying to understand what might be causing this difference. Could there be any factors I might be overlooking? I’d really appreciate any suggestions on how to align my testing to ensure the fix works correctly for everyone.

Here’s the PR link:https://github.com/petrasovaa/grass/pull/4

my output :


reviewer’s output :

I answered it in your other post. May I suggest not posting your question on multiple places and please be more patient, people have their lives and may not be able to respond immediately.

I’m really sorry about that! :pray: I truly appreciate your time and understand that everyone has their own commitments. I’ll make sure to be more mindful and keep discussions in one place. Thank you for your patience!

Dear OSGeo Community,

I’ve drafted my GSoC proposal for integrating SLMs with GRASS GIS and would love your feedback. Any suggestions to improve it would be greatly appreciated!

Here’s the draft : Zero-Cost, Offline AI Chatbot for GRASS-GIS - Google Docs

Thank you for your time!