One codebase for the Peskas fisheries dashboards of Zanzibar, Kenya and Mozambique. Each dashboard gives fisheries managers and researchers a view of small-scale coastal fisheries (catch, revenue, fishing effort and fishing gear), broken down by district and updated regularly from field data.
Each country has its own dashboard, built from this same code. The dashboards are open: anyone can read them without an account or login. Zanzibar and Kenya are in Swahili and English; Mozambique is in Portuguese, English and Swahili.
- See the headline figures for the last complete months against the same months a year earlier, and the estimated catch, revenue and fishing trips of all boats by two methods side by side.
- Follow catch, revenue, catch and revenue per trip, trip length and the number of recorded landings month by month, for the whole country or for chosen districts.
- Compare districts on a map, in a ranked chart and in a table.
- See where tracked boats spend their fishing time on a 1 km grid map of fishing effort.
- Compare fishing gears: how often each is used, what it catches and earns per hour, and how much of its catch is below the size at which fish first reproduce.
- Explore the species landed: their share of the catch, how many tonnes of each all boats land (FAO ARTFISH estimate), their price, the size of the fish against the size at maturity, and the catch's mean trophic level.
- Check vulnerable species: catch by vulnerability to fishing, sharks and rays, and IUCN and CITES status.
- Read how every figure is made, and its limits, on the Data and methods page, and download any chart's data.
- Landing surveys. Enumerators (trained data collectors) record landings at landing sites. A landing is a boat's return to shore with its catch.
- GPS trackers (Pelagic Data Systems). Small solar-powered devices on some boats record where they travel. They feed the fishing-effort map, which covers only boats that carry a tracker.
- Estimates for all boats. Two methods scale the surveyed landings up to every boat of a district: the GPS tracker method, from how often tracked boats fish, and FAO's ARTFISH method, from the days fishers say they fished and the boat census. The dashboards show both, and the Data and methods page explains why their figures differ.
Each country's Peskas data pipeline cleans and summarises these records by month and district, and the dashboard reads those summaries. New data appears every few days, when the pipeline runs (every 2 days for Kenya and Mozambique, every 4 days for Zanzibar).
Terms used on the dashboards:
- Catch per unit effort: kilograms of catch per fisher per hour of the trip.
- Revenue per unit effort: revenue per fisher per hour, in local currency (Tanzanian shillings for Zanzibar, Kenyan shillings for Kenya, meticais for Mozambique).
The dashboards are developed and run by WorldFish. For questions, write to peskas.platform@gmail.com.
Peskas is WorldFish's open-source platform for monitoring small-scale fisheries (https://peskas.org).
- Peskas Timor-Leste: Timor-Leste portal
- Peskas Coasts: regional comparison across countries
- Peskas Tracks: app for fishers to see their trips and log catches
- Peskas Kenya BMU dashboard: dashboard for Beach Management Units in Kenya
- Peskas Management Platform: data review and download for survey teams
- Peskas Fishery Data API: programmatic access to landing data
- Data pipelines: Kenya, Zanzibar, Mozambique, Timor-Leste, Coasts
A pnpm Turborepo whose only app is apps/isomorphic-i18n: a Vite single-page app (React Router) with a small Nitro server for the tRPC API. It reads the monthly summaries that peskas.coasts::export_portal writes to MongoDB.
Requirements: Node.js 20.19+ or 22.12+ (Vite 8) and pnpm 9.
Setup
pnpm install
cp apps/isomorphic-i18n/.env.local.example apps/isomorphic-i18n/.env
pnpm run i18n:dev # dashboard at http://localhost:3001Fill in the values in .env. The full list of variables the build reads is in turbo.json.
One codebase, one deployment per country. Each country is a separate Vercel project built from this repository and configured through environment variables, so adding a country needs no fork. Each deployment needs at least:
VITE_COUNTRY_CODE: which country to build (TZ,KEorMZ; defaultTZ). Zanzibar usesTZ, Tanzania's country code.MONGODB_URI: the country's summaries database.MONGODB_URI_COASTS: the database that holds the district boundaries (wio_gaul2).VITE_MAPBOX_TOKEN: base map for the fishing-effort map.VITE_GA_MEASUREMENT_ID: the country's Google Analytics stream (seeapps/isomorphic-i18n/ANALYTICS.md).VITE_POSTHOG_KEY: the PostHog project all countries share (same file).
VITE_* values are public and inlined into the browser bundle at build time, so changing one needs a redeploy; the others stay on the server. Country settings (districts, colours, currency, map view, languages) live in packages/domain/src/country.ts. To add a country, follow apps/isomorphic-i18n/COUNTRY_SETUP.md.
Upgrading a deployment from 1.x (Next.js): rename NEXT_PUBLIC_COUNTRY_CODE, NEXT_PUBLIC_MAPBOX_TOKEN, NEXT_PUBLIC_GA_MEASUREMENT_ID and NEXT_PUBLIC_GA_ROLLUP_ID to their VITE_* names, and delete NEXTAUTH_SECRET, NEXTAUTH_URL, EMAIL_SERVER, EMAIL_FROM, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET and NEXT_PUBLIC_GOOGLE_MAP_API_KEY, which nothing reads any more.
Main commands
pnpm run i18n:dev,pnpm run i18n:build,pnpm run i18n:lint: run, build or lint the dashboard.pnpm --filter i18n previewserves a production build locally.pnpm run build,pnpm run lint: the whole workspace.
Production: the three Vercel projects (peskas-dashboard-zanzibar, peskas-dashboard-kenya, peskas-dashboard-mozambique) deploy to production on every push to dev, the default branch.
Releases: add a block at the top of NEWS.md. On every push to dev, .github/workflows/release.yml publishes that block as a GitHub release.
Tests: pnpm test (vitest) checks the country registry, the metric catalogue and the summary queries, the last on an in-memory MongoDB. packages/nosql/src/test-monthly.ts checks the live monthly summaries connection and data.
AI-assisted work: see CLAUDE.md.