Re: [GRASS-dev] Grass to postgis topology export performance

2014-04-02 Thread Rémi Cura
Hey,
thanks for your answer.

I uploaded a new test file of about the same number of line (32k),
also already topological (meaning in theory there is no need to split line,
just compute node, neighbourhood, and faces).

It is here : http://trac.osgeo.org/postgis/ticket/2695

About the command I used, I followed the wiki page on grass, I tried both
suggested methods:
I issued those with grass 7 svn, on windows, using the GUI to have a
terminal.

As I stated grass is extremely fast to build topology, and then the export
to postgis topology is already faster than using pure postgis topology, but
yet surprisingly slow compared to the grass internal.


v.in.ogr dsn=PG:host=localhost port=5433 dbname=street_gen user=postgres
password=?? layer=bdtopo.route out=test_postgis_import
v.out.postgis -l -2 input=route@T051 dsn=PG:host=localhost
dbname=street_gen port=5433 user=postgres password=?? olayer=test_layer -t



v.external.out dsn=PG:host=localhost dbname=street_gen port=5433
user=postgres password=?? options=topology=yes format=PostgreSQL
v.in.ogr dsn=\route_utf8.shp -t


Cheers,
Rémi-C


2014-04-01 13:42 GMT+02:00 Martin Landa landa.mar...@gmail.com:

 Hi,

 2014-04-01 11:43 GMT+02:00 Rémi Cura remi.c...@gmail.com:

  Grass GIS is very fast to construct a topology over vectors (5 secs), and
  then surprisingly slow in exporting this model to Postgis topology (145
  sec).
 
  Is there a perticular reason for this? I tried to read the code, but
  couldn't get to the sql querries.
 
  Also, in a more prospective way, could Grass import from geometry
 (shapefile
  for example) then export to postgis topology be isolated (into an exe or
 a
  lib?).

 could you post exact commands you run, or some sample data to play
 with. Thanks, Martin

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Addons to Ohloh

2014-04-02 Thread Markus Neteler
On Wed, Apr 2, 2014 at 4:24 AM, Vaclav Petras wenzesl...@gmail.com wrote:

 On Mon, Mar 31, 2014 at 4:06 AM, Luca Delucchi lucadel...@gmail.com wrote:

  GRASS GIS Addons can be added as additional repository for GRASS GIS
  project
  or they can be a separated project at Ohloh. Some projects went this way
  of
  having plugins/extension/addons separated. The reasons for this might be
  that the developers group, used languages or contribution frequency can
  be
  really different. What do you think? Or do you know some other ways on
  Ohloh? (I don't know much about Ohloh.)
 

 I'd like to see it separated from the main code


 Any other opinions?

 The name would be probably GRASS GIS Addons. Although, we have some
 uncertainty about extension/addon/module/... terminology.

 What is the best way to connect two projects together? Homepage link, tags
 or just text?

I can check if I can link it as subproject to the existing GRASS registration.

Markus

 ___
 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


[GRASS-dev] compiling 7.0 on MacOS 10.9

2014-04-02 Thread Micha Silver

  
  
Has anyone compiled GRASS 7.0 on MacOS Mavricks? Any
  tips?
  Thanks,
  

-- 
Micha Silver
GIS Consulting
052-3665918
http://www.surfaces.co.il

  

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] compiling 7.0 on MacOS 10.9

2014-04-02 Thread epi
Micha,

i use homebrew to satisfy the dependencies for grass7 

./configure  \
--with-opengl-includes=/opt/X11/include/ \
--with-opengl-libs=/opt/X11/lib/ \
--with-cairo-includes=/usr/local/Cellar/cairo/1.12.16/include/cairo/ \
--with-cairo-libs=/usr/local/Cellar/cairo/1.12.16/lib/ \
--with-freetype-includes=/usr/local/include/freetype2 \
--with-blas \
--with-geos \
--with-lapack \
--with-netcdf \
--with-odbc \
--with-pthread \
--with-postgres \
--with-sqlite \
--with-wxwidgets=/usr/local/Cellar/wxmac/3.0.0.0/bin/wx-config 

the build ends with Errors in:
/Users/epi/dev/grass7_trunk/lib/nviz
/Users/epi/dev/grass7_trunk/misc/m.nviz.image
/Users/epi/dev/grass7_trunk/visualization/wximgview

The modules are all fully functionals but because i use python from home-brew 
as well (not the system one)
it is 64 bit and is not compatible with wx-2.8 … i have wx3.0 installed (that’s 
64bit) but the main gui doesn’t start. 
This the log from :

 g.gui gui=wxpython

Launching wxpython GUI in the background, please wait...
GRASS 7.0.svn (nc_spm_08_grass7):~  Traceback (most recent call last):
  File /usr/local/grass-7.0.svn/etc/gui/wxpython/wxgui.py, line 143, in 
module
sys.exit(main())
  File /usr/local/grass-7.0.svn/etc/gui/wxpython/wxgui.py, line 136, in main
app = GMApp(workspaceFile)
  File /usr/local/grass-7.0.svn/etc/gui/wxpython/wxgui.py, line 50, in 
__init__
wx.App.__init__(self, False)
  File 
/usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/wx-3.0-osx_cocoa/wx/_core.py,
 line 8631, in __init__
self._BootstrapApp()
  File 
/usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/wx-3.0-osx_cocoa/wx/_core.py,
 line 8196, in _BootstrapApp
return _core_.PyApp__BootstrapApp(*args, **kwargs)
  File /usr/local/grass-7.0.svn/etc/gui/wxpython/wxgui.py, line 84, in OnInit
workspace = self.workspaceFile)
  File /usr/local/grass-7.0.svn/etc/gui/wxpython/lmgr/frame.py, line 109, in 
__init__
self._menuTreeBuilder = LayerManagerMenuData()
  File /usr/local/grass-7.0.svn/etc/gui/wxpython/lmgr/menudata.py, line 40, 
in __init__
MenuTreeModelBuilder.__init__(self, filename, expandAddons=expandAddons)
  File /usr/local/grass-7.0.svn/etc/gui/wxpython/core/menutree.py, line 69, 
in __init__
xmlTree = etree.parse(filename)
  File 
/usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py,
 line 1182, in parse
tree.parse(source, parser)
  File 
/usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py,
 line 657, in parse
self._root = parser.close()
  File 
/usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py,
 line 1654, in close
self._raiseerror(v)
  File 
/usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py,
 line 1506, in _raiseerror
raise err
xml.etree.ElementTree.ParseError: no element found: line 1, column 0


the wx dialog for (most but not all **) the grass modules, works fine.
** command like g.region, r.mask and others do not lunch a gui dialog when type 
their name in the grass shell.

Massimo.

On Apr 2, 2014, at 9:48 AM, Micha Silver mi...@arava.co.il wrote:

 Has anyone compiled GRASS 7.0 on MacOS Mavricks? Any tips?
 Thanks,
 
 -- 
 Micha Silver
 GIS Consulting
 052-3665918
 http://www.surfaces.co.il
 ___
 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

[GRASS-dev] G7.trunk: r.colors color list wxpython issue

2014-04-02 Thread Markus Neteler
Hi,

some recent change in trunk (didn't find which) broke the color list
generator in r.colors:

Traceback (most recent call last):
  File /home/neteler/software/grass71/dist.x86_64-unknown-
linux-gnu/etc/gui/wxpython/gui_core/widgets.py, line 1294,
in OnDrawItem

r.x + bitmap.GetWidth() + 10,
AttributeError
:
'NoneType' object has no attribute 'GetWidth'
Traceback (most recent call last):
  File /home/neteler/software/grass71/dist.x86_64-unknown-
linux-gnu/etc/gui/wxpython/gui_core/widgets.py, line 1294,
in OnDrawItem

r.x + bitmap.GetWidth() + 10,
AttributeError

[...]
:
'NoneType' object has no attribute 'GetWidth'
Traceback (most recent call last):
  File /home/neteler/software/grass71/dist.x86_64-unknown-
linux-gnu/etc/gui/wxpython/gui_core/widgets.py, line 1294,
in OnDrawItem

r.x + bitmap.GetWidth() + 10,
AttributeError
:
'NoneType' object has no attribute 'GetWidth'

Using:
g.version -g
version=7.1.svn
date=2014
revision=59549M
build_date=2014-04-02
build_platform=x86_64-unknown-linux-gnu

A fix would be appreciated. In relbranch70 is seems to work fine.

thanks
Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] G7.trunk: r.colors color list wxpython issue

2014-04-02 Thread Anna Petrášová
On Wed, Apr 2, 2014 at 5:56 AM, Markus Neteler nete...@osgeo.org wrote:

 Hi,

 some recent change in trunk (didn't find which) broke the color list
 generator in r.colors:


hmm, it works for me. But I remember, it happened to me some time ago but
then it started to work again. It looks like it can't find the thumbnails.
I fixed it to display at least the name of the color table when it can't
find the picture for whatever reason.


Anna


 Traceback (most recent call last):
   File /home/neteler/software/grass71/dist.x86_64-unknown-
 linux-gnu/etc/gui/wxpython/gui_core/widgets.py, line 1294,
 in OnDrawItem

 r.x + bitmap.GetWidth() + 10,
 AttributeError
 :
 'NoneType' object has no attribute 'GetWidth'
 Traceback (most recent call last):
   File /home/neteler/software/grass71/dist.x86_64-unknown-
 linux-gnu/etc/gui/wxpython/gui_core/widgets.py, line 1294,
 in OnDrawItem

 r.x + bitmap.GetWidth() + 10,
 AttributeError

 [...]
 :
 'NoneType' object has no attribute 'GetWidth'
 Traceback (most recent call last):
   File /home/neteler/software/grass71/dist.x86_64-unknown-
 linux-gnu/etc/gui/wxpython/gui_core/widgets.py, line 1294,
 in OnDrawItem

 r.x + bitmap.GetWidth() + 10,
 AttributeError
 :
 'NoneType' object has no attribute 'GetWidth'

 Using:
 g.version -g
 version=7.1.svn
 date=2014
 revision=59549M
 build_date=2014-04-02
 build_platform=x86_64-unknown-linux-gnu

 A fix would be appreciated. In relbranch70 is seems to work fine.

 thanks
 Markus

 ___
 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] compiling 7.0 on MacOS 10.9

2014-04-02 Thread Vaclav Petras
On Wed, Apr 2, 2014 at 4:37 AM, epi massimodisa...@gmail.com wrote:


 the build ends with Errors in:
 /Users/epi/dev/grass7_trunk/lib/nviz
 /Users/epi/dev/grass7_trunk/misc/m.nviz.image


This looks like a problem to link OpenGL.


 /Users/epi/dev/grass7_trunk/visualization/wximgview

 This looks like a problem to link wxWidgets (the C++ library, not the
Python binding wxPython).


 The modules are all fully functionals but because i use python from
 home-brew as well (not the system one)
 it is 64 bit and is not compatible with wx-2.8 … i have wx3.0 installed
 (that’s 64bit) but the main gui doesn’t start.
 This the log from :

  g.gui gui=wxpython

 Launching wxpython GUI in the background, please wait...
 GRASS 7.0.svn (nc_spm_08_grass7):~  Traceback (most recent call last):
   File /usr/local/grass-7.0.svn/etc/gui/wxpython/wxgui.py, line 143, in
 module
 ...
 self._menuTreeBuilder = LayerManagerMenuData()
   File /usr/local/grass-7.0.svn/etc/gui/wxpython/lmgr/menudata.py, line
 40, in __init__
 MenuTreeModelBuilder.__init__(self, filename,
 expandAddons=expandAddons)
   File /usr/local/grass-7.0.svn/etc/gui/wxpython/core/menutree.py, line
 69, in __init__
 xmlTree = etree.parse(filename)
   ...
   File
 /usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py,
 line 1506, in _raiseerror
 raise err
 xml.etree.ElementTree.ParseError: no element found: line 1, column 0

 This is probably caused by the fact that compilation for gui/wxpython/xml
failed. I secretly hoped that this will be improved by r59485, are you
using that version? The workaround used before was delete
dist.../etc/gui/wxpython/xml and then run compilation of gui/wxpython
inside GRASS session.

https://trac.osgeo.org/grass/changeset/59485 (modify Rules.make to fix
build_modules_xml.py on Windows (TODO: replace this workaround))
http://lists.osgeo.org/pipermail/grass-dev/2014-March/067876.html (get
interface description for python modules on Windows)


 the wx dialog for (most but not all **) the grass modules, works fine.

 ** command like g.region, r.mask and others do not lunch a gui dialog when
 type their name in the grass shell.

 This is actually standard behavior. Probably not documented well. This is
how g.region parameters are handled. Use `g.region --ui`.


 Massimo.

 On Apr 2, 2014, at 9:48 AM, Micha Silver mi...@arava.co.il wrote:

  Has anyone compiled GRASS 7.0 on MacOS Mavricks? Any tips?
 Thanks,

 --
 Micha Silver
 GIS Consulting
 052-3665918http://www.surfaces.co.il

 ___
 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

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] get interface description for python modules on Windows

2014-04-02 Thread Vaclav Petras
For the record:

r59485
modify Rules.make to fix build_modules_xml.py on Windows (TODO: replace
this workaround)
https://trac.osgeo.org/grass/changeset/59485



On Wed, Mar 26, 2014 at 4:47 PM, Vaclav Petras wenzesl...@gmail.com wrote:

 Thanks, your analyses seems very deep. It would be incredibly useful if
 somebody would solve this issue since it might fix also compilation on some
 Macs (#1819), for Ubuntu PPA and some other less usual configurations.

 Vaclav

 https://trac.osgeo.org/grass/ticket/1819


 On Tue, Mar 25, 2014 at 2:54 PM, Martin Landa landa.mar...@gmail.comwrote:

 Hi,

 I am trying to fix `build_modules_xml.py` to produces description also
 for Python modules. The problem is the failure in grass.script's
 get_interface_description() [1] caused by two issues. When running the
 script from Makefile [2], the PATHEXT variable can miss '.py'
 extension (for running session it's set up by grass.py [3]. I have
 fixed this issue in r59338.

 The _remaining_ issue is related to Makefiles. Strangely the rule [4]
 produces _doubled_ PATH, on Windows it's cased by LD_LIBRARY_PATH
 which overwrites manually defined PATH:


 GISRC=/c/osgeo4w/usr/src/grass_trunk/dist.i686-pc-mingw32/demolocation/.grassrc70
 GISBASE=c:/osgeo4w/usr/src/grass_trunk/dist.i686-pc-mingw32
 --
 PATH=/c/osgeo4w/usr/src/grass_trunk/dist.i686-pc-mingw32/bin:/c/osgeo4w/usr/src/grass_trunk/dist.i686-pc-mingw32/bin:/c/osgeo4w/usr/src/grass_trunk/dist.i686-pc-mingw32/scripts:
 $PATH

 PYTHONPATH=c:/osgeo4w/usr/src/grass_trunk/dist.i686-pc-mingw32/etc/python;c:/osgeo4w/usr/src/grass_trunk/dist.i686-pc-mingw32/etc/python;$PYTHONPATH
 --
 PATH=/c/osgeo4w/usr/src/grass_trunk/dist.i686-pc-mingw32/bin:/c/osgeo4w/usr/src/grass_trunk/dist.i686-pc-mingw32/scripts:/c/osgeo4w/usr/src/grass_trunk/dist.i686

 -pc-mingw32/lib:/c/osgeo4w/usr/src/grass_trunk/dist.i686-pc-mingw32/lib:.:/usr/local/bin:/mingw/bin:/bin:/osgeo4w/bin:/c/Windows/system32:/c/Windows:/c/Windows/
 WBem:/usr/bin:/osgeo4w/apps/Python27/Scripts
 LC_ALL=C python tools/build_modules_xml.py 
 /c/osgeo4w/usr/src/grass_trunk/dist.i686-pc-mingw32/etc/gui/wxpython/

 The result is that `$GISBASE/scripts` is not in the path and
 get_interface() fails. Does anybody have an idea how to correctly fix
 `run_grass` rule. If I add `$GISBASE/scripts` to LD_LIBRARY_PATH
 manually, it starts to work.

 Thanks for any idea in advance, Martin

 [1]
 http://trac.osgeo.org/grass/browser/grass/trunk/lib/python/script/task.py#L455
 [2]
 http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/Makefile#L53
 [3]
 http://trac.osgeo.org/grass/browser/grass/trunk/lib/init/grass.py#L418
 [4]
 http://trac.osgeo.org/grass/browser/grass/trunk/include/Make/Rules.make#L33

 --
 Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa
 ___
 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

[GRASS-dev] Planetary Datums help to add in GRASS

2014-04-02 Thread Yann Chemin
Hi,

I would like to add planetary Datums in GRASS as from this:
http://help.arcgis.com/en/arcims/10.0/mainhelp/mergedprojects/ArcXMLGuide/elements/gcs.htm#104900and
after

Right now GRASS issues a benign warning on importing LOLA DEM:

WARNING: Datum Moon_2000 not recognised by GRASS and no parameters found

This kind of information is in the URL:
104900 GCS_Mercury_2000
GEOGCS[GCS_Mercury_2000,DATUM[D_Mercury_2000,SPHEROID[Mercury_2000_IAU_IAG,2439700.0,0.0]],PRIMEM[Reference_Meridian,0.0],UNIT[Degree,0.0174532925199433]]

104901 GCS_Venus_1985
GEOGCS[GCS_Venus_1985,DATUM[D_Venus_1985,SPHEROID[Venus_1985_IAU_IAG_COSPAR,6051000.0,0.0]],PRIMEM[Reference_Meridian,0.0],UNIT[Degree,0.0174532925199433]]

104902 GCS_Venus_2000
GEOGCS[GCS_Venus_2000,DATUM[D_Venus_2000,SPHEROID[Venus_2000_IAU_IAG,6051800.0,0.0]],PRIMEM[Reference_Meridian,0.0],UNIT[Degree,0.0174532925199433]]

104903 GCS_Moon_2000
GEOGCS[GCS_Moon_2000,DATUM[D_Moon_2000,SPHEROID[Moon_2000_IAU_IAG,1737400.0,0.0]],PRIMEM[Reference_Meridian,0.0],UNIT[Degree,0.0174532925199433]]

104904 GCS_Mars_1979
GEOGCS[GCS_Mars_1979,DATUM[D_Mars_1979,SPHEROID[Mars_1979_IAU_IAG,3393400.0,192.0430107526882]],PRIMEM[Reference_Meridian,0.0],UNIT[Degree,0.0174532925199433]]

104905 GCS_Mars_2000
GEOGCS[GCS_Mars_2000,DATUM[D_Mars_2000,SPHEROID[Mars_2000_IAU_IAG,3396190.0,169.8944472236118]],PRIMEM[Reference_Meridian,0.0],UNIT[Degree,0.0174532925199433]]


Any hint would be great thanks,
Yann
-- 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] compiling 7.0 on MacOS 10.9

2014-04-02 Thread epi

On Apr 2, 2014, at 4:10 PM, Vaclav Petras wenzesl...@gmail.com wrote:

 
 On Wed, Apr 2, 2014 at 4:37 AM, epi massimodisa...@gmail.com wrote:
 
 the build ends with Errors in:
 /Users/epi/dev/grass7_trunk/lib/nviz
 /Users/epi/dev/grass7_trunk/misc/m.nviz.image
 
 This looks like a problem to link OpenGL.
  

That’s correct, for some reason seems that it doesn’t detect the right 
architecture :


###
MacBook-Pro-di-Massimo-2:nviz epi$ make
cc -dynamiclib -compatibility_version 7.1 -current_version 7.1 -install_name 
/usr/local/grass-7.1.svn/lib/libgrass_nviz.7.1.svn.dylib -o 
/Users/epi/dev/grass7_trunk/dist.x86_64-apple-darwin13.1.0/lib/libgrass_nviz.7.1.svn.dylib
 -L/Users/epi/dev/grass7_trunk/dist.x86_64-apple-darwin13.1.0/lib 
-L/Users/epi/dev/grass7_trunk/dist.x86_64-apple-darwin13.1.0/lib 
-L/usr/local/opt/tcl-tk/lib  -arch x86_64
OBJ.x86_64-apple-darwin13.1.0/change_view.o 
OBJ.x86_64-apple-darwin13.1.0/cplanes_obj.o 
OBJ.x86_64-apple-darwin13.1.0/draw.o OBJ.x86_64-apple-darwin13.1.0/exag.o 
OBJ.x86_64-apple-darwin13.1.0/lights.o OBJ.x86_64-apple-darwin13.1.0/map_obj.o 
OBJ.x86_64-apple-darwin13.1.0/nviz.o OBJ.x86_64-apple-darwin13.1.0/position.o 
OBJ.x86_64-apple-darwin13.1.0/render.o  -lgrass_ogsf.7.1.svn 
-lgrass_gis.7.1.svn -L/opt/X11/lib/  -lGL 
Undefined symbols for architecture x86_64:
  _XCloseDisplay, referenced from:
  _Nviz_destroy_render_window in render.o
  _XCreatePixmap, referenced from:
  _Nviz_create_render_window in render.o
  _XFree, referenced from:
  _Nviz_create_render_window in render.o
  _XFreePixmap, referenced from:
  _Nviz_destroy_render_window in render.o
  _XOpenDisplay, referenced from:
  _Nviz_create_render_window in render.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** 
[/Users/epi/dev/grass7_trunk/dist.x86_64-apple-darwin13.1.0/lib/libgrass_nviz.7.1.svn.dylib]
 Error 1
###

MacBook-Pro-di-Massimo-2:~ epi$ file /opt/X11/lib/libGL.dylib
/opt/X11/lib/libGL.dylib: Mach-O universal binary with 2 architectures
/opt/X11/lib/libGL.dylib (for architecture i386):   Mach-O dynamically 
linked shared library i386
/opt/X11/lib/libGL.dylib (for architecture x86_64): Mach-O 64-bit 
dynamically linked shared library x86_64


 /Users/epi/dev/grass7_trunk/visualization/wximgview
 
 This looks like a problem to link wxWidgets (the C++ library, not the Python 
 binding wxPython).


i fixed this adding a sim. link in use/local

ln -s /usr/local/Cellar/wxmac/3.0.0.0/lib/libwx_osx_cocoau-3.0.0.0.0.dylib 
/usr/local/lib/


  
 The modules are all fully functionals but because i use python from home-brew 
 as well (not the system one)
 it is 64 bit and is not compatible with wx-2.8 … i have wx3.0 installed 
 (that’s 64bit) but the main gui doesn’t start. 
 This the log from :
 
  g.gui gui=wxpython
 
 Launching wxpython GUI in the background, please wait...
 GRASS 7.0.svn (nc_spm_08_grass7):~  Traceback (most recent call last):
   File /usr/local/grass-7.0.svn/etc/gui/wxpython/wxgui.py, line 143, in 
 module
 ...
 self._menuTreeBuilder = LayerManagerMenuData()
   File /usr/local/grass-7.0.svn/etc/gui/wxpython/lmgr/menudata.py, line 40, 
 in __init__
 MenuTreeModelBuilder.__init__(self, filename, expandAddons=expandAddons)
   File /usr/local/grass-7.0.svn/etc/gui/wxpython/core/menutree.py, line 69, 
 in __init__
 xmlTree = etree.parse(filename)
   ...
   File 
 /usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py,
  line 1506, in _raiseerror
 raise err
 xml.etree.ElementTree.ParseError: no element found: line 1, column 0
 
 This is probably caused by the fact that compilation for gui/wxpython/xml 
 failed. I secretly hoped that this will be improved by r59485, are you using 
 that version? The workaround used before was delete 
 dist.../etc/gui/wxpython/xml and then run compilation of gui/wxpython inside 
 GRASS session.
 

thanks! i followed this procedure, now the gui starts :) and it is usable.

a problem witth Wx font already reported previously :

http://lists.osgeo.org/pipermail/grass-dev/2013-December/066536.html

is still here, i have this log printed in the shell all the time i use the gui :

2014-04-02 23:31:51.720 Python[78021:d07] CoreText performance note: Client 
called CTFontCreateWithName() using name .Lucida Grande UI and got font with 
PostScript name .LucidaGrandeUI. For best performance, only use PostScript 
names when calling this API.



i know it is a known problem,
http://forums.wxwidgets.org/viewtopic.php?f=23t=38311
 i hoped it was a 2.9 bug … while it still here with wx3.0


 https://trac.osgeo.org/grass/changeset/59485 (modify Rules.make to fix 
 build_modules_xml.py on Windows (TODO: replace this workaround))
 http://lists.osgeo.org/pipermail/grass-dev/2014-March/067876.html (get 
 interface description for python modules on Windows)
 
 
  the wx dialog for 

[GRASS-dev] manual pages: trac new modules/params/flags

2014-04-02 Thread Martin Landa
Hi all,

it would make sense to add to the modules manual pages information in
which version the module has been introduced. We can start with
r.streams.* modules which were added recently to trunk/relbr70. It
would be also nice to track newly added parameters or flags.

There are several options, one of them is a new h2 section, eg.

h2Find a nice name for new section/h2

Module emr.mymodule/em added in GRASS 7.0.

ul
liParameter bnewparam/b added in GRASS 7.1.
/ul

What do you think? Martin

-- 
Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev


Re: [GRASS-dev] Planetary Datums help to add in GRASS

2014-04-02 Thread Yann Chemin
Hi Alessandro,

I updated the planetary Ellipsoid table (r59566) with the definitions from
the website.

Cheers,
Yann


On 2 April 2014 23:27, Alessandro Frigeri
alessandro.frig...@iaps.inaf.itwrote:

 Hi Yann,

 maybe the name of the ellipse/datum fund in LOLA metadata does not match
 the name found in the ellipse.table
 http://svn.osgeo.org/grass/grass/trunk/lib/gis/ellipse.table.solar.system?


 I'm out of office now, I will check tomorrow

 Best,

 Alessandro





 2014-04-02 17:23 GMT+02:00 Yann Chemin yche...@gmail.com:

 Hi,

 I would like to add planetary Datums in GRASS as from this:

 http://help.arcgis.com/en/arcims/10.0/mainhelp/mergedprojects/ArcXMLGuide/elements/gcs.htm#104900and
  after

 Right now GRASS issues a benign warning on importing LOLA DEM:

 WARNING: Datum Moon_2000 not recognised by GRASS and no parameters found

 This kind of information is in the URL:
 104900 GCS_Mercury_2000

 GEOGCS[GCS_Mercury_2000,DATUM[D_Mercury_2000,SPHEROID[Mercury_2000_IAU_IAG,2439700.0,0.0]],PRIMEM[Reference_Meridian,0.0],UNIT[Degree,0.0174532925199433]]

 104901 GCS_Venus_1985

 GEOGCS[GCS_Venus_1985,DATUM[D_Venus_1985,SPHEROID[Venus_1985_IAU_IAG_COSPAR,6051000.0,0.0]],PRIMEM[Reference_Meridian,0.0],UNIT[Degree,0.0174532925199433]]

 104902 GCS_Venus_2000

 GEOGCS[GCS_Venus_2000,DATUM[D_Venus_2000,SPHEROID[Venus_2000_IAU_IAG,6051800.0,0.0]],PRIMEM[Reference_Meridian,0.0],UNIT[Degree,0.0174532925199433]]

 104903 GCS_Moon_2000

 GEOGCS[GCS_Moon_2000,DATUM[D_Moon_2000,SPHEROID[Moon_2000_IAU_IAG,1737400.0,0.0]],PRIMEM[Reference_Meridian,0.0],UNIT[Degree,0.0174532925199433]]

 104904 GCS_Mars_1979

 GEOGCS[GCS_Mars_1979,DATUM[D_Mars_1979,SPHEROID[Mars_1979_IAU_IAG,3393400.0,192.0430107526882]],PRIMEM[Reference_Meridian,0.0],UNIT[Degree,0.0174532925199433]]

 104905 GCS_Mars_2000
 GEOGCS[GCS_Mars_2000,DATUM[D_Mars_2000,SPHEROID[Mars_2000_IAU_IAG,3396190.0,169.8944472236118]],PRIMEM[Reference_Meridian,0.0],UNIT[Degree,0.0174532925199433]]


 Any hint would be great thanks,
 Yann
 --
 




 --
 Alessandro Frigeri
 Istituto di Astrofisica e Planetologia Spaziali - Istituto Nazionale di
 Astrofisica, Roma, Italy




-- 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev