Finding path of global skeleton sometimes fails

[jacobeverist]

When finding a path between points on the global skeleton, it sometimes fails because the start and target node are the same. The big question is why is the same node for the start and finish being selected, should we check for this case or let it continue to error out until we find the root cause.

[jacobeverist]

This situation occurs also if the start and end nodes are very very close to each other.

As in:
(2.10, 1.35)
(2.22, 1.36)

Noticed that the startNode is never included in the final path. This could also be the cause of the related issue #8