UWB Ranging and Localization Dataset for "High-Accuracy Ranging and Localization with Ultra-Wideband Communication for Energy-Constrained Devices"

UWB Ranging and Localization Dataset for "High-Accuracy Ranging and Localization with Ultra-Wideband Communication for Energy-Constrained Devices" This dataset accompanies the paper "High-Accuracy Ranging and Localization with Ultra-Wideband Communication for Energy-Constrained Devices," by L. Flueratoru, S. Wehrli, M. Magno, S. Lohan, D. Niculescu, accepted for publication in the IEEE Internet of Things Journal. Please refer to the paper for more information about analyzing the data. If you find this dataset useful, please consider citing our paper in your work. This dataset is split into two parts: "ranging" and "localization." Both parts contain measurements acquired with 3db Access and Decawave MDEK1001 UWB devices. In the "3db" and "decawave" datasets, when a recording has the same name, it means that the measurements were acquired at the exact same locations with the two types of devices. The "3db" ranging dataset contains, apart from these, more measurements acquired in various LOS and NLOS scenarios. In the directory "images" you can find photos of some of the setups. The "ranging" and "localization" directories both contain a "data" directory which holds the datasets and a "code" directory with Python scripts that show how to read and analyze the data. The 3db Access ranging recordings contain the following data: - True distance - Measured distance - Channel on which the measurements were acquired (can be 6.5, 7, or 7.5 GHz) - Time of arrival as identified by the chipset - Channel impulse response (CIR) - Line-of-sight (LOS)/non-line-of-sight (NLOS) scenario (encoded as 0 and 1, respectively) - If NLOS, the type of NLOS obstruction and its tickness. The Decawave ranging recordings contain the following data: - True distance - Measured distance - Line-of-sight (LOS)/non-line-of-sight (NLOS) scenario (encoded as 0 and 1, respectively) - If NLOS, the type of NLOS obstruction and its tickness. The MDEK kit operates only on the 6.5 GHz channel and cannot output the CIR without further code modifications, which is why this data is not available for the Decawave dataset. The localization dataset includes the following data: - True location as measured by an HTC Vive system - Estimated location using a Gauss-Newton trilateration algorithm (please refer to the paper for more details) - Distance measurements between each anchor and the tag.