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

[Veronica Andreo]

Hi Helli

El jue., 9 may. 2019 19:53, Helmut Kudrnovsky  escribió:

> Veronica Andreo wrote
> > Hola :)
> >
> > El mar., 7 may. 2019 a las 16:20, Veronica Andreo (<
>
> > veroandreo@
>
> > >)
> > escribió:
> >
> >> El mar., 7 may. 2019 a las 11:54, Martin Landa (<
>
> > landa.martin@
>
> > >)
> >> escribió:
> >>
> >>> Hi,
> >>>
> >>> út 7. 5. 2019 v 11:14 odesílatel Veronica Andreo <
>
> > veroandreo@
>
> > >
> >>> 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).
> >>>
> >>
> > Any other opinion/objection? Shall I post on FB and Twitter then? New
> > announcement here with deadline?
> >
> > Vero
> >
> >>
> >> +1! :)
> >>
> >> Vero
> >>
> >
> > ___
> > grass-dev mailing list
>
> > grass-dev@.osgeo
>
> > https://lists.osgeo.org/mailman/listinfo/grass-dev
>
> at least regarding tickets related to winGRASS 7.7.svn/Trunk and Python 3,
> trac issues can't be reviewed cause of
>
> https://trac.osgeo.org/grass/ticket/3837


See Martin's original mail and links. The tickets that need to be reviewed
are those with milestone 7.0.7 and 7.2.4, as to know if they are still
valid and milestone should be moved to 7.6.2

Tickets with milestone 7.8 will be migrated anyway...

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

[Helmut Kudrnovsky]

Veronica Andreo wrote
> Hola :)
> 
> El mar., 7 may. 2019 a las 16:20, Veronica Andreo (<

> veroandreo@

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

> landa.martin@

> >)
>> escribió:
>>
>>> Hi,
>>>
>>> út 7. 5. 2019 v 11:14 odesílatel Veronica Andreo <

> veroandreo@

> >
>>> 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).
>>>
>>
> Any other opinion/objection? Shall I post on FB and Twitter then? New
> announcement here with deadline?
> 
> Vero
> 
>>
>> +1! :)
>>
>> Vero
>>
> 
> ___
> grass-dev mailing list

> grass-dev@.osgeo

> https://lists.osgeo.org/mailman/listinfo/grass-dev

at least regarding tickets related to winGRASS 7.7.svn/Trunk and Python 3,
trac issues can't be reviewed cause of

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




-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3373: Lock file message

[GRASS GIS]

#3373: Lock file message
--+-
  Reporter:  baharmon |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  minor|  Milestone:  7.8.0
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:  lockfile
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by sbl):

 * milestone:  7.2.4 => 7.8.0


Comment:

 All enhancements should point to 7.8

-- 
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] #3502: v.proj location not set in dialog

[GRASS GIS]

#3502: v.proj location not set in dialog
+-
  Reporter:  balagates  |  Owner:  grass-dev@…
  Type:  defect | Status:  new
  Priority:  normal |  Milestone:  7.4.5
 Component:  wxGUI  |Version:  7.4.0
Resolution: |   Keywords:  v.proj location
   CPU:  OSX/Intel  |   Platform:  MacOSX
+-
Changes (by sbl):

 * milestone:  7.2.4 => 7.4.5


-- 
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] #3616: selecting location and mapset selections from pulldowns do not register in GUI

[GRASS GIS]

#3616: selecting location and mapset selections from pulldowns do not register 
in
GUI
--+-
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.4.5
 Component:  wxGUI|Version:  7.4.1
Resolution:   |   Keywords:  v.proj
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by sbl):

 * milestone:  7.2.4 => 7.4.5


-- 
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] #3297: Add sorting capabilities to color table editor

[GRASS GIS]

#3297: Add sorting capabilities to color table editor
--+-
  Reporter:  marisn   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  minor|  Milestone:  7.4.5
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by sbl):

 * milestone:  7.2.4 => 7.4.5


Comment:

 Still relevant I guess...

-- 
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] #3363: Add mask input parameter to v.surf.idw

[GRASS GIS]

#3363: Add mask input parameter to v.surf.idw
--+--
  Reporter:  Lads |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Vector   |Version:  7.2.1
Resolution:   |   Keywords:  v.surf.idw, mask
   CPU:  Unspecified  |   Platform:  Unspecified
--+--
Changes (by sbl):

 * milestone:  7.2.4 => 7.8.0


Comment:

 All enhancements should point to 7.8

-- 
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] #3281: region boundaries rendering

[GRASS GIS]

#3281: region boundaries rendering
--+---
  Reporter:  vincent  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:  g.region, map display
   CPU:  Unspecified  |   Platform:  Unspecified
--+---
Changes (by sbl):

 * milestone:  7.2.4 => 7.8.0


Comment:

 All enhancements should point to 7.8

-- 
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] #3480: m.cogo enhancement request: add declination support

[GRASS GIS]

#3480: m.cogo enhancement request: add declination support
--+-
  Reporter:  fgfletcher   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Default  |Version:  7.0.1
Resolution:   |   Keywords:  m.cogo
   CPU:  Unspecified  |   Platform:  MacOSX
--+-
Changes (by sbl):

 * milestone:  7.2.4 => 7.8.0


Comment:

 All enhancements should point to 7.8

-- 
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] #3419: v.to.db sinuous

[GRASS GIS]

#3419: v.to.db sinuous
+
  Reporter:  jradinger  |  Owner:  grass-dev@…
  Type:  defect | Status:  new
  Priority:  normal |  Milestone:  7.4.5
 Component:  Vector |Version:  7.2.2
Resolution: |   Keywords:  v.to.db, shape metrics
   CPU:  All|   Platform:  All
+
Changes (by sbl):

 * milestone:  7.2.4 => 7.4.5


Comment:

 Markus explanation answered the question-part of the ticket quite well.
 However, a warning message might be helpful for the users and then there
 is the issue with slope Markus mentioned...

-- 
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] #3304: db.copy GUI does not allow to enter from_table name

[GRASS GIS]

#3304: db.copy GUI does not allow to enter from_table name
--+-
  Reporter:  marisn   |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.2.4
 Component:  wxGUI|Version:  svn-trunk
Resolution:  fixed|   Keywords:  db.copy
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by sbl):

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


Comment:

 Works for me in GRASS 7.6

-- 
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] #3159: No label in output when using a point vector layer as in put in r.what

[GRASS GIS]

#3159: No label in output when using a point vector layer as in put in r.what
--+-
  Reporter:  pvanbosgeo   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  closed
  Priority:  normal   |  Milestone:  7.4.5
 Component:  Default  |Version:  unspecified
Resolution:  fixed|   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by sbl):

 * status:  new => closed
 * resolution:   => fixed
 * milestone:  7.0.7 => 7.4.5


Comment:

 Fixed in r71091

-- 
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] #3330: t.rast.to.rast3 error: Argument list too long

[GRASS GIS]

#3330: t.rast.to.rast3 error: Argument list too long
--+-
  Reporter:  richardc |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  7.8.0
 Component:  Temporal |Version:  7.2.0
Resolution:   |   Keywords:
   CPU:  x86-64   |   Platform:  Linux
--+-
Changes (by sbl):

 * type:  defect => enhancement
 * milestone:  7.2.4 => 7.8.0


Comment:

 This is a OS limitation.
 However a workaround could be added, I guess.
 See also #2418

-- 
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] #2236: REQUIREMENTS file not clear about compilation and priority

[GRASS GIS]

#2236: REQUIREMENTS file not clear about compilation and priority
-+-
  Reporter:  wenzeslaus  |  Owner:  grass-dev@…
  Type:  task| Status:  new
  Priority:  trivial |  Milestone:  7.8.0
 Component:  Docs|Version:  svn-trunk
Resolution:  |   Keywords:  compilation, requirements,
   CPU:  |  dependencies
  Unspecified|   Platform:  Unspecified
-+-
Changes (by sbl):

 * milestone:  7.0.7 => 7.8.0


Comment:

 Bumping it to 7.8

-- 
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] #2525: Unable to open sqlite database if path contains non-latin letters

[GRASS GIS]

#2525: Unable to open sqlite database if path contains non-latin letters
--+-
  Reporter:  marisn   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  major|  Milestone:  7.6.2
 Component:  wxGUI|Version:  svn-releasebranch70
Resolution:   |   Keywords:  attribute
   CPU:  Unspecified  |   Platform:  MSWindows Vista
--+-
Changes (by sbl):

 * milestone:  7.0.7 => 7.6.2


Comment:

 In 7.6, the state is actually worse, if the mapset contains non-ascii
 characters...

 With mapset "tøst", GUI does not start up. Also maps with name tøst cannot
 be created:

 {{{
 v.edit map=test tool=create
 WARNING: Illegal filename . Character  not allowed.
 }}}

-- 
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] #3650: Cartographic composer: scale and rotation options do not work for north arrow

[GRASS GIS]

#3650: Cartographic composer: scale and rotation options do not work for north
arrow
--+-
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Ps.map   |Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by veroandreo):

 * version:  unspecified => svn-trunk
 * component:  Default => Ps.map
 * milestone:   => 7.8.0


-- 
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] #1105: un-red the trac theme

[GRASS GIS]

#1105: un-red the trac theme
--+-
  Reporter:  hamish   |  Owner:  grass-dev@…
  Type:  task | Status:  new
  Priority:  minor|  Milestone:  Website
 Component:  Website  |Version:
Resolution:   |   Keywords:  trac theme
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by sbl):

 Still relevant? Also after move to git?

-- 
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]

Hola :)

El mar., 7 may. 2019 a las 16:20, Veronica Andreo ()
escribió:

> 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).
>>
>
Any other opinion/objection? Shall I post on FB and Twitter then? New
announcement here with deadline?

Vero

>
> +1! :)
>
> Vero
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #3841: script/core.py: create_location() fails with FileNotFoundError: [Errno 2] No such file or directory: '/tmp/grass7-root-94/tmploc/PERMANENT/MYNAME'

[GRASS GIS]

#3841: script/core.py: create_location() fails with FileNotFoundError: [Errno 2]
No such file or directory: '/tmp/grass7-root-94/tmploc/PERMANENT/MYNAME'
---+-
 Reporter:  neteler|  Owner:  grass-dev@…
 Type:  defect | Status:  new
 Priority:  normal |  Milestone:  7.8.0
Component:  Python |Version:  svn-trunk
 Keywords:  python3, grass.py  |CPU:  x86-64
 Platform:  Linux  |
---+-
 In a docker environment (Ubuntu 18:04 based) I get this startup error with
 trunk (on a pure Python 3 environment):

 {{{
 # note: the second line from bottom is local debug output via print()

 root@6ade79b80a2b:/grassdb# grass --tmp-location EPSG:25832 --exec
 g.extension -s extension=i.sentinel url=/src/i.sentinel
 Starting GRASS GIS...
 Creating new GRASS GIS location ...
 /tmp/grass7-root-37 tmploc EPSG:25832
 ERROR: FileNotFoundError(2, 'No such file or directory')
 }}}

 With Python debugger (pdb) I see that it cannot open a file with
 `codecs.open()`:

 {{{
 root@6ade79b80a2b:/grassdb# grass --tmp-location EPSG:25832 --exec
 g.extension -s extension=i.sentinel url=/src/i.sentinel
 Starting GRASS GIS...
 Creating new GRASS GIS location ...
 /tmp/grass7-root-94 tmploc EPSG:25832
 25832 None
 > /usr/local/bin/grass(853)create_location()
 -> gcore.create_location(gisdbase, location,
 (Pdb) s
 > /usr/local/bin/grass(854)create_location()
 -> epsg=epsg, datum_trans=datum_trans)
 (Pdb) s
 --Call--
 >
 /usr/local/grass77/etc/python/grass/script/core.py(1518)create_location()
 -> def create_location(dbase, location, epsg=None, proj4=None,
 filename=None,
 (Pdb) s
 >
 /usr/local/grass77/etc/python/grass/script/core.py(1538)create_location()
 -> gisdbase = None
 (Pdb) s
 >
 /usr/local/grass77/etc/python/grass/script/core.py(1539)create_location()
 -> if epsg or proj4 or filename or wkt:
 (Pdb) s
 >
 /usr/local/grass77/etc/python/grass/script/core.py(1541)create_location()
 -> gisdbase = gisenv()['GISDBASE']
 (Pdb) s
 --Call--
 > /usr/local/grass77/etc/python/grass/script/core.py(1075)gisenv()
 -> def gisenv(env=None):
 (Pdb) s
 > /usr/local/grass77/etc/python/grass/script/core.py(1086)gisenv()
 -> s = read_command("g.gisenv", flags='n', env=env)
 (Pdb) s
 --Call--
 > /usr/local/grass77/etc/python/grass/script/core.py(491)read_command()
 -> def read_command(*args, **kwargs):
 (Pdb) s
 > /usr/local/grass77/etc/python/grass/script/core.py(500)read_command()
 -> encoding = 'default'
 (Pdb) s
 > /usr/local/grass77/etc/python/grass/script/core.py(501)read_command()
 -> if 'encoding' in kwargs:
 (Pdb) s
 > /usr/local/grass77/etc/python/grass/script/core.py(504)read_command()
 -> if _capture_stderr and 'stderr' not in kwargs.keys():
 (Pdb) s
 > /usr/local/grass77/etc/python/grass/script/core.py(506)read_command()
 -> process = pipe_command(*args, **kwargs)

 [...]

 > /usr/local/grass77/etc/python/grass/script/core.py(512)read_command()
 -> if _capture_stderr and returncode:
 (Pdb) n
 > /usr/local/grass77/etc/python/grass/script/core.py(514)read_command()
 -> return handle_errors(returncode, stdout, args, kwargs)
 (Pdb) n
 --Return--
 >
 
/usr/local/grass77/etc/python/grass/script/core.py(514)read_command()->'GISDBASE=/gr...T=\n'
 -> return handle_errors(returncode, stdout, args, kwargs)
 (Pdb) n
 > /usr/local/grass77/etc/python/grass/script/core.py(1087)gisenv()
 -> return parse_key_val(s)
 (Pdb) n
 --Return--
 >
 /usr/local/grass77/etc/python/grass/script/core.py(1087)gisenv()->{'GISDBASE':
 ...: ''}
 -> return parse_key_val(s)
 (Pdb) n
 >
 /usr/local/grass77/etc/python/grass/script/core.py(1542)create_location()
 -> run_command('g.gisenv', set='GISDBASE=%s' % dbase)
 (Pdb) n
 >
 /usr/local/grass77/etc/python/grass/script/core.py(1544)create_location()
 -> if not os.path.exists(dbase):
 (Pdb) n
 >
 /usr/local/grass77/etc/python/grass/script/core.py(1548)create_location()
 -> if os.path.exists(os.path.join(dbase, location)):
 (Pdb) n
 >
 /usr/local/grass77/etc/python/grass/script/core.py(1556)create_location()
 -> kwargs = dict()
 (Pdb) n
 >
 /usr/local/grass77/etc/python/grass/script/core.py(1557)create_location()
 -> if datum:
 (Pdb) n
 >
 /usr/local/grass77/etc/python/grass/script/core.py(1559)create_location()
 -> if datum_trans:
 (Pdb) n
 >
 /usr/local/grass77/etc/python/grass/script/core.py(1562)create_location()
 -> if epsg:
 (Pdb) n
 >
 /usr/local/grass77/etc/python/grass/script/core.py(1563)create_location()
 -> ps = pipe_command('g.proj', quiet=True, flags='t', epsg=epsg,
 (Pdb) n
 >
 /usr/local/grass77/etc/python/grass/script/core.py(1564)create_location()
 -> location=location, stderr=PIPE, **kwargs)
 (Pdb) n
 >
 /usr/local/grass77/etc/python/grass/script/core.py(1577)create_location()
 -> if epsg or proj4 or filename or wkt:
 (Pdb) n
 >
 /usr/local/grass77/etc/python/grass/script/core.py(1578)create_location()
 -> error = ps.communicate()[1]

Re: [GRASS-dev] pygrass.gis.region.Region + depths property

[Panagiotis Mavrogiorgos]

On Thu, May 9, 2019 at 4:20 PM Panagiotis Mavrogiorgos 
wrote:

> Hello all,
>
> The Region class defines a ["depths" property](
> https://github.com/GRASS-GIS/grass-ci/blob/6451c5aa008d59506f7fb8ce54e0b72eb2188ad2/lib/python/pygrass/gis/region.py#L210-L219)
> which is not being used in e.g. .keys(), __repr__(), __eq__() etc.
> Shouldn't it be added there too?
>
> with kind regards
> Panos
>

In the same topic, shouldn't the property setter (i.e. _set_depths) call
adjust()? In which case, shouldn't adjust() call G_adjust_Cell_head3()
instead of G_adjust_Cell_head()?

Should I open an issue?

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

[GRASS-dev] pygrass.gis.region.Region + depths property

[Panagiotis Mavrogiorgos]

Hello all,

The Region class defines a ["depths" property](
https://github.com/GRASS-GIS/grass-ci/blob/6451c5aa008d59506f7fb8ce54e0b72eb2188ad2/lib/python/pygrass/gis/region.py#L210-L219)
which is not being used in e.g. .keys(), __repr__(), __eq__() etc.
Shouldn't it be added there too?

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

Re: [GRASS-dev] FYI: Season of the Docs

[Moritz Lennert]

On 9/05/19 10:08, Panagiotis Mavrogiorgos wrote:

Hello all,

This year google launched a new project similar to Summer of Code whose 
scope is improving documentation. The deadline has passed but it might 
make sense to keep it in mind for next year:


https://developers.google.com/season-of-docs/

There is an announcement mailing list, so it might be a good idea for 
some core member to subscribe: 
https://groups.google.com/forum/#!forum/season-of-docs-announce


Generally all GSoC or similar events are handled centrally via OSGeo 
with individual projects providing ideas.


This year, OSGeo has been accepted as organisation: 
https://wiki.osgeo.org/wiki/Season_Of_Docs_2019


For GSoC, see:
See https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2019


Markus did transmit the info to the list:

https://lists.osgeo.org/pipermail/grass-dev/2019-April/091819.html


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

Re: [GRASS-dev] [GRASS GIS] #3166: Parallelization with tiling for grass.script

[GRASS GIS]

#3166: Parallelization with tiling for grass.script
--+--
  Reporter:  wenzeslaus   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Python   |Version:  unspecified
Resolution:   |   Keywords:  script, parallel
   CPU:  Unspecified  |   Platform:  Unspecified
--+--
Changes (by martinl):

 * milestone:  7.6.2 => 7.8.0


Comment:

 It seems that `grass.script.parallel` is not even part of trunk.

 {{{
 grass7_trunk/lib/python/script$ ls *.py
 array.py  core.py  db.py  __init__.py  raster3d.py  raster.py  setup.py
 task.py  utils.py  vector.py
 }}}

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] FYI: Season of the Docs

[Panagiotis Mavrogiorgos]

Hello all,

This year google launched a new project similar to Summer of Code whose
scope is improving documentation. The deadline has passed but it might make
sense to keep it in mind for next year:

https://developers.google.com/season-of-docs/

There is an announcement mailing list, so it might be a good idea for some
core member to subscribe:
https://groups.google.com/forum/#!forum/season-of-docs-announce

with kind regards,
Panos
___
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]

Thank you markus

On Wed, May 8, 2019 at 10:54 PM Markus Metz 
wrote:

> It depends. g.mapset changes the current mapset (and location and
> database). It might also create a new mapset in an existing location, but
> it always switches. If that switch is not desired, GISRC must be adjusted
> to the original GRASS session. G_make_mapset() is a C function and should
> be used by C modules. Of course you could use it with pygrass, but pygrass
> initializes the GRASS C libraries, and you need to take care that
> initializations are properly updated when changing mapsets (and locations).
> Creating a new mapset in an existing location is not difficult: create the
> folder and copy DEFAULT_WIND from PERMANENT to WIND in the new mapset.
> Maybe create a new function create_mapset() in lib/python/script/utils.py?
>

Generally speaking, I think it is important that the API comes first. Once
some functionality has been implemented in a library it can then be exposed
to the end users in multiple ways (e.g. CLI, REST, whatever). Among other
things, by implementing the API first, it is much easier to test the code +
you follow DRY.

This is why I mentioned "G_make_mapset()" which seems to already be
implementing this functionality and which, as you mentioned, is exposed to
Python via pygrass. The idea is that if in the future the process of
creating a mapset becomes more complicated, then we would only have to
update "G_make_mapset()". That being said I am not familiar enough with the
initialization process so I can't really argue if a pure python
implementation is needed or not.

Now to become more specific, as an API user, I think would find it strange
that calling the "create_mapset()" function also changes the current
mapset. I like it when things are explicit + it makes it easier to document
and test. As far as implementing "create_mapset()" in
lib/python/script/utils.py, why not move the relevant functions from
"gui/wxpython/startup/utils.py" and have the GUI code import them from the
"grass" lib?

BTW, those functions do need a few improvements; e.g. rename_mapset()
should fail to rename PERMANENT etc, but let's move them first and we can
do that later.


> >>> I adjusted the wxGUI startup wizard and the tests in trunk r74472,3
> (the tests should use g.mapset -c, not yet implemented)
> >
> >
> > I think that in the nc_spm_full_v2alpha dataset WIND and DEFAULT_WIND
> differ, so 74473 might break any tests that don't explicitly set the region
> themselves (which of course they should). We will see.
>
> IMHO, tests need to set the region themselves, just as users. The current
> region is such a fundamental concept of GRASS (raster processing) that I
> regard it as a mistake if the current region is not explicitly set to
> actual demands.
>

I completely agree that tests that don't set the region themselves should
be fixed.

all the best,
Panos
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev