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

Creating the data folder structure #21

Closed
swapnesh-wani opened this issue Apr 15, 2019 · 8 comments
Closed

Creating the data folder structure #21

swapnesh-wani opened this issue Apr 15, 2019 · 8 comments

Comments

@swapnesh-wani
Copy link

@fangchangma I have two questions

  1. I downloaded the kitii dataset which has a folder structure like this

image

Now, do I have to delete |-- val folder and replace with the following?

image

if my assumption is correct then the above steps will make dir structure like this

image

  1. Where can I get the kitti_rgb data? Do I need to download from here for all the drive data that is there is kitti depth dataset? If yes, then do I need to copy the same folder
    image again?
@fangchangma
Copy link
Owner

fangchangma commented Apr 15, 2019

  1. There is no need to delete or move any files from the kitti depth dataset. You can keep the raw val folder while having the val_selection_cropped folder in the same directory.
  2. Yes, we need to download the raw data and extract the rgb images. The rgb images need to be structured in a similar way to the depth dataset.

The reason why I did not release the downloaded rgb dataset was to avoid violation of the kitti' licences.

@swapnesh-wani
Copy link
Author

@fangchangma thank you for your reply. Creating the rgb dataset is one tedious task because I have to look for each drive id and download the data and then selecting the corresponding images that are there in the depth-dataset.

Just for the confirmation, after downloading all the relevant rgb files, the dir structure should look like this?

image

@WANGYINGYU
Copy link

WANGYINGYU commented Apr 25, 2019

@fangchangma thank you for your reply. Creating the rgb dataset is one tedious task because I have to look for each drive id and download the data and then selecting the corresponding images that are there in the depth-dataset.

Just for the confirmation, after downloading all the relevant rgb files, the dir structure should look like this?

image

Hello,
I have the same problem, and I don't know how to match rgb and d in the flower structure. Can you give me some advice?
Thank you.@swapnesh-wani

@swapnesh-wani
Copy link
Author

@fangchangma thank you for your reply. Creating the rgb dataset is one tedious task because I have to look for each drive id and download the data and then selecting the corresponding images that are there in the depth-dataset.
Just for the confirmation, after downloading all the relevant rgb files, the dir structure should look like this?
image

Hello,
I have the same problem, and I don't know how to match rgb and d in the flower structure. Can you give me some advice?
Thank you.@swapnesh-wani

Hi @WANGYINGYU, I haven't downloaded the rgb dataset yet. But, I think the rgb dataset should look like my previous comment. Waiting for @fangchangma to confirm.

@fangchangma
Copy link
Owner

Hi. I just uploaded the scripts for downloading the RGB dataset. The README has also been updated to provide more details regarding the folder structures. Please let me know if it is unclear.

@swapnesh-wani
Copy link
Author

@fangchangma thanks for uploading the scripts. That will surely help a lot.

@WANGYINGYU
Copy link

@swapnesh-wani @fangchangma Thank you for your reply. But I still have a few questions about the datasets.
1)Is the val_selection_cropped folder in the kitti_depth folder downloaded from the manually selected validation and test data sets (5 GB) in kitti depth?
2)The velodyne_raw folder in the /kitti_depth/train/20******drive****_sync/proj_depth/ folder is downloaded from kitti depth's projected raw LiDaR scans data set (2 GB) and placed In the corresponding position?

@fangchangma
Copy link
Owner

@WANGYINGYU

  1. Yes
  2. Yes

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

3 participants