Files
OKF_Vault/knowledge/challenges/schwarz-digits-pulse-of-the-city.md
T
Noel Sabia af985e1bd9 docs: add complete Schwarz Digits STACKIT and use-case details
Capture the advertising, store-location, staffing, customer-estimation, STACKIT Kubernetes Engine, Vue/Go, and Onyx requirements from the challenge deck. Document the example heat-map and time-series views.
2026-11-13 18:25:31 +01:00

99 lines
7.5 KiB
Markdown

---
type: Hackathon Challenge
title: "Pulse of the City: turning footfall data into decisions"
description: Build a production-ready application on STACKIT that turns privacy-preserving pedestrian counts from Heilbronn into an interactive tool for advertising, store, staffing, and planning decisions.
resource: ../../Schwarz%20Digits/FCH%20Challenge%20The%20_Pulse%20of%20the%20City_.pdf
tags: [hackathon, future-city-hackathon-2026, schwarz-digits, footfall, pax-counter, smart-city, visualization, prediction, stackit, retail, advertising, staffing]
status: stable
generated: { by: opencode/deepseek-v4.1-flash, at: 2026-11-13T17:25:08Z }
sources:
- id: pulse-brief
resource: ../../Schwarz%20Digits/FCH%20Challenge%20The%20_Pulse%20of%20the%20City_.pdf
title: "The Pulse of the City — challenge brief"
author: team:schwarz-digits
- id: digits-deck
resource: ../../Schwarz%20Digits/Challange%20Schwarz%20Digits.pdf
title: "Pulse of a City — Schwarz Digits challenge deck"
author: team:schwarz-digits
---
# At a glance
| Field | Value |
|---|---|
| Organizer | [Schwarz Digits](/organizers/schwarz-digits.md) |
| Data | Numbers of people measured in a given area by sensors in Heilbronn's inner city (PAX counters) |
| Output | A production-ready application, already deployed to the provided STACKIT infrastructure |
| Primary decisions | Advertisement placements, store locations, and staffing |
| Bonus | Vue and Go, plus the Onyx component library |
| Users | Retail store managers, waste planners, and the City of Heilbronn |
| Stretch goal | Estimations and predictions, not only historical visualisation |
# The problem
Cities and retailers want to know how many people walk down a street, but raw sensor counts are just numbers. Store managers and city planners struggle to visualise those counts alongside contextual factors such as weather or holidays. Without an intuitive way to analyse past crowds, opportunities for efficiency are lost.[^pulse-brief]
The true value is not only crunching numbers. It is proving that a team can take raw, privacy-preserving sensor data, fuse it with real-world context, and turn it into an intuitive visual story. A predictive model is the extra step that turns hindsight into foresight.[^pulse-brief]
# The data
The challenge deck describes the dataset as **numbers of people measured in a given area**, collected using sensors in the Heilbronn inner city.[^digits-deck] The core dataset is provided by **Code for Heilbronn** and captured through a network of LoRa-based PAX counters deployed across the city. The sensors estimate crowd density by passively sniffing Bluetooth signals (MAC address advertisements) from nearby smartphones and smartwatches, then transmit aggregated device counts over a low-power LoRaWAN network in near real time.[^pulse-brief]
Important properties:
- The counts are **estimates**, not a census. Not everyone carries a device with Bluetooth enabled, so normalisation and critical interpretation matter.
- The sensors are described as **privacy-preserving** because they count aggregated devices rather than identify people.
- The brief advises the organizer to provide the data as clean CSV or JSON with clear geographic coordinates for each sensor. The dataset is **not stored in this repository**; teams receive it through the organizer.
# Your task
Schwarz Digits wants tooling that helps optimize **advertisement placements, store locations, or staffing** based on estimations about the numbers of customers walking by.[^digits-deck] More broadly, build an interactive tool that helps different parties get insights from the data for planning, reviewing, and optimizing events, stores, and maintenance. Moving from plain numbers to estimations and predictions is explicitly called out as extra cool.[^pulse-brief]
## Delivery on STACKIT
The deck states the delivery expectation directly: Schwarz Digits would love to see a **production-ready application that is already deployed to the provided STACKIT infrastructure**. To get access to the **STACKIT Kubernetes Engine**, talk to the organizer.[^digits-deck]
This is a deployment requirement, not only a technology preference: the application should run on the provided infrastructure rather than only on a laptop or a public demo host.
## Bonus points
- Use **Vue** and **Go**, the stack Schwarz Digits uses for most of its modern applications.
- Use the **Onyx** component library at https://onyx.schwarz/.[^digits-deck]
# Example views
The challenge slide illustrates the intended output with two views: a **heat map over a map of Heilbronn** and a **multi-line time-series chart** whose vertical axis runs from 0 to 140. These are illustrative examples, not a fixed specification, but they show the kind of exploration Schwarz Digits expects: where people are, and how the counts change over time.[^digits-deck]
# Who uses it
The core idea is to turn estimated customer counts into better decisions about advertisement placements, store locations, and staffing. The brief describes three concrete user groups. They are useful as design targets, not as a required feature list.
| User | Use case |
|---|---|
| Lidl / Kaufland | Store managers visually identify when and why foot traffic spiked, then optimize staffing schedules. With predictions, they can adjust baking times for fresh bread or push localized app discounts. |
| PreZero | Planners analyse historical heatmaps to redraw waste collection routes around proven high-traffic zones. With predictions, they can move to dynamic routing, for example scheduling a targeted Sunday morning collection before bins overflow after a forecast sunny Saturday at the Neckarufer. |
| City of Heilbronn | Integrate the tool into a public Smart City Dashboard so citizens can see how busy areas typically are. Predictions can help manage dynamic street lighting, route traffic during major events, or place temporary infrastructure. |
# What makes a strong solution
- **Fuse data with context.** Combine footfall counts with weather, holidays, events, or other real-world signals that explain the patterns.
- **Connect estimates to decisions.** Show how an estimated customer count changes an advertising placement, a store-location choice, or a staffing plan.
- **Tell a visual story.** The result should be intuitive, not a table of aggregated numbers.
- **Make it usable.** A store manager or city planner should be able to move from the overall picture to a specific street, time, or event.
- **Ship it on STACKIT.** The application should be deployed to the provided infrastructure, not only run locally.
- **Respect privacy.** Work with aggregated counts and avoid exposing personal information.
- **Go beyond hindsight.** A predictive or estimation layer is the differentiator.
# Open questions
- What spatial granularity and time range does the PAX dataset cover? The brief describes the source but not the exact schema.
- How should device penetration bias be corrected or at least disclosed?
- What does "production ready" mean for authentication, operations, and data refresh in the time available?
# Sources
The challenge brief contains the data description, use cases, and advice.[^pulse-brief] The Schwarz Digits deck contains the advertising, store-location, and staffing framing, the example heat map and time-series view, the STACKIT deployment requirement, and the technology bonus.[^digits-deck]
[^pulse-brief]: Schwarz Digits / Code for Heilbronn, "The Pulse of the City", challenge brief, 2026.
[^digits-deck]: Schwarz Digits, "Pulse of a City — Challenge Future City Hackathon 2026", challenge deck, 2026.