Updated

ttn-zurich-data

API Access

Access dataset files directly from scripts, code, or AI agents.

Browse dataset files
Dataset Files

Each file has a stable URL (r-link) that you can use directly in scripts, apps, or AI agents. These URLs are permanent and safe to hardcode.

/loleg/ttn-zurich-data/
https://datahub.io/loleg/ttn-zurich-data/_r/-/README.md
Key Files

Start with these files — they give you everything you need to understand and access the dataset.

README.mddocumentation
https://datahub.io/loleg/ttn-zurich-data/_r/-/README.md
Typical Usage
  1. 1. Download data resources listed in the metadata file
  2. 2. Read README.md for full context

Data Views

Data Previews

Gateways map

Gateways data

Loading data...

Schema

nametypeformat
device_idintegerdefault
eui_idstringdefault
platformstringdefault
categorystringdefault
latnumberdefault
lngnumberdefault
altitudenumberdefault
ETH_distnumberdefault

Sample data (preview)

Loading data...

Schema

nametypeformat
idintegerdefault
device_idintegerdefault
last_onlinestringdefault
rx_oknumberdefault
tx_innumberdefault
measured_atstringdefault

Sample data (compressed)

Unsupported data preview format `zip`

Data Files

FileDescriptionSizeLast modifiedDownload
ttn_gateways_geojson
40.1 kB
ttn_gateways_geojson
ttn_gateways
12.1 kB
ttn_gateways
ttn_measurements_preview
6.25 kB
ttn_measurements_preview
ttn_measurements
8.61 MB
ttn_measurements
FilesSizeFormatCreatedUpdatedLicenseSource
48.67 MBgeojson, csv, zipalmost 2 years ago

DataHub packaged badge

Data from The Things Network (TTN) gateways in Zürich, collected as part of ongoing research and originally provided by Benedikt Hitz-Gamper (Institute of Information Systems, University of Bern) for the TWIST 2018 hackathon. Uploaded by @gnz and reformatted by @loleg as Geospatial Data Package for publication at DataHub.io

Data files

File ttn_gateways.csv (134 rows)

  • device_id: unique key for device_id in table ttn_measurements (this is an internal key, not connected with TTN IDs)
  • eui_id: id used by TTN to uniquely identify gateways
  • platform: make/model of gateway if provided
  • category: clustered value for platform
  • lat/lng: location of gateway if provided
  • altitude: altitute of gateway if provided
  • ETH_dist: distance from gateway to ETH main building (selection criteria for gateways is < 20km)

File ttn_measurements.csv (750926 rows)

(Distributed as ZIP-compressed file, with .preview file available)

  • id: unique id
  • device_id: key for device_id in table ttn_gateways
  • last_online: last handshake of gateway with TTN backend
  • rx_ok: number of packets received by this gateway (counter is never reset)
  • tx_in: number of packets sent by this gateway (counter is never reset)
  • measured_at: time of measurement

To decide whether a gateway is online, verify the difference of measured_at - last_online. If difference is smaller than 30 to 90 seconds, the gateway was online at this time.

Note: Somethimes last_online is greater than measured_at, this has to do with the fact that the values get actually stored in the database after measured_at and sometimes even a newer last_online is available.

Credit

Data part of ongoing research, provided by Benedikt Hitz-Gamper, Institute of Information Systems, University of Bern, benedikt.hitz@iwi.unibe.ch

License

The content in this repository is licensed under the CC-BY-SA 4.0 License (see the LICENSE file for details) unless stated otherwise.

License: CC BY-SA 4.0