<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Dear all,<div class=""><br class=""></div><div class="">A couple of weeks ago I made the mistake of upgrading Opensuse on this 32 Toshiba Laptop to 13.2. Grass failed to work with error messages indicating NumPy had not been installed. It had been installed but did not contain the files Grass was looking for. Attempts at removing and re-installing NumPy all produced the same incomplete file set. (i586 installation)</div><div class=""><br class=""></div><div class="">I have reverted to Opensuse 13.1 and now have another non working version Grass 6.4</div><div class=""><br class=""></div><div class="">Traceback (most recent call</div><div class="">
<p style="margin-bottom: 0cm" class="">GRASS 6.4.3 (South_Oxfordshire):~ >
Traceback (most recent call last):</p><p style="margin-bottom: 0cm" class=""> File
"/opt/grass/etc/wxpython/wxgui.py", line 139, in <module></p><p style="margin-bottom: 0cm" class=""> sys.exit(main())</p><p style="margin-bottom: 0cm" class=""> File
"/opt/grass/etc/wxpython/wxgui.py", line 132, in main</p><p style="margin-bottom: 0cm" class=""> app = GMApp(workspaceFile)</p><p style="margin-bottom: 0cm" class=""> File
"/opt/grass/etc/wxpython/wxgui.py", line 45, in __init__</p><p style="margin-bottom: 0cm" class=""> wx.App.__init__(self, False)</p><p style="margin-bottom: 0cm" class=""> File
"/usr/lib/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py",
line 7981, in __init__</p><p style="margin-bottom: 0cm" class=""> self._BootstrapApp()</p><p style="margin-bottom: 0cm" class=""> File
"/usr/lib/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py",
line 7555, in _BootstrapApp</p><p style="margin-bottom: 0cm" class=""> return
_core_.PyApp__BootstrapApp(*args, **kwargs)</p><p style="margin-bottom: 0cm" class=""> File
"/opt/grass/etc/wxpython/wxgui.py", line 78, in OnInit</p><p style="margin-bottom: 0cm" class=""> workspace = self.workspaceFile)</p><p style="margin-bottom: 0cm" class=""> File
"/opt/grass/etc/wxpython/lmgr/frame.py", line 111, in
__init__</p><p style="margin-bottom: 0cm" class=""> self.toolbars = { 'workspace' :
LMWorkspaceToolbar(parent = self),</p><p style="margin-bottom: 0cm" class=""> File
"/opt/grass/etc/wxpython/lmgr/toolbars.py", line 40, in
__init__</p><p style="margin-bottom: 0cm" class="">
self.InitToolbar(self._toolbarData())</p><p style="margin-bottom: 0cm" class=""> File
"/opt/grass/etc/wxpython/gui_core/toolbars.py", line 96, in
InitToolbar</p><p style="margin-bottom: 0cm" class=""> self.CreateTool(*tool)</p><p style="margin-bottom: 0cm" class=""> File
"/opt/grass/etc/wxpython/gui_core/toolbars.py", line 120,
in CreateTool</p><p style="margin-bottom: 0cm" class=""> shortHelp, longHelp)</p><p style="margin-bottom: 0cm" class=""> File
"/usr/lib/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_controls.py",
line 3764, in AddLabelTool</p><p style="margin-bottom: 0cm" class=""> shortHelp, longHelp, clientData)</p><p style="margin-bottom: 0cm" class=""> File
"/usr/lib/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_controls.py",
line 3686, in DoAddTool</p><p style="margin-bottom: 0cm" class=""> return
_controls_.ToolBarBase_DoAddTool(*args, **kwargs)</p><p style="margin-bottom: 0cm" class="">ValueError: invalid null reference in
method 'ToolBarBase_DoAddTool', expected argument 4 of type 'wxBitmap
const &'</p><div class=""><br class=""></div><div class="">I am assuming both the errors in 13.2 and now in 13.1 are due to installation issues. Grass 6.4 worked well in 13.1 until I upgraded. Can anyone help?</div><div class=""><br class=""></div><div class="">Thanks</div><div class=""><br class=""></div><div class="">Tim</div><div class="">
<div class="">Tim Southern</div><div class="">17, Park Close,</div><div class="">Sonning Common,</div><div class="">Oxfordshire</div><div class="">RG4 9RY</div><div class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 25 Nov 2014, at 20:00, <a href="mailto:grass-user-request@lists.osgeo.org" class="">grass-user-request@lists.osgeo.org</a> wrote:</div><br class="Apple-interchange-newline"><div class="">Send grass-user mailing list submissions to<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:grass-user@lists.osgeo.org" class="">grass-user@lists.osgeo.org</a><br class=""><br class="">To subscribe or unsubscribe via the World Wide Web, visit<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>http://lists.osgeo.org/mailman/listinfo/grass-user<br class="">or, via email, send a message with subject or body 'help' to<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>grass-user-request@lists.osgeo.org<br class=""><br class="">You can reach the person managing the list at<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>grass-user-owner@lists.osgeo.org<br class=""><br class="">When replying, please edit your Subject line so it is more specific<br class="">than "Re: Contents of grass-user digest..."<br class=""><br class=""><br class="">Today's Topics:<br class=""><br class=""> 1. Re: Computing major and minor axes for polygons (Benjamin Ducke)<br class=""> 2. Re: Computing major and minor axes for polygons (S?ren Gebbert)<br class=""> 3. Re: Computing major and minor axes for polygons (Nikos Alexandris)<br class=""><br class=""><br class="">----------------------------------------------------------------------<br class=""><br class="">Message: 1<br class="">Date: Mon, 24 Nov 2014 22:50:46 +0100<br class="">From: Benjamin Ducke <benducke@fastmail.fm><br class="">To: grass-user <grass-user@lists.osgeo.org><br class="">Subject: Re: [GRASS-user] Computing major and minor axes for polygons<br class="">Message-ID: <5473A836.5030305@fastmail.fm><br class="">Content-Type: text/plain; charset=utf-8<br class=""><br class="">Right, a PCA of the polygon vertices, I assume?<br class="">Maybe "v.to.db" could be enhanced to allow it to upload<br class="">the lengths of the first two/three components to the<br class="">attribute table?<br class=""><br class="">For a quick fix, I solved the problem in a shell script using<br class="">a crude approximation. FWIW:<br class="">0. Set major axis length=-1<br class="">1. Rotate polygon by 10? (v.transform)<br class="">2. Fit region to polygon (g.region vect=).<br class="">3. Get width of region. If it is greater than major axis length,<br class=""> set "major axis length = width"<br class="">4. Repeat from 1, until polygon has been rotated 350?<br class="">5. Minor axis length = height of current region.<br class=""><br class="">Like I said, it's just a crude approximation (precision can<br class="">be increased by using smaller rotation steps) and slow, too.<br class="">But it's good enough for my purposes, which is basically to<br class="">calculate "elongation=len(major)/len(min)".<br class=""><br class="">Best,<br class=""><br class="">Ben<br class=""><br class="">On 24/11/14 19:27, S?ren Gebbert wrote:<br class=""><blockquote type="cite" class="">IIRC is the code to compute the major and minor axes already in GRASS.<br class="">You need to perform a Karhunen-Loewe-Transformation for each Polygon.<br class="">This is also known as principal components analysis.<br class=""><br class="">Best regards<br class="">Soeren<br class=""><br class="">Am 21.11.2014 23:33 schrieb "Benjamin Ducke" <benducke@fastmail.fm<br class=""><mailto:benducke@fastmail.fm>>:<br class=""><br class=""> Hi All --<br class=""><br class=""> Does anybody here know of an existing GRASS modules that<br class=""> will compute the major and minor axes for the polygons of<br class=""> a vector map?<br class=""><br class=""> Thanks and best,<br class=""><br class=""> Ben<br class=""> _______________________________________________<br class=""> grass-user mailing list<br class=""> grass-user@lists.osgeo.org <mailto:grass-user@lists.osgeo.org><br class=""> http://lists.osgeo.org/mailman/listinfo/grass-user<br class=""><br class=""></blockquote><br class=""><br class=""><br class="">-- <br class="">Dr. Benjamin Ducke<br class="">{*} Geospatial Consultant<br class="">{*} GIS Developer<br class=""><br class="">Spatial technology for the masses, not the classes:<br class="">experience free and open source GIS at http://gvsigce.org<br class=""><br class=""><br class="">------------------------------<br class=""><br class="">Message: 2<br class="">Date: Mon, 24 Nov 2014 23:44:29 +0100<br class="">From: S?ren Gebbert <soerengebbert@googlemail.com><br class="">To: Benjamin Ducke <benducke@fastmail.fm><br class="">Cc: grass-user <grass-user@lists.osgeo.org><br class="">Subject: Re: [GRASS-user] Computing major and minor axes for polygons<br class="">Message-ID:<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><CAPHDReJy+aLKPEZThfCd+8M935qGiLD1f-yNhrjemZ-s8RUmog@mail.gmail.com><br class="">Content-Type: text/plain; charset=UTF-8<br class=""><br class="">Hi Ben,<br class=""><br class="">2014-11-24 22:50 GMT+01:00 Benjamin Ducke <benducke@fastmail.fm>:<br class=""><blockquote type="cite" class="">Right, a PCA of the polygon vertices, I assume?<br class=""></blockquote><br class="">Exactly, create a covariance matrix from the vertices coordinates of<br class="">each polygon<br class="">and compute the eigenvectors and eigenvalues of these matrices.<br class=""><br class="">Best regards<br class="">Soeren<br class=""><br class=""><blockquote type="cite" class="">Maybe "v.to.db" could be enhanced to allow it to upload<br class="">the lengths of the first two/three components to the<br class="">attribute table?<br class=""><br class="">For a quick fix, I solved the problem in a shell script using<br class="">a crude approximation. FWIW:<br class="">0. Set major axis length=-1<br class="">1. Rotate polygon by 10? (v.transform)<br class="">2. Fit region to polygon (g.region vect=).<br class="">3. Get width of region. If it is greater than major axis length,<br class=""> set "major axis length = width"<br class="">4. Repeat from 1, until polygon has been rotated 350?<br class="">5. Minor axis length = height of current region.<br class=""><br class="">Like I said, it's just a crude approximation (precision can<br class="">be increased by using smaller rotation steps) and slow, too.<br class="">But it's good enough for my purposes, which is basically to<br class="">calculate "elongation=len(major)/len(min)".<br class=""><br class="">Best,<br class=""><br class="">Ben<br class=""><br class="">On 24/11/14 19:27, S?ren Gebbert wrote:<br class=""><blockquote type="cite" class="">IIRC is the code to compute the major and minor axes already in GRASS.<br class="">You need to perform a Karhunen-Loewe-Transformation for each Polygon.<br class="">This is also known as principal components analysis.<br class=""><br class="">Best regards<br class="">Soeren<br class=""><br class="">Am 21.11.2014 23:33 schrieb "Benjamin Ducke" <benducke@fastmail.fm<br class=""><mailto:benducke@fastmail.fm>>:<br class=""><br class=""> Hi All --<br class=""><br class=""> Does anybody here know of an existing GRASS modules that<br class=""> will compute the major and minor axes for the polygons of<br class=""> a vector map?<br class=""><br class=""> Thanks and best,<br class=""><br class=""> Ben<br class=""> _______________________________________________<br class=""> grass-user mailing list<br class=""> grass-user@lists.osgeo.org <mailto:grass-user@lists.osgeo.org><br class=""> http://lists.osgeo.org/mailman/listinfo/grass-user<br class=""><br class=""></blockquote><br class=""><br class=""><br class="">--<br class="">Dr. Benjamin Ducke<br class="">{*} Geospatial Consultant<br class="">{*} GIS Developer<br class=""><br class="">Spatial technology for the masses, not the classes:<br class="">experience free and open source GIS at http://gvsigce.org<br class="">_______________________________________________<br class="">grass-user mailing list<br class="">grass-user@lists.osgeo.org<br class="">http://lists.osgeo.org/mailman/listinfo/grass-user<br class=""></blockquote><br class=""><br class="">------------------------------<br class=""><br class="">Message: 3<br class="">Date: Tue, 25 Nov 2014 19:10:38 +0200<br class="">From: Nikos Alexandris <nik@nikosalexandris.net><br class="">To: <grass-user@lists.osgeo.org><br class="">Subject: Re: [GRASS-user] Computing major and minor axes for polygons<br class="">Message-ID: <5db8e3e250d0adde57c6a9628ba5611f@nikosalexandris.net><br class="">Content-Type: text/plain; charset=UTF-8; format=flowed<br class=""><br class="">On 24.11.2014 23:50, Benjamin Ducke wrote:<br class=""><blockquote type="cite" class="">Right, a PCA of the polygon vertices, I assume?<br class="">Maybe "v.to.db" could be enhanced to allow it to upload<br class="">the lengths of the first two/three components to the<br class="">attribute table?<br class=""><br class="">For a quick fix, I solved the problem in a shell script using<br class="">a crude approximation. FWIW:<br class="">0. Set major axis length=-1<br class="">1. Rotate polygon by 10? (v.transform)<br class="">2. Fit region to polygon (g.region vect=).<br class="">3. Get width of region. If it is greater than major axis length,<br class=""> set "major axis length = width"<br class="">4. Repeat from 1, until polygon has been rotated 350?<br class="">5. Minor axis length = height of current region.<br class=""></blockquote><br class="">Wow, What a smart approach! :-)<br class=""><br class="">Nikos<br class=""><br class=""><br class="">------------------------------<br class=""><br class="">_______________________________________________<br class="">grass-user mailing list<br class="">grass-user@lists.osgeo.org<br class="">http://lists.osgeo.org/mailman/listinfo/grass-user<br class=""><br class="">End of grass-user Digest, Vol 103, Issue 42<br class="">*******************************************<br class=""></div></blockquote></div><br class=""></div></body></html>