Re: [GRASS-dev] GSOC 2018 project for GRASS GIS

[Sanjeet]

On Sat, Mar 3, 2018 at 10:50 PM, Anna Petrášová  wrote:
> Basically, the GUI is mostly ported to work with wxPython4 (phoenix),
> which is (unlike wxpython 3) Python 3 ready. So far we are running the
> GUI on Python 2.7 only. There are some loose ends and depreciation
> warnings, which would be nice to get rid of. Since we need to keep
> backwards compatibility with wxpython 3, we wrapped some GUI classes
> (gui/wxpython/gui_core/wrap.py), so you can start there. You need to
> test your changes under both wxpython 3 and 4. Let me know if you need
> more clarification. More info what is Attribute Table manager:
>
> https://grass.osgeo.org/grass75/manuals/wxGUI.dbmgr.html
> https://grasswiki.osgeo.org/wiki/WxGUI_Attribute_Table_Manager

Hi Anna,

I've created a patch file for the ticket #3510.

> To post a patch in that ticket, you need to get osgeo id:
> https://www.osgeo.org/community/getting-started-osgeo/osgeo_userid/

I'm waiting for 'mantra' to create the osgeo user id, so that I can
upload the patch file.

-- 
Sanjeet Bhatti
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSOC 2018 project for GRASS GIS

[Sanjeet]

On Mon, Mar 5, 2018 at 6:43 PM, Anna Petrášová  wrote:
> Look in the GUI console (second tab at the bottom in Layer Manager).
> You can check if you are indeed running wxpython 4 easily from GUI, go
> to Python tab and try:
 import wx
 wx.version()
> 4.0.1 gtk2 (phoenix)
>
> I would recommend running it in virtualenv.
>

Yes, I see them now. Thanks!

-- 
Sanjeet Bhatti
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSOC 2018 project for GRASS GIS

[Anna Petrášová]

On Mon, Mar 5, 2018 at 7:20 PM, Sanjeet  wrote:
> On Sat, Mar 3, 2018 at 10:50 PM, Anna Petrášová  wrote:
>> Hi Sanjeet,
>
> Hi Anna,
>
>> On Mon, Feb 26, 2018 at 9:08 PM, Sanjeet  wrote:
>>
>> I would leave that up to you, you can send it in email, post it on
>> your github or whatever seems convenient for you.
>
> I will share the list soon.
>
>> Regarding the GUI, you can look at this ticket:
>> https://trac.osgeo.org/grass/ticket/3510
>>
>> Basically, the GUI is mostly ported to work with wxPython4 (phoenix),
>> which is (unlike wxpython 3) Python 3 ready. So far we are running the
>> GUI on Python 2.7 only. There are some loose ends and depreciation
>> warnings, which would be nice to get rid of. Since we need to keep
>> backwards compatibility with wxpython 3, we wrapped some GUI classes
>> (gui/wxpython/gui_core/wrap.py), so you can start there. You need to
>> test your changes under both wxpython 3 and 4. Let me know if you need
>> more clarification. More info what is Attribute Table manager:
>>
>> https://grass.osgeo.org/grass75/manuals/wxGUI.dbmgr.html
>> https://grasswiki.osgeo.org/wiki/WxGUI_Attribute_Table_Manager
>
> Meanwhile, I've setup my development environment and compiled the
> source code. I did not see the warning messages when I opened the
> Attribution Table Manager as mentioned in the ticket #3510 even when I
> installed wxpython 4 (on system Ubuntu 16.04 with Python 2.7.x).
>
> Is it supposed to be displaying in the console? Because I did not get
> any warnings.
> I even tried to set the g.gisenv set="DEBUG=5" to print the debugging
> messages along with WX_DEBUG. Am I missing some step?

Look in the GUI console (second tab at the bottom in Layer Manager).
You can check if you are indeed running wxpython 4 easily from GUI, go
to Python tab and try:
>>> import wx
>>> wx.version()
4.0.1 gtk2 (phoenix)

I would recommend running it in virtualenv.


>
> Thanks
> --
> Sanjeet Bhatti
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSOC 2018 project for GRASS GIS

[Sanjeet]

On Sat, Mar 3, 2018 at 10:50 PM, Anna Petrášová  wrote:
> Hi Sanjeet,

Hi Anna,

> On Mon, Feb 26, 2018 at 9:08 PM, Sanjeet  wrote:
>
> I would leave that up to you, you can send it in email, post it on
> your github or whatever seems convenient for you.

I will share the list soon.

> Regarding the GUI, you can look at this ticket:
> https://trac.osgeo.org/grass/ticket/3510
>
> Basically, the GUI is mostly ported to work with wxPython4 (phoenix),
> which is (unlike wxpython 3) Python 3 ready. So far we are running the
> GUI on Python 2.7 only. There are some loose ends and depreciation
> warnings, which would be nice to get rid of. Since we need to keep
> backwards compatibility with wxpython 3, we wrapped some GUI classes
> (gui/wxpython/gui_core/wrap.py), so you can start there. You need to
> test your changes under both wxpython 3 and 4. Let me know if you need
> more clarification. More info what is Attribute Table manager:
>
> https://grass.osgeo.org/grass75/manuals/wxGUI.dbmgr.html
> https://grasswiki.osgeo.org/wiki/WxGUI_Attribute_Table_Manager

Meanwhile, I've setup my development environment and compiled the
source code. I did not see the warning messages when I opened the
Attribution Table Manager as mentioned in the ticket #3510 even when I
installed wxpython 4 (on system Ubuntu 16.04 with Python 2.7.x).

Is it supposed to be displaying in the console? Because I did not get
any warnings.
I even tried to set the g.gisenv set="DEBUG=5" to print the debugging
messages along with WX_DEBUG. Am I missing some step?

Thanks
-- 
Sanjeet Bhatti
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSOC 2018 project for GRASS GIS

[Sanjeet]

On Wed, Feb 28, 2018 at 8:38 AM, Markus Neteler  wrote:
>
> There are some tickets flagged with "python3":
> https://trac.osgeo.org/grass/query?status=!closed=~python3
>
> I suppose that more tickets should carry that keyword but they need to
> be identified by scanning those with "python" keyword.
>
> The topic suggestions are posted here (as you know):
> https://trac.osgeo.org/grass/wiki/GSoC/2018
>
> but did you already check this page?
> https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students

Hi Markus,

Thanks for sharing the links. I've gone through them now.

-- 
Sanjeet Bhatti
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3471: Custom dropdown control doesn’t recognize mouse events

[GRASS GIS]

#3471: Custom dropdown control doesn’t recognize mouse events
--+
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  reopened
  Priority:  major|  Milestone:  7.2.3
 Component:  wxGUI|Version:  7.2.2
Resolution:   |   Keywords:  wxPython, dropdown control
   CPU:  Unspecified  |   Platform:  MacOSX
--+
Changes (by cmbarton):

 * status:  closed => reopened
 * priority:  normal => major
 * resolution:  fixed =>


Comment:

 I was wrong. This is still a problem. In fact, the dropdown menu is now
 invisible. See settings/grass working environment/change location and
 mapset. The change mapset control cannot be used at all. Upgrading to
 major (maybe should be critical) since it makes a set of functions
 completely unusable.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3487: vector digitizer unstable

[GRASS GIS]

#3487: vector digitizer unstable
+-
  Reporter:  cmbarton   |  Owner:  grass-dev@…
  Type:  defect | Status:  new
  Priority:  critical   |  Milestone:
 Component:  wxGUI  |Version:  7.2.2
Resolution: |   Keywords:  digitizer
   CPU:  OSX/Intel  |   Platform:  MacOSX
+-

Comment (by cmbarton):

 Also affects 7.4.0 and 7.5 trunk.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] planning releases - spring 2018

[Markus Neteler]

Hi devs,

just FYI - the roadmap is now updated according to latest discussions here:

https://trac.osgeo.org/grass/roadmap

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

Re: [GRASS-dev] [GRASS GIS] #3511: [patch] v.buffer: allow squared buffers around points

[GRASS GIS]

#3511: [patch] v.buffer: allow squared buffers around points
--+-
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.4.1
 Component:  Vector   |Version:  svn-trunk
Resolution:   |   Keywords:  v.buffer squared buffer
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by mmetz):

 Replying to [comment:1 mlennert]:
 > Replying to [ticket:3511 mlennert]:
 > > The attached patch implements squared buffers around points.
 >
 > Forgot to explain: with the patch, v.buffer should create square buffers
 around points if the -s flag is set.

 Currently v.buffer always uses Vect_point_buffer2() for points, but the
 Vect_*_buffer*() functions might disappear at some stage because they are
 not working properly (apart from point buffering). Therefore it might be
 safer to add this functionality to v.buffer directly.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3511: [patch] v.buffer: allow squared buffers around points

[GRASS GIS]

#3511: [patch] v.buffer: allow squared buffers around points
--+-
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.4.1
 Component:  Vector   |Version:  svn-trunk
Resolution:   |   Keywords:  v.buffer squared buffer
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by mlennert):

 Replying to [ticket:3511 mlennert]:
 > The attached patch implements squared buffers around points.

 Forgot to explain: with the patch, v.buffer should create square buffers
 around points if the -s flag is set.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] How difficult would it be to modify v.buffer to allow creation of square buffers around points

[Moritz Lennert]

On 05/03/18 14:10, Markus Metz wrote:



On Mon, Mar 5, 2018 at 12:07 PM, Moritz Lennert 
> wrote:

 >
 > Hi,
 >
 > For some applications it is sometimes interesting to be able to 
create square buffers around points. So my question to those who know 
the GEOS code best: How difficult would it be to change v.buffer to be 
able to do this ?


Buffers around points are trivial, and square buffers around points 
would be even more trivial. This could be triggered by the already 
existing -s flag (square caps at end of lines, outside corners straight).


Please create a ticket for square buffers around points such that this 
request does not get forgotten.


Done [1] already with an attempt at a (very simple) patch. Would be 
great if you could have a look.


Moritz

[1] https://trac.osgeo.org/grass/ticket/3511


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

Re: [GRASS-dev] [GRASS GIS] #3511: [patch] v.buffer: allow squared buffers around points

[GRASS GIS]

#3511: [patch] v.buffer: allow squared buffers around points
--+-
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.4.1
 Component:  Vector   |Version:  svn-trunk
Resolution:   |   Keywords:  v.buffer squared buffer
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by mlennert):

 * Attachment "squared_buffer_around_points.diff" added.


-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] [GRASS GIS] #3511: [patch] v.buffer: allow squared buffers around points

[GRASS GIS]

#3511: [patch] v.buffer: allow squared buffers around points
-+-
 Reporter:  mlennert |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  normal   |  Milestone:  7.4.1
Component:  Vector   |Version:  svn-trunk
 Keywords:  v.buffer squared buffer  |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 The attached patch implements squared buffers around points.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] How difficult would it be to modify v.buffer to allow creation of square buffers around points

[Markus Metz]

On Mon, Mar 5, 2018 at 12:07 PM, Moritz Lennert <
mlenn...@club.worldonline.be> wrote:
>
> Hi,
>
> For some applications it is sometimes interesting to be able to create
square buffers around points. So my question to those who know the GEOS
code best: How difficult would it be to change v.buffer to be able to do
this ?

Buffers around points are trivial, and square buffers around points would
be even more trivial. This could be triggered by the already existing -s
flag (square caps at end of lines, outside corners straight).

Please create a ticket for square buffers around points such that this
request does not get forgotten.

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

Re: [GRASS-dev] How difficult would it be to modify v.buffer to allow creation of square buffers around points

[Veronica Andreo]

Indeed, this would be a very cool feature to have! +1!

2018-03-05 12:07 GMT+01:00 Moritz Lennert :

> Hi,
>
> For some applications it is sometimes interesting to be able to create
> square buffers around points. So my question to those who know the GEOS
> code best: How difficult would it be to change v.buffer to be able to do
> this ?
>
> Moritz
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] How difficult would it be to modify v.buffer to allow creation of square buffers around points

[Moritz Lennert]

Hi,

For some applications it is sometimes interesting to be able to create 
square buffers around points. So my question to those who know the GEOS 
code best: How difficult would it be to change v.buffer to be able to do 
this ?


Moritz

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

Re: [GRASS-dev] [GRASS GIS] #774: i.rgb.his, i.his.rgb, d.his support for >8 bit

[GRASS GIS]

#774: i.rgb.his, i.his.rgb, d.his support for >8 bit
--+-
  Reporter:  hamish   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.4.1
 Component:  Raster   |Version:  svn-trunk
Resolution:   |   Keywords:  i.rgb.his, i.his.rgb, d.his
   CPU:  All  |   Platform:  All
--+-

Comment (by Nikos Alexandris):

 Replying to [comment:19 wenzeslaus]:
 > Replying to [comment:16 mlennert]:
 > > Nikos, how confident are you about your version in the sandbox ? Can
 it replace the version in trunk ?
 >
 > This is a computational danger zone, I think also automatic tests are
 required. I suggest to add tests to the modules in trunk and use them to
 test the new modules (whether they are in sandbox or addons).

 I fully agree. These tests would be another good exercise for me. If I
 only can make it to the upcoming code sprint, I will work on these.

 Please, see also/don't forget the other two:

 - https://trac.osgeo.org/grass/browser/sandbox/alexandris/i.rgb.hsl
 - https://trac.osgeo.org/grass/browser/sandbox/alexandris/i.hsl.rgb

-- 
Ticket URL: 
GRASS GIS 

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