-
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
About LineString format and example loading GPS points in python api #164
Comments
I have tried using |
You can check this link for example https://github.com/cyang-kth/fmm/blob/master/example/notebook/fmm_example.ipynb For GPS CSV you can do
from fmm import GPSConfig,ResultConfig
input_config = GPSConfig()
input_config.file = "../data/gps.csv"
input_config.id = "id"
input_config.gps_point = true |
Thanks for your reply. I have run through the code successfully according to your instruction. This is what I get for the output status:
However, when I look into the output file, all the |
Please check the issue #138 (comment) for summary of common problems. You need to refer to this https://github.com/cyang-kth/osm_mapmatching for downloading road network. The one downloaded from osmnx does not have the ID field (osmid could be a tuple and it should not be used as ID). |
Thanks for your reply. |
I am trying to use the Python API to match the trajectory in GPS coordinates (with time step). However, I am not that familiar with the LineString input. Almost all the examples provided in python API use the LineString as the input but I do not know how to convert the GPS coordinates to this format.
Therefore, I am wondering how can I convert the GPS coordinates to the LineString
wkt
format.Also in the wiki, it is stated that loading the GPS points in
csv
file is supported. Could the author please provide an example matching the trajectory data in the format of GPS coordinates or give me some hints on how can I convert the GPS coordinates to the LineString format?Thank you!
The text was updated successfully, but these errors were encountered: