Capture all six Future City Hackathon 2026 challenges as OKF v0.2 concepts, with dataset and organizer concepts, indexes, and a log. Configure release-please with the simple strategy so the first release PR bumps the repository from 0.0.0 to 0.1.0.
111 lines
6.8 KiB
Markdown
111 lines
6.8 KiB
Markdown
---
|
|
type: Hackathon Challenge
|
|
title: "LoRaWAN network planning: from real-world signals to smarter deployment"
|
|
description: Use real urban LoRaWAN reception data to explain signal quality, predict coverage at new locations, and build a first gateway-planning tool for cities.
|
|
resource: ../../HNVG/readme%20LoRaWAN_Network_Planning_Challenge.docx
|
|
tags: [hackathon, future-city-hackathon-2026, hnvg, lorawan, network-planning, geospatial, prediction, smart-city]
|
|
status: stable
|
|
generated: { by: opencode/deepseek-v4.1-flash, at: 2026-11-13T17:13:56Z }
|
|
sources:
|
|
- id: hnvg-readme
|
|
resource: ../../HNVG/readme%20LoRaWAN_Network_Planning_Challenge.docx
|
|
title: "LoRaWAN Network Planning Challenge — README"
|
|
author: team:hnvg
|
|
- id: hnvg-deck
|
|
resource: ../../HNVG/Pitch%20%20LoRaWAN_Network_Planning_Challenge.pptx
|
|
title: "Smart Cities Need Connectivity — challenge pitch"
|
|
author: team:hnvg
|
|
---
|
|
|
|
# At a glance
|
|
|
|
| Field | Value |
|
|
|---|---|
|
|
| Organizer | [HNVG](/organizers/hnvg.md) |
|
|
| Core question | How can a city make a better first decision about its future LoRaWAN network? |
|
|
| Data | About 600 transmitters, 8 gateways, and real-world reception data from a Heilbronn test area |
|
|
| Tasks | Understand, explore, predict, and plan |
|
|
| Output | A coverage prediction and a prototype that compares candidate gateway locations |
|
|
| Scope | Partial solutions are explicitly welcome |
|
|
|
|
# The problem
|
|
|
|
Smart meters, environmental sensors, mobility, and energy applications all need reliable connectivity. Cities considering a LoRaWAN network face practical questions: How many gateways are needed? Where should they go? What coverage can be expected?[^hnvg-readme]
|
|
|
|
Radio coverage is not a perfect circle around a gateway. Buildings, terrain, height, vegetation, and other characteristics of the urban environment influence whether a signal actually arrives. The challenge is to plan deployments from expected reception quality rather than from a simple radius.[^hnvg-readme]
|
|
|
|
# Your task
|
|
|
|
The brief defines four connected tasks. Teams may go deep in one or more of them.
|
|
|
|
## 1 — Understand
|
|
|
|
Explore the reception data, identify patterns, and develop hypotheses about why some signals are received reliably while others are not.[^hnvg-readme]
|
|
|
|
## 2 — Explore
|
|
|
|
Find and integrate publicly available data that helps explain the patterns. Possible factors include distance and obstacles such as buildings and terrain, radio settings such as spreading factor, bandwidth and transmit power, and interference or network traffic. The brief presents these as examples, not a checklist: find the data you think matters and test whether it actually does.[^hnvg-readme]
|
|
|
|
## 3 — Predict
|
|
|
|
Use what you learned to develop a model or another approach that estimates where LoRaWAN reception is likely to work and where it may become difficult.[^hnvg-readme]
|
|
|
|
## 4 — Plan
|
|
|
|
Turn the insights into a first planning tool for cities. The prototype should let users select and explore different potential gateway locations and assess expected coverage and likely gaps.[^hnvg-readme]
|
|
|
|
# The vision
|
|
|
|
The intended flow is **select an area → explore relevant data → assess potential sites → estimate reception**. The goal is not to replace professional radio planning or field measurements. It is to give a city a useful first answer to "What could a LoRaWAN network look like in our city?" and to make the approach transferable to other cities and regions.[^hnvg-readme]
|
|
|
|
# What you get
|
|
|
|
The challenge package includes six tables. The full schema, row counts, and data-quality notes are in the [HNVG LoRaWAN reception dataset](/data/hnvg-lorawan-reception.md) concept.
|
|
|
|
| File | What it contains |
|
|
|---|---|
|
|
| `transmission_data.csv` | Received uplink messages from water meters, with gateway reception, signal quality, radio settings, and message metadata. |
|
|
| `transmitter meta data.csv` | One row per water meter: meter size, installation date, calibration year, address, and GPS coordinates. |
|
|
| `gateway meta data.csv` | One row per gateway: gateway identifier, display name, latitude, and longitude. |
|
|
| `mapping transmitter id.csv` | Links a device's system ID and name to its water meter number. |
|
|
| `HN_Adresses.csv` | Addresses in Heilbronn with postal code, city, street, and house number, usable for out-of-sample predictions after geocoding. |
|
|
| `potential_gw_location.csv` | Candidate gateway locations with latitude and longitude, usable to compare sites and estimate coverage and redundancy. |
|
|
|
|
## Data caveats worth knowing before modelling
|
|
|
|
- `transmission_data.csv` is semicolon-delimited and uses a period as the decimal separator. Some metadata files use a comma as the decimal separator for coordinates, so normalise before joining.
|
|
- One metadata file is not UTF-8; the supplied copy decodes as Latin-1. Import identifiers as text to preserve leading zeros.
|
|
- Received messages alone do not establish packet-loss rates. A reliable estimate of expected transmissions is needed for that.
|
|
- Preserve separate gateway receptions of the same message when analysing redundancy; do not deduplicate them away.[^hnvg-readme]
|
|
- The README says about 600 transmitters and 8 gateways. The delivered `transmission_data.csv` contains 448 distinct devices and 9 distinct gateway IDs, while the gateway metadata has 8 rows. Check the mismatch before treating either count as ground truth.
|
|
- GPS coordinates in the transmitter metadata are of uncertain quality; the README presumes WGS 84.
|
|
|
|
# Expected deliverables
|
|
|
|
Depending on scope, the brief asks for:[^hnvg-readme]
|
|
|
|
- A working prototype, analysis, or demonstrator.
|
|
- Source code and basic setup instructions.
|
|
- A short explanation of the approach.
|
|
- An overview of additional datasets and sources.
|
|
- Key findings or results.
|
|
- Assumptions and limitations.
|
|
- A short final pitch or demo.
|
|
|
|
# What makes a strong solution
|
|
|
|
- **Smart use of data:** identify useful additional data and show why it matters.
|
|
- **Evidence:** demonstrate that assumptions or the model help explain or predict reception.
|
|
- **Practical value:** help a city make a better first deployment decision.
|
|
- **Usability:** make the result understandable without radio-planning expertise.
|
|
- **Transparency:** make assumptions, limitations, and uncertainty visible.[^hnvg-readme]
|
|
|
|
Partial solutions are welcome. Depth in one part is better than a superficial solution to everything: discovering a valuable public dataset, explaining differences in reception, building a strong coverage model, creating an intuitive visualisation, or building the full planning prototype are all valid contributions.[^hnvg-readme]
|
|
|
|
# Sources
|
|
|
|
The README is the detailed brief and data dictionary.[^hnvg-readme] The pitch deck states the challenge in short form.[^hnvg-deck]
|
|
|
|
[^hnvg-readme]: HNVG, "LoRaWAN Network Planning Challenge — README", challenge brief and data documentation, 2026.
|
|
[^hnvg-deck]: HNVG, "Smart Cities Need Connectivity", challenge pitch deck, 2026.
|