-
Notifications
You must be signed in to change notification settings - Fork 215
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 get information from original GPS points linked with matched edge #56
Comments
I am not quite sure about your problem. The optimal path (opath below) contains the edge matched for each point in a trajectory. Is that what you need? |
Thank you very much for quick reply. i like to assign the timestamp from 5 GPS points (orange points from original trajectory shown in above figure) to matched edge (in opath) . For instance, given the time stamps of GPS points to be (t1,t2,t3,t4,t5) respectively. |
Now I understand your problem. The master branch version of the fmm does not handle this unmatched point problem. If t2 is not matched, then the whole trajectory is skipped and not matched. However, a separate segmentation branch actually addressed this issue (it is not fully tested so not merged into the master) https://github.com/cyang-kth/fmm/tree/feature-segmentation where if t2 is not matched, the opath field will have a value of -1 so you can iterate through the same timestamps and check if there are any value of -1 in opath. fmm/example/segment/mr_outlier.txt Line 2 in e537f25
You can check this example for more detailed illustration https://github.com/cyang-kth/fmm/tree/feature-segmentation/example/segment You need to clone that branch using
|
Thank you very much. That is what i need please. |
I would like to get some attributes from original GPS points (say, timestamp) and link them to matched edge (in cpath). However, if there are some unmatched points ramdomly occured, i could not know the correct order of the matched edge (in opath) related with original GPS points (the order should not be the same as in original GPS points). So, is it possible to get the information from original GPS points linked with matched edge, please?
The text was updated successfully, but these errors were encountered: