Re: [GRASS-user] G_malloc: out of memory
Kurt: > I am running into a problem I've never seen before. I > was trying to digitize a vector file. I had imported it > from a dxf file and was trying to close up some vectors > points. Suddenly v.digit closed, and when I tried to reopen > I got: > > v.digit(4314,0xa0371fa0) malloc: *** mmap(size=1207963648) > failed (error code=12) > *** error: can't allocate region > *** set a breakpoint in malloc_error_break to debug > > G_malloc: out of memory whenever v.digit crashes try "v.build mapname" to recover. Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] GRASS tools for palsar/radar images
Hi, I'm looking for some tools in processing radar/palsar data. pre-processing, image classification, etc. So far, I found RAT radartools http://srv-43-200.bv.tu-berlin.de/rat/index.php Any GRASS user doing radar processing? cheers, maning -- |-|--| | __.-._ |"Ohhh. Great warrior. Wars not make one great." -Yoda | | '-._"7' |"Freedom is still the most radical idea of all" -N.Branden| | /'.-c |Linux registered user #402901, http://counter.li.org/ | | | /T |http://esambale.wikispaces.com/ | | _)_/L I http://epsg4253.wordpress.com/ | |-|--| ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] G_malloc: out of memory
I used g.region to set the resolution from 10m to 100m, then to 1m. on 100m I get PNG: GRASS_TRUECOLOR status: TRUE PNG: collecting to file: /Users/kurtsprings/grassdata/OSI0834/ PERMANENT/.tmp/Kurt-Springs-MacPro.local/5417.0.ppm, GRASS_WIDTH=309, GRASS_HEIGHT=482 d.rast(5512) malloc: *** mmap(size=1206358016) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug G_malloc: out of memory on 1m I get PNG: GRASS_TRUECOLOR status: TRUE PNG: collecting to file: /Users/kurtsprings/grassdata/OSI0834/ PERMANENT/.tmp/Kurt-Springs-MacPro.local/5417.0.ppm, GRASS_WIDTH=309, GRASS_HEIGHT=482 d.rast(5528) malloc: *** mmap(size=1206358016) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug G_malloc: out of memory Other project locations, set at 10m are okay. Kurt On Nov 20, 2008, at 6:59 PM, Glynn Clements wrote: Kurt Springs wrote: I am running into a problem I've never seen before. I was trying to digitize a vector file. I had imported it from a dxf file and was trying to close up some vectors points. Suddenly v.digit closed, and when I tried to reopen I got: v.digit(4314,0xa0371fa0) malloc: *** mmap(size=1207963648) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug G_malloc: out of memory When I tried to open my raster map I got: PNG: GRASS_TRUECOLOR status: TRUE PNG: collecting to file: /Users/kurtsprings/grassdata/OSI0834/ PERMANENT/.tmp/Kurt-Springs-MacPro.local/4266.0.ppm, GRASS_WIDTH=309, GRASS_HEIGHT=482 d.rast(4325) malloc: *** mmap(size=1206358016) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug G_malloc: out of memory I tried opening a different project location and it still works. Can anyone tell me what is wrong and how to get this project location up and running again, or what went wrong to begin with. The most likely reason is that the region resolution is too fine. Use "g.region res=..." to change it, or "g.region -d" to restore the default region. -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] G_malloc: out of memory
Kurt Springs wrote: > I am running into a problem I've never seen before. I was trying to > digitize a vector file. I had imported it from a dxf file and was > trying to close up some vectors points. Suddenly v.digit closed, and > when I tried to reopen I got: > > v.digit(4314,0xa0371fa0) malloc: *** mmap(size=1207963648) failed > (error code=12) > *** error: can't allocate region > *** set a breakpoint in malloc_error_break to debug > > G_malloc: out of memory > > When I tried to open my raster map I got: > > > PNG: GRASS_TRUECOLOR status: TRUE > > PNG: collecting to file: /Users/kurtsprings/grassdata/OSI0834/ > PERMANENT/.tmp/Kurt-Springs-MacPro.local/4266.0.ppm, > > GRASS_WIDTH=309, GRASS_HEIGHT=482 > d.rast(4325) malloc: *** mmap(size=1206358016) failed (error code=12) > *** error: can't allocate region > *** set a breakpoint in malloc_error_break to debug > > G_malloc: out of memory > > I tried opening a different project location and it still works. Can > anyone tell me what is wrong and how to get this project location up > and running again, or what went wrong to begin with. The most likely reason is that the region resolution is too fine. Use "g.region res=..." to change it, or "g.region -d" to restore the default region. -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] drawing wind vectors
Alberto Pettazzi wrote: > Hi > everybody! > > I have 2 files, containing u and v component of wind vector > respectively. Is there any simple way to plot the wind > field? > > thank you as usual, > > -- [please post in plain text, html makes it hard for some of us to read...] Use the d.rast.arrow module. See the help page for conversion of u,v to magnitude,direction. (assuming you can make u,v into raster maps; what form is the data in?) d.rast.arrow screenshot here: http://grass.osgeo.org/screenshots/raster.php In Matlab this is known as a quiver plot, here is a addon for Octave to do that with free software: http://octplot.sourceforge.net/quiver.html I had thought for a while to add to d.rast.arrow wind barb rendering, and with the advent of GDAL reading the WMO's GRIB format there is a bit more reason to do that. For now the zyGrib program is nice to look at those: http://zygrib.free.fr/ Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
RE: [GRASS-user] error running digitzing tool wxpython
> Date: Thu, 20 Nov 2008 21:20:22 +0100 > From: [EMAIL PROTECTED] > To: grass-user@lists.osgeo.org > Subject: [GRASS-user] error running digitzing tool wxpython > > Hello Grass Usersgroup > > Running on linux open suse 10.3 have download > grass-6.4.svn_src_snapshot_2008_11_15.tar.gz > en install some additional libraries (wxwidget, wxpyton ,swig etc) and > compiled the source-code include the pyton > digitizing tool v.digit. Check if you compiled the source code -with-python "-with-python" is not enough to get the new wxPython GUI installed. That is only required for the new vdigit. > Running the digitize tool I've the following error masseges: > > if len(self.vdigitMove['id']) > 0: > TypeError > : > tuple indices must be integers > Traceback (most recent call last): > File "/usr/local/grass-6.4.svn/etc/wxpython/gui_modules/ma > pdisp.py", line 1125, in MouseActions > > self.OnMouseMoving(event) > File "/usr/local/grass-6.4.svn/etc/wxpython/gui_modules/ma > pdisp.py", line 2011, in OnMouseMoving > > if len(self.vdigitMove['id']) > 0: > TypeError > : > tuple indices must be integers > Traceback (most recent call last): > File "/usr/local/grass-6.4.svn/etc/wxpython/gui_modules/ma > pdisp.py", line 1125, in MouseActions > > self.OnMouseMoving(event) > File "/usr/local/grass-6.4.svn/etc/wxpython/gui_modules/ma > pdisp.py", line 2011, in OnMouseMoving > > if len(self.vdigitMove['id']) > 0: > TypeError > : > tuple indices must be integers > Traceback (most recent call last): > File "/usr/local/grass-6.4.svn/etc/wxpython/gui_modules/ma > pdisp.py", line 1125, in MouseActions > > self.OnMouseMoving(event) > File "/usr/local/grass-6.4.svn/etc/wxpython/gui_modules/ma > pdisp.py", line 2011, in OnMouseMoving > > if len(self.vdigitMove['id']) > 0: > TypeError > : > tuple indices must be integers > > > What is wrong? > The vectormap contains floating point coordinates, and reading the > report of Martin Landa (Perugia, 21-22 Feb 2008) > wxPython-based GUI for GRASS GIS > > "the general display architecture needs to bee improved to support > floating-point coordinates" > Is here the problem > > > > thanks for help > > Joop Goedbloed > Jhon Ortiz Trujillo Geologist - EOS-DTH - ICP Bogotá - Colombia _ Los más de lo más, Especial Rankings http://events.es.msn.com/dinero/listas/default.aspx___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] G_malloc: out of memory
I am running into a problem I've never seen before. I was trying to digitize a vector file. I had imported it from a dxf file and was trying to close up some vectors points. Suddenly v.digit closed, and when I tried to reopen I got: v.digit(4314,0xa0371fa0) malloc: *** mmap(size=1207963648) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug G_malloc: out of memory When I tried to open my raster map I got: PNG: GRASS_TRUECOLOR status: TRUE PNG: collecting to file: /Users/kurtsprings/grassdata/OSI0834/ PERMANENT/.tmp/Kurt-Springs-MacPro.local/4266.0.ppm, GRASS_WIDTH=309, GRASS_HEIGHT=482 d.rast(4325) malloc: *** mmap(size=1206358016) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug G_malloc: out of memory I tried opening a different project location and it still works. Can anyone tell me what is wrong and how to get this project location up and running again, or what went wrong to begin with. Kurt ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] error running digitzing tool wxpython
Hello Grass Usersgroup Running on linux open suse 10.3 have download grass-6.4.svn_src_snapshot_2008_11_15.tar.gz en install some additional libraries (wxwidget, wxpyton ,swig etc) and compiled the source-code include the pyton digitizing tool v.digit. Running the digitize tool I've the following error masseges: if len(self.vdigitMove['id']) > 0: TypeError : tuple indices must be integers Traceback (most recent call last): File "/usr/local/grass-6.4.svn/etc/wxpython/gui_modules/ma pdisp.py", line 1125, in MouseActions self.OnMouseMoving(event) File "/usr/local/grass-6.4.svn/etc/wxpython/gui_modules/ma pdisp.py", line 2011, in OnMouseMoving if len(self.vdigitMove['id']) > 0: TypeError : tuple indices must be integers Traceback (most recent call last): File "/usr/local/grass-6.4.svn/etc/wxpython/gui_modules/ma pdisp.py", line 1125, in MouseActions self.OnMouseMoving(event) File "/usr/local/grass-6.4.svn/etc/wxpython/gui_modules/ma pdisp.py", line 2011, in OnMouseMoving if len(self.vdigitMove['id']) > 0: TypeError : tuple indices must be integers Traceback (most recent call last): File "/usr/local/grass-6.4.svn/etc/wxpython/gui_modules/ma pdisp.py", line 1125, in MouseActions self.OnMouseMoving(event) File "/usr/local/grass-6.4.svn/etc/wxpython/gui_modules/ma pdisp.py", line 2011, in OnMouseMoving if len(self.vdigitMove['id']) > 0: TypeError : tuple indices must be integers What is wrong? The vectormap contains floating point coordinates, and reading the report of Martin Landa (Perugia, 21-22 Feb 2008) wxPython-based GUI for GRASS GIS "the general display architecture needs to bee improved to support floating-point coordinates" Is here the problem thanks for help Joop Goedbloed ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Varying results - v.select,v.distance,v.what
At 12:15 PM 11/19/2008, Kevin Webb wrote: --Workflow-- A LOCATION was created tailored to the specifics of the layer I am processing. The layer itself was imported using: v.external, followed by v.category, followed by v.db.connect. Am I doing this incorrectly? Should I expect the three methods to yield the same result? Which method is suggested to be the most reliable? Thank you. KFW I decided to run v.select, v.distance, and v.what comparisons on another layer that I have imported using v.external. The 3 query techniques all returned the same value which lead me to believe that it was something I had done improperly on the import sequence for the layer that was giving me erroneous results; investigation yields more questions. --The layer for which v.select, v.distance and v.what results match-- GRASS 6.4.svn (PREC0101):~ > v.db.connect -p PREC0102_EXT Vector map <[EMAIL PROTECTED]> is connected by: layer <1> table in database through driver with key <> GRASS 6.4.svn (PREC0101):~ > v.info -c PREC0102_EXT Displaying column types/names for database connection of layer 1: INTEGER|ID INTEGER|GRIDCODE CHARACTER|INCHES Supposedly, queries are NOT supposed to work on this layer because v.category has not been run - there is no category (cat) field, yet v.select, v.distance, and v.what all work and result values are the same. Why do queries on this layer this work? --The layer for which v.select, v.distance, and v.what results do NOT match-- GRASS 6.4.svn (CENSUS_ESRI_04):~ > v.db.connect -p EXT_CENSUS_CAT Vector map <[EMAIL PROTECTED]> is connected by: layer <1> table in database through driver with key layer <2> table in database through driver with key GRASS 6.4.svn (CENSUS_ESRI_04):~ > v.info -c EXT_CENSUS_CAT layer=1 Displaying column types/names for database connection of layer 1: INTEGER|cat GRASS 6.4.svn (CENSUS_ESRI_04):~ > v.info -c EXT_CENSUS_CAT layer=2 Displaying column types/names for database connection of layer 2: DOUBLE PRECISION|SQMI CHARACTER|STATE_FIPS CHARACTER|CNTY_FIPS CHARACTER|STCOFIPS CHARACTER|TRACT CHARACTER|BLKGRP CHARACTER|FIPS INTEGER|POP2000 DOUBLE PRECISION|POP00_SQMI INTEGER|POP2003 INTEGER|WHITE INTEGER|BLACK INTEGER|AMERI_ES INTEGER|ASIAN INTEGER|HAWN_PI INTEGER|OTHER INTEGER|MULT_RACE INTEGER|HISPANIC INTEGER|MALES INTEGER|FEMALES INTEGER|AGE_UNDER5 INTEGER|AGE_5_17 INTEGER|AGE_18_21 INTEGER|AGE_22_29 INTEGER|AGE_30_39 INTEGER|AGE_40_49 INTEGER|AGE_50_64 INTEGER|AGE_65_UP DOUBLE PRECISION|MED_AGE DOUBLE PRECISION|MED_AGE_M DOUBLE PRECISION|MED_AGE_F INTEGER|HOUSEHOLDS DOUBLE PRECISION|AVE_HH_SZ INTEGER|HSEHLD_1_M INTEGER|HSEHLD_1_F INTEGER|MARHH_CHD INTEGER|MARHH_NO_C INTEGER|MHH_CHILD INTEGER|FHH_CHILD INTEGER|FAMILIES DOUBLE PRECISION|AVE_FAM_SZ INTEGER|HSE_UNITS INTEGER|VACANT INTEGER|OWNER_OCC INTEGER|RENTER_OCC For this layer, point-in-polygon queries are executed on layer#1, and attributes are queried from layer#2; v.select, v.distance, and v.what all return different cat values. v.db.connect -p indicates layer#2 is keyed by the field yet I don't see a 'cat' field in the v.info output, shouldn't there be a 'cat' column in layer#2 or am I misinterpreting how multiple layers are properly added to a vector? Corrections/suggestions? Thank you. KFW ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-dev] Re: [GRASS-user] how to measure distances in a constrained space
Glynn Clements wrote: > > In any case, the specific purpose of r.grow.distance is: > > > >r.grow.distance generates a raster map representing the distance to > >the nearest non-null cell in the input map. > > It now has an additional function: to generate a raster map containing > the value of the nearest cell. > > >From this, it is possible to mimic the behaviour of r.grow, but > substantially faster, with e.g.: > > # equivalent to: r.grow input=$inmap output=$outmap radius=$radius > metric=$metric > temp=r.grow.tmp.$$ > r.grow.distance in=$inmap distance=$temp.dist value=$temp.near metric=$metric > r.mapcalc "$outmap = if($temp.dist < $radius,$temp.near,null())" > r.colors $outmap rast=$temp.near > g.remove rast=$temp.dist,$temp.near > > Whereas the worst-case time taken by r.grow is proportional to the > square of the buffer radius, the above is proportional only to the > area of the map, regardless of the buffer radius. > > I'll replace r.grow in 7.0 with a script along these lines. Done. I've also fixed the spelling of "euclidean" in both r.grow and r.grow.distance, in 6.4 and 7.0. -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Compile grass6_devel with ffmpeg support?
Nikos Alexandris wrote: > Has anybody compiled recently grass6_devel (aka grass-6.4.svn) with > ffmpeg support? > > It does not work for me. Always complaining about missing "ffmpeg > includes" but I am sure they exist on my system > (under /usr/include/ffmpeg). Look at the error messages in config.log. Note that an error reporting a "missing" header means that it failed to compile (more precisely, preprocess) a test program which "#include"s that header. This can be caused by factors other than the header actually being absent. It works for me in 7.0 (with ffmpeg-0.4.9_p20070616-r3) and there are no differences in the FFMPEG configure checks between 6.4 and 7.0. However, the FFMPEG API is quite unstable, and we only attempt to support the most common version (more precisely, the checks get changed when the existing checks no longer work for at least one GRASS developer who understands how to fix configure.in). -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Compile grass6_devel with ffmpeg support?
Hi all! Has anybody compiled recently grass6_devel (aka grass-6.4.svn) with ffmpeg support? It does not work for me. Always complaining about missing "ffmpeg includes" but I am sure they exist on my system (under /usr/include/ffmpeg). Thank you, Nikos ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] calculating statistics based upon a raster patch map
Hufkens Koen wrote: > I've got two maps, a map with patches or areas which I want to evaluate. > A second map contains a parameter which I want to evaluate (average, > std) based upon areas as delineated in the first map. The output of all > this would optimally be a third map with the results of the evaluation > (average, std) given to the areas of the first map. > > Is this possible in a simple way, or should I write something myself. I > can't seem to find a premade function that does this or something close > to it. r.statistics does this, but both inputs have to be integer raster maps. In 7.0-svn, r.statistics2 and r.statistics3 provide similar functionality, but allow the cover map to be floating-point. If your base map is a vector map, you can convert it with v.to.rast. If you need aggregates other than those provided by r.statistics etc, then you can to use r.stats (with the restriction that both maps must be integers) to collate the data into tuples of (base category, cover value, count), and calculate the aggregates with e.g. awk. -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] drawing wind vectors
How are the components formatted? 2008/11/20 Nikos Alexandris <[EMAIL PROTECTED]>: > On Thu, 2008-11-20 at 14:10 +0100, Alberto Pettazzi wrote: >> Hi everybody! >> >> I have 2 files, containing u and v component of wind vector >> respectively. Is there any simple way to plot the wind field? >> >> thank you as usual, >> -- >> >> >> Alberto Pettazzi > > Hi! > > If I got it right then you should have a look at GRASS' module m.cogo > and QGIS' "Azimuth and Distance Plugin". > > Regards, Nikos > > > ___ > grass-user mailing list > grass-user@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-user > ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] drawing wind vectors
On Thu, 2008-11-20 at 14:10 +0100, Alberto Pettazzi wrote: > Hi everybody! > > I have 2 files, containing u and v component of wind vector > respectively. Is there any simple way to plot the wind field? > > thank you as usual, > -- > > > Alberto Pettazzi Hi! If I got it right then you should have a look at GRASS' module m.cogo and QGIS' "Azimuth and Distance Plugin". Regards, Nikos ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] drawing wind vectors
Hi everybody! I have 2 files, containing u and v component of wind vector respectively. Is there any simple way to plot the wind field? thank you as usual, -- Alberto Pettazzi MeteoGalicia - Departamento de Climatología y Observación Consellería de Medio Ambiente e Desenvolvemento Sostible Área Central, Local: L-31-C. Polígono de Fontiñas 15703 Santiago de Compostela. A Coruña Teléfono: +34-981-957463 e-mail: [EMAIL PROTECTED] ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] calculating statistics based upon a raster patch map
On Donnerstag, 20. November 2008 13:57:42 Hufkens Koen wrote: > Hi list, > > I've got two maps, a map with patches or areas which I want to evaluate. A > second map contains a parameter which I want to evaluate (average, std) > based upon areas as delineated in the first map. The output of all this > would optimally be a third map with the results of the evaluation (average, > std) given to the areas of the first map. > > Is this possible in a simple way, or should I write something myself. I > can't seem to find a premade function that does this or something close to > it. it is quit simple: 1) change your 'patch map' with r.to.vect and v.to.rast into individually numbered patches 2) change your value_raster to integer and multiplication (e.g. '*100') is advisable: r.mapcalc "tmp1=int(value_raster*100)" 3) query your raster: r.statistics base=patch_raster cover=tmp1 method=average out=value_raster --o 4) perhaps use r.mapcalc to revert the *100 modification in the new map regards, Martin -- ** University of Wuerzburg Institute of Geography Department of Remote Sensing Remote Sensing and Biodiversity Unit Am Hubland 97074 Wuerzburg, Germany @ German Aerospace Center (DLR) German Remote Sensing Data Center (DFD) Phone: +49-(0)931-888-4797 Fax:+49-(0)931-888-4961 Email: [EMAIL PROTECTED] url: http://www.remote-sensing.uni-wuerzburg.de ** ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] calculating statistics based upon a raster patch map
Hi list, I've got two maps, a map with patches or areas which I want to evaluate. A second map contains a parameter which I want to evaluate (average, std) based upon areas as delineated in the first map. The output of all this would optimally be a third map with the results of the evaluation (average, std) given to the areas of the first map. Is this possible in a simple way, or should I write something myself. I can't seem to find a premade function that does this or something close to it. Kind regards, Koen ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Legend with multiple columns - scale
Casey Vandenberg wrote: > I am new to the world of Grass and have run into a bit of a > snag. I am currently trying to create a legend with > multiple columns (3). I can place the legend on my map > without difficulties, however the problem arises when I try > and move it. Based on the map in question, I want the > legend displayed on the left hand side of my map. As I > alter the legend's x location (where /x/ /y/) to bring > the legend closer to the left edge of the map, the spacing > between the columns increases substantially (i.e. the legend > seems to be maintaining a link to the right edge of the map > and is just increasing the spacing between the columns so > that the left edge of the legend matches the /where x > /position). The problem with this is that it is not > graphically appealing whatsoever. > > Is there anyway that I can specify the width of the column > itself so that the spacing is reduced? Or is there any way > that I can remove that "link" with the right hand > edge of the map so the legend moves freely along the x axis > without being stretched out? There is don't-go-off-the-edge code in there as you suspect. (see ps/ps.map/ps_vlegend.c) Can you file a wish/bug in the tracker for that? preferably with an example from the spearfish or North Carolina test datasets + screenshots of the issue. for now you can play with the paper margins; but is it the paper margin or the map-box margin which is the limit? > Also with regards to my scalebar. Is there any way that I > can change the text of the scalebar so that the units are in > km instead of metres? Right now I am using a map at a scale > of 1:500 000, and I would rather my scalebar display 100 km > as opposed to 100 000 metres. this has recently been added in grass 6.4, you'll need to compile from a SVN snapshot to get it. see the online ps.map help page for details. Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] v.net.iso - node costs
Hi Hamish, all 2008/11/18 Hamish <[EMAIL PROTECTED]>: > > yes, I get the same error. > A trouble shared is a trouble halved. > with `g.gisenv set="DEBUG=5"` it shows that the error arrives in > lib/vector/Vlib/net.c line ~ 374 and lib/vector/Vlib/level_two.c line > ~ 261, but then I find it hard to follow the memory address for > Map->plus.Node[]. > > Not very much about this in the bug tracker. Is this a bug/defect ? Paolo ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
