StoryMaps

ArcGIS StoryMaps combines maps, text, photographs, video and other media into a guided web story. For Māori GIS work it is most useful as a communication layer: the analysis and source data can stay in your GIS, while the StoryMap presents an approved version to whānau, trustees, partners or the public.

Official StoryMaps site: https://storymaps.arcgis.com/

Start with examples

The Matawhenua: Tirohanga 3D Māori GIS ki te Whakapapa collection contains practical examples designed for Māori GIS learning. Open the example closest to your kaupapa before building your own.

Example	What it demonstrates	Useful for
Creating 3D Flythroughs for Cultural Narratives	Sidecar, 3D scene and place-to-place movement	rohe, whenua, historical journeys, restoration projects
Whenua Māori 3D Flythrough	A finished simple 3D fly-through	seeing what a short 3D narrative can look like
Applications of Imagery for kaupapa Māori GIS mapping	Swipe comparisons, current and historic imagery, examples around Aotearoa	change over time, hazards, heritage, environmental monitoring
Ngā Kōrero o Te Whenua He Tirohanga 3D	Imagery sources and 3D storytelling	finding imagery and building place-based visual narratives
Te Whakapapa o ngā Awa	Freshwater data, catchments, monitoring and a 3D scene	awa, wai quality, restoration and catchment kaupapa
Accessing Council GIS Maps, and data	Linking narrative guidance to council viewers and data sources	teaching people how to find and use local GIS information
Matawhenua GIS Mapping	Long-form practical guide, downloads and GIS setup	training, reference material and an offline GIS kete
Ngā Raraunga mō ngā Kaupapa Māori GIS Mahere	A large collection of GIS data sources	data discovery and learning where information comes from

These examples show different ways of using StoryMaps. They are not templates that need to be copied exactly.

The 2026 wānanga

The 19 June 2026 Ngā Poutama Matawhenua session Kōrero ā-Mahere: 3D StoryMaps for Kaupapa Māori GIS Mapping covers StoryMaps, 3D fly-throughs, imagery, swipe maps, map tours and sidecars.

• Open the current LINZ recording/resource link
• Read the short site article
• See all Ngā Poutama videos and StoryMaps

Where StoryMaps fits

A useful architecture is:

1. source data is stored and managed in the appropriate GIS, database or controlled file store
2. restricted information stays in that controlled source
3. an approved view or derived layer is created for the intended audience
4. a web map uses only the information approved for that audience
5. the StoryMap presents the web map with narrative, images and context

This separates the system of record from the public or partner presentation.

Good uses

StoryMaps works particularly well for:

• explaining a kaupapa to governance or funders
• showing environmental restoration and monitoring outcomes
• presenting change over time using current and historical imagery
• creating a guided journey through several places
• explaining a catchment, coastline or rohe without requiring the reader to operate GIS software
• combining maps with photographs, archival material and short narrative
• documenting a project method or training workflow
• publishing a curated resource guide such as a set of data links

It is less suitable as the place where authoritative working data is maintained.

Decide the audience first

Before opening the builder, write down:

• who the story is for
• what the reader needs to understand or do
• what information must remain restricted
• who approves publication
• whether precise locations are necessary
• whether the story should be publicly searchable

A StoryMap intended for a small governance group can contain more detail than a public story indexed by search engines. Build for the intended audience rather than trying to make one story serve everyone.

Keep sensitive data out of the presentation layer

A public StoryMap should not be the first place where you decide whether information is sensitive.

For restricted or culturally sensitive data:

• maintain the source layer privately
• create a separate view or derived layer for publication
• remove fields that the audience does not need
• generalise locations where exact geometry is unnecessary
• check attachments, related records and popups
• avoid identifiers that allow a public layer to be linked back to a restricted register

In ArcGIS Online, hosted feature layer views can help expose only the fields and features intended for an audience:

https://doc.arcgis.com/en/arcgis-online/manage-data/create-hosted-views.htm

Choose the StoryMap technique that fits

Sidecar and 3D scene

Use a sidecar when the reader should move through a sequence of places while the map or scene changes.

The 3D flythrough tutorial demonstrates this pattern. It can work for:

• a sequence of important places
• a restoration programme moving down an awa
• a historical journey
• several whenua blocks or project sites
• changes along a coastline

Keep each stop short. The map should do part of the explanation.

Swipe

Use swipe when the main point is comparison.

The imagery StoryMap demonstrates comparisons between historical and recent imagery. Useful applications include:

• coastal retreat
• river movement
• forestry change
• urban expansion
• restoration before and after works
• disaster impacts

Always show or state the dates of the two images being compared.

Map tour

Use a map tour when each location has a photograph, short description or other media. This is useful where sequence is less important than exploring a set of places.

Long-form reference story

A StoryMap can also behave more like a practical guide. Matawhenua GIS Mapping combines instructions, downloads, data descriptions and examples in one resource.

For a long guide, provide strong headings and keep the most common tasks near the top. Readers should not have to scroll through the whole story to find a download or core instruction.

Freshwater example

Te Whakapapa o ngā Awa demonstrates how a StoryMap can act as both a resource directory and a practical freshwater mapping example.

It brings together:

• river and catchment information
• monitoring and water-quality resources
• examples of field data
• a simple 3D scene
• links to external datasets and tools

For an iwi or hapū project, the public StoryMap might show the catchment, monitoring approach and approved summary results while the detailed field observations remain in a controlled dataset.

Imagery example

Applications of Imagery for kaupapa Māori GIS mapping demonstrates how one resource can use examples from different parts of Aotearoa to teach a method rather than tell one local story.

That approach works well for training. Each example can demonstrate one technique such as:

• comparing two dates
• interpreting a historic aerial photograph
• showing environmental change
• using imagery after a natural hazard
• exploring a location in 3D

See Retrolens and historical imagery workflows for the underlying imagery workflow.

Data-discovery example

The 2026 council GIS StoryMap demonstrates another valuable use of StoryMaps: teaching people where to find information.

Instead of republishing council datasets, the story explains the pathway to the source. This is useful because council data and service URLs change. The narrative can explain what to look for while the authoritative provider remains responsible for the current dataset.

See NZ data sources for the wider data workflow.

Build a simple story

A practical first StoryMap can be built in six steps.

1. Write a one-sentence purpose and identify the audience.
2. Prepare one safe web map containing only the layers needed for the story.
3. Add a short introduction explaining the kaupapa and what the reader will see.
4. Add one StoryMap technique such as sidecar, swipe or map tour.
5. Add sources, dates and limitations alongside the relevant map or image.
6. Test the complete story logged out before publishing it publicly.

Do not begin with a 30-section story. A short complete story is easier to review and maintain.

Sharing review

Before publication, check each linked ArcGIS item separately:

• StoryMap sharing
• web map sharing
• feature and imagery layer sharing
• view layer versus source layer
• popup fields
• attachments
• editing settings
• download and export permissions

A public StoryMap can fail because a required layer is private. It can also expose more than intended because an underlying layer was made public unnecessarily.

ArcGIS Online sharing guidance:

• https://doc.arcgis.com/en/arcgis-online/share-maps/share-items.htm
• https://doc.arcgis.com/en/arcgis-online/share-maps/overview-of-sharing.htm

Accessibility and readability

Before publishing:

• add useful alternative text to important images
• use a clear heading structure
• keep paragraphs short enough for web reading
• avoid putting essential information only inside an image
• use readable colour contrast
• provide captions where dates or sources matter
• test maps and media on a phone as well as a desktop

Esri accessibility information:

https://www.esri.com/en-us/about/accessibility/overview

Metadata and maintenance

A StoryMap can remain online long after its creator moves on. Record enough information for someone else to maintain it.

Useful details include:

• owner or responsible role
• audience
• publication approval
• source datasets
• last checked date
• links to the underlying maps and layers
• sensitivity or tikanga notes
• expected review cycle

For stories that link to external datasets, review links periodically. A broken external link is easier to fix when the page records the source organisation and dataset name as well as the URL.

More examples

• Matawhenua StoryMaps collection
• Ngā Poutama Matawhenua videos and StoryMaps
• Whenua
• Retrolens and historical imagery workflows
• NZ data sources

StoryMaps resources:

https://www.esri.com/en-us/arcgis/products/arcgis-storymaps/resources

Last reviewed: 26 August 2026