StreetSeen - Reimagining Corridor
Seamless City Intelligence
Driving 0-1 Product Innovation to Revolutionize Urban Mobility with Sustainable Solutions.
StreetSeen is an urban intelligence platform built to help planners, architects, and healthcare providers make better, faster, data-driven decisions about the spaces where people live and move. By turning fragmented geospatial and real-time sensor data into intuitive, multi-scale visualizations, Scorridors enables cities and organizations to analyze accessibility, connectivity, and livability at a glance.
A Unified Design Language for a Global Digital Ecosystem
Context & Challenge
Our mission was to transform raw complexity into clarity — creating a product that could adapt to different users (from city planners to healthcare providers) while staying scalable across multiple cities.
Key Challenges
Real-Time Data & Usability: Displaying dynamic street-level info without overwhelming users.
Diverse Users Needs: Tailoring experiences for city planners, residents, and tourists.
Integration: Ensuring smooth integration with urban sensors and mapping systems.
Scalability: Creating a flexible interface that handles large data across cities.
HOW DID WE WIN IN 32 WEEKS?
Research & Discovery
Users & Stakeholders
Our primary audience spanned across public and private sectors, each with unique needs:
City Planners:
Needed to evaluate mobility, accessibility, and equity across neighborhoods.
Wanted scenario modeling tools to see how policy changes or infrastructure updates might ripple through a corridor.
Healthcare Providers:
Focused on understanding how corridor connectivity impacts access to care.
Wanted the ability to overlay social determinants of health (e.g., proximity to clinics, transit access, environmental factors).
Urban Designers & Architects:
Required visual modeling tools to experiment with corridor interventions.
Needed integration with existing urban data systems to avoid starting from scratch.
User Personas
City Planner
Urban Mobility & Policy analyst
Goals:
Assess mobility equity across corridors
Identify high-activity vs underserved areas
Prioritize investments for maximum community impact
Pain Points:
Current GIS tools are overly technical
Data is siloed across multiple platforms
Difficult to communicate findings to non-technical stakeholders
Healthcare Analyst
Public health researcher & access advocate
Goals:
Study how corridor connectivity affects access to clinics/hospitals
Identify “health deserts” and underserved populations
Collaborate with city agencies to align transport & health goals
Pain Points:
Limited ability to overlay health and mobility datasets
Insights often lag due to outdated batch data
Lack of clear visualization for community engagement
Urban Designer / Architect
Designer of interventions at corridor and street levels
Goals:
Model design scenarios (adding stops, greening streets, changing lane allocations)
Communicate design impact to planners and communities
Export visuals for stakeholder meetings and design proposals
Pain Points:
Hard to move from macro data → micro design decisions
Tools don’t support quick scenario testing
Existing visuals are too technical for public presentations
Measuring What Truly Matters in Urban Spaces
This diagram emphasizes the human experience of streetscapes — prioritizing safety, accessibility, greenery, and consistent building fabric. By highlighting how people perceive the city at walking speed, it shows that frequency of interest, protection from weather, and useful destinations shape how corridors support livability.
DESIGN Principles
CLARITY
Challenge observed: During research, planners and healthcare analysts felt overwhelmed by “data overload” from existing GIS dashboards. Complex layers buried the insights they actually needed.
How we addressed it:
Prioritized the signal over noise by designing a progressive disclosure model: high-level KPIs up front, deeper metrics only when requested.
Adopted a minimalist visual language — consistent stroke weights, color-coded corridor ribbons, and standardized icons — to reduce cognitive load.
Result: Users reported they could interpret dashboards more quickly and felt more confident sharing outputs with non-technical stakeholders.
Scalability
Challenge observed: Urban systems exist across multiple scales — regional networks, neighborhood corridors, and street-level segments. Most tools force users into one scale only.
How we addressed it:
Built a multi-scale visualization model (Network → Corridor → Segment), allowing seamless zoom with contextual continuity.
Created reusable components in the design system that adapt to each scale, so the interface feels consistent whether viewing 5 miles or 500 feet.
Result: Scorridors scaled gracefully across large cities and small districts, enabling broader adoption and cross-department collaboration.
Transparency
Challenge observed: Stakeholders worried about trusting real-time feeds — if data felt incomplete or outdated, they hesitated to act on it.
Integrated data provenance cues: timestamps, source labels, and confidence indicators directly into the UI.
Designed visual treatments (opacity, hatching) to convey uncertainty instead of hiding it.
Added contextual “insight cards” that explained anomalies (e.g., “Transit feed delayed — showing last known values”).
Result: Users trusted the tool more, reporting higher confidence in using Scorridors for decision-making and presentations.
THE DESIGNS
A modular control center designed for clarity, urgency, and scalable threat visibility.
Network Mode
Corridor Mode
Segment Mode
01. Multi-scale visualization (network → corridor → segment)
GOAL: Let users move fluidly from strategic, city-wide patterns to tactical, block-level detail without losing context.
What we built:
Network Mode (city / region): aggregated corridor ribbons over a subdued base map. Useful for spotting city-wide trends (high-activity corridors, transit deserts, health-access clusters).
Corridor Mode (route-level): single corridor selected — longitudinal view with split-map: route timeline on the left, map on the right. Shows flows, stops, and corridor-specific KPIs across time.
Segment Mode (street/block): block-by-block view with detailed micro-metrics: pedestrian counts, curb cuts, transit stop accessibility, air quality.
Data behaviors:
Automatic aggregation: server-side aggregation at different zoom levels to keep maps fast and readable.
Uncertainty visualization: opacity or hatching for low-confidence segments to avoid overinterpreting sparse data.
02. Intuitive UI: layered maps, filters & interactive overlays
GOAL: Allow users to tailor complexity to their task, surfacing insights rather than noise.
Core UI elements:
Layer Manager: grouped layers (transport, health, environment, demographics) with opacity sliders and legend previews.
Filter bar: persistent top bar with common filters (date/time, mode, demographic cohort) and an “Advanced Filters” modal for compound conditions.
Insight Cards: contextual micro-explanations that appear when a pattern of interest is detected — e.g., “Transit frequency drops during late evenings along this corridor; consider increased stops.”
Segment Inspector: docked detail panel with time-series, raw sensor feed snippets, and download buttons.
Scenario Builder: sandbox UI that applies modifications (close lane, add bus stop) and runs a quick difference simulation showing projected KPI deltas.
Microinteractions:
Hover reveals light tooltips; click pins open full inspector.
Progressive disclosure: advanced metrics hidden by default and surfaced with a single click.
Map double-click to center; keyboard navigation of list items; ESC to close modals.
03. Customizable dashboards for different roles
GOAL: Let each user arrive at a tailored workspace optimized for their goals—without building separate tools.
Widgets (examples):
Corridor Summary Card (top KPI strip)
Time Slider & Playback Controls
Layer Manager (toggle overlays: transit, bike lanes, air quality, crime)
Comparison Panel (compare two corridors side-by-side)
Scenario Builder (apply “what-if” interventions and preview outcomes)
Layout & customization:
Drag-and-drop grid layout (saveable presets)
Shareable “view links” — encode filters and map position in URL for collaboration
Export: PDF report template and CSV export for data teams
05. Design System & Components
GOAL: Create a modular system enabling consistent UI, fast prototyping and cross-product reuse.
Design tokens:
Color tokens for map semantics (positive / negative / neutral), typographic scale, spacing, elevation/shadow tokens.
Key components:
MapShell (Map + Controls)
LayerToggle + LegendItem
CorridorCard (summary + CTA)
SegmentInspector (timeseries + raw data + provenance)
TimeSlider + Play/Pause
ScenarioBuilder modal + results table
Notification / Alert toasts
PresetLayout manager
Map symbology:
Colorblind-safe palettes, patterned fills for uncertainty, iconography for sensor types, and scalable corridor strokes.
Documentation:
Component usage guidelines, keyboard interactions, responsiveness rules, and accessibility examples.
Driving Transformation, Enhancing User Experience, and Delivering Measurable Results Across Key Metrics
~30%
~50%
+15%
^25%
“Scorridors helped us see the big picture and the street-level detail in the same tool. That’s a game changer for planning.” — City Planner, Orlando
🔍 Reflections
Driving Transformation, Enhancing User Experience, and Delivering Measurable Results Across Key Metrics
Balancing Complexity with Clarity:
One of the biggest design challenges was simplifying dense geospatial data without oversimplifying. The layered zoom approach (Network → Corridor → Segment) became the key.
Scalability Matters:
Early testing showed that what worked for one city needed to scale to many. Designing modular components and dashboards helped future-proof the product.
User Trust is Critical:
Early testing showed that what worked for one city needed to scale to many. Designing modular components and dashboards helped future-proof the product.
🛠️ Next Steps
Scorridors has strong foundations, but its potential continues to grow