Open redcic75 opened 1 year ago
@redcic75 Ran into the same issue as you. Great that you found a fix. Usually you can fork the project and create a fix on you own repository. You can then create a PR from your fork to this repo and link that PR with this issue. But if you want I can do that for you.
What I additionally saw is, that a related issue was reopened: https://github.com/manuelbieh/geolib/issues/129
@timvahlbrock : Thanks for your message. I'm working on other subjects at the time but feel free to use my proposed code to create the PR if you need it.
@redcic75 Ran into the same issue as you. Great that you found a fix. Usually you can fork the project and create a fix on you own repository. You can then create a PR from your fork to this repo and link that PR with this issue. But if you want I can do that for you.
@timvahlbrock : Thanks for your message. I'm working on other subjects at the time but feel free to use my proposed code to create the PR if you need it.
@redcic75 Ran into the same issue as you. Great that you found a fix. Usually you can fork the project and create a fix on you own repository. You can then create a PR from your fork to this repo and link that PR with this issue. But if you want I can do that for you.
Already happened. Opened it for the other Issue, as there was more traffic. Did some cleanup and mentioned you as co-author.
Hello @manuelbieh ,
I've just noticed that the fix you've commited after issue #227 and pushed does not deal with all the problematic cases. When we call
getDistanceFromLine
we still getNaN
whenpoint === startLine
and whenstartLine === endLine
.This fix in
getDistanceFromLine.ts
should correct this issue:I've written the following test. They fail with the current version of the code but they pass with the above fix:
I don't have the access right to push this modification on a new branch on your repo.