[GRASS-user] Opensuse 13.1 Grass
Tim Southern
tim.southern at talktalk.net
Sun Nov 30 01:13:51 PST 2014
Can confirm that Grass is apparently working under 13.1. Grass crashed trying to save a screen image from the Grass toolbar command. Rebooted ok.
Thanks.
Will try and install 13.2 again and try Grass. Why was Numpy incomplete?
Kind regards
Tim
Tim Southern
17, Park Close,
Sonning Common,
Oxfordshire
RG4 9RY
> On 30 Nov 2014, at 05:02, grass-user-request at lists.osgeo.org wrote:
>
> Send grass-user mailing list submissions to
> grass-user at lists.osgeo.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.osgeo.org/mailman/listinfo/grass-user
> or, via email, send a message with subject or body 'help' to
> grass-user-request at lists.osgeo.org
>
> You can reach the person managing the list at
> grass-user-owner at lists.osgeo.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of grass-user digest..."
>
>
> Today's Topics:
>
> 1. Re: Grass 6.4, Opensuse 13.1/13.2 (Angelos Tzotsos)
> 2. mapping interface (shashank khare)
> 3. Re: how to change all cats in a vector line
> (C?sar Augusto Ram?rez Franco)
> 4. Re: grass-user Digest, Vol 103, Issue 47 (Michael Barton)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 30 Nov 2014 05:16:07 +0200
> From: Angelos Tzotsos <gcpp.kalxas at gmail.com>
> To: grass-user at lists.osgeo.org
> Subject: Re: [GRASS-user] Grass 6.4, Opensuse 13.1/13.2
> Message-ID: <547A8BF7.3090306 at gmail.com>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> Problem fixed on both openSUSE 13.1 and 13.2
> Can you please confirm?
>
> On 11/30/2014 01:43 AM, Angelos Tzotsos wrote:
>> Hi Tim,
>>
>> I will have a look at this and report back.
>>
>> Cheers,
>> Angelos
>>
>> On 11/29/2014 03:32 PM, Tim Southern wrote:
>>> Dear all,
>>>
>>> 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)
>>>
>>> I have reverted to Opensuse 13.1 and now have another non working
>>> version Grass 6.4
>>>
>>> Traceback (most recent call
>>> GRASS 6.4.3 (South_Oxfordshire):~ > Traceback (most recent call last):
>>> File "/opt/grass/etc/wxpython/wxgui.py", line 139, in <module>
>>> sys.exit(main())
>>> File "/opt/grass/etc/wxpython/wxgui.py", line 132, in main
>>> app = GMApp(workspaceFile)
>>> File "/opt/grass/etc/wxpython/wxgui.py", line 45, in __init__
>>> wx.App.__init__(self, False)
>>> File
>>> "/usr/lib/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py",
>>> line 7981, in __init__
>>> self._BootstrapApp()
>>> File
>>> "/usr/lib/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py",
>>> line 7555, in _BootstrapApp
>>> return _core_.PyApp__BootstrapApp(*args, **kwargs)
>>> File "/opt/grass/etc/wxpython/wxgui.py", line 78, in OnInit
>>> workspace = self.workspaceFile)
>>> File "/opt/grass/etc/wxpython/lmgr/frame.py", line 111, in __init__
>>> self.toolbars = { 'workspace' : LMWorkspaceToolbar(parent = self),
>>> File "/opt/grass/etc/wxpython/lmgr/toolbars.py", line 40, in __init__
>>> self.InitToolbar(self._toolbarData())
>>> File "/opt/grass/etc/wxpython/gui_core/toolbars.py", line 96, in
>>> InitToolbar
>>> self.CreateTool(*tool)
>>> File "/opt/grass/etc/wxpython/gui_core/toolbars.py", line 120, in
>>> CreateTool
>>> shortHelp, longHelp)
>>> File
>>> "/usr/lib/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_controls.py",
>>> line 3764, in AddLabelTool
>>> shortHelp, longHelp, clientData)
>>> File
>>> "/usr/lib/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_controls.py",
>>> line 3686, in DoAddTool
>>> return _controls_.ToolBarBase_DoAddTool(*args, **kwargs)
>>> ValueError: invalid null reference in method 'ToolBarBase_DoAddTool',
>>> expected argument 4 of type 'wxBitmap const &'
>>>
>>> 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?
>>>
>>> Thanks
>>>
>>> Tim
>>> Tim Southern
>>> 17, Park Close,
>>> Sonning Common,
>>> Oxfordshire
>>> RG4 9RY
>>>
>>>
>>>
>>>> On 25 Nov 2014, at 20:00, grass-user-request at lists.osgeo.org wrote:
>>>>
>>>> Send grass-user mailing list submissions to
>>>> grass-user at lists.osgeo.org
>>>>
>>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>> http://lists.osgeo.org/mailman/listinfo/grass-user
>>>> or, via email, send a message with subject or body 'help' to
>>>> grass-user-request at lists.osgeo.org
>>>>
>>>> You can reach the person managing the list at
>>>> grass-user-owner at lists.osgeo.org
>>>>
>>>> When replying, please edit your Subject line so it is more specific
>>>> than "Re: Contents of grass-user digest..."
>>>>
>>>>
>>>> Today's Topics:
>>>>
>>>> 1. Re: Computing major and minor axes for polygons (Benjamin Ducke)
>>>> 2. Re: Computing major and minor axes for polygons (S?ren Gebbert)
>>>> 3. Re: Computing major and minor axes for polygons (Nikos
>>>> Alexandris)
>>>>
>>>>
>>>> ----------------------------------------------------------------------
>>>>
>>>> Message: 1
>>>> Date: Mon, 24 Nov 2014 22:50:46 +0100
>>>> From: Benjamin Ducke <benducke at fastmail.fm>
>>>> To: grass-user <grass-user at lists.osgeo.org>
>>>> Subject: Re: [GRASS-user] Computing major and minor axes for polygons
>>>> Message-ID: <5473A836.5030305 at fastmail.fm>
>>>> Content-Type: text/plain; charset=utf-8
>>>>
>>>> Right, a PCA of the polygon vertices, I assume?
>>>> Maybe "v.to.db" could be enhanced to allow it to upload
>>>> the lengths of the first two/three components to the
>>>> attribute table?
>>>>
>>>> For a quick fix, I solved the problem in a shell script using
>>>> a crude approximation. FWIW:
>>>> 0. Set major axis length=-1
>>>> 1. Rotate polygon by 10? (v.transform)
>>>> 2. Fit region to polygon (g.region vect=).
>>>> 3. Get width of region. If it is greater than major axis length,
>>>> set "major axis length = width"
>>>> 4. Repeat from 1, until polygon has been rotated 350?
>>>> 5. Minor axis length = height of current region.
>>>>
>>>> Like I said, it's just a crude approximation (precision can
>>>> be increased by using smaller rotation steps) and slow, too.
>>>> But it's good enough for my purposes, which is basically to
>>>> calculate "elongation=len(major)/len(min)".
>>>>
>>>> Best,
>>>>
>>>> Ben
>>>>
>>>> On 24/11/14 19:27, S?ren Gebbert wrote:
>>>>> IIRC is the code to compute the major and minor axes already in GRASS.
>>>>> You need to perform a Karhunen-Loewe-Transformation for each Polygon.
>>>>> This is also known as principal components analysis.
>>>>>
>>>>> Best regards
>>>>> Soeren
>>>>>
>>>>> Am 21.11.2014 23:33 schrieb "Benjamin Ducke" <benducke at fastmail.fm
>>>>> <mailto:benducke at fastmail.fm>>:
>>>>>
>>>>> Hi All --
>>>>>
>>>>> Does anybody here know of an existing GRASS modules that
>>>>> will compute the major and minor axes for the polygons of
>>>>> a vector map?
>>>>>
>>>>> Thanks and best,
>>>>>
>>>>> Ben
>>>>> _______________________________________________
>>>>> grass-user mailing list
>>>>> grass-user at lists.osgeo.org <mailto:grass-user at lists.osgeo.org>
>>>>> http://lists.osgeo.org/mailman/listinfo/grass-user
>>>>>
>>>>
>>>>
>>>> --
>>>> Dr. Benjamin Ducke
>>>> {*} Geospatial Consultant
>>>> {*} GIS Developer
>>>>
>>>> Spatial technology for the masses, not the classes:
>>>> experience free and open source GIS at http://gvsigce.org
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>> Message: 2
>>>> Date: Mon, 24 Nov 2014 23:44:29 +0100
>>>> From: S?ren Gebbert <soerengebbert at googlemail.com>
>>>> To: Benjamin Ducke <benducke at fastmail.fm>
>>>> Cc: grass-user <grass-user at lists.osgeo.org>
>>>> Subject: Re: [GRASS-user] Computing major and minor axes for polygons
>>>> Message-ID:
>>>> <CAPHDReJy+aLKPEZThfCd+8M935qGiLD1f-yNhrjemZ-s8RUmog at mail.gmail.com>
>>>>
>>>> Content-Type: text/plain; charset=UTF-8
>>>>
>>>> Hi Ben,
>>>>
>>>> 2014-11-24 22:50 GMT+01:00 Benjamin Ducke <benducke at fastmail.fm>:
>>>>> Right, a PCA of the polygon vertices, I assume?
>>>> Exactly, create a covariance matrix from the vertices coordinates of
>>>> each polygon
>>>> and compute the eigenvectors and eigenvalues of these matrices.
>>>>
>>>> Best regards
>>>> Soeren
>>>>
>>>>> Maybe "v.to.db" could be enhanced to allow it to upload
>>>>> the lengths of the first two/three components to the
>>>>> attribute table?
>>>>>
>>>>> For a quick fix, I solved the problem in a shell script using
>>>>> a crude approximation. FWIW:
>>>>> 0. Set major axis length=-1
>>>>> 1. Rotate polygon by 10? (v.transform)
>>>>> 2. Fit region to polygon (g.region vect=).
>>>>> 3. Get width of region. If it is greater than major axis length,
>>>>> set "major axis length = width"
>>>>> 4. Repeat from 1, until polygon has been rotated 350?
>>>>> 5. Minor axis length = height of current region.
>>>>>
>>>>> Like I said, it's just a crude approximation (precision can
>>>>> be increased by using smaller rotation steps) and slow, too.
>>>>> But it's good enough for my purposes, which is basically to
>>>>> calculate "elongation=len(major)/len(min)".
>>>>>
>>>>> Best,
>>>>>
>>>>> Ben
>>>>>
>>>>> On 24/11/14 19:27, S?ren Gebbert wrote:
>>>>>> IIRC is the code to compute the major and minor axes already in
>>>>>> GRASS.
>>>>>> You need to perform a Karhunen-Loewe-Transformation for each Polygon.
>>>>>> This is also known as principal components analysis.
>>>>>>
>>>>>> Best regards
>>>>>> Soeren
>>>>>>
>>>>>> Am 21.11.2014 23:33 schrieb "Benjamin Ducke" <benducke at fastmail.fm
>>>>>> <mailto:benducke at fastmail.fm>>:
>>>>>>
>>>>>> Hi All --
>>>>>>
>>>>>> Does anybody here know of an existing GRASS modules that
>>>>>> will compute the major and minor axes for the polygons of
>>>>>> a vector map?
>>>>>>
>>>>>> Thanks and best,
>>>>>>
>>>>>> Ben
>>>>>> _______________________________________________
>>>>>> grass-user mailing list
>>>>>> grass-user at lists.osgeo.org <mailto:grass-user at lists.osgeo.org>
>>>>>> http://lists.osgeo.org/mailman/listinfo/grass-user
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Dr. Benjamin Ducke
>>>>> {*} Geospatial Consultant
>>>>> {*} GIS Developer
>>>>>
>>>>> Spatial technology for the masses, not the classes:
>>>>> experience free and open source GIS at http://gvsigce.org
>>>>> _______________________________________________
>>>>> grass-user mailing list
>>>>> grass-user at lists.osgeo.org
>>>>> http://lists.osgeo.org/mailman/listinfo/grass-user
>>>>
>>>> ------------------------------
>>>>
>>>> Message: 3
>>>> Date: Tue, 25 Nov 2014 19:10:38 +0200
>>>> From: Nikos Alexandris <nik at nikosalexandris.net>
>>>> To: <grass-user at lists.osgeo.org>
>>>> Subject: Re: [GRASS-user] Computing major and minor axes for polygons
>>>> Message-ID: <5db8e3e250d0adde57c6a9628ba5611f at nikosalexandris.net>
>>>> Content-Type: text/plain; charset=UTF-8; format=flowed
>>>>
>>>> On 24.11.2014 23:50, Benjamin Ducke wrote:
>>>>> Right, a PCA of the polygon vertices, I assume?
>>>>> Maybe "v.to.db" could be enhanced to allow it to upload
>>>>> the lengths of the first two/three components to the
>>>>> attribute table?
>>>>>
>>>>> For a quick fix, I solved the problem in a shell script using
>>>>> a crude approximation. FWIW:
>>>>> 0. Set major axis length=-1
>>>>> 1. Rotate polygon by 10? (v.transform)
>>>>> 2. Fit region to polygon (g.region vect=).
>>>>> 3. Get width of region. If it is greater than major axis length,
>>>>> set "major axis length = width"
>>>>> 4. Repeat from 1, until polygon has been rotated 350?
>>>>> 5. Minor axis length = height of current region.
>>>> Wow, What a smart approach! :-)
>>>>
>>>> Nikos
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>> _______________________________________________
>>>> grass-user mailing list
>>>> grass-user at lists.osgeo.org
>>>> http://lists.osgeo.org/mailman/listinfo/grass-user
>>>>
>>>> End of grass-user Digest, Vol 103, Issue 42
>>>> *******************************************
>>>
>>>
>>>
>>> _______________________________________________
>>> grass-user mailing list
>>> grass-user at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/grass-user
>>
>>
>
>
> --
> Angelos Tzotsos
> Remote Sensing Laboratory
> National Technical University of Athens
> http://users.ntua.gr/tzotsos
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 30 Nov 2014 03:46:54 +0000
> From: shashank khare <skhare at hotmail.com>
> To: "grass-user at lists.osgeo.org" <grass-user at lists.osgeo.org>
> Subject: [GRASS-user] mapping interface
> Message-ID: <BLU175-W24E2D4661F9FD9E586BF7CC97C0 at phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I want to develop a mapping application using python for avalanche flow simulation which takes a lot of user inputs. I do not want to go through wxGUI as the user is not interested in options shown by its GUI. Is there any documentation about 2d/3d mapping interface classes/modules which I can use. If these are not documented I can help in it.
> ThanksShash
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20141130/ce5cae59/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 30 Nov 2014 04:13:43 +0000
> From: C?sar Augusto Ram?rez Franco <caesarivs at gmail.com>
> To: GRASS User List <grass-user at lists.osgeo.org>
> Subject: Re: [GRASS-user] how to change all cats in a vector line
> Message-ID:
> <CAJDYeikYbxrb3-w3ZSiiN3ufZoLzQRnQow+RjgD5=RZDs67XVw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello Michael
>
> You could use r.stream.order after r.stream.extract to get your stream
> network ordered, and then, after running r.thin on the ordered stream
> network, convert it to vector using r.to.vect with the -v flag, that way,
> each order is a cat, you can them use v.to.points or the add-on suggested
> below to get topologically-correct points along the stream network, you
> could also use r.stream.distance and upload distance and elevation to each
> point using v.what.rast
>
> I usually run R from within GRASS and use the spgrass6 library to read the
> vector map and analyze the data there
>
> Regards
>
> C?sar.
>
> El s?b, 29 de noviembre de 2014 06:29 p.m., Helmut Kudrnovsky <hellik at web.de>
> escribi?:
>
>> Michael Barton wrote
>>> Hi Markus,
>>>
>>> What I'm trying to do is start with a raster stream map from r.drain and
>>> convert it to a sequence of vector points, where each point has
>>> information as to its position along the stream. I then use the points
>> for
>>> sampling a stream profile and related information. Oddly enough, with all
>>> of the very useful stream analysis modules, there is nothing I could find
>>> to generate the data for a stream profile (distance from outlet or from
>>> headwaters vs. elevation).
>>>
>>> v.to.points does a nice job of creating a sequence of evenly spaced
>> points
>>> with information about their location along a line (the "along" field).
>>> BUT, if the line is composed of multiple segments or even if it has an
>>> irregularity in it, the "along" values start over again from 0. The only
>>> way I can use it is if I have a very clean and continuous vector line
>> with
>>> only a single cat.
>>>
>>> This has proven surprisingly difficult to obtain reliably from my raster
>>> stream map. So far, the only way has been to do a two sequences of
>> v.clean
>>> (with thresholds 1.5 X the raster resolution) and v.build.polylines. If
>>> you have any better suggestion, I'd love to hear it.
>>>
>>> Thanks again for the polylines idea. That was a big help.
>>>
>>> Michael
>>> ____________________
>>> C. Michael Barton
>>> Director, Center for Social Dynamics & Complexity
>>> Professor of Anthropology, School of Human Evolution & Social Change
>>> Head, Graduate Faculty in Complex Adaptive Systems Science
>>> Arizona State University
>>>
>>> voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
>>> fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
>>> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
>>>
>>>
>>>
>>>
>>>> On Nov 29, 2014, at 10:20 AM, Michael Barton <
>>
>>> Michael.Barton@
>>
>>> > wrote:
>>>>
>>>> Thanks. This helped.
>>>>
>>>> Michael
>>>> ____________________
>>>> C. Michael Barton
>>>> Director, Center for Social Dynamics & Complexity
>>>> Professor of Anthropology, School of Human Evolution & Social Change
>>>> Head, Graduate Faculty in Complex Adaptive Systems Science
>>>> Arizona State University
>>>>
>>>> voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
>>>> fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
>>>> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> On Nov 29, 2014, at 1:23 AM, Markus Neteler <
>>
>>> neteler@
>>
>>> > wrote:
>>>>>
>>>>> On Sat, Nov 29, 2014 at 6:16 AM, Michael Barton <
>>
>>> Michael.Barton@
>>
>>> > wrote:
>>>>>> I have a vector line that is divided into 12 cat values. I?d like all
>>>>>> of the
>>>>>> line to have a single cat value. I?ve tried v.category to no avail. If
>>>>>> I
>>>>>> delete all categories and then add new categories, I get 12 cats
>> again.
>>>>>> And
>>>>>> I can find no other way to get a single cat for the entire line.
>>>>>> Hopefully
>>>>>> someone can tell what I?m missing here.
>>>>>
>>>>> Please try to use
>>>>> http://grass.osgeo.org/grass70/manuals/v.build.polylines.html
>>>>>
>>>>> Markus
>>>>
>>>
>>> _______________________________________________
>>> grass-user mailing list
>>
>>> grass-user at .osgeo
>>
>>> http://lists.osgeo.org/mailman/listinfo/grass-user
>>
>> http://grass.osgeo.org/grass71/manuals/r.stream.extract.html ?
>>
>>
>>
>> -----
>> best regards
>> Helmut
>> --
>> View this message in context: http://osgeo-org.1560.x6.
>> nabble.com/how-to-change-all-cats-in-a-vector-line-tp5175575p5175634.html
>> Sent from the Grass - Users mailing list archive at Nabble.com.
>> _______________________________________________
>> grass-user mailing list
>> grass-user at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/grass-user
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20141130/fc9f610c/attachment-0001.html>
>
> ------------------------------
>
> Message: 4
> Date: Sun, 30 Nov 2014 04:51:04 +0000
> From: Michael Barton <Michael.Barton at asu.edu>
> To: grass-user grass-user <grass-user at lists.osgeo.org>
> Subject: Re: [GRASS-user] grass-user Digest, Vol 103, Issue 47
> Message-ID: <D877804B-CAF8-4178-9156-6D2F160CA3C0 at asu.edu>
> Content-Type: text/plain; charset="utf-8"
>
> r.stream.extract can make the raster streams?ones that are pretty much equivalent to those made with r.watershed. But it can?t do stream profiles AFAICT. Also, like r.watershed, it extracts a stream network, not a particular stream. That is why we?re using r.drain to extract a particular drainage.
>
> MICHAEL
> ____________________
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Professor of Anthropology, School of Human Evolution & Social Change
> Head, Graduate Faculty in Complex Adaptive Systems Science
> Arizona State University
>
> voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
>
>
>
> On Nov 29, 2014, at 4:40 PM, grass-user-request at lists.osgeo.org<mailto:grass-user-request at lists.osgeo.org> wrote:
>
> Re: [GRASS-user] how to change all cats in a vector line
>
>
> Michael Barton wrote
> Hi Markus,
>
> What I'm trying to do is start with a raster stream map from r.drain and
> convert it to a sequence of vector points, where each point has
> information as to its position along the stream. I then use the points for
> sampling a stream profile and related information. Oddly enough, with all
> of the very useful stream analysis modules, there is nothing I could find
> to generate the data for a stream profile (distance from outlet or from
> headwaters vs. elevation).
>
> v.to.points does a nice job of creating a sequence of evenly spaced points
> with information about their location along a line (the "along" field).
> BUT, if the line is composed of multiple segments or even if it has an
> irregularity in it, the "along" values start over again from 0. The only
> way I can use it is if I have a very clean and continuous vector line with
> only a single cat.
>
> This has proven surprisingly difficult to obtain reliably from my raster
> stream map. So far, the only way has been to do a two sequences of v.clean
> (with thresholds 1.5 X the raster resolution) and v.build.polylines. If
> you have any better suggestion, I'd love to hear it.
>
> Thanks again for the polylines idea. That was a big help.
>
> Michael
> ____________________
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Professor of Anthropology, School of Human Evolution & Social Change
> Head, Graduate Faculty in Complex Adaptive Systems Science
> Arizona State University
>
> voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu<http://csdc.asu.edu/>
>
>
>
>
> On Nov 29, 2014, at 10:20 AM, Michael Barton <
>
> Michael.Barton@
>
> > wrote:
>
> Thanks. This helped.
>
> Michael
> ____________________
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Professor of Anthropology, School of Human Evolution & Social Change
> Head, Graduate Faculty in Complex Adaptive Systems Science
> Arizona State University
>
> voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu<http://csdc.asu.edu/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Nov 29, 2014, at 1:23 AM, Markus Neteler <
>
> neteler@
>
> > wrote:
>
> On Sat, Nov 29, 2014 at 6:16 AM, Michael Barton <
>
> Michael.Barton@
>
> > wrote:
> I have a vector line that is divided into 12 cat values. I?d like all
> of the
> line to have a single cat value. I?ve tried v.category to no avail. If
> I
> delete all categories and then add new categories, I get 12 cats again.
> And
> I can find no other way to get a single cat for the entire line.
> Hopefully
> someone can tell what I?m missing here.
>
> Please try to use
> http://grass.osgeo.org/grass70/manuals/v.build.polylines.html
>
> Markus
>
>
> _______________________________________________
> grass-user mailing list
>
> grass-user at .osgeo
>
> http://lists.osgeo.org/mailman/listinfo/grass-user
>
> http://grass.osgeo.org/grass71/manuals/r.stream.extract.html ?
>
>
>
> -----
> best regards
> Helmut
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20141130/1cda7384/attachment.html>
>
> ------------------------------
>
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user
>
> End of grass-user Digest, Vol 103, Issue 48
> *******************************************
More information about the grass-user
mailing list