Improve booleanOverlap docs

I am having this polygon:

const polygon = JSON.parse('{"type":"Feature","properties":{},"geometry":{"type":"Polygon","coordinates":[[[6.26950853,50.72473626],[6.26953794,50.72468996],[6.2695546,50.7246512],[6.26949169,50.72468741],[6.26948194,50.72469389],[6.26946154,50.72470787],[6.26949172,50.72474162],[6.26950853,50.72473626]]]}}');

and this bounding box:

const bbox = JSON.parse('{"type":"Feature","properties":{},"geometry":{"type":"Polygon","coordinates":[[[6.511887823915231,50.950514414615334],[6.512896634823051,50.53594214902105],[5.98503728350704,50.53594214902105],[5.98604609441486,50.950514414615334],[6.511887823915231,50.950514414615334]]]}}');

I want to know if the polygon is intesecting the bounding box

I use booleanOverlap

turf.booleanOverlap(polygon, bbox);

It returns false.

Why is that? That definetly is within the bounding box. As far as I understand it should return true?

[rowanwins]

booleanIntersects does now also exists, it’s only a recent addition and hasn’t made it’s way into the docs, but it is available via npm, that said it just returns the opposite of booleanDisjoint.

[andrewharvey]

I just ran into this issue, I was thinking that booleanOverlap was an intersection, I can see here it’s not. I think that once booleanIntersects makes it to the docs, this would clear up the issue as most people looking for intersects would use it rather than falsly trying to use overlap.