TIN to Raster fails in Python IDE stand-alone script but works in Python Window in Pro 3

[JoeLummi]

I am developing a stand-alone script.  One process - Tin to Raster - seems to fail when executed in a Python IDE (Wing IDE).  The Tin to raster tool will return a raster with nodata values even though the TIN in question has the expected values.  Oddly the code snippet works in the Python window within ArcGIS Pro v3.  From the Python code window Tin to raster will return a raster with the expected values from the TIN.

The code snips are visible from this GIS SE site.

Why does the Tin to Raster fail (and that is the only tool to fail) in a much large script?

https://gis.stackexchange.com/questions/450391/arcpy-3-tin-to-raster-returns-nodata-raster-in-stand-...

[ShaunWalbridge]

@JoeLummi it looks like it may have been a data issue based on your response on GIS.SE, was that the case and you were able to address this? Would you be able to write here what you did on GIS.SE and mark that as the accepted answer? Thanks!

[JoeLummi · Accepted solution]

The raster data and the vector data did not share the same coordinate reference system (CRS).  In ArcGIS 10.x this would have returned a 99999 error.  In Pro it apparently corrupts the file geodatabase.  Ensuring the vector and raster data shared the same CRS overcame the issue.

[ShaunWalbridge]

Glad you found a solution. If you have a process which corrupts a geodatabase, it'd be great to get that logged through support so it can be addressed in the software, but I know that's work that you have found away around and may not be a priority for you.

Cheers, Shaun

[JoeLummi]

Tin to Raster was the offending toolbox tool.