ESRI has released File Geodatabase API to access ESRI schema without having to have ArcObjects license. This is a simple way out to analyze the data and create custom report of features outside of ESRI ecosystem. For non -ESRI developers this is a boon and for .Net developers it is ease to utilize Microsoft .Net or C++ libraries to access the File Geodabase Objects. ESRI is doing incremental update on this and soon they will release Java API to access as well.
Recently we developed Google Maps Application for one of clients displaying markers for Retail Layers and Georgia DOT points.
Here is the live url
If you wanted to create a small geodatabase with few feature classes or object classes you have two options.
- ESRI File Geodatabase
- Personal Geodatabase (Microsoft Access Database)We recommend to use ESRI File Geodabase, because it is simple and all data is stored in a folder with the .gdb extension. It is robust and it has 1 Terabyte per table size limit compared to Microsoft’s 2 GB total database limit. However both of them they don’t support ESRI versioning support. Here are top reasons to select file geodatabase option. (1) Improved versatility and usability. (2) Optimized performance for ArcMap editing (3) Easy Data Migration between geodatabases (4) Few size limitations for import/export operations (5) Custom Storage Configuration to support /store large raster images.
Recently we developed a web mapping application to lay GA DOT data over Google Maps. The GA DOT data was in ESRI Geodatabase format.. We had to extract Lat/Long from ESRI Shape field. If you run into problem like this you can use this script to get Lat/Long from ESRI shape.
Traditionally we upgrade geodatabase by running ArcSDE post process. In ArcGIS 10.0 you will use ArcCatalog tool to upgrade the geodatabase.
Upgrading VBA to Addins is the new technique to recycle VBA projects and code. With ArcGIS 10.0 the following add-in types are supported in the current release:
- Buttons and tools
- Combo boxes
- Menus and context menus
- Toolbars
- Tool palettes
- Dockable windows
- Application extensions
- Editor extensions
VBA environment in ESRI ArcGIS Desktop is gone in the new version. If you have VBA customization for ArcGIS Desktop you have following options:
- Python Geo-processing scripts
- ArcGIS Addin – using Microsoft .Net Framework and Java
ESRI has created an extensible model to create and manage addins. Click here to learn more.
ESRI has introduced the concept of Multiversion view to update the featureclasses directly via SQL statements. We have been using this to extract data from featureclasses for reporting purpose. The multiversion view is created at ArcSDE level and do not participate in geodatabase behavior.
Steps for reading purposes only:
- Create a multiversion view
- Assign privileges or roles to the multiversion views
- Use them just like table.
Advantages:
- Quick, fast to access featureclass data.
- Can use ADO.Net to access and report on featureclass.
- Great performance while joining featureclasses.
Steps for editing multiversion view:
- Create a multiversion view
- Create a version to do you edits
- Start a edit session by calling edit_version or a custom function
- Do edits –> Save
- Stop edit version by calling a edit version or custom function
- Reconcile and Post edits via ArcGIS
At Socket Technologies we use multiversion view extensively for Enterprise Geodatabse reporting purposes.
As a ESRI ArcObjects developer you can automate the labeling by combining the data from fields.
While combining field values into one string and updating the target field is simple, there may be a situation where in you want to sort the values in ascending or descending order.Here is sample code where we are trying to combine three ESRI fields and sorting the data and then updating the field.
private void button1_Click(object sender, EventArgs e)
ESRI lets ArcGIS Server run 64 bit operating system. There are known issues running ArcObjects code built on Micorosft .Net platform on 64 bit operating system.
In Visual Studio the developers normally set the build–>Platform target to “Any CPU”, this needs to be changed and set to x86 platform, because ESRI ArcObjects run as 32 bit applications on a 64 bit Operating System. Please see the screenshot from Visual Studio –>Properties–>Build–>General–>Platform target
Socket Tech Support Team

