Some deployments need more than CMS-published GeoJSON and mapsight-pulp transforms: structured imports, a station model, time-series storage, and a public read API for Count Aggregator and similar dashboards.
Mapsight monorepo packages (@mapsight/count-aggregator-api, @mapsight/count-aggregator-ui) consume such an API — but
the platform application itself is host-operated and not part of the open-source monorepo today.
| Signal | CMS + pulp | Platform |
|---|---|---|
| Bicycle/pedestrian/traffic counter time series | Limited | ✓ |
| Scheduled imports from vendor APIs (Niotix, EcoCounter, OCPI2, …) | — | ✓ |
| Admin UI for stations, presets, data quality | — | ✓ |
| OpenAPI-documented public GeoJSON + values API | Partial | ✓ |
| Meilisearch or similar search over station metadata | — | ✓ |
If thematic maps only need static or lightly transformed GeoJSON, start without a platform.
flowchart TB
Vendors["External vendor APIs CSV"]
Platform["Host data platform Laravel"]
DB["MariaDB or equivalent"]
Public["Public read API OpenAPI"]
Admin["Authenticated admin modules"]
UI["count-aggregator-ui embed or SPA"]
Vendors --> Platform
Platform --> DB
Platform --> Public
Platform --> Admin
UI --> Public
Typical stack (reference deployments): Laravel backend, React admin modules, relational DB, optional Meilisearch. Exact versions and modules vary by host.
| Package | Role |
|---|---|
@mapsight/count-aggregator-api |
TypeScript client + types aligned to platform OpenAPI |
@mapsight/count-aggregator-ui |
React dashboard widgets (wizard, charts, map layers) |
| Host CMS/SPA app | Builds embed or /count-aggregator/ SPA shell |
The platform exposes routes such as:
GET /{type}/stations,GET /stations.geojsonGET /{type}/values/{from}/{to}/{resolution}GET /{type}/last-values/{resolution}- Published OpenAPI at
/public/count-aggregator/openapi.json(path prefix varies by host)
Configure the API base URL in host app env — never hardcode customer domains in public package docs.
- Deploy platform behind same ingress as Mapsight apps (common path prefix e.g.
/msp/). - Run import schedulers and migrations on the host.
- Publish public API routes separately from authenticated admin routes.
- Build count-aggregator UI into CMS snippet or SPA; point
@mapsight/count-aggregator-apiat public base URL.
The demo app includes a mock API for local development without a live platform.
The reference platform is proprietary today (may open-source later). That affects:
- opencode.de / CIVITAS component listings
- What can be copied into public documentation vs maintainer-only notes
Public docs describe the pattern; deployment-specific URLs, customer names, and admin modules stay in private maintainer docs.
- Public documentation for self-hosted platform setup when/if repo opens
- Generic docker-compose example without customer-specific config
- Alignment of platform OpenAPI with
@mapsight/count-aggregator-apirelease cadence
- PULP.md
- Integration overview
- Ecosystem
@mapsight/count-aggregator-uipackage README and PLAN