Developing a Field-companion app

Hi everyone,

The past couple of weeks I've been working on a field-app built especially for ecologists. The main trigger was that as an engineer working in ecology, I've often heard frustrations from other engineers about data-management in fieldwork. 

So I've started building something that would improve the fieldwork experience, tailored towards ecology:

  • Offline first
  • Records structured data (customisable attributes but trying to provide everything out of the box)
  • Exports to Darwin Core Archive, Shapefile, GeoPackage, CSV, or custom templates for your local records centre
  • GPS track recording, photo attachment, equipment logging

It's still in early development and only a couple of people are testing it (I can not support any more testers at the moment) but I'd really value input from people who deal with this daily:

  • Is the reformatting step for ecology databases a real pain point, or just annoying but manageable?
  • Where does your data actually end up? GBIF? NBN Atlas?
  • What would make you trust a new tool enough to use it on a real field campaign?

I've put up a page with more detail if anyone's curious: gettaxon.com

I'd love some honest feedback.




Chris Nicholas
@chrisgnicholas  | he/him/it
Society for Conservation GIS
IT 'Forest Gump' veteran in remote sensing/location services/XR/IoT ML/Agentic AI
Conversation starter level 2
Poster level 1
Commenter level 2

how is this fundamentally different than Kobo toolbox, SMART collect, Cybertracker, Earth Ranger mobile?



I also understand the new SERCA effort will redo/unify EarthRanger and SMART collect

 

 

https://www.kobotoolbox.org/