<div dir="ltr">Thanks to your input I have been able to input all the ESRI Geodatabase feature classes and tables. I used the OGR2OGR tool with the parameters specified by Regina. Note that to append all tables you should omit table names. <br>
<br>I am able to display the database tables in ArcMap using zigGIS. However, when I try to add a feature class, I get the following errors in the zigGIS Feedback window:<br><br>1. Unsupported geometry type GEOMETRY<br> I understand this was created by the OGR2OGR tool. Can I just delete it?<br>
<br>2. Unsupported type Decimal on FeatureClassNameORTableName.OBJECTID<br><br>This is the most troubling of the error messages. The OBJECTID is,<br>of course, what ESRI uses as primary key to link the spatial vector table to the attribute table of a feature class. If this type is not supported, how can an ESRI Feature Class work correctly in PostGIS?<br>
<br>3. The FeatureClassNameORTableName.gid field was not found.<br><br>No idea on what this means.<br><br>Thanks!<br><br><div class="gmail_quote">On Tue, Jul 29, 2008 at 4:10 PM, Ragi Y. Burhum <span dir="ltr"><<a href="mailto:ragi@burhum.com" target="_blank">ragi@burhum.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tue, Jul 29, 2008 at 12:01 PM,<br>
<<a href="mailto:postgis-users-request@postgis.refractions.net" target="_blank">postgis-users-request@postgis.refractions.net</a>> wrote:<br>
><br>
> Message: 20<br>
> Date: Tue, 29 Jul 2008 09:47:22 -0700<br>
> From: "Juan Declet" <<a href="mailto:reguerete@gmail.com" target="_blank">reguerete@gmail.com</a>><br>
<div>> Subject: Re: [postgis-users] ESRI Geodatabases, relationship classes<br>
> and PostGIS<br>
</div>> To: "PostGIS Users Discussion" <<a href="mailto:postgis-users@postgis.refractions.net" target="_blank">postgis-users@postgis.refractions.net</a>><br>
> Message-ID:<br>
> <<a href="mailto:c566dff90807290947q48e44807j57efb6e50712d80d@mail.gmail.com" target="_blank">c566dff90807290947q48e44807j57efb6e50712d80d@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>
<div>><br>
> Can anyone suggest a workaround? I am trying to implement relationship<br>
> classes from a Personal Geodatabase into PostGIS. What about if I created<br>
> the relationship classes natively in the PostGIS database server? The issue<br>
> then would be getting ArcMap to recognize the relationship classes and<br>
> enforce them via editing. I know this is more of an ArcGIS question, but am<br>
> lookin for the input of experienced PostGIS users.<br>
<br>
</div>You are working with 2 different abstractions... one at the ArcObjects<br>
level, and the other one at the RDBMS. Don't get them confused.<br>
<br>
If your intent is to simply enforce the cardinality constraint, go<br>
ahead and create the relationship at the PostgreSQL level. As long as<br>
you are doing non-versioning editing, your ArcMap save operation will<br>
be done within a transaction... if an RDBMS error is raised (and you<br>
will get one if you violate the contraint you created) that<br>
transaction will be rolled back and you will get the RDBMS message in<br>
ArcMap. Be mindful that during the edit session you will not see the<br>
error until ArcMap flushes its edit session (during a save, search,<br>
etc).<br>
<br>
If your intent is to have ArcMap recognize the relationship, for<br>
example, to be able to navigate it through the object inspector, you<br>
are going to need to insert the right entries in the GDB_*<br>
(GDB_Relationships, GDB_ObjectClasses, etc) tables. The easiest bet is<br>
to create the relationship through ArcCatalog once and check the<br>
entries it created in those GDB metadata tables so you know how it<br>
works.<br>
<div><br>
><br>
> On Tue, Jul 29, 2008 at 9:34 AM, Lee Hachadoorian <<br>
> <a href="mailto:lee.hachadoorian@gmail.com" target="_blank">lee.hachadoorian@gmail.com</a>> wrote:<br>
><br>
>> Yes, ArcCatalog creates a standard Access database table, but enforces<br>
>> the creation of a unique index called OBJECTID (which is not, however,<br>
>> actually a primary key).<br>
<br>
</div>Ha ha.. that is debatable :-)<br>
<div><br>
>> So what Regina describes should work.<br>
>><br>
>> There's an ogr2ogr cheatsheet at BostonGIS<br>
>> (<a href="http://www.bostongis.com/?content_name=ogr_cheatsheet" target="_blank">http://www.bostongis.com/?content_name=ogr_cheatsheet</a>).<br>
>><br>
>> I'm not sure about the relationship classes question, although my<br>
>> suspicion is that the conversion works table-by-table on data (spatial<br>
>> and non-spatial) only. Since the relationship classes are not stored<br>
>> in the feature class or non-spatial table itself (they are stored in a<br>
>> table called GDB_RelClasses), I suspect that ogr2ogr will not do<br>
>> anything to convert them. Can someone confirm?<br>
>><br>
>> --<br>
</div><div>>> Lee Hachadoorian<br>
>> PhD Student, Geography<br>
>> Program in Earth & Environmental Sciences<br>
>> CUNY Graduate Center<br>
<br>
</div>My two cents,<br>
<br>
- Ragi Yaser Burhum<br>
<div><div></div><div>_______________________________________________<br>
postgis-users mailing list<br>
<a href="mailto:postgis-users@postgis.refractions.net" target="_blank">postgis-users@postgis.refractions.net</a><br>
<a href="http://postgis.refractions.net/mailman/listinfo/postgis-users" target="_blank">http://postgis.refractions.net/mailman/listinfo/postgis-users</a><br>
</div></div></blockquote></div><br></div>