[Gvsig_english] Cannot add GeoDb table to a View (Antonio Falciano)

Antonio Falciano afalciano at yahoo.it
Mon Aug 20 09:58:17 CEST 2012


Al,
I'm happy to know that legacy.sql solves these compatibility issues.
Thanks for sharing your follow up.

Cheers,
Antonio


Il 19/08/2012 2.57, Al Vigil ha scritto:
> Antonio,
> The problem is solved.  I followed up with postgis via the ticket you 
> mentioned in your message.  Their advise, to install legacy.sql, fixed 
> the problem.  This is what posgis said:
>
>     /Comment(by robe):/
>     //
>     / Al,/
>     //
>     / You can try installing the legacy.sql file packaged with PostGIS
>     2.0 that
>      is in share/contrib/postgis-2.0 folder (where the other PostGIS
>     scripts
>      are).  That reinstalls all the legacy functions we took out and
>     resolves
>      many of these kinds of issues./
>     //
>     / If that still doesn't work, can you turn on logging on your
>     database and
>      let us know what errors you are seeing in the logs./
>     //
>     / to turn on logging do the following - replace mygisdb with the
>     name of the
>      database you are connecting to./
>     //
>     / {{{
>      ALTER DATABASE mygisdb SET log_statement='all';
>      }}}/
>     //
>     / The logs are usually written to the pg_logs folder of your
>     PostgreSQL data
>      folder.
>      Check the latest one -- usually notes the missing function or
>     issue with
>      call.
>     /
>     > Il 17/08/2012 21.12, Al Vigil ha scritto:
>     >> I have no trouble displaying shp files, only PostGis GeoDb tables.
>     >> Am using the binaries for Postgresql 9.1 and PostGis 2.0.1
>     running under
>     >> Windows Vista.  The vectors
>     >> are stored in a geometry column and am using projection 4326 on the
>     >> View, the same projection as the table.
>     >
>     > Hi Al,
>     > I think that the issue is probably due to your PostGIS version,
>     because
>     > gvSIG 1.1x actually supports only PostGIS 1.x and not the latest
>     2.0.
>     > In reference to this there's also a ticket in the PostGIS bug
>     tracker [1].
>     > IMHO adding the PostGIS 2.0 support is a useful feature request,
>     but I
>     > don't know if developers have enough time and resources to solve
>     this
>     > problem right now that gvSIG 1.12 final is going to be released.
>     >
>     > Cheers,
>     > Antonio
>     >
>     > [1] http://trac.osgeo.org/postgis/ticket/833
>     >
>     > --
>     > Antonio Falciano
>     > http://www.linkedin.com/in/antoniofalciano
>     >
>     >
>     > ------------------------------
>     >
>     > _______________________________________________
>     > Gvsig_internacional mailing list
>     > Gvsig_internacional at listserv.gva.es
>     <mailto:Gvsig_internacional at listserv.gva.es>
>     > http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
>     >
>     >
>     > End of Gvsig_internacional Digest, Vol 79, Issue 10
>     > ***************************************************
>
>
>
> _______________________________________________
> Gvsig_internacional mailing list
> Gvsig_internacional at listserv.gva.es
>
> To see the archives, edit your preferences or unsubscribe from this mailing list, please access this url:
>
> http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional

-- 
Antonio Falciano
http://www.linkedin.com/in/antoniofalciano



More information about the Gvsig_internacional mailing list