Thanks George - I will check this out. I think that your method of detailing the various tables to include WILL be useful for me. What I am less sure about is whether or not this will export "links" from tables... but then again, I do not even know if personal geoDB will support that...
In other words, my goal is to give my users something with a structure that holds features in one table, then associates those features with various properties tables. As an aside, this is a pretty typical use case, I have inherited stewardship of a ShapeFile with 58,000 rows in it, and 135 columns. I pulled it into a nicely atomized and structured PostgreSQL db, but my users really want me to give them a daily dump of the old 58,000x135 shape file -- I want to lure them away from such abominations... On Tue, Dec 2, 2014 at 2:23 PM, George Silva <[email protected]> wrote: > Hello Robert, > > If your slave copy is read-only, you can setup a export job using ogr2ogr > to generate the File Geodatabase daily. > > Personal Geodatabase are not supported, but File Geodatabase are. You'll > need to compile GDAL with FGDB support, that must be installed separately. > > Some Geodatabase features are not supported via export directly, such as > the creation of Feature Datasets. > > Check this gist: > > https://gist.github.com/george-silva/787861408555572ad100 > > The main export.sh script takes up a few parameters, so you can pass them > along. This uses a table inside postgresql to know in advance about the > layers I have and those that need to be exported. > > This is bit more sophisticated, but you can hardcode your script and it > will work the same. > > Let me know how that works out for you. > > On Tue, Dec 2, 2014 at 4:37 PM, Robert Burgholzer <[email protected]> wrote: > >> Wondering if anyone has any experience running from PG to ESRI mdb. >> Basically, we want to use PostGIS as our master, and then replicate in >> GeoDB format for field personel to reference when they are unable to >> connect to the Web due to remote location (which happens very frequently in >> our line of work). >> >> Any thoughts, experiences would be welcome. >> >> -- >> -- >> Robert W. Burgholzer >> 'Making the simple complicated is commonplace; making the complicated >> simple, awesomely simple, that's creativity.' - Charles Mingus >> Athletics: http://athleticalgorithm.wordpress.com/ >> Science: http://robertwb.wordpress.com/ >> Wine: http://reesvineyard.wordpress.com/ >> >> _______________________________________________ >> postgis-users mailing list >> [email protected] >> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users >> > > > > -- > George R. C. Silva > SIGMA Consultoria > ---------------------------- > http://www.consultoriasigma.com.br/ > > _______________________________________________ > postgis-users mailing list > [email protected] > http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users > -- -- Robert W. Burgholzer 'Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that's creativity.' - Charles Mingus Athletics: http://athleticalgorithm.wordpress.com/ Science: http://robertwb.wordpress.com/ Wine: http://reesvineyard.wordpress.com/
_______________________________________________ postgis-users mailing list [email protected] http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
