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

How to read the tracklets and get the box on image? (for both 2d and 3d) #36

Closed
lucasjinreal opened this issue Oct 30, 2018 · 7 comments

Comments

@lucasjinreal
Copy link

As title suggested

@dakdouky
Copy link

dakdouky commented Feb 27, 2019

Same problem here! have you found a solution, @jinfagang ?

@leeclemnet
Copy link
Member

Currently we only support the raw and odometry datasets. Support for the tracking dataset would be a nice addition if someone in the community wanted to tackle it and submit a PR.

@dakdouky
Copy link

dakdouky commented Mar 1, 2019

I've managed to do it and will make it available soon. thanks :)
untitled

@leeclemnet
Copy link
Member

Apparently I forgot about #28, which added support for the tracking dataset. I haven't used it personally. Does it do what you need, or have you added something on top of it to get the bounding boxes?

@dakdouky
Copy link

dakdouky commented Mar 1, 2019

In fact, I did not use it. Instead, I build some wrapping on top of Christian Herdtweck XML parser.
I'm trying to add a Dynamic/Static annotation to the tracklets.

@LukeAI
Copy link

LukeAI commented Jun 6, 2019

Hey guys,
I want to be able to read the raw tracklets and extract the projected 2d bounding boxes and corresponding rgb image. I understand that this is possible with these utils but How can I do this?
@MOHAMEDELDAKDOUKY @leeclemnet

@DerekGloudemans
Copy link

I implemented bbox plotting for 2d and 3d objects for the tracking dataset. Will port it over to this repo and submit a pull request eventually. For now, the code is in: https://github.com/DerekGloudemans/KITTI-utils/blob/master/track_loader.py

Worth noting that the tracking dataset has very coarse object heights (I don't think they had people manually adjust the heights on this datset and the velodyne data perhaps doesn't contain this info because the objects extend above its range. I added a naive correction with a constant value for each class.

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

5 participants