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:  new
  Priority:  normal   |  Milestone:  7.2.4
 Component:  Temporal |Version:  svn-trunk
Resolution:   |   Keywords:  t.register encoding
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by 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.

-- 
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] #3075: profile surface analysis tool transect segment markers issue

[GRASS GIS]

#3075: profile surface analysis tool transect segment markers issue
--+--
  Reporter:  pvanbosgeo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.2.4
 Component:  Default  |Version:  unspecified
Resolution:  fixed|   Keywords:  profile, gui
   CPU:  Unspecified  |   Platform:  Linux
--+--
Changes (by veroandreo):

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


Comment:

 neither in current 76 relbranch; all looks good. Closing.

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

El lun., 6 may. 2019 17:49, Markus Neteler  escribió:

> Hi Martin,
>
> On Mon, May 6, 2019 at 11:41 AM Martin Landa 
> wrote:
> >
> > Dear all,
> >
> > based on decision made by PSC [1], the GRASS GIS source code will be
> > moved from SVN hosted by OSGeo to Git hosted by GitHub.com. More
> > details at [2].
>
> [...migration of tickets ...]
>
> > When this part will be done the migration can start, see draft [5].
>
> Why wait for that with the source code migration?
> Please let's start with it. The tickets can follow in a second step.
>

+1!

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 :)

My 0.01 pesos cents :D
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

[Markus Neteler]

Hi Martin,

On Mon, May 6, 2019 at 11:41 AM Martin Landa  wrote:
>
> Dear all,
>
> based on decision made by PSC [1], the GRASS GIS source code will be
> moved from SVN hosted by OSGeo to Git hosted by GitHub.com. More
> details at [2].

[...migration of tickets ...]

> When this part will be done the migration can start, see draft [5].

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 0.02 cents,
Markus

> [1] https://lists.osgeo.org/pipermail/grass-psc/2019-April/002034.html
> [2] 
> https://trac.osgeo.org/grass/wiki/GitMigration#ImplementationofmigrationfromOSGeoSVNandtractoGitHub
> [3] 
> https://trac.osgeo.org/grass/query?status=assigned=new=reopened=status=7.0.7
> [4] 
> https://trac.osgeo.org/grass/query?status=assigned=new=reopened=status=7.2.4
> [5] https://trac.osgeo.org/grass/wiki/GitMigration#Migrationplandraft
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3064: r.external gui does not display layer in list of layers when selected via browse button

[GRASS GIS]

#3064: r.external gui does not display layer in list of layers when selected via
browse button
--+--
  Reporter:  dnewcomb |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.2.4
 Component:  Default  |Version:  svn-releasebranch72
Resolution:   |   Keywords:  Windows 7 r.external
   CPU:  Unspecified  |   Platform:  MSWindows 7
--+--

Comment (by hellik):

 tested here with

 {{{
 GRASS version: 7.6.1
 GRASS SVN revision: r74292
 Build date: 2019-03-19
 Build platform: x86_64-w64-mingw32
 GDAL: 2.4.0
 PROJ.4: 5.2.0
 GEOS: 3.7.0
 SQLite: 3.26.0
 Python: 2.7.14
 wxPython: 2.8.12.1
 Platform: Windows-10-10.0.17763 (OSGeo4W)
 }}}

 worksforme.

 closing ticket; 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] #3064: r.external gui does not display layer in list of layers when selected via browse button

[GRASS GIS]

#3064: r.external gui does not display layer in list of layers when selected via
browse button
--+--
  Reporter:  dnewcomb |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.2.4
 Component:  Default  |Version:  svn-releasebranch72
Resolution:  worksforme   |   Keywords:  Windows 7 r.external
   CPU:  Unspecified  |   Platform:  MSWindows 7
--+--
Changes (by hellik):

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


-- 
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] #3065: v.external gui does not display layer in list of layers when selected via browse button

[GRASS GIS]

#3065: v.external gui does not display layer in list of layers when selected via
browse button
---+---
  Reporter:  dnewcomb  |  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  normal|  Milestone:  7.2.4
 Component:  wxGUI |Version:  svn-releasebranch72
Resolution:|   Keywords:  windows 7, v.external
   CPU:  x86-64|   Platform:  MSWindows 7
---+---

Comment (by hellik):

 testef with

 {{{
 GRASS version: 7.6.1
 GRASS SVN revision: r74292
 Build date: 2019-03-19
 Build platform: x86_64-w64-mingw32
 GDAL: 2.4.0
 PROJ.4: 5.2.0
 GEOS: 3.7.0
 SQLite: 3.26.0
 Python: 2.7.14
 wxPython: 2.8.12.1
 Platform: Windows-10-10.0.17763 (OSGeo4W)
 }}}

 worksforme

 closing ticket, 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] #3075: profile surface analysis tool transect segment markers issue

[GRASS GIS]

#3075: profile surface analysis tool transect segment markers issue
--+--
  Reporter:  pvanbosgeo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.2.4
 Component:  Default  |Version:  unspecified
Resolution:   |   Keywords:  profile, gui
   CPU:  Unspecified  |   Platform:  Linux
--+--

Comment (by hellik):

 tested with

 {{{
 GRASS version: 7.6.1
 GRASS SVN revision: r74292
 Build date: 2019-03-19
 Build platform: x86_64-w64-mingw32
 GDAL: 2.4.0
 PROJ.4: 5.2.0
 GEOS: 3.7.0
 SQLite: 3.26.0
 Python: 2.7.14
 wxPython: 2.8.12.1
 Platform: Windows-10-10.0.17763 (OSGeo4W)
 }}}

 can't be reproduced here.

-- 
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] #3155: inconsistent newlines handling on Windows

[GRASS GIS]

#3155: inconsistent newlines handling on Windows
--+-
  Reporter:  annakrat |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.6.2
 Component:  LibVector|Version:  svn-trunk
Resolution:   |   Keywords:  newline
   CPU:  Unspecified  |   Platform:  MSWindows 8
--+-
Changes (by hellik):

 * milestone:  7.2.4 => 7.6.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] [GRASS GIS] #2702: G7: vector vrt not recognized by "v.in.ogr - import common formats" by mode directory

[GRASS GIS]

#2702: G7: vector vrt not recognized by "v.in.ogr - import common formats" by 
mode
directory
--+-
  Reporter:  hellik   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.6.2
 Component:  Default  |Version:  svn-releasebranch76
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by hellik):

 * version:  svn-releasebranch70 => svn-releasebranch76
 * milestone:  7.0.7 => 7.6.2


Comment:

 still relevant for:
 {{{
 in mode "source type: directory; format: vrt": if I enter the path to
 directory, only the shapefile in this folder is recognized, although vrt
 is defined as format.
 }}}

 upgrading milestone

-- 
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] #3156: Cannot export GRASS raster map using r.out.png (crashes on windows)

[GRASS GIS]

#3156: Cannot export GRASS raster map using r.out.png (crashes on windows)
--+-
  Reporter:  spawley  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.6.2
 Component:  Raster   |Version:  svn-releasebranch76
Resolution:   |   Keywords:  r.out.png, wingrass, g.ppmtopng
   CPU:  x86-64   |   Platform:  MSWindows 7
--+-
Changes (by hellik):

 * version:  7.0.4 => svn-releasebranch76
 * milestone:  7.0.7 => 7.6.2


Comment:

 Replying to [comment:21 martinl]:
 > Still relevant?

 no crash, but empty png files (header unkown).

 upgrade milestone

-- 
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] #2700: scatterplots in g.gui.iclass don't work on Windows

[GRASS GIS]

#2700: scatterplots in g.gui.iclass don't work on Windows
---+---
  Reporter:  annakrat  |  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  normal|  Milestone:  7.6.2
 Component:  wxGUI |Version:  svn-releasebranch76
Resolution:|   Keywords:  g.gui.iclass, scatterplot
   CPU:  All   |   Platform:  MSWindows 8
---+---
Changes (by hellik):

 * version:  svn-releasebranch70 => svn-releasebranch76
 * milestone:  7.0.7 => 7.6.2


Comment:

 g.gui.iclass doesn't work at all in winGRASS 7.6.1.

 milestone updated

-- 
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] #3114: v.kriging: images in manual do not show (and when shown should be bigger)

[Eva Stopková]

Thank you for the reminder; I prepared the pdf file with some case studies
in 2016 [1] and I edited the manual, so no images are needed anymore. I've
checked the link from the manual to the pdf recently, it does not work at
the moment. In the next weeks, I am moving to another place, but after that
I am ready to fix it. There are still several updates from 2018 [2] that
I've done in v.kriging that should be tracked as well.
Best regards,

Eva

[1]
https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.kriging/v.kriging.pdf
[2] https://ojs.cvut.cz/ojs/index.php/gi/article/view/gi.17.2.4

ne 28. 4. 2019 o 16:23 GRASS GIS  napísal(a):

> #3114: v.kriging: images in manual do not show (and when shown should be
> bigger)
> --+--
>   Reporter:  mlennert |  Owner:  grass-dev@…
>   Type:  defect   | Status:  new
>   Priority:  normal   |  Milestone:
>  Component:  Addons   |Version:  unspecified
> Resolution:   |   Keywords:  v.kriging manual
>CPU:  Unspecified  |   Platform:  Unspecified
> --+--
> Changes (by martinl):
>
>  * milestone:  7.0.7 =>
>
>
> --
> Ticket URL: 
> GRASS GIS 
>
>
___
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?

[Markus Metz]

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.
>
> Some functions copy DEFAULT_WIND from PERMANENT. E.g.:
>
> lib/gis/make_mapset.c
> pygrass.gis.make_mapset()
> the grass executable
>
> While others copy WIND from PERMANENT. E.g.
>
> the tests
> gui.wxpython.startup.create_mapset()
>
> Is there an established convention?

IMHO, new mapsets should use DEFAULT_WIND from PERMANENT. But the current
region of a new mapset is often adjusted, therefore it does not really
matter if DEFAULT_WIND or WIND is used.

my2c

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

Re: [GRASS-dev] [GRASS GIS] #2555: v.colors: silently ignores rules given at stdin

[GRASS GIS]

#2555: v.colors: silently ignores rules given at stdin
--+-
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Vector   |Version:  svn-releasebranch70
Resolution:   |   Keywords:  v.colors stdin
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by martinl):

 * milestone:  7.2.4 => 7.8.0


Comment:

 Let's hope.

-- 
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] #2935: r.watershed returns bogus flow direction without warning when using large "virtual" terrain

[GRASS GIS]

#2935: r.watershed returns bogus flow direction without warning when using large
"virtual" terrain
--+-
  Reporter:  mankoff  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Raster   |Version:  7.2.0
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  MacOSX
--+-
Changes (by mankoff):

 * milestone:  7.2.4 => 7.8.0


Comment:

 Updating milestone so that this is included in !GitHub migration.

-- 
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] #3461: STVDS and libgis error on OS X

[GRASS GIS]

#3461: STVDS and libgis error on OS X
+-
  Reporter:  mankoff|  Owner:  grass-dev@…
  Type:  defect | Status:  closed
  Priority:  normal |  Milestone:  7.2.4
 Component:  LibGIS |Version:  7.2.2
Resolution:  wontfix|   Keywords:  temporal, stvds
   CPU:  OSX/Intel  |   Platform:  MacOSX
+-
Changes (by mankoff):

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


Comment:

 Opting to close because I'm the only person who seemed affected by this
 issue and I'm not using OS X any longer.

-- 
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] #3695: r.terraflow should support large file dimensions by default

[GRASS GIS]

#3695: r.terraflow should support large file dimensions by default
--+-
  Reporter:  mankoff  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Raster   |Version:  svn-trunk
Resolution:   |   Keywords:  r.terraflow
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by mankoff):

 * milestone:   => 7.8.0


Comment:

 Upgrading milestone so that this ticket is migrated to GitHub

-- 
Ticket URL: 
GRASS GIS 

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

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

[Panagiotis Mavrogiorgos]

Hello all,

I am a bit confused WRT what the expected WIND should be when you create a
new mapset.

Some functions copy DEFAULT_WIND from PERMANENT. E.g.:

   - lib/gis/make_mapset.c
   


   - pygrass.gis.make_mapset()
   

   - the grass executable
   


While others copy WIND from PERMANENT. E.g.

   - the tests
   

   - gui.wxpython.startup.create_mapset()
   


Is there an established convention?

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

Re: [GRASS-dev] [GRASS GIS] #2670: v.voronoi skeleton: nonsense result with many adjacent polygons

[GRASS GIS]

#2670: v.voronoi skeleton: nonsense result with many adjacent polygons
--+-
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Default  |Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by mmetz):

 Replying to [comment:9 martinl]:
 > With GRASS 7.6.0 I am getting
 >
 > {{{
 > v.voronoi -s census_wake2000 out=census_skel
 > Reading features...
 > ERROR: Found 0 vertices in , but at least 2
 are
 >needed
 > }}}
 >
 > ?

 From the manual: "The bounds of the output map are limited by the current
 region (see g.region)."

 Then you get no error but nonsense results.

 Replying to [comment:10 mlennert]:
 > Moving this on to milestone 7.8, but not sure if this is really fixable.
 >
 > MarkusM, should this be a no fix ?

 Not sure, v.voronoi generally suffers from numerical instability.
 Previously, I could improve it a bit, but it's not perfect, but I have one
 more idea (maybe in the next few weeks I find time to try this idea: scale
 coordinates to region center).

 Furtheron, something seems to be conceptually wrong with the skeletons for
 adjacent areas, that should be fixable.

-- 
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] #3392: t.register: encoding error

[GRASS GIS]

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

Comment (by mlennert):

 Has the work on Python 3 changed anything for this discussion, here ?

-- 
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] #3300: v.rast.stats: wrong results for non-first category values in the case of multiple category values per feature

[GRASS GIS]

#3300: v.rast.stats: wrong results for non-first category values in the case of
multiple category values per feature
--+--
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Vector   |Version:  unspecified
Resolution:   |   Keywords:  v.rast.stats overlap
   CPU:  Unspecified  |   Platform:  Unspecified
--+--
Changes (by mlennert):

 * milestone:  7.2.4 => 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] #2555: v.colors: silently ignores rules given at stdin

[GRASS GIS]

#2555: v.colors: silently ignores rules given at stdin
--+-
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.2.4
 Component:  Vector   |Version:  svn-releasebranch70
Resolution:   |   Keywords:  v.colors stdin
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by mlennert):

 Martin, do you think this is something which will ever be fixed, or should
 we consider v.colors as an experience with limits that we will not work on
 anymore ?

-- 
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] #2483: adding output to groups

[GRASS GIS]

#2483: adding output to groups
--+---
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.2.4
 Component:  Imagery  |Version:  svn-trunk
Resolution:  wontfix  |   Keywords:  i.maxlik, group, subgroup
   CPU:  Unspecified  |   Platform:  Unspecified
--+---
Changes (by mlennert):

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


Comment:

 I think this is rather a no fix. Maybe one day we will rework the whole
 logic, but until then, i.maxlik and i.segment users just have to watch
 out...

-- 
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] #3186: [PATCH] i.in.spotvgt: allow import of any band, not only NDVI

[GRASS GIS]

#3186: [PATCH] i.in.spotvgt: allow import of any band, not only NDVI
--+
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Imagery  |Version:  svn-trunk
Resolution:   |   Keywords:  i.in.spotvgt bands
   CPU:  Unspecified  |   Platform:  Unspecified
--+
Changes (by mlennert):

 * milestone:  7.0.7 => 7.8.0


Comment:

 I think this is still relevant, but am not a regular SPOT imagery user, so
 am not 100% sure the patch is acceptable to all. Best bet is probably to
 just apply it and see ;-)

-- 
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] #2670: v.voronoi skeleton: nonsense result with many adjacent polygons

[GRASS GIS]

#2670: v.voronoi skeleton: nonsense result with many adjacent polygons
--+-
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  Default  |Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by mlennert):

 * milestone:  7.0.7 => 7.8.0


Comment:

 Moving this on to milestone 7.8, but not sure if this is really fixable.

 MarkusM, should this be a no fix ?

-- 
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] #3326: using g.mapset to create new mapset in another location fails

[GRASS GIS]

#3326: using g.mapset to create new mapset in another location fails
--+-
  Reporter:  pvanbosgeo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.6.2
 Component:  Default  |Version:  svn-releasebranch76
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by mmetz):

 Replying to [comment:5 veroandreo]:
 > Still valid in 76 relbranch. However, it works fine in current trunk,
 i.e. WIND file is created properly.

 This has been fixed in relbr76 r74430 on Apr 27, 2019. Is your local copy
 up to date?

-- 
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] #3326: using g.mapset to create new mapset in another location fails

[GRASS GIS]

#3326: using g.mapset to create new mapset in another location fails
--+-
  Reporter:  pvanbosgeo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.6.2
 Component:  Default  |Version:  svn-releasebranch76
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by veroandreo):

 * version:  unspecified => svn-releasebranch76
 * milestone:  7.2.4 => 7.6.2


Comment:

 Still valid in 76 relbranch. However, it works fine in current trunk, i.e.
 WIND file is created properly.

-- 
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] #3294: g.gui.tplot: error when trying to plot a STVDS

[GRASS GIS]

#3294: g.gui.tplot: error when trying to plot a STVDS
-+-
  Reporter:  lrntct  |  Owner:  grass-dev@…
  Type:  defect  | Status:  reopened
  Priority:  normal  |  Milestone:  7.8.0
 Component:  wxGUI   |Version:  svn-trunk
Resolution:  |   Keywords:
   CPU:  x86-64  |   Platform:  Linux
-+-
Changes (by veroandreo):

 * version:  7.2.0 => svn-trunk
 * milestone:  7.2.4 => 7.8.0


Comment:

 Changing milestone. I get the last error reported:

 {{{
 Traceback (most recent call last):
   File "/home/veroandreo/software/grass7_trunk/dist.x86_64
 -pc-linux-gnu/gui/wxpython/tplot/frame.py", line 882, in
 OnRedraw

 self._redraw()
   File "/home/veroandreo/software/grass7_trunk/dist.x86_64
 -pc-linux-gnu/gui/wxpython/tplot/frame.py", line 893, in
 _redraw

 self._getSTVDData(self.datasetsV)
   File "/home/veroandreo/software/grass7_trunk/dist.x86_64
 -pc-linux-gnu/gui/wxpython/tplot/frame.py", line 566, in
 _getSTVDData

 lay = int(row['layer'])
 TypeError
 :
 int() argument must be a string or a number, not 'NoneType'
 Traceback (most recent call last):
   File "/home/veroandreo/software/grass7_trunk/dist.x86_64
 -pc-linux-gnu/gui/wxpython/tplot/frame.py", line 882, in
 OnRedraw

 self._redraw()
   File "/home/veroandreo/software/grass7_trunk/dist.x86_64
 -pc-linux-gnu/gui/wxpython/tplot/frame.py", line 893, in
 _redraw

 self._getSTVDData(self.datasetsV)
   File "/home/veroandreo/software/grass7_trunk/dist.x86_64
 -pc-linux-gnu/gui/wxpython/tplot/frame.py", line 566, in
 _getSTVDData

 lay = int(row['layer'])
 TypeError
 :
 int() argument must be a string or a number, not 'NoneType'
 }}}

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

[Martin Landa]

Hi,

po 6. 5. 2019 v 12:10 odesílatel Helmut Kudrnovsky  napsal:
> > In this regard I would like to ask you for ASSISTANCE. All
> >tickets with milestone 7.0 [3], 7.2 [4] should be reviewed and either
> >to be closed or milestone changed to 7.4 (or 7.6/7.8/8.0).
>
> do we have some date until when tickets should be reviewed?

ASAP, we would like to finish migration in reasonable 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] svn/trac -> git/github migration plan

[Helmut Kudrnovsky]

hi Martin,

> In this regard I would like to ask you for ASSISTANCE. All
>tickets with milestone 7.0 [3], 7.2 [4] should be reviewed and either
>to be closed or milestone changed to 7.4 (or 7.6/7.8/8.0).

do we have some date until when tickets should be reviewed?



-
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

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

[Martin Landa]

Dear all,

based on decision made by PSC [1], the GRASS GIS source code will be
moved from SVN hosted by OSGeo to Git hosted by GitHub.com. More
details at [2].

It's also planned to move open issues from trac to GitHub issue
system. In this regard I would like to ask you for ASSISTANCE. All
tickets with milestone 7.0 [3], 7.2 [4] should be reviewed and either
to be closed or milestone changed to 7.4 (or 7.6/7.8/8.0). Only
tickets with milestone 7.4+ will be migrated. We are assuming that 7.0
and 7.2 reached EOL. Our goal: to have open tickets only with
milestone 7.4.5+.

When this part will be done the migration can start, see draft [5].

Thanks for you help, feedback in advance! Ma

[1] https://lists.osgeo.org/pipermail/grass-psc/2019-April/002034.html
[2] 
https://trac.osgeo.org/grass/wiki/GitMigration#ImplementationofmigrationfromOSGeoSVNandtractoGitHub
[3] 
https://trac.osgeo.org/grass/query?status=assigned=new=reopened=status=7.0.7
[4] 
https://trac.osgeo.org/grass/query?status=assigned=new=reopened=status=7.2.4
[5] https://trac.osgeo.org/grass/wiki/GitMigration#Migrationplandraft

-- 
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] [PROJ] PROJ 6.1.0RC1

[Helmut Kudrnovsky]

fyi https://lists.osgeo.org/pipermail/proj/2019-May/008515.html

###


I have prepared candidates for the upcoming releases of PROJ 6.1.0 and
proj-datumgrid-europe-1.3.

Download the archives here:

https://download.osgeo.org/proj/proj-6.1.0RC1.tar.gz
(https://download.osgeo.org/proj/proj-6.1.0RC1.tar.gz.md5)
https://download.osgeo.org/proj/proj-6.1.0RC1.zip
(https://download.osgeo.org/proj/proj-6.1.0RC1.zip.md5)

https://download.osgeo.org/proj/proj-datumgrid-europe-1.3RC1.tar.gz
https://download.osgeo.org/proj/proj-datumgrid-europe-1.3RC1.zip


Please test the release candidates and report back any problems you may
find. If no issues
are discovered I plan to call the vote for promotion to final release on
Monday May 13th with
a targeted release date at May 15th.

/Kristian
###

from the included NEWS file:

###
 Updates
 ---

 o Include custom ellipsoid definitions from QGIS (#1337)

 o Add "-k ellipsoid" option to projinfo (#1338)

 o Make cs2cs support 4D coordinates (#1355)

 o WKT2 parser: update to OGC 18-010r6 (#1360 #1366)

 o Update internal version of googletest to v1.8.1 (#1361)

 o Database update: EPSG v9.6.1, IGNF v3.0.3, ESRI 10.7.0
   and add operation_version column (#1368)

 o Add proj_normalize_for_visualization() that attempts to apply axis
   ordering as used by most GIS applications and PROJ <6 (#1387)

 o Added noop operation (#1391)

 o Paths set by user take priority over PROJ_LIB for search paths (#1398)

 o Reduced database size (#1438)

 o add support for compoundCRS and concatenatedOperation named from
   their components (#1441)

 Bug fixes
 -

 o Have gie return non-zero code when file can't be opened (#1312)

 o CMake cross-compilation fix (#1316)

 o Use 1st eccentricity instead of 2nd eccentricity in Molodensky (#1324)

 o Make sure to include grids when doing Geocentric to CompoundCRS with
   nadgrids+geoidgrids transformations (#1326)

 o Handle coordinates outside of bbox better (#1333)

 o Enable system error messages in command line automatically in builds
(#1336)

 o Make sure to install projinfo man page with CMake (#1347)

 o Add data dir to pkg-config file proj.pc (#1348)

 o Fix GCC 9 warning about useless std::move() (#1352)

 o Grid related fixes (#1369)

 o Make sure that ISO19111 C++ code sets pj_errno on errors (#1405)

 o vgridshift: handle longitude wrap-around for grids with 360deg
   longitude extent (#1429)

 o proj/cs2cs: validate value of -f parameter to avoid potential crashes
(#1434)

 o Many division by zero and similar bug fixes found by OSS Fuzz.
###




-
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