[GRASS-user] r.in.external in GUI
Hello, I cannot find r.in.external in the wxPython based GUI: http://grass.itc.it/grass64/manuals/html64_user/r.external.html Would it be possible to add support for * r.in.external for a single layer * r.in.external for multiple layers in the same way as it is provided with r.in.gdal? The same same applies to v.in.external. I use grass64 compiled from yesterday's SVN rev. Kind regards, Timmie ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.in.external in GUI
Tim Michelsen ha scritto: I cannot find r.in.external in the wxPython based GUI: http://grass.itc.it/grass64/manuals/html64_user/r.external.html Would it be possible to add support for * r.in.external for a single layer * r.in.external for multiple layers in the same way as it is provided with r.in.gdal? The same same applies to v.in.external. isn't it r.external instead of r.in.external? however, just yesterday we put it in the QGIS gui, nice coincidence. All the best. -- Paolo Cavallini: http://www.faunalia.it/pc ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Write python grass program with osgeo4w
Moskovitz, Bob wrote: A coworker and I have been trying to use the first example in http://download.osgeo.org/grass/grass6_progman/pythonlib.html http://download.osgeo.org/grass/grass6_progman/pythonlib.html. We discovered that import grass.script as grass has to be changed to import grass. Below is the example and the error we are getting is this: C:\m.test.py Traceback (most recent call last): File C:\OSGeo4W\apps\grass\GRASS-~1.0SV/scripts\m.test.py, line 31, in module options, flags = grass.parser() File C:\OSGeo4W\apps\grass\GRASS-~1.0SV\etc\python\grass.py, line 208, in parser os.execvp(g.parser, [name] + argv) File C:\OSGeo4W\apps\Python25\lib\os.py, line 353, in execvp _execvpe(file, args) File C:\OSGeo4W\apps\Python25\lib\os.py, line 389, in _execvpe func(fullname, *argrest) OSError: [Errno 22] Invalid argument Any ideas what is going on? This is a bug in grass.py; Windows requires g.parser.exe rather than g.parser. This was fixed with: http://trac.osgeo.org/grass/changeset/37075 -- Glynn Clements gl...@gclements.plus.com ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] .grassrc missing
Gabrial wrote: Following installation of Grass from fink the versions there seem really really old, why not try http://grass.osgeo.org/grass64/binary/macosx/ ? 6.4.0rc5 is ready for everyday use. I am getting an error Warning: spearfish60 is not a valid mapset. spearfish60 isn't a mapset, it's the project location name. the mapset to select is user1 within the spearfish location. see http://grass.bologna.enea.it/tutorial/ http://grass.osgeo.org/grass64/manuals/html64_user/helptext.html good luck, Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.thin quirk
On Jun 11, 2009, at 12:50 AM, Dwight Needels wrote: On Jun 11, 2009, at 12:01 AM, Dwight Needels wrote: On Jun 6, 2009, at 11:36 PM, Dwight Needels wrote: Hi all. I have run into a quirk using r.thin, but I am not sure whether or not it is a bug. I have a raster that was generated from multiple GPS tracks using v.rast followed by r.buffer. Using r.thin followed by r.to.vect creates a vector that must then be cleaned using v.clean to remove dangles (so far, so good). The quirk is that r.thin occasionally creates a triangle at the intersection of two lines instead of two intersecting lines. All of the examples I have seen involve relatively acute angles (less than 25 degrees??). I have attached a screenshot that shows the raster in magenta, the vector with dangles in white, and the cleaned vector as (a thinner) green. There are numerous acute angles that generate the vectors I would expect, with one exception in the center. Is this expected behavior? If so, is there an easy way to search for all such resulting triangles in a vector or to remove all such extra lines in a vector? If not, is there a way to fix it? Thanks, -Dwight r.thin.png ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user Although I figured out how to file a bug report on this, http://trac.osgeo.org/grass/ticket/636 , I am not sure how to respond directly to comments on the ticket. Hamish, I used the screenshot showing the vectors because I had already created it to look for artifacts. The extra line that makes the triangle is also present in the thinned raster (screenshot attached). Thanks, -Dwight r.thin_raster.png Follow-up... the two examples of this happening in this particular file each have a single white pixel surrounded on 7 out of 8 directions by red pixels, but still touching a white pixel on a corner in the 8th direction (see two screenshots). I suspect that r.thin is treating this as a hole even though it is touching an edge. Another way of saying this is that the two red pixels touching in 1 out of the 8 directions are treated as a line. Perhaps there could be a flag to control this behavior. Thanks, -Dwight r.thinpinched_1.pngr.thinpinched_2.png It does appear that the observed quirk is caused by the way r.thin treats pixels that touch only at their corners. I thought I could work around this my using r.neighbors method=mode. Although this does eliminate single empty pixels, it sometimes generates new ones elsewhere. Although I am sure there is a clever way to use r.mapcal, I ended up inverting the map, running r.grow, and inverting again (the equivalent of what could be called r.shrink). As far as I can tell, this eliminates single pixel holes without generating new ones. Can someone who understands the way r.grow works confirm that this will always be the case? In the workflow where I discovered this (averaging GPS tracks), I ended up using r.buffer on the inverted map instead of r.grow. In addition to apparently eliminating triangles at intersections, it also reduces the number of dangles generated by r.thin by smoothing the raster before thinning. -Dwight ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] what is requried when import data to grass?
I don't recall the start of your thread: Are you saying that you need to be able to handle any data that clients throw at you in *any* CRS? How will you know the CRS of the client's maps? (Many data formats do not require full metadata with CRS information) In fact I perfer to create location and mapset for each requested map according the crs or other parameter, and how to get the parameter is another topic( for some ogc web servcie wcs wms we can get most paramter from the requsted url for example: http://localhost:8080/wcs?Request=wcsidentifier=imageIDcrs=EPSG:4326bbox=[][]$format=tiff .) So what block me is the location and mapset, in a word I am so unfamiliar with the grass although I have read some documents that I can not confignation as the pywps did. And one other point came to my mind: be aware that the user calling the GRASS script must be the owner of the $GISDBASE directory structure. So if these are web based apps, then the user running your http server must own the GRASS database directory. What we do is to provide a interface to the user, the process name and some required parameter for the grass, the real requestor of the grass is ourselvers , in other words it is the server (we own the GISDBASE)to call the grass,and the parameter passed to grass come from the user. May be I can describe it as follows: the user(web browse) provide the paramter and the original map ---our server(get the para and the map) - call the grass (pass the praa and map) -grass process-grass send the result,(may be exported) -server get the requested data --- send the request data to user client Good luck, and keep us posted, -- Micha GRASS once the straight-forward way to make the required location, mapset and files, then use the instructions here: http://grass.osgeo.org/wiki/GRASS_and_Shell to run your grass commands from a shell/python script? I read the shell,actually I am using another script in the annex,and I think they have the same thought. 2009/6/11 Micha Silver mi...@arava.co.il mailto:mi...@arava.co.il maven apache wrote: Hi: I followed the doc from the web resrouce: https://svn.wald.intevation.org/svn/pywps/tags/pywps-3.1.0/pywps/Grass.py And I think what we are doing is similar to theirs,so I thought the confignation of grass maybe correct for us. Is there some special reason you need to create the GRASS directory structure programatically each time? Can't you just start GRASS once the straight-forward way to make the required location, mapset and files, then use the instructions here: http://grass.osgeo.org/wiki/GRASS_and_Shell to run your grass commands from a shell/python script? --Micha 2009/6/11 Nikos Alexandris nikos.alexand...@felis.uni-freiburg.de mailto:nikos.alexand...@felis.uni-freiburg.de maven: And I know the reason of the problem now. Which is? However as what you said,I should create a new location and mapset if necessary,it does not work. I create two folders nLocation/nmapset and create a wind file in the nmapset dir, however when I run the grass gui,I also can not seclect the new location to enter. Sorry, I never create manually those directories and the WIND file. I always use the recommended way, that is through GRASS. Read _A)_ or/ and _B)_ in: http://grass.osgeo.org/grass64/manuals/html64_user/helptext.html It throw the error message:the selection location [nlocation ]is not valide. Is the procedure I create the new location is wrong? I followed the maual Which manual? Nikos This mail was received via Mail-SeCure System. ___ grass-user mailing list grass-user@lists.osgeo.org mailto:grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user This mail was received via Mail-SeCure System. 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
