I agree on that: these postings are valuable to the MapInfo MI-L; when this
comes to a solution, I will post our findings there as well.
Anyhow, this made me think of what might be different between your and mine
configuration... How about the encoding of the database?
Mine is defined as follows:
CREATE DATABASE "nwpgdb"
WITH OWNER = postgres
ENCODING = 'SQL_ASCII'
LC_COLLATE = 'Dutch_Netherlands.1252'
LC_CTYPE = 'Dutch_Netherlands.1252'
CONNECTION LIMIT = -1;
Both 'UTF8' and 'SQL ASCII' render the same message in MapInfo: "Unable to
translate the Spatial Constraint." (using pgsqlODBC ANSI v8.03.04.00), for
both little datasets I tested with: provinces of the Netherlands (national
spatial reference system; EPSG 28992) and the political map op Africa
(non-earth), resulting in the following spatial constraints, respectively:
Provinces: CONSTRAINT "enforce_srid_SP_GEOMETRY" CHECK
(st_srid("SP_GEOMETRY") = 28992)
Africa: CONSTRAINT "enforce_srid_SP_GEOMETRY" CHECK (st_srid("SP_GEOMETRY")
= (-1))
What other differences between our set-ups may we think of?
Rob
2009/10/7 Richard Greenwood <richard.greenw...@gmail.com>
> On Wed, Oct 7, 2009 at 12:24 AM, InterRob <rob.mar...@gmail.com> wrote:
> > Thank you for the suggestion; again something I did not think of (!)...
> > So I tried some really 'easy' little datasets; points with some INT
> > attributes. Still no luck, though...
> > It seems that MapInfo v10 is not compatible with PostGIS 1.4.0. This
> makes
> > me wondering, having the error message in mind ("Unable to translate the
> > Spatial Constraint."): is this spatial constraint expressed differently
> in
> > PostGIS 1.4.0 , comparing it to, say, 1.3.5? One could even think of even
> > very small differences like capitals in functions e.g. st_srid() versus
> > ST_srID() etc. etc. At least success has been reported (by some other
> users,
> > like you Richard) of working with PostGIS (1.3.5 or lower) from
> MapInfo...
>
> Okay, I just installed Postgres 8.4 and PostGIS 1.4 and uploaded my
> test table via Easyloader, and then connected to it with un-cached
> Live access and it seems to be working for me. The spatial constraint
> that MapInfo is imposing on my table is:
> st_srid("SP_GEOMETRY") = (-1)
> What's your spatial constrain? What happens if you drop it?
>
> This thread might be valuable on MapInfo-L as I think the issues are
> more with MI than PostGIS.
>
> --
> Richard Greenwood
> richard.greenw...@gmail.com
> www.greenwoodmap.com
>
>
_______________________________________________
postgis-users mailing list
postgis-users@postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
