Microscopic Vehicle Trajectories from Heterogeneous and Area-Based Traffic

The Microscopic Vehicle Trajectory (MVT) data are from an urban midblock location in the National Capital Region of India, featuring highly heterogeneous and area-based traffic (weak lane-based/non-lane-based/disordered traffic, as you prefer to call it :D ^-^). The traffic was captured from a fixed height above the road surface (150 meters) using a UAV (drone), covering a nearly 180-meter stretch of road in both directions. The fundamental diagrams (FDs) are also attached. The MVTs are exported at a temporal resolution of 0.1 seconds.The coordinates are calibrated in relation to the local coordinate system.The dataset is in CSV format, with semicolons (;) as separators, and contains:DEL2: Over 3.5 million unique data points across all rows for more than 7,000 unique vehicles,DEL3: Over 1.5 million unique data points across all rows for more than 7,000 unique vehicles,DEL4: Over half (0.5) a million unique data points across all rows for more than 3,000 unique vehicles,DEL5: Nearly half (0.5) a million unique data points across all rows for more than 2500 unique vehicles,NDA1: Over 300,000 unique data points across all rows for more than 2700 unique vehicles, andNDA2: Over 360,000 unique data points across all rows for more than 2300 unique vehicles. Note: The MVT data has been extracted using the Data from Sky software, and the veracity of the output has already been checked in another study."Ali, Y., Krishnan, K.N., Sarkar, D.R., Rao, K.R., Chatterjee, N., Bhaskar, A., 2024. Scrutinizing Data from Sky : An Examination of Its Veracity in Area Based Traffic Contexts. arXiv Prepr. Arch. 1 . doi:https://doi.org/10.48550/arXiv.2404.17212" The data headers are as follows:Track ID: A unique Identifier for each vehicleType: Vehicle types (Tuk-Tuk: Motorised three-wheelers, Medium Vehicle: Light Commercial Vehicles)Track Width [m]: The width of the traced vehicle's bounding box in metersTrack Length [m]: The length of the traced vehicle's bounding box in metersAvg. Speed [km/h]: Mean speed of the traced vehicles x [m], y [m]: Local coordinates of the centre of the vehicleSpeed [km/h]: Instantaneous speed of the vehicleTan. Acc. [ms-2]: instantaneous Longitudinal acceleration in the direction of motionLat. Acc. [ms-2]: instantaneous lateral acceleration across the direction of motionTime [s]: Time stamp of the records (rows)Angle [rad]: Heading angle with reference to the horizontal frame Note: Some coordinate values (x, y) may appear negative, which is due to the local coordinate calibration. All the coordinates need to be shifted so the minimum values align with the origin for better data readability (it's okay if you don't). Important: Because the data is extracted with local coordinate calibration, traffic movement (changes in the x coordinate) will appear to increase in one direction of traffic and decrease in the other. P.S. It may appear that the data "DEL 1" is missing, but it is intentionally withheld to maintain dataset consistency. DEL 1 data pertain to a signalised intersection's single approach, whereas the datasets released here are from midblock locations. All the best! :)Have a happy research journey! (: