James Beard

> it should just return an empty FeatureCollection instead of throwing an error Thanks @stevage. Have updated the title of the issue based on the above. Will see if we...

Hi @wtchen. Are you still looking in to this? No worries if not. Let us know though so I can unassign you in case someone else would like to take...

Thanks for raising this @kevinschaich. To what extent are you requesting support? Let's say the spectrum runs from "let people provide z coords but ignore them for calculations" all the...

Hi @Harpush. Can you please see if the behaviour has changed with the latest alpha? We have changed bundlers which may have had an effect.

Not sure if I need to request a review from yourselves. However noticed that there are several recent PRs that look like they're waiting on automated build results? From May...

This PR should be good to go now. Uses geodesy 2.3.0. Bundle size increases in my build from 568083 to 584415 (about 3%).

Hi @Harpush. Could you please try one of the recent alpha releases to see if they fix this issue for you? We've changed around the way Turf is packaged for...

Hi @maral. Thanks for looking into this. If possible we should avoid converting back and forth between mercator projection (given its distortion with latitude). Is it possible there's a way...

Hi @rd-atmosphericg2 Would you mind describing how you see this behaving in relation to the example map below? The geojson to produce this is generated from the bigMatrix test case,...

Thanks for providing that detail. So, is the crux of your problem that _your_ data doesn't look like the test case data above? I haven't been able to get your...