Re: [GRASS-user] New AddOns for Analyzing landscape connectivity based on graph-theory - the r.connectivity.*-toolchain
Hi again Now I added som bugfixes for the issues Helmut came across. A and B are changed in the manual. For issue C (unary operator expected) it was too simple to blame Microsoft... (Sorry for that, Bill.) And it was no problem with v.extract either. Actually, it was my fault, because I tried to catch the number of centroids from the secondary output of v.extract using grep. But due to translation, centroids are not allways called centroids, so grep did not find anything on my german system... Now I use v.info for that. This means an extra command in the loop but it should work now (independend from language settings). The R-path issue is tackled (for the time being) by adjusting the error message until a more general solution is found... In other words, users have to add the path to R into their environment settings (if that has not been done before) in order to make the AddOn usable. R can be installed where so ever on the system, so looking for R is not too easy (or fast)... Furthermore a requirement section is added to the manual of r.connectivity.network. Cheers Stefan By the way: a) Does anyone know if xargs also works with wingrass? Alternatives? b) Hints for a convenient parallel processing solution in R which also works on Windows (alternative or in addition to multicore and doMC on Linux) would be most welcome... -- View this message in context: http://osgeo-org.1560.n6.nabble.com/New-AddOns-for-Analyzing-landscape-connectivity-based-on-graph-theory-the-r-connectivity-toolchain-tp5000351p5003434.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] New AddOns for Analyzing landscape connectivity based on graph-theory - the r.connectivity.*-toolchain
hi Stefan, Now I added an example to the manuals based on the North Carolina data set. thanks, tested now with osgeo4w-wingrass6.4.3svn in win7-64bit-box following your example. some issues: (A) manual ###Patch input vector map ##Extract habitat patches #Condition 1: Category 11 = Bottomland Hardwoods/Hardwood Swamps #Condition 2: no border-cells are suitable r.mapcalc patches=if(\ landuse96_28m[0,1]==11\ [...] in windows (from the mapcalc-gui): r.mapcalc patches = if(landuse96_28m[0,1]==11landuse96_28m[0,-1]==11landuse96_28m[1,1]==11landuse96_28m[1,0]==11landuse96_28m[1,-1]==11landuse96_28m[-1,1]==11landuse96_28m[-1,0]==11landuse96_28m[-1,-1]==11landuse96_28m==11,1,null()) (B) manual: v.extract input=patches@user1 output=patches_1ha type=point,line,boundary,centroid,area,face layer=1 where=area_ha1 new=-1 --overwrite maybe simplified and correctedt to? v.extract input=patches output=patches_1ha type=area layer=1 where=area_ha 1 (C) r.connectivity.distance --verbose patches=patches_1ha@g65 costs=costs@g65 pop_proxy=area_ha prefix=hws_connectivity folder=C:\tmp\connect cutoff=4500 border_dist=18 Preparing boundaries... Calculating connectivity-distances for patch number 2 C:/OSGeo4W/apps/grass/grass-6.4.3svn/scripts/r.connectivity. distance: line 379: [: -gt: unary operator expected C:/OSGeo4W/apps/grass/grass-6.4.3svn/scripts/r.connectivity. distance: line 386: [: -eq: unary operator expected Calculating connectivity-distances for patch number 13 [...] C:/OSGeo4W/apps/grass/grass-6.4.3svn/scripts/r.connectivity. distance: line 386: [: -eq: unary operator expected Calculating connectivity-distances for patch number 298 C:/OSGeo4W/apps/grass/grass-6.4.3svn/scripts/r.connectivity. distance: line 379: [: -gt: unary operator expected C:/OSGeo4W/apps/grass/grass-6.4.3svn/scripts/r.connectivity. distance: line 386: [: -eq: unary operator expected (Wed Sep 19 14:59:51 2012) Command finished (5 min 49 sec) there are a lot of these [: -eq: unary operator expected-messages. following files are created: closest.points edges.csv r_connectivity.log r_connectivity.log.tmp vertices_part_1.csv vertices_part_2.csv (D) some test r.connectivity.network -y -i folder=C:\tmp\connect connectivity_cutoff=1500.0 lnbh_cutoff=2.0 cl_thres=10 exponent=-3 kernel_plot=C:\tmp\connect\kernel.eps overview_plot=C:\tmp\connect\overview.eps cores=1 rm: cannot lstat `C:tmpconnect/r_connectivity.log.tmp': No such file or directory which: R: unknown command ERROR: R is required, please install R first r.connectivity.network -y -i folder='C:\tmp\connect' connectivity_cutoff=1500.0 lnbh_cutoff=2.0 cl_thres=10 exponent=-3 kernel_plot=C:\tmp\connect\kernel.eps overview_plot=C:\tmp\connect\overview.eps cores=1 rm: cannot lstat `C:tmpconnect/r_connectivity.log.tmp': No such file or directory which: R: unknown command ERROR: R is required, please install R first (Wed Sep 19 15:09:44 2012) Command finished (1 sec) r.connectivity.network -y -i folder=C:\tmp\connect connectivity_cutoff=1500.0 lnbh_cutoff=2.0 cl_thres=10 exponent=-3 kernel_plot=C:\tmp\connect\kernel.eps overview_plot=C:\tmp\connect\overview.eps cores=1 ERROR: r_connectivity.log file could not be found or is not readable. = r_connectivity.log seams not be readable = R is installed here on my system, but (as default by the R-installation) not in the %PATH% have a look how GRASS GIS-R-coupling is done by the standalone-wingrass-installer (but not in osgeo4w-wingrass): http://grass.osgeo.org/wiki/R_statistics#MS_Windows - best regards Helmut -- View this message in context: http://osgeo-org.1560.n6.nabble.com/New-AddOns-for-Analyzing-landscape-connectivity-based-on-graph-theory-the-r-connectivity-toolchain-tp5000351p5002964.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] New AddOns for Analyzing landscape connectivity based on graph-theory - the r.connectivity.*-toolchain
Dear Helumt Many thanks for testing! I have to admit, that I personally find it quite challenging to write a shell-script that also works on (the different) Windows platforms (I really should learn more Python...). On Windows everything feels less predictable... B) B can be easily fixed and I shall do so ASAP. Regarding A: Did I get you right that you had problems with the ' \ ' and ' '? Removing the backslash won`t be a problem, but I think the quotation-marks are required on Linux... For the latter it is probably best to put a note in the example... C) C occurs because v.extract (at line 377 of the script) fails. I assume you used the command-line in the wxPython-GUI? Could you be so kind and try to use the command in the text version of wingrass? I managed to run the example on Windows XP and in the text-GUI. It is a mystery to me why some wingrass commands behave differently when invoked from the command-line in the GUI and from the command-line (text-GUI). Maybe the wxPython - text - GUI differences are also causing A (and D)!? I think it would be a pitty if the GUI was not usable for these addons, but I feel that it is beyond my power to make it work... Are there any solutions I could use from other shell-scripts (calling v.extract)? D) The %PATH% settings are also a problem for ghostscript which is required for eps-output (the plots). Because this is neither added to the %PATH%-variable by default, I simply skipped/deactivated checking for ghostscript in windows (here also the commands / executables can be different... :-( ), so checking for ghostscript on Windows is challenging in itself. The problem with R is, that R is called by the script (while ghostscript is not). In other words: the script requires that the path to R is defined in the %PATH% settings and that R can be called directly... Maybe the best way to solve this is to add this information to the error-message (and a link to the GRASS-R-Wiki...). Strange that r_connectivity.log seams not to be readable. Because from your output you posted I can see, that the file was written at the correct place. So the path must have been interpreted correctly for writing. I have no idea why it is obviously not interpreted correctly for reading... I will check that... Best regards Stefan -- View this message in context: http://osgeo-org.1560.n6.nabble.com/New-AddOns-for-Analyzing-landscape-connectivity-based-on-graph-theory-the-r-connectivity-toolchain-tp5000351p5003029.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] New AddOns for Analyzing landscape connectivity based on graph-theory - the r.connectivity.*-toolchain
hi Stefan, Many thanks for testing! de nada Regarding A: Did I get you right that you had problems with the ' \ ' and ' '? r.mapcalc patches=if(\ landuse96_28m[0,1]==11\ [...] this isn't possible in the wxgui-commandline (not tried in the wingrass-windows-commandline; most users on windows probably are using only the GUI) Removing the backslash won`t be a problem, but I think the quotation-marks are required on Linux... unfortunately there seams to be inconsistency between unix/windows/GUI/commandline For the latter it is probably best to put a note in the example... sure, but better feel free to open a ticket for this in http://trac.osgeo.org/grass/, because otherwise it's getting lost in manual/ML and other modules/scripts etc. are able to benefit C) C occurs because v.extract (at line 377 of the script) fails. I assume you used the command-line in the wxPython-GUI? yes Could you be so kind and try to use the command in the text version of wingrass? sure, but unfortunately the same message: [...] Calculating connectivity-distances for patch number 279 C:/OSGeo4W/apps/grass/grass-6.4.3svn/scripts/r.connectivity.distance: line 379: [: -gt: unary operator expected C:/OSGeo4W/apps/grass/grass-6.4.3svn/scripts/r.connectivity.distance: line 386: [: -eq: unary operator expected 100% 100% Calculating connectivity-distances for patch number 294 C:/OSGeo4W/apps/grass/grass-6.4.3svn/scripts/r.connectivity.distance: line 379: [: -gt: unary operator expected C:/OSGeo4W/apps/grass/grass-6.4.3svn/scripts/r.connectivity.distance: line 386: [: -eq: unary operator expected 100% 100% Calculating connectivity-distances for patch number 298 C:/OSGeo4W/apps/grass/grass-6.4.3svn/scripts/r.connectivity.distance: line 379: [: -gt: unary operator expected C:/OSGeo4W/apps/grass/grass-6.4.3svn/scripts/r.connectivity.distance: line 386: [: -eq: unary operator expected 100% 100% GRASS 6.4.3svn (nc_spm_08) It is a mystery to me why some wingrass commands behave differently when invoked from the command-line in the GUI and from the command-line (text-GUI). ...windows itself is a mystery...not only the differences between XP, Vista, 7 and soon 8 I think it would be a pitty if the GUI was not usable for these addons, but I feel that it is beyond my power to make it work... Are there any solutions I could use from other shell-scripts (calling v.extract)? feel free to post this issue separately on the dev-ML or open a ticket in http://trac.osgeo.org/grass/ The %PATH% settings are also a problem for ghostscript which is required for eps-output (the plots). adding the ghostscript-%PATH%-issue to the manual? Because this is neither added to the %PATH%-variable by default, I simply skipped/deactivated checking for ghostscript in windows (here also the commands / executables can be different... :-( ), the windows mystery... so checking for ghostscript on Windows is challenging in itself. The problem with R is, that R is called by the script (while ghostscript is not). In other words: the script requires that the path to R is defined in the %PATH% settings and that R can be called directly... Maybe the best way to solve this is to add this information to the error-message (and a link to the GRASS-R-Wiki...). in the standalone winGRASS6.5svn/winGRASS7-installer there is the new approach of R-winGRASS-coupling by the Windows batchfiles for use with R mentioned in the wiki (http://grass.osgeo.org/wiki/R_statistics#GRASS_7_Usage), in the upcoming standalone winGRASS6.4.3(svn) there is the old statically approach (http://grass.osgeo.org/wiki/R_statistics#GRASS_6_Usage_III_.28taken_from_the_grass-stats-ML.29) because of nearly feature freeze. in short, in the standalone-winGRASSX.x.x, R should in the %PATH% in the osgeo4w-winGRASSX.x.x R isn't yet in the %PATH%. please feel free to open a ticket in http://trac.osgeo.org/grass/ to change this. Strange that r_connectivity.log seams not to be readable. Because from your output you posted I can see, that the file was written at the correct place. yes So the path must have been interpreted correctly for writing. I have no idea why it is obviously not interpreted correctly for reading... I will check that... no idea at the moment for this. - best regards Helmut -- View this message in context: http://osgeo-org.1560.n6.nabble.com/New-AddOns-for-Analyzing-landscape-connectivity-based-on-graph-theory-the-r-connectivity-toolchain-tp5000351p5003035.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] New AddOns for Analyzing landscape connectivity based on graph-theory - the r.connectivity.*-toolchain
Dear Helmut, Giovanni, Markus, Now I added an example to the manuals based on the North Carolina data set. Cheers Stefan -- View this message in context: http://osgeo-org.1560.n6.nabble.com/New-AddOns-for-Analyzing-landscape-connectivity-based-on-graph-theory-the-r-connectivity-toolchain-tp5000351p5002755.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] New AddOns for Analyzing landscape connectivity based on graph-theory - the r.connectivity.*-toolchain
Hi I did use the g.extension-manager through the wxGUI. And both, scripts and bat-files are in the addon-folder (within my Windows user profile). The GUI of the addons starts and I can fill in the parameters. But after ran the command (clicked the Run button) I get the message mentioned. I checked if the scripts work in general by copying the scripts manually into the script folder and the bat-files into the bin folder (after adjusting the path to %GISBASE%)... After I did that the scripts worked (though only through command line, through the wxGUI v.extract did not run successful). Probably, the addon-path (spaces in the path to my Windows user profile...) causes trouble? Stefan -- View this message in context: http://osgeo-org.1560.n6.nabble.com/New-AddOns-for-Analyzing-landscape-connectivity-based-on-graph-theory-the-r-connectivity-toolchain-tp5000351p5001880.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] New AddOns for Analyzing landscape connectivity based on graph-theory - the r.connectivity.*-toolchain
hi Probably, the addon-path (spaces in the path to my Windows user profile...) causes trouble? possible. maybe do you have an example with spearfish-/nc-sample-dataset to test? I've seen there are R and some R-packages as dependencies; maybe a short notice in the manual would be helpfull. - best regards Helmut -- View this message in context: http://osgeo-org.1560.n6.nabble.com/New-AddOns-for-Analyzing-landscape-connectivity-based-on-graph-theory-the-r-connectivity-toolchain-tp5000351p5001909.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] New AddOns for Analyzing landscape connectivity based on graph-theory - the r.connectivity.*-toolchain
Hi, it doesn't find the executing shell. it's my fault, did you use g.extension from the command line? please try the g.extension-manager from the GUI. then precompiled corresponding bat-files should be installed. HTH - best regards Helmut -- View this message in context: http://osgeo-org.1560.n6.nabble.com/New-AddOns-for-Analyzing-landscape-connectivity-based-on-graph-theory-the-r-connectivity-toolchain-tp5000351p5001677.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] New AddOns for Analyzing landscape connectivity based on graph-theory - the r.connectivity.*-toolchain
OK, then I will add an example based on the North Carolina dataset, as soon as I find the time for that. I do not think addidional data is necessary. I will figure that out and come back to you if necessary. In the meantime, I made some adjustments in the scripts, so they can be run with WinGRASS as well. But I did not manage to add the AddOns using g.extension under MS Windows. In this context I have two additional questions (in order to make the AddOns available on Windows as well): For WinGRASS version 6, additional .bat files are required in the bin-folder. Should these bat-files be added to the svn-repository? If the AddOns are not compiled, no html-help is build either. Should one add a complete module.html to the svn repository? Stefan -- View this message in context: http://osgeo-org.1560.n6.nabble.com/New-AddOns-for-Analyzing-landscape-connectivity-based-on-graph-theory-the-r-connectivity-toolchain-tp5000351p5001370.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] New AddOns for Analyzing landscape connectivity based on graph-theory - the r.connectivity.*-toolchain
On Wed, Sep 12, 2012 at 10:48 AM, SBL stefan.blumentr...@nina.no wrote: OK, then I will add an example based on the North Carolina dataset, as soon as I find the time for that. I do not think addidional data is necessary. I will figure that out and come back to you if necessary. In the meantime, I made some adjustments in the scripts, so they can be run with WinGRASS as well. Congratulations! But I did not manage to add the AddOns using g.extension under MS Windows. (They appear to be compiled: http://wingrass.fsv.cvut.cz/grass64/addons/grass-6.4.3svn/ ) In this context I have two additional questions (in order to make the AddOns available on Windows as well): For WinGRASS version 6, additional .bat files are required in the bin-folder. Should these bat-files be added to the svn-repository? I think yes, and the Makefile should take care to get them into the bin-folder. If the AddOns are not compiled, no html-help is build either. Should one add a complete module.html to the svn repository? No since this would generate double parameter entries. You can see them in HTML mode through trac, e.g. https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.connectivity.corridors/description.html (svn propset must be right for this, I fixed it) Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] New AddOns for Analyzing landscape connectivity based on graph-theory - the r.connectivity.*-toolchain
But I did not manage to add the AddOns using g.extension under MS Windows. (They appear to be compiled: http://wingrass.fsv.cvut.cz/grass64/addons/grass-6.4.3svn/ ) tried here with osgeo4w-wingrass6.4.3svn g.extension.py extension=r.connectivity.corridors svnurl=http://svn.osgeo.org/grass/grass-addons/grass6 Downloading precompiled GRASS Addons r.connectivity.corridors... Updating metadata file... Installation of r.connectivity.corridors successfully finished (Wed Sep 12 23:07:38 2012) Command finished (3 sec) (Wed Sep 12 23:07:46 2012) g.extension.py extension=r.connectivity.distance svnurl=http://svn.osgeo.org/grass/grass-addons/grass6 Downloading precompiled GRASS Addons r.connectivity.distance... Updating metadata file... Installation of r.connectivity.distance successfully finished (Wed Sep 12 23:07:50 2012) Command finished (3 sec) (Wed Sep 12 23:07:56 2012) g.extension.py extension=r.connectivity.network svnurl=http://svn.osgeo.org/grass/grass-addons/grass6 Downloading precompiled GRASS Addons r.connectivity.network... Updating metadata file... Installation of r.connectivity.network successfully finished (Wed Sep 12 23:07:59 2012) Command finished (3 sec) - best regards Helmut -- View this message in context: http://osgeo-org.1560.n6.nabble.com/New-AddOns-for-Analyzing-landscape-connectivity-based-on-graph-theory-the-r-connectivity-toolchain-tp5000351p5001549.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] New AddOns for Analyzing landscape connectivity based on graph-theory - the r.connectivity.*-toolchain
For WinGRASS version 6, additional .bat files are required in the bin-folder. Should these bat-files be added to the svn-repository? I think yes, and the Makefile should take care to get them into the bin-folder. AFAIK bat-files are built by addon-compilation: C:\Users\X\AppData\Roaming\GRASS6\addons dir /b modules.xml r.connectivity.corridors r.connectivity.corridors.bat r.connectivity.distance r.connectivity.distance.bat r.connectivity.network r.connectivity.network.bat [...] the wx-gui of the 3 modules are starting, but the manual is missing in the wx-gui; altough the html's are built and in C:\Users\\AppData\Roaming\GRASS6\addons\docs\html - best regards Helmut -- View this message in context: http://osgeo-org.1560.n6.nabble.com/New-AddOns-for-Analyzing-landscape-connectivity-based-on-graph-theory-the-r-connectivity-toolchain-tp5000351p5001551.html Sent from the Grass - Users mailing list archive at Nabble.com. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] New AddOns for Analyzing landscape connectivity based on graph-theory - the r.connectivity.*-toolchain
Dear all, Last week I presented a set of three new GRASS-AddOns for analyzing landscape connectivity based on graph-theory at the European Congress of Conservation Biology (ECCB, http://eccb2012.org/) in Glasgow . This set of tools applies methods documented (a.o.) in the following literature to the input data you might have. Bunn, A. G., Urban, D. L. Keitt, T. H. 2000: Landscape connectivity: A conservation application of graph theory. Journal of Environmental Management (2000) 59: 265-278. http://www.sciencedirect.com/science/article/pii/S0301479700903736 Calabrese, J. M. Fagan, W. F. 2004/b: A comparison-shopper's guide to connectivity metrics. Front Ecol Environ 2 (10): 529-536 . http://dx.doi.org/10.1890/1540-9295(2004)002[0529:ACGTCM]2.0.CO;2http://dx.doi.org/10.1890/1540-9295(2004)002%5b0529:ACGTCM%5d2.0.CO;2 Minor, E. S. Urban, D. L. 2008: A Graph-Theory Framework for Evaluating Landscape Connectivity and Conservation Planning. Conservation Biology 22 (2): 297-307. http://www.uic.edu/labs/minor/minorurban2008.pdf Zetterberg, A., Mörtberg, U. M. Balfors, B. 2010: Making graph theory operational for landscape ecological assessments, planning, and design. Landscape and Urban Planning (2010) 95: 181-191. http://www.sciencedirect.com/science/article/pii/S016920461204 Ranius, T. Roberge, J.-M. 2011: Effects of intensified forestry on the landscape-scale extinction risk of dead wood dependent species. Biodiversity and Conservation 20 (13): 2867-2882. http://www.springerlink.com/content/ch9qtv2665h624q4 The input data the tools take are: - A polygon vector map containing habitat patches (of your species / habitat type in question) and a column for a population proxy (e.g. patch area). (required) - A cost raster map (for more information on that see the r.cost-manual) (optional; if no cost raster is provided Euclidean distance is used). - Dispersal information o A maximum (cost) distance threshold for assumed connectivity o A dispersal kernel (defined by three variables of a negative exponential decay function (see eg. Bunn et al. 2000) The outputs are connectivity measures on vertex (=patch) level, edge (= the connection between two patches) level, and graph (the entire network) level. With r.connectivity.corridors you can also identify corridors for the connections (edges) you select, and you can weight their importance based on a column of your choice (e.g. connectivity measures from r.connectivity.network). The tools (and documentation) can be found in the GRASS AddOns SVN repository (see: r.connectivity.distance, r.connectivity.network, r.connectivity.corridors in the http://grass.osgeo.org/wiki/GRASS_AddOns/). They are UNIX-shell (and one R-) scripts. Required additional software is: Cran R with at least the packages igraph (version 0.6-2) and nlme installed. If you want to make use of parallel processing / multi-threading you need also the packages doMC, foreach, iterators, codetools, and multicore. But multithreading is only supported on LINUX. The tools have not been tested on Windows yet, but this will be done in near future. Any kind of feedback would be very much appreciated! Cheers Stefan P.S.: What do you think, how helpful would an example based on the spearfish dataset be? If you think so, I will add that to the documentation, as soon as the projects which triggered the development of the r.connectivity.*-tools are published. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] New AddOns for Analyzing landscape connectivity based on graph-theory - the r.connectivity.*-toolchain
P.S.: What do you think, how helpful would an example based on the spearfish dataset be? +1, it would be very good to have examples about this tools. thanks! ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] New AddOns for Analyzing landscape connectivity based on graph-theory - the r.connectivity.*-toolchain
On Fri, Sep 7, 2012 at 10:36 AM, Giovanni Manghi giovanni.man...@faunalia.pt wrote: P.S.: What do you think, how helpful would an example based on the spearfish dataset be? +1, it would be very good to have examples about this tools. Please use the North Carolina dataset which is much richer. If you need specific data, we can extend it which we'll do anyway for the upcoming NC dataset update. Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
