Re: [GRASS-dev] G70 Ubuntu: GUI menu access for i.eb.hsebal01 looks for i.eb.h_sebal01

2015-01-01 Thread Martin Landa
Hi,

2015-01-02 4:32 GMT+01:00 Yann Chemin :
> maybe creating a directory in user with two significant number for the
> version might help in this case
>
> but not sure it is in the general interest.
>
> .grass7/toolboxes/menudata.xml
> ->
> .grass70/toolboxes/menudata.xml

I would suggest to keep .grass7{majorversion}, if you need something
special for toolboxes then probably

.grass7/toolboxes/metadata-7.0.xml

Martin

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


Re: [GRASS-dev] G70 Ubuntu: GUI menu access for i.eb.hsebal01 looks for i.eb.h_sebal01

2015-01-01 Thread Yann Chemin
maybe creating a directory in user with two significant number for the
version might help in this case

but not sure it is in the general interest.

.grass7/toolboxes/menudata.xml
->
.grass70/toolboxes/menudata.xml

On 2 January 2015 at 06:49, Vaclav Petras  wrote:

>
> On Wed, Dec 31, 2014 at 11:06 AM, Markus Neteler 
> wrote:
>
>> On Wed, Dec 31, 2014 at 3:52 PM, Yann Chemin  wrote:
>> > indeed Markus,
>> >
>> > it is using an old file from:
>> > /home/yann/.grass7/toolboxes/menudata.xml
>> >
>> > Correcting that file makes it OK.
>>
>> Good. But do you need that file at all?
>>
>> The file is generated if you have your custom menu and/or toolboxes
> defined.
>
>
>> > Deleting it makes it follow the PPA version.
>>
>> Perfect. Not sure if we could auto-detect an outdated toolbox file
>
>
> We do that for user-created files but not for the files in the
> distribution; it just didn't seem important at the time of writing.
>
> See:
>
>
> http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/core/toolboxes.py
>



-- 

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

Re: [GRASS-dev] [GRASS GIS] #2521: d.vect.thematic, "Neither MONITOR (managed by d.mon command) nor" error

2015-01-01 Thread GRASS GIS
#2521: d.vect.thematic, "Neither MONITOR (managed by d.mon command) nor" error
+---
  Reporter:  jamesp670  |   Owner:  grass-dev@…  
  Type:  defect |  Status:  closed   
  Priority:  normal |   Milestone:  7.0.0
 Component:  Display| Version:  svn-releasebranch70  
Resolution:  fixed  |Keywords:  d.vect.thematic  
  Platform:  Linux  | Cpu:  x86-64   
+---

Comment(by wenzeslaus):

 Replying to [comment:2 martinl]:
 > You need to enable direct rendering (1) or start graphic monitor (2) to
 use d.vect.thematic.

 I think that the error message is quite informative but it seems that
 without documenting this behavior, people just consider this as an bug
 rather than wrong usage of interface.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] G70 Ubuntu: GUI menu access for i.eb.hsebal01 looks for i.eb.h_sebal01

2015-01-01 Thread Vaclav Petras
On Wed, Dec 31, 2014 at 11:06 AM, Markus Neteler  wrote:

> On Wed, Dec 31, 2014 at 3:52 PM, Yann Chemin  wrote:
> > indeed Markus,
> >
> > it is using an old file from:
> > /home/yann/.grass7/toolboxes/menudata.xml
> >
> > Correcting that file makes it OK.
>
> Good. But do you need that file at all?
>
> The file is generated if you have your custom menu and/or toolboxes
defined.


> > Deleting it makes it follow the PPA version.
>
> Perfect. Not sure if we could auto-detect an outdated toolbox file


We do that for user-created files but not for the files in the
distribution; it just didn't seem important at the time of writing.

See:

http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/core/toolboxes.py
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS 7 - Ubuntu package build problem on Launchpad

2015-01-01 Thread Vaclav Petras
On Tue, Dec 30, 2014 at 9:29 AM, Markus Neteler  wrote:

> # --> configure -->
> include/Make/Platform.make:GRASS_VERSION_SVN   = 63869M
>

It seems strange that the revision number ends with M. This means that the
source code was modified. Is this the case? If yes, is it ok?
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #2520: d.grid: -c and -d flags not displaying + and - marks

2015-01-01 Thread GRASS GIS
#2520: d.grid: -c and -d flags not displaying + and - marks
--+-
 Reporter:  richardc  |   Owner:  grass-dev@…  
 Type:  defect|  Status:  new  
 Priority:  normal|   Milestone:  7.0.0
Component:  Display   | Version:  svn-trunk
 Keywords:  d.grid|Platform:  Linux
  Cpu:  x86-32|  
--+-

Comment(by annakrat):

 It works for me with r63876. Could you see any errors?

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] wxGUI no longer shows zoom box

2015-01-01 Thread Anna Petrášová
On Wed, Dec 31, 2014 at 9:31 AM, Markus Neteler  wrote:

> Hi,
>
> for some weeks the wxGUI no longer shows the box when zooming...
> Should I open a ticket for that?
>

Trunk or release branch? When I zoom I can see the red line. Does it happen
with a fresh GUI instance?

Anna


>
> thank
> 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] [GRASS GIS] #2343: GRASS 7: "inf" values break insert statements in v.rast.stats

2015-01-01 Thread GRASS GIS
#2343: GRASS 7: "inf" values break insert statements in v.rast.stats
--+-
 Reporter:  sbl   |   Owner:  grass-dev@…  
 Type:  defect|  Status:  new  
 Priority:  normal|   Milestone:  7.0.0
Component:  Python| Version:  svn-releasebranch70  
 Keywords:  v.rast.stats  |Platform:  All  
  Cpu:  All   |  
--+-

Comment(by neteler):

 ...should r62938 be reverted and implemented differently?

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Planning GRASS GIS 7.0.0RC1

2015-01-01 Thread Markus Neteler
On Wed, Dec 31, 2014 at 5:33 PM, Markus Neteler  wrote:
> Hi,
>
> due to incomplete backports (or statements that they should not be
> done), RC1 is slightly postponed.
> I see notable differences here:
> - lib/vector/Vlib/ascii.c
> - lib/vector/Vlib/build.c
> - lib/vector/Vlib/line.c
> - lib/vector/Vlib/map.c
> - lib/vector/Vlib/read_pg.c
> - lib/vector/Vlib/remove_areas.c
> - lib/vector/Vlib/snap.c
> - lib/vector/Vlib/write_nat.c

... remain unclear to me.

Additionally, I found the deactivated
grass70/vector/v.in.sites/
 remove or move to Addons?

Furthermore, many vector/ modules show unbackported differences
--> I cannot judge them.

In display/ are also a series of differences but Martin is working on that.

Then: misc/ + ps/ + raster/ + imagery/ + raster3d/ + scripts/ +
temporal/ I have checked. There are only these relevant differences:
- r.distance (Huidae)
- r.proj bugfixes (Markus Metz)
- r.spread (Vaclav)
- new r3 modules by Anna (perhaps yet experimental)

In general/ there are differences in
- g.rename (Huidae)
- manage/lister (Huidae)

Also the wxGUI differences I'll leave to the experts :-)

Just to bring this to your attention.

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


Re: [GRASS-dev] point cloud analysis: new features

2015-01-01 Thread Paulo van Breugel
Great! The spatial cluster analysis option would be really good, e.g. for model 
evaluation using spatially segregated k-fold cross validation methods.



On 1 January 2015 22:18:39 CET, Markus Metz  
wrote:
>Hi all,
>
>a new spatial index for point data is available in lib/btree2: a
>multidimensional search tree, also known as k-d tree.
>
>What is it good for:
>
>- nearest neighbor statistics: test if points are randomly
>distributed. The current GRASS addon v.nnstat uses an external k-d
>tree from PCL (which in turn uses flann) which finds the approximate,
>not the exact nearest neighbor. The new GRASS-native k-d tree always
>finds the real nearest neighbor.
>
>- spatial cluster analysis: a point cloud can be partitioned into
>separate clusters where points within each cluster are closer to each
>other than to points of another cluster. To be implemented.
>
>- point cloud thinning: a sample can be generated from a large point
>cloud by specifying a minimum distance between sample points. To be
>implemented.
>
>The new k-d tree is now used by v.clean tool=snap (Vect_snap_lines()),
>reducing both memory consumption and processing time.
>
>
>More technical:
>the new k-d tree finds the exact nearest neighbor(s), not some
>approximation. It supports up to 255 dimensions. It is dynamic, i.e.
>points can be inserted and removed at any time. It is balanced to
>improve search performance. It provides k nearest neighbor search
>(find k neighbors to a given coordinate) as well as radius or distance
>search (find all neighbors within radius, i.e. not farther away than
>radius to a given coordinate).
>
>Markus M
>___
>grass-dev mailing list
>grass-dev@lists.osgeo.org
>http://lists.osgeo.org/mailman/listinfo/grass-dev

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] point cloud analysis: new features

2015-01-01 Thread Markus Metz
Hi all,

a new spatial index for point data is available in lib/btree2: a
multidimensional search tree, also known as k-d tree.

What is it good for:

- nearest neighbor statistics: test if points are randomly
distributed. The current GRASS addon v.nnstat uses an external k-d
tree from PCL (which in turn uses flann) which finds the approximate,
not the exact nearest neighbor. The new GRASS-native k-d tree always
finds the real nearest neighbor.

- spatial cluster analysis: a point cloud can be partitioned into
separate clusters where points within each cluster are closer to each
other than to points of another cluster. To be implemented.

- point cloud thinning: a sample can be generated from a large point
cloud by specifying a minimum distance between sample points. To be
implemented.

The new k-d tree is now used by v.clean tool=snap (Vect_snap_lines()),
reducing both memory consumption and processing time.


More technical:
the new k-d tree finds the exact nearest neighbor(s), not some
approximation. It supports up to 255 dimensions. It is dynamic, i.e.
points can be inserted and removed at any time. It is balanced to
improve search performance. It provides k nearest neighbor search
(find k neighbors to a given coordinate) as well as radius or distance
search (find all neighbors within radius, i.e. not farther away than
radius to a given coordinate).

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


Re: [GRASS-dev] Planning GRASS GIS 7.0.0RC1

2015-01-01 Thread Martin Landa
Hi,

2014-12-31 17:33 GMT+01:00 Markus Neteler :
> - lib/vector/Vlib/net_analyze.c
> - lib/vector/Vlib/net_build.c

I would say, do not backport. It's related to quite new support for
turns in vector networks [1]. I would say new feature in GRASS
7.1/7.2.

Martin

[1] http://grasswiki.osgeo.org/wiki/Turns_in_the_vector_network_analysis

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


Re: [GRASS-dev] Planning GRASS GIS 7.0.0RC1

2015-01-01 Thread Martin Landa
Hi,

2014-12-31 17:33 GMT+01:00 Markus Neteler :
> Not sure what's experimental and what's a forgotten bugfix backports?

I would also add http://trac.osgeo.org/grass/ticket/2522

Martin

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


[GRASS-dev] [GRASS GIS] #2522: d.vect.thematic, d.thematic.area in GRASS 7.0

2015-01-01 Thread GRASS GIS
#2522: d.vect.thematic, d.thematic.area in GRASS 7.0
--+-
 Reporter:  martinl   |   Owner:  grass-dev@…   
   
 Type:  defect|  Status:  new   
   
 Priority:  blocker   |   Milestone:  7.0.0 
   
Component:  Display   | Version:  svn-trunk 
   
 Keywords:  d.vect.thematic, d.thematic.area  |Platform:  Unspecified   
   
  Cpu:  Unspecified   |  
--+-
 Currently we have two modules for thematic rendering vector data:

  * d.vect.thematic
  * d.thematic.area

 d.vect.thematic is a Python script which has been rewritten from Bash
 based on code from GRASS 6. This module runs several times d.vect command
 to render thematic data. This makes an integration of this module in wxGUI
 as problematic.

 d.thematic.area is a C module which use C library. This make this module
 quicker to render data and more flexible. The code can be shared eg. with
 v.colors to calculate breaks, etc. Unfortunately it's just written for
 areal features and seems to be somehow not finished.

 My suggestion is (before GRASS 7 release):

  * to move python script `d.vect.thematic` to addons
  * rename `d.thematic.area` to `d.thematic` or better `d.vect.thematic`
 (in this case to rename `d.vect.thematic` in addons to `d.vect.thematic2`)
 - any other name?

 In the future to improve C module based on functionality of Python script.

 Any comments, ideas?

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #2521: d.vect.thematic, "Neither MONITOR (managed by d.mon command) nor" error

2015-01-01 Thread GRASS GIS
#2521: d.vect.thematic, "Neither MONITOR (managed by d.mon command) nor" error
+---
  Reporter:  jamesp670  |   Owner:  grass-dev@…  
  Type:  defect |  Status:  closed   
  Priority:  normal |   Milestone:  7.0.0
 Component:  Display| Version:  svn-releasebranch70  
Resolution:  fixed  |Keywords:  d.vect.thematic  
  Platform:  Linux  | Cpu:  x86-64   
+---
Changes (by martinl):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 I am taking liberty to close this ticket. Please reopen if needed.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #2521: d.vect.thematic, "Neither MONITOR (managed by d.mon command) nor" error

2015-01-01 Thread GRASS GIS
#2521: d.vect.thematic, "Neither MONITOR (managed by d.mon command) nor" error
-+--
 Reporter:  jamesp670|   Owner:  grass-dev@…  
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  7.0.0
Component:  Display  | Version:  svn-releasebranch70  
 Keywords:  d.vect.thematic  |Platform:  Linux
  Cpu:  x86-64   |  
-+--

Comment(by martinl):

 BTW, I fixed a lot of issues in r63904. Also `-u` flag is now `rgb_column`
 option (similary to other modules like v.colors and d.vect).

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #2521: d.vect.thematic, "Neither MONITOR (managed by d.mon command) nor" error

2015-01-01 Thread GRASS GIS
#2521: d.vect.thematic, "Neither MONITOR (managed by d.mon command) nor" error
-+--
 Reporter:  jamesp670|   Owner:  grass-dev@…  
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  7.0.0
Component:  Display  | Version:  svn-releasebranch70  
 Keywords:  d.vect.thematic  |Platform:  Linux
  Cpu:  x86-64   |  
-+--

Comment(by martinl):

 You need to enable direct rendering (1) or start graphic monitor (2) to
 use d.vect.thematic. Now the module prints the error message without
 traceback:

 {{{
 d.vect.thematic obce_polygon column=statuskod
 ERROR: Neither MONITOR (managed by d.mon command) nor
 GRASS_RENDER_IMMEDIATE (used for direct rendering) defined)
 }}}

 Start monitor:

 {{{
 d.mon wx0
 }}}

 or file-based, eg.

 {{{
 d.mon cairo out=thematic.png
 }}}

 {{{
 d.vect.thematic obce_polygon column=statuskod
 }}}

 (1) http://grass.osgeo.org/grass71/manuals/variables.html#list-of-
 selected-grass-environment-variables-for-rendering
 (2) http://grass.osgeo.org/grass71/manuals/d.mon.html

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] grass on launchpad

2015-01-01 Thread Martin Landa
Hi,

2015-01-01 12:25 GMT+01:00 Martin Landa :
> grass-devel. The next step is to add grass70 package to grass-stable
> which will be built on request based on 7.0.0beta4, RC1, 7.0.0... Any
> hints how to set it up?

I tried to create a new branch which points 7.0.0beta4 [1], based on
that I can create a recipe. But it's not apparently a good way. Is it
possible to create recipe which points to given tarball [2]? Thanks
for clarification. Martin

[1] https://code.launchpad.net/~grass/grass/7.0.0
[2] https://launchpad.net/grass/7.0/7.0.0beta4/+download/grass-7.0.0beta4.tar.gz

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


Re: [GRASS-dev] grass on launchpad

2015-01-01 Thread Martin Landa
Hi,

2014-12-31 11:52 GMT+01:00 Martin Landa :
> currently we have recipe to build relbr7 [1] which points to base
> branch SVN [2]. To build package for beta4 I need to create a new
> recipe and register a new base branch which points to svn tagged
> branch [3], is it right? Any comments from our Launchpad gurus are
> highly welcome:-)

any idea? Currently we have 7.0 series [1] which points to
releasebranch_70 [2]. Based on that I will set up daily builds for
grass-devel. The next step is to add grass70 package to grass-stable
which will be built on request based on 7.0.0beta4, RC1, 7.0.0... Any
hints how to set it up?

Thanks, Martin

[1] https://launchpad.net/grass/7.0
[2] https://code.launchpad.net/~grass/grass/releasebranch_7_0

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


Re: [GRASS-dev] [GRASS GIS] #2521: d.vect.thematic, "Neither MONITOR (managed by d.mon command) nor" error

2015-01-01 Thread GRASS GIS
#2521: d.vect.thematic, "Neither MONITOR (managed by d.mon command) nor" error
-+--
 Reporter:  jamesp670|   Owner:  grass-dev@…  
 Type:  defect   |  Status:  new  
 Priority:  normal   |   Milestone:  7.0.0
Component:  Display  | Version:  svn-releasebranch70  
 Keywords:  d.vect.thematic  |Platform:  Linux
  Cpu:  x86-64   |  
-+--
Changes (by martinl):

  * keywords:  => d.vect.thematic
  * component:  Vector => Display


-- 
Ticket URL: 
GRASS GIS 

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