Re: [GRASS-user] manual page for addons
There was some discussion this summer in relation to g.extension about user-addon paths. For user manual pages, see how I do it for OSX in macosx/app/ build_html_user_index.sh. It's basically a copy of build_html_index.sh (used in compilation only) changed to build a user html index on startup, from a known path (not GRASS_ADDON_PATH). It's a bit clunky because the installed help index is static, so the user help index must be a separate index, and it's not possible to link to a user's home folder from the main index in html (because it's variable). I think GRASS needs a more structured external addon path setup than the loose GRASS_ADDON_PATH (which only extends the env PATH). My GRASS_ADDON_ETC, and companion g.findetc is one step to this, but it doesn't say anything about help files. On Nov 1, 2009, at 8:30 PM, Hamish wrote: there may be something in William's extra ETC for frameworks magic. Hamish - William Kyngesburye http://www.kyngchaos.com/ "Oh, look, I seem to have fallen down a deep, dark hole. Now what does that remind me of? Ah, yes - life." - Marvin ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] manual page for addons
there may be something in William's extra ETC for frameworks magic. Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Problem with Lidar Tools
Thanks for your help ! Unfortunately I still don't get satisfying results with the Lidar tools. Here is what I have done so far: - Updated to 6.4 on Windows: v.outlier doesn't work (see my post in Win Grass forum) - Installed Grass 6.4 RC 5 on Ubuntu (Ubuntu package): same results like on Windows Grass 6.3 - Decreased spline steps to 0.04: v.outlier and v.lidar.edgedetection give errors. My results are better the higher the spline steps are (> 20). Brovelli recommends spline step 3 up to 4 times of the planimetric resolution. AFAIK planimetric resolution means points per m². If I have 50 pts/m² this would mean a spline step of 200 ?? With spline steps about 20 I get nice edges and with spline step of 400 complete buildings are detected as edges. - Tried the Lidar demo data (nc_spm_08_2008_may18) and followed the instructions on the Micro-tutorial_for_LIDAR_data_analysis: v.lidar.edgedetection took so long, that I canceled process after 1 h (input file has only 2000-3000 points - so something must be wrong) I have also a problem to understand the definitions of first and last return data. Here is a part of my Lidar data (ASCII format converted from raw LIdar binary): 0 lon lat height intensity last first 1 3360422.27 5825275.62 37.16 255 1 1 2 3360421.94 5825275.60 38.21 56 0 1 3 3360422.48 5825275.60 37.18 255 1 0 4 3360422.17 5825275.58 38.18 141 0 1 5 3360422.65 5825275.58 37.26 255 1 0 6 3360422.84 5825275.56 37.31 255 1 1 7 3360423.05 5825275.54 37.32 255 1 1 8 3360423.36 5825275.52 37.13 255 1 1 9 3360423.06 5825275.50 38.11 12 0 1 10 3360423.60 5825275.50 37.09 255 1 0 11 3360423.70 5825275.49 37.32 255 1 1 First and last returns can be true (1) or false (0) or both. My understanding is, that all points that have first return=true are first returns and all returns that have last=true are last returns. When first and last are true we have a single pulse otherwise we have double pulses. If I understand the microtutorial correctly I need for v.lidar.growing as input the last return single pulses (last=true and first=false) and as first all pulses with first=true. But I get better results when I use as input all last return pulses (only last=true) and as input only the first single pulses (first=true and last=false). I still have the problem that v.lidar.growing does not change categories. Output has only 2 categories - same as output of v.lidar.edgedetection. I have attached two screenshots of my results so far (using the parameters in my first post). I have not yet run v.surf.bspline. http://n2.nabble.com/file/n3928180/lidar_before_after.jpg Classification after v.lidar.edgedetection: http://n2.nabble.com/file/n3928180/edgedetected.jpg Any ideas regarding v.lidar.growing ? Thanks - Kaipi -- View this message in context: http://n2.nabble.com/Problem-with-Lidar-Tools-tp3918684p3928180.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] NVIZ - Visualization of buildings
On Fri, Oct 30, 2009 at 10:24 AM, incanus wrote: > > Hi everyone, > I'm trying to visualize a DEM that I've generated of the buildings of a > city. In each cell I have the meters of elevation. When I try to see it with > NVIZ I found that it makes something like interpolation, smoothing the > corners like it was a DEM of terrain instead of "hard edges" (i don't know > how to say it). For speed reasons, NVIZ is per default (typically) starting with a reduced visualization. To increase that: Menu: Visualize -> Raster Surface -> Resolution | fine: XXX The smaller XXX, the higher the shown resolution. When XXX=1, then the full resolution as defined by g.region is used. Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Topographic Correction of Satellite images
On Fri, Oct 30, 2009 at 12:45 PM, Pablo Carreira wrote: > > I'm seaching for a way to do orthoretification of GeoEye1 high resolution > images on grass based o SRTM DEM, the add-on i.topo.corr does not exist > anymore. It does :) http://trac.osgeo.org/grass/browser/grass-addons/imagery/i.topo.corr > Does anyone have a clue on how to do that? But i.topo.corr is a radiation correction, not a terrain correction in the sense of orthorectification. A rudimentary implementation was available in GRASS 4.x in the image3 library but that was not completely developed. We are looking for a developer (master student thesis?) to implement such an algorithm. Meanwhile you could check OSSIM which has some sensor models: http://download.osgeo.org/ossim/docs/pdfs/OSSIMOrthos.pdf Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Help needed in identifying the DEM / DTED classes used in grass
On Fri, Sep 18, 2009 at 5:27 AM, Anand V wrote: > Hi there, > > I am new to GRASS and iam trying to load DTED map in my application. In > GRASS source code i need to identify the classes used to load a DEM or DTED > data. > > I tried and i am not able to identify. Please check r.in.gdal: http://grass.osgeo.org/grass64/manuals/html64_user/r.in.gdal.html Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] manual page for addons
2009/9/16 Facundo Muñoz : > > Hi, > I'm using a grass script of my own (say script.sh) which is located in a > separate directory pointed by GRASS_ADDON_PATH. > However, the graphical interface provided by g.parser does not show the > corresponding manual page. > I have a script.sh.html in the same directory. ¿Should I put a copy in > /usr/share/doc/grass-doc/html/? Yes. > ¿Is there any other environment variable pointing to the add-on > documentation? AFAIK that's not (yet?) available. Markus > Thanks! > ƒacu.- > ___ > grass-user mailing list > grass-user@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-user > ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Using GRASS and R at the same time (wxpython)
On Thu, Oct 29, 2009 at 11:22 AM, Martin Mainzer wrote: > Hello at all > I do my statistical analyses with R. In the old tcltk-GUI I used "Run > (background)" to start R from within the GRASS GUI. Within the new > wxpython-GUI I would like to have the same behaviour, but I do not know how > to manage it. If I run "rgui" in the cmd section, GRASS will not accept any > other command. "rgui&" fails (also "rgui.exe&" and "rgui.exe &". AFAIK the wxpython-GUI cmd line is not a true command line. > How can I > use GRASS and R at the same time, without freezing of GRASS during R is > running (from within the new wxpython-GUI). > I used the binary installer for windows > (WinGRASS-6.4.0SVN-r39626-1-Setup.exe) on a W2k machine. http://grass.osgeo.org/grass64/binary/mswindows/native/#Launching_GRASS -> Click on the GRASS msys icon... This should open the wxGUI along with a cmd line which should support "&". Please report back to the list if this helps. Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
