InScope: A New Real-world 3D Infrastructure-side Collaborative Perception Dataset for Open Traffic Scenarios

March 12, 2026 · View on GitHub

ckpts video

This is the official implementation of the InScope dataset. The paper has been accepted by Information Fusion. "InScope: A New Real-world 3D Infrastructure-side Collaborative Perception Dataset for Open Traffic Scenarios". Xiaofei Zhang, Yining Li, Jinping Wang, Xiangyi Qin, Ying Shen, Zhengping Fan, Xiaojun Tan


The ground truth of sequence 0000.

Overview

Data Download

Due to project restrictions, the InScope dataset is made conditionally public. If you need to use the InScope dataset, please fill in the following ./assets/InScope_Dataset_Release_Agreement.docx file and email your full name and affiliation to the contact person. We ask for your information only to ensure the dataset is used for non-commercial purposes.

After downloading the data, please put the data in the following structure:

├── InScope-Sec, InScope_Pri, and InScope datasets
│   ├── ImageSets
|      |── train.txt
|      |── test.txt
|      |── val.txt
│   ├── labels
|      |── 000000.txt
|      |── 000001.txt
|      |── 000002.txt
|      |── ...
│   ├── points
|      |── 000000.npy
|      |── 000001.npy
|      |── 000002.npy
|      |── ...
├── InScope_track
│   ├── label_02
|      |── 0000.txt
|      |── 0001.txt
|      |── 0002.txt
|      |── ...
│   ├── points
|      |── 0000
|          |── 000000.bin
|          |── 000001.bin
|          |── 000002.bin
|          |── ...
|      |── 0001
|      |── 0002
|      |── ...
│   ├── evaluate_tracking.seqmap
│   ├── evaluate_tracking.seqmap.test
│   ├── evaluate_tracking.seqmap.training
│   ├── evaluate_tracking.seqmap.val

Data Loading

To facilitate researchers' use and understanding, we adapted the InScope dataset to the OpenPCDet framework and provided the corresponding dataset configuration file ./InScope.config

Quick Start

For detection training & inference, you can find instructions in detection_code/openpcdet/README_InScope.md in detail.

All the checkpoints are released in link in the tabels below, you can save them in codes/ckpts/.

Benchmark

Results of 3D object detection based on the InScope dataset

MethodsCar AP@0.7Pedestrian AP@0.5Cyclist AP@0.5Truck AP@0.7mAP40FPSDownload Link
PointRCNN71.7568.1362.9194.5074.324.58[URL]
3DSSD68.0013.8836.5895.0853.3811.35[URL]
SECOND72.8247.9559.9195.9869.1720.58[URL]
Pointpillar78.0435.3458.4695.8666.9324.51[URL]
PV-RCNN75.0548.3756.3194.5268.564.35[URL]
PV-RCNN++80.5553.3170.9295.9275.1814.66[URL]
CenterPoint77.2470.4574.7496.1279.6430.49[URL]
CenterPoint_RCNN78.3371.1375.2396.4880.296.55[URL]

Results of 3D object detection based on the InScope-Sec, InScope_Pri, and InScope datasets

Detection result based on the InScope-Sec Only

MethodsCar AP@0.7Pedestrian AP@0.5Cyclist AP@0.5Truck AP@0.7mAP40FPSDownload Link
PointRCNN14.1223.6620.6245.3625.9422.94[URL]
Pointpillar44.7733.1831.4282.5247.9787.72[URL]
PV-RCNN++43.4934.6039.9476.0448.5216.67[URL]
CenterPoint35.9237.4038.2468.7845.08107.53[URL]

Detection result based on the InScope_Pri Only

MethodsCar AP@0.7Pedestrian AP@0.5Cyclist AP@0.5Truck AP@0.7mAP40FPSDownload Link
PointRCNN61.1488.8061.9948.9665.224.67[URL]
Pointpillar67.3423.8243.5191.5956.5725.25[URL]
PV-RCNN++72.5945.2661.2191.0267.5213.81[URL]
CenterPoint61.3149.6252.7382.0261.4233.90[URL]

Detection result based on the Early Fusion (InScope) Mechanism

MethodsCar AP@0.7Pedestrian AP@0.5Cyclist AP@0.5Truck AP@0.7mAP40FPSDownload Link
PointRCNN71.7568.1362.9194.5074.324.58[URL]
Pointpillar78.0435.3458.4695.8666.9324.33[URL]
PV-RCNN++80.5553.3170.9295.9275.1812.45[URL]
CenterPoint77.2470.4574.7496.1279.6430.49[URL]

Detection result based on the Late Fusion Mechanism

MethodsCar AP@0.7Pedestrian AP@0.5Cyclist AP@0.5Truck AP@0.7mAP40FPSDownload Link
PointRCNN62.6961.3152.3190.9366.811.32[pri URL]+[sec URL]
Pointpillar68.6531.8149.9293.4860.961.81[pri URL]+[sec URL]
PV-RCNN++68.0153.4756.9592.6567.771.21[pri URL]+[sec URL]
CenterPoint58.1350.0356.0185.6562.456.40[pri URL]+[sec URL]

Detection result based on the Middle Fusion Mechanism (based on BEV fusion framework)

MethodsCar AP@0.7Pedestrian AP@0.5Cyclist AP@0.5Truck AP@0.7mAP40FPSDownload Link
Point-RCNN------
Pointpillar------
PV-RCNN++73.7852.0662.0691.8969.9513.02[BEV fusion URL]
CenterPoint52.7438.9551.1981.7356.1515.85[BEV fusion URL]

We provide another middle fusion framework, based on 2D feature fusion mechanism. The checkpoint can be found in [PV-RCNN++ 2D fusion URL] and [CenterPoint 2D fusion URL].

Results of data domain transfer on the car class

Source→TargetDAIR-V2X-I→KITTIONCE→KITTIInScope→KITTIInScope→DAIR-V2X-IDAIR-V2X-I→InScope
mAP40mAP40mAP40mAP40AP40
Source Domain37.98[URL]41.65[URL]52.97[URL]31.05[URL]32.16[URL]
SN44.80[URL]49.34[URL]61.87[URL]31.81[URL]33.25[URL]
ST3D65.35[URL]58.19[URL]74.63[URL]48.98[URL]37.03[URL]
Target Domain81.63[URL]81.63[URL]81.63[URL]81.41[URL]71.75[URL]

3D Multiobject tracking results on the car, pedestrian, cyclist, and truck.

Tracking result of the AD3DMOT based on the InScope dataset on the car class (IoU threshold = 0.5/0.7)

DetectorsAMOTA↑MOTA↑IDSW↓FRAG↓
PointRCNN74.81/60.3463.25/44.4512/6595/1834
Pointpillar82.23/64.9868.85/46.8256/44391/2166
PVRCNN++81.63/68.7167.56/50.7283/39386/1560
Centerpoint78.76/61.2561.02/40.9827/15367/1720

Tracking result of the AD3DMOT based on the InScope-Pri dataset on the car class (IoU threshold = 0.5/0.7)

DetectorsAMOTA↑MOTA↑IDSW↓FRAG↓
PointRCNN61.14/44.9155.04/35.3442/311319/2406
Pointpillar74.02/51.8166.89/37.84154/631820/3138
PVRCNN++73.47/57.8254.98/37.94378/99914/1524
Centerpoint76.01/49.3261.89/31.07103/49717/2151

Tracking result of the AD3DMOT based on the InScope dataset on the pedestrian class (IoU threshold = 0.25/0.5)

DetectorsAMOTA↑MOTA↑IDSW↓FRAG↓
PointRCNN59.89/56.5939.73/37.061/16/22
Pointpillar32.09/27.4227.79/25.360/04/24
PVRCNN++31.39/28.5427.71/25.753/310/20
Centerpoint67.38/62.0363.48/59.305/48/35

Tracking result of the AD3DMOT based on the InScope-Pri dataset on the pedestrian class (IoU threshold = 0.25/0.5)

DetectorsAMOTA↑MOTA↑IDSW↓FRAG↓
PointRCNN78.76/72.6567.61/60.941/1189/241
Pointpillar78.14/72.7868.68/61.437/6130/321
PVRCNN++73.76/67.6758.18/51.6125/12121/205
Centerpoint75.37/64.2765.03/53.4310/7298/500

Tracking result of the AD3DMOT based on the InScope dataset on the cyclist class (IoU threshold = 0.25/0.5)

DetectorsAMOTA↑MOTAIDSW↓FRAG↓
PointRCNN60.97/50.2741.56/33.7710/1399/272
Pointpillar49.96/33.7533.82/22.333/1364/379
PVRCNN++63.00/52.6543.22/34.12126/82177/349
Centerpoint68.78/57.5045.42/37.586/1670/267

Tracking result of the AD3DMOT based on the InScope-Pri dataset on the cyclist class (IoU threshold = 0.25/0.5)

DetectorsAMOTA↑MOTA↑IDSW↓FRAG↓
PointRCNN38.31/25.5727.68/18.7431/27302/595
Pointpillar27.90/9.4619.41/5.5822/12272/275
PVRCNN++23.27/17.0612.37/10.4448/32151/140
Centerpoint55.81/34.8838.70/19.5546/19198/613

Tracking result of the AD3DMOT based on the InScope dataset on the truck class (IoU threshold = 0.5/0.7)

DetectorsAMOTA↑MOTA↑IDSW↓FRAG↓
PointRCNN82.53/78.6773.34/68.203/2124/181
Pointpillar82.18/76.7975.26/70.339/880/182
PVRCNN++81.50/77.2069.15/64.539/876/141
Centerpoint81.44/76.1171.89/65.857/770/207

Tracking result of the AD3DMOT based on the InScope-Pri dataset on the truck class (IoU threshold = 0.5/0.7)

DetectorsAMOTA↑MOTA↑IDSW↓FRAG↓
PointRCNN78.76/72.6567.61/60.941/1189/241
Pointpillar78.14/72.7868.68/61.437/6130/321
PVRCNN++73.76/67.6758.18/51.6125/12121/205
Centerpoint75.37/64.2765.03/53.4310/7298/500

TODO

The code and configuration of 3DMOT on the InScope dataset will be released.

Citation

If you find InScope useful in your research or applications, please consider giving us a star 🌟.

The BibTeX format is as follows:

@article{inscope_2026,
title = {InScope: A new real-world 3D infrastructure-side collaborative perception dataset for open traffic scenarios},
journal = {Information Fusion},
volume = {128},
pages = {103951},
year = {2026},
issn = {1566-2535},
doi = {https://doi.org/10.1016/j.inffus.2025.103951},
author = {Xiaofei Zhang and Yining Li and Jinping Wang and Xiangyi Qin and Ying Shen and Zhengping Fan and Xiaojun Tan},
}

Acknowledgment