I am interested in extending GraphHopper for indoor routing and have a bunch of queries around the same:
I saw the existing new feature request #646. Has it been taken up by someone?
I had asked for suggestions about Indoor Routing on SO. Peter pointed me to the open issue #82 on area routing which is pretty old. Is any work being done on that?
I like Peter’s suggestion of teaching LocationIndexTree to return points within the room boundaries of the query point. From what I have seen of GraphHopper code, one way of doing that would be to associate area information with nodes of the index tree and have an area aware edge filter. Any comments?
I hope I have categorised the topic correctly. Searching for topics on ‘indoor’ did not get me any results.
Have not thought it through. A simple workaround would be to have the normal routes through an area and then some routes for the ‘maximum extent of the room’, that way you don’t need to change anything, but not sure about the disadvantages.
I thought about that but there is no way to ensure that some path outside the area will not be nearer to a point than a route inside. Another way is to surround every obstacle with a route so no path ever crosses the obstacle. That won’t require any change but I don’t know if it will scale and it does not seem very elegant. Still have to think it through though.
Hmmh, indeed that seems all a bit too hackish and a proper area selection when doing the location lookup would be better. (Or maybe a different feeding technique into the location index, not yet tried & thought through)