We have real large geospatial tables. Not having an option to turn MakeValid
off will kill our applications’ performance as indexes are essential.
For a simple query, the disk reads are 100x more for a query including the
MakeValid. Hence, the cpu resources required are multifold too.
Yes, pl
I think we can remove MakeValid from the queries entirely.
The problem is that if the table contains invalid geometries, the entire
query will fail.
Best regards,
Tamas
Seth G ezt írta (időpont: 2019. szept. 7., Szo,
21:35):
> Hi,
>
> Good question. This is a fairly new change as part of
> ht
Hi,
Good question. This is a fairly new change as part of
https://github.com/mapserver/mapserver/issues/5781 from April this year.
In SQL Profiler I seem to get GEOM.STIntersects for WFS requests and
GEOM.MakeVaid().STIntersects for WMS.
MakeValid does appear to stop the index being used. Do y
Hello,
I noticed that when MapServer issues the query to MS SQL Server, it appends
a .MakeValid() tag to the geometry field, which makes data access highly
inefficient as no spatial indexes can be used when the MakeValid() is used.
Here is the query that is being produced:
SELECT
convert
