atlas

Research map / Detection and segmentation / 3D detection and driving

PC-BEV: An Efficient Polar-Cartesian BEV Fusion Framework for LiDAR Semantic Segmentation

AAAI 2025 · Detection and segmentation › 3D detection and driving · approach: Multi-camera BEV detection · 8 citations (OpenAlex)

Read the paperCheck your idea against 108,967 papers

AI-extracted summary. Written by AI from the paper's full text. Numbers and claims can be wrong or missing context, so check the paper before you cite or build on it.

Proposes PC-BEV, a BEV-only LiDAR segmentation framework that fuses Polar and Cartesian BEV branches via precomputed remap operations and a hybrid Transformer-CNN backbone, reaching SOTA-level mIoU on SemanticKITTI and nuScenes with faster inference than point-based multiview fusion.

Problem

Multiview LiDAR segmentation fusion (e.g., range view and BEV) relies on computationally expensive point-based grid sampling and scatter operations because views lack fixed correspondences, which hinders real-time deployment.

Approach

Fuse Polar and Cartesian partitionings within a single BEV space, exploiting their fixed grid-to-grid correspondence to precompute remap indices for dense, memory-friendly feature alignment instead of point-based interaction; add a Transformer-then-U-Net CNN hybrid backbone.

Key results

Measured effects reported in the paper

What was changedWhereMeasuredEffect
Fuse Polar and Cartesian BEV branches instead of using the Polar branch alone (ablation)PC-BEV · SemanticKITTI validationmIoU: 61.2 -> 66.4Helped
Fuse Polar and Cartesian BEV branches instead of using the Cartesian branch alone (ablation)PC-BEV · SemanticKITTI validationmIoU: 56.5 -> 66.4Helped
Fuse Polar and Cartesian partitioning strategies (ablation)PC-BEV · nuScenes validationmIoU: 75.0 -> 76.2Helped
Add remap-based feature fusion to the two-branch model (ablation)PC-BEV · nuScenes validationmIoU: 76.2 -> 78.2Helped
Add Transformer-CNN Mixture Architecture (ablation)PC-BEV · nuScenes validationmIoU: 78.2 -> 78.8Helped
Replace remap-based fusion with point-based fusion (ablation)PC-BEV · nuScenes validationlatency: 29 -> 39Hurt
Use remap-based rather than point-based feature interactionBEV feature interaction · BEV features, 0.2m voxel resolutionlatency: 6.8 -> 0.04; 8.0 -> 0.04Helped
Use PC-BEV rather than AMVNetLiDAR semantic segmentation · SemanticKITTI validationmIoU: 65.2 -> 66.4Helped
Use PC-BEV rather than RPVNetLiDAR semantic segmentation · nuScenes validationmIoU: 77.6 -> 78.8Helped
Use PC-BEV rather than CPGNetLiDAR semantic segmentation · SemanticKITTI testmIoU: 68.3 -> 67.2Hurt

Surprising findings

Limitations

Experimental setup

Datasets: SemanticKITTI nuScenes-lidarseg

Benchmarks: SemanticKITTI nuScenes-lidarseg

Metrics: mIoU latency (ms)

Baselines: RangeNet++ PolarNet GFNet AMVNet RPVNet CPGNet RangeViT CENet MaskRange KPRNet SalsaNext PCSCNet

Builds on: PolarNet AMVNet CPGNet GFNet SalsaNext

Closest papers by meaning

Writing a paper in this area? scime draft is a free LaTeX editor with AI included, real-time co-authors and a check of your references and venue rules before you submit. It also imports OpenAI Prism projects.

Open scime draft

Get the next scime Dispatch and a monthly field update

Free. We send a confirmation link first; every email has a one-click unsubscribe. Privacy