GP Tools — Disallow null shape, null geometry, and nil geometry where applicable

[Bud]

It seems like some GP tools behave unexpectedly when there are rows with null shapes, null geometries, and nil geometries.

For example, BUG-000122441 - Dissolving a line feature using the 'Unsplit lines' option causes ArcGIS Pro to crash if the data contains null geometry.

Idea: For tools that can't handle null shapes, null geometries, and nil geometries, throw an error instead of producing unexpected results.

[BBicking1]

Hello Bud,

the issue is already addressed.

If you encountered the same issue in 3.3 and it consistently reproduces, please log a Support issue with detailed repro steps and data, so we can investigate. Make sure to hit Send report so we receive the crash report with crash dump file.

[MargaretCrawford]

Hi @Bud, as mentioned above the specific bug you included has been fixed since Pro 2.7. 

But if you are getting unexpected results you could try to run Check Geometry on the feature class to find any problems, then Repair Geometry to correct the problems if needed.

Also, as previously discussed, development cannot provide sweeping fixes that address how all geoprocessing tools handle problems with data quality. If you are getting a crash or an Error 999999 we want to hear about the specific tool and reproducible case. So, please log this as a BUG with Esri Support. I am going to close this idea.

[Bud]

But if you are getting unexpected results you could try to run Check Geometry on the feature class to find any problems, then Repair Geometry to correct the problems if needed.

Note: Those tools don't support ST_Geometry, which is the datatype I use (Oracle).