topic Re: Connect to Geodatabase Featureclass and/or shapefile in ArcObjects SDK Questions

Connect to Geodatabase Featureclass and/or shapefile

GinoMellino — Mon, 11 Feb 2013 02:17:44 GMT

Hi All,

This is probably very simple. I can load a geodatabase featureclass with IWorkspace::OpenFromFile and the FileGDBWorkspaceFactory CoClass and likewise with ShapefileWorkspaceFactoryClass for shapefiles...is there a way to load both with the same generic workspace factory or do I have to set a different one based on what is selected in my custom Add data dialog?

Thanks in advance
Gino

Re: Connect to Geodatabase Featureclass and/or shapefile

LeoDonahue — Mon, 11 Feb 2013 02:39:26 GMT

This is probably very simple. I can load a geodatabase featureclass with IWorkspace::OpenFromFile and the FileGDBWorkspaceFactory CoClass and likewise with ShapefileWorkspaceFactoryClass for shapefiles...is there a way to load both with the same generic workspace factory or do I have to set a different one based on what is selected in my custom Add data dialog?

There is a generic workspace factory, it's called IWorkspaceFactory. Many other concrete classes implement this Interface, such as the two types you mentioned.

Re: Connect to Geodatabase Featureclass and/or shapefile

AlexanderGray — Mon, 11 Feb 2013 16:45:03 GMT

The interface is generic (IWorkspaceFactory) but the classes that implement it are all specific to the data type. There isn't a workspaceFactory Factory class that creates the one you need based on the data type you input or that figures out the data type provided in the file path (.shp, .gdb or .sde.) To make it would be easy but of limited value.

Re: Connect to Geodatabase Featureclass and/or shapefile

LeoDonahue — Mon, 11 Feb 2013 18:08:48 GMT

The interface is generic (IWorkspaceFactory) but the classes that implement it are all specific to the data type.

You are correct sir.

I was being intentionally less obvious to the OP because I thought maybe they would see the difference between Interfaces and Classes and realize the answer to their question.

Re: Connect to Geodatabase Featureclass and/or shapefile

AlexanderGray — Mon, 11 Feb 2013 18:20:45 GMT

You are correct sir.

I was being intentionally less obvious to the OP because I thought maybe they would see the difference between Interfaces and Classes and realize the answer to their question.

I didn't mean your answer was incorrect or anything. I just got thinking about the class factory design pattern, in which the factory class decides what type of object to create. This is different from the workspace factory since you have to know what type of workspace you want (shapefile, file gdb, sde, etc.) before creating a specific type of workspace factory to get that same type of workspace. It strikes me as somewhat going against what the factory design pattern is supposed to be. Factories are supposed to decide the specific class type for you...

Re: Connect to Geodatabase Featureclass and/or shapefile

GinoMellino — Mon, 11 Feb 2013 21:58:26 GMT

Hi all and thanks for the replies.

I did recognise that IWorkspaceFactory was an interface but must apologise as I lack a good understanding of programming. I thought that there may be a generic coclass which implements IWorkspaceFactory which I could use. Thanks Alexander for clearing this up.

I am trying to use a GXDialog to add data of any kind to a map, which is why I need to be able to handle the user selecting Shapefile/GDB/SDE data sources. Is there a recommended way of handling these different types of data? Currently as a work around I test for the .shp extension to determine if its type.

Again, Thanks for your help

Re: Connect to Geodatabase Featureclass and/or shapefile

LeoDonahue — Sun, 12 Dec 2021 02:16:25 GMT

There is a really cool thing called the ArcObjects API. Granted, I can't hold it against anyone who tries to make sense of the ArcObjects .NET API, because you can't find anything without expanding, expanding, expanding..

This is a Java example, so sorry for that.

I opened eclipse and used the new project wizard to create a console application. Then I used the sample ArcGIS snippets for listing feature classes of a FGDB workspace.

Notice in listFeatureclass, they use the concrete class FileGeodatabaseWorkspaceFactory to create new FileGeodatabaseWorkspaceFactory.

Notice in listFeatureclass2, we're using the WorkspaceFactory class .. what? What kind of black magic is that?

Give them a try, pass in a file name of "c:\\myfgdb.gdb" and see what happens.

    public static void listFeatureclass(String file) throws java.net.UnknownHostException, java.io.IOException {
        com.esri.arcgis.datasourcesGDB.FileGDBWorkspaceFactory factory = new com.esri.arcgis.datasourcesGDB.FileGDBWorkspaceFactory();
        com.esri.arcgis.geodatabase.IWorkspace workspace = factory.openFromFile(file, 0);
        com.esri.arcgis.geodatabase.IEnumDataset enumDataset = workspace.getDatasets(com.esri.arcgis.geodatabase.esriDatasetType.esriDTFeatureClass);
        com.esri.arcgis.geodatabase.IDataset ds = null;    
        ds = enumDataset.next();
        while(ds != null){
            com.esri.arcgis.geodatabase.IFeatureClass fClass = new com.esri.arcgis.geodatabase.IFeatureClassProxy(ds);
            int fCount = fClass.featureCount(null);
            System.out.println("FeatureClass "+ fClass.getAliasName() +" has "+fCount+ " features.");
            ds = enumDataset.next();
        }
    }
    
    public static void listFeatureclass2(String file) throws java.net.UnknownHostException, java.io.IOException {
        com.esri.arcgis.geodatabase.WorkspaceFactory factory = new com.esri.arcgis.geodatabase.WorkspaceFactory(new com.esri.arcgis.datasourcesGDB.FileGDBWorkspaceFactory());
        com.esri.arcgis.geodatabase.IWorkspace workspace = factory.openFromFile(file, 0);
        com.esri.arcgis.geodatabase.IEnumDataset enumDataset = workspace.getDatasets(com.esri.arcgis.geodatabase.esriDatasetType.esriDTFeatureClass);
        com.esri.arcgis.geodatabase.IDataset ds = null;    
        ds = enumDataset.next();
        while(ds != null){
            com.esri.arcgis.geodatabase.IFeatureClass fClass = new com.esri.arcgis.geodatabase.IFeatureClassProxy(ds);
            int fCount = fClass.featureCount(null);
            System.out.println("FeatureClass "+ fClass.getAliasName() +" has "+fCount+ " features.");
            ds = enumDataset.next();
        }
    }

Re: Connect to Geodatabase Featureclass and/or shapefile

LeoDonahue — Sun, 12 Dec 2021 02:16:27 GMT

I just got thinking about the class factory design pattern, in which the factory class decides what type of object to create. This is different from the workspace factory since you have to know what type of workspace you want (shapefile, file gdb, sde, etc.) before creating a specific type of workspace factory to get that same type of workspace. It strikes me as somewhat going against what the factory design pattern is supposed to be. Factories are supposed to decide the specific class type for you...

Are you talking about the Factory Method pattern? If yes, then you create an interface for creating objects, and let subclasses define what type of object is being created.

You could do something lame like this, but don't.

com.esri.arcgis.datasourcesfile.ShapefileWorkspaceFactory shp = new com.esri.arcgis.datasourcesfile.ShapefileWorkspaceFactory();

com.esri.arcgis.datasourcesGDB.FileGDBWorkspaceFactory fgdb = new com.esri.arcgis.datasourcesGDB.FileGDBWorkspaceFactory();

            createWorkspace("d:\\somefolder",shp,"someshapefilename");
            createWorkspace("d:\\somefolder\\somegeodatabase.gdb",fgdb,null);

    public static void createWorkspace(String filePath, IWorkspaceFactory temp, String shapefileName){
        
        try {
            if(temp.getWorkspaceType() == esriWorkspaceType.esriFileSystemWorkspace){
                com.esri.arcgis.geodatabase.WorkspaceFactory wsf = new com.esri.arcgis.geodatabase.WorkspaceFactory(temp);
                com.esri.arcgis.geodatabase.Workspace work = new com.esri.arcgis.geodatabase.Workspace(wsf.openFromFile(filePath, 0));
                com.esri.arcgis.geodatabase.IFeatureClass featureClass = work.openFeatureClass(shapefileName);
                System.out.println(featureClass.getAliasName() + " " + featureClass.featureCount(null));
            }
            
            if(temp.getWorkspaceType() == esriWorkspaceType.esriLocalDatabaseWorkspace){
                com.esri.arcgis.geodatabase.WorkspaceFactory factory = new com.esri.arcgis.geodatabase.WorkspaceFactory(temp);
                com.esri.arcgis.geodatabase.IWorkspace workspace = factory.openFromFile(filePath, 0);
                com.esri.arcgis.geodatabase.IEnumDataset enumDataset = workspace.getDatasets(com.esri.arcgis.geodatabase.esriDatasetType.esriDTFeatureClass);
                com.esri.arcgis.geodatabase.IDataset ds = null;    
                ds = enumDataset.next();
                while(ds != null){
                    com.esri.arcgis.geodatabase.IFeatureClass fClass = new com.esri.arcgis.geodatabase.IFeatureClassProxy(ds);
                    int fCount = fClass.featureCount(null);
                    System.out.println(fClass.getAliasName() +" has "+fCount+ " features.");
                    ds = enumDataset.next();
                }
            }
        } catch (AutomationException e) {
            // TODO Auto-generated catch block
            e.printStackTrace();
        } catch (IOException e) {
            // TODO Auto-generated catch block
            e.printStackTrace();
        }
        
    }

Re: Connect to Geodatabase Featureclass and/or shapefile

AlexanderGray — Tue, 12 Feb 2013 16:43:31 GMT

Are you talking about the Factory Method pattern? If yes, then you create an interface for creating objects, and let subclasses define what type of object is being created.

Yes I was talking about Factory method pattern. I was thinking something along those lines. A class where you just pass a string in the constructor, no workspace factory, and it spit out the appropriate workspace. It seems like a recipe for trouble for not much gain. I really don't feel like maintaining the code for every possible type of workspace including some that don't exist yet. Now if that sort of class was provided as part of the API, like an actual factory class, it would abstract a lot of the things you need to do and would reduce programmer error.

WorkspaceFactory Class
ctor workspaceStr
    Determine type of workspace needed
    Create workspace factory for type

workspace property
    Open workspace
    return workspace

Re: Connect to Geodatabase Featureclass and/or shapefile

LeoDonahue — Tue, 12 Feb 2013 17:51:00 GMT

Yes I was talking about Factory method pattern. I was thinking something along those lines. A class where you just pass a string in the constructor, no workspace factory, and it spit out the appropriate workspace.

You would not want to pass a string, because that is not type safe. What if someone passed in a misspelled string?

Re: Connect to Geodatabase Featureclass and/or shapefile

AlexanderGray — Tue, 12 Feb 2013 18:18:11 GMT

You would not want to pass a string, because that is not type safe. What if someone passed in a misspelled string?

Not a string containing the type, a string containing the path to the workspace. Based on the type of string, *.gdb, *mdb, *.sde etc. or the contents of the directory (info sub dir) or shapefiles, etc. the code decides which workspace factory is appropriate to instantiate.

Re: Connect to Geodatabase Featureclass and/or shapefile

LeoDonahue — Tue, 12 Feb 2013 18:33:08 GMT

right the constructor receives the string param that then decides what kind of workspace to create. What if I passed in the string "taco"?

Re: Connect to Geodatabase Featureclass and/or shapefile

AlexanderGray — Tue, 12 Feb 2013 19:10:53 GMT

Well same as if you try openFromFile with string "taco" on a valid workspace factory. In this case, failure just comes earlier. The whole point is validating the string before you even create the workspace factory. In the process of trying to figure out the type of workspace there is a step that checks if it is a valid directory or file, if not throw an argument exception. If after trying a bunch of combination, the code still can't figure out a valid workspace type, throw an argument exception.

Re: Connect to Geodatabase Featureclass and/or shapefile

LeoDonahue — Tue, 12 Feb 2013 20:01:42 GMT

But wouldn't you still want to pass an interface type to this factory method that decides how to return a workspace, rather than a string?

There is more than one esriWorkspaceType.esriFileSystemWorkspace, which could be shapefile, in memory, etc.

Just as there is more than one type of esriWorkspaceType.esriLocalDatabaseWorkspace

If you declare a IWorkspaceFactory variable as a concrete type, then that type becomes the parameter for the WorkspaceFactory constructor.

Re: Connect to Geodatabase Featureclass and/or shapefile

AlexanderGray — Tue, 12 Feb 2013 20:41:27 GMT

Well the exercise would be fraught with danger of returning the wrong type of workspace but to pass in the type as a parameter negates the purpose. Which is why I have never done it. However it is done in esri code because the GxDialog returns IGxObjects that have an IName. The IName allows you to open the item which means creating a workspace somewhere. I just haven't quite figured out how to do it with the IGxObject and IGxObjectFactory (which is strongly typed.) Somewhere in the GxDialog, it recognizes the file types on disc and it can later open by creating the appropriate workspace. I think we have run off the original topic here.

Re: Connect to Geodatabase Featureclass and/or shapefile

EricBader — Sat, 16 Feb 2013 14:33:56 GMT

....

This is a Java example, so sorry for that.

Ha! No need to ever apologize for using Java. Thanks for these great discussions.

Re: Connect to Geodatabase Featureclass and/or shapefile

AlexanderGray — Sun, 12 Dec 2021 02:16:30 GMT

    public static void listFeatureclass(String file) throws java.net.UnknownHostException, java.io.IOException {
        com.esri.arcgis.datasourcesGDB.FileGDBWorkspaceFactory factory = new com.esri.arcgis.datasourcesGDB.FileGDBWorkspaceFactory();
        com.esri.arcgis.geodatabase.IWorkspace workspace = factory.openFromFile(file, 0);
        com.esri.arcgis.geodatabase.IEnumDataset enumDataset = workspace.getDatasets(com.esri.arcgis.geodatabase.esriDatasetType.esriDTFeatureClass);
        com.esri.arcgis.geodatabase.IDataset ds = null;    
        ds = enumDataset.next();
        while(ds != null){
            com.esri.arcgis.geodatabase.IFeatureClass fClass = new com.esri.arcgis.geodatabase.IFeatureClassProxy(ds);
            int fCount = fClass.featureCount(null);
            System.out.println("FeatureClass "+ fClass.getAliasName() +" has "+fCount+ " features.");
            ds = enumDataset.next();
        }
    }
    
    public static void listFeatureclass2(String file) throws java.net.UnknownHostException, java.io.IOException {
        com.esri.arcgis.geodatabase.WorkspaceFactory factory = new com.esri.arcgis.geodatabase.WorkspaceFactory(new com.esri.arcgis.datasourcesGDB.FileGDBWorkspaceFactory());
        com.esri.arcgis.geodatabase.IWorkspace workspace = factory.openFromFile(file, 0);
        com.esri.arcgis.geodatabase.IEnumDataset enumDataset = workspace.getDatasets(com.esri.arcgis.geodatabase.esriDatasetType.esriDTFeatureClass);
        com.esri.arcgis.geodatabase.IDataset ds = null;    
        ds = enumDataset.next();
        while(ds != null){
            com.esri.arcgis.geodatabase.IFeatureClass fClass = new com.esri.arcgis.geodatabase.IFeatureClassProxy(ds);
            int fCount = fClass.featureCount(null);
            System.out.println("FeatureClass "+ fClass.getAliasName() +" has "+fCount+ " features.");
            ds = enumDataset.next();
        }
    }

That is really interesting, Java is very different when it comes to that sort of thing. You can't do that in .NET, the constructor for workspacefactory is not accessible outside the its own assembly. Typically in .NET you don't declare an object as a class, always an interface

even if you know the exact type of class to which you have a reference, the .NET runtime still does not have the required metadata to cast the variable to a strongly typed RCW

http://help.arcgis.com/en/sdk/10.0/arcobjects_net/conceptualhelp/index.html#//000100000151000000