0 %

Hello There!

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

Information

Follow Me

linkedin
contact@redagraphics.com
Resume

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
Mapersive · Process section

How the pipeline took shape.

Mapersive served two people who rarely share a tool: the GIS analyst who works the data, and the city decision-maker who works the question. The process started with both.

Discovery & research

Two users, two very different questions.

Research meant studying both sides of the same dataset: how analysts already worked in Esri, and what city officials needed to see before they could act. Switch between them to see what each one asked of the product.

Confidence on every asset

Extraction results they could check, correct, merge or reject against the source imagery.

Structure that matches the city's data

Feature types, custom attributes and storage set up the way their dataset already works.

Delivery into Esri

Layers pushed straight into the tools they already use, with no extra steps.

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.

My role beyond the screen

Designing the hand-off, not only the interface.

Most of the work sat between layers: what one step passes to the next, and who owns it.

Traced what the analyst and the decision-maker each do at capture, extraction, validation, structuring and delivery, so neither had to learn the other's job.

Feature types, custom attributes, personalization and storage structure, flexible enough for complex urban datasets.

Export formats, scheduled syncs and shared map views, worked through with engineering so output lands in existing GIS workflows.

Teams, roles and access, project assignment and activity history, added as the platform grew beyond single users.

Impact & reflection

From street imagery to decisions cities act on.

Built and refined from zero, the platform grew from extraction alone to teams, feature personalization and full Esri delivery, and is now used by major cities in Morocco and abroad.

5Layers from street to Esri
2Users served by one pipeline
1Integration into existing GIS tools
What this changed about how I design

Designing for two users at once taught me to design the hand-off as carefully as the screen. The output had to be exact for the analyst and obvious for the person acting on it.

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.
next

Souk Artisan

Product Design