Re: [GRASS-dev] [release planning] 7.6.0

[Vaclav Petras]

On Tue, Jun 26, 2018 at 10:33 PM, Vaclav Petras 
wrote:

>
> On Sun, Jun 17, 2018 at 5:24 PM, Markus Neteler  wrote:
>
>> On Mon, Jun 11, 2018 at 6:07 PM, Markus Neteler 
>> wrote:
>> > Hi devs,
>> >
>> > according to our plans we should start to prepare the initial 7.6.0
>> release:
>> >
>> > https://trac.osgeo.org/grass/milestone/7.6.0
>>
>> What needs to be fixed in _trunk_ first before branching
>> "releasebranch_7_6/" ?
>>
>
>
> The two following enhancement tickets would be really good to resolve
> before 7.6 (branch or at least release) since it requires CLI API to be
> consolidated. #3586 is a blocker because it needs an API change (new API
> which is now in trunk, 7.5) and #3585 would be good to have resolved before
> this new API is publicized (it suggests to simplify it at the cost of
> duplication or potential confusion).
>
> #3585 Don't require -c for --tmp-location
> #3586 Add XY location to grass command interface
>
> https://trac.osgeo.org/grass/ticket/3585
> https://trac.osgeo.org/grass/ticket/3586
>
>
I fixed and closed these two last week.

#3348 or other bugs or annoyances don't prevent us from branching as they
don't involve large code changes which would make subsequent backports
impossible nor they are API changes which could lead to bad legacy APIs or
API breaks.

There are no tickets marked as blocker or critical and there is only 8
defect tickets.

Additionally, the `grass --tmp-location` flag is probably (hopefully)
addition useful enough to make for next minor release. (Forgive me for not
recalling other changes.) [Side note: I'm saying this because I just saw a
note somewhere complaining that now software is released based on different
occasions not when it is ready for the next version. In our case, we missed
the birthday date, but we have features and fixes!]

Best,
Vaclav

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

Re: [GRASS-dev] [GRASS GIS] #3619: G_OPT_DB_WHERE - non-functional 'table' icon in gui

[GRASS GIS]

#3619: G_OPT_DB_WHERE - non-functional 'table' icon in gui
--+---
  Reporter:  pvanbosgeo   |  Owner:  martinl
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.4.2
 Component:  wxGUI|Version:  svn-trunk
Resolution:  fixed|   Keywords:
   CPU:  Unspecified  |   Platform:  Linux
--+---
Changes (by martinl):

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


Comment:

 In [changeset:"73133" 73133]:
 {{{
 #!CommitTicketReference repository="" revision="73133"
 G_OPT_DB_WHERE - non-functional 'table' icon in gui, closes #3619
 (merge r73114, r73118-73119 from trunk)
 }}}

-- 
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 final report week 13 - GRASS GIS module for Sentinel-2 cloud and shadow detection

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

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] i.sentinel.import problems

[Martin Landa]

Hi Luca,

út 21. 8. 2018 v 12:12 odesílatel Luca Delucchi  napsal:
> - a problem with the cloud mask

fixed in r73131. A new info message is printed.

No clouds layer found in
.
Import skipped

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] GSoC 2018 final report week 13 - GRASS GIS module for Sentinel-2 cloud and shadow detection

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

Does your addon also  work with already atmospheric corrected sentinel data
by other software, or is the step with i.sentinel.preproc  needed? 

Is there maybe a workflow with such data documented in the wiki?



-
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] i.sentinel.import problems

[Martin Landa]

Hi Luca,

út 21. 8. 2018 v 12:12 odesílatel Luca Delucchi  napsal:
> i.sentinel.import -cr input=/tmp/ pattern='B[02|03|04|08|8A|11|12]'

please try

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

Fixed in r73130.

[...]

Martin

-- 
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] i.sentinel.import does not list downloaded data

[Martin Landa]

Hi Markus,

út 21. 8. 2018 v 12:29 odesílatel Markus Neteler  napsal:
> sentinelsat.sentinel.SentinelAPIError: HTTP status 500 Internal Server
> Error: InvalidKeyException : Invalid key
> (b8d040e9-9466-453c-8792-5a451f0943a0_1_8A1104_20170314T104411) to
> access Products
>
> Could you please catch this error message?

fixed in r73129. Martin


-- 
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] i.sentinal addons

[Roberta Fagandini]

Hi all,
obviously, it's ok for me but is it possible to wait for the announcement
of GSoc results?
I added the links to the SVN repository to my final report and I'd like
them to work for a few more days.

Thanks!

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

* Moritz Lennert  [2018-08-21 12:57:01 +0200]:


On 21/08/18 12:47, Stefan Blumentrath wrote:

Hi Nikos,

If you are interested in dictionary output you could do:

category_labels = grass.parse_command('r.category', map='youmap', 
delimiter='\t')


Right, nice solution !

For those not very familiar with the scripting library: the 
"delimiter" option here is an option to parse_command, not to 
r.category. It decides which delimiter parse_command should use for 
deciding what is a key and what is a value.


Fantastic.  I read that 'delimiter' somewhere... :-)

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] Parsing output of r.category which includes labels

[Moritz Lennert]

On 21/08/18 12:47, Stefan Blumentrath wrote:

Hi Nikos,

If you are interested in dictionary output you could do:

category_labels = grass.parse_command('r.category', map='youmap', 
delimiter='\t')


Right, nice solution !

For those not very familiar with the scripting library: the "delimiter" 
option here is an option to parse_command, not to r.category. It decides 
which delimiter parse_command should use for deciding what is a key and 
what is a value.


Moritz

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

Re: [GRASS-dev] On post-processing a raster map's mapcalc related history string

[Nikos Alexandris]

* Moritz Lennert  [2018-08-21 09:53:21 +0200]:


On 21/08/18 01:50, Nikos Alexandris wrote:

* Nikos Alexandris  [2018-08-20 20:11:57 +0200]:

2) Look back some time, r.cross has had problems with zeroes and NULLs.


At least this one is True!, see also:

https://trac.osgeo.org/grass/ticket/3080
https://lists.osgeo.org/pipermail/grass-dev/2017-September/086090.html
and this thread, finally:
https://lists.osgeo.org/pipermail/grass-user/2018-February/077931.html



But this seems to have been solved, now, or ?


Right, need to revisit this part of the script.

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] Parsing output of r.category which includes labels

[Stefan Blumentrath]

Hi Nikos,

If you are interested in dictionary output you could do:

category_labels = grass.parse_command('r.category', map='youmap', 
delimiter='\t')

Cheers
Stefan

-Original Message-
From: grass-dev  On Behalf Of Nikos 
Alexandris
Sent: tirsdag 21. august 2018 02:02
To: Moritz Lennert 
Cc: GRASS-GIS development mailing list 
Subject: Re: [GRASS-dev] Parsing output of r.category which includes labels

* Moritz Lennert  [2018-08-20 13:40:36 +0200]:

>On 19/08/18 22:19, Nikos Alexandris wrote:
>>If I am not wrong, all use cases of `read_command()` [0, 1], in (at 
>>least) the grass-addons repository, do not consider an output from 
>>`r.category` which includes labels.
>>
>>[0] 
>>https://grass.osgeo.org/grass74/manuals/libpython/script.html?highligh
>>t=read_command#script.core.read_command
>>[1] 
>>https://grass.osgeo.org/grass75/manuals/libpython/script.html?highligh
>>t=read_command#script.core.read_command
>>
>>
>>I work on such a case where category numbers come along with label strings.
>>To read category numbers, I came up with:
>>
>>```
>>import grass.script as grass
>>grass.read_command('r.category', map=base).split('\n')[:-1]
>>
>>for category in categories:
>> category = category.split('\t')[0] ```
>>
>>Is there any other command that will do this better? Would you 
>>consider adding one?
>
>If all the modules are trying to do is get a list of category values, 
>your approach seems the right one to me, but a simple list 
>comprehension should do the trick in one line:
>
>cats = [int(x[0]) for x in [x.split('\t') for x in 
>g.read_command('r.category', map='RasterMap').splitlines()]]

Great. I love comprehensions (and generators).
It's one of my favourite Python exercises.

>This will work whether there are labels or not. IMHO, there is no need 
>to use anything more sophisticated.
>
>Especially since a
>
>grep -R "r.category" * | grep read_command
>
>only gives 4 hits:
>
>imagery/i.segment.uspo/i.segment.uspo.py:numsegments = 
>len(gscript.read_command('r.category',
>raster/r.geomorphon/testsuite/test_r_geom.py:category = 
>read_command('r.category', map=self.outele)
>raster/r.geomorphon/testsuite/test_r_geom.py:category = 
>read_command('r.category', map=self.outsint)
>raster/r.neighborhoodmatrix/r.neighborhoodmatrix.py:numneighbors = 
>len(gscript.read_command('r.category',
>
>The first and last only read the length (number) of categories, so this 
>isn't an issue.
>
>Have you met other instances ?

No.  Yet, my Skepsis now is the following:

The argument you present, if I understand it right, is "no need to bother", 
since there aren't but a few potential use cases.

What about better integration and more joyful scripting? `r.category` handles 
both values and labels.  And there is currently no `grass.script` helper 
function that considers both labels out of the box.

For example, a parser helper that will return a dictionary.
Is this "too much" here?

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

Re: [GRASS-dev] i.sentinel.import does not list downloaded data

[Markus Neteler]

Hi Martin,

found a small glitch when a user enters a non-sensical UUID (low priority):

GRASS 7.5.svn (utm32N):~ > i.sentinel.download
settings=~/.esa_sentinelhub
uuid=b8d040e9-9466-453c-8792-5a451f0943a0_1_8A1104_20170314T104411 -l
Traceback (most recent call last):
  File "/home/mundialis/.grass7/addons/scripts/i.sentinel.download",
line 386, in 
sys.exit(main())
  File "/home/mundialis/.grass7/addons/scripts/i.sentinel.download",
line 358, in main
downloader.set_uuid(options['uuid'].split(','))
  File "/home/mundialis/.grass7/addons/scripts/i.sentinel.download",
line 303, in set_uuid
for k, v in self._api.get_product_odata(uuid, full=True).items():
  File "/usr/lib/python2.7/site-packages/sentinelsat/sentinel.py",
line 383, in get_product_odata
_check_scihub_response(response)
  File "/usr/lib/python2.7/site-packages/sentinelsat/sentinel.py",
line 892, in _check_scihub_response
raise api_error
sentinelsat.sentinel.SentinelAPIError: HTTP status 500 Internal Server
Error: InvalidKeyException : Invalid key
(b8d040e9-9466-453c-8792-5a451f0943a0_1_8A1104_20170314T104411) to
access Products

Could you please catch this error message?

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

[GRASS-dev] i.sentinal addons

[Luca Delucchi]

Hi all,

could we move the new modules (i.sentinel.preproc and i.sentinel.mask)
into i.sentinel folder, so people installing i.sentinel they install
the 4 modules.

I can take care to fix the Makefiles

-- 
ciao
Luca

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

[GRASS-dev] i.sentinel.import problems

[Luca Delucchi]

Hi Martin,

I'm trying i.sentinel.* module and I got problems with i.sentinel.import
I downloaded 3 scene with i.sentinel.download

i.sentinel.download -l settings=/tmp/settings_sentinel
start=2017-01-10 end=2017-01-13 order=desc clouds=0
3 Sentinel product(s) found
860d118d-c117-4472-8b51-654d6784a40a 2017-01-12T16:16:21Z  0% S2MSI1C
c2eaa8d0-eebe-4b4d-b18b-669a2172b02f 2017-01-12T16:16:21Z  0% S2MSI1C
a3d9b19c-2262-4f88-b107-07ee09e217d3 2017-01-12T16:16:21Z  0% S2MSI1C

and after I run

i.sentinel.import -cr input=/tmp/ pattern='B[02|03|04|08|8A|11|12]'

I got two problems:
- all bands are imported
g.list rast map=. pattern=*_B*
T17SLT_20170112T161621_B01
T17SLT_20170112T161621_B02
T17SLT_20170112T161621_B03
T17SLT_20170112T161621_B04
T17SLT_20170112T161621_B05
T17SLT_20170112T161621_B06
T17SLT_20170112T161621_B07
T17SLT_20170112T161621_B08
T17SLT_20170112T161621_B09
T17SLT_20170112T161621_B10
T17SLT_20170112T161621_B11
T17SLT_20170112T161621_B12
T17SLT_20170112T161621_B8A
T17SNT_20170112T161621_B01
T17SNT_20170112T161621_B02
T17SNT_20170112T161621_B03
T17SNT_20170112T161621_B04
T17SNT_20170112T161621_B05
T17SNT_20170112T161621_B06
T17SNT_20170112T161621_B07
T17SNT_20170112T161621_B08
T17SNT_20170112T161621_B09
T17SNT_20170112T161621_B10
T17SNT_20170112T161621_B11
T17SNT_20170112T161621_B12
T17SNT_20170112T161621_B8A
T17SNU_20170112T161621_B01
T17SNU_20170112T161621_B02
T17SNU_20170112T161621_B03
T17SNU_20170112T161621_B04
T17SNU_20170112T161621_B05
T17SNU_20170112T161621_B06
T17SNU_20170112T161621_B07
T17SNU_20170112T161621_B08
T17SNU_20170112T161621_B09
T17SNU_20170112T161621_B10
T17SNU_20170112T161621_B11
T17SNU_20170112T161621_B12
T17SNU_20170112T161621_B8A

- a problem with the cloud mask

Reprojecting ...
ERROR: No OGR layers available
ERROR: Unable to import
   

ERROR: No OGR layers available
ERROR: Unable to import
   

ERROR: No OGR layers available
ERROR: Unable to import
   

Exception OSError: OSError(2, 'No such file or directory') in > ignored

probably because the clouds are 0%

-- 
ciao
Luca

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

[GRASS-dev] d.vect.colhist

[Paulo van Breugel]

Hi Moritz,

I am trying out your addon d.vect.colhist. One problem I encountered was 
that the 'table' button to define the 'WHERE' condition using the GUI 
was not working (initial reason I filed the bug report 
https://trac.osgeo.org/grass/ticket/3619). In the case of your addon, 
what is missing (to make this work) is the layer selector:


#%option G_OPT_V_FIELD
#%end

Adding that will also make the 'table' button work.

Cheers,

Paulo


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

Re: [GRASS-dev] [GRASS GIS] #3619: G_OPT_DB_WHERE - non-functional 'table' icon in gui

[GRASS GIS]

#3619: G_OPT_DB_WHERE - non-functional 'table' icon in gui
--+---
  Reporter:  pvanbosgeo   |  Owner:  martinl
  Type:  defect   | Status:  assigned
  Priority:  normal   |  Milestone:  7.4.2
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Linux
--+---

Comment (by pvanbosgeo):

 Problem fixed for me, thanks

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] On post-processing a raster map's mapcalc related history string

[Moritz Lennert]

On 21/08/18 01:50, Nikos Alexandris wrote:

* Nikos Alexandris  [2018-08-20 20:11:57 +0200]:

2) Look back some time, r.cross has had problems with zeroes and NULLs.


At least this one is True!, see also:

https://trac.osgeo.org/grass/ticket/3080
https://lists.osgeo.org/pipermail/grass-dev/2017-September/086090.html
and this thread, finally:
https://lists.osgeo.org/pipermail/grass-user/2018-February/077931.html


But this seems to have been solved, now, or ?

Moritz


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