DOI: 10.5281/zenodo.3342253
title: Sigfox and LoRaWAN Datasets for Fingerprint Localization in Large Urban and Rural Areas

description: <strong>INTRODUCTION</strong> The goal of these LPWAN datasets is to provide the global research community with a benchmark tool to evaluate fingerprint localization algorithms in large outdoor environments with various properties. An identical collection methodology was used for all datasets: during a period of three months, numerous devices containing a GPS receiver periodically obtained new location data, which was sent to a local data server via a Sigfox or LoRaWAN message. Together with network information such as the receiving time of the message, base station IDs' of all receiving base stations and the Received Signal Strength Indicator (RSSI) per base station, this location data was stored in one of the three LPWAN datasets: <strong>lorawan_dataset_antwerp.csv</strong> 130 430 LoRaWAN messages, obtained in the city center of Antwerp <strong>sigfox_dataset_antwerp.csv</strong> 14 378 Sigfox messages, obtained in the city center of Antwerp <strong>sigfox_dataset_rural.csv</strong> 25 638 Sigfox messages, obtained in a rural area between Antwerp and Ghent As the rural and urban Sigfox datasets were recorded in adjacent areas, many base stations that are located at the border of these areas can be found in both datasets. However, they do not necessarily share the same identifier: e.g. ‘BS 1’ in the urban Sigfox dataset could be the same base station as ‘BS 36’ in the rural Sigfox dataset. If the user intends to combine both Sigfox datasets, the mapping of the ID's of these base stations can be found in the file: <strong>sigfox_bs_mapping.csv</strong> The collection methodology of the datasets, and the first results of a basic fingerprinting implementation are documented in the following journal paper:<br> http://www.mdpi.com/2306-5729/3/2/13 <strong>UPDATES IN VERSION 1.2</strong> In this version of the LPWAN dataset, only the LoRaWAN set has been updated. The Sigfox datasets remain identical to version 1.0 and 1.1. The main updates in the LoRaWAN set are the following: <strong>New data</strong>: the LoRaWAN messages in the new set are collected 1 year after the previous dataset version. To be consistent with the previous versions, the new LoRaWAN set is uploaded in the same .CSV format as before. This upload can still be found in this repository as ‘<strong>lorawan_dataset_antwerp.csv</strong>’. <strong>More gateways</strong>: Compared to the previous dataset, 4 gateways were added to the LoRaWAN network. The RSSI of these gateways are shown in columns ‘BS 69’, ‘BS 70’,‘BS 71’ and ‘BS 72’. All other ‘BS’ columns are in the same order as in previous dataset versions. <strong>More metadata: </strong>In the previous LoRaWAN dataset, metadata was limited to 3 receiving gateways per message. In the new dataset version, metadata from all receiving gateways is included in every message. Moreover, some gateways provide a timestamp with nanosecond precision, which can be used to evaluate Time Difference of Arrival localization methods with LoRaWAN. <strong>2 file formats: </strong>As more metadata becomes available, we find it important to share the dataset in a clearer overview. This also allows researchers to evaluate the performance of LoRaWAN in an urban environment. Therefore, we publish the new LoRaWAN dataset as a .CSV file as described above, but also as a .JSON file (<strong>lorawan_antwerp_2019_dataset.json.txt,</strong> the .txt file type had to be appended, otherwise the file could not be uploaded to Zenodo) An example of one message in this JSON format can be seen below: JSON format description: <strong>HDOP</strong>: Horizontal Dilution of Precision <strong>dev_addr: </strong>LoRaWAN device address <strong>dev_eui: </strong>LoRaWAN device EUI <strong>sf: </strong>Spreading factor <strong>channel: </strong>TX channel (EU region) <strong>payload: </strong>application payload <strong>adr: </strong>Adaptive Data Rate (1 = enabled, 0= disabled) <strong>counter: </strong>device uplink message counter <strong>latitude: </strong>Groundtruth TX location latitude <strong>longitude: </strong>Groundtruth TX location longitude <strong>airtime: </strong>signal airtime (seconds) <strong>gateways:</strong> <strong>rssi: </strong>Received Signal Strength <strong>esp: </strong>Estimated Signal Power <strong>snr: </strong>Signal-to-Noise Ratio <strong>ts_type: </strong>Timestamp type. If this says "GPS_RADIO", a nanosecond precise timestamp is available <strong>time: </strong>time of arrival at the gateway <strong>id: </strong>gateway ID JSON example <pre><code class="language-json">{ "hdop": 0.7, "dev_addr": "07000EFE", "payload": "008d000392d54c4284d18c403333333f04682aa9410500e8fd4106cabdbc420f00db0d470ce32ac93f0d582be93f0bfa3f8d3f", "adr": 1, "latitude": 51.20856475830078, "counter": 31952, "longitude": 4.400575637817383, "airtime": 0.112896, "gateways": [ { "rssi": -115, "esp": -115.832695, "snr": 6.75, "rx_time": { "ts_type": "None", "time": "2019-01-04T08:59:53.079+01:00" }, "id": "08060716" }, { "rssi": -116, "esp": -125.51497, "snr": -9.0, "rx_time": { "ts_type": "GPS_RADIO", "time": "2019-01-04T08:59:53.962029179+01:00" }, "id": "FF0178DF" } ], "dev_eui": "3432333853376B18", "sf": 7, "channel": 8 }</code></pre>