One of the frequent questions we get asked are what file formats will GeoCommons support in the future. Currently we are working on adding GeoRSS, KML network links and KMZs. The big push with these file formats is to allow dynamic data to be added to GeoCommons, which we think will open a lot of new possibilities for what you can do with both analysis and data visualization. The question we’ve been kicking around recently is what other data formats make sense to provide support for?
In a couple of presentation we’ve gotten the question if GeoCommons will support ESRI “personal geodatabases” or “file geodatabases”. For those who have fallen behind in their kool aid consumption:
File Geodatabases—Stored as folders in a file system. Each dataset is held as a file that can scale up to 1 TB in size. This option is recommended over personal geodatabases.
Personal Geodatabases—All datasets are stored within a Microsoft Access data file, which is limited in size to 2 GB.
My quick assessment is that the “personal geodatabases” would be possible since it is a single file in a well known format. Unfortunately from what I’ve read and heard ESRI is pushing folks to adopt “file geodatabases”. The expanded storage size and versatility seem like solid advantages, but what I’ve not been able to sort out is data portability. More specifically if I have my data in a “file geodatabase” how do I load it into other applications outside the ESRI stack. We happened to be at the GeoInt conference last week so we stopped by the ESRI booth to ask. After a bit of confusion as to why we would want to load the data into another application the answer was that we needed to use the “interoperability extension tool“, although it would make a lot more sense to use ArcGIS Server and expose the data as a web service through it.
Both are very clever ways to sell more ESRI product and there is nothing wrong with that – it pays the rent. It does create a bit of a conundrum as to what is the best way to support data portability for traditional GIS data outside of shapefile support. Digging through the ESRI online help there is the suggestion of using “geodatabase XML” which has an open specification. It looks promising, but I’m just not so sure many users are going to dig through a 46 page specification to make their data portable.
Jame’s Fee has brought up this conundrum under the idea of a “GIS interchange file“, which would be a no-brainer to support. In its absence I’m wondering what the community would like to see supported. Are geodatabses worth the effort? Would support for an OGR driver make more sense to allow direct database dumps into and out of GeoCommons? Possibly support for SpatiaLite? Does someone need to push a data interchange standard with the OGC? Is there already one that I do not know about (no I don’t really see GML as that)? Any and all suggestion would be greatly appreciated.
Welcome to the Esri DC Development Center blog. We write about features of our work on big data analytics, open platforms, and open data, what is new and exciting in the Esri and community, and general industry thought leadership and discussions of geospatial data visualization and analysis.
Please explore what we're working on and let us know if you have any questions or ideas!
- Histogram Time Slider | #MustVisit - Pintu Gerbang on Histogram Time Slider
- Armanda Dudden on Helpful Data for the San Diego Fires
- Quinton Salomon on Dataset of the Day: State Firearm Restrictions, Solely based on Crime Rates?
- Gertha Godzik on Dataset of the Day: After the Floods, Farmers Get a Little Help From Uncle Sam!
- http://www.infographicsshowcase.com/legal-plans-can-reduce-stress-increase-wellness on Heat Maps for Google Maps – (a.k.a GeoIQ mashup)