๐บ๏ธImpact Tracker & Site Selection
What we needed to support
Once we had started operations there was a greater need to visually predict, optimize, and understand the impact of our activity. This system needed to be updated and recalculated frequently as weather forecast data changed and in-situ trajectory data was collected.
A large part of Running Tides methodology was deciding where to deploy to maximize the amount of materials sinking below a 1000m threshold. We also had a wide range of geospatial data that was a necessary input for our research and modeling work.
What we built
A web app that captures much of our research and deployment data and presents it all on a single map.
The web app lets you inspect
Deployment vessel paths
Path of all buoys
Modeled benthic density of deployed substrate
Modeled visual of the plume of deployed substrate
Modeled trajectories
Running Tide's different operating locations
Simulated paths of materials being transported
We also built a platform for geospatial data. This platform is intended for researchers but has a broad range of capabilities, may of which are available in the impact tracker as well.
Projected trajectories based on location, winds, waves and currents
Sink efficiency contours
Statistics
Anticipated operating areas
EEZs
What we wouldโve wanted to build next
Ultimately we intended the internal map to serve all geospatial data that we had acquired in a single place with a dedicated tile server. The impact tracker would eventually be superseded by this map once we were ready to make it public.
Our hope was that these tools would make communications about our work easier as well as giving our science team the tools it needed to rapidly develop new methods of removing carbon and deciding where to deploy from.
Last updated