Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extracting layer ID from x,y and z coordinates #27

Open
Ghallabi opened this issue Nov 29, 2018 · 14 comments
Open

Extracting layer ID from x,y and z coordinates #27

Ghallabi opened this issue Nov 29, 2018 · 14 comments

Comments

@Ghallabi
Copy link

Ghallabi commented Nov 29, 2018

Hi,

I am working with Kitti dataset and I want to add a "ring id" label to each point . Instead of having XYZI points, I am wondering if we can have XYZRI points ?

@Ghallabi Ghallabi changed the title Hi, Extracting layer ID from x,y and z coordinates Nov 29, 2018
@versatran01
Copy link

When you say "ring id", does that mean which beam each point belongs to? For example, if one is using VLP64, then there would be 64 different ring ids?

@Ghallabi
Copy link
Author

Ghallabi commented Dec 1, 2018

Yes, exactly.
Is this label already available ?
Best,

@versatran01
Copy link

I don't know, but I was trying to do the same thing but looks like it is not possible just from the data.

@versatran01
Copy link

One could possibly calculate the altitude of each point and then assign a corresponding ring id?

@aidanjones3
Copy link

I also am interested in determining a solution to this problem. I had two thoughts on the matter: The first being if the kitti datasets somehow have the points ordered already? This may provide some structure to take advantage of. The other would be to look at the timestamp of the points in spherical coordinates per frame. Not entirely sure if this would work but just my thoughts.

@geoeo
Copy link

geoeo commented Oct 3, 2019

Formulae is given in #49 But it doesnt seem to work. I would love to hear if it works for you

@aidanjones3
Copy link

Will attempt, and update you with results.

@versatran01
Copy link

One (fixable) problem is you won't get clean data.
I think kitti paper says that they undistorted the point cloud so when you convert them from euclidean to polar coordinates, it will be noisy.

@geoeo
Copy link

geoeo commented Oct 3, 2019

Where do they say that? In the dataset paper? Also, does that mean the synced data part should work?

@versatran01
Copy link

Yeah I think in the paper. So raw data should work, not synced because that's where they corrected the lidar data.

@geoeo
Copy link

geoeo commented Oct 4, 2019

Thanks for the help. I checked with both and both provide angles which are outside the range of 2-24.8. I looked at the manual again for the HDL 64 E and it states it comes with a calibration.xml. :( Im not really sure how researchers used the kitti velodyne data to provide accurate reconstruction if this is missing

@versatran01
Copy link

Then it's a problem with kitti.

@matigolias
Copy link

Check VincentCheungM/Run_based_segmentation#3 for finding the ring in a non-angle based approach

@mr-abramenko
Copy link

Check Taeyoung96@a77c6df for finding the ring in a angle based approach

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants