No mistake, you are correct. there is a bug in the describe function (on version 10.0, 10.1 and 10.2) Hopefully they will address it.Here is the tech support info if it helps:[#NIM088547 Using the describe properties to pull the spatial reference on a TIN fails with AttributeError: DescribeData: Method SpatialReference does not exist.]
I added this incident to the list of affected users. In the bug report, I also added the properties extent, MExtent, and ZExtent to the list of unsupported dataset properties for TINs.
For a work-around, this is cumbersome, but you could create a new shapefile or feature class, setting the spatial reference to that of the TIN, then query the spatial reference properties of the new shapefile. For instance:
relPath = os.path.dirname (sys.argv[0]) # script path tin = os.path.join (relPath, "lido_TIN") arcpy.CreateFeatureclass_management (relPath, "abc.shp", "POINT", spatial_reference = tin) shp = os.path.join (relPath, "abc.shp") desc = arcpy.Describe (shp) arcpy.AddMessage ("spatialReference: " + str (desc.spatialReference.name)) arcpy.Delete_management (shp)
R_