Re: [GRASS-dev] [GRASS GIS] #3713: add powershell shell support to grass74.py

[GRASS GIS]

#3713: add powershell shell support to grass74.py
--+-
  Reporter:  pmolzer  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:
 Component:  Startup  |Version:  7.4.2
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  MSWindows
--+-

Comment (by pmolzer):

 I've attached a diff.  I could not find grass74.py in the source but there
 is grass.py, so I've modified 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] [GRASS GIS] #3713: add powershell shell support to grass74.py

[GRASS GIS]

#3713: add powershell shell support to grass74.py
--+-
  Reporter:  pmolzer  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:
 Component:  Startup  |Version:  7.4.2
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  MSWindows
--+-
Changes (by pmolzer):

 * Attachment "grass.py.diff" added.


-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] i.sentinel improvements

[Veronica Andreo]

Hi Lu,

El lun., 17 dic. 2018 a las 10:39, Luca Delucchi ()
escribió:

> Hi all,
>
> I would like to do some improvements in i.sentinel
> Since I'm not the main author I would like to get approval before to
> start to work on it.
> - i.sentinel.download add capability to filter out scenes with small
> percent (user could decide the percentage to keep) of area matching
> the area of interest
> - i.sentinel.import add capability to cut the scene on the footprint
> to simplify scenes patch
> - i.sentinel.preproc add capability to compute topographic correction
>

+1! (no idea about differences among topographic correction algorithms,
though... is c-factor the best one?)

What will the module do with L2A data? Only topographic correction?

unrelated, probably this module could be renamed to
> i.sentinel.import.preproc or similar since it's importing data. Any
> idea/opinion?
>

Yeah, that would be an option... What about keeping i.sentinel.import for
the import part and make i.sentinel.preproc only about pre-processing,
i.e., atcorr and topcorr?

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

Re: [GRASS-dev] i.sentinel improvements

[Martin Landa]

Hi,

po 17. 12. 2018 v 10:39 odesílatel Luca Delucchi  napsal:
> - i.sentinel.download add capability to filter out scenes with small
> percent (user could decide the percentage to keep) of area matching
> the area of interest

sounds great :-)

> - i.sentinel.import add capability to cut the scene on the footprint
> to simplify scenes patch

great again :-)

> - i.sentinel.preproc add capability to compute topographic correction
> using the following prcedure

unrelated, probably this module could be renamed to
i.sentinel.import.preproc or similar since it's importing data. Any
idea/opinion?

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

[GRASS-dev] i.sentinel improvements

[Luca Delucchi]

Hi all,

I would like to do some improvements in i.sentinel
Since I'm not the main author I would like to get approval before to
start to work on it.
- i.sentinel.download add capability to filter out scenes with small
percent (user could decide the percentage to keep) of area matching
the area of interest
- i.sentinel.import add capability to cut the scene on the footprint
to simplify scenes patch
- i.sentinel.preproc add capability to compute topographic correction
using the following prcedure

###
eval `r.sunmask -sg ele=DTM year=${dat:0:4} month=$(echo $dat:4:2 |
sed 's/^0*//') day=${dat:6:2} hour=${dat:9:2} minute=${dat:11:2}
second=${dat:13:2} timezone=0`
z=`echo "90 - $sunangleabovehorizon" | bc -l`
echo "${inpmap} $z $sunazimuth"
i.topo.corr -i basemap=DTM zenit=$z azimuth=$sunazimuth output=dtm_illu

for m in `g.list type=raster pattern=${inpmap}*_cor`; do g.region
raster=$m; r.mapcalc expr="${m}_d=double(${m})"; done

i.topo.corr basemap=dtm_illu input=`g.list type=raster sep=comma
pattern=${inpmap}*_cor_d` output=tcor zenith=$z method=c-factor

g.remove -f type=raster pattern=${inpmap}*_cor_d
###

let me know.

-- 
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] #3712: v.colors2 range check bug

[GRASS GIS]

#3712: v.colors2 range check bug
--+-
  Reporter:  pmolzer  |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:
 Component:  Addons   |Version:  7.4.2
Resolution:  fixed|   Keywords:
   CPU:  Unspecified  |   Platform:  All
--+-
Changes (by lucadelu):

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


Comment:

 In [changeset:"73813" 73813]:
 {{{
 #!CommitTicketReference repository="" revision="73813"
 v.colors2: fixed #3712
 }}}

-- 
Ticket URL: 
GRASS GIS 

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