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

where does osrm store nodes and edge data in the source code. #6091

Closed
shubham121297 opened this issue Jul 28, 2021 · 4 comments
Closed

where does osrm store nodes and edge data in the source code. #6091

shubham121297 opened this issue Jul 28, 2021 · 4 comments

Comments

@shubham121297
Copy link

where does osrm store nodes and edge data in the source code. Like in which file of Project-OSRM
/osrm-backend.which file contains the graph ?

@mjjbell
Copy link
Member

mjjbell commented Jul 28, 2021

The graph representation appears in OSRM source code in many places and in many forms, so without knowing what you're doing it might not be helpful.
I'd suggest taking a look at these two wiki pages to understand the OSRM concepts:

@shubham121297
Copy link
Author

thank you for your response @mjjbell .I want to find out the variable or data structure in which the edges are stored .I want to make changes in that ds to show the information like until which date the particular edge is blocked or is to be avoided ,(if any edge due to natural disaster, or some sports event is blocked) and return that information in the response in route leg objects. And make an application so that if any route contains that edge ,i will show its information binded in a popup to that edge.I guess you can get me now.

@shubham121297
Copy link
Author

@mjjbell ,@danpat waiting for your response.Thanks.

@mjjbell
Copy link
Member

mjjbell commented Aug 2, 2021

If I understand correctly, you want to annotate the returned route with additional context (as opposed to say, using external data sources to alter the routing results).

You can already use annotations=nodes to annotate the route result with the OSM node IDs for each coordinate on the route.

#5968 adds the same functionality for OSM ways, so that could act as a starting point for your use-case with edges. You could then match these way IDs to your external dataset for displaying information in your app.

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

No branches or pull requests

2 participants