ArcCatalog – How to Solve ‘Cannot Create Topology’ Error

arccatalogarcgis-10.0errorfile-geodatabasetopology

I have a FileGeodatabase in ArcGIS 10.0 with a feature dataset and five feature classes (3 polygon shapes, 1 line shape, 1 point shape).

I'm trying to create a topology to verify some vectors. Rightclicking Feature Dataset > New... > Topology.

I'm getting the following error message in ArcCatalog:

ArcCatalog cannot create topology. The selected feature dataset does not contain any feature classes which can participate in a topology.

Browsing the internet for the error message, I found this tech article by ESRI. It tells the following:

There are several reasons for a feature class to be excluded from participating in a topology:

  • The feature class already participates in a topology or geometric network.
  • The feature class is an annotation or dimension feature class.
  • The feature class is registered as versioned.

I'm not quite sure what that means. There is no other topology or geometric network as far as I can see. What is an annotation or dimension feature class? The classes are all X;Y-coordinates only (2D). What is a versioned or registerd feature class?

I've tried checking all classes properties for something that sounds like that.

This answer to a similar question suggests to unregister the feature classes. But how?

Best Answer

My guess is your going to want one layer, vector features, no points. No crossing line situations, overlapping lines, points, polygons. Try merging layers. What type of feature are you creating a network from, streets? Do your points have an association with the streets, Do your polygons reference the features they contain or visa versa in the tables? You might need to clean up the tables and data through quality processes and processes to make all associations clean. Have you defined a logic process model for what you are trying to achieve. I think asking the right questions sometimes help arrive at the correct answers for problems. You are trying to associate feature in a single layer otherwise a process would have to run accross layers to create an association which is an added layer of complexity and would have to be programaticaly achieved within the SQL.

Related Question