This is very weird. Very weird. I have experience with Esri SDE and if you are working with OGC standarts everything should work fine.
Did you registered all your tables trough ArcSDE? If not, you need to do it. OLE Connections will only let you handle tabular information, so let that go. It's not the way. AFAIK ESRI implements OGC standarts. You should NOT have problems with point geometry. Att George On Wed, Nov 18, 2009 at 6:39 PM, Ragi Y. Burhum <rbur...@gmail.com> wrote: > > From: Thomas Jakubicka <cra...@gmx.net> >> Subject: [postgis-users] Postgis and arcgis with data interoperability >> extension >> To: <postgis-users@postgis.refractions.net> >> Message-ID: <c729d2df.2936%cra...@gmx.net<c729d2df.2936%25cra...@gmx.net> >> > >> Content-Type: text/plain; charset="US-ASCII" >> >> >> Hello, >> >> I am trying to access my postgis/postgreSQL database through the >> datainteroperability extension and have problems with all my point data. I >> can load and export polygons but no points. The connection to the database >> works fine but when i try to load point data the attribute table is empty >> and only the header row is shown >> > > That seems bizarre. FYI, ESRI provides their own implementation of a > Geometry type on PostgreSQL. You can also use PostGIS. My "psychic > debugging" skills tell me there is a chance you may be mixing the two? > > Also, did you load the PostGIS functions as described in the documentation > for the database you are working with *before* loading the data? > > >> I also tried to access the database through an OLE DB connection witch is >> working so far that I get access to all tables stored in the database but >> still can not show the spatial information. With this connection all >> datasets are shown with the table-symbol and the geometry field stays >> empty. >> > > This is how the ESRI OLE DB provider works - it doesn't load and spatial > information. Anything you load from there will be "just a table" > > >> We are using the Postgis/PostgreSQL version 8.3 and ArcEditor 9.3.1 >> >> Thanks for your help >> >> > The best thing I could recommend to you now is to do some logging from the > PostgreSQL side of things. See what SQL is being executed during the load > and it should show you your problem right away. > > Hope this helps, > > - Ragi > > _______________________________________________ > postgis-users mailing list > postgis-users@postgis.refractions.net > http://postgis.refractions.net/mailman/listinfo/postgis-users > > -- George R. C. Silva Desenvolvimento em GIS www.sextantegeo2.blogspot.com
_______________________________________________ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
