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

Provide OSM node ids in nearest response #2548

Closed
vkurchatkin opened this issue Jun 14, 2016 · 4 comments
Closed

Provide OSM node ids in nearest response #2548

vkurchatkin opened this issue Jun 14, 2016 · 4 comments

Comments

@vkurchatkin
Copy link
Contributor

vkurchatkin commented Jun 14, 2016

It would be useful to have node ids of matched segment in nearest response. To be specific, that could be used to simplify building traffic data CSV from raw GPS data

@vkurchatkin vkurchatkin changed the title :Rl Provide OSM node ids in nearest response Jun 14, 2016
@TheMarex
Copy link
Member

For an existing solution try using the match service. Since 5.2 we expose the OSM ids for each RouteLeg if you set annotations=true.

@vkurchatkin
Copy link
Contributor Author

@TheMarex already doing that, but I thought it would be nice to have an easier way to do this. If you are interested in such a feature, I would like to take a stab

@danpat
Copy link
Member

danpat commented Jun 20, 2016

@vkurchatkin Go for it :-)

@SiarheiFedartsou
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants