The feature class has SDEBINARY specified as the geometry storage type.The issue may occur due to one of the following reasons: The Identify tool window does not display any attribute information when a join exists from a feature class to a geodatabase table, with SDEBINARY as the geometry storage type. Problem: The Identify tool fails on an SDEBINARY feature class joined to a geodatabase table Description FeatureclassToCoverage_conversion ( inFeatures, outCover, clusterTolerance, precision ) arcpy. workspace = "C:/data" # Set local variables inFeatures =, ,, , ] outCover = "C:/output/Montgomery" clusterTolerance = 0.000656 precision = "DOUBLE" # Execute FeatureclassToCoverage and CreateLabels arcpy. # Name: FeatureclassToCvoerage_Example.py # Description: Converts several featureclasses to one coverage # Import system modules import arcpy from arcpy import env # Set environment settings env. Syntax FeatureclassToCoverage_conversion (in_features, out_cover, ) Parameter This command transfers the attribute from the route, with its' unlimited vertices, to each segment of the entire line in the coverage, each of which is 500 vertices long. In order to transfer those attributes to the individual lines in the coverage, you can run the ArcInfo Workstation command ROUTEARC at the ArcInfo Workstation command line. When a line feature class is converted to a coverage, the attributes of the lines are stored in the ROUTE subclass. At the 500th vertex, the vertex automatically becomes a node, and a new line is started. In the ArcInfo Workstation coverage data model, a line is defined by 500 vertices. In a line feature class, there is no effective limit to the number of vertices that can exist in a single line feature. If you convert such a feature class to a polygon coverage, any overlapping polygons, discontinuous polygons, or "donut holes" will be lost or changed because those types of geometries are not permitted in polygon coverages. When converting a polygon feature class with overlapping polygons, discontiguous polygons, or "donut holes", you should convert the feature class to a region coverage. The remaining feature classes will contain regions. When more than two polygon feature classes or layers are entered, only one of the feature classes can have polygons built in the output coverage. The remaining feature classes will contain routes. When more than two line feature classes or layers are entered, only one of the feature classes can have arcs built in the output coverage. To do this, choose LABEL as the type of features for the input points. If one point feature class and one polygon feature class are entered as inputs, the point feature class can represent labels for the output coverage. It is suggested you run the Create Labels tool after successfully executing this tool to ensure all polygon features have an accurate label. The default precision of the output will be DOUBLE. If the output contains a region subclass, it will be prefixed by REGION (for example, REGION.parcels). When one polygon feature class is entered as input, you can choose to build a coverage for polygons or regions. If the output contains a route subclass, it will be prefixed by ROUTE (for example, ROUTE.streets). When one line feature class is entered as input, you can choose to build a coverage for arcs or routes. Null geometries will be dropped during conversion. If no cluster tolerance is specified, a default is calculated.Ĭoverages do not support null geometries. The fuzzy tolerance of the output coverage will be the same as the cluster tolerance specified when executing this tool. The cluster tolerance acts the same as the fuzzy tolerance in ArcInfo Workstation. Creates a single ArcInfo Workstation coverage from one or more input feature classes or layers.