All work

Cartostead

Before the map, a publication system.

In development

A geospatial publication and serving platform for catalogs, permissions, validation, jobs, styles and map/vector/tile delivery.

What I’m building

Spatial publication is more than putting a map on a screen. Data quality, jobs, styles, permissions and serving behavior need a coherent lifecycle.

My role

Product & systems architecture

I’m building the publication and serving architecture around spatial catalogs, permissions, asynchronous jobs, validation and operational auditing.

Spatial publicationControl planeMap services
Cartostead dashboard with demo spatial workspaces, published layers and background jobs.
Publication dashboard · Demo data
Cartostead

Publication dashboard · Demo data

The design decision

Separate the publication control plane from the serving path. Catalogs, validation and permissions coordinate the work; serving components expose map, vector and tile outputs.

What needs care

Spatial data quality, long-running publication work, permission boundaries and service consistency matter as much as visualization. The development scope includes standards-based map services and vector/tile delivery.

Architecture walkthrough

From spatial dataset to service

An illustrative system flow, not live product activity.

  1. 01

    Dataset

    Spatial sources enter the publication workflow.

  2. 02

    Validate

    Validation assesses the data before publication work proceeds.

  3. 03

    Process

    Jobs prepare spatial outputs and publication state.

  4. 04

    Publish

    The publication pipeline coordinates prepared data and styles.

  5. 05

    Catalog / permissions

    The control plane manages catalog state, permissions and auditing.

  6. 06

    Map / vector / tiles

    Serving components expose the published spatial outputs.

Next case studyQanivo