Countculture
Pulse Analytics · Councils & BIDs

City Centre Pedestrian Counting

Footfall evidence for councils and business associations

Show your centre is recovering, prove what events deliver, and put investment where people actually are, with footfall data that councils and members accept.

Built for

City centre managers, BIDs and economic development teams

You need to show that the precinct is recovering, that events pay for themselves and that public money is going where people are, and you need it in a form the council and your members will accept.

A Count Pod enclosure on a city street
Show the precinct is recovering
Week-on-week and year-on-year vibrancy scores for every street and zone.
Measure every event
Footfall before, during and after, against a baseline.
Make the funding case
Reports written for council papers and member updates.
Movement between sites on a cruise day · example Auckland data
What you get

What’s included

  • Precinct-level footfall across streets and zones, with sensors under canopies, on streetlights and signals, painted to match heritage frontages
  • Cruise schedules, event calendars and weather shown as overlays, so a trend can be told apart from a one-off spike
  • Population zones for open spaces, foreshores and events where there is no single gate to count
  • Automated monthly reporting for members, elected officials and the public; open data publishing under Creative Commons if you choose
  • Live API feeds to council planning teams and public portals
  • City Pulse: a daily 0 to 100 score and fourteen-day forecast built on this data
How it works

How a deployment runs

01
Network design

We map your sites, choose Count Pods or CCTV integration per location, and fit each pod with a lens for its mounting height.

02
Install

Solar Count Pods need no mains power or trenching. CCTV integration runs on a lightweight CPU server inside your network.

03
Validate

Our engineering team loads a custom AI model for each site, then calibrates, tunes and ground-truths it against manual counts before go-live. All of it is done remotely.

04
Decide

Pulse Analytics dashboards, automated reports and the REST API put the data where your team already works.

Outcomes

Customer results

↗
Heart of the City
Heart of the City

Auckland CBD since 2011: one of the longest-running computer vision counting programmes in the region

A growing sensor network across the centre, live on hotcity.co.nz and open under Creative Commons since 2012. Evidence of 14 times more pedestrians than vehicles on High Street drove its upgrade under Access for Everyone and a Living Streets Aotearoa award.

↗
Dunedin City Council
Dunedin City Council

George Street: 14 sensors through a NZ$100m upgrade

For three years the scene changed every week as scaffolding, hoardings and machinery moved through, and the system kept counting without retraining or gaps. “Making sure that we're doing that in the same way all of the time, so we establish a comparable set of data.” Glen Hazelton, Dunedin City Council

↗
City of Sydney
City of Sydney

Oxford Street: pedestrian and micromobility data through a cycleway trial

A trial with the Oxford Street business community gave the City continuous pedestrian and micromobility data on one of its busiest retail streets.

Christchurch City Council logo
City of Parramatta logo
City of Darwin logo
Heart of the City logo
City of Sydney logo
City Pulse · For councils and city agencies

The city centre, measured.

Pulse Analytics for Cities is the counting and reporting. City Pulse is a daily 0 to 100 score with a fourteen-day forecast, built on top of it and calibrated on your city's own record. If we can't measure something, the platform says so.

City Pulse index
Example
63
OF 100 · BASELINE 65
BASE
65
SEASON
−6
EVENTS
+4
CRUISE
0
A modelled 0 to 100 read of city-centre activity, where an average day sits at 65.
How it works

One score, with the working shown

The Pulse score reads the city centre from 0 to 100, today and fourteen days ahead. It is built from factors measured on the city’s own history: the seasonal rhythm, the shape of each weekday, public holidays, events tiered by venue, and cruise ships by passenger count. Open any score and it shows its working, factor by factor. If a score looks wrong, the breakdown shows which factor moved it.

Pulse · 2
City Pulse score
Fourteen-day forecast
Movement · 8
Sensor map
Sensor breakdown
Precinct performance
Precinct profile
Transport
Construction alerts
Cruise schedule
Linkage lab
Economy · 5
Business intelligence
Venue churn
Trading opportunity
Spend intelligence
Visitor intelligence
Safety & policy · 4
Crime and safety
Policy evidence
Activation ROI
Project impact
Calibration

Calibrated on your city’s own history

Every factor in the score is measured on years of your city’s own counts, using matched-day comparisons and control streets. The result is a measured answer to the questions that come up in committee: what an event delivered, what a major visitor draw is worth, and how much of a change is real.

Events, measured
Your event history
Uplift by venue size

Each event’s lift is calibrated against your city’s own event record, with day and night events treated separately, so the next one can be forecast and judged fairly.

Visitor drivers
Matched days
What a major draw is worth

Conferences, stadium days, festivals or cruise calls: whatever brings people into your centre is measured against comparable days and a control street, so the lift you report is real.

Findings
Evidence over instinct
Results people don’t expect

Calibration regularly shows that the days and drivers people assume matter most are not the ones moving the numbers. That is the evidence a council can take into a funding decision.

Data quality

How we catch our own errors

One view was about to report 325 business openings in a single month. The platform held the figure back because it detected that its data coverage had changed, not the number of businesses.

Provenance on the face of the platform

Every figure carries what it comes from and how it was measured.

Degraded feeds are declared

When a feed degrades, the platform says so instead of papering over it.

Forecast marked against reality

Scored against counted reality on the platform itself, error rate published.

Around 100 automated data checks

Run on every release, so a code change can’t start overstating results unnoticed.

See Pulse Analytics on your own sites.

Book a demo