Spatial interface thinking
The project demonstrates an interest in map-based presentation and location-aware exploration.
Project case study
NZ Change Map Case Study
An archived New Zealand public-data map prototype showing mapping interface work, data-presentation thinking, and practical project documentation.
Project snapshot
Public data made easier to explore
NZ Change Map is an archived John Finnerty web project. It is positioned as an interactive public-data map prototype for New Zealand, with source archive history and metadata for mapping, geospatial work, data visualization, Python, SQLite, and public data.
Public source archive
Archived project notes
Public-data mapping
New Zealand context
Mapping and data problem
Turn scattered information into something navigable
Maps can make public information easier to inspect, compare, and revisit. NZ Change Map is useful portfolio evidence because it frames data as an interactive experience rather than a static table or article.
Source-aware framing
The case study keeps claims close to public evidence and leaves source-pipeline details as an evidence gap until they are documented.
Prototype delivery
A source archive and archived project-history page keep the project inspectable without presenting the old map demo as current.
Technical signals
What the project demonstrates
The useful evidence is the public source archive history and metadata: an archived map-facing project record and topics that connect the work to geospatial data, visualization, Python, SQLite, and New Zealand public-data context.
Data visualization
The project supports a clear case-study narrative around making data easier to scan and interpret visually.
Geospatial project framing
source archive metadata links the project to maps, geospatial work, public data, Python, and SQLite.
Static deployment
The historical GitHub Pages URL now serves NZ Live Radio, with project-history links back to these archived NZ Change Map notes.
Capability evidence
Skills reflected by the project
NZ Change Map supports a professional profile around data-aware web tools, public-data presentation, static deployment, and careful project documentation.
Maps
Geospatial data
Data visualization
Public data
Python
SQLite
Archived project history
New Zealand context
Evidence links
Project note references
These are the current public references for the archived project. The historical GitHub Pages URL now serves NZ Live Radio and is linked here only as source archive history. The original map demo is retired. This case study does not claim source completeness, official status, audience numbers, client outcomes, awards, or uptake.
Historical project URL
Current NZ Live Radio page with links back to archived NZ Change Map project notes.
NZ Live Radio case study
Current owned case study describing the NZ Live Radio directory experiment and its boundaries.
Source archive
Public source archive preserving NZ Change Map history and later NZ Live Radio work.
Short project profile
Concise finnerty.me page linking archived project notes, source archive history, and this case study.
Project hub
More software and project notes by John Finnerty.
Related project context
Connected project-note work
The closest related pages are the NZ Political Promise Tracker, for source-aware civic data framing, and Cookr, for a product-style web application example.
NZ Political Promise Tracker
Private civic-data prototype using source evidence.
Cookr
Mobile-first cooking assistant case study.
About John Finnerty
Current professional profile and project note context.
John Finnerty New Zealand
Current New Zealand profile connecting public-data projects, technical consulting, and owned evidence.
Project proof loop
Keep this case study connected to the wider proof system
This project page is part of a public evidence loop: source archive metadata, project references, case-study notes, project hub links, and maintenance checklists should tell the same careful status story.
Project proof system
How the project hub connects source archives, project pages, case studies, and profile evidence.
public source archive proof path
Reading path for source archive metadata, project pages, canonical URLs, screenshots, and public profile links.
Project SEO checklist
Checklist for README links, homepage fields, titles, canonicals, schema, and project evidence.
Technical SEO audit checklist
Audit path for crawlability, structured data, internal links, and search-visible proof signals.
Local launch tool
Practical checklist for publishing small static sites, proof pages, analytics, and handover notes.
Public build note generator
Tool notes for turning project changes into clear public build updates without overclaiming.
More current project-note evidence