THOR - people tracks

Open data API in a single place

Provided by Zenodo

Get early access to THOR - people tracks API!

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

Dataset information

Country of origin
Updated
2020.01.24 00:00
Created
2019.09.10
Available languages
English
Keywords
Motion Prediction, Social Robotics, People Tracking, Human Robot Interaction
Quality scoring

Dataset description

THÖR is a dataset with human motion trajectory and eye gaze data collected in an indoor environment with accurate ground truth for the position, head orientation, gaze direction, social grouping and goals. THÖR contains sensor data collected by a 3D lidar sensor and involves a mobile robot navigating the space. In comparison to other, our dataset has a larger variety in human motion behaviour, is less noisy, and contains annotations at higher frequencies. The dataset includes 13 separate recordings in 3 variations: ``One obstacle" - features one obstacle in the environment and no robot ``Moving robot" - features one obstacle in the environment and the moving robot ``Three obstacles" - features three obstacles in the environment and no robot THOR - people tracks is the part of THÖR data set containing ground truth position of people in the environment, including information about head orientation.  The data are available in three formats: mat - Matlab binary file TSV - text file bag - ROS bag file MAT files File - [char] Path to original QTM file Timestamp - [string] Date and time of the startof the data collection Start Fram - [char] 1 Frames - [double] Number of frames in the file FrameRate - [double] Number of frames per second Events - [struct] 0 Trajectories - [struct] 3D postion of observed reflective markers Labeled  - [struct] Markers belonging to the tracked agents: Count - [double] Number of tracked markers Labels - [cell] List of marker labels Data - [double] Array of dimension {Count}x4x{Frames}, contains the 3D position of each marker and residue RigidBodies - [struct] 6D pose of the helmet, corresponds to head poistion and orientation: Bodies - [double] Number of tracked bodies Name  - [cell] Bodies Names Positions - [double] Array of dimension {Bodies}x3x{Frames} contains the position of the centre of the mass of the markers defining the rigid body Rotations - [double] Array of dimension {Bodies}x9x{Frames} contains rotation matrix describing the orientation of the rigid body RPYs  - [double] Array of dimension {Bodies}x3x{Frames} contains orientation of the rigid body described as RPY angles Residual - [double] Array of dimension {Bodies}x1x{Frames} contains residual for each rigid body TSV files 3D data File Header NO_OF_FRAMES  - number of frames in the file   NO_OF_CAMERAS - number of cameras tracking makers NO_OF_MARKERS - number of tracked markers FREQUENCY - tracking frequency [Hz]    NO_OF_ANALOG - number of analog inputs    ANALOG_FREQUENCY - frequency of analog input    DESCRIPTION -  -- TIME_STAMP - the beginning of the data recording DATA_INCLUDED - the type of data included MARKER_NAMES - names of tracked makers Column names Frame - frame ID Time - frame timestamp [marker name] [C] - coordinate of a [marker name] along [C] axis 6D data File Header NO_OF_FRAMES  - number of frames in the file   NO_OF_CAMERAS - number of cameras tracking makers NO_OF_MARKERS - number of tracked markers FREQUENCY - tracking frequency [Hz]    NO_OF_ANALOG - number of analog inputs    ANALOG_FREQUENCY - frequency of analog input    DESCRIPTION -  -- TIME_STAMP - the beginning of the data recording DATA_INCLUDED - the type of data included BODY_NAMES - names of tracked rigid bodies Colum Names Frame - frame ID Time - frame timestamp The columns are grouped according to the rigid body. Each group starts with the name of the rigid body and then is followed by the position of the centre of the mas and the orientation expressed as RPY angles and rotation matrix Reference: For more details check project website thor.oru.se or check our publications: @article{thorDataset2019, title={TH\"OR: Human-Robot Indoor Navigation Experiment and Accurate Motion Trajectories Dataset}, author={Andrey Rudenko and Tomasz P. Kucner and Chittaranjan S. Swaminathan and Ravi T. Chadalavada and Kai O. Arras and Achim J. Lilienthal}, journal={arXiv preprint arXiv:1909.04403}, year={2019} }  
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