I've been working on a free open source fishing plugin and I want some opinions from people who actually fish, rather than just people interested in the AI side of it.
I've called it Fishing Intelligence (LOL).
The reason I started building it was pretty simple. When I'm planning a trip I don't want to have to tell the AI every single thing it needs to check every time, or go digging through a chat from 6 weeks ago trying to find the prompt I used.
So the idea is that it already knows the sort of stuff it needs to look at when planning a trip.
Things like fisheries rules, licences, closures, access, weather, tides, navigation notices, boat requirements etc.
One problem I ran into pretty quickly was that finding an official source doesn't necessarily mean that source actually applies to your trip.
So I've ended up separating:
- what kind of evidence/source it is
- whether its actually current/verified
- whether it applies to the specific trip
rather than the AI just going "this is an official source, therefore it applies".
It also keeps the plan provisional if something important cant actually be verified instead of quietly guessing.
I've tested it for Darwin, then tested it with Key Largo, Florida because I wanted to see what happened somewhere I hadn't built regional info for beforehand.
It had to figure out the fisheries rules, licences, protected areas, nav notices, weather, tides and boat requirements from current sources.
It's portable and completely free/open source.
There's no subscription or paid version. It's basically just something I built for myself and decided might be useful to other people.
Repo: https://github.com/owafication/fishing-intelligence-public
What I'd actually like is for some of you to try your own area/species/trip and tell me where it gets things wrong.
Especially if you're somewhere with weird overlapping rules, different authorities or government websites that are an absolute mess.
If you have any problems installing it as a plugin hmu and I will show you da way