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 obtain the positional data 'gp_pos.csv' ? #1

Open
DayDayUpUpUp666 opened this issue Oct 7, 2021 · 7 comments
Open

How to obtain the positional data 'gp_pos.csv' ? #1

DayDayUpUpUp666 opened this issue Oct 7, 2021 · 7 comments

Comments

@DayDayUpUpUp666
Copy link

I wonder to know that how the positional data is obtained?The experimental results of other data sets in your article, and how to get the corresponding positional data?

@mchancan
Copy link
Owner

mchancan commented Oct 8, 2021

Thank you for your question and interest in the article.
I manually created gp_pos.csv using a website service that got me the coordinates (x, y) from the map provided here. Then I just normalized these values between 0 to 1 to generate gp_pos.csv.
For the other datasets, you can basically directly use their GPS data to create a similar *.csv file. For example, a raw GPS-data file for Nordland can be found by the end of this article. For this particular dataset, you might need to interpolate some missing GPS data points that you might find within each traversal in order to have the same number of GPS data points and images. You can try to make it for Nordland and then you will likely easily generalize the procedure for the order datasets. If this doesn't work for you, I think I can try to share the preprocessed GPS data I used for Nordland in the papers---although I don't have access to my PC at the moment so it might take a while.

@DayDayUpUpUp666
Copy link
Author

Thanks for your detailed reply!I have one more question to know. Training is using images and positional data, and do you use positional data when testing?

@mchancan
Copy link
Owner

mchancan commented Oct 11, 2021

Yes.

@agtbaskara
Copy link

Thank you for your question and interest in the article. I manually created gp_pos.csv using a website service that got me the coordinates (x, y) from the map provided here. Then I just normalized these values between 0 to 1 to generate gp_pos.csv. For the other datasets, you can basically directly use their GPS data to create a similar *.csv file. For example, a raw GPS-data file for Nordland can be found by the end of this article. For this particular dataset, you might need to interpolate some missing GPS data points that you might find within each traversal in order to have the same number of GPS data points and images. You can try to make it for Nordland and then you will likely easily generalize the procedure for the order datasets. If this doesn't work for you, I think I can try to share the preprocessed GPS data I used for Nordland in the papers---although I don't have access to my PC at the moment so it might take a while.

Can you please share the preprocessed GPS data you use? I want to replicate the experiment using the Nordland dataset.
Also, did you extract the frame from the video once every 1 second? What method did you use to interpolate the missing GPS data points? Because it seems that the number of frame and GPS data points in the video is not the same (I assume we use Summer GPS data points as the main reference).

@mchancan
Copy link
Owner

mchancan commented Dec 9, 2021

Hi. I can certainly share it here next week if that's fine (I hope to finally go back to the lab and turn on my PC by Friday next week). For Nordland, I used summer as reference and sampled at 1 FPS to then interpolate the missing points with scipy (I couldn't remember the exact function name I used but I will share the python script to do so along with the GPS data). Thanks for your patience. Regards

@agtbaskara
Copy link

Any update on this? I hope you can go to your lab

@mchancan
Copy link
Owner

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