Blind spots and large balcony overhang?

[sanzoghenzo]

Hi there!

I know that I can use the Blind Spot slots to account for overhangs, but I have some troubles configuring it in a good way.

My case: south-facing, all-height window and an hoverang (upstairs balcony) of 1.1m that spans almost 4m to the left of the window and only 40cm to the right.
After some calculations, I have a 30° range in elevation, so using the maximum elevation for the "above" setting is a bit overkill.
I thought about splitting the blind spot into multiple slots, but there are only 3, so I cannot be that precise. Maybe I'm worrying for nothing, but since I also have 3 buildings inside the FOV, if I would like to describe the full reality outside my window I'm out of luck.

Can the blind spots slots be dynamic, something like a table with the ability to add rows?

[jrhubott]

I want to flag one thing before you build this: the way the three slots combine will break your plan if you try to split that 30° band across two of them.

A slot doesn't carry an elevation range today, just a single elevation value and an elevation_mode of above or below, so each one is a one-sided cut. And multiple slots combine as a union rather than an intersection: the containment check runs any() across every slot you've configured. Set one slot at above 25 and another at below 55, hoping to land on the 25-55 band, and what you actually get is 0-90 suppressed. The two half-planes union together and cover the whole elevation range all day, with nothing in the UI telling you it happened. I wanted to flag that specifically since it's exactly the workaround you were about to try.

Given that, here's the honest answer for your overhang today: one slot, mode above, elevation set to the bottom of your 30° band, the angle where the balcony first starts shading the glass. You lose the top of the band since the slot keeps suppressing above it too, but that's usually fine for an overhang: above that band the sun is even higher and the balcony is still in the way. It's a workaround, not a real fit for your geometry, so check it against your own numbers rather than taking mine on faith.

Your asymmetric spread, 4m to one side and 40cm to the other, is a different story: it's expressible today, no workaround needed. Left and right are independently signed gamma from the window's center, meaning you can set a wedge that's heavily skewed to one side rather than symmetric. Just remember it's measured from the center rather than either edge; on a wide window like yours, you compensate by hand when picking the edge angles.

For the buildings, and for a real min/max elevation band instead of the one-sided cut, I filed #1210 to cover both. Raising the slot count, or making it dynamic, is genuinely low-effort: glare zones already run 4 slots through the same engine, and everything downstream (schema, UI, sensors, diagnostics, translations) is already written to not care how many slots there are. The bounded elevation band is more involved, but the same issue tracks it.

For details, see the Blind Spot wiki page.

[sanzoghenzo]

Sorry I wasn't been clear before, but the 30° is not the band between "below" and "above": it's the difference between the "above' threshold at the leftmost corner (4.4m horizontal distance and 2.7m height => 31.45°) and the same threshold in front of the window (the 1.1 horizontal distance, 2.7m height => 69.78°).

Now that I think of it, a linear interpolation between known points (the corners of the overhangs) would make much more sense for this!