Re: [GRASS-dev] does GRASS 7 for Mac compile yet?
Hi, On Mon, Feb 4, 2013 at 11:57 PM, epi massimodisa...@gmail.com wrote: i'm trying to debug the build of GRASS 7 on mac OSX 10.8.x in 64 bit with WX 2.9.x After commenting the check for wx version i got the GUI start, some worning what exactly is the problem with the 'check for wx version'? The warning (wx.InitAllImageHandlers) and the PrepareDC error should be fixed now. Anna : ### GRASS 7.0.svn (spearfish60):~ /usr/local/grass-7.0.svn/etc/gui/wxpython/wxgui.py:54: wxPyDeprecationWarning: Call to deprecated item 'InitAllImageHandlers'. wx.InitAllImageHandlers() /usr/local/grass-7.0.svn/etc/gui/wxpython/gui_core/goutput.py:230: wxPyDeprecationWarning: Call to deprecated item 'SetVirtualSizeHints'. outputSizer.SetVirtualSizeHints(self.panelOutput) ### the Window Manager seems to work properly (i cal load a layer Rast/Vect in the lkayer tree, the shell also pront out the log of commands nicely) but i can't display layers (both Vector and Raster are not displayed). Commenting this 2 line in madisp.py : 359 #self.PrepareDC(dc) 519#self.PrepareDC(dc) i got the Raster map displaying properly but no vector, the error is in a missed Cairo Driver : /usr/local/grass-7.0.svn/etc/gui/wxpython/gui_core/ghelp.py: 608: wxPyDeprecationWarning: Call to deprecated item 'InitAllImageHandlers'. wx.InitAllImageHandlers() Command 'd.vect map=archsites@PERMANENT type=point,line,area,face' failed Details: Unknown display driver cairo Command 'd.vect map=archsites@PERMANENT type=point,line,area,face' failed Details: Unknown display driver cairo I wasn't able to get the cairo driver working during the Make step, it shows the error at the end of the log [1] about a missed arch ... but i guess ... I have everything built as --universal In doubt I rebuilt fontconfig and cairo and checked the relative architecture : lipo -info /usr/local/Cellar/cairo/1.12.12/lib/cairo/libcairo-trace.0.dylib /usr/local/Cellar/cairo/1.12.12/lib/libcairo-gobject.2.dylib /usr/local/Cellar/cairo/1.12.12/lib/libcairo-script-interpreter.2.dylib /usr/local/Cellar/cairo/1.12.12/lib/libcairo.2.dylib Architectures in the fat file: /usr/local/Cellar/cairo/1.12.12/lib/cairo/libcairo-trace.0.dylib are: i386 x86_64 Architectures in the fat file: /usr/local/Cellar/cairo/1.12.12/lib/libcairo-gobject.2.dylib are: i386 x86_64 Architectures in the fat file: /usr/local/Cellar/cairo/1.12.12/lib/libcairo-script-interpreter.2.dylib are: i386 x86_64 Architectures in the fat file: /usr/local/Cellar/cairo/1.12.12/lib/libcairo.2.dylib are: i386 x86_64 epi:~ epi$ /usr/local/Cellar/fontconfig/2.10.91/bin/fc-cache:Mach-O universal binary with 2 architectures /usr/local/Cellar/fontconfig/2.10.91/bin/fc-cache (for architecture i386): Mach-O executable i386 /usr/local/Cellar/fontconfig/2.10.91/bin/fc-cache (for architecture x86_64): Mach-O 64-bit executable x86_64 /usr/local/Cellar/fontconfig/2.10.91/bin/fc-cat: Mach-O universal binary with 2 architectures /usr/local/Cellar/fontconfig/2.10.91/bin/fc-cat (for architecture i386): Mach-O executable i386 /usr/local/Cellar/fontconfig/2.10.91/bin/fc-cat (for architecture x86_64): Mach-O 64-bit executable x86_64 /usr/local/Cellar/fontconfig/2.10.91/bin/fc-list: Mach-O universal binary with 2 architectures /usr/local/Cellar/fontconfig/2.10.91/bin/fc-list (for architecture i386): Mach-O executable i386 /usr/local/Cellar/fontconfig/2.10.91/bin/fc-list (for architecture x86_64): Mach-O 64-bit executable x86_64 /usr/local/Cellar/fontconfig/2.10.91/bin/fc-match:Mach-O universal binary with 2 architectures /usr/local/Cellar/fontconfig/2.10.91/bin/fc-match (for architecture i386): Mach-O executable i386 /usr/local/Cellar/fontconfig/2.10.91/bin/fc-match (for architecture x86_64): Mach-O 64-bit executable x86_64 /usr/local/Cellar/fontconfig/2.10.91/bin/fc-pattern: Mach-O universal binary with 2 architectures /usr/local/Cellar/fontconfig/2.10.91/bin/fc-pattern (for architecture i386): Mach-O executable i386 /usr/local/Cellar/fontconfig/2.10.91/bin/fc-pattern (for architecture x86_64): Mach-O 64-bit executable x86_64 /usr/local/Cellar/fontconfig/2.10.91/bin/fc-query:Mach-O universal binary with 2 architectures /usr/local/Cellar/fontconfig/2.10.91/bin/fc-query (for architecture i386): Mach-O executable i386 /usr/local/Cellar/fontconfig/2.10.91/bin/fc-query (for architecture x86_64): Mach-O 64-bit executable x86_64 /usr/local/Cellar/fontconfig/2.10.91/bin/fc-scan: Mach-O universal binary with 2 architectures /usr/local/Cellar/fontconfig/2.10.91/bin/fc-scan (for architecture i386): Mach-O executable i386 /usr/local/Cellar/fontconfig/2.10.91/bin/fc-scan (for architecture x86_64): Mach-O 64-bit executable x86_64 /usr/local/Cellar/fontconfig/2.10.91/bin/fc-validate: Mach-O universal binary with 2 architectures /usr/local/Cellar/fontconfig/2.10.91/bin/fc-validate (for architecture i386): Mach-O
Re: [GRASS-dev] [GRASS GIS] #1239: wxGUI command layer broken and unusable
#1239: wxGUI command layer broken and unusable ---+ Reporter: garu | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 6.4.3 Component: wxGUI | Version: 6.4.3 RCs Keywords: layer manager |Platform: MSWindows XP Cpu: Unspecified| ---+ Comment(by annakrat): I have made a few changes in grass 7, could you test if it helps at least with some of the issues? Anna -- Ticket URL: http://trac.osgeo.org/grass/ticket/1239#comment:12 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] citation GRASS extensions
Hi, I was just looking at citation information. It is clear how to cite GRASS itself, but what if you want to cite an extension? Or as an extension author you want to suggest a citation? R has a pretty could system in place where citation information is included in every package and available through the citation() function. I think it is automatically generated or the developer can include his/her own citation information to be displayed. I guess one option is to provide a suggested citation in the manual page? Any ideas? Cheers, Paulo ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] does GRASS 7 for Mac compile yet?
[all deleted] Apologies for hijacking the thread! I can't seem to be able to configure as I did on Sunday!? Nothing changed since Sunday, yet, I get: --%--- .. checking for nad2bin... no configure: error: *** Unable to locate nad2bin (needs to be in PATH). ---%-- Any hints? nad2bin relies on /Library/Frameworks/PROJ.framework/Versions/4/Programs/nad2bin. Can I add this somehow with a --with-proj or alike switch? Thank you, Nikos ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Simple bash auto-completion for GRASS
Hi, he is the simple incomplete version of auto-completion for GRASS bash command line. Implemented only of two commands -- d.rast and d.vect -- and works only in the case with single parameter (d.vect mapname). It completes the name of raster/vector map (for all mapsets as returned by g.mlist). How to test it: in the GRASS command line run source bash_completion.sh. Type d.rast and press TAB. I don't know what should be auto-completed; how to deal with the number of GRASS commands; if/how to handle parameters; what are side-effects; how it works on various systems/shells; and how to integrated into GRASS. The question which I tried to answer is: Is that possible? Vaclav bash_completion.sh Description: Bourne shell script ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] does GRASS 7 for Mac compile yet?
Nikos Alexandris wrote: .. --%--- .. checking for nad2bin... no configure: error: *** Unable to locate nad2bin (needs to be in PATH). ---%-- Please, disregard the previous post. I was wrong in adding the complete /Library/Frameworks/PROJ.framework/Versions/4/Programs/nad2bin instead of simply /Library/Frameworks/PROJ.framework/Versions/4/Programs in ~/.bash_profile Best, Nikos ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Simple bash auto-completion for GRASS
Vaclav Petras wrote: Hi, he is the simple incomplete version of auto-completion for GRASS bash command line. Thanks for the attempt Vaclav. This would be a POWER-feature :-) Implemented only of two commands -- d.rast and d.vect -- and works only in the case with single parameter (d.vect mapname). It completes the name of raster/vector map (for all mapsets as returned by g.mlist). How to test it: in the GRASS command line run source bash_completion.sh. Type d.rast and press TAB. I don't know what should be auto-completed; I think it would be a great time-saver if it would be possible to auto-complete existing map (file)names for parameters like input=, map= and why not (sub-)group names (think of i.group group=...) and color rules (think of r.colors map=... color=...). how to deal with the number of GRASS commands; if/how to handle parameters; what are side-effects; how it works on various systems/shells; and how to integrated into GRASS. The question which I tried to answer is: Is that possible? Thank you, Nikos ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] grass wiki main page colorbrewer tool
Helena wrote: this topic should cover the programming part, not the design of symbology. ok, We need to have d.rast.leg and d.vect.leg - even if it is just single color for a feature like water So like the ps.map vector legend, but as a d.* module, right? Glynn already converted d.rast.leg to python, how would you like to see that be improved? (besides renaming it d.rast.legend) re. improvements for d.rast.leg, here is a mock up I just made of some MODIS SST data with some ideas in it: http://bambi.otago.ac.nz/hamish/grass/screenshots/sst_4uNight_A2012047.png Only part which isn't real is I squashed the LL Plate Carree's width by percentage (approx cos(lat) * 100) in GIMP, instead of doing a real reprojection. The rest is scriptable: * decorations are on the left (flag to move it to the right) * uses d.font for a TrueType font^ (I set it to Vera) * units are taken from 'r.info -u' if they are set * d.legend's range= is take from r.univar -e perc=2,98 * d.text with the map name is rotated 90 deg to up the map space * a calculation is made to automatically pick a nice d.grid interval * I still like the black backgrounds from old versions of GRASS for satellite imagery :) ^note we can make good use of the GRASS_FONT and GRASS_FONTSIZE enviro variables for all d.* modules, avoiding extra options thus simplifying the code. Of course the GUI versions would need friendly wrappers with buttons and drop down lists, but that's relatively easy. (like we have r.colors and v.colors - I was thrilled to discover v.colors, thanks a lot for that, you are welcome, although as you noticed it's a complete hack taking advantage of r.colors as it does. Better to would be to add colr files to the vector/ format for GRASS 7. I think that using GRASSRGB column should remain as an option, but the 'd.vect zcolor=' style could use an optional colr file, so you had more options for coloring e.g. LiDAR w/ no DB table than just the presets. Perhaps similar to the user-file symbol support in the user's mapset (yes, it's possible) you could have a mapset or location based directory with personal color maps it could check to use? (/or a colors/ dir within the grass addons dir(s) too?) e.g. the streets map with speed limits in the nc data set looks great and I see the trick with the legend, but that is not a solution for vector data in general) screenshot? (perhaps for the website; we need more good vector ones there) We need better handling of scale bar and everything needs to be more robust. You mean in the wxGUI map display window, not the d.* C modules, right? Or that those things should be drawn as vector not with 1 pixel wide lines which do not work well with a large display size as may be used in a poster? I looked at the cartographic composer and recommended it to students but we are still behind other packages in terms of producing nice maps in a convenient way - everything (or most of it ) is there, it just needs more work. fwiw, knowing ps.map well, I think it is absolutely marvelous. There is still some work to do merging some nice features from ps.output, like the better borders. That is the part of GRASS I get most complaints about, although some students produce beautiful maps with GRASS. I'd be delighted to see them file wishes in the trac'er. I hope the composer takes care of a lot of the eeek it's controlled by text issues, and once they have their text control file they feel comfortable changing e.g. the caption spelling in it, or map name if they need to produce a series, in a text editor and see the joy of consistent templates. Hamish: Even though it is very popular in other widely used software, I've always tried to steer away from applying discrete classes to continuous raster data. IMO it deserves it's own chapter in How to lie with statistics*, ... I totally agree with you on this but there is some research that says otherwise If it's the journal article I'm thinking of, I know about it, I've read it, and I don't agree with its conclusions. and there are some situations when the discrete maps simply work better. I can see it when we have the GRASS and ArcGIS maps side-by-side, our continuous color ramps are certainly better than the grey ramp for continuous data in ArcGIS, but the discrete color ramps produced by some ArcGIS modules are often more readable although they can hide some detail - I try to deliver that message all the time and we use relief shading a lot to avoid hiding features. It very much depends on the data - it would be a long discussion. It could be, but I'd probably need to study up on my ER Tufte a bit more to be able to do it well. :) The precipitation example in GRASSbook - Fig.6.17 is a good example where the continuous color ramp did not work, even when it was in color you could not see the pattern. (I only had Vol 1, but luckily our library has access to the eBook :) If you really want to do it though there's no
Re: [GRASS-dev] Simple bash auto-completion for GRASS
On 05/02/13 12:02, Vaclav Petras wrote: Hi, he is the simple incomplete version of auto-completion for GRASS bash command line. Implemented only of two commands -- d.rast and d.vect -- and works only in the case with single parameter (d.vect mapname). It completes the name of raster/vector map (for all mapsets as returned by g.mlist). How to test it: in the GRASS command line run source bash_completion.sh. Type d.rast and press TAB. I don't know what should be auto-completed; how to deal with the number of GRASS commands; if/how to handle parameters; what are side-effects; how it works on various systems/shells; and how to integrated into GRASS. The question which I tried to answer is: Is that possible? You might want to look at this old implementation: http://www.sorokine.info/grass-complete/ Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] does GRASS 7 for Mac compile yet?
On the wxpython-problematic for OS-X: I can compile grass_trunk which ends up with various wxpython related errors. So, the gui wont launch. Could it be that we only need to properly install - python 2.7 http://python.org/ftp/python/2.7.3/python-2.7.3-macosx10.6.dmg - wxpython 2.9 (the cocoa build) http://downloads.sourceforge.net/wxpython/wxPython2.9-osx-2.9.4.0-cocoa-py2.7.dmg and then set up properly GRASS to pick those up? Since I have previous experience under OS-X (only linux here), I can't easily switch python versions, etc. Thanx, Nikos ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] does GRASS 7 for Mac compile yet?
On the wxpython-problematic for OS-X: I can compile grass_trunk which ends up with various wxpython related errors. So, the gui wont launch. Could it be that we only need to properly install - python 2.7 http://python.org/ftp/python/2.7.3/python-2.7.3-macosx10.6.dmg - wxpython 2.9 (the cocoa build) http://downloads.sourceforge.net/wxpython/wxPython2.9-osx-2.9.4.0-cocoa-py2.7.dmg and then set up properly GRASS to pick those up? Since I have no previous experience under OS-X (only linux here), I can't easily switch python versions, etc. Thanx, Nikos ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] does GRASS 7 for Mac compile yet?
Nikos Alexandris wrote: On the wxpython-problematic for OS-X: .. - python 2.7 http://python.org/ftp/python/2.7.3/python-2.7.3-macosx10.6.dmg - wxpython 2.9 (the cocoa build) http://downloads.sourceforge.net/wxpython/wxPython2.9-osx-2.9.4.0-cocoa-py2.7.dmg and - numpy http://garr.dl.sourceforge.net/project/numpy/NumPy/1.6.1/numpy-1.6.1-py2.7-python.org-macosx10.6.dmg and then set up properly GRASS to pick those up? O-kay, it seems it works :-) Configured by setting --with-wxwidgets=/usr/local/lib/wxPython-2.9.4.0/bin/wx-config, compiled, and correcting another locale-related problem (setting LC_CTYPE=en_US.UTF-8) . We can now proceed in debugging errors... :-) Nikos ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Simple bash auto-completion for GRASS
On 5 February 2013 12:42, Hamish hamis...@yahoo.com wrote: Vaclav wrote: he is the simple incomplete version of auto-completion for GRASS bash command line. Hi, did you know about the previous work on this for grass 5? It would need updating for sure, but maybe a lot of the work is already done for you. It is still online: http://www.sorokine.info/grass-complete/ Hi, I didn't. So it was even working some day. It might be useful if somebody (not sure if me) will actually write the general completion. However, it is for g5, bash 2 (I have 4) and it is written in perl. For g7 it should be probably in Python. While looking to the code, I'm afraid of various shells differences. Finally, there is --interface-description (with the parameter type) which would help to build the completion files (not there is some parsing and guessing). This part might be even easier than it was for 5. Nevertheless, it seems that there was and is an interest in this. Vaclav Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #1554: wxGUI Cartographic Composer: preview broken on Windows
#1554: wxGUI Cartographic Composer: preview broken on Windows +--- Reporter: martinl | Owner: grass-dev@… Type: defect | Status: new Priority: critical| Milestone: 6.4.3 Component: wxGUI | Version: unspecified Keywords: cartographic composer, psmap, wingrass |Platform: MSWindows XP Cpu: Unspecified | +--- Comment(by annakrat): After some changes, preview seems to work. Tested with winGRASS 7. Please could anyone test the tomorrow snapshot? Anna -- Ticket URL: http://trac.osgeo.org/grass/ticket/1554#comment:11 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] does GRASS 7 for Mac compile yet?
On Feb 5, 2013, at 7:13 AM, Nikos Alexandris wrote: Nikos Alexandris wrote: On the wxpython-problematic for OS-X: .. - python 2.7 http://python.org/ftp/python/2.7.3/python-2.7.3-macosx10.6.dmg Python 2.7 is in the Mac system starting with 10.7 (Lion). And on 10.6, the system python 2.6 works just fine. - wxpython 2.9 (the cocoa build) http://downloads.sourceforge.net/wxpython/wxPython2.9-osx-2.9.4.0-cocoa-py2.7.dmg More correctly - install wxpython 2.9 to match your python. For OS X 10.6 users, you would install wxpython 2.9 carbon py2.6. and - numpy http://garr.dl.sourceforge.net/project/numpy/NumPy/1.6.1/numpy-1.6.1-py2.7-python.org-macosx10.6.dmg Well, if you are using my GDAL framework for GRASS, it has a numpy installer in the download (and it's also available as a separate download). This is made for the system python (the official binaries are made only for the python.org python). and then set up properly GRASS to pick those up? O-kay, it seems it works :-) Configured by setting --with-wxwidgets=/usr/local/lib/wxPython-2.9.4.0/bin/wx-config, compiled, and correcting another locale-related problem (setting LC_CTYPE=en_US.UTF-8) . We can now proceed in debugging errors... :-) Nikos ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev - William Kyngesburye kyngchaos*at*kyngchaos*dot*com http://www.kyngchaos.com/ All generalizations are dangerous, even this one. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #1239: wxGUI command layer broken and unusable
I'll see if I can update this afternoon after class and let you know. Thanks. Michael __ C. Michael Barton Director, Center for Social Dynamics Complexity Professor of Anthropology, School of Human Evolution Social Change Arizona State University Tempe, AZ 85287-2402 USA voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671(SHESC), 480-727-0709 (CSDC) www:http://csdc.asu.edu, http://shesc.asu.edu http://www.public.asu.edu/~cmbarton On Feb 5, 2013, at 2:36 AM, GRASS GIS t...@osgeo.org wrote: #1239: wxGUI command layer broken and unusable ---+ Reporter: garu | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 6.4.3 Component: wxGUI | Version: 6.4.3 RCs Keywords: layer manager |Platform: MSWindows XP Cpu: Unspecified| ---+ Comment(by annakrat): I have made a few changes in grass 7, could you test if it helps at least with some of the issues? Anna -- Ticket URL: http://trac.osgeo.org/grass/ticket/1239#comment:12 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] does GRASS 7 for Mac compile yet?
I recommend NOT installing a 3rd party Python. OS X 10.7 and 10.8 already come with Python 2.6 and 2.7 installed. My installation instructions, worked out with William Kyngesburye are designed so that GRASS will work with Python 2.6 and OS X 10.6 (which many people still use). I get a series of errors during compiling that say 'can't find wx'. But these are bogus. All the affected modules (e.g., mapswipe) work fine. If you cannot launch the GUI there is some kind of different problem. 1) What OS are you using? If you have OS X 10.6, you need to follow different instructions from what I said. Also, you need the 10.6 SDK's in order to compile a version that works on 10.6 if you are running 10.8. 2) Often a failure to launch is actually traceable to an out of date GDAL version, though this should not be a problem if you are compiling yourself. 3) Another reason for a launch failure is a mismatch between the location of wxPython in the configure script and where it really is located on your computer. You might try to download my GRASS 7 binary, compiled Sunday night, and see if it runs with all the proper frameworks installed (these are also on the site). You can find it at http://www.public.asu.edu/~cmbarton/files/grass_mac/OSX10.6-snowleopard/ Michael __ C. Michael Barton Director, Center for Social Dynamics Complexity Professor of Anthropology, School of Human Evolution Social Change Arizona State University Tempe, AZ 85287-2402 USA voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671(SHESC), 480-727-0709 (CSDC) www:http://csdc.asu.edu, http://shesc.asu.edu http://www.public.asu.edu/~cmbarton On Feb 5, 2013, at 5:24 AM, Nikos Alexandris n...@nikosalexandris.net wrote: On the wxpython-problematic for OS-X: I can compile grass_trunk which ends up with various wxpython related errors. So, the gui wont launch. Could it be that we only need to properly install - python 2.7 http://python.org/ftp/python/2.7.3/python-2.7.3-macosx10.6.dmg - wxpython 2.9 (the cocoa build) http://downloads.sourceforge.net/wxpython/wxPython2.9-osx-2.9.4.0-cocoa-py2.7.dmg and then set up properly GRASS to pick those up? Since I have no previous experience under OS-X (only linux here), I can't easily switch python versions, etc. Thanx, Nikos ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS6.4.3RC2 issues
On Tue, Jan 22, 2013 at 2:47 AM, Helena Mitasova hmit...@ncsu.edu wrote: - in 2D display legend is now much better than ever before, but when the d.legend command is run from command line it appears that the legend parameters are not carried over to the GUI and need to be entered in GUI again - is this the desired behavior? For example in the sequence # Convert from vector to raster in this assignment http://courses.ncsu.edu/mea582/common/GIS_anal_grass/GIS_Anal_grdataS2.html this command does not work properly from the command line d.legend streets_speed_30m at=5,30,2,5 use=25,35,45,55,65 Also, if there is a legend already present, Add legend opens the legend GUI behind the map display window (where it is of course hard to find) I think this issue has already been discussed before BTW, the legend now runs on Mac in 3d wxnviz well. Please try to test, I made larger changes and I hope I didn't create any new problem. - g.remove run from command console thinks I am in PERMANENT rather than the current mapset I was not able to reproduce it, anyone else? Anna g.remove rast=elev_lidrural1mr_1m Removing raster elev_lidrural1mr_1m WARNING: Raster map elev_lidrural1mr_1m not found WARNING: elev_lidrural1mr_1m nothing removed from linux shell it works GRASS 6.4.3RC2 (nc_spm_08):~ g.remove rast=elev_lidruralmr_1m Removing raster elev_lidruralmr_1m ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS GIS] #1239: wxGUI command layer broken and unusable
#1239: wxGUI command layer broken and unusable ---+ Reporter: garu | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 6.4.3 Component: wxGUI | Version: 6.4.3 RCs Keywords: layer manager |Platform: MSWindows XP Cpu: Unspecified| ---+ Comment(by cmbarton): Just recompiled and tested. It is now useable. You can see what you are typing. I tried it with d.rast aspect in the nc_spm_08 demo set. Thanks Michael -- Ticket URL: http://trac.osgeo.org/grass/ticket/1239#comment:13 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] r.surf.idw in latlon region?
I see in GRASS 7 that r.surf.idw2 does not work in a latlon region. It recommends using r.surf.idw. But r.surf.idw doesn't see to do anything either. It runs with no errors but does not produce an interpolated map. Michael C. Michael Barton Director, Center for Social Dynamics Complexity Professor of Anthropology, School of Human Evolution Social Change Arizona State University voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
