File Geodatabase API is now available on Linux

Well ask and you shall receive.

We’ve added a Linux version of the File GDB API.

It is available from the same download page as the windows version.

Now developers can develop file geodatabase code on a Linux machine.

Happy Feet!

Now I gotta get off my duff and do something with it. Good to see some Linux support here, feel like Esri is saying Use Me.

Get to know ArcPad AXF

The excellent ArcPad Team Blog has info on the new storage format for ArcPad 7.1.

Prior to ArcPad 7.1, shapefiles were ArcPad’s most common spatial file format for features. Shapefiles are great for many applications, but shapefiles lack the capabilities to support more sophisticated relational database requirments that exist in the ArcGIS Geodatabase. So ArcPad 7.1 introduced the AXF format, which we like to refer to as a “lightweight geodatabase”.

As a user of ArcPad at my old job, I really hated storing information in the shapefile format. Actually I hate shapefiles, period. Any format that requires you to maintain at least 3 separate files to ensure they work is a bad idea in my book. I liked that the ArcPad team build upon the Microsoft’s SQL Server Compact Edition platform.

Time to bury the shapefile format!

The GIS Interchange File

All too often we have to request people resend datasets to each other because they get blocked by email, one important file gets left off or systems just don’t recognize a file type. I’ve run into a problem today where a company FTP site is rejecting a shapefile because it doesn’t recognize the .shp, .shx, .dbf extensions. I thought I could get around by zipping the data, but it appears to scan the zip file for extension types. So the “solution” was to zip the shapefile, change its extension to .doc and tell the recipient that they need to change the extension back to .zip.

This kind of stuff happens way too often. Personal Geodatabases have the problem of the .mdb extension that is rejected outright by most email systems and other formats aren’t readily usable by folks systems. The “old days” were easy because we all used coverages and shared them via the .e00 format that was almost always acceptable by everyone. Amazing how we take such steps back over time and you’d think data sharing would be easier than it was in 1995.

How do you folks share data? KML, GML, Etch A Sketch, e00, zip, web services, etc?

Update: Jason Birch has some ideas about using SQLite as an interchange format. Well worth the read.

ArcGIS Server and ArcSDE (and even Microsoft SQL Server 2008 Spatial)

OK, so here is what is happening at 9.3 with ArcSDE.

  1. ArcSDE finally rides into the sunset. Even though technically ArcSDE has been replaced at 9.2, it was still a separate product. Now at 9.3 it will become fully integrated into ArcGIS Server. ArcGIS Server Enterprise will be the “traditional” ArcSDE level where ArcGIS Server supports an unlimited number of users via either direct connect or connection to an application server. It offers DBMS support for IBM DB2, IBM Informix, all editions of Microsoft SQL Server, Oracle and PostgreSQL. It has no data or memory limits. The Workgroup level of ArcGIS Server supports a maximum of 10 direct connect users. It includes an embedded DBMS (Microsoft SQL Server Express Spatial). It has a data limit of 4 GB and a memory limit of 1 GB.
  2. ArcGIS will connect to Microsoft SQL Server via direct connect. Out of the box ArcGIS application will be able to connect to Microsoft SQL Server Express Spatial, but if you want unlimited users, you’ll need to purchase ArcGIS Server Enterprise. This is probably less than what folks wanted, but you’ll have to sort that our yourselves.
  3. ArcGIS supports older versions of the Geodatabase. At 9.3, ArcGIS can connect and create geodatabases (personal, file) back to 9.0. This means you won’t need to keep older versions of the geodatabase around to share with others. You also won’t have to upgrade your geodatabases just because ArcGIS went to a new release. If you wish, you can keep your older geodatabases running at whatever release you wish (back to 9.0).
  4. SQL Server 2008 Spatial will be fully supported when Microsoft releases final version of SQL Server 2008. This might mean that SQL Server 2008 support might not show up until SP1 or SP2 for 9.3. It all depends on Microsoft’s release schedule.
  5. PostgreSQL support will be available at 9.3 as has been reported. There will be support for both the PostGIS and ESRI data types.
  6. ArcGIS Engine will allow developing with Microsoft SQL Server 2008 Express so you can scale down your enterprise applications to the workgroup level. You’ll no longer be limited to working with personal for file geodatabases.
  7. ArcGIS Server Enterprise will support 64bit processors. This is only the spatial database application server and not the AGS Basic, Standard and Advanced product.

So does that answer your questions about ESRI spatial database support at 9.3?

Geodatabase Replication

I get a ton of emails asking me exactly how ESRI’s geodatabase replication works. It is pretty slick to be honest so I think everyone who has SDE should probably learn more about it. ESRI has posted a podcast titled “Geodatabase Replication: Working with Replication that explains in more detail what geodatabase replication is.

Geodatabase replication enables the distribution of datasets across several geodatabases, and provides a mechanism for keeping those datasets in synch by sending changes over the network or the Internet. This discussion contains suggestions for planning a replication strategy that will help you implement a comprehensive distributed data workflow. The mechanics of creating and synchronizing replicas are also discussed.


Learning about geodatabase replication is cool!