date:20180228

Re: [GRASS-dev] [GRASS GIS] #2762: more informative error messages in lib/rast/get_row.c

2018-02-28 Thread GRASS GIS

#2762: more informative error messages in lib/rast/get_row.c
--+---
  Reporter:  dylan|  Owner:  grass-dev@…
  Type:  enhancement  | Status:  reopened
  Priority:  minor|  Milestone:  7.4.1
 Component:  Raster   |Version:  svn-trunk
Resolution:   |   Keywords:  error message
   CPU:  All  |   Platform:  All
--+---

Comment (by neteler):

 Replying to [comment:13 martinl]:
 > What exactly should be backported?

 I think these msg improvements (from #3499):
  * r72030 libraster: more informative messages when reading a row fails
  * r72031 libgis: more informative messages when (de)compression fails
  * r72042 libgis: add warnings when writing compressed data fails

-- 
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] #3416: t.list: add mapset option as in g.list

2018-02-28 Thread GRASS GIS

#3416: t.list: add mapset option as in g.list
--+
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  closed
  Priority:  normal   |  Milestone:  7.4.1
 Component:  Temporal |Version:  svn-trunk
Resolution:  fixed|   Keywords:  t.list, mapset
   CPU:  Unspecified  |   Platform:  Unspecified
--+
Changes (by martinl):

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


Comment:

 Feel free to reopen if desired.

-- 
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] #3349: v.import: add 'where' parameter

2018-02-28 Thread GRASS GIS

#3349: v.import: add 'where' parameter
--+
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.4.1
 Component:  Vector   |Version:  unspecified
Resolution:   |   Keywords:  v.import where
   CPU:  Unspecified  |   Platform:  Unspecified
--+

Comment (by martinl):

 What is status of this ticket?

-- 
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] #2762: more informative error messages in lib/rast/get_row.c

2018-02-28 Thread GRASS GIS

#2762: more informative error messages in lib/rast/get_row.c
--+---
  Reporter:  dylan|  Owner:  grass-dev@…
  Type:  enhancement  | Status:  reopened
  Priority:  minor|  Milestone:  7.4.1
 Component:  Raster   |Version:  svn-trunk
Resolution:   |   Keywords:  error message
   CPU:  All  |   Platform:  All
--+---

Comment (by martinl):

 What exactly should be backported?

-- 
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] #2676: r.neighbors on large rasters

2018-02-28 Thread GRASS GIS

#2676: r.neighbors  on large rasters
--+---
  Reporter:  dnewcomb |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  closed
  Priority:  normal   |  Milestone:  7.4.1
 Component:  Default  |Version:  svn-trunk
Resolution:  wontfix  |   Keywords:  r.neighbors large rasters
   CPU:  x86-64   |   Platform:  Linux
--+---
Changes (by martinl):

 * status:  reopened => closed
 * resolution:   => wontfix


Comment:

 No activity last 3 years, closing. Feel free to reopen if desired.

-- 
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] #1938: r.fillnulls: per hole filling speed-up

2018-02-28 Thread GRASS GIS

#1938: r.fillnulls: per hole filling speed-up
--+-
  Reporter:  sbl  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  reopened
  Priority:  normal   |  Milestone:  7.4.1
 Component:  Python   |Version:  svn-trunk
Resolution:   |   Keywords:  r.fillnulls
   CPU:  All  |   Platform:  All
--+-

Comment (by martinl):

 See also G74:r.fill.stats

-- 
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] #3177: Automatically register addons in GUI

2018-02-28 Thread GRASS GIS

#3177: Automatically register addons in GUI
--+--
  Reporter:  sbl  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  minor|  Milestone:  7.4.1
 Component:  Addons   |Version:  unspecified
Resolution:   |   Keywords:  g.extension,Makefile
   CPU:  Unspecified  |   Platform:  All
--+--

Comment (by hellik):

 Replying to [comment:2 martinl]:
 > Already done, Addons are visible in Modules tab (after restarting the
 GUI). Time to close this issue?

 AFAIK only C addons are added to the Modules tab, but not python addons;
 behaviour seen in winGRASS.

-- 
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] #3505: Opening a workspace file

2018-02-28 Thread GRASS GIS

#3505: Opening a workspace file
--+-
  Reporter:  clerici  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  major|  Milestone:  7.4.1
 Component:  wxGUI|Version:  7.4.0
Resolution:   |   Keywords:  wingrass
   CPU:  Unspecified  |   Platform:  MSWindows 8
--+-

Comment (by hellik):

 Replying to [comment:5 martinl]:
 > No traceback in Console?

 set DEBUG=3 and then opened the workspace

 {{{
 C:\>D1/3: G_set_program_name(): g.gisenv
 D3/3: G_option_to_separator(): key = separator -> sep = '
 '
 D1/3: G_set_program_name(): g.gisenv
 D3/3: G_option_to_separator(): key = separator -> sep = '
 '
 D1/3: grass.script.core.start_command(): g.tempfile -d pid=12544
 D1/3: G_set_program_name(): g.tempfile
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1
 D2/3: G__temp_element(): .tmp/unknown (tmp=0)
 D2/3: G_file_name(): path =
 D:\grassdata\nc_spm_08_grass7\user1\.tmp/unknown\12544.0
 D2/3: G_tempfile_pid():
 D:\grassdata\nc_spm_08_grass7\user1\.tmp/unknown\12544.0
 D1/3: grass.script.core.start_command(): g.tempfile -d pid=12544
 D1/3: G_set_program_name(): g.tempfile
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1
 D2/3: G__temp_element(): .tmp/unknown (tmp=0)
 D2/3: G_file_name(): path =
 D:\grassdata\nc_spm_08_grass7\user1\.tmp/unknown\12544.0
 D2/3: G_tempfile_pid():
 D:\grassdata\nc_spm_08_grass7\user1\.tmp/unknown\12544.0
 D1/3: grass.script.core.start_command(): g.gisenv -n
 D1/3: G_set_program_name(): g.gisenv
 D3/3: G_option_to_separator(): key = separator -> sep = '
 '
 D1/3: grass.script.core.start_command(): g.proj -p
 D1/3: grass.script.core.start_command(): g.region -ugpc
 D1/3: grass.script.core.start_command(): g.gisenv -n
 D1/3: G_set_program_name(): g.gisenv
 D3/3: G_option_to_separator(): key = separator -> sep = '
 '
 D1/3: grass.script.core.start_command(): g.findfile -n mapset=user1
 file=MASK element=cell
 D1/3: G_set_program_name(): g.findfile
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1\cell\MASK
 D1/3: grass.script.core.start_command(): g.gisenv -n
 D1/3: G_set_program_name(): g.gisenv
 D3/3: G_option_to_separator(): key = separator -> sep = '
 '
 D1/3: grass.script.core.start_command(): g.findfile -n mapset=user1
 file=MASK element=cell
 D1/3: G_set_program_name(): g.findfile
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1\cell\MASK
 D1/3: grass.script.core.start_command(): g.gisenv -n
 D1/3: G_set_program_name(): g.gisenv
 D3/3: G_option_to_separator(): key = separator -> sep = '
 '
 D1/3: grass.script.core.start_command(): g.gisenv -n
 D1/3: G_set_program_name(): g.gisenv
 D3/3: G_option_to_separator(): key = separator -> sep = '
 '
 D1/3: grass.script.core.start_command(): g.findfile -n mapset=user1
 file=MASK element=cell
 D1/3: G_set_program_name(): g.findfile
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1\cell\MASK
 D1/3: grass.script.core.start_command(): g.gisenv -n
 D1/3: G_set_program_name(): g.gisenv
 D3/3: G_option_to_separator(): key = separator -> sep = '
 '
 D1/3: grass.script.core.start_command(): g.findfile -n mapset=user1
 file=MASK element=cell
 D1/3: G_set_program_name(): g.findfile
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1\cell\MASK
 D1/3: grass.script.core.start_command(): g.region -ugpc s=215000.0
 e=645000.0 w=63.0 n=228500.0
 D1/3: grass.script.core.start_command(): g.gisenv -n
 D1/3: G_set_program_name(): g.gisenv
 D3/3: G_option_to_separator(): key = separator -> sep = '
 '
 D1/3: grass.script.core.start_command(): g.findfile -n mapset=user1
 file=MASK element=cell
 D1/3: G_set_program_name(): g.findfile
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1\cell\MASK
 D1/3: grass.script.core.start_command(): g.gisenv -n
 D1/3: G_set_program_name(): g.gisenv
 D3/3: G_option_to_separator(): key = separator -> sep = '
 '
 D1/3: grass.script.core.start_command(): g.findfile -n mapset=user1
 file=MASK element=cell
 D1/3: G_set_program_name(): g.findfile
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1\cell\MASK
 D1/3: grass.script.core.start_command(): g.tempfile pid=12544
 D1/3: G_set_program_name(): g.tempfile
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1
 D2/3: G_file_name(): path = D:\grassdata\nc_spm_08_grass7\user1
 D2/3:

Re: [GRASS-dev] [GRASS GIS] #3505: Opening a workspace file

2018-02-28 Thread GRASS GIS

#3505: Opening a workspace file
--+-
  Reporter:  clerici  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  major|  Milestone:  7.4.1
 Component:  wxGUI|Version:  7.4.0
Resolution:   |   Keywords:  wingrass
   CPU:  Unspecified  |   Platform:  MSWindows 8
--+-

Comment (by hellik):

 Replying to [comment:5 martinl]:
 > Replying to [comment:2 hellik]:
 >
 > > and confirmed. moving/deleting layers isn't possible.
 >
 > It's not possible to move/delete layers only from open workspace or also
 after adding few layers into new workspace?
 >
 > No traceback in Console?
 >
 > Reporter claims that this bug is not included in GRASS 7.2.2. It's
 strange, there is the same wxPython version, and apparently it's only
 Windows related.

 workflow:

 {{{
 d.rast map=elevation@PERMANENT
 d.vect map=streams@PERMANENT color=blue fill_color=blue width=1
 d.vect map=firestations@PERMANENT width=1 icon=extra/target size=15
 }}}

 {{{
 save workspace as g74.gxw
 }}}

 {{{
 
 
 
 
 
 
 
 
 
 
 15
 
 
 firestations@PERMANENT
 
 
 extra/target
 
 
 1
 
 
 
 
 
 
 blue
 
 
 streams@PERMANENT
 
 
 blue
 
 
 1
 
 
 
 
 
 
 elevation@PERMANENT
 
 
 
 
 
 }}}

 closing winGRASS7.4.0 session, then re-opening winGRASS7.4.0

 opening workspace g74.gxw

 => not possible to move/delete layers from open workspace

 then add a new layer

 {{{
 d.vect map=bridges@PERMANENT width=1 icon=extra/bridge size=15
 }}}

 => not possible to move/delete layers from open workspace **and** not
 possible to move/delete new added layer.

 no traceback in console

-- 
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] #3290: i.segement references

2018-02-28 Thread GRASS GIS

#3290: i.segement references
-+-
  Reporter:  wenzeslaus  |  Owner:  grass-dev@…
  Type:  | Status:  new
  enhancement|
  Priority:  trivial |  Milestone:  7.4.1
 Component:  Imagery |Version:  svn-trunk
Resolution:  |   Keywords:  i.segment, references, doc,
   CPU:  |  documentation, man
  Unspecified|   Platform:  Unspecified
-+-

Comment (by martinl):

 What is status of this ticket?

-- 
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] #26: please let people find their EPSG on the web

2018-02-28 Thread GRASS GIS

#26: please let people find their EPSG on the web
--+
  Reporter:  timmie   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  closed
  Priority:  trivial  |  Milestone:  7.4.1
 Component:  wxGUI|Version:  unspecified
Resolution:  wontfix  |   Keywords:  wxgui, location-wizard
   CPU:  Unspecified  |   Platform:  Unspecified
--+
Changes (by martinl):

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


Comment:

 Closing, please feel free to reopen if desired.

-- 
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] #3177: Automatically register addons in GUI

2018-02-28 Thread GRASS GIS

#3177: Automatically register addons in GUI
--+--
  Reporter:  sbl  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  minor|  Milestone:  7.4.1
 Component:  Addons   |Version:  unspecified
Resolution:   |   Keywords:  g.extension,Makefile
   CPU:  Unspecified  |   Platform:  All
--+--

Comment (by martinl):

 Already done, Addons are visible in Modules tab (after restarting the
 GUI). Time to close this issue?

-- 
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] #3050: Set size in d.northarrow

2018-02-28 Thread GRASS GIS

#3050: Set size in d.northarrow
-+-
  Reporter:  wenzeslaus  |  Owner:  grass-dev@…
  Type:  | Status:  new
  enhancement|
  Priority:  minor   |  Milestone:  7.4.1
 Component:  Display |Version:  svn-trunk
Resolution:  |   Keywords:  d.northarrow, cartography, gsoc2016
   CPU:  |   Platform:  Unspecified
  Unspecified|
-+-

Comment (by martinl):

 Can we close the issue?

-- 
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] #2234: wxGUI d.mon and g.gui monitor rendering is slow

2018-02-28 Thread GRASS GIS

#2234: wxGUI d.mon and g.gui monitor rendering is slow
--+
  Reporter:  wenzeslaus   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  minor|  Milestone:  7.4.1
 Component:  wxGUI|Version:  unspecified
Resolution:   |   Keywords:  rendering, display
   CPU:  Unspecified  |   Platform:  All
--+

Comment (by martinl):

 Almost 2 years no activity. Closing, feel free to reopen if needed.

-- 
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] #2234: wxGUI d.mon and g.gui monitor rendering is slow

2018-02-28 Thread GRASS GIS

#2234: wxGUI d.mon and g.gui monitor rendering is slow
--+
  Reporter:  wenzeslaus   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  closed
  Priority:  minor|  Milestone:  7.4.1
 Component:  wxGUI|Version:  unspecified
Resolution:  fixed|   Keywords:  rendering, display
   CPU:  Unspecified  |   Platform:  All
--+
Changes (by martinl):

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


-- 
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] #3506: 3D view mode not available: Reason: name '__int64' is not defined

2018-02-28 Thread GRASS GIS

#3506: 3D view mode not available: Reason: name '__int64' is not defined
-+-
 Reporter:  hellik   |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  major|  Milestone:  7.4.1
Component:  wxGUI|Version:  7.4.0
 Keywords:   |CPU:  Unspecified
 Platform:  MSWindows 8  |
-+-
 tested with

 {{{
 System Info
 GRASS version: 7.5.svn
 GRASS SVN revision: r72285
 Build date: 2018-01-27
 Build platform: x86_64-w64-mingw32
 GDAL: 2.2.3
 PROJ.4: 4.9.3
 GEOS: 3.5.0
 SQLite: 3.17.0
 Python: 2.7.5
 wxPython: 2.8.12.1
 Platform: Windows-8-6.2.9200 (OSGeo4W)
 }}}

 after starting the GUI, there is following error message in the wxGUI
 output window:

 {{{
 3D view mode not available: Reason: name '__int64' is not defined
 }}}

-- 
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] #3505: Opening a workspace file

2018-02-28 Thread GRASS GIS

#3505: Opening a workspace file
--+-
  Reporter:  clerici  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  major|  Milestone:  7.4.1
 Component:  wxGUI|Version:  7.4.0
Resolution:   |   Keywords:  wingrass
   CPU:  Unspecified  |   Platform:  MSWindows 8
--+-

Comment (by martinl):

 Replying to [comment:2 hellik]:

 > and confirmed. moving/deleting layers isn't possible.

 It's not possible to move/delete layers only from open workspace or also
 after adding few layers into new workspace?

 No traceback in Console?

 Reporter claims that this bug is not included in GRASS 7.2.2. It's
 strange, there is the same wxPython version, and apparently it's only
 Windows related.

-- 
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] #3505: Opening a workspace file

2018-02-28 Thread GRASS GIS

#3505: Opening a workspace file
--+-
  Reporter:  clerici  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  major|  Milestone:  7.4.1
 Component:  wxGUI|Version:  7.4.0
Resolution:   |   Keywords:  wingrass
   CPU:  Unspecified  |   Platform:  MSWindows 8
--+-
Changes (by hellik):

 * priority:  normal => major
 * platform:  Unspecified => MSWindows 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] #3505: Opening a workspace file

2018-02-28 Thread GRASS GIS

#3505: Opening a workspace file
--+-
  Reporter:  clerici  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.4.1
 Component:  wxGUI|Version:  7.4.0
Resolution:   |   Keywords:  wingrass
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by hellik):

 Replying to [comment:1 martinl]:
 > I cannot reproduce this bug on Linux. It's probably Windows related. Can
 anyone else on Windows reproduce it?

 tested also with

 {{{
 System Info
 GRASS version: 7.5.svn
 GRASS SVN revision: r72285
 Build date: 2018-01-27
 Build platform: x86_64-w64-mingw32
 GDAL: 2.2.3
 PROJ.4: 4.9.3
 GEOS: 3.5.0
 SQLite: 3.17.0
 Python: 2.7.5
 wxPython: 2.8.12.1
 Platform: Windows-8-6.2.9200 (OSGeo4W)
 }}}

 and confirmed. moving/deleting layers isn't possible.

-- 
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] #3505: Opening a workspace file

2018-02-28 Thread GRASS GIS

#3505: Opening a workspace file
--+-
  Reporter:  clerici  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.4.1
 Component:  wxGUI|Version:  7.4.0
Resolution:   |   Keywords:  wingrass
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by hellik):

 Replying to [comment:1 martinl]:
 > I cannot reproduce this bug on Linux. It's probably Windows related. Can
 anyone else on Windows reproduce it?

 tested by

 {{{
 System Info
 GRASS version: 7.4.0
 GRASS SVN revision: r72154
 Build date: 2018-01-27
 Build platform: x86_64-w64-mingw32
 GDAL: 2.2.3
 PROJ.4: 4.9.3
 GEOS: 3.5.0
 SQLite: 3.17.0
 Python: 2.7.5
 wxPython: 2.8.12.1
 Platform: Windows-8-6.2.9200 (OSGeo4W)
 }}}

 and confirmed. moving/deleting layers isn't possible.

-- 
Ticket URL: 
GRASS GIS 

___
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

2018-02-28 Thread Markus Metz

On Wed, Feb 28, 2018 at 3:38 PM, Markus Neteler  wrote:
>
> Hi Sanjeet,
>
> On Tue, Feb 27, 2018 at 3:08 AM, Sanjeet  wrote:
> > Hi,
> >
> > My name is Sanjeet Bhatti and I am an MSc. student in Computer Science
> > from University of Saskatchewan, Canada. I was going through the list
> > of GSOC project ideas of GRASS GIS and I found one that caught my
> > interest: "Full support of Python 3 in GRASS GIS".
>
> That's great and for sure an important topic to work on!
>
> > I am familiar with python programming as well as have a basic
> > understanding of wxPython. Currently, I am setting up my development
> > environment by checking out the development branch (trunk) of GRASS 7
> > available at this link[0].
> > Are there any initial tasks that I should be doing apart from listing
> > the generally used solutions for migrating from Python 2 to 3? And,
> > where do I need to submit these?
>
> There are some tickets flagged with "python3":
> https://trac.osgeo.org/grass/query?status=!closed=~python3

What is the policy about the python shebang explained in python PEP 394
https://www.python.org/dev/peps/pep-0394/

-->
In order to tolerate differences across platforms, all new code that needs
to invoke the Python interpreter should not specify python, but rather
should specify either python2 or python3 (or the more specific python2.x
and python3.x versions; see the Migration Notes). This distinction should
be made in shebangs, when invoking from a shell script, when invoking via
the system() call, or when invoking in any other context.
<--

... unless scripts are deliberately written to be source compatible with
both Python 2.x and 3.x

Currently packagers replace python with python2 in the shebang of GRASS
scripts.

Markus M

>
> 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
>
> Best
> Markus
>
>
>
> > Thank you,
> > Sanjeet
> >
> > [0] svn.osgeo.org/grass/grass/
> > ___
> > 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 mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3505: Opening a workspace file

2018-02-28 Thread GRASS GIS

#3505: Opening a workspace file
--+-
  Reporter:  clerici  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.4.1
 Component:  wxGUI|Version:  7.4.0
Resolution:   |   Keywords:  wingrass
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by martinl):

 * keywords:   => wingrass
 * component:  Default => wxGUI
 * milestone:   => 7.4.1


Comment:

 I cannot reproduce this bug on Linux. It's probably Windows related. Can
 anyone else on Windows reproduce it?

-- 
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] #3505: Opening a workspace file

2018-02-28 Thread GRASS GIS

#3505: Opening a workspace file
-+-
 Reporter:  clerici  |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  normal   |  Milestone:
Component:  Default  |Version:  7.4.0
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 When a saved setting is loaded (Files > Workspace > Open) in my GRASS7.4.0
 for Windows, the maps are correctly listed in the Layer Manager and
 displayed in the Map Display, but in the Layer Manager no action (delete,
 move, etc) is possible on the listed maps.

 Platform Windows 8  and Windows 10.
 It  works on WinGrass 7.2.2

-- 
Ticket URL: 
GRASS GIS 

___
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

2018-02-28 Thread Markus Neteler

Hi Sanjeet,

On Tue, Feb 27, 2018 at 3:08 AM, Sanjeet  wrote:
> Hi,
>
> My name is Sanjeet Bhatti and I am an MSc. student in Computer Science
> from University of Saskatchewan, Canada. I was going through the list
> of GSOC project ideas of GRASS GIS and I found one that caught my
> interest: "Full support of Python 3 in GRASS GIS".

That's great and for sure an important topic to work on!

> I am familiar with python programming as well as have a basic
> understanding of wxPython. Currently, I am setting up my development
> environment by checking out the development branch (trunk) of GRASS 7
> available at this link[0].
> Are there any initial tasks that I should be doing apart from listing
> the generally used solutions for migrating from Python 2 to 3? And,
> where do I need to submit these?

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

Best
Markus



> Thank you,
> Sanjeet
>
> [0] svn.osgeo.org/grass/grass/
> ___
> 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] Geomorphometry conference 2018 (Boulder, CO) - deadlines extended

2018-02-28 Thread Carlos Grohmann

New deadlines for the Geomorphometry conference!!

http://2018.geomorphometry.org

Don't miss this opportunity!

*Importante dates:*

   - Extended 4 page abstracts due: 15 March 2018
   - Workshop proposals due: 15 March 2018
   - Notification of acceptance and required revisions: 31 March 2018
   - Registration opens: 1 April 2018
   - Final camera-ready digital manuscripts due: 15 May 2018
   - Early registration deadline: 15 July 2018
   - Conference: August 13-17 2018



EasyChair system 


*Conference themes and publications*

Themes include but are not limited to:


   - Use of Digital Elevation, Terrain and Surface Models and Canopy Heigh
   Models in hydrological modeling and biogeography
   - Acquisition and processing of high resolution elevation data collected
   with LIDAR and photogrammetry (structure from motion)
   - Mapping and analyzing Earth surface at ultra-high resolutions using
   sUAS (small Unmanned Aerial Systems)
   - New algorithms and software for automated interpretation of digital
   elevation data
   - Modeling extreme processes and natural hazards on the Earth surface
   - Modeling and analyzing urban topography (3D cities) using lidar or
   photogrammetry data
   - Multi-scale automated mapping of Earth surface changes
   - Acquisition and analysis of bathymetry data
   - Working with continental-scale high resolution data
   - Simulating changes of the Earth surface relief
   - 3D and 4D dynamics of Earth surface

Peer reviewed proceedings will be published online, with DOIs. One or more
special journal issues planned.



best

Carlos

-- 
Prof. Carlos Henrique Grohmann
Institute of Energy and Environment - Univ. of São Paulo, Brazil
- Digital Terrain Analysis | GIS | Remote Sensing -

http://carlosgrohmann.com
http://orcid.org/-0001-5073-5572

Can’t stop the signal.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Future of external Processing providers in QGIS

2018-02-28 Thread Paolo Cavallini

Il 27/02/2018 19:59, Markus Neteler ha scritto:
> Hi Paolo,
> 
> (reducing to grass-dev)
> 
> thanks for your detailed summary! I have just added a related agenda item to
> https://grasswiki.osgeo.org/wiki/GRASS_GIS_Community_Sprint_Bonn_2018#Agenda_-_What_we_plan_to_do

Glad you appreciated it - I think it was an excellent example of how
things can go, democratically, in GFOSS community.
Looking forward for further progress on this. Of course I'm available
for help.
All the best.

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #2762: more informative error messages in lib/rast/get_row.c

Re: [GRASS-dev] [GRASS GIS] #3416: t.list: add mapset option as in g.list

Re: [GRASS-dev] [GRASS GIS] #3349: v.import: add 'where' parameter

Re: [GRASS-dev] [GRASS GIS] #2762: more informative error messages in lib/rast/get_row.c

Re: [GRASS-dev] [GRASS GIS] #2676: r.neighbors on large rasters

Re: [GRASS-dev] [GRASS GIS] #1938: r.fillnulls: per hole filling speed-up

Re: [GRASS-dev] [GRASS GIS] #3177: Automatically register addons in GUI

Re: [GRASS-dev] [GRASS GIS] #3505: Opening a workspace file

Re: [GRASS-dev] [GRASS GIS] #3505: Opening a workspace file

Re: [GRASS-dev] [GRASS GIS] #3290: i.segement references

Re: [GRASS-dev] [GRASS GIS] #26: please let people find their EPSG on the web

Re: [GRASS-dev] [GRASS GIS] #3177: Automatically register addons in GUI

Re: [GRASS-dev] [GRASS GIS] #3050: Set size in d.northarrow

Re: [GRASS-dev] [GRASS GIS] #2234: wxGUI d.mon and g.gui monitor rendering is slow

Re: [GRASS-dev] [GRASS GIS] #2234: wxGUI d.mon and g.gui monitor rendering is slow

[GRASS-dev] [GRASS GIS] #3506: 3D view mode not available: Reason: name '__int64' is not defined

Re: [GRASS-dev] [GRASS GIS] #3505: Opening a workspace file

Re: [GRASS-dev] [GRASS GIS] #3505: Opening a workspace file

Re: [GRASS-dev] [GRASS GIS] #3505: Opening a workspace file

Re: [GRASS-dev] [GRASS GIS] #3505: Opening a workspace file

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

Re: [GRASS-dev] [GRASS GIS] #3505: Opening a workspace file

[GRASS-dev] [GRASS GIS] #3505: Opening a workspace file

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

[GRASS-dev] Geomorphometry conference 2018 (Boulder, CO) - deadlines extended

Re: [GRASS-dev] Future of external Processing providers in QGIS

26 matches

Site Navigation

Mail list logo

Footer information