nearestPointOnLine deviation
Open
Nobody has claimed this yet.
@turf/nearest-point-on-line
- Dominant language
- TypeScript
- Stars
- 10.5k
- Forks
- 1k
- Avg merge
- 1h 11m
- Merged PRs (30d)
- 4
Description
Here is an small example.
Some points at the line were calculated right on point and
some were calculated with a deviation.
I wanna know what's the reason for the deviation,
for me it seems to be to big for an round-off error.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported deviation in the linked JSFiddle, focusing on the nearestPointOnLine entry point named in the issue. Compare the calculated points with the input line and determine whether the behavior is an algorithmic error or expected precision; document the cause and confirm the result with a focused reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100