Latest Contributions by JimO_Leary1

Yes, that works. You still have to join the full path name to the feature class name, but you don't have to set the env.workspace. Thanks ... View more

This code return  "IOError: Roads does not exist." ----------------code BEGINS---------------------- from arcpy import * env.workspace = r"C:\folder1\USA.gdb" # Get a list of the feature classes in the current workspace lstFeatureClass = arcpy.ListFeatureClasses() # Make an empty list to hold the feature classes in the current GDB lstFeatureClassStored = [] # Populate the list with the feature classes from the current workspace for featureClass in lstFeatureClass:     lstFeatureClassStored.append(featureClass) # Change the workspace env.workspace = r"C:\folder2\Iowa.gdb" # Loop through the stored feature classes. Here is where the exception is raised for featureClassStored in lstFeatureClassStored:     desc = arcpy.Describe(featureClassStored)     print desc.Name --------------------code ENDS--------------------------- However, I think it is because the lstFeatureClassStored only stores the name of the feature class, not the feature class object itself, and when I change the environment it doesn't know "Roads". By adding the whole path to the feature class as below, I can then loop through the list and access each feature class by the absolute file name. -------------------code BEGINS--------------------------- import arcpy from arcpy import * pathToFirstWorkspace = r"C:\folder1\USA.gdb" env.workspace = pathToFirstWorkspace lstFeatureClass = arcpy.ListFeatureClasses() lstFeatureClassStored = [] for featureClass in lstFeatureClass:     # Store the absolute path to the feature class inside the GDB     pathToFeatureClass = r"%s\%s" % (pathToFirstWorkspace,featureClass)     lstFeatureClassStored.append(pathToFeatureClass) # Change the workspace env.workspace = r"C:\folder2\Iowa.gdb" # Access the feature class by the absolute path to the GDB for pathToFeatureClass in lstFeatureClassStored:     desc = arcpy.Describe(pathToFeatureClass)     print desc.Name --------------------code ENDS----------------------------- So this works, but it still doesn't answer my question, is there a way to get a listing of classes without using env.workspace and ListFeatureClasses()? It seems very limiting to have to set the environment when you want to know what is in a geodatabase. Thanks ... View more

Thanks for that answer, Jake. It worked for me. ... View more

Thanks Bruno. I think this refers to creating a geodatabase, though, not running the Create Spatial Type, which would actually create the ST_GEOMETRY type. ... View more

The layer is a table in Oracle Spatial, and is not joined to any other table, and is not a view. It is not versioned. The Data Type for the geometry column is SDO_GEOMETRY. When I execute the following query: select t.x, t.y from fire_stations, table(sdo_util.getvertices(geom)) t ...I can see x and y rows for each feature. However, when I use ArcMap 10.2 to export the table into a file GDB, I cannot add the file GBD table to ArcMap, and when I try to view it in FME Data Inspector, FME tells me that it has no geometry. One difference between this database and the databases for which I can add features to ArcMap is that the tables in this database were created by FME. However, FME is very sophisticated and should take care of all details needed when creating a spatial table. For example, it correctly inserts a record into ALL_SDO_GEOM_METADATA. So I don't know what the difference is. Thanks for your help. ... View more