Latest Contributions by LanceShipman

#1 Represents a bug which we will fix in the next release. You can fix it by modifying the 10.0 in the second line of the XML to 10.1. #2 Is the result of not including the \ in the table name. ... View more

The Montgomery.gdb included in the Tutorial does not include a feature class named centroids. In any case the spatial reference information is stored in two locations. The data in both locations should be the same, but centroids case, it's not. This should never happen, so I'm trying to get an idea of what workflow created it. We are modifying the API to look in both locations when we output a feature class or feature dataset description. The annotation feature class geometry type is always polygon. Please note that annotation is not supported by the API. You can read the table, but insert or update is blocked. ... View more

How was the Centroids feature class created? The spatial reference is missing from its description. ArcGIS is getting the information from an alternate location. It should be in both locations. ... View more

I use Final release of FGDBAPI. The Geodatabase::CreateTable can't create featureclass using the XML that exported from GetDefinition. The error code is -2147467259 and the description is "General function failure". The XML that exported from GetDefinition does not contain WKT and WKID tags under SpatialReference tag. There isn't way to get a spatial reference information from FGDB except using ArcGIS. When a featureclass is created using XML with the minimum spatial reference definition, a spatial reference does not equal to the default values of ArcGIS Desktop. #1 & #2 Please send a copy of your feature class (lshipman@esri.com) and we will take a look. Both of these work for us. #3 ArcGIS Desktop has access to functionality not present in the API so the default values will be different. To get more error information when table creation fails add the extended error code from the following code fragment.   if ((hr = geodatabase.CreateTable(featureClassDef,L"", streetsTable)) != S_OK)   {     wcout << "An error occurred while creating the table." << endl;     ErrorInfo::GetErrorDescription(hr, errorText);     wcout << errorText << "(" << hr << ")." << endl; // Report any extended errors (XML). ErrorInfo::GetErrorRecordCount(recordCount); for (int i = 0;i <= (recordCount - 1); i++) {   ErrorInfo::GetErrorRecord(i,hr,errorText);   wcout << errorText << endl; } ErrorInfo::ClearErrors();     return -1; ... View more

Converting a personal geodatabase or a file geodatabase from v10 to v9.3: 1) Create empty v9.3 pgdb or fgdb 2) Export v10 pgdb/fgdb to xml workspace 3) Import xml workspace into v9.3 pgdb/fgdb Alternatively: 1) Create empty v9.3 pgdb or fgdb 2) Copy/Paste the contents of the v10 geodatabase  into v9.3 pgdb/fgdb The first approach will be slower, but will preserve unused domains. The second approach is faster, but will only copy used domains. ... View more

The included Montgomery.gdb does not include a feature class named centroids. Are you using Final or Beta 3? The following code exports the XML from the Blocks feature class. It does include the spatial reference. #include <string> #include <iostream> #include <fstream> #include <FileGDBAPI.h> using namespace std; using namespace FileGDBAPI; int main() {   // Open the geodatabase.   fgdbError hr;   wstring errorText;   Geodatabase geodatabase;   if ((hr = OpenGeodatabase(L"C:/FileGDB_API_Issues/Montgomery.gdb", geodatabase)) != S_OK)   {     wcout << "An error occurred while opening the geodatabase." << endl;     ErrorInfo::GetErrorDescription(hr, errorText);     wcout << errorText << "(" << hr << ")." << endl;     return -1;   }   Table table;   if ((hr = geodatabase.OpenTable(L"\\Landbase\\Blocks", table)) != S_OK)   {     wcout << "An error occurred while opening the table." << endl;     ErrorInfo::GetErrorDescription(hr, errorText);     wcout << errorText << "(" << hr << ")." << endl;     return -1;   }   string tableDef;   if ((hr = table.GetDefinition(tableDef)) != S_OK)   {     wcout << "An error occurred while opening the table." << endl;     ErrorInfo::GetErrorDescription(hr, errorText);     wcout << errorText << "(" << hr << ")." << endl;     return -1;   }   ofstream myfile;   myfile.open("../Blocks.xml", ios::out);   myfile << tableDef;   tableDef.clear();   myfile.close();   // Close the table   if ((hr = geodatabase.CloseTable(table)) != S_OK)   {     wcout << "An error occurred while closing Cities." << endl;     ErrorInfo::GetErrorDescription(hr, errorText);     wcout << errorText << "(" << hr << ")." << endl;     return -1;   }   // Close the geodatabase   if ((hr = CloseGeodatabase(geodatabase)) != S_OK)   {     wcout << "An error occurred while closing the geodatabase." << endl;     ErrorInfo::GetErrorDescription(hr, errorText);     wcout << errorText << "(" << hr << ")." << endl;     return -1;   }   return 0; } ... View more

As noted in the readme under Notes, #3, the API does not support multi-threading. That said, the infinite loop is strange. We have investigated this an it has to do with our use of libXML internally. We continue to investigate this and will post any results on the blog. ... View more

It's likely to be fixed in the next update. ... View more

It's a bug with the usage of the spatial index. ... View more

We plan to release a .Net wrapper for the API in the next few months. ... View more

I'd like to be able to use the File Geodatabase API to create text labels with assigned heights, location, font, and horizontal and vertical alignment.   Is there a simple way to do this with the File Geodatabase API? There is no simple way to do this with the API. Annotation feature classes are not supported. ... View more

Final returns the following error: This release of the GeoDatabase is either invalid or out of date.(-2147220965). The file geodatabase is a 9.3 geodatabase. The API only supports 10.0 or later. You need to upgrade the file geodatabase to 10.0. Final has been posted to the resources site. ... View more

I'm glad that you were able to find a backup. Please keep an eye on what processes are run on the data. This is not a normal occurrence. A gdb file can be copied from another file geodatabase, but it appears that some of the files under the file geodatabase directory were missing and these can not be recreated. A 10.0 File Geodatabase contains 40 files upon creation, a 9.3 contains 25. Adding data to the file geodatabase will create more. If a file geodatabase contains less than the initial number of files, it's damaged. A file geodatabase cannot be damaged without some external action. It's just a collection of files. External action can be copy/paste/move of the file geodatabase outside of ArcGIS (Windows Explorer) where a file is locked and the copy/paste/move process does not compete. Restoring a partial backup would leave a damaged file geodatabase. ... View more

We expect to have final posted sometime today. I'd be happy to look at your file geodatabase. Send a zipped copy to me at lshipman@esri.com or place a copy of it on the esri ftp site. Is it a 10.0 file geodatabase? If not, you can't open it. You may be able to get extended error information by using the following code:   fgdbError hr;   wstring errorText;   Geodatabase geodatabase;   int recordCount = 0;   if ((hr = OpenGeodatabase(L"../data/Querying.gdb", geodatabase)) != S_OK)   {     wcout << "An error occurred while opening the geodatabase." << endl;     ErrorInfo::GetErrorDescription(hr, errorText);     wcout << errorText << "(" << hr << ")." << endl;     // Report any extended errors (XML).     ErrorInfo::GetErrorRecordCount(recordCount);     for (int i = 0;i <= (recordCount - 1); i++)     {         ErrorInfo::GetErrorRecord(i,hr,errorText);         wcout << errorText << endl;     }     ErrorInfo::ClearErrors();     return -1;   } This is particularly helpful when creating a table as XML parsing errors are reported via this mechanism. ... View more