Re: [GRASS-dev] [GRASS GIS] #3564: Inconsistent results from qsort callback in g.mkfontcap

[GRASS GIS]

#3564: Inconsistent results from qsort callback in g.mkfontcap
--+
  Reporter:  yugr |  Owner:  grass-dev@…
  Type:  defect   | Status:  reopened
  Priority:  normal   |  Milestone:  7.6.0
 Component:  Default  |Version:  7.4.0
Resolution:   |   Keywords:  qsort callback
   CPU:  All  |   Platform:  All
--+
Changes (by neteler):

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


Comment:

 Do(n't) we want a bulk backport? If yes, I can do that

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Regarding More Contributions

[Sunveer Singh]

Hi,

How was the GSoC this year? Hope you guys enjoyed mentoring new students!

I would like to contribute more tests, On which modules should I write test?

Thank You
Sunveer
https://sunveersingh.github.io/


On Sat, Aug 18, 2018 at 4:27 AM Luca Delucchi  wrote:

> On Sat, 21 Jul 2018 at 17:52, Sunveer Singh 
> wrote:
> >
> > Hi!
> >
>
> Hi Sunveer,
>
> > Sorry I was not active for a long. But from now I will be giving my
> whole to contribute.
> >
>
> sorry for the delay in the answer, but this summer is really busy
>
> > What can I do? I have already written some tests for modules and I can
> write more.
> >
>
> yes you can write more test or improve translation of your mother
> language [0] or look to some simple issue [1]
>
> > And if there is more stuff I can do please let me know.
> >
> > Thank you
> > Sunveer
>
> [0] https://www.transifex.com/grass-gis/grass7/dashboard/
> [1] https://trac.osgeo.org/grass/report/1
>
> --
> ciao
> Luca
>
> www.lucadelu.org
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3466: v.to.db: check if column exists before running

[GRASS GIS]

#3466: v.to.db: check if column exists before running
--+-
  Reporter:  sbl  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.6.0
 Component:  Vector   |Version:  svn-releasebranch74
Resolution:   |   Keywords:  v.to.db,column
   CPU:  All  |   Platform:  All
--+-
Changes (by mmetz):

 * type:  defect => enhancement


Comment:

 Changing to enhancement because the result is not incorrect if the
 column(s) don't exist. The requested check if the columns to be updated
 exist will not change the result.

-- 
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] #3448: v.buffer native failures

[GRASS GIS]

#3448: v.buffer native failures
--+-
  Reporter:  marisn   |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.6.0
 Component:  Vector   |Version:  unspecified
Resolution:  wontfix  |   Keywords:  v.buffer v.parallel
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by mmetz):

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


Comment:

 This is a long known issue and the reason why v.buffer uses GEOS
 buffering. GRASS native buffering will probably not be fixed because GEOS
 buffering is working, thus closing as won't 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] #3509: g.region grow with negative number limited because of top and bottom

[GRASS GIS]

#3509: g.region grow with negative number limited because of top and bottom
-+-
  Reporter:  wenzeslaus  |  Owner:  grass-dev@…
  Type:  defect  | Status:  closed
  Priority:  minor   |  Milestone:  7.6.0
 Component:  Raster  |Version:  svn-trunk
Resolution:  fixed   |   Keywords:  grow, shrink, g.region, expand
   CPU:  |  computational region, extent, 3D
  Unspecified|   Platform:  Unspecified
-+-
Changes (by mmetz):

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


Comment:

 Fixed by lucadelu with r72397.

-- 
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] #3564: Inconsistent results from qsort callback in g.mkfontcap

[GRASS GIS]

#3564: Inconsistent results from qsort callback in g.mkfontcap
--+
  Reporter:  yugr |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.6.0
 Component:  Default  |Version:  7.4.0
Resolution:  fixed|   Keywords:  qsort callback
   CPU:  All  |   Platform:  All
--+
Changes (by mmetz):

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


Comment:

 All instances of possible inconsistent results or potential buffer
 overflow have been fixed.

-- 
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] #3564: Inconsistent results from qsort callback in g.mkfontcap

[GRASS GIS]

#3564: Inconsistent results from qsort callback in g.mkfontcap
--+
  Reporter:  yugr |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.6.0
 Component:  Default  |Version:  7.4.0
Resolution:   |   Keywords:  qsort callback
   CPU:  All  |   Platform:  All
--+

Comment (by mmetz):

 In [changeset:"73140" 73140]:
 {{{
 #!CommitTicketReference repository="" revision="73140"
 Vlib: add comment to qsort cmp fn (see #3564)
 }}}

-- 
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] #3564: Inconsistent results from qsort callback in g.mkfontcap

[GRASS GIS]

#3564: Inconsistent results from qsort callback in g.mkfontcap
--+
  Reporter:  yugr |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.6.0
 Component:  Default  |Version:  7.4.0
Resolution:   |   Keywords:  qsort callback
   CPU:  All  |   Platform:  All
--+

Comment (by mmetz):

 In [changeset:"73139" 73139]:
 {{{
 #!CommitTicketReference repository="" revision="73139"
 r.distance: fix qsort cmp fn (see #3564)
 }}}

-- 
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] #3564: Inconsistent results from qsort callback in g.mkfontcap

[GRASS GIS]

#3564: Inconsistent results from qsort callback in g.mkfontcap
--+
  Reporter:  yugr |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.6.0
 Component:  Default  |Version:  7.4.0
Resolution:   |   Keywords:  qsort callback
   CPU:  All  |   Platform:  All
--+

Comment (by mmetz):

 In [changeset:"73138" 73138]:
 {{{
 #!CommitTicketReference repository="" revision="73138"
 r.kappa: fix qsort cmp fn (see #3564)
 }}}

-- 
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] #3564: Inconsistent results from qsort callback in g.mkfontcap

[GRASS GIS]

#3564: Inconsistent results from qsort callback in g.mkfontcap
--+
  Reporter:  yugr |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.6.0
 Component:  Default  |Version:  7.4.0
Resolution:   |   Keywords:  qsort callback
   CPU:  All  |   Platform:  All
--+

Comment (by mmetz):

 In [changeset:"73137" 73137]:
 {{{
 #!CommitTicketReference repository="" revision="73137"
 r.stats: fix qsort cmp fn (see #3564)
 }}}

-- 
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] #3564: Inconsistent results from qsort callback in g.mkfontcap

[GRASS GIS]

#3564: Inconsistent results from qsort callback in g.mkfontcap
--+
  Reporter:  yugr |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.6.0
 Component:  Default  |Version:  7.4.0
Resolution:   |   Keywords:  qsort callback
   CPU:  All  |   Platform:  All
--+

Comment (by mmetz):

 In [changeset:"73136" 73136]:
 {{{
 #!CommitTicketReference repository="" revision="73136"
 r.what: fix qsort cmp fn (see #3564)
 }}}

-- 
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] #3564: Inconsistent results from qsort callback in g.mkfontcap

[GRASS GIS]

#3564: Inconsistent results from qsort callback in g.mkfontcap
--+
  Reporter:  yugr |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.6.0
 Component:  Default  |Version:  7.4.0
Resolution:   |   Keywords:  qsort callback
   CPU:  All  |   Platform:  All
--+

Comment (by mmetz):

 In [changeset:"73135" 73135]:
 {{{
 #!CommitTicketReference repository="" revision="73135"
 v.profile: fix qsort cmp fn (see #3564)
 }}}

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Parsing output of r.category which includes labels

[Nikos Alexandris]

Stefan,

a somewhat irrelevant question to the original subject:

do you think the NumPy way is worth to collage a series of `r.stats`
outputs?

Imagine administrative boundaries and one `r.stats` call for each. They
may be tenths, or hundreds, or thousands as the script is meant to cover
European wide extents.

Or should I just work this out using native Python?

Thank you for any thoughts,
Nikos

* Stefan Blumentrath  [2018-08-20 10:48:34 +]:


Hi Nikos,

You could use numpy and genfromtxt() to parse the output string...
genfromtxt() requires an StringIO object (or file) and StringIO (from io) 
requires unicode()...

So you could do:

from io import StringIO
import numpy as np
output = np.genfromtxt(StringIO(unicode(grass.read_command('r.category', 
map=base))) , delimiter='\t', dtype=None, names=['cat', 'label'])

That causes however some overhead [1]. So if it makes sense depends on what you 
want to do with the data in the further processing chain...

Cheers
Stefan

1: https://docs.scipy.org/doc/numpy/user/basics.io.genfromtxt.html


[rest deleted]


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

Re: [GRASS-dev] i.sentinel.import problems

[Luca Delucchi]

On Tue, 21 Aug 2018 at 18:59, Martin Landa  wrote:
>
> Hi Luca,
>

Hi Markus,

>
> fixed in r73131. A new info message is printed.
>
> No clouds layer found in
> .
> Import skipped
>

also this works, thanks

> Ma
>

-- 
ciao
Luca

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

Re: [GRASS-dev] i.sentinel.import problems

[Luca Delucchi]

On Tue, 21 Aug 2018 at 18:34, Martin Landa  wrote:
>
> Hi Luca,
>

Hi Martin,

>
> please try
>
> i.sentinel.import -cr input=/tmp/ pattern='B(02|03|04|08|8A|11|12)'
>
> Fixed in r73130.
>

it works thanks!

> [...]
>
> Martin
>

-- 
ciao
Luca

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

Re: [GRASS-dev] [GRASS GIS] #3537: Add functionalities –tmp-location and –no-clean

[GRASS GIS]

#3537: Add functionalities –tmp-location and –no-clean
-+--
  Reporter:  radeknovotny94  |  Owner:  grass-dev@…
  Type:  enhancement | Status:  closed
  Priority:  normal  |  Milestone:  7.6.0
 Component:  Startup |Version:  svn-trunk
Resolution:  fixed   |   Keywords:  tmp-location, no-clean, exec
   CPU:  All |   Platform:  All
-+--

Comment (by Nikos Alexandris):

 Just some extra thoughts: perhaps the error message should *not* say
 anything but what actually happens: the file is not found.

 What are your thoughts in general? Even this very check, in case the file
 does exist, does not ensure that the file will be available. Right after
 the check anything can happen at the OS level.

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] On d.rast & Co

[Nikos Alexandris]

Dear developers,

are there any plans to improve d.rast.leg?


The d.* tools, I bet, are pretty much part of any prototyping work.
If not of any development phase of real work too.

`d.legend` has some handy flags, i.e.

 -v   Do not show category labels
 -c   Do not show category numbers
 ..
 -b   Show background
 -l   Use logarithmic scale

which are not present in `d.rast.leg`.


As well, with `d.rast.leg` it is not possible to modify the sizing of
the "map" inside the frame, nor font(size)s.  Some times, it's hard to
understand why the size of the legend differs between maps that are
actually of the same type and their values range within the same set of
numbers. And the title is simply too small. Yet, it is useful that the
map is smaller than the frame.

At this point, I am not sure/forgot whether `d.rast.leg` uses multiple
frames to split map and legend.


On the other hand, building a decent output, including text and legend,
takes a bit more than one command. Usually three (`d.rast`, `d.text`,
`d.legend`).

The aim is to have a straightforward and decent output that can be used,
for example, in manuals. With less time spending on re-building what
actually `d.rast.leg` should provide.

Nikos


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

Re: [GRASS-dev] GSoC 2018 final report week 13 - GRASS GIS module for Sentinel-2 cloud and shadow detection

[Roberta Fagandini]

Hi Helmut,

2018-08-21 19:52 GMT+02:00 Roberta Fagandini :

> Hi Helmut,
>
> 2018-08-21 18:46 GMT+02:00 Helmut Kudrnovsky :
>
>> Hi Roberta,
>>
>> >The title of the project is "GRASS GIS module for Sentinel-2 cloud >and
>> shadow detection". It adds new tools for the processing of >Sentinel 2
>> images to GRASS GIS software (Organization: OSGeo).
>>
>> Thanks for the nice addon!
>>
>
> Thank you, I hope it will be useful for the GRASS community!
>
>
>>
>> Does your addon also  work with already atmospheric corrected sentinel
>> data
>> by other software, or is the step with i.sentinel.preproc  needed?
>>
>
> Sure, it works with bands corrected with other software. For instance
> before developing i.sentinel.preproc I used arcsi to correct bands (I also
> tested i.sentinel.mask with bands corrected using Qgis).
> It also works with Sentinel images of the L2A level. If I remember
> correctly Stefan told me to have tested i.sentinel.mask with L2A images
> obtaining good results.
>
>
>>
>> Is there maybe a workflow with such data documented in the wiki?
>>
>
> you can find more information and a general workflow about the module and
> the developed algorithm in the manual page [0]. Hope this helps!!
>
> [https://grass.osgeo.org/grass74/manuals/addons/i.sentinel.mask.html]
>

sorry, I thought you were referring to my GSoC wiki page but maybe I
understood what you meant for 'wiki' [0]. I will add the documentation
about i.sentinel.mask and i.sentinel.preproc in the next days.

Kind regards,

Roberta

[0] https://grasswiki.osgeo.org/wiki/SENTINEL


>
> kind regards
>
> Roberta
>
>
>>
>>
>>
>> -
>> 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 mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3626: auto-compiled Windows version

[GRASS GIS]

#3626: auto-compiled Windows version
--+-
  Reporter:  pkameswari   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  7.4.2
 Component:  Compiling|Version:  unspecified
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by hellik):

 Replying to [comment:1 pkameswari]:
 > It is highly required by many users that windows offline system users
 not able to compile GRASS GIS because of the libraries required by grass
 gis will have to be downloaded manually through OSGEO4W.If the system
 which is online used to download libraries, can have different OS and
 accordingly libraries can be downloaded.which are not able to used for
 offline compilation.So i request grass developers to post auto-compiled
 version for windows version.

 have a look here:

 https://grass.osgeo.org/download/software/ms-windows/

 there are already pre-compiled winGRASS binaries available:

 -current stable
 -development daily builds

 the same is available via OSGeo4W. anything missing here?

 regarding libaries for compiling, the only decision to be made is between
 32bit and 64bit versions. these libraries should work then from Win7 and
 higher.

-- 
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] #3626: auto-compiled Windows version

[GRASS GIS]

#3626: auto-compiled Windows version
--+-
  Reporter:  pkameswari   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  major|  Milestone:  7.4.2
 Component:  Compiling|Version:  unspecified
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by pkameswari):

 It is highly required by many users that windows offline system users not
 able to compile GRASS GIS because of the libraries required by grass gis
 will have to be downloaded manually through OSGEO4W.If the system which is
 online used to download libraries, can have different OS and accordingly
 libraries can be downloaded.which are not able to used for offline
 compilation.So i request grass developers to post auto-compiled version
 for windows version.

-- 
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] #3626: auto-compiled Windows version

[GRASS GIS]

#3626: auto-compiled Windows version
-+-
 Reporter:  pkameswari   |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  major|  Milestone:  7.4.2
Component:  Compiling|Version:  unspecified
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 It is highly required by many users that windows offline system users not
 able to compile GRASS GIS because of the libraries required by grass gis
 will have to be downloaded manually through OSGEO4W.If the system which is
 online used to download libraries, can have different OS and accordingly
 libraries can be downloaded.which are not able used by offline
 compilation.So i request grass developers to post auto-compiled version
 for windows version.

-- 
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] #3625: patch for i.atcorr for hyperspectral data

[GRASS GIS]

#3625: patch for i.atcorr for hyperspectral data
-+-
 Reporter:  pkameswari   |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  normal   |  Milestone:
Component:  Default  |Version:  unspecified
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 It is obeserved that i.atcorr is not supporting for hyperspectral data.if
 more number of bands iwave throws exception.Grass Gis 7.4.X can be ported
 for hyperion sensor.also observed if more number of bands, i.group fails
 to create output stack file because of string constraints. that also can
 be changed.

-- 
Ticket URL: 
GRASS GIS 

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