Need help to optimize potentially erroneous spatial SQL query

sql sql-server elasticsearch spatial-query spatial-index

What if you did the calculation each time you added a new shape, then stored just the intersections in a table? Now your query is instantaneous.

CodeHunter