So I was walking to the Esri Dev Meetup in Arlington, VA with Kate Chapman and Adam Estrada and we were talking about SpatiaLite. Specifically, we were discussing James’ recent post and the lack of uptake of SpatiaLite. The really easy thing to do is to lay the blame at the feet of Esri for not supporting it. But then it occurred to me that Esri hasn’t succeeded in making the file geodatabase the next shapefile nor did they succeed in making the personal geodatabase the next shapefile. When I think about it, Esri has been trying really hard to kill the shapefile for a long time, without success.
A little historical perspective is in order. At the time ESRI published the shapefile format, they were under a lot of pressure from the community to open something. I recall most of the focus being on the ARC/INFO coverage, mainly because a lot of data resided in that format. Instead, they opened the shapefile, which had been introduced with ArcView 2.0. It took off like wildfire. Before long, every major competing platform could read and write shapefiles (heck, even Visio had a “maps” feature that could read it).
Keep in mind that most of us were dissatisifed with DBF files even back then. They were already long in the tooth. Also, the multiple-file structure of the shapefile was clunky from the get-go. The way I see it, the main reason for the success of the shapefile was the lack of anything else. The shapefile never had to present a “compelling reason to change” because there was nothing to change from. Sure, everyone still used their GIS-du-jour’s proprietary format (MapInfo TAB for example) but we could now pass around shapefiles freely.
The problem with any data format that seeks to succeed the shapefile is that it must first succeed the shapefile in the minds of users. Any subsequent pretender format must jump a hurdle that the shapefile simply did not. It must provide a compelling reason to change from the shapefile. As developers and system architects, we have plenty of those reasons (long column names, topology, better spatial reference support, object-oriented data, single-file structures, etc.). For whatever reason, those things have not resonated with the users. Even all of the compelling features of the geodatabase (which are well-summarized here), for those users committed to staying completely within the Esri framework, have not killed off the shapefile.
So I’m left to wonder if the shapefile is:
a) the brainless format that just won’t die; or
b) good enough?