Nesta-related data platforms

Embedded engineering on Nesta ecosystem open tools: Svizzle Svelte viz library (including Mapbox-in-Svelte), WAIfinder UK AI map with Innovate UK, Dapsboard, EURITO indicators, and annotation backends—map-first geospatial UX, layers, and filters alongside accessible dashboards.

WAIfinder

Desktop

WAIfinder interactive map interface — desktop capture

Mobile

WAIfinder interactive map interface — mobile capture
Dapsboard
Dapsboard analytics dashboard
EURITO indicators
EURITO indicators application interface

Summary

Infomerx LLC supplied embedded software engineering across several open-source programmes in the Nesta data-and-innovation ecosystem. Map-first UX—declarative layers, filters, clustering, and map–list coherence—was central to that work (especially on WAIfinder), not a side track. Framing here is factual only and does not imply endorsement by Nesta or its partners.

Programmes and surfaces at a glance

  • Svizzle — Shared Svelte visualization library: charts, Mapbox-in-Svelte (@svizzle/mapbox), layout primitives, accessibility clean-up, and package documentation used across apps.
  • WAIfinder — Nesta and Innovate UK collaboration: UK AI ecosystem explorer—interactive map, lists, search and filters, org–place–topic flows, partner branding constraints.
  • Dapsboard — DAPS data exploration: nested aggregations, coverage-style queries, dataset specs, end-to-end authentication (tokens, HTTP 401 handling, hooks-based auth flows).
  • EURITO indicators — Application modernisation (Sapper → SvelteKit), Svizzle upgrades (time–region–value, themed UI), guide routes, quality tooling in delivery history.
  • Annotation / infrastructure — Services and deploy/teardown automation for document annotation pipelines against ElasticSearch / S3, with nginx and operator docs for safe AWS runs.
Technical notes

Front ends are predominantly Svelte / SvelteKit with Svizzle packages; backends include Node.js, ElasticSearch, AWS (e.g. SES, CloudFormation-style deploy scripts), Fastify / Express, and nginx. Commit details are available in the public repositories. This page stays at programme and architecture level.

Challenge

Policy and research audiences need maps, indicators, and dashboards that stay legible under real metric density: coherent map–list behaviour, progressive disclosure instead of “chart soup,” and reusable building blocks so each new tool does not reinvent visualization, auth, and deployment patterns.

Technical notes

Cross-cutting UX patterns include supercluster-style grouping, auto-zoom / manual map control hand-off, and explore machines (e.g. XState in Dapsboard) that keep query state aligned with the UI.

Approach

Infomerx worked inside existing programme repos: ship vertical slices in the product repositories, land shared abstractions in the library where they belong, and keep operator-facing docs and scripts honest so pipelines stay deployable—not only demo-ready.

Technical notes

Conventional commits, peer review in the upstream workflow, and cross-repo semver discipline on @svizzle/* packages (local npm link flows where apps trailed published releases) were part of day-to-day delivery.

What Infomerx delivered

  • Svizzle and Mapbox-in-Svelte — Shared Svelte components for data visualization, including @svizzle/mapbox: Mapbox wrapped so apps get declarative map layers and map UI widgets with the same reactivity model as the rest of the UI (used heavily in WAIfinder), plus charts, layout primitives, accessibility clean-up, and package documentation.
  • WAIfinder — The UK AI ecosystem explorer: interactive map, lists, search and filters, org–place–topic flows, and ongoing integration with the evolving Svizzle stack and partner branding requirements.
  • Dapsboard — DAPS data exploration: nested aggregations, coverage-style queries, dataset specs, and end-to-end authentication (token verification, client handling of HTTP 401, hooks-based auth flow).
  • EURITO indicators — Application modernisation (Sapper to SvelteKit), Svizzle upgrades (including time–region–value and themed UI), guide routes, and quality-tooling hooks in the delivery history.
  • Annotation backends — Services and deploy/teardown automation for document annotation pipelines against ElasticSearch / S3, with nginx and operator documentation so the stack could be run safely in AWS.
Technical notes

Infomerx-attributed commit volume across the six principal nestauk programme projects is on the order of 680+ unique commits in audited histories; full contribution details can be found in the public repositories.

Outcomes

Outcomes are best read as capability and maintainability: reusable visualization and map primitives, production-shaped auth and explore flows, and pipelines that other researchers and engineers could extend without a ground-up rewrite. Any quantitative programme metrics stay with the programme owners and contracts—not reproduced here.

Upstream code and docs live under the nestauk GitHub organization. Infomerx does not own those repositories; links are for transparency only.