Re: [GRASS-user] Report from ongoing GRASS GIS Community Sprint in Prague
Paolo, you have not hurt anyone, you were annoying and arrogant, a behaviour that is virtually absent from this mailing list, and I for my part do not want to tolerate it. Anyway, continuing the thread this way is fruitless. This thread is about the QGIS SEXTANTE plugin. From a QGIS perspective, it is just that, a plugin for QGIS with backends to a number of analytical tools. From a GRASS perspective, this is a python version of SEXTANTE with one binding (QGIS) and including a backend to GRASS. I would like to see evolve python SEXTANTE into a more generic python SEXTANTE where it is easy to add more bindings, as in java SEXTANTE. I would also like to help improve the GRASS backend. In order to achieve this, I try to get into contact with people who are actually doing something on python SEXTANTE, i.e. the developers. Ciao, Markus On Tue, May 29, 2012 at 11:31 AM, Paolo Cavallini cavall...@faunalia.it wrote: Il 28/05/2012 21:17, Markus Metz ha scritto: not to java SEXTANTE. While on it (the blaming), I think it is time for Paolo to apologize for his rude [1] comments [2][3][4][5][6][7] earlier in the thread. I'm more than happy to apologize if I have hurt the sensibility of anybody. However, I think there is some misunderstanding, let's try to clarify: -SEXTANTE has two versions now (which are like 2 different projects) -The QGIS version is still unstable, but is a much better software (cleaner design, different things, etc) -It would be great to coordinate both versions, but it has to be done manually. currently, Victor Olaya is putting time on the QGIS version and not in the gvSIG one, so they might get uncoordinated, which Victor do not see as a terrible problem, anyway. -SEXTANTE for gvSIG has more algorithms and is more prepared for that, while SEXTANTE for QGIS has more backends, and is better suited for it. [2] http://osgeo-org.1560.n6.nabble.com/Report-from-ongoing-GRASS-GIS-Community-Sprint-in-Prague-tp4977136p4977385.html the link is wrong, the original source code is at http://code.google.com/p/sextante/source/browse/trunk/soft/bindings/qgis-plugin/src From the link I provided, you can easily find the source code at: http://plugins.qgis.org/plugins/sextante/ so it should be, according to Victor choice: http://sextante.googlecode.com/svn/trunk/ [3] http://osgeo-org.1560.n6.nabble.com/Report-from-ongoing-GRASS-GIS-Community-Sprint-in-Prague-tp4977136p4977411.html Paolo is appropriating python SEXTANTE as the QGIS Python plugin called sextante. See [2] I really do not understand this (see above). What is Python SEXTANTE? Anyway, sending a link and appropriating code seems different acts. [4] http://osgeo-org.1560.n6.nabble.com/Report-from-ongoing-GRASS-GIS-Community-Sprint-in-Prague-tp4977136p4977430.html Paolo is again appropriating python SEXTANTE (Please do nont send bug reports concerning it to other bugtrackers.) as the QGIS Python plugin called sextante. See [2] Bugs concerning the SEXTANTE QGIS Python plugin should be sent to: http://hub.qgis.org/projects/sextante/issues I do not see how this is appropriating anything. [5] http://osgeo-org.1560.n6.nabble.com/Report-from-ongoing-GRASS-GIS-Community-Sprint-in-Prague-tp4977136p4977473.html Paolo: I can correct you :) 1. Paolo was not addressed. 2. The issue has been resolved, no need for any further correction 3. I, not Paolo, gave an explanation and examples for the issue discussed (there is a complete re-write of SEXTANTE in Python). As I explained in a previous mail, Victor Olaya is the person who can best correct anybody on this. I took the liberty of talking on his behalf just because we are in close contact, and he has not subscribed to this list. [6] http://osgeo-org.1560.n6.nabble.com/Report-from-ongoing-GRASS-GIS-Community-Sprint-in-Prague-tp4977136p4977489.html Paolo: ... and join us. Paolo is not a developer of SEXTANTE, but very active for QGIS. Therefore us does obviously not mean SEXTANTE but QGIS. Paolo is again appropriating python SEXTANTE (Please do nont send bug reports concerning it to other bugtrackers.) as the QGIS Python plugin called sextante. See [2] Yes, us means QGIS. We (QGIS) already decided to integrate SEXTANTE into QGIS master as soon as code freeze is over (we are now releasing QGIS 1.8), so the distinction is blurred. [7] http://osgeo-org.1560.n6.nabble.com/Report-from-ongoing-GRASS-GIS-Community-Sprint-in-Prague-tp4977136p4977500.html At this stage of the python version of SEXTANTE, the main objective should be to get a stable version of python SEXTANTE. That is, a generic python SEXTANTE, not just something that works for QGIS and nothing else (with the SEXTANTE/GRASS interface not even working properly, see main comment). Paolo is again appropriating python SEXTANTE (Please do nont send bug reports concerning it to other bugtrackers.) as the QGIS Python plugin called sextante. See [2] Where do you find a
Re: [GRASS-user] Problems compiling Grass 6.4 and Grass addons under MacOS
On Wed, May 30, 2012 at 5:52 AM, David Montoya jdmon...@gmail.com wrote: I installed Grass using the files from kyngchaos and I need to compile some addons. Please tell us which. I tried to install them by two ways, using g.extensions but it doesn't work, and through modbuild following the instruction but I get the following error: My Os is MacOS Lion 10.7 MacBook-Pro-de-Jose:r.stream.extract jdmonto0$ make GRASS_HOME='~/modbuild' GRASS_APP='/Applications/GRASS-6.4.app' ../../include/Make/Module.make:25: warning: overriding commands for target `install' ../../include/Make/Rules.make:90: warning: ignoring old commands for target `install' gcc -I~/modbuild/dist.i386-apple-darwin11.3.0/include -I/Applications/GRASS-6.4.app/Contents/MacOS/include -Os -fexceptions -arch i386 -arch x86_64 -isysroot /Developer/SDKs/MacOSX10.6.sdk -I/Library/Frameworks/GDAL.framework/Versions/1.9/Headers -I/Library/Frameworks/GEOS.framework/Versions/3/unix/include -DPACKAGE=\grassmods\ -I~/modbuild/dist.i386-apple-darwin11.3.0/include -I/Applications/GRASS-6.4.app/Contents/MacOS/include -o OBJ.i386-apple-darwin11.3.0/close.o -c close.c In file included from close.c:1: /Applications/GRASS-6.4.app/Contents/MacOS/include/grass/gis.h:24:19: error: stdio.h: No such file or directory This is a fundamental system file. On my Linux box, it is in a package called glibc-headers. No idea how that's called on MacOSX. The lack of this file causes all subsequent errors. ... I tried also to compile Grass by my own, but I get some errors when I run the command make. The configuration that I use is as follow: ./configure \ ... At this point, everything seems to be ok, but when I run make, I get this error: ... Errors in: /Users/jdmonto0/Downloads/grass/grass64_release/lib/iostream /Users/jdmonto0/Downloads/grass/grass64_release/gui/wxpython /Users/jdmonto0/Downloads/grass/grass64_release/raster/r.terraflow /Users/jdmonto0/Downloads/grass/grass64_release/visualization/nviz -- In case of errors please change into the directory with error and run 'make'. -- please do this and report the errors. Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Problems compiling Grass 6.4 and Grass addons under MacOS
David wrote: /Applications/GRASS-6.4.app/Contents/MacOS/include/grass/gis.h:24:19: error: stdio.h: No such file or directory MarkusN: This is a fundamental system file. On my Linux box, it is in a package called glibc-headers. No idea how that's called on MacOSX. The lack of this file causes all subsequent errors. perhaps install Xcode development tools from the Mac install DVD ? (just a guess) Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Problems compiling Grass 6.4 and Grass addons under MacOS
This is a problem I've seen before (those headers are in the Xcode installation). I think Apple's -isysroot SDK flag is a bit broken in Xcode 4.1 (or 4.2? before the app store release) so the system is not looking in the right place. The new Xcode 4.3 seems to be fixed, though I haven't paid close attention to it. There are 2 parts now to Xcode - the app and the CLI tools. Both can be downloaded free (the app was available only from the app store for a while) You really only need the CLI tools, but it doesn't have the SDKs. The app has the SDKs, but they're in the wrong place for GRASS to see them. You need to dig into the Xcode app package Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs and copy the MacOSX10.6.sdk to /Developer/SDKs on your Mac. On May 30, 2012, at 6:01 AM, Hamish wrote: David wrote: /Applications/GRASS-6.4.app/Contents/MacOS/include/grass/gis.h:24:19: error: stdio.h: No such file or directory MarkusN: This is a fundamental system file. On my Linux box, it is in a package called glibc-headers. No idea how that's called on MacOSX. The lack of this file causes all subsequent errors. perhaps install Xcode development tools from the Mac install DVD ? (just a guess) Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user - William Kyngesburye kyngchaos*at*kyngchaos*dot*com http://www.kyngchaos.com/ I ache, therefore I am. Or in my case - I am, therefore I ache. - Marvin ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] NBR tool for Landsat 7 images
Greetings Grass users, Just writing to share with the community a little python script for GRASS 6.4 we developed at the Instituto de Información Territorial del Estado de Jalisco, in México. The purpose of the script is to obtain the NBR (Normalized Burn Ratio) out of a Landsat 7 image without the hassle of passing the image to radiance and reflectance values and writing the formulas manually. Hope you find good use for it and would greatly appreciate your feedback. https://sourceforge.net/projects/dn2nbr.ottosworkshop.p/ Adiós! Daniel. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Fwd: Re: [Qgis-developer] Sextante: v.buffer angle does not work
FYI. Thanks. Messaggio originale Oggetto: Re: [Qgis-developer] Sextante: v.buffer angle does not work Data: Wed, 30 May 2012 18:33:19 +0200 Mittente: Victor Olaya vola...@gmail.com A: cavall...@faunalia.it CC: qgis-developer qgis-develo...@lists.osgeo.org , I had splitted it, and in fact this algorithm just calls the angle option, but it still complains This is your command line v.buffer input=tmp1338388935286 angle=90 tolerance=0.01 -s -c output=output --overwrite and it says ERRORE: Select a buffer distance/minordistance/angle or column, but not both. But it's only passing an angle, not any of the other options!!!. Or you are not supposed to use tolerance with the angle option? Any GRASS expert can help? ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Fwd: Re: [Qgis-developer] Sextante: v.buffer angle does not work
On 30/05/12 18:44, Paolo Cavallini wrote: FYI. Thanks. Messaggio originale Oggetto: Re: [Qgis-developer] Sextante: v.buffer angle does not work Data: Wed, 30 May 2012 18:33:19 +0200 Mittente: Victor Olayavola...@gmail.com A: cavall...@faunalia.it CC: qgis-developerqgis-develo...@lists.osgeo.org , I had splitted it, and in fact this algorithm just calls the angle option, but it still complains This is your command line v.buffer input=tmp1338388935286 angle=90 tolerance=0.01 -s -c output=output --overwrite and it says ERRORE: Select a buffer distance/minordistance/angle or column, but not both. But it's only passing an angle, not any of the other options!!!. Or you are not supposed to use tolerance with the angle option? Actually, the relevant part of the code is this: if (((dista_opt-answer || buffer_opt-answer) bufcol_opt-answer) || (!(dista_opt-answer || buffer_opt-answer || bufcol_opt-answer))) G_fatal_error(_(Select a buffer distance/minordistance/angle or column, but not both.)); which means that you need either a buffer distance or a buffer column, but not neither or both of these. I guess the distance/minordistance/angle part was meant to signal that distance could be combined with minordistance and or angle, but I agree that the message is not very clear in that way. I think it should rather read something like this: You must indicate either a buffer distance or column, but not both. An angle on its own could not define a buffer, so it would be useless. Moritz ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Help - Tabulate Areas (ESRI function) for GRASS
Hi, i have a raster file about land usage (crops / urban areas ecc..) I have defined some zones around some given points of a vector layer and I'd like to calculate the % of those areas occupied by each value of the raster file in order to make an estimate on the average usages of the selected areas. I know that in arcgis there is a function to do so called Tabulate Areas, but I can't find such feature in GRASS. If anyone can help me I'd be so grateful. Regards, -- *Alejandro Coca Castro* ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Help - Tabulate Areas (ESRI function) for GRASS
On 05/30/2012 11:07 PM, Alejandro Coca Castro wrote: Hi, i have a raster file about land usage (crops / urban areas ecc..) I have defined some zones around some given points of a vector layer and I'd like to calculate the % of those areas occupied by each value of the raster file in order to make an estimate on the average usages of the selected areas. I know that in arcgis there is a function to do so called Tabulate Areas, but I can't find such feature in GRASS. I think you can use r.stats for this. First rasterize your (vector) areas with v.to.rast. Use a numeric column for the use=attr option. Then use r.stats with both the landuse raster and the zones raster as input. So if you have a landuse raster, and a zones vector with i.e. a zone_id column, then: v.to.rast in=zones out=zones use=attr colu=zone_id r.stats -p in=zones,landuse fs=, out=landuse_zones_percent.csv If anyone can help me I'd be so grateful. Regards, -- */Alejandro Coca Castro/**//**//**//*// This mail was received via Mail-SeCure System. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user This mail was received via Mail-SeCure System. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
