@kmadsen , can you say more about how this pr came about? Is there a reason why you want another version of TurfMeasurement.along()?

We try to keep the Turf porting as close to turf.js as possible. Per http://turfjs.org/docs/#along docs, this method takes a LineString.

If you've got a list of Point objects, TurfMeasurement.along(LineString.fromLngLats(coords)) should work for you, no?

@langsmith thanks for the reference http://turfjs.org/docs. There's a few things that are there, not in our mapbox-java that I would like to use!

The reason I was looking to simplify the interface a little is because I'm using it over here: https://github.com/mapbox/mapbox-navigation-android/pull/2802/files#diff-a4ab863681b076878569a40fd6ca5c45R36

So I'm already using along as it is.

 val point = TurfMeasurement.along(LineString.fromLngLats(segmentRoute), distanceMeters, TurfConstants.UNIT_METERS)

buy why convert back and forth from LineString?

 val point = TurfMeasurement.along(segmentRoute, distance, TurfConstants.UNIT_METERS)

So yeah, this pull request is a suggestion. There are already public interfaces to Point in there. It seems the decision was to hide the List? Maybe because turf original interface comes from javascript?