-
Notifications
You must be signed in to change notification settings - Fork 56
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
Inquiry Regarding Labeled LOS/NLOS Dataset and CSV Format Data #28
Comments
Hi Yelyzaveta, About the LOS and NLOS visibility labelling, only selected data is available at this moment, you can check with this link: For the CSV format of the data, the RINEX format is a standard format for different processing toolboxes to handle directly. Maybe some open-sourced toolboxes or libraries are a good starting point, such as:
Once again, thanks for your attention to our dataset. Regards, |
Thank you @ivannhf so much for your reply . Can you please share with me any related to this datasets works and documentation how this dataset collected so I can cite it in my article |
You can refer to the citation below, |
Good day,
My name is Yelyzaveta Pervysheva, and I am currently working on multipath using AI technologies. I recently came across your dataset in RINEX format and found it to be quite intriguing for my research purposes.
I am particularly interested in obtaining a labeled dataset that distinguishes between Line-of-Sight (LOS) and Non-Line-of-Sight (NLOS) scenarios. Given the complexity of my research, having access to such a dataset would significantly contribute to the advancement of my work.
Additionally, I was wondering if it would be possible to acquire the same dataset in CSV format, since i struggle of convert those obs files.
Could you please let me know if such a labeled LOS/NLOS dataset is available? Furthermore, if the dataset can be provided in CSV format or if there are any conversion tools available, I would greatly appreciate your assistance in this matter.
Thank you very much for your time and consideration. You can contact me at [email protected]
Warm regards,
Yelyzaveta Pervysheva
The text was updated successfully, but these errors were encountered: