feat: add Schwarz Digits challenge website and data access
Capture the FCH26 challenge site: hero framing, three use cases, sensor-data and SKE access links, Vue.js/Go and Onyx details, and the STACKIT DNS guide. Add a PAX counter dataset concept with the published download password.
This commit is contained in:
1 parent
c02d2ea621
commit
48ffb5ba08
6 files changed
+124
-14
No files matched your search
@@ -1,12 +1,17 @@
|
||||
---
|
||||
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.
|
||||
description: Build a production-ready application on STACKIT that turns privacy-preserving pedestrian counts from Heilbronn into predictive tooling 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 }
|
||||
generated: { by: opencode/deepseek-v4.1-flash, at: 2026-11-13T17:34:32Z }
|
||||
sources:
|
||||
- id: challenge-site
|
||||
resource: http://challenge-digits.fch26.stackit.run/
|
||||
title: "FCH26 — Pulse of a City: Heilbronn challenge website"
|
||||
author: team:schwarz-digits
|
||||
last_modified: 2026-11-13T15:48:33Z
|
||||
- id: pulse-brief
|
||||
resource: ../../Schwarz%20Digits/FCH%20Challenge%20The%20_Pulse%20of%20the%20City_.pdf
|
||||
title: "The Pulse of the City — challenge brief"
|
||||
@@ -22,13 +27,28 @@ sources:
|
||||
| Field | Value |
|
||||
|---|---|
|
||||
| Organizer | [Schwarz Digits](/organizers/schwarz-digits.md) |
|
||||
| Website | http://challenge-digits.fch26.stackit.run/ |
|
||||
| Data | Numbers of people measured in a given area by sensors in Heilbronn's inner city (PAX counters) |
|
||||
| Data access | [Get Sensor Data](https://file4you.schwarz/download.xhtml?id=e7205b9e3ee64a58b795d2e9d535fbce) — password `fch26digits` |
|
||||
| SKE access | [Request SKE Access](https://forms.gle/hcBsHjozDSGbcXUt7) |
|
||||
| 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 |
|
||||
| Bonus | Vue.js + 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 |
|
||||
|
||||
# Challenge website
|
||||
|
||||
The official challenge page is http://challenge-digits.fch26.stackit.run/. It frames the task as **"Decode the Pulse of Heilbronn"**: "Leverage inner-city sensor data measuring pedestrian density to build predictive tooling. Help local businesses optimize operations based on the ebb and flow of foot traffic."[^challenge-site]
|
||||
|
||||
It provides:
|
||||
|
||||
- **Get Sensor Data** — a download link for the inner-city sensor data, protected by the password `fch26digits` printed on the page.
|
||||
- **Request SKE Access** — the form for STACKIT Kubernetes Engine access from the mentors.
|
||||
- The three use cases, requirements, bonus points, and the STACKIT DNS guide summarised on this page.
|
||||
|
||||
The page is titled "FCH26 - Pulse of a City: Heilbronn" and is powered by STACKIT and Schwarz Digits.[^challenge-site]
|
||||
|
||||
# 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]
|
||||
@@ -43,7 +63,7 @@ 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.
|
||||
- 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**; download it from the [challenge website](http://challenge-digits.fch26.stackit.run/) with the password published there. See [Schwarz Digits PAX counter data](/data/schwarz-digits-pax-counter-data.md).
|
||||
|
||||
# Your task
|
||||
|
||||
@@ -51,19 +71,34 @@ Schwarz Digits wants tooling that helps optimize **advertisement placements, sto
|
||||
|
||||
## 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]
|
||||
Both the deck and the challenge website make deployment a requirement. The deck asks for a **production-ready application that is already deployed to the provided STACKIT infrastructure**.[^digits-deck] The website calls this **Production Ready on SKE**: "We want to see your application fully deployed. Get access to the STACKIT Kubernetes Engine (SKE) from our mentors and host your solution on enterprise-grade infrastructure."[^challenge-site]
|
||||
|
||||
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.
|
||||
Request access with the [SKE access form](https://forms.gle/hcBsHjozDSGbcXUt7). 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]
|
||||
- **The Digits Tech Stack:** use **Vue.js** for the frontend and **Go** for backend services. This is the stack Schwarz Digits highly encourages.[^challenge-site]
|
||||
- **Onyx Component Library:** design the UI with the official open-source design system. Documentation, components, and design tokens are at https://onyx.schwarz/.[^challenge-site]
|
||||
|
||||
# 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]
|
||||
|
||||
# Hints and resources
|
||||
|
||||
- **STACKIT DNS configuration:** to expose the application to the web automatically, use the external-dns extension with the Kubernetes cluster. See the [STACKIT DNS guide](https://docs.stackit.cloud/products/runtime/kubernetes-engine/how-tos/use-the-stackit-dns-extension-with-your-cluster/#example).[^challenge-site]
|
||||
- **Footer links:** the challenge page also lists Rules & Guidelines, Data Privacy, and Contact Mentors. At capture time these point to `#`, so contact the mentors directly.
|
||||
|
||||
# Use cases
|
||||
|
||||
The challenge website names three primary use cases:[^challenge-site]
|
||||
|
||||
| Use case | What it means |
|
||||
|---|---|
|
||||
| Targeted Advertising | Analyze pedestrian volume and movement patterns to pinpoint the most lucrative locations and timeframes for physical advertisement placements in the city center. |
|
||||
| Strategic Store Locations | Use foot traffic estimations to identify high-potential commercial zones. Empower retailers to choose new storefront locations backed by real urban mobility data. |
|
||||
| Dynamic Staffing | Predict peak customer hours by modeling the number of people walking by. Enable store managers to align their staff schedules with actual street-level demand. |
|
||||
|
||||
# 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.
|
||||
@@ -86,13 +121,14 @@ The core idea is to turn estimated customer counts into better decisions about a
|
||||
|
||||
# Open questions
|
||||
|
||||
- What spatial granularity and time range does the PAX dataset cover? The brief describes the source but not the exact schema.
|
||||
- What spatial granularity and time range does the PAX dataset cover? The challenge site provides the download; inspect the delivered files for the schema and coverage.
|
||||
- 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]
|
||||
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] The challenge website is the source for the current data-access and SKE links, the three website use cases, the Vue.js/Go and Onyx wording, and the STACKIT DNS guide.[^challenge-site]
|
||||
|
||||
[^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.
|
||||
[^challenge-site]: Schwarz Digits, "FCH26 - Pulse of a City: Heilbronn" challenge website, http://challenge-digits.fch26.stackit.run/, accessed 2026-11-13.
|
||||
Reference in new issue
Block a user