From bernhard at intevation.de Mon Jan 1 23:45:07 2007 From: bernhard at intevation.de (Bernhard Reiter) Date: Mon, 1 Jan 2007 23:45:07 +0100 Subject: Planning for 1.2.0 release. In-Reply-To: <200611061131.32035.bernhard@intevation.de> References: <200611061131.32035.bernhard@intevation.de> Message-ID: <200701012345.12234.bernhard@intevation.de> On Monday 06 November 2006 11:31, Bernhard Reiter wrote: > So what do you we need to do to get 1.2.0 out of the door? I think we are very close to roll 1.2.0. > Browsing our problem tracker at wald, here are the issues that I think > we should address before releasing 1.2.0: > > 97 problem accessing database tables with 1.1.0 version : wx 2.6 problem > 98 problem accessing database tables with 1.1.0 version : point layers 97 and 98 are resolved. > 118 problem with utf8 systems trying to see non utf8 table Didrik has a patch for this one. > We must look into the postgis failures I had on Debian Etch (see my post > a few minutes ago). I have just right now fixed those test with revision 217. > In addition I think we should fix the packaging for Debian Etch as well. This is not critical for the release. And because I was quite busy with other stuff, Thuban has missed the freeze for Etch. Bernhard -- Managing Director - Owner, www.intevation.net (Free Software Company) Germany Coordinator, fsfeurope.org (Non-Profit Org for Free Software) www.kolab-konsortium.com (Email/Groupware Solution, Professional Service) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://www.intevation.de/pipermail/thuban-devel/attachments/20070101/a3bb305b/attachment.bin From dpinte at itae.be Tue Jan 2 14:29:02 2007 From: dpinte at itae.be (Didrik Pinte) Date: Tue, 02 Jan 2007 14:29:02 +0100 Subject: Planning for 1.2.0 release. In-Reply-To: <200701012345.12234.bernhard@intevation.de> References: <200611061131.32035.bernhard@intevation.de> <200701012345.12234.bernhard@intevation.de> Message-ID: <1167744542.14298.1.camel@geru-itae> Le lundi 01 janvier 2007 ? 23:45 +0100, Bernhard Reiter a ?crit : > > > 118 problem with utf8 systems trying to see non utf8 table > > Didrik has a patch for this one. I will try to patch the trunk asap (probably before the week-end). Happy new year to Intevation and the Thuban team ! Didrik -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?= Url : http://www.intevation.de/pipermail/thuban-devel/attachments/20070102/95c5cb67/attachment.bin From charles.mccreary at crmeng.com Thu Jan 4 16:31:02 2007 From: charles.mccreary at crmeng.com (Charles McCreary) Date: Thu, 04 Jan 2007 09:31:02 -0600 Subject: raster image works on Linux, busted on Windows Message-ID: <459D1DB6.2090900@crmeng.com> I've been working with/on thuban in Linux and all is well. When I built on Windows, I ran into a problem with raster images. I previously posted three messages about the problem but I used a non-list-member email so they are awaiting moderator approval, please disregard. The raster image shows up masked, as it turns out. The default masktype is MASK_BIT (layer.py - RasterLayer.__init__). If I change the masktype to none or alpha, the raster is displayed properly. Why does MASK_BIT work differently on linux and windows? -- Charles R. McCreary PE CRM Engineering Services www.crmeng.com 903.643.3490 - Voice 903.643.3012 - Facsimile From bernhard at intevation.de Thu Jan 4 17:02:35 2007 From: bernhard at intevation.de (Bernhard Reiter) Date: Thu, 4 Jan 2007 17:02:35 +0100 Subject: raster image works on Linux, busted on Windows In-Reply-To: <459D1DB6.2090900@crmeng.com> References: <459D1DB6.2090900@crmeng.com> Message-ID: <200701041702.40055.bernhard@intevation.de> On Thursday 04 January 2007 16:31, Charles McCreary wrote: > I've been working with/on thuban in Linux and all is well. When I built > on Windows, I ran into a problem with raster images. You probably should include the details of your build as well. In your other email you have said that you did use SVN trunk (which is good). > I previously posted > three messages about the problem but I used a non-list-member email so > they are awaiting moderator approval, please disregard. I rejected them as you have requested. Note that you can do this by yourself with the link in the hold notice you have been send. > The raster image shows up masked, as it turns out. The default masktype > is MASK_BIT (layer.py - RasterLayer.__init__). If I change the masktype > to none or alpha, the raster is displayed properly. > > Why does MASK_BIT work differently on linux and windows? I cannot say. It could be a wx problem. The next step would probably be to write a small test application which only uses wx and see if the problem can be triggered this way as well. If so, we should report the problem to wx or wxpython, where ever we can trigger it. Looking into gdalwarp certainly is also worth trying as Jonathan had to build in a few workaround for different wx issues around the mask and you could just see a side effect of his workarounds. Bernhard -- Managing Director - Owner, www.intevation.net (Free Software Company) Germany Coordinator, fsfeurope.org (Non-Profit Org for Free Software) www.kolab-konsortium.com (Email/Groupware Solution, Professional Service) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://www.intevation.de/pipermail/thuban-devel/attachments/20070104/4c89d03d/attachment.bin From bernhard at intevation.de Thu Jan 4 19:05:45 2007 From: bernhard at intevation.de (Bernhard Reiter) Date: Thu, 4 Jan 2007 19:05:45 +0100 Subject: raster image works on Linux, busted on Windows In-Reply-To: <459D34F8.4000106@crmeng.com> References: <459D1DB6.2090900@crmeng.com> <200701041702.40055.bernhard@intevation.de> <459D34F8.4000106@crmeng.com> Message-ID: <200701041905.46183.bernhard@intevation.de> On Thursday 04 January 2007 18:10, Charles McCreary wrote: > I suspect a wx problem. test_baserenderer.py runs OK so that tells me > gdalwarp must be working OK. Our testcases might not test everything, I suggest to prove the hypothesis that wx contains the defect with a small test application. Bernhard -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://www.intevation.de/pipermail/thuban-devel/attachments/20070104/c2216a7c/attachment.bin From thuban-bugs at wald.intevation.org Sat Jan 6 02:04:43 2007 From: thuban-bugs at wald.intevation.org (thuban-bugs@wald.intevation.org) Date: Sat, 6 Jan 2007 02:04:43 +0100 (CET) Subject: =?UTF-8?B?W3RodWJhbi1CdWdzXVsyNTddIHBvc3RnaXMgdGFibGUgY2Fubm90IGJlIG9wZW5lZA==?= Message-ID: <20070106010443.6852B1800168@pyrosoma.intevation.org> Bugs item #257, was opened at 2007-01-06 02:04 Status: Open Priority: 3 Submitted By: Didrik Pinte (dpinte) Assigned to: Nobody (None) Summary: postgis table cannot be opened Resolution: None Version: None Category: None Initial Comment: Using the latest svn version on a Debian system with psycopg 1, I get the following error while opening a postgis table : Can't open the database table 'network' I've updated Thuban/UI/mainwindow.py in order to get more info about the problem . So I've added a str of the Exception to the RunMessageBox call. Can't open the database table 'network' ERROR: column "cellgeom" does not exist SELECT srid, type FROM geometry_columns WHERE f_table_name = '"network"' AND f_geometry_column = cellgeom This is pretty strange. The table name is quoted and don't have to and the column name is not even single quoted. The corresponding line of code is : Thuban/Model/postgisdb.py - line 533 : cursor.execute("SELECT srid, type FROM geometry_columns" " WHERE f_table_name = %s AND f_geometry_column=%s", (self.tablename, self.geometry_column)) The postgresql backend is a 8.1 server with latin-1 database and postgis 1.6. My locale are ISO-8859-1. ---------------------------------------------------------------------- You can respond by visiting: http://wald.intevation.org/tracker/?func=detail&atid=105&aid=257&group_id=6