Skip to content

Bijux Pollenomics

bijux-pollenomics publishes public evidence surfaces about Nordic pollenomics, environmental context, archaeology, boundaries, fieldwork, and ancient-DNA recovery. This site explains what the repository publishes today, what those outputs can answer, and where the limits still are before you lean on a report, ranking, or map view.

Maintainer-only notes stay under docs/internal/ and are not part of the public website navigation.

Python 3.11+ License: Apache-2.0 Verify Release PyPI Release GHCR Release GitHub Docs Release GHCR packages Published packages

bijux-pollenomics pollenomics

bijux-pollenomics pollenomics

bijux-pollenomics docs pollenomics docs

Start Here

If you are new to the project, read the site in this order:

flowchart TB
    pollen["pollen and environmental source families"]
    context["archaeology, boundary, and fieldwork context"]
    samples["sample-backed ancient DNA context"]
    reports["country bundles and atlas evidence tables"]
    atlas["visible atlas point or country surface"]
    review["traceability and limits stay visible"]

    pollen --> reports
    context --> reports
    samples --> reports
    reports --> atlas
    atlas --> review

What Is Strong Today

  • the repository already publishes tracked pollen, archaeology, boundary, and fieldwork context as reviewable files plus public report surfaces
  • world, Europe-plus, Nordic, and country bundles are one publication family, not disconnected products
  • the Sweden lake ranking packet and optional Nordic lake overlays now make lake prioritization visible without hiding the underlying evidence packet

What Is Still Constrained

  • animal aDNA extraction and the strongest claims that depend on deeper sample recovery remain less mature than the rest of the repository
  • visible map proximity still does not substitute for chronology review, source posture, or field verification
  • lake ranking surfaces are decision-support outputs, not bathymetry or coring plans

Choose A Route

  • use the product guide when you need the overall answer: what the repository is for and how the outputs fit together
  • use the data guide when you need the evidence answer: what is in scope, how it is governed, and what remains weak
  • use the report portal when you want the checked-in public outputs first
  • use the Nordic atlas guide when you need map behavior, filters, point posture, and overlay caveats
  • use the fieldwork record when you want one real visited location instead of a generalized public summary

These routes are written for readers first. You should be able to understand what the repository publishes, why a map or ranking exists, and where the limits still are without reading the source tree first.

Fieldwork Record

The fieldwork section is intentionally narrow. It anchors one mapped point to a real visit without pretending that field media replaces curated sample, paper, or supplement evidence.

Field sampling at Lyngsjön Lake on 2026-02-26.
Lyngsjön Lake, southwest of Kristianstad, during winter field collection on 2026-02-26.

What The Repository Does Not Claim

  • that map proximity alone establishes scientific weight
  • that every visible layer has identical provenance quality
  • that a project list alone is enough to justify a mapped point
  • that unresolved or region-only geography should be published like exact site evidence
  • that the current narrow animal aDNA atlas candidate surface means the repository is already scientifically broad
  • that the repository is already the full cross-evidence pollenomics engine

Read By Question