How to Build a 3D Story Map, and When to Use ArcGIS StoryMaps
How to plan and build an interactive 3D story map: chapters, camera moves, building data, performance and mobile, with open-source tools or ArcGIS StoryMaps.
By Ahsan Mukhtar, CEO and Managing Director
Key takeaways
- Write the story before touching the map; each chapter needs one point and one camera view.
- Keep the text, the map and the numbers in sync, so readers trust what they see.
- Use ArcGIS StoryMaps to configure quickly, and a custom build when you need 3D, large data or full design control.
A story map combines a map with a narrative told in chapters. As the reader moves from one chapter to the next, the text, the camera and the data on the map change together. Done well, it explains a place, a plan or a change in a way that neither a report nor a plain map can. A 3D story map adds height, which matters whenever the story is about buildings, skylines, terrain or growth.
See two examples: the Dublin Story Map raises 13,666 buildings in Dublin city centre and tells the city's story in eight chapters, from the medieval city to Silicon Docks. Manhattan in Layers shows all 45,195 buildings in Manhattan with a time slider from 1800 to today.
1. Start with the story, not the map
Before choosing any software, write the story as a short outline:
- Who is it for? Residents, investors, council members and tourists need different stories.
- What should they understand at the end? One sentence.
- Which chapters get them there? Usually five to ten, each with one point.
For each chapter, note the place it shows, the camera view (overhead or tilted, near or far), the data on the map and the one fact the reader should take away. This outline becomes the specification for the build.
2. Choose the platform
| ArcGIS StoryMaps | Custom web story map | |
|---|---|---|
| Built by | Configuring templates | Writing code on open-source libraries |
| 3D | Supported through ArcGIS scenes | Full control with deck.gl, MapLibre, CesiumJS or three.js |
| Large datasets | Limited by the hosted layers and licence | Limited mainly by how the data is prepared |
| Design | Within the template's options | Anything your brand needs |
| Best for | Teams already on ArcGIS who want speed | Bespoke stories, big data, 3D and full branding |
ArcGIS StoryMaps is a good choice for organisations with ArcGIS licences and a story that fits its templates. A custom build makes sense when the story depends on 3D, on tens of thousands of features, on a dashboard that responds to the map, or on a design that has to match a brand. Our comparison of ArcGIS alternatives covers the wider platform choice.
Common open-source building blocks are:
- MapLibre GL JS for vector maps and extruded buildings
- deck.gl for large datasets and 3D layers on the GPU
- CesiumJS for globes, terrain and 3D Tiles
- three.js for fully custom 3D scenes
- Scrollama or a similar library for scroll-driven chapters
3. Prepare the data
Most 3D city stories start with building footprints and heights:
- Open city data, where available, such as NYC's building footprints and tax lots behind Manhattan in Layers
- OpenStreetMap, which has footprints almost everywhere and heights or storey counts for many buildings
- LiDAR or city 3D models where accurate heights matter
Fill missing heights carefully: estimate them from building type or storey count, and say so on the map. Then trim the data to what the story uses, and pack it into a compact file. A story that loads in two seconds gets read; one that loads in twenty does not.
4. Design the chapters and camera moves
Each chapter defines a camera position (centre, zoom, tilt and rotation) and what the map shows. Smooth flights between chapters help readers keep their bearings. A few rules help:
- move the camera less than you think, and never make readers dizzy
- change one thing at a time: the place, or the data, not both at once
- highlight what the text mentions, and fade the rest
- offer a play button for a guided tour, and let readers explore freely at any point
5. Keep the text, map and numbers in sync
The strongest story maps let readers check the claims. A small dashboard that counts what is on screen, such as buildings in view, the tallest one or a breakdown by use, turns a pretty map into evidence. When the text says "most buildings here are under four storeys", the chart beside it should show exactly that.
6. Make it work on phones and for everyone
- On small screens, stack the text over the map and keep chapters short.
- Respect the reduced-motion setting: cut camera flights to quick fades.
- Provide the key facts as text, so the story still works for screen readers and for search engines.
- Add a data table or download for readers who want the numbers.
7. Publish and measure
Host the story on your own website so it builds your audience, not a platform's. Track how far readers get through the chapters; a big drop at one chapter usually means it is too long or unclear.
A short checklist
- One-sentence goal and a chapter outline before any build
- Platform chosen for the story's needs, not by habit
- Data trimmed, packed and with honest notes on estimates
- Gentle camera moves, one change per chapter
- Dashboard or numbers that match the text
- Mobile layout, reduced motion and a text alternative
Summary
A good 3D story map is a good story first: a clear audience, a single message and chapters that each make one point. Pick ArcGIS StoryMaps when configuration is enough, and a custom build on open-source tools when you need 3D, large data or full design control. To see what a custom build can do, open the Dublin Story Map, Manhattan in Layers or our 3D City Map of a Helsinki bus route.
References and further reading
Working on something similar? Jugrafiya builds GIS products, spatial data pipelines and the web and mobile software around them.
Talk to an engineer