Re: [GRASS-dev] r54612 - grass/trunk/mswindows - wingrass: attempt to define python file association
On Mon, Jan 14, 2013 at 10:45 PM, Martin Landa landa.mar...@gmail.com wrote: Hi Markus, 2013/1/14 Markus Metz markus.metz.gisw...@gmail.com: Currently the native installer contains python which is provided within osgeo4w framework (taken from python.org ASAR). The python version coming with osgeow4 or wingrass is not a Windows python, it is a msys python. Windows does not know about it. are you sure about it? See [1]. According to [1], the python files are first copied to a different location, then the(-core, -help, -wrapper packages are created. Windows does not know about it, what the osgeo4w user gets is not a system-wide Windows installation, python is only available within the osgeo4w msys environment. Markus M Martin [1] http://trac.osgeo.org/osgeo4w/wiki/pkg-python/Python27 -- Martin Landa landa.martin gmail.com * http://geo.fsv.cvut.cz/~landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [GRASS-PSC] ESA Summer of Code in Space
On 14/01/13 18:28, Luca Delucchi wrote: Hi Moritz 2013/1/14 Moritz Lennertmlenn...@club.worldonline.be: Just stumbled upon this: http://sophia.estec.esa.int/socis2012/ It is only open to students enrolled in European universities, but it might be an interesting addition to GSoC for developing remote sensing modules for GRASS. Yes, I think this is a good idea. This is the last year edition. Please look for update. I did, but couldn't find anything. I just subscribed to their mailing list so I'll get the news when the 2013 edition is launched. Moritz ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] r54612 - grass/trunk/mswindows - wingrass: attempt to define python file association
Markus Metz wrote: Hm, not sure. Esri ArcGIS contains also installation of Python. Esri ArcGIS installs system-wide a true Windows version of Python. Another possibility is to look at the way e.g. LibreOffice or Gimp install python on Windows (not system-wide). AFAIK, those packages only support Python scripting within the application. That's the easy case. A system-wide installation means that you can execute Python scripts from a command prompt, from batch files, with system(), subprocess.Popen(), etc, in the same way that you can execute batch files (CreateProcess() only works for binary executables, so scripts can never truly be first-class citizens on Windows). I found that problems go away if I install http://www.python.org/ftp/python/2.7.3/python-2.7.3.msi which is a true Windows system-wide installation. Right. But this isn't something which GRASS can do unconditionally. The user may already have a system-wide Python installation for other reasons, and blindly replacing it with a different version will break that. Also, if the user has a system-wide Python, any packages (e.g. wxPython, numpy, etc) have to match that specific version. In particular, if the user has Python 3.x, they are almost certainly going to require the Python launcher: http://docs.python.org/3/using/windows.html#launcher For this situation, GRASS can set PY_PYTHON in sthe environment to force a specific Python interpreter within a GRASS session. It *might* be feasible to bundle the launcher and, if necessary, forcibly associate the .py extension with the launcher. This could be acceptable provided that we can be sure that the existing behaviour is preserved for non-GRASS Python scripts. As a last resort, we might need to install Python scripts with a different extension (e.g. .gpy) to allow them to be associated with a specific Python interpreter without affecting other packages which use Python (e.g. ArcGIS). Note that we will be running into similar issues on Linux as some distributions start using Python 3.x for /usr/bin/python. But on Linux, the fix is much simpler: use #!/usr/bin/env python and put a symlink from $GISBASE/bin/python to any Python 2.x interpreter. -- Glynn Clements gl...@gclements.plus.com ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Strange import of .asc
Il 14/01/2013 20:17, Helmut Kudrnovsky ha scritto: yes - have you tired displaying it under the vector? yes, the newly imported raster and also your raster delivered with the location are aligned with the vector. I've also tested a raster link with r.external, this linked is also aligned to the vector. I get this strange artifact (both on GRASS and on QGIS GUIs), see attached (in red the vector derived from the imported raster, on the background the imported raster; the original one is perfectly aligned with the vector). I suppose as a consequence of this, querying values gives wrong results. Thanks a lot. -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario attachment: shot2013-01-15 10:24:33.png___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Strange import of .asc
Il 14/01/2013 20:17, Helmut Kudrnovsky ha scritto: yes - have you tired displaying it under the vector? yes, the newly imported raster and also your raster delivered with the location are aligned with the vector. I've also tested a raster link with r.external, this linked is also aligned to the vector. at other zoom levels, I get different misaligment, see attached -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario attachment: shot2.png___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Strange import of .asc
I get this strange artifact (both on GRASS and on QGIS GUIs) here on my side it's aligned, see attached screenshot (your vector and an imported raster of your asc-file). screenshot.png http://osgeo-org.1560.n6.nabble.com/file/n5027529/screenshot.png I suppose as a consequence of this, querying values gives wrong results. probably. which grass version are you using? here on my side wingrass6.4.3RC2. - best regards Helmut -- View this message in context: http://osgeo-org.1560.n6.nabble.com/Strange-import-of-asc-tp5027341p5027529.html Sent from the Grass - Dev mailing list archive at Nabble.com. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Strange import of .asc
Hi Paolo I have imported your layers in grass 6.4 and the vector and both the rasters (original and the asci after import) align perfectly well. I tried the same in grass 7.0, with the same result. Cheers, Paulo On 01/15/2013 10:43 AM, Paolo Cavallini wrote: Il 14/01/2013 20:17, Helmut Kudrnovsky ha scritto: yes - have you tired displaying it under the vector? yes, the newly imported raster and also your raster delivered with the location are aligned with the vector. I've also tested a raster link with r.external, this linked is also aligned to the vector. at other zoom levels, I get different misaligment, see attached ___ 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] Strange import of .asc
Il 15/01/2013 14:42, Paulo van Breugel ha scritto: Hi Paolo I have imported your layers in grass 6.4 and the vector and both the rasters (original and the asci after import) align perfectly well. I tried the same in grass 7.0, with the same result. Thanks a lot to both of you for checking. I have this issue both with 6.4.2 on Debian and (I suppose) 6.4.3RC2 from osgeo4w. Really puzzling. Ideas on wht to test? All the best. -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
