EcoAquatic - a free South African aquatic-species conservation platform (built on GBIF / iNaturalist data) - by @uncleh25

Goal of the tool:

A free, non-commercial platform focused on South African aquatic species and their conservation. It lets anyone look up a local fish species, see its IUCN conservation status and a conservation “health” picture, view where it has been recorded, and log their own sightings. It is aimed specifically at South African waters (the Benguela and Agulhas systems and South African estuaries) rather than being global but shallow.

Niche it fills in the iNaturalist ecosystem:

iNaturalist is broad and global; EcoAquatic is narrow and local. A South-African-aquatic conservation lens layered on top of the observation data the community already produces. Species occurrences come from GBIF (which includes this community’s research-grade iNaturalist observations), enriched with IUCN Red List status and FishBase biology, plus local features iNat doesn’t aim to cover: conservation health scoring, threat/incident reporting, and strict geoprivacy for threatened South African species. It’s meant to complement iNaturalist, not replace it. iNat for observing broadly, EcoAquatic for a focused conservation view of local species.

Is there a commercial component, or do you plan into include one in the future? Are donations requested? (yes/no, explain):

No. EcoAquatic is free and non-commercial. There will be no ads, no paid tiers, no donations requested, and no current plan to monetize it.

What sort of data (if any) does your app collect from its users?:

For people who create an account: an email address and a display name (passwords are stored hashed).

For people who contribute: the observations and incident reports they choose to submit species, date/time, location, and any optional photos or notes, and device GPS only if they tap to auto-fill it. Location data for threatened species (IUCN VU/EN/CR) is coarsened to roughly a 10 km grid before it is ever shown publicly, and incident reports can be submitted anonymously. Data isn’t sold or shared commercially.

Link to your iNaturalist profile:

https://www.inaturalist.org/people/uncleh25

Description:

I’m a South African angler and iNaturalist observer, and I’ve been building EcoAquatic (https://ecoaquatic.org) to give our local aquatic species a dedicated conservation home. You can search roughly 3,000 fish species recorded in South African waters, see each one’s IUCN status, population trend, FishBase biology and a conservation health score, view recorded occurrences on a map, and log your own sightings. Threatened species have their locations automatically obscured to protect them. It’s early and solo-built, and currently web-based (a mobile app is planned), so I’d genuinely value feedback from people who know this data well.

Discussion questions or areas seeking feedback:

  • Does the South African species coverage and taxonomy look right to those who know it?
  • Is the conservation information (IUCN status, health scoring) clear and scientifically sound?
  • How does the sighting-logging flow feel — anything confusing or missing?
  • Is the geoprivacy approach (10 km coarsening for threatened species) the right call, or would you handle it differently?
  • Any South African anglers or naturalists here who’d like to contribute sightings and help build the local picture?
3 Likes

This is very exciting! I am not an angler and I know very little about local aquatic species other than what has been shared with me by others who are more knowledgeable…but this seems to fill such an important niche and (from my first-impression visit) it looks like a solid, robust, scientifically sound project. I appreciate the tag line ‘mapped and defended’. Well done!

when you say that there’s threat/incident reporting, who actually gets these reports? ultimately, a report is only useful if people are using it to take action. if you’re creating a new platform that attempts to carve away a subset of what would have been iNaturalist observations, i’m not sure how this makes things better. all of a sudden people who are trying to monitor things now have to monitor another platform.

i didn’t look at exactly how you’re doing this or planning to do this, but just based on your interface and your description here, you’re almost certainly doing it wrong. iNaturalist’s own geoprivacy mechanism has problems, but what you’re describing sounds problematic, too.

Thank you, that really means a lot, especially this early. “Mapped and defended” is the whole idea in three words, so I’m glad it landed. And you don’t need to be an angler to help: a lot of what makes this useful is just people caring that it’s accurate and clear. If anything ever looks off or confusing as you poke around, I’d genuinely welcome it and further improve upon it.

1 Like

Thanks, and these are exactly the questions I need to be asked, so I appreciate that you took the time.

On who gets the incident reports, honestly, that loop isn’t closed yet. Reports currently go to operational roles inside the platform (rangers, moderators, institutions) and a review queue. but the part that actually matters, routing an illegal-fishing or pollution report to a real authority who can act (here that’d be DFFE’s fisheries side, SANParks, CapeNature), isn’t wired up, because none of those bodies are on it. I’d rather build that with input than guess: in your experience, who should receive this kind of report for it to lead to action?

On the “why another platform” point, that’s fair, and I am aware that there’s an overlap. I’m not trying to pull observations away from iNaturalist. EcoAquatic is built on top of GBIF occurrence data (which already includes the community’s iNat records), and what I’m actually trying to add are the parts iNat doesn’t aim at: threat/incident response, conservation-status synthesis (IUCN, SASSI), and a tight South-African-waters focus. The direction I want is to consume that open data as a conservation lens, not ask anyone to re-log somewhere new, rather “a view on data you already contribute,” not a competing silo. If that isn’t coming across, that’s genuinely useful for me to hear.

First the geoprivacy part, right now I coarsen threatened-species locations by snapping the true point to a ~0.1° grid, and I’ve come to think that has real problems. It’s a smaller cell than iNaturalist’s (~0.2°), so it’s actually less protective. Snapping to a grid node makes an obscured point look falsely precise, and repeated observations in the same cell collapse onto the same node, which can signal a frequently-visited spot rather than hide it.
So I’m reconsidering it, likely a larger cell for the most sensitive species, randomising within the cell instead of snapping to a node, and showing it as an area rather than a precise-looking pin. If you’ve got the time, I’d really value specifics on what looked problematic to you.

i would reach out to the enforcement section of each of these bodies to see how they get their reports to act on currently. this will tell you whether they would even be open to ingesting another source of information. if so, then i would ask them about the good and bad points of the various feeds that they currently use.

if your scope is only aggregating and providing another view of the data, that might be useful, but for that, you only need interfaces from other systems, not a mechanism to record additional reports in your own system.

there are many potential issues with implementing some sort of geoprivacy protections. one thing to know is that geoprivacy protections that consider location only will be ineffective when there are other related records that are not protected.

i don’t want to get too much into the other sorts of problems because that sort of discussion could provide insight into some of the less obvious but bigger issues with iNaturalist’s location protections.

Thank you for this, this is really helpful.

With regards rto enforcement, I’m going to act on it and reach out to the enforcement sections (DFFE fisheries, SANParks, CapeNature) to understand how they currently receive and act on reports before I build any more of that side. You’re right that if nobody ingests it, and if the real value is aggregation and a conservation-focused view, that leans far more on interfacing with existing systems than on collecting new reports. That’s a genuinely useful reframing of where to point this.

On geoprivacy: the point that location-only protection fails when correlated records aren’t protected has landed, and it’s shifted how I think about it — a whole-system property rather than one coarsened field. I can already see vectors in my own data (a user’s other unobscured sightings from the same trip, photo metadata, timestamps), so I’ll treat it that way. I completely understand not wanting to detail the subtler iNaturalist issues publicly — if you’d ever be open to sharing any of it privately I’d be grateful, but genuinely no pressure; you’ve already given me a lot to work with.

1 Like

EDIT: I did a proper system-level pass rather than just the coordinate. I tightened how the correlated stuff (free-text fields, timestamps, who sees what) could give an obscured location away, and locked precise data to vetted roles. Also took th other advice and reached out to the enforcement side of DFFE / SANParks / CapeNature to understand how they actually receive and act on reports before I build any more of the incident side, and I had a couple of early replies, still learning there. Genuinely appreciate the push; it made the thing better. Happy to go into the geoprivacy detail by DM if you’re ever curious.

2 Likes