Steve Bennett

Have you tried using the `on('error')` event? I haven't, but in theory you could parse the description to find out which layer caused it.

Oh, I didn't know about this ticket! Me, I would love more string-handling functions: - left - right - split - titlecase (yes I know it's difficult to do in...

Agree with all that. > Point possibly within the polygon. This wording is a little clumsy, perhaps "Point being tested." > * @param {Feature} polygon Polygon to search within. Probably...

Hmm, I don't see anything in [the GeoJSON spec](http://geojson.win/#section-3.1.4) prohibiting LineStrings consisting of the same position twice. Or maybe I misunderstood your meaning.

I'm not sure that's a strong argument against ever returning a zero-length linestring. It's just up to the user to not pass that result to other places where it might...

Ah, I have eventually discovered that `bboxClip` does some, but not all of this: - only handles bbox, not arbitrary polygons - does not handle Point/MultiPoint (easy to implement) -...

I don't think `mask` and `difference` would achieve the same thing. In any case, operations using a general polygon (as opposed to a bbox) are orders of magnitude slower, and...

Yeah, well, I did. But on further reflection, a general clipping function and a bbox clipping function are probably best kept as two separate concepts.

Well, this is bizarre, I've just discovered issue #1565. Apparently I made exactly the same suggestion in January 2019. I have no memory of this. That issue got a bit...

Looks like a bug/limitation, it only works correctly with Point features.