PostGIS 2.0 Testing on various desktops

[robe]

Desktops to test - just itemizing issues so far that we need to address before release (either with an FAQ workaround or get the developers of these to revise)

GvSig — I know already gvSig 1.10 doesn't work with PostGIS 2.0 — looks like they are using AsEWKB which I pulled out.

Others to test uDig -

QGIS 1.5 seems to work okay with 2.0

OpenJump (I have just 1.3.1 need to check newer)— Ad hoc Query tool works okay but Data Store layer doesn't seems to use obsolete Extent

pgRouting — I think this will have issues too as last version I checked was I think using deprecated startpoint and endpoint functions among other things.

[robe]

On closer inspection — QGIS has issues too. QGIS Info tool doesn't work because it uses

AsBinary, intersects, and setsrid

[nicklas]

In QGIS this is solved in QGIS trunk (QGIS 1.7). They have nightly builds that I use. But quite annoying is that nightly build id built against Gdal 1.6.x but QGIS 1.6 is built against 1.7.x for Ubuntu. Have not successed to use the raster plugin with any of the versions. load raster to db works, but I have not been able to view the data in QGIS.

For gvSig there is also some trouble in 1.10 not passing the z-values. I had a patch from the developers to try 3D-extension. After some help from them I had it working. About ST_Asbinary I don't know if this was before AsBinary was removed or if it was fixed in that patch. The z-issue should hopefully be fixes in release 1.11. I also had some troubles with connections hanging after I had removed the table from gvSig.

/Nicklas

[jef]

Replying to robe:

On closer inspection — QGIS has issues too. QGIS Info tool doesn't work because it uses

AsBinary, intersects, and setsrid

Fixed in ​http://trac.osgeo.org/qgis/changeset/15072/ QGIS r15072

[robe]

Jef, Thanks.