You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we discussed in #64, there's already some tools can help us for OSRM debugging, e.g.
osrm-frontend: show routes, guidances
Debug map of osrm-frondend: show speeds for all ways
But for OSRM debugging, they're not enough. At least we want to see information of OSRM compiled mapdata.
Let's record and discuss our expectation/requirements here:
Requirements/Expectation:
First of all, we could have a frontend tool for visualization and a backend microservice to provide data. Every operation on frontend tool will get real data from the backend service.
First question: let's have name for both of them.
frontend tool
web based tool (osrm-frontend is a extremely good example)
can select node/way by click on the map, can show details of selected node/way/relation
can show each edge's weight/duration of a route
backend microservice
restful API for frontend call
can load compiled OSRM mapdata
The text was updated successfully, but these errors were encountered:
For the backend mircoservice, the most important task is to understand the compiled mapdata structure. The OSRM compiled mapdata looks store as plain structure in file, it may not that difficult to understand them. We could evaluate whether it's possible.
Will also load all relations on the way's two end points, such as restrictions, naturalguidances
Display endpoint's ID for this way, which is used for building graph connectivity
In OSRM, we want to have similar capability, but one important point is original way from source data is not existed in query graph. Below are some functionality I feel is helpful:
Give a OSRM node, we could get its original pbf nodeid/lat,lon
Give a pbf nodeid we could try to find OSRM node id
Give a OSRM edge, we could get related wayids/lat,lon/tags, etc
Give a wayid, we could get related OSRM edge id(s)
speed, cost, and how the result is calculated, such as static information like lua profile, dynamic information like live traffic, historical speed
As we discussed in #64, there's already some tools can help us for OSRM debugging, e.g.
But for OSRM debugging, they're not enough. At least we want to see information of OSRM compiled mapdata.
Let's record and discuss our expectation/requirements here:
Requirements/Expectation:
First of all, we could have a frontend tool for visualization and a backend microservice to provide data. Every operation on frontend tool will get real data from the backend service.
First question: let's have name for both of them.
frontend tool
backend microservice
The text was updated successfully, but these errors were encountered: