From field data to publishable ecological portals.
Niamoto turns occurrence records, taxa inventories, and plot data into shareable static portals. Open source, plugin-based, built for ecologists.
pip install niamoto 
The toolkit in three verbs.
Each stage is a module. Each module is a plugin. No black boxes.
Import any ecological data.
CSV, GeoPackage, GeoJSON, raster. Auto-configuration detects file types and maps fields. Darwin Core friendly.
datasets:
occurrences:
connector:
type: file
format: csv
path: imports/occurrences.csvTransform with plugins.
Declarative YAML transforms turn raw data into indexes, statistics, distributions, and widgets. Extend what is missing.
- group_by: taxons
widgets_data:
distribution_map:
plugin: geospatial_extractor
- group_by: plots
widgets_data:
species_list:
plugin: top_rankingPublish a static portal.
Auto-generated site with maps, charts, and per-group pages. Deploy anywhere — GitHub Pages, Netlify, your own server.
niamoto run
# → exports/web/ ready to deployThree surfaces, one publishing grammar.
The aim is not to showcase one deployment's numbers. It is to show how the same publishing logic turns field material into pages people can actually consult.
The portal opens with orientation, not noise.
Maps, recent additions, and portal sections are presented as reading landmarks. The page introduces a territory and the way its data is organised at the same time.
- Context The territory is named and situated before any stat becomes meaningful.
- Access Navigation gives direct entry to taxons, plots, methods, and updates.
- Tone The interface reads like a publication front page rather than a dashboard.
A list becomes a way of reading the corpus.
Each group is presented as a legible index that can be scanned, filtered, and revisited by botanists, managers, or contributors — 1 667 taxons here, plots and shapes in another tab.
- Corpus The list shows the scale of the group — every entry accessible and individually readable.
- Filters Sorting and browsing remain attached to ecological categories, not only technical fields.
- Continuity From this index, every detail page keeps the same visual and narrative language.
A group detail page is where map, evidence, and method meet.
The detail page for any Niamoto group — taxon, plot, shape, or another reference — is the clearest output: a single page that assembles occurrences, territorial context, and reading cues into a durable reference.
- Map Occurrences are visible as a territorial pattern, not a hidden attribute.
- Method Charts and summaries remain tied to the way the data was structured upstream.
- Durability The page can be cited, shared, archived, or read offline as a static document.
From inventory to public reading.
The portal is only the last visible layer. What matters is the continuity between survey material, structured transformations, and the final pages.
Collect
Occurrences, plots, taxonomies, and territorial files are gathered in their raw form, with all the irregularities of real field work.
Structure
YAML pipelines define the logic that turns files into indexes, summaries, widgets, and page-ready content.
Publish
The result is a static portal: clear URLs, shareable pages, and no hidden runtime dependency on a hosted backend.
Consult
Researchers, institutions, and field teams read the same material through pages designed for long-term consultation.
Live portals built with Niamoto.
The same grammar, three territories, one static output.
Portail des forêts du Bassin du Congo
Gabon – Cameroun
Partners to be announced
Portail de la flore amazonienne
Guyane
Partners to be announced
A desktop app and a CLI, same engine.
For scientists and field teams.
Drag-and-drop your data, configure collections visually, publish in one click. Available for macOS, Windows, and Linux.
For developers and automation.
Python-first, plugin-based. Scriptable for reproducible pipelines and CI workflows.
pip install niamoto
niamoto init my-project
niamoto runCalm, declarative, field-scientist.
A portal is interesting not because one deployment reached a figure, but because the publishing system stays legible when the project scales, changes region, or outlives its initial funding.
Evidence over scoreboard
Screens, detail pages, and method notes communicate more than a hero KPI ever will.
Method stays visible
The publishing chain remains part of the narrative, so readers understand what produced the page they are consulting.
Same grammar, many territories
Nouvelle-Calédonie is an example, not the whole story. The page frames it as one deployment among others.
Static as a feature
A shareable ecological portal should remain deployable, archivable, and readable without platform dependence.
Built in the open, for the scientific community.
GPL v3 licensed. Maintained by Arsis. Pull requests welcome — and a repeatable publishing grammar that turns ecological work into pages that can be read, cited, and maintained over time.
GPL v3 · Maintained by Arsis
Our partners
Funders, research institutions, and data providers
