Re: [GRASS-user] Re: First time trying to install add on g.extension (r.stream.order)
On Sat, Sep 25, 2010 at 10:47 AM, Tim Michelsen wrote: >> note g.extension is rather new and untested compared the rest of >> the software, especially on Windows. Besides svn for building C >> modules, you will need a C compiler which doesn't ship with the >> GRASS installer. > What about a automtaci build process on the server? > Then the users would download a "package" and drop in a extension > directory or use g.extension for that task. > I mean something similar to Launchpad PPA or PyPi. For Windows: We need to convince Martin Landa to run a compilation of all Addons on his winGRASS build server. I have added Makefiles to most directories, whatever is missing would just be not there then. Then copy the resulting *.exe into a separate Addons download directory on josef... Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Estimating Albedo from Landsat
Nikos: ... > Downloaded: > - extra: LT50160351988258XXX03 (includes visible clouds - maybe good for > testing?) # import landsat bands in wgs84, utm, zone 17 # r.proj to nc_spm_08/landsat # set region g.region rast=lsat5_1988.1 -p projection: 99 (Lambert Conformal Conic) zone: 0 datum: nad83 ellipsoid: a=6378137 es=0.006694380022900787 north: 361770 south: 144750 west: 463950 east: 709530 nsres: 30 ewres: 30 rows: 7234 cols: 8186 cells: 59217524 # rgb colors for 742 i.landsat.rgb r=lsat5_1988.2 g=lsat5_1988.4 b=lsat5_1988.7 strength=96 d.rgb r=lsat5_1988.2 g=lsat5_1988.4 b=lsat5_1988.7 # obvious clouds # toar i.landsat.toar band_prefix=lsat5_1988 method=uncorrected sensor=5 product_date=1988-09-14 date=1988-09-14 solar_elevation=48.6773844 # acca i.landsat.acca -5f2 band_prefix=lsat5_1988.toar output=lsat5_1988.toar.acca # how many cats? r.info lsat5_1988.toar.acca -r min=6 max=9 # draw only "acca" cat=6 d.erase black d.rast lsat5_1988.toar.acca cat=6 -o In the "acca" result: - clouds are detected (cat=6), not that bad(ly) I suppose. Some filtering could push away the (rest of the) "noise". - obvious mis-detections (commission errors) found within - n=188310 s=168270 w=618870 e=636150 (bare ground? urban area? not sure about the confusing land cover/class here...) - n=219030 s=180510 w=646410 e=655740 (road) - in the borders due to the non-identical extent of all bands (!?) - categories 7 and 8 seem to be empty, category 9 looks very messy Could it be that non-cloudy acquisitions are mistreated by the algorithm? I can't clearly recognise clouds in the landsat scenes included in NC data set (both the 1987 and the 2000 scenes). Will (then) the algorithm work (only) with (very) cloudy data? Nikos ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Unable to load gdal library error
On Sat, Sep 25, 2010 at 7:57 AM, Glynn Clements wrote: > > Daniel Victoria wrote: > >> It's strange cause I can use gdalinfo and gdal_translate on the SRTM >> tif tiles and last night I patched them using gdal_merge.py. Also, >> r.in.gdal works fine. And I can run r.info on the tiles imported using >> r.external. But I can't display them or query the values (r.what also >> gives ERROR: Unable to load GDAL library). > > That error message indicates a failure to load the GDAL library at run > time via dlopen(). r.in.gdal is linked against GDAL, and r.info > doesn't need access to the raster data. You will only get the error > from modules which attempt to access the raster data for a "linked" > map created with r.external. > > The code which loads the library attempts to dlopen() each of > following names in turn: > > libgdal.1.1.so > gdal.1.0.so > gdal.so.1.0 > libgdal.so.1 > libgdal.so > > If none of the attempts succeed, you get the above error. > > The library must be listed in /etc/ld.so.cache (generated by ldconfig) > or in one of the directories in $LD_LIBRARY_PATH. Also, it must have > complete dependency information, and all of its dependencies must be > satisfied. > I guess it's a library naming problem then because what I have inside ld.so.chache is: dan...@xadrez:/etc$ sudo ldconfig -p | grep gdal libgdal1.7.0.so.1 (libc6) => /usr/lib/libgdal1.7.0.so.1 libgdal1.7.0.so (libc6) => /usr/lib/libgdal1.7.0.so libgdal1.6.0.so.1 (libc6) => /usr/lib/libgdal1.6.0.so.1 dan...@xadrez:/etc$ Also, I don't have any of the lib names mentioned by Glynn in /usr/lib, as you can see bellow. dan...@xadrez:/usr/lib$ ls *gdal* libgdal1.6.0.so.1 libgdal1.7.0.a libgdal1.7.0.so.1 libgdal1.6.0.so.1.13.3 libgdal1.7.0.so libgdal1.7.0.so.1.14.2 gdal16plugins: gdal_GRASS.so ogr_GRASS.so gdal17plugins: gdal_GRASS.so ogr_GRASS.so So, by linking libgdal.1.1.so to libgdal1.7.0.so everything came back to normal... Well, sort of... Now, when I try r.what on the raster I get... WARNING: category support for [srtm_21_12] in mapset [PERMANENT] missing ERROR: Unable to read category file of raster map in For the record, this is part of the r.info output of the srtm tile: Type of Map: raster Number of Categories: ?? | | Data Type:CELL | | Rows: 6001 | | Columns: 6001 | | Total Cells: 36012001 Cheers Daniel > Glynn Clements > ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Unable to load gdal library error
Daniel Victoria wrote: > It's strange cause I can use gdalinfo and gdal_translate on the SRTM > tif tiles and last night I patched them using gdal_merge.py. Also, > r.in.gdal works fine. And I can run r.info on the tiles imported using > r.external. But I can't display them or query the values (r.what also > gives ERROR: Unable to load GDAL library). That error message indicates a failure to load the GDAL library at run time via dlopen(). r.in.gdal is linked against GDAL, and r.info doesn't need access to the raster data. You will only get the error from modules which attempt to access the raster data for a "linked" map created with r.external. The code which loads the library attempts to dlopen() each of following names in turn: libgdal.1.1.so gdal.1.0.so gdal.so.1.0 libgdal.so.1 libgdal.so If none of the attempts succeed, you get the above error. The library must be listed in /etc/ld.so.cache (generated by ldconfig) or in one of the directories in $LD_LIBRARY_PATH. Also, it must have complete dependency information, and all of its dependencies must be satisfied. -- Glynn Clements ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] First time trying to install add on g.extension (r.stream.order)
-Ursprüngliche Nachricht- Von: "Helmut Kudrnovsky" Gesendet: 25.09.2010 11:19:32 An: grass-user@lists.osgeo.org Betreff: First time trying to install add on g.extension (r.stream.order) >>> I have looked through many posts and help files to no avail, if >>> anyone can tell me what additional steps/programs/plugins are >> >required to install addons I would really appreciate the help. >> >>see [http://subversion.apache.org] > >some time ago I've opened a ticket in osgeo4w to include svn into the stack ah ... and i can see, in preparing the wingrass-package, all svn-exes are removed, see http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_6_4/mswindows/GRASS-Packager.bat#L62 I'll remove this line and then we'll see how g.extension is working on windows. best regards Helmut ___ Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02 ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] First time trying to install add on g.extension (r.stream.order)
>> I have looked through many posts and help files to no avail, if >> anyone can tell me what additional steps/programs/plugins are > >required to install addons I would really appreciate the help. > >see [http://subversion.apache.org] some time ago I've opened a ticket in osgeo4w to include svn into the stack >note g.extension is rather new and untested compared the rest of >the software, especially on Windows. Besides svn for building C >modules, you will need a C compiler which doesn't ship with the >GRASS installer. a C compiler is shiped with the Wingrass-installer, because all of the osgeo4w-build- environment is included in the WinGrass-installer. see output from the msys-rxvt-command-line of WinGrass64-release: Cleaning up temporary files ... Starting GRASS ... WARNUNG: Attention! WARNUNG: Locking is not supported on Windows! __ ___ _____ / / __ \/ | / ___/ ___/ / / _/ ___/ / / __/ /_/ / /| | \__ \\_ \ / / __ / / \__ \ / /_/ / _, _/ ___ |___/ /__/ / / /_/ // / ___/ / \/_/ |_/_/ |_/// \/___/// Welcome to GRASS 6.4.0 (2010) GRASS homepage: http://grass.osgeo.org/ This version running thru: Bourne Shell (/bin/sh) Help is available with the command: g.manual -i See the licence terms with: g.version -c If required, restart the GUI with: g.gui wxpython When ready to quit enter:exit GRASS 6.4> gcc --help Usage: gcc.exe [options] file... Options: -pass-exit-codes Exit with highest error code from a phase --help Display this information --target-helpDisplay target specific command line options (Use '-v --help' to display command line options of sub-processes) -dumpspecs Display all of the built in spec strings -dumpversion Display the version of the compiler -dumpmachine Display the compiler's target processor -print-search-dirs Display the directories in the compiler's search pat h -print-libgcc-file-name Display the name of the compiler's companion library -print-file-name= Display the full path to library -print-prog-name= Display the full path to compiler component -print-multi-directory Display the root directory for versions of libgcc -print-multi-lib Display the mapping between command line options and multiple library search directories -print-multi-os-directory Display the relative path to OS libraries -Wa,Pass comma-separated on to the assembler -Wp,Pass comma-separated on to the preprocesso r -Wl,Pass comma-separated on to the linker -Xassembler Pass on to the assembler -Xpreprocessor Pass on to the preprocessor -XlinkerPass on to the linker -save-temps Do not delete intermediate files -pipeUse pipes rather than intermediate files -timeTime the execution of each subprocess -specs=Override built-in specs with the contents of -std= Assume that the input sources are for -BAdd to the compiler's search paths -b Run gcc for target , if installed -V Run gcc version number , if installed -v Display the programs invoked by the compiler -### Like -v but options quoted and commands not executed -E Preprocess only; do not compile, assemble or link -S Compile only; do not assemble or link -c Compile and assemble, but do not link -o Place the output into -x Specify the language of the following input files Permissible languages include: c c++ assembler none 'none' means revert to the default behavior of guessing the language based on the file's extension Options starting with -g, -f, -m, -O, -W, or --param are automatically passed on to the various sub-processes invoked by gcc.exe. In order to pass other options on to these processes the -W options must be used. For bug reporting instructions, please see: http://www.mingw.org/bugs.shtml>. GRASS 6.4> best regards Helmut ___ GRATIS: Spider-Man 1-3 sowie 300 weitere Videos! Jetzt kostenlose Movie-FLAT freischalten! http://movieflat.web.de smime.p7s Description: S/MIME Cryptographic Signature ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Re: First time trying to install add on g.extension (r.stream.order)
> note g.extension is rather new and untested compared the rest of > the software, especially on Windows. Besides svn for building C > modules, you will need a C compiler which doesn't ship with the > GRASS installer. What about a automtaci build process on the server? Then the users would download a "package" and drop in a extension directory or use g.extension for that task. I mean something similar to Launchpad PPA or PyPi. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
