Open jlaura opened 11 years ago
Fixed using the proposed fixed with 2 caveats:
This error is still persisting and is being tagged as an enhancement.
The workaround is: Export as a shapefile to for sequential FID. Delete the OID field from the shapefile (it may be necessary to create a filler field to ensure that the shapefile contains FID, shape, 1 other field). Export the shapefile as a featureclass back into the geodatabase.
In the cluster analysis tool it is not possible to hardcode the necessary offset for using a shapefile vs. using a featureclass. Currently the tool works with OIDs (featureclass) and uses a hardcoded '-1'.
Proposed fix is to set the offset to '-n', where 'n' is 0 by default and set to 1 if the workspace is a geodatabse..