I'm using 7.4 BC3. I have a feeling this issue has to do with the geo-bounding box in general. Because some of these polygons can be pretty complex, I'd imagine that we'll start to see this error more and more as the feature gets utilized. The error shown below doesn't provide any good options really either. Is there anything we can do here? I'm worried this will dramatically affect the experience of this feature. Every time you zoom in the error continues to pop up as well.

Separately, it feels to me like filtering the geometry should have also filtered out the shape from the layer I was interacting with. In the GIF below, I would have expected all districts to also be filtered out and not just the underlying data. Is there a way we can filter out the points and the joined field as well? This feels less like a bug but more of a UX issue.

Here's what I'm using:
The data set is Get It Done Requests year-to-date csv from here.
You'll need to tweak the mappings and ingest pipeline when uploading via file upload

Add this to the mapping:

"location"{
   "type":"geo_point"
}

and this processor to the pipeline

{
  "processors": [
    {
      "set": {
        "field": "location",
        "value": "{{lat}},{{lng}}"
      }
    }
  ]
}

Due to #45520, I can't seem to make the actual export but here are the original objects I imported from 7.3:
get-it-done_saved_objects.zip

This was the geojson file I uploaded for san diego counties with the sd index pattern:
sd.geojson.zip

cc: @bcamper