0 %

Hello There!

Designing products people actually enjoy starts with a conversation, let’s talk.

Follow Me

Mapersive

Client
Mapersive
Role
Poduct Designer
Period
2023-2025

About Project

Every street holds information most people never think to look for signage, infrastructure, urban assets invisible until someone extracts it. Mapersive was built to do exactly that: turn street-level imagery into structured, usable geospatial data.

The challenge was never just extraction, it was translation making highly technical geospatial output legible and exportable for GIS analysts, city planners, and decision-makers working in tools like Esri, without forcing them to change how they already work.

  • Product design for GIS & geospatial tools
  • Systems integration
  • Team & role management design

Two users,
one pipeline.

Street imagery becomes a decision in five moves. A GIS analyst works the data; a city decision-maker works the question. The design had to hold both at once without asking either to learn the other's job.

01
Capture
GIS analyst
Defines the capture area and which feature types are worth extracting from it.
City decision-maker
States the question: which assets, which district, by when.
02
Extract
GIS analyst
Runs extraction and watches the confidence on every detected asset.
City decision-maker
Not their step. The platform stays quiet until there is something to look at.
03
Validate
GIS analyst
Corrects, merges and rejects features against the source imagery.
City decision-maker
Reviews a sample and flags what does not match the street they know.
04
Structure
GIS analyst
Sets feature types, attributes and storage structure for the city's dataset.
City decision-maker
Asks for the cuts they work in: by district, by asset type, by condition.
05
Deliver
GIS analyst
Pushes the layer straight into Esri, without leaving the workflow they had.
City decision-maker
Opens the map and acts on it: budget, maintenance, planning.

The hard part was never extraction. It was making the output legible to someone who will never open a GIS tool, while keeping it exact enough for someone who lives in one.

Five layers,
street to Esri.

The product is a stack. Each layer does one job and hands off cleanly to the next, which is what let the platform grow from extraction alone to teams, personalization and full Esri delivery.

01
Imagery intake
Owned by field ops
Capture sessions Coverage by district Source management
02
Extraction
Owned by GIS analysts
Feature detection Confidence scoring Review queue Correction tools
03
Feature library
Owned by GIS analysts
Feature types Custom attributes Personalization Storage structure
04
Workspace
Owned by admins
Teams Roles and access Project assignment Activity history
05
Delivery
Where the product ends
Esri integration Export formats Scheduled syncs Shared map views

Shaped by what streets don't say out loud
turning raw geography into insight
cities can act on.

01. Translating Geospatial Complexity

Design started by understanding two very different users at once technical GIS analysts and non-technical city officials and the gap between raw extracted data and a decision someone could actually act on.

02. Designing Intelligent Workflows

Feature types, storage structures, and export flows were designed to be flexible enough for complex urban datasets, yet simple enough to move seamlessly into existing GIS software without added steps.

03. Implementation

The platform was built and refined from zero, expanding to support team and role management, feature personalization, and full Esri integration now used by major cities in Morocco and abroad.