[GRASS-dev] Image Segmentation - GRASS - GSoC report #8
Hi, Here is this week's update: Accomplished: * "mid term" review, not just the required question from Google, but also compiling and prioritizing remaining ideas for improving the program. * Started on that todo list, doing some general code clean up after getting some detailed comments from Markus. * Pierre is getting good results using the program, some segmentations are at: http://grass.osgeo.org/wiki/GRASS_GSoC_2012_Image_Segmentation#Results Plan: * Add as many of the top priority items as possible (starting seeds plus more speed improvements) Blocking: Nothing. -Eric ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Problem compiling ximgview in the latest grass_trunk
Thanks heaps for your help Glynn, it worked. For reference, here's the workaround I used: roudierp@mangatainoka:/usr/local/src/grass_trunk$ more include/Make/Platform.make | grep -n XLIB 86:XLIBPATH= -L/usr/bin Cheers, Pierre 2012/7/14 Glynn Clements : > > Pierre Roudier wrote: > >> Is there an easy work-around this? > > Provided that the configure script completes, you can edit > include/Make/Platform.make by hand. The relevant variables are > XLIBPATH and XLIB. > > -- > Glynn Clements -- Scientist Landcare Research, New Zealand ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Problem compiling ximgview in the latest grass_trunk
Pierre Roudier wrote: > Is there an easy work-around this? Provided that the configure script completes, you can edit include/Make/Platform.make by hand. The relevant variables are XLIBPATH and XLIB. -- Glynn Clements ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [pyGRASS] Report #8
Hi everyone! you can follow the pyGrass's progress from the wiki page: http://grass.osgeo.org/wiki/GRASS_SoC_Ideas_2012/High_level_map_interaction#Report7_-_2012-07-13 1) What did I do this week? Start to work on the pygrass modules class. 2) What will I be working on next week? Continue with the the pygrass modules class. 3) Did I meet with any stumbling blocks? No, I wrote a first implementation of the pygrass modules, but after discussion with my mentor I have started to rewrite the class. King regards! Pietro ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Weekly report #8 - GRASS v.net front end
Hello, 1) What do I have completed this week? This week I have integrated 5 v.net.* modules into front end. I have also added output console into dialog and analysis run in other thread. More info can be found at [1]. 2) What am I going to achieve for next week? I am going to work on improving usability of the dialog, because so far I have just added new functions and have not paid much attention to layout of dialog. Also I would like to extend settings possibilities and start to work on snaping to nodes. 3) Is there any blocking issue? No. Regards, Stepan [1] http://grass.osgeo.org/wiki/GRASS_GSoC_2012_WxGUI_front_end_for_vector_analysis_modules#Week_8_.28July_9.29 ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] limits of r.patch
Margherita, You may be running into the open file limit for linux. http://www.cyberciti.biz/faq/linux-increase-the-maximum-number-of-open-files/ , although 1573 files seems a bit low.I generally batch my r.patch'ing in groups of 120 or so with a python script , then go back and r.patch the results. It works well if the file names are related to the file locations. See ugly python script below where elevation grid data with the "temp_"grid tiles were named by the x coordinate were patched together ( yes, I know you can do this better now with direct python calls to grass:-)): # grass_tile_merge.py import os,string,re,glob grdarr=['D2370','D2371','d2371','d2372','D2372','D2373'] for grdarrlist in grdarr: gtarr=['0','1','2','3','4','5','6','7','8','9'] for gtarrl in gtarr: gtarrb=['0','1','2','3','4','5','6','7','8','9'] for gtarrl2 in gtarrb: gtarrc=['0','1','2','3','4','5','6','7','8','9'] for gtarrl3 in gtarrc: grdstr="" gtemp="temp_"+grdarrlist+gtarrl+gtarrl2+gtarrl3 #print grpitem greplist="/imagery/grass/ncstpftlidar_83/newdem/fcell/"+grdarrlist+gtarrl+gtarrl2+gtarrl3+"*_ras" grdlist=glob.glob(greplist) # creates a list of those grid files for t1 in grdlist: t1base=os.path.basename(t1) grdstr=grdstr+t1base+"," #grdarr.append(t1base) grdstr=grdstr[:-1] print grdstr regtite="g.region rast=%s"%(grdstr) os.system(regtite) patchgrp="r.patch input=%s output=%s"%(grdstr,gtemp) print patchgrp os.system(patchgrp) #http://grass.fbk.eu/grass64/manuals/html64_user/r.patch.html Hope this helps. Doug Doug Newcomb USFWS Raleigh, NC 919-856-4520 ext. 14 doug_newc...@fws.gov - The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats. Margherita Di Leo Sent by: grass-dev-boun...@lists.osgeo.org 07/13/2012 11:27 AM To grass-dev@lists.osgeo.org cc Subject [GRASS-dev] limits of r.patch Hi All, I probably am requiring too much, but this is just for sharing an experience. I've just imported in GRASS 1573 ASTER GDEM tiles, using r.external, and everything seemed to be OK. Then I ran: GRASS 6.4.3svn (ASTER_GDEM):~ > r.patch in=`g.mlist pat=AST* sep=,` out=aster_gdem ERROR 1: TIFFOpen:/forest/ASTER-GDEM/Dem_lzw/ASTGTM_N45E010_dem_lzw.tif: Too many open files WARNING: Unable to open raster map ERROR: One or more input raster maps not found I'm on Red Hat Enterprise Linux Server Rel. 6.3, RAM 16 GB. Cheers, -- Dr. Margherita Di Leo ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] limits of r.patch
2012/7/13 Margherita Di Leo : > Hi All, > hi madi > I probably am requiring too much, but this is just for sharing an > experience. I've just imported in GRASS 1573 ASTER GDEM tiles, using > r.external, and everything seemed to be OK. Then I ran: > > GRASS 6.4.3svn (ASTER_GDEM):~ > r.patch in=`g.mlist pat=AST* sep=,` > out=aster_gdem > ERROR 1: TIFFOpen:/forest/ASTER-GDEM/Dem_lzw/ASTGTM_N45E010_dem_lzw.tif: Too > many open files > WARNING: Unable to open raster map > ERROR: One or more input raster maps not found > > I'm on Red Hat Enterprise Linux Server Rel. 6.3, RAM 16 GB. > I think it's a limit of linux, you could patch images in more tiles and after patch the tiles in a file > Cheers, > > -- > Dr. Margherita Di Leo > -- ciao Luca http://gis.cri.fmach.it/delucchi/ www.lucadelu.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] limits of r.patch
Hi All, I probably am requiring too much, but this is just for sharing an experience. I've just imported in GRASS 1573 ASTER GDEM tiles, using r.external, and everything seemed to be OK. Then I ran: GRASS 6.4.3svn (ASTER_GDEM):~ > r.patch in=`g.mlist pat=AST* sep=,` out=aster_gdem ERROR 1: TIFFOpen:/forest/ASTER-GDEM/Dem_lzw/ASTGTM_N45E010_dem_lzw.tif: Too many open files WARNING: Unable to open raster map ERROR: One or more input raster maps not found I'm on Red Hat Enterprise Linux Server Rel. 6.3, RAM 16 GB. Cheers, -- Dr. Margherita Di Leo ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] script selecting the extent
Solved by: gdaltindex index.shp *.tif ogr2ogr -f CSV list.csv an_index.shp -spat xmin ymin xmax ymax ciao On Fri, Jul 13, 2012 at 11:37 AM, Margherita Di Leo < dileomargher...@gmail.com> wrote: > Hi, > > I have more than 22000 GeoTiff's stored in a folder (the world coverage of > ASTER GDEM) and I have to select among them only those covering the Europe > area, in order to import them in GRASS. I was about to write a Python > script to do that (using gdalinfo), but I felt like reinventing the wheel, > because I'm pretty sure I've already seen in the internet something doing > that, but can't remember where.. or likely some of you guys has already > experienced this and are willing to share a script :-) > > TIA, > > madi > > > -- > Dr. Margherita Di Leo > > > > -- Dr. Margherita Di Leo ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] script selecting the extent
Hi, I have more than 22000 GeoTiff's stored in a folder (the world coverage of ASTER GDEM) and I have to select among them only those covering the Europe area, in order to import them in GRASS. I was about to write a Python script to do that (using gdalinfo), but I felt like reinventing the wheel, because I'm pretty sure I've already seen in the internet something doing that, but can't remember where.. or likely some of you guys has already experienced this and are willing to share a script :-) TIA, madi -- Dr. Margherita Di Leo ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
