Accepted Interactive Prototype

Downtown Elgin Google Maps Interactive Tour

A guided 3D exploration of downtown Elgin’s landmarks, riverfront, and civic story, with explicit sources, accuracy limits, user-directed camera movement, and a complete map-free reading path.

Status
Accepted interactive prototype
Experience
Four guided story stops
Map
Google Maps Platform 3D context
Authority
Independent; not an official City service
Downtown Elgin guided 3D overview with story panel, sources, controls, and visible Google Maps attribution
The opening view connects the Fox River, bridges, rail corridor, civic spaces, downtown fabric, and Elgin Tower while keeping sources and controls visible.

The opportunity

Turn geographic context into a guided story.

An open 3D map offers freedom but little narrative structure. Visitors can lose orientation, miss the relationship between landmarks, or mistake visual context for authoritative civic data.

What Christian needed to solve

Create a focused exploration that helped people move through downtown context without autoplay, false precision, unsupported history, or dependence on a single map-loading path.

What Christian designed

Four stops, one spatial information model.

The tour moves through Downtown overview, Elgin Tower, Fox River and riverfront, and the civic and transportation core. Each stop carries its own camera, description, contextual annotation, sources, limitations, order, and accessibility label.

How it works

Visitors start the tour, move Previous or Next, choose a stop directly, exit, reset to Downtown, or use optional camera controls. Every transition is user initiated; there is no autoplay, tracking, or unattended navigation.

Contribution

Christian’s role

Christian defined the bounded civic-story objective, approved the source and safety constraints, directed AI-assisted implementation, reviewed camera and interface revisions, authorized a bounded model review, completed the final human review, and accepted the prototype.

AI and tools

Implementation support

AI-assisted development supported story modeling, interface and fallback implementation, test drafting, visual diagnosis, and documentation. A bounded model review evaluated six screenshots; Christian made the final design and acceptance decisions.

Design and technical decisions

Geographic context with visible limits.

Spatial story model

Typed stop records separate content, camera data, source records, context notes, order, and accessibility labels from event handlers.

Context, not authority

Google imagery and geometry are described as contextual, potentially out of date, and not survey-grade.

Map-free fallback

All four stops, descriptions, source links, and disclosures remain available without initializing the Google loader.

Interruptible motion

Camera actions are explicit, Orbit is optional and stoppable, and reduced-motion mode removes animated transition duration.

Evidence and validation

Accepted after implementation and human review.

Validation establishes the prototype’s recorded behavior—not official endorsement, adoption, tourism impact, or geographic authority.

4ordered guided story stops
32tests passed at acceptance
2 modes3D map and map-free story
0experience console errors in review

Build and lint passed. Desktop and mobile presentations, Google attribution, map-free fallback, reduced motion, focus retention, Orbit start/stop, stop-change cancellation, sources, disclosures, and no-overflow behavior were reviewed. VoiceOver was not rerun.

Technologies, by purpose

  • Mapping: Google Maps JavaScript API with the native 3D maps library
  • Experience: HTML, CSS, and JavaScript within an isolated Vite prototype
  • Content and geography: typed story-stop data and bounded OpenStreetMap orientation sources
  • Validation: Vitest, build and lint checks, browser interaction review, responsive screenshots, and human acceptance

Known limitations

Google controls imagery currency, mesh quality, coverage, and renderer behavior. Geometry is contextual, not survey-grade. OpenStreetMap completeness varies. Actual outage, quota exhaustion, broader devices, and VoiceOver were not fully exercised. This is not an official City of Elgin service.

What Christian learned

Spatial interfaces become more trustworthy when camera intent, source provenance, accuracy notes, fallback content, and user control are designed as one system.

What could improve next

Complete a broader assistive-technology and device review, formalize source-license review, and continue testing how each camera composition distinguishes one civic relationship from another.

Discuss the tour with Christian.

Contact Christian