Luftlagebild und Drohnendetektionen - 2025/26

Open data API in a single place

Provided by Hochschule Kempten

Get early access to Luftlagebild und Drohnendetektionen - 2025/26 API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2025.10.09 18:26
Created
2025.10.10
Available languages
English
Keywords
ads-b, flarm, drohnenverkehr, allgair, kempten, drid, luftverkehr
Quality scoring

Dataset description

DE: Die Datensätze enthalten Trajektorien gängiger Transponderdaten aus dem Luft- und Drohnenverkehr. Verwendete Protokolle sind ADS-B, FLARM, DRID und Mode-S. Der Datensatz ist zudem mit Informationen aus Drohnendetektionen angereichert. Positionsdaten wurden, sofern möglich, zusätzlich zu den in den Transponderdaten übermittelten Positionen über Multilateration oder Kreuzpeilung bestimmt. Die Datenerfassung erfolgte im Rahmen des Projekts AllgAir mittels zu diesem Zweck aufgestellter Sensoren im Zeitraum März 2025 bis voraussichtlich März 2026. Neben den ursprünglichen GPS-Koordinaten liegen umgerechnete kartesische Koordinaten (EPSG:5555) sowie Geoid-Höhen (GCG2016/2023) vor. ADS-B, Mode-S und FLARM-Daten wurden analog zum Aircraftlist JSON Service gespeichert – weitere Informationen: https://wiki.jetvision.de/wiki/Radarcape:Software_Features#Aircraftlist_JSON_Service Zusätzlich wurden FLARM-Daten des Open-Glider-Network (OGN) Decoder ARP-S redundant gespeichert, um Signalstärkeninformationen beizufügen: https://github.com/glidernet/ogn-rf DRID- und Drohnendetektionsdaten stammen aus Dedrone.TrackerAI HTTP Push JSON-Datensätzen. Eine öffentliche Schnittstellendokumentation existiert nicht; die hier interpretierten Daten basieren auf den Strukturen, die im File "dronedetection_known_structures.json" dokumentiert sind. Weitere Informationen zum Projekt: https://www.hs-kempten.de/hochschule/aktuelles/artikel/verbesserung-der-sicherheit-im-flugverkehr-2999 EN: The datasets contain trajectories of common transponder data from both manned aviation and drone traffic. The protocols used include ADS-B, FLARM, DRID, and Mode-S. The dataset is further enriched with information from drone detections. Whenever possible, positional data were determined in addition to the positions transmitted via the transponder using multilateration or cross-bearing techniques. Data collection was conducted within the framework of the AllgAir project using sensors specifically deployed for this purpose, from March 2025 to approximately March 2026. In addition to the original GPS coordinates, converted Cartesian coordinates (EPSG:5555) and geoid heights (GCG2016/2023) are provided. ADS-B, Mode-S, and FLARM data were stored in accordance with the Aircraftlist JSON Service – further information: https://wiki.jetvision.de/wiki/Radarcape:Software_Features#Aircraftlist_JSON_Service Additionally, FLARM data from the Open Glider Network (OGN) Decoder ARP-S were stored redundantly to include signal strength information: https://github.com/glidernet/ogn-rf DRID and drone detection data were extracted from Dedrone.TrackerAI HTTP Push JSON datasets. No public API documentation exists; the interpreted data are based on the structures documented in the file "dronedetection_known_structures.json". More information about the project: https://www.hs-kempten.de/hochschule/aktuelles/artikel/verbesserung-der-sicherheit-im-flugverkehr-2999
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks