Merging of consecutive edges with same direction not always desirable

[loopRW]

two consecutive edges with same direction will be merged as one edge and the length will be read till the end of the merged edge. This is not desirable when there is a barrier or stop between the two (e.g., a door).

[dsato80]

Then we need to add an attribute to the node to prevent merging or need to add code to check surrounding obstacles (based on POI), in this case a door, not to merge two edges. What do you think?

[loopRW]

If the goal is to make poi based destinations, we might as well do poi based obstacles

[chengxiong-ruan]

switching to a more general solution might help as well. geocoding each poi
instead of making it as a node, reporting obstacle poi on route.

On Sat, Aug 20, 2016 at 11:19 AM, loopRW notifications@github.com wrote:

If the goal is to make poi based destinations, we might as well do poi
based obstacles

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#40 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGT2S17q8crraudcyGD0JHkjFZUTqUT7ks5qhxrpgaJpZM4Joklt
.