laptop and a wrench

Bug

ST_INTERSECT provides wrong results in ArcGIS for Desktop 10.4.1 and ArcGIS Desktop 10.5 when compared with the same SQL query run on a 10.1, 10.2.x or 10.3.x geodatabase.

Last Published: August 21, 2017 ArcSDE/Enterprise Geodatabase
Bug ID Number BUG-000104547
SubmittedApril 18, 2017
Last ModifiedAugust 26, 2025
Applies toArcSDE/Enterprise Geodatabase
Version found10.4.1
Version Fixed10.5.1
StatusFixed

Workaround

Work with a different SRID which spatial reference is more accurate altering geometry using function ST_TRANSFORM. Step by step: 1. Have a custom SRID from a spatial reference 2154 using XY tolerance and resolution more accurate.From ArcCatalog > crate a new feature class > set name 'C300008' > put spatial reference 2154 > Alter XT tolerance, from 0.001 à 0.00001, uncheck 'Accept default resolution' > don't change XY resolution value (0.000005) and then leave the default settings. 2. Get AUTH_SRID value from feature class named 'C300008' using following SQL Query:Select l.TABLE_NAME, l.SRID, sr.AUTH_SRID, sr.xycluster_tol, sr.srtext from layers l INNER JOIN spatial_references sr ON l.SRID=sr.SRID where l.table_name in ('C300008','ENVOI1');In my sample, AUTH_SRID value is equal to 300004. So now we used it under ST_TRANSFORM function. 3. Using the following Query:select sde.st_astext(sde.st_intersection(sde.st_transform(sde.st_geometry(bpp, 2154),300004),sde.st_geometry(ilo, 2154))) into res from DUAL;Careful to use ST_TRANSFORM as the first parameter of the function ST_INTERSECTION like above.

Steps to Reproduce

Bug ID: BUG-000104547

Software:

  • ArcSDE/Enterprise Geodatabase

Get notified when the status of a bug changes

Download the Esri Support App

Discover more on this topic

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options