AfCENAtlas

From a data source to a map anyone can question

Six stages, each with a clear split between what you do, what Atlas prepares and what the platform guarantees.

Start mappingData and governance
  1. 01

    Connect

    0-1

    Link PostgreSQL, PostGIS, Corridor OS, a GeoJSON URL, an ArcGIS FeatureServer or a WFS, or upload GeoJSON, CSV, KML or a zipped Shapefile.

    You
    Choose the source and test the connection.
    Atlas
    Browse the tables and layers and preview the features.
    The platform guarantees
    Secrets are encrypted and write-only. Database queries run read-only.
  2. 02

    Build

    2

    Create a map and add layers from your datasets, grouped the way your audience thinks.

    You
    Pick the datasets, name the layers and set the default view.
    Atlas
    Propose layers, groups and camera framing from a plain-language brief.
    The platform guarantees
    Every dataset records its feature count, coverage, schema and source.
  3. 03

    Style

    3

    Colours, Maki icons, sizes, labels, legends, clustering and zoom ranges, over light, dark or satellite basemaps.

    You
    Set the look of each layer and its legend.
    Atlas
    Restyle and toggle layers on request.
    The platform guarantees
    Stored styles round-trip exactly into the viewer. What you set is what renders.
  4. 04

    Version and publish

    4-5

    Validate the map, save versions and publish an immutable snapshot at a stable URL.

    You
    Choose public, organisation or private access and approve publication.
    Atlas
    Check the map for publication and list what would block it.
    The platform guarantees
    Published versions are immutable and checksummed. Draft edits never leak into them.
  5. 05

    Embed and share

    6

    Share the live link, embed the viewer with an iframe, or read the map in code with the typed client.

    You
    Pick the version and the clean-embed options: language, layers, panel, camera, basemap and title.
    Atlas
    On public maps, answer visitors within that one map only.
    The platform guarantees
    Private and organisation maps require sign-in. A pinned version never changes.
  6. 06

    Ask Atlas

    7

    Ask questions in plain language and watch Atlas work the map.

    You
    Ask, follow up and decide what to do with the answer.
    Atlas
    Plan the steps, fly the camera, toggle layers, query features and keep the context.
    The platform guarantees
    Every step is traceable in Activity and every tool call is audited.

What you hold at the end

  • A published map

    A stable URL for the live, interactive map, with labels in English and Portuguese.

  • A dataset catalogue

    Every source with its licence, attribution, feature count, coverage and ingestion status.

  • Governed layers

    Styles, groups and legends stored as data, not buried in code.

  • A publication check

    What passes, what blocks publication and which layers are unavailable, stated plainly.

  • Version history

    Every published version, who published it, when, and its checksum. Never overwritten.

  • Machine-readable config

    The published map as JSON through the public API, typed by @afcen/map-client.

You do not have to watch it work

Long jobs, such as ingesting a large dataset or a multi-step Atlas run, keep going in the background. You are notified in the app, and by email if you choose, when work completes, fails or needs your decision.

Bring your corridor data to the map

Connect a database, a web service or a file, shape the layers, and publish a map your partners can open, embed and question.

Start mappingContact us