[postgis-users] Postgis and arcgis with data interoperability extension
Paragon Corporation
lr at pcorp.us
Thu Nov 19 09:41:37 PST 2009
Thomas,
Try changing the client encoding of your db to latin1. That's what I do.
ALTER DATABASE mydb SET client_encoding=latin1;
Leo
-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Thomas
Sent: Thursday, November 19, 2009 10:47 AM
To: PostGIS Users Discussion
Subject: Re: [postgis-users] Postgis and arcgis with data interoperability
extension
Maybe I have an idea how. to solve the Problem: The error message that i get
from the database is that the query is using the wrong encoding: IBM/latin
but in the database we are using UTF8 Does anybody know how to change that
Regards
Thomas
On 19.11.09 10:50, "Andreas Neumann" <a.neumann at carto.net> wrote:
> Hi Thomas,
>
> did you have a look at ziggis? It enables data connection and editing of
> native Postgis geometries without the need for ArcSDE.
>
> It is commercial, but much cheaper than SDE: http://pub.obtusesoft.com/
>
> I don't have ESRI myself, so I don't have experience with it, but it is
> definitely worth a try.
>
> Andreas
>
>
> On Thu, November 19, 2009 10:19 am, Thomas wrote:
>>
>> Ok thanks for the OLE DB info.
>> I am still new to working with databases so maybe I am wrong, but ESRI
>> told
>> me that I can use ArcSDE only with the Server Version that I until now
don
>> t
>> have. But still it should be possible to connect through the Data
>> Interoperability Extension.
>> The strange thing is that it works with polygons but not with point
>> geometry
>>
>> Thanks for your ideas
>>
>> thomas
>>
>>
>> On 18.11.09 22:51, "George Silva" <georger.silva at gmail.com> wrote:
>>
>>> 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 <rburhum at gmail.com>
>>> wrote:
>>>>
>>>>> From: Thomas Jakubicka <crazyh at gmx.net>
>>>>> Subject: [postgis-users] Postgis and arcgis with data interoperability
>>>>> extension
>>>>> To: <postgis-users at postgis.refractions.net>
>>>>> Message-ID: <C729D2DF.2936%crazyh at gmx.net
>>>>> <mailto:C729D2DF.2936%25crazyh at 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 at postgis.refractions.net
>>>> http://postgis.refractions.net/mailman/listinfo/postgis-users
>>>>
>>>
>>>
>>
>> _______________________________________________
>> postgis-users mailing list
>> postgis-users at postgis.refractions.net
>> http://postgis.refractions.net/mailman/listinfo/postgis-users
>>
>
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
More information about the postgis-users
mailing list