Re: [GRASS-dev] [GRASS GIS] #3199: r.in.srtm.region requires change for new USGS user authentication

[GRASS GIS]

#3199: r.in.srtm.region requires change for new USGS user authentication
--+-
  Reporter:  stjo |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.0.6
 Component:  Addons   |Version:  svn-releasebranch70
Resolution:  fixed|   Keywords:  r.in.srtm.region
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by neteler):

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


Comment:

 I have now also added add single tile support and explain the new USGS
 user authentication in the manual page (r69925).

 Closing.

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3199: r.in.srtm.region requires change for new USGS user authentication

[GRASS GIS]

#3199: r.in.srtm.region requires change for new USGS user authentication
--+-
  Reporter:  stjo |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.0.6
 Component:  Addons   |Version:  svn-releasebranch70
Resolution:   |   Keywords:  r.in.srtm.region
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by neteler):

 Thanks a lot, submitted with minor modifications in r69924

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] r.colors.out_sld

[Blumentrath, Stefan]

Dear all,

Yesterday I pushed a GRASS GIS 7 / Python version of r.colors.out_sld to AddOns.

Further improvements to the GRASS 6 version are category label support, UTF-8 
encoding and a preliminary manual 
(https://grass.osgeo.org/grass70/manuals/addons/r.colors.out_sld.html).

It is still limited to SLD v1.0.0.

The produced SLDs validate without issues in GeoServer, but further testing is 
very welcome...

Mvh
Stefan

From: grass-dev [mailto:grass-dev-boun...@lists.osgeo.org] On Behalf Of 
Blumentrath, Stefan
Sent: 21. november 2016 14:07
To: GRASS developers list (grass-dev@lists.osgeo.org) 

Subject: [GRASS-dev] r.colors.out_sld

Hi,

In order to get some of my data properly from GRASS into GeoNode (which is 
based on GeoServer) I would like to also export the GRASS color tables into 
SLD, so I can import them to GeoServer too.

I found the r.colors.out_sld AddOn 
(https://svn.osgeo.org/grass/grass-addons/grass6/raster/r.colors.out_sld/) for 
that purpose, but it is GRASS 6 Shell script. Even though I think it would work 
with GRSS 7 too, my questions are:

1)  Are there other solutions in GRASS 7 to produce SLD I might have 
overlooked?

2)  If not, do you think it there is a point porting r.colors.out_sld to 
GRASS7 / Python (which I would volunteer for)? or

3)  Would it be better to add SLD export as a flag to r.colors.out?

Kind regards,
Stefan


Stefan Blumentrath
Researcher II

Norwegian Institute for Nature Research - NINA
Postal address: Gaustadalléen 21, NO-0349 Oslo, NORWAY
Delivery/Visiting address: Gaustadalléen 21, NO-0349 Oslo, NORWAY
Phone: +47 46 34 11 58 * Cell: +47 46 34 11 58 * Fax: +47 73 80 14 01 * 
www.nina.no


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

Re: [GRASS-dev] winGRASS7.2/trunk (standalone and OSGeo4W) wxGUI startup very slow/freezes

[Markus Neteler]

On Fri, Nov 25, 2016 at 8:45 PM, Martin Landa  wrote:
> Hi,
>
> 2016-11-25 20:34 GMT+01:00 Helmut Kudrnovsky :
>> sorry for the noise:  it's my restrictive firewall/antivirus which slowed
>> down the startup. I had to adapt the rules for winGRASS.
>>
>> all starts normally now, OSGeo4W-winGRASS and standalone.
>
> good news, would be probably good idea to document it somewhere on
> wiki since more users can have similar problem. Thanks, Ma

Yes, please add it here:

https://grasswiki.osgeo.org/wiki/WinGRASS_errors

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

Re: [GRASS-dev] [GRASS GIS] #3210: r.texture: bug when non continuous series of values

[GRASS GIS]

#3210: r.texture: bug when non continuous series of values
--+-
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  defect   | Status:  reopened
  Priority:  normal   |  Milestone:  7.2.0
 Component:  Raster   |Version:  svn-trunk
Resolution:   |   Keywords:  r.texture
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by neteler):

 Replying to [comment:28 mlennert]:
 ...

 > Ok, I've moved things around quite a lot and added some more notes. Now
 the description is short and focuses on the explanation of the actual
 parameters of the module and more detailed content discussion is in the
 notes.
 ...
 > IMHO, this is ready to go into the other branches, especially 7.2 before
 its release. However, should I merge all of the different commits we did
 in the last days, or can I just copy over the r.texture.html file ? Don't
 know what consequences that has on svn history...

 Current best practice in case of '''HTML pages''':

 copy over the entire file if you want everything to be taken over (or use
 e.g. "meld" otherwise). Then a commit mesg like this:


 {{{
 svn ci -m"r.texture manual: sync to trunk (rxxx, ryyy, ...)"
 raster/r.texture/r.texture.html
 }}}

 Like this anyone can look up the individual modifications. We stopped
 copying the svn history across branches some time ago since it caused more
 troubles than gave advantages.

 Note: in case of C or Python source code backports this script is better:

 {{{
 grass-addons/tools/svn-merge.sh
 }}}

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] svn instructions needed

[Markus Neteler]

On Sat, Nov 26, 2016 at 8:20 AM, Moritz Lennert
 wrote:
> Hi,
>
> Just a quick question about mergin between branches.
>
> In the course of the work on #3210 concerning r.texture [1], MarkusM and I
> have repeatedly modified the html man page in trunk. I would like to merge
> this back into the other branches. Do I need to individually merge all the
> different commits, or can I just copy over the finished version of the html
> file ? What is better in terms of svn history ?

Current best practice in case of *HTML* pages:

copy over the entire file if you want everything to be taken over (or
use e.g. "meld" otherwise).

Then a commit mesg like this:

svn ci -m"r.texture manual: sync to trunk (rxxx, ryyy, etc)"
raster/r.texture/r.texture.html

Like this anyone can look up the individual modifications.

Markus

PS: in case of C or Python source code backports this script is better:
grass-addons/tools/svn-merge.sh
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [RCs] GRASS 7.2.0RC2

[Martin Landa]

Hi,

2016-11-24 22:36 GMT+01:00 Markus Neteler :
> https://trac.osgeo.org/grass/wiki/Release/7.2.0-News#ReleaseCandidate1RC2
>
> Please package it, thanks.

* Windows packages (stanalone and osgeo4w) are ready and uploaded for testing.
* UbuntuGIS Experimental PPA updated also

(will be mentioned in news)

Ma

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev