Papers › PolarNet: An Improved Grid Representation for Online LiDAR Point Clouds Semantic Segmentation

PolarNet: An Improved Grid Representation for Online LiDAR Point Clouds Semantic Segmentation

31 Mar 2020CVPR 2020 6arXiv:2003.14032archive 2025-07-28

Yang Zhang, Zixiang Zhou, Philip David, Xiangyu Yue, Zerong Xi, Boqing Gong, Hassan Foroosh

The need for fine-grained perception in autonomous driving systems has resulted in recently increased research on online semantic segmentation of single-scan LiDAR. Despite the emerging datasets and technological advancements, it remains challenging due to three reasons: (1) the need for near-real-time latency with limited hardware; (2) uneven or even long-tailed distribution of LiDAR points across space; and (3) an increasing number of extremely fine-grained semantic classes. In an attempt to jointly tackle all the aforementioned challenges, we propose a new LiDAR-specific, nearest-neighbor-free segmentation algorithm - PolarNet. Instead of using common spherical or bird's-eye-view projection, our polar bird's-eye-view representation balances the points across grid cells in a polar coordinate system, indirectly aligning a segmentation network's attention with the long-tailed distribution of the points along the radial axis. We find that our encoding scheme greatly increases the mIoU in three drastically different segmentation datasets of real urban LiDAR single scans while retaining near real-time throughput.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 11 code samples: 10 from 3 repositories linked to this paper, 1 identical to code harvested from another paper's repository. Across all 11: 11 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 3 violated, 5 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 3 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 2 samples from 1 repository, 2 ran (1 with no instrument failure; 1 where Syntology's instrument failed); community (archive-listed): 8 samples from 2 repositories, 8 ran (6 with no instrument failure; 2 where Syntology's instrument failed); 1 identical to code first harvested elsewhere. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

edwardzhou130/PolarSeg officialmentioned in papermentioned on GitHubpytorchSyntology: 2 samples, 2 ran (1 instrument-failed) · 0 unverified report
Yvanali/KITTISeg mentioned on GitHubpytorchBSD-3-ClauseSyntology: 6 samples, 6 ran (2 instrument-failed) · 0 unverified report
bbejczy/polarseg-kitti mentioned on GitHubpytorchSyntology: not harvested report
isunLt/PolarSeg mentioned on GitHubpytorchBSD-3-ClauseSyntology: 2 samples, 2 ran (0 instrument-failed) · 0 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

11 samples harvested: 11 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 3 violated, 5 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

3ran · violated contract
3ran; the contract check could not run
5ran

Licence: 1 of the 11 samples is pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 3 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. 1 sample is listed last, in a group without a repository. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

edwardzhou130/PolarSeg official repository 2 samples, 2 ran (1 instrument-failed) · 0 unverified
fast_hist in 24 papers
census: 2 implementations from 6 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 1, kind int, dtype int32 · arg 2: rank 1, kind int, dtype int32
train_SemanticKITTI.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant BSD-3-Clause (permissive) · 87f4974196dfa580 · report fixture: signature pred:ndarray/1/int, label:ndarray/1/int, n:int/0/int · returned ndarray · level recorded 2026-09-22
fast_hist_crop train_SemanticKITTI.py ran · violated contract BSD-3-Clause (permissive) · 3d2448f07f7f9e8f · report fixture: signature output:ndarray/1/int, target:ndarray/1/int, unique_label:ndarray/1/int · returned ndarray · level recorded 2026-09-22
Yvanali/KITTISeg community (archive-listed) 6 samples, 6 ran (2 instrument-failed) · 0 unverified
cart2polar in 5 papers dataloader/dataset.py ran fingerprinted BSD-3-Clause (permissive) · 4cbfcba4a545864d · report fixture: signature input_xyz:ndarray/2/float · returned ndarray · level recorded 2026-09-24
grp_range_torch network/ptBEV.py ran BSD-3-Clause (permissive) · bb6f31439534fc4b · report fixture: signature a:Tensor/1/int, dev:str/0/str · returned Tensor · level recorded 2026-09-24
iou in 97 papers
census: 5 implementations from 7 papers, 5 distinct outputs across 5 buckets, one shared input per bucket this sample: bucket 3 of 5, arg 1: rank 2, kind int, dtype int64 · arg 2: rank 2, kind int, dtype int64
network/lovasz_losses.py ran; the contract check could not run (RAISES) fingerprinted BSD-3-Clause (permissive) · d94639b28b2134ff · report fixture: signature preds:ndarray/2/int, labels:ndarray/2/int, C:int/0/int, EMPTY:float/0/float, ignore:NoneType/0/?, per_image:bool/0/bool · returned ndarray · level recorded 2026-09-22
iou_binary in 27 papers network/lovasz_losses.py ran; the contract check could not run (RAISES) fingerprinted BSD-3-Clause (permissive) · 1211530cd527bd0b · report fixture: signature preds:ndarray/3/int, labels:ndarray/3/int, EMPTY:float/0/float, ignore:int/0/int, per_image:bool/0/bool · returned float · level recorded 2026-09-22
lovasz_grad in 42 papers network/lovasz_losses.py ran · violated contract fingerprinted BSD-3-Clause (permissive) · e85b5d21dc5b8382 · report fixture: signature gt_sorted:Tensor/1/int · returned Tensor · level recorded 2026-09-22
polar2cat in 5 papers dataloader/dataset.py ran fingerprinted BSD-3-Clause (permissive) · dd197502413d486a · report fixture: signature input_xyz_polar:ndarray/2/float · returned ndarray · level recorded 2026-09-24
isunLt/PolarSeg community (archive-listed) 2 samples, 2 ran (0 instrument-failed) · 0 unverified
nb_greedy_FPS network/ptBEV.py ran BSD-3-Clause (permissive) · 8293ba05297fe94b · report fixture: signature xyz:ndarray/2/float, K:int/0/int · returned ndarray · level recorded 2026-09-24
parallel_FPS network/ptBEV.py ran BSD-3-Clause (permissive) · 6e18c9fe0ec4521a · report fixture: signature np_cat_fea:ndarray/2/float, K:int/0/int · returned ndarray · level recorded 2026-09-24
Repository not located 1 sample, 1 ran (0 instrument-failed) · 0 unverified
1 sample is identical to code Syntology harvested from another paper's repository; this paper's own copy was not located, so no repository is named and no licence is recorded.
per_class_iu in 9 papers repository not located ran · violated contract fingerprinted licence of this copy not recorded · b1c59751f8968e99 · report fixture: signature hist:ndarray/2/float · returned ndarray · level recorded 2026-09-22

Tasks

3D Semantic SegmentationAutonomous DrivingLIDAR Semantic SegmentationRobust 3D Semantic SegmentationSegmentationSemantic Segmentation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
3D Semantic Segmentation SemanticKITTI PolarNet test mIoU 57.2% #24 of 45 Archive leaderboard report
LIDAR Semantic Segmentation nuScenes PolarNet test mIoU 0.69 #28 of 36 Archive leaderboard report
Robust 3D Semantic Segmentation SemanticKITTI-C PolarNet mean Corruption Error (mCE) 118.56% #18 of 22 Archive leaderboard report
Robust 3D Semantic Segmentation nuScenes-C PolarNet mean Corruption Error (mCE) 115.09% #11 of 12 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

Introduced by this paper: PolarNet

PolarNet

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections