Re: [GRASS-dev] Which is the correct WIND convention for creating a new mapset?

[Markus Metz]

On Tue, May 7, 2019 at 10:20 AM Panagiotis Mavrogiorgos 
wrote:
>
>
>
> On Mon, May 6, 2019 at 9:38 PM Markus Metz 
wrote:
>>
>>
>>
>> On Mon, May 6, 2019 at 6:21 PM Panagiotis Mavrogiorgos 
wrote:
>> >
>> > Hello all,
>> >
>> > I am a bit confused WRT what the expected WIND should be when you
create a new mapset.
>>
>> > [...]
>>
>> > Is there an established convention?
>>
>> IMHO, new mapsets should use DEFAULT_WIND from PERMANENT.
>
>
> Thank you Markus, that's what I expected, too.
>
>>
>> But the current region of a new mapset is often adjusted, therefore it
does not really matter if DEFAULT_WIND or WIND is used.
>
>
> I don't disagree, but still, I don't see what's the benefit of not using
the same convention everywhere. Furthermore, I truly don't understand why 4
different implementations are needed.

True, g.mapset -c should be used whenever possible. I adjusted the wxGUI
startup wizard and the tests in trunk r74472,3 (the tests should use
g.mapset -c, not yet implemented)

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

Re: [GRASS-dev] [GRASS GIS] #3790: Cleanup gettext usage for python code

[GRASS GIS]

#3790: Cleanup gettext usage for python code
--+-
  Reporter:  pmav99   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  reopened
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Python   |Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by neteler):

 Replying to [comment:8 pmav99]:
 > Are you sure this is at trunk Markus? Since 74307
 {{{gui_core/widgets.py}}} shouldn't be trying to import {{{_}}}.

 Oh, apparently a old compilation leftover. After "make distclean" and
 recompilation it works (right now using Python 2). Sorry for the "d.mon"
 noise.

-- 
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] #3790: Cleanup gettext usage for python code

[GRASS GIS]

#3790: Cleanup gettext usage for python code
--+-
  Reporter:  pmav99   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  reopened
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Python   |Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by pmav99):

 Are you sure this is at trunk Markus? Since 74307
 {{{gui_core/widgets.py}}} shouldn't be trying to import {{{_}}}.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] svn/trac -> git/github migration plan

[Veronica Andreo]

El mar., 7 may. 2019 a las 11:54, Martin Landa ()
escribió:

> Hi,
>
> út 7. 5. 2019 v 11:14 odesílatel Veronica Andreo 
> napsal:
> > I'd suggest then to set a deadline for ticket review by reporters, eg:
> this Sunday (or any other date before the planned code sprint in Berlin)
>
> could work. Till Sunday I will have also time to test issue migration
> a bit more. Then migration could happen in beginning of next week
> (Mon/Tue).
>

+1! :)

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

Re: [GRASS-dev] [GRASS GIS] #3790: Cleanup gettext usage for python code

[GRASS GIS]

#3790: Cleanup gettext usage for python code
--+-
  Reporter:  pmav99   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  reopened
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Python   |Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by neteler):

 Here, how to see the (or one of the) errors easily:

 {{{
 GRASS 7.7.svn (nc_spm_08_grass7):~ > d.mon wx0
 GRASS 7.7.svn (nc_spm_08_grass7):~ > Traceback (most recent call last):
   File "/home/mneteler/software/grass77/dist.x86_64-pc-linux-
 gnu/gui/wxpython/mapdisp/main.py", line 47, in 
 from core.render import Map, MapLayer, Overlay, RenderMapMgr
   File "/home/mneteler/software/grass77/dist.x86_64-pc-linux-
 gnu/gui/wxpython/core/render.py", line 42, in 
 from core.ws import RenderWMSMgr
   File "/home/mneteler/software/grass77/dist.x86_64-pc-linux-
 gnu/gui/wxpython/core/ws.py", line 33, in 
 from core.gthread import gThread
   File "/home/mneteler/software/grass77/dist.x86_64-pc-linux-
 gnu/gui/wxpython/core/gthread.py", line 28, in 
 from core.gconsole import EVT_CMD_DONE, wxCmdDone
   File "/home/mneteler/software/grass77/dist.x86_64-pc-linux-
 gnu/gui/wxpython/core/gconsole.py", line 49, in 
 from gui_core.forms import GUI
   File "/home/mneteler/software/grass77/dist.x86_64-pc-linux-
 gnu/gui/wxpython/gui_core/forms.py", line 98, in 
 from gui_core.widgets import StaticWrapText, ScrolledPanel,
 ColorTablesComboBox, \
   File "/home/mneteler/software/grass77/dist.x86_64-pc-linux-
 gnu/gui/wxpython/gui_core/widgets.py", line 90, in 
 from core.utils import _
 ImportError: cannot import name '_' from 'core.utils'
 (/home/mneteler/software/grass77/dist.x86_64-pc-linux-
 gnu/gui/wxpython/core/utils.py)

 }}}

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] fatra reports have not been updated since 2019-03-26

[Panagiotis Mavrogiorgos]

The testsuite reports has not been updated for quite some time now. Can
someone please have a look?

http://fatra.cnr.ncsu.edu/grassgistests/summary_report/nc/index.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] svn/trac -> git/github migration plan

[Martin Landa]

Hi,

út 7. 5. 2019 v 11:14 odesílatel Veronica Andreo  napsal:
> I'd suggest then to set a deadline for ticket review by reporters, eg: this 
> Sunday (or any other date before the planned code sprint in Berlin)

could work. Till Sunday I will have also time to test issue migration
a bit more. Then migration could happen in beginning of next week
(Mon/Tue).


Ma

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

[GRASS-dev] [GRASS GIS] #3840: v.to.rast: allow rasterization of z value also for 3D lines with differing altitude

[GRASS GIS]

#3840: v.to.rast: allow rasterization of z value also for 3D lines with 
differing
altitude
-+-
 Reporter:  sbl  |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  normal   |  Milestone:  7.8.0
Component:  Default  |Version:  svn-trunk
 Keywords:  v.to.rast|CPU:  Unspecified
 Platform:  All  |
-+-
 In order to rasterize 3D lines, on has to add points along the line and
 rasterize the points (whos hight btw is nicely interpolated). That is not
 too efficient...

 Would be great if v.to.rast could do this interpolation as well and assign
 height to pixels along the line accordingly...

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] svn/trac -> git/github migration plan

[Veronica Andreo]

Hi Martin,

Thanks for explanation and for all your hard work! :)

El mar., 7 may. 2019 05:28, Martin Landa  escribió:

> Hi,
>
> po 6. 5. 2019 v 23:06 odesílatel Veronica Andreo 
> napsal:
> > Say, if source code migration starts tomorrow, how long it would take?
> Then set that day (+2 or 3 if you want) as deadline for tickets revision,
> then migrate tickets, done :)
>
> source code migration will take a few hours. See my notes in previous
> mail.


I'd suggest then to set a deadline for ticket review by reporters, eg: this
Sunday (or any other date before the planned code sprint in Berlin)

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

Re: [GRASS-dev] svn/trac -> git/github migration plan

[Martin Landa]

Hi,

po 6. 5. 2019 v 23:06 odesílatel Veronica Andreo  napsal:
> Say, if source code migration starts tomorrow, how long it would take? Then 
> set that day (+2 or 3 if you want) as deadline for tickets revision, then 
> migrate tickets, done :)

source code migration will take a few hours. See my notes in previous mail. Ma

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

Re: [GRASS-dev] svn/trac -> git/github migration plan

[Martin Landa]

Hi,

po 6. 5. 2019 v 22:49 odesílatel Markus Neteler  napsal:
> Why wait for that with the source code migration?
> Please let's start with it. The tickets can follow in a second step.
> This also prevents us from being overloaded.

my idea to do migration in one step comes from assumption that new git
commits can be referenced to github issues. Issue migration needs to
be also done on private repository. This would require to set up empty
private repo, migrate tickets and than transfer ticket using GitHub
API to public repo. This complicates procedure a bit. I would still
prefer to do source code and issues migration together even it will
take some time.

Ma

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

Re: [GRASS-dev] Which is the correct WIND convention for creating a new mapset?

[Panagiotis Mavrogiorgos]

On Mon, May 6, 2019 at 9:38 PM Markus Metz 
wrote:

>
>
> On Mon, May 6, 2019 at 6:21 PM Panagiotis Mavrogiorgos 
> wrote:
> >
> > Hello all,
> >
> > I am a bit confused WRT what the expected WIND should be when you create
> a new mapset.
>
> [...]
>
> Is there an established convention?
>
> IMHO, new mapsets should use DEFAULT_WIND from PERMANENT.
>

Thank you Markus, that's what I expected, too.


> But the current region of a new mapset is often adjusted, therefore it
> does not really matter if DEFAULT_WIND or WIND is used.
>

I don't disagree, but still, I don't see what's the benefit of not using
the same convention everywhere. Furthermore, I truly don't understand why 4
different implementations are needed.

with kind regards,
P.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3392: t.register: encoding error

[GRASS GIS]

#3392: t.register: encoding error
--+-
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.2.4
 Component:  Temporal |Version:  svn-trunk
Resolution:  fixed|   Keywords:  t.register encoding
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by mlennert):

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


Comment:

 Replying to [comment:41 veroandreo]:
 > Replying to [comment:40 mlennert]:
 > > Has the work on Python 3 changed anything for this discussion, here ?
 >
 > Testing the commands provided in comment:21 gives no error here (trunk,
 r74471M) within a python3 virtual environment. Also no errors in 76
 relbranch.
 >
 > Tell me if I can test further, but I'd suggest closing since the
 reported issue seems to be gone.

 Thanks a lot for testing. As it works for you, I'm closing. We can reopen
 if needed.

-- 
Ticket URL: 
GRASS GIS 

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