[GRASS-dev] Re: [GRASS GIS] #532: Vector editing not possible with wx tools

2010-03-03 Thread GRASS GIS
#532: Vector editing not possible with wx tools
--+-
  Reporter:  geognu1  |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  major|   Milestone:  6.4.0
 Component:  wxGUI| Version:  6.4.0 RCs
Resolution:   |Keywords:  vector, digit
  Platform:  All  | Cpu:  x86-32   
--+-
Comment (by neteler):

 Replying to [comment:16 neteler]:
  Replying to [comment:15 glynn]:
   Replying to [comment:14 neteler]:
  
Also for me it fails *since* RC5.
  
   With a 'wxversion' referenced before assignment error?
 
  It fails silently. Also when using 'g.gui wxpython': the old map
 flashed,
  then return to command line and nothing else.

 This problem has been solved: it was wxPythonGTK being compiled with
 '''internal'''
 expat support instead of --with-expat=sys. To verify:

 {{{
 ldd /usr/lib/wxPython/lib/libwx_gtk2u-2.8.so.0.5.0 | grep expat
 - no link to external libexpat as it should be
 }}}

 Recompilation of wxPythonGTK with --with-expat=sys solved this problem,
 wxGUI is now functional.

-- 
Ticket URL: http://trac.osgeo.org/grass/ticket/532#comment:22
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] future thematic cartography in GRASS [was: Re: [GRASS GIS] #974: [Patch] add option to d.vect to make symbol size proportionate to square root of size_column]

2010-03-03 Thread Hamish
Moritz wrote:
 What is still missing right now is an easy way to display a
 combination of color-classified and proportionately sized
 symbols. It is possible to declare an arbitrary numeric
 column as z-height and use that with zcolor, but I don't
 think this is very straightforward and even though ISTR you
 don't see the need for that, cartographic theory (at least
 for thematic maps) still calls for reduced numbers of
 classes.

The debate rages on whether class-splitting is a good idea or not.
2c In my personal opinion it is open to huge misleading abuse both
intentional and unintentional, and so I try to avoid it. Probably
even more so than the potential to abuse statistics because it also
plays tricks on your visual perceptions. For raster maps the best
compromise I know is to include continuous color maps with contour
lines over the top. For vector maps I don't know of a good compromise,
or even if one is possible. /2c

 However, if we go this way, I would need to add a flag to
 d.vect which allows sorting symbols with the largest in the
 back. This is absolutely necessary for readability. However,
 this implies a fundamental change in the d.vect code,

As this is just the beginning, I would prefer a new module for that
along the lines of d.vect.chart.

why not simplify the name to just d.thematic?


regards,
Hamish

ps- see also v.colors and the new extra/ring symbol



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


[GRASS-dev] svn: 41275 (Identation error in core.py?)

2010-03-03 Thread Pietro Zambelli
Hi all!

I try to compile grass7 from svn I reach this error:

GRASS GIS compilation log   


-   


Started compilation: Wed Mar  3 12:34:18 CET 2010   


--  


Errors in:  


/home/pietro/builds/grass70/src/grass70/lib/python  


/home/pietro/builds/grass70/src/grass70/scripts/d.vect.thematic 


/home/pietro/builds/grass70/src/grass70/scripts/r.in.srtm   


/home/pietro/builds/grass70/src/grass70/scripts/v.db.update 


--  


In case of errors please change into the directory with error and run 'make'.   


If you get multiple errors, you need to deal with them in the order they


appear in the error log. If you get an error building a library, you will   


also get errors from anything which uses the library.   


-- 

then I try to run 'make':
--
$ cd src/grass70/lib/python/

python $ make   


python -m py_compile /home/pietro/builds/grass70/src/grass70/dist.x86_64-
unknown-linux-gnu/etc/python/grass/script/core.py   
   
Sorry: IndentationError: ('expected an indented block', 
('/home/pietro/builds/grass70/src/grass70/dist.x86_64-unknown-linux-
gnu/etc/python/grass/script/core.py', 71, 10, 'return val\n'))make: *** 
[/home/pietro/builds/grass70/src/grass70/dist.x86_64-unknown-linux-
gnu/etc/python/grass/script/core.pyc] Error 1 


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


Re: [GRASS-dev] Error while browsing files with GRASS

2010-03-03 Thread Maciej Sieczka

Luisa Peña pisze:

yes, Probably it's. The thing is I don't know where/how to fix this.


In any case though don't hesitate to report bugs in GRASS Trac.

--
Maciej Sieczka
http://www.sieczka.org

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


[GRASS-dev] [GRASS GIS] #981: v.external db connection key missing for some GDAL drivers

2010-03-03 Thread GRASS GIS
#981: v.external db connection key missing for some GDAL drivers
-+--
 Reporter:  rblazek  |   Owner:  grass-dev@lists.osgeo.org
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  6.4.0
Component:  Vector   | Version:  unspecified  
 Keywords:   |Platform:  Unspecified  
  Cpu:  Unspecified  |  
-+--
 If OGR_L_GetFIDColumn does not return a column (OGR SHP driver for
 example) it is then missing in db connection info and consequently db
 operations do not work on vector created using v.external. The problem is
 here
 http://trac.osgeo.org/grass/browser/grass/trunk/lib/vector/Vlib/field.c#L8
  and there is already TODO here
 http://trac.osgeo.org/grass/browser/grass/trunk/lib/vector/Vlib/field.c#L582

 The problem can be tested either by v.db.connect -p, no key printed or
 d.what.vect for example (key field missing in query).

 I dont think it can be easily fixed. It would be possible to add OGR FID
 to attributes, but OGR SQL engine most probably does not know about FID,
 it only works on true attributes (to be verified, maybe FID is available
 with some special name).

 Radim

-- 
Ticket URL: http://trac.osgeo.org/grass/ticket/981
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #982: Vector modules changing db should call Vect_set_db_updated

2010-03-03 Thread GRASS GIS
#982: Vector modules changing db should call Vect_set_db_updated
-+--
 Reporter:  rblazek  |   Owner:  grass-dev@lists.osgeo.org
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  6.4.0
Component:  default  | Version:  unspecified  
 Keywords:   |Platform:  Unspecified  
  Cpu:  Unspecified  |  
-+--
 All vector modules which modify its attribute table (structure or data)
 should call Vect_set_db_updated like v.what.rast for example does.

 It involves most v.db.* modules.

-- 
Ticket URL: http://trac.osgeo.org/grass/ticket/982
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #981: v.external db connection key missing for some GDAL drivers

2010-03-03 Thread GRASS GIS
#981: v.external db connection key missing for some GDAL drivers
--+-
  Reporter:  rblazek  |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  normal   |   Milestone:  6.4.0
 Component:  Vector   | Version:  unspecified  
Resolution:   |Keywords:  v.external   
  Platform:  Unspecified  | Cpu:  Unspecified  
--+-
Changes (by martinl):

  * keywords:  = v.external

-- 
Ticket URL: http://trac.osgeo.org/grass/ticket/981#comment:1
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] svn: 41275 (Identation error in core.py?)

2010-03-03 Thread Markus Neteler
On Wed, Mar 3, 2010 at 12:58 PM, Pietro Zambelli peter.z...@gmail.com wrote:
 Hi all!

 I try to compile grass7 from svn I reach this error:

 GRASS GIS compilation log
 -
 Started compilation: Wed Mar  3 12:34:18 CET 2010
 --
 Errors in:
 /home/pietro/builds/grass70/src/grass70/lib/python
 /home/pietro/builds/grass70/src/grass70/scripts/d.vect.thematic
 /home/pietro/builds/grass70/src/grass70/scripts/r.in.srtm
 /home/pietro/builds/grass70/src/grass70/scripts/v.db.update
 --
 In case of errors please change into the directory with error and run 'make'.
 If you get multiple errors, you need to deal with them in the order they
 appear in the error log. If you get an error building a library, you will
 also get errors from anything which uses the library.
 --

 then I try to run 'make':
 --
 $ cd src/grass70/lib/python/
 python $ make
 python -m py_compile /home/pietro/builds/grass70/src/grass70/dist.x86_64-
 unknown-linux-gnu/etc/python/grass/script/core.py
 Sorry: IndentationError: ('expected an indented block',
 ('/home/pietro/builds/grass70/src/grass70/dist.x86_64-unknown-linux-
 gnu/etc/python/grass/script/core.py', 71, 10, '    return val\n'))make: ***
 [/home/pietro/builds/grass70/src/grass70/dist.x86_64-unknown-linux-
 gnu/etc/python/grass/script/core.pyc] Error 1

I have tried with today's SVN - no such problem.

[nete...@north python]$ touch core.py
[nete...@north python]$ make
/usr/bin/install -c  -m 644 core.py
/home/neteler/grass70/dist.x86_64-unknown-linux-gnu/etc/python/grass/script/core.py
python -m py_compile
/home/neteler/grass70/dist.x86_64-unknown-linux-gnu/etc/python/grass/script/core.py
[nete...@north python]$

Perhaps you have local modifications? Which python version do you use?

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


Re: [GRASS-dev] svn: 41275 (Identation error in core.py?)

2010-03-03 Thread Glynn Clements

Pietro Zambelli wrote:

 then I try to run 'make':
 --
 $ cd src/grass70/lib/python/
 python $ make
 python -m py_compile 
 /home/pietro/builds/grass70/src/grass70/dist.x86_64-unknown-linux-gnu/etc/python/grass/script/core.py
 Sorry: IndentationError: ('expected an indented block', 
 ('/home/pietro/builds/grass70/src/grass70/dist.x86_64-unknown-linux-gnu/etc/python/grass/script/core.py',
  71, 10, 'return val\n'))
 make: *** 
 [/home/pietro/builds/grass70/src/grass70/dist.x86_64-unknown-linux-gnu/etc/python/grass/script/core.pyc]
  Error 1 

Have you edited that file? The only way that I can see that error
occurring is if the tab at the beginning of the line has been replaced
by 4 spaces (Python assumes 8-column tabs).

-- 
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] future thematic cartography in GRASS [was: Re: [GRASS GIS] #974: [Patch] add option to d.vect to make symbol size proportionate to square root of size_column]

2010-03-03 Thread Hamish
Moritz wrote:
 What is still missing right now is an easy way to display a
 combination of color-classified and proportionately sized
 symbols.

by the way, WRT floating point raster maps there is a control in ps.map's
colortable instruction to show range bands instead of a smooth legend:


   Adding the
   discrete  Y  instruction  will  command  the program to
   treat the map as a categorical map.  In  this  way  the
   legend can be created with discrete range bands instead
   of a continuous gradient. You must use  the  r.category
   or r.support module to set up the range labels first.




Hamish



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


[GRASS-dev] [GRASS GIS] #983: sort g.mapsets -l output

2010-03-03 Thread GRASS GIS
#983: sort g.mapsets -l output
-+--
 Reporter:  neteler  |   Owner:  grass-dev@lists.osgeo.org
 Type:  enhancement  |  Status:  new  
 Priority:  normal   |   Milestone:  6.4.1
Component:  default  | Version:  svn-releasebranch64  
 Keywords:   |Platform:  All  
  Cpu:  All  |  
-+--
 The output of g.mapsets -l is currently unordered:

 {{{
 GRASS 6.4.0svn (patUTM32):~  g.mapsets -l
 lidar2006 slovenia PERMANENT modisLST005warming_cooling dalponte
 solarenergy
 corine modisLST005quality ortho_texture modisLST005dtr modisLST005winkler
 belluno modisLST005dekads16 modisLST005annual modisLST005monthly
 arco_texture
 modisLST005GDD_b11 lidar_patris zanzara_tigre_seasonality
 modisLST005dailymeans modisLST005rst2006_2010 ortho_2006 solarenergy2
 modisLST005rst_tiger population castellani modisLST005GDD modisEVI005
 dtm_1m_external modisLST005filt westnile watersheds linke_turbidity
 zanzara_satellite irs_liss horizon sqlite lagolo modisLST005analysis
 solarenergyPAT modisLST005dailyminimum modisLST005rst2000_2005
 modisLST005dekads7 neteler meteo_iasma irs_liss2 landsat liss
 modisLST005filt2
 landsat_thermal patris_ortho_texture
 }}}

 It would be quite helpful to add an alphabetical sort here.

-- 
Ticket URL: http://trac.osgeo.org/grass/ticket/983
GRASS GIS http://grass.osgeo.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev