We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am using STMATCH for matching GPS pings on a large city map. I am converting the map from osm using osmnx graph_from_xml function.
The results look good. I am using the following configuration:
config.k = 7 config.gps_error = 0.5 config.radius = 0.4 config.vmax = 30 config.factor = 1.5 config.reverse_tolerance = 1.0
I am using the Python wrapper, taking the input in wkt format , and matching using match_wkt function.
The inference time for some trips with moderate number of pings(Around 250 pings) exceeds 5 seconds. What can we do to bring the inference time down?
The text was updated successfully, but these errors were encountered:
You could use the fmm algorithm instead of the stmatch.
Sorry, something went wrong.
No branches or pull requests
I am using STMATCH for matching GPS pings on a large city map.
I am converting the map from osm using osmnx graph_from_xml function.
The results look good. I am using the following configuration:
I am using the Python wrapper, taking the input in wkt format , and matching using match_wkt function.
The inference time for some trips with moderate number of pings(Around 250 pings) exceeds 5 seconds.
What can we do to bring the inference time down?
The text was updated successfully, but these errors were encountered: