Can anyone suggest a workaround? I am trying to implement relationship classes from a Personal Geodatabase into PostGIS. What about if I created the relationship classes natively in the PostGIS database server? The issue then would be getting ArcMap to recognize the relationship classes and enforce them via editing. I know this is more of an ArcGIS question, but am lookin for the input of experienced PostGIS users.
On Tue, Jul 29, 2008 at 9:34 AM, Lee Hachadoorian < [EMAIL PROTECTED]> wrote: > Yes, ArcCatalog creates a standard Access database table, but enforces > the creation of a unique index called OBJECTID (which is not, however, > actually a primary key). So what Regina describes should work. > > There's an ogr2ogr cheatsheet at BostonGIS > (http://www.bostongis.com/?content_name=ogr_cheatsheet). > > I'm not sure about the relationship classes question, although my > suspicion is that the conversion works table-by-table on data (spatial > and non-spatial) only. Since the relationship classes are not stored > in the feature class or non-spatial table itself (they are stored in a > table called GDB_RelClasses), I suspect that ogr2ogr will not do > anything to convert them. Can someone confirm? > > -- > Lee Hachadoorian > PhD Student, Geography > Program in Earth & Environmental Sciences > CUNY Graduate Center > _______________________________________________ > postgis-users mailing list > [email protected] > http://postgis.refractions.net/mailman/listinfo/postgis-users >
_______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
