topic Problem with arcpy.describe in Python Questions

Problem with arcpy.describe

Anonymous User — Tue, 11 Aug 2015 11:58:03 GMT

Dear all

I am facing the next problem:

- I have a feature datasatet and a table in a geodatabase, both with the same name (lets say "object1"). It seems not to be any restriction for this.

- However, when I try to get the description (arcpy.Describe) using this common name "object1" I always get the description of the feature dataset and I am not able to access to the description of the table.....

Is there any workaround?

Thank you in advance

Jesús de Diego

Re: Problem with arcpy.describe

WesMiller — Tue, 11 Aug 2015 12:43:29 GMT

Is your table inside your dataset with the same name? You need to provide the full path "database\dataset\table"

Re: Problem with arcpy.describe

Anonymous User — Tue, 11 Aug 2015 13:44:36 GMT

Hi Wes

I believe that tables can't be added to feature datasets....Anyway, in my case, the table is outside any feature dataset.

Following your path example:

Path for the table:

"Database\Table"

Path for the Feature Dataset:

"Database\Feature Dataset"

.... the same....

Thank you anyway

Jesús de Diego

Re: Problem with arcpy.describe

XanderBakker — Tue, 11 Aug 2015 13:51:48 GMT

True, tables do not have spatial data and cannot be stored in a feature Dataset. I would recommend renaming the table and make sure that all the elements in your gdb have a unique name. Also if you would want to start a cursor on the table, it will not find the table (since it will encounter the feature dataset with that name first) and throws an error.

Re: Problem with arcpy.describe

Zeke — Tue, 11 Aug 2015 15:21:09 GMT

I didn't think you could have any elements with the same name in a gdb.

Re: Problem with arcpy.describe

XanderBakker — Sat, 11 Dec 2021 23:03:28 GMT

In fact you can:

... and:

... but you can't have a table and a featureclass with the same name or have two featureclasses with the same name although the reside in different feature datasets.

The Describe functionality can be applied to both the featureclass and the feature dataset:

>>> desc1 = arcpy.Describe(r"D:\Xander\GeoNet\Describe\test2.gdb\SomeName")
>>> desc1.datasetType
u'FeatureDataset'
>>> desc2 = arcpy.Describe(r"D:\Xander\GeoNet\Describe\test2.gdb\SomeName\SomeName")
>>> desc2.datasetType
u'FeatureClass'

... for the table and feature dataset, you can't since they are referenced the same way. If the Featureclass would reside outside the feature dataset, the same would apply for the featureclass, not being able to be described:

>>> desc3 = arcpy.Describe(r"D:\Xander\GeoNet\Describe\test.gdb\Information")
>>> desc3.datasetType
u'FeatureDataset'

Re: Problem with arcpy.describe

BlakeTerhune — Sat, 11 Dec 2021 23:03:31 GMT

With this in mind, you could either rename your geodatabase table and dataset so they are unique, or make a table view of the table using a where clause that will not return any rows (for speed/performance) and do a describe on the view.

where_clause = "1=0"  ## Intentionally will not return any rows
arcpy.MakeTableView_management(inTable, "outTableView", where_clause)
descView = arcpy.Describe("outTableView")
print descView.name, descView.datasetType

Re: Problem with arcpy.describe

XanderBakker — Wed, 12 Aug 2015 11:39:22 GMT

If renaming the table is not an option than the snippet provided by Blake T will offer the best solution.

Re: Problem with arcpy.describe

JoshuaBixby — Sat, 11 Dec 2021 23:03:33 GMT

Not saying this is any better than Blake T's approach, but there is an arcpy.Describe only approach:

gdb = #path to geodatabase
for child in arcpy.Describe(gdb).children:
    if child.name == 'someName' and child.datasetType == 'Table':
        desc = child
        break