[gdal-dev] Re: ESRI file geodatabase support

[Duarte Carreira]

Ragi,

That is a good point, as always. Unfortunately I am not able to do that, but I can help in any other way...

The zigGIS driver (I think ) is for reading/writing PostGIS using ArcMap, without having ArcSDE in the middle. As far as I know it does not read File geodatabases... I think for now you would have to reverse engineer the way fgdb's are written... given the effort, the discussion on whether to invest the time on fgbd or invest it on SL is at least interesting... and even fun for some of us.

Duarte

De: Ragi Burhum [mailto:ragi at burhum.com]
Enviada: quinta-feira, 17 de Junho de 2010 21:57
Para: gdal-dev at lists.osgeo.org
Cc: Duarte Carreira; Eric Wolf; Peter J Halls; Matt Wilkie
Assunto: RE: [gdal-dev] Re: ESRI file geodatabase support

From: Duarte Carreira <DCarreira at edia.pt<mailto:DCarreira at edia.pt>>
Subject: RE: [gdal-dev] Re: ESRI file geodatabase support
To: Eric Wolf <ebwolf at gmail.com<mailto:ebwolf at gmail.com>>, Peter J Halls <P.Halls at york.ac.uk<mailto:P.Halls at york.ac.uk>>
Cc: "gdal-dev at lists.osgeo.org<mailto:gdal-dev at lists.osgeo.org>" <gdal-dev at lists.osgeo.org<mailto:gdal-dev at lists.osgeo.org>>,      Matt Wilkie
       <maphew at gmail.com<mailto:maphew at gmail.com>>

Well, if SpatiaLite offers some "proper" benefits and disseminates through all of the FOSS world, then it may get a strong enough push even for ESRI to pick it up. It happened before... (kml?)

If SL would:


1)      Be as fast as shapefile in production settings, desktop and webgis

2)      Offer SQL support, spatial and otherwise, also through desktop tools like QGIS

3)      Allow editing while serving (even if for 1 editor only)

4)      Better support in QGIS than for shapefile (take advantage of Spatial SQL, all other functionality)

5)      Same for MapServer, GeoServer, gvSIG, et al.

6)      Allow easy managing of rasters inside the .db file, through QGIS

7)      ??more ideas/requests??

Then it would be a very, very good contender... and the ball would be kicked to "the other side".
And it seems we're already there for some of the listed features.
Duarte

Or even better, instead of waiting and complaining, we could just write a GeoDatabase OGR (ESRI) Workspace ourselves.

There are already examples of working ones out there

http://svn.obtusesoft.com/core/trunk/

So instead of hoping and pleading for support, someone should just sit down and write it.

I started one at one point (C++), got side tracked with other things. If anyone is interested in that source code, I would be happy to share that too.

- Ragi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/gdal-dev/attachments/20100618/aad50ede/attachment.html