[GRASS-user] FYI - python eclipse ubuntu
Hello, Just reporting I got the using eclipse to develop GRASS Python programs directions to work in Ubuntu 9.10. http://grass.osgeo.org/wiki/Using_Eclipse_to_develop_GRASS_Python_programs But I had to use grass65 to get it to work. (don't know why) Both the binary Grass64 and svn Grass64 just would not work. Thats it, Matthew _ Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Compare GRASS versions
Thanks Markus So the main reason for still supporting GRASS 6.4 is its stability right? For instance, do you plan to launch 6.5 as a end-product? Thanks Jenny 6.4 and 6.5 are rather close, 7 is starting to deviate. What I need to know is if there is any document that compares and assesses these 3 versions in order to characterizes each one. To my knowledge there is none. The Wiki would be the right place to start it. For instance GRASS6.5 is able to have dynamic wxpython scripts (e.g. v.krige) that is an interesting funcionality. Yes - but for stability reasons (in case you need it in production), you may consider 6.4. If functionality is missing and available in later versions, it could be discussed to backport it for 6.4.1 if not too complicated. Otherwise, take the next higher version number. Markus ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Compare GRASS versions
Hi, 2010/4/26 Jenny Turner jennyturner1...@gmail.com: Thanks Markus So the main reason for still supporting GRASS 6.4 is its stability right? For instance, do you plan to launch 6.5 as a end-product? I think that GRASS 6.5 probably will be released (as technical preview) - some enhancements, and mainly improved wxGUI. wxGUI in 6.4 is frozen for few months, wxGUI from 6.5 is still synchronized with GRASS 7.0 wxGUI. But it doesn't mean that there will be 6.6 as stable version. The related question is when GRASS 7.0 will be out (one/two years?) Martin -- Martin Landa landa.martin gmail.com * http://gama.fsv.cvut.cz/~landa ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.in.wms / Wheregroup OSM WMS
Peter wrote: I`m trying to access a WMS service for european OSM data (german link: http://www.wheregroup.com/de/freier_wms_mit_openstreetmap_daten) in GRASS 6.4 with r.in.wms in an EXPSG4326 location r.in.wms --o v=5 layers=Wald mapserver=http://osm.wheregroup.com/cgi-bin/osm_basic.xml output=Wald (please use the r.in.wms -c flag while debugging) This produces this error message by r.in.wms: ERROR 4: `/shazzam/locations/wms_download/Wald__0.geotiff' not recognised as a supported file format. ERROR: r.in.gdalwarp: gdalwarp failure. The error message is justified, as the content of Wald__0.geotiff is actually XML, not a geotiff: for me + multiple versions of Debian, the xml is correctly noticed and is displayed to the screen instead of written as a .tif. the test in the grass 6 version is: if [ `file -b $FILES | grep -c ^HTML\|^XML` -eq 1 ] ; then what does this say: file -b really_a_xml.tif ? `file` is not highly portable, better ways to test it welcome. ?xml version=1.0 encoding=ISO-8859-1? ows:ExceptionReport xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:ows=http://www.opengis.net/ows/1.1; version=1.1.1 xml:lang=en-US xsi:schemaLocation=http://www.opengis.net/ows/1.1 http://schemas.opengis.net/ows/1.1.0/owsExceptionReport.xsd; ows:Exception exceptionCode=service locator=MissingParameterValue ows:ExceptionTextmsWFSDispatch(): WFS server error. Incomplete WFS request: SERVICE parameter missing/ows:ExceptionText /ows:Exception /ows:ExceptionReport notice it says _WFS_ server error not _WMS_ server error. I expect the wheregroup people are reading the OSM (vector) data from a WFS server, rendering it with Osmarender or Mapnik on-the-fly, then WMS'ing the rasterized result. and the problem is between them and their OSM vector source. ??, Hamish ps- for lots of Blue Marble you might as well download the large binary grids. ~ 1.4gb for the whole world. or use r.in.onearth WMS frontend from wiki addons. look on the Global datasets page in the wiki. (currently stalled) ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] GRASS rasterformat supported by GDAL
Greetings As far as I know GDAL supports GRASS raster format. So, I wanted to get some information regarding a specific Raster using GDALINFO so I decided to test it with nc_spm_08/landsat dataset. But I really don't know in which sub-folder I shoudl run gdalinfo lsat7_2000_10 file. And another thing: I'm testing another tool that, it supposes to support GRASS but I need to send them a sample of GRASS raster file. Which file, from which sub-folder, I should send to them? Thanks Franz ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Compare GRASS versions
Jenny: So the main reason for still supporting GRASS 6.4 is its stability right? still? we haven't even released it yet! :) For instance, do you plan to launch 6.5 as a end-product? Martin: I think that GRASS 6.5 probably will be released (as technical preview) At this time my 2c would rather discourage considering that for another year. (fwiw I am not very excited about releasing binary snapshots of the development versions either) - some enhancements, and mainly improved wxGUI. wxGUI in 6.4 is frozen for few months, wxGUI from 6.5 is still synchronized with GRASS 7.0 wxGUI. so let's backport the best of the updated GUI for 6.4.1 ... although I am not at all in favour of backporting changes en masse. But it doesn't mean that there will be 6.6 as stable version. The related question is when GRASS 7.0 will be out (one/two years?) please let's concentrate our efforts on 1 very stable version, 1 development version, and 1 backporting sandbox for testing. otherwise new development effort remains unfocused and slow and grass 7.0 takes 2 years instead of 2 years. cheers, Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] GRASS rasterformat supported by GDAL
Franz wrote: As far as I know GDAL supports GRASS raster format. So, I wanted to get some information regarding a specific Raster using GDALINFO so I decided to test it with nc_spm_08/landsat dataset. But I really don't know in which sub-folder I shoudl run gdalinfo lsat7_2000_10 file. see http://www.gdal.org/frmt_grass.html (once the server comes back up) And another thing: I'm testing another tool that, it supposes to support GRASS but I need to send them a sample of GRASS raster file. Which file, from which sub-folder, I should send to them?Thanks try pointing them to the NC or Spearfish sample datasets. Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] $PATH for External executable files
Greetings I have a few external executable files that I want to call from GRASS Python. 1) Where should I place them in order to call them 2) Where/How can i define the path to those files/executables Thanks Gilbert ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Odd scaling issue with ps.map output and ghostscript ps2pdf
On several occasions I've created maps with ps.map at 1:24000 scale, converted to PDF form with ghostscript's ps2pdf script, and sent them off to a printer (i.e. paid a shop to print them) only to find that they've come back in 1:25000 scale instead. The first time this happened was after I'd imported the PDF into Inkscape to clean up labels, so I attributed it to Inkscape. This time, however, I cleverly avoided using Inkscape to monkey with the map, and found it came back to me in 1:25000 again anyway. And when I investigated, found that the PDF file was indeed shrunk from the PostScript --- when I viewed on screen at 1:1 scale, I found that my 1:24000 UTM interpolator worked great with the on-screen postscript file, but I needed to create a 1:25000 interpolator for the PDF version of the same file. I'm really puzzled how this can happen, and am guessing that somehow ghostscript is using a different DPI to create the PDF file than it should. Has anyone else ever seen this odd behavior? I'd really like to understand it and avoid it again. For both delivering to a print shop and for importing to Inkscape, PDF format is better than PostScript, so I'm really keen to fix this problem. For those who want a look, the map in question is temporarily available in both PDF and PostScript versions at ftp://ftp.swcp.com/pub/tmp/russo/. The files at that ftp site are automatically deleted after 4 days, though. Can anyone suggest a way around this scaling of the map by ghostscript? Or point me to a reason it should be happening? -- Tom RussoKM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236http://kevan.org/brain.cgi?DDTNM It is better to live on your feet than to die with your knees. -- Mil Millington on running, in Instructions for Living Someone Else's Life ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r.in.wms / Wheregroup OSM WMS
Peter wrote: I`m trying to access a WMS service for european OSM data (german link: http://www.wheregroup.com/de/freier_wms_mit_openstreetmap_daten) in GRASS 6.4 with r.in.wms in an EXPSG4326 location r.in.wms --o v=5 layers=Wald mapserver=http://osm.wheregroup.com/cgi-bin/osm_basic.xml output=Wald [...] Hamish: I expect the wheregroup people are reading the OSM (vector) data from a WFS server, rendering it with Osmarender or Mapnik on-the-fly, then WMS'ing the rasterized result. and the problem is between them and their OSM vector source. This has been confirmed: There are pecularities regarding the WMS. Thanks for the support, Hamish ! I guess r.in.wms would benefit from improved error checking in the future, as otherwise similar WMS-related postings might appear again and again on the list. Peter ??, Hamish ps- for lots of Blue Marble you might as well download the large binary grids. ~ 1.4gb for the whole world. or use r.in.onearth WMS frontend from wiki addons. look on the Global datasets page in the wiki. (currently stalled) -- Dr. Peter Löwe peter.lo...@gmx.de GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
