James Beard

Took a look at the git blame for this. The variable has been in there since day 1, and (though not conclusive) even Typescript reckons oneInside can only be false,...

Hi @PereUbu7. Understand it's been a while since you proposed this. Are you still interested in getting this merged with some assistance from us?

This could well be the difference between spherical and ellipsoidal calculations. Using the two different methods in geopy produces the results mentioned above: using great_circle gives (4353m) vs geodesic (4367)....

Hi @JamesLMilner @rowanwins @twelch . Will take a look at this if you'd like to assign my way.

The length accuracy part of this should be addressed by #2476. User needs to pass in the appropriate ellipsoid for underlying distance() calculation to use.

Resolved by PR #19

Possible workaround [here](https://github.com/vercel/next.js/issues/59344#issuecomment-1846128759) @darenmalfait Let us know if that helps.

Hi @bernatfortet and @darenmalfait. Just released a new alpha that changes our packaging approach somewhat. Would you mind checking to make sure it isn't a step backwards for you? [7.0.0-alpha.114](https://www.npmjs.com/package/@turf/turf/v/7.0.0-alpha.114)

Thanks @bernatfortet Will mark this resolved for now and include something in the 7.0.0 release notes to that effect.

Thanks for taking a look at this @Leffe108. Have made a request above if you could expand the tests to cover some more of the functionality that would be fantastic.