Re: [GRASS-dev] [GRASS GIS] #3114: v.kriging: images in manual do not show (and when shown should be bigger)

2016-08-29 Thread Markus Neteler 
On Sun, Aug 28, 2016 at 11:08 PM, Eva Stopková  wrote:
> Dear all,
>
>>  The v.kriging addon could do with a bit more love for documentation: In
>>  the  manual the images are not shown. All images as in an 'images'
>>  directory within the addons directory, but that images directory does not
>>  get installed together with the addon.
>>
>>  I don't know if there is Makefile magic to install that directory.
>
> I have tried adding VPATH [1] to the Makefile.

This will not work and also not necessarily portable. And image
copying is already implemented :) and no private solution should be
implemented.

See
include/Make/HtmlRules.make

> I would like to ask... does
> the issue with missing images happen just here [2]

Yes.

> or does it appear in general?

No

> I have tried to install the modules from addons (after cleaning my
> GRASS) and the images seem to work correctly in my computer. I would like to
> understand the issue better, may I ask what is the difference between
> compiling module at user's computer and here [2]?

If the images are at root directory of the addon nothing has to be
done in the addon Makefile and it will work on any platform.

>> The other solution is to put all images into the root directory of the
>> addon.
>
> I would prefer them to stay in separate subdirectories, but if it won't
> work, I shall replace them.

Why do you need a separate subdirectory (especially images/small/)?
Maybe a Makefile trick could be added to support a subdirectoy but two
of them are not ideal.

[...]

Best,
Markus

> [1] https://www.gnu.org/software/make/manual/html_node/General-Search.html
> [2] https://grass.osgeo.org/grass70/manuals/addons/v.kriging.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [vincent...@oslandia.com: Re: [Qgis-developer] issue move to gh stalled]

2016-08-29 Thread Nikos Alexandris 


Hi GRASSers,

anyone interested in this? I use both github and gitlab as well. The
latter (actually gitlab.com) because of the option for cost-free private
repositories.

I did install once gitlab locally. It was like a 5 minute work.

Cheers, Nikos



- Forwarded message from "Vincent Picavet (ml)"  
-


Subject: Re: [Qgis-developer] issue move to gh stalled
From: "Vincent Picavet (ml)" 
To: "qgis-develo...@lists.osgeo.org" , "strk 
(s...@keybit.net)" , Björn Harrtell 
Date: Mon, 29 Aug 2016 09:33:16 +0200

Hello,

Just a note to say that SAC is currently testing an OSGeo GitLab
instance. It is on a temporary server, but may be used freely and can be
used for testing and migration purpose.

What is currently lacking is not setup time, but instead :
* a decision from OSGeo's community on what we do want to use as a
modern software hosting platform
* a maintainance team
* a better server for the definitive setup

I think that if QGIS is willing to migrate to GitLab, using this
opportunity to join forces with current SAC effort would be great.
CCed to Bjorn and Sandro who currently lead the testing effort.

You can already give it a try here (latest GitLab version) :
https://git.osgeo.org/gitlab/

Vincent

Just a On 27/08/2016 13:47, Tudor Barascu wrote:

Hi all,

I am volunteering to install, do maintenance if you'll go the gitlab
way. I would have said this from the start but I didn't notice that such
a discussion was taking place. I am positive that I would manage this I
have good enough experience with system administration and I'm actually
maintaning a gitlab private instance for about 2 years now.
Although I can manage it on my own it would be very nice if somebody
else would also be involved.
I can also help with migrating the issues from redmine to gitlab.

Regards,
Tudor

PS. I think gitlab would be the better option


On Saturday, August 27, 2016 12:00 PM, Andreas Neumann
 wrote:


Hi Denis,
We had a look at hosted solutions (for Gitlab and for Redmine) - but
most of them had been too expensive for our case - they have a limit on
the number of users that can be associated with a project, or other
limits like file sizes/total project size, etc.
Running our own gitlab instance would have been an option, but no one
volunteered to take on the task of permanently maintaining the
infrastructure, e.g. dealing with security issues/patching/upgrading,
spammers, deal with the evil guys out on the web. Maybe if we can find
someone who wants to take on the task (ideally more than one person), we
could reconsider to use a self-hosted gitlab.
Note that the new Redmine instance has some integration with github.
Jürgen, Richard or Pirmin can tell you the details.

What is so bad with Redmine? And exactly what integration with github
are you missing? Maybe Redmine can do this integration.

Andreas

Am 26.08.2016 um 23:03 schrieb Denis Rouzaud:

Hi all,
Being part of the unhappy, I would like to ask if you have considered
running our own gitlab instance or using a gitlab service?
To me integrated solution should be a hard requirement.
If we have to maintain something like Redmine, why not gitlab. It
seems you can categorize issues.
Denis

Le ven. 26 août 2016 22:24, Andreas Neumann mailto:a.neum...@carto.net>> a écrit :

Hi,

The issue tracker was discussed almost 1.5h at the board meeting - and
it wasn't a clear and unanimous decision. Some board members
(including
me) also changed their minds during the discussion. Apparently not all
core devs were happy with the quite limited filtering and structuring
options that github offers. The issue tracker is certainly quite
limited, compared to other issue tracker offerings. Offering only
labels
is quite limited. In addition, migrating all the existing tickets from
Redmine to Github turned out to be non-trivial - and we don't want to
loose the old issues.

Finally, it is probably good that we are in control of the issues and
that it runs on free software. The board knows that not all people are
happy with this decision but one cannot make everyone happy ... we
hope
that the "unhappy" people can still live with the renewed (and faster)
Redmine.

The issues are migrated to the newest Redmine version and on a
dedicated
machine rented by QGIS.ORG  to ensure good
performance. This should make
dealing with issues much more pleasant and more performant.

Big thanks to Jürgen, Richard and Pirmin for dealing with the Redmine
migration.

Andreas

Am 26.08.2016 um 22:08 schrieb Marco Bernasocchi:
> .
>
>
>> I was under the impression that we were leaning towards to
migrating
>> to GH issues tracker.
>> What was the main reason behind choosing Redmine again? technical
>> issues? lack of time to solve them? Will the migration to a new
>> Redmine version be effortless?
>>
> Me too. I'm still convinced that th

Re: [GRASS-dev] [vincent...@oslandia.com: Re: [Qgis-developer] issue move to gh stalled]

2016-08-29 Thread Luca Delucchi 
On 29 August 2016 at 10:04, Nikos Alexandris  wrote:
>
> Hi GRASSers,
>

Hi,

> anyone interested in this? I use both github and gitlab as well. The
> latter (actually gitlab.com) because of the option for cost-free private
> repositories.
>

yes sure, we could start to move something there like promo material
there just to start really to use it

> I did install once gitlab locally. It was like a 5 minute work.
>

ok, but now we don't need to install new instance, we can use that one

> Cheers, Nikos
>


-- 
ciao
Luca

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

Re: [GRASS-dev] [vincent...@oslandia.com: Re: [Qgis-developer] issue move to gh stalled]

2016-08-29 Thread Markus Neteler 
On Mon, Aug 29, 2016 at 10:24 AM, Luca Delucchi  wrote:
> On 29 August 2016 at 10:04, Nikos Alexandris  wrote:
>>
>> Hi GRASSers,
>>
>
> Hi,
>
>> anyone interested in this?

Yes! On the previous beta installation of
https://git.osgeo.org/gitlab/

there was already a GRASS git repo, see
https://lists.osgeo.org/pipermail/grass-dev/2016-June/080687.html

Seems to be outdated but I'll ask Sandro about this.

...
> yes sure, we could start to move something there like promo material
> there just to start really to use it

Good idea.

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

Re: [GRASS-dev] Towards SVN - git integration

2016-08-29 Thread Markus Neteler 
(back to this thread as it comes with a better subject title)


-- Forwarded message --
From: Markus Neteler 
Date: Mon, Aug 29, 2016 at 11:54 AM
Subject: Re: [GRASS-dev] [vincent...@oslandia.com: Re:
[Qgis-developer] issue move to gh stalled]
To: Luca Delucchi 
Cc: Nikos Alexandris , GRASS-dev


On Mon, Aug 29, 2016 at 10:24 AM, Luca Delucchi  wrote:
> On 29 August 2016 at 10:04, Nikos Alexandris  wrote:
>>
>> Hi GRASSers,
>>
>
> Hi,
>
>> anyone interested in this?

Yes! On the previous beta installation of
https://git.osgeo.org/gitlab/

there was already a GRASS git repo, see
https://lists.osgeo.org/pipermail/grass-dev/2016-June/080687.html
--> https://git.osgeo.org/gogs/grass/grassgis

it seems to be outdated but I'll ask Sandro about this.
Or Pietro Z knows?

...
> yes sure, we could start to move something there like promo material
> there just to start really to use it

Good idea.

The current state of git related OSGeo services is listed here:

https://wiki.osgeo.org/wiki/SAC:Git_Service

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

Re: [GRASS-dev] [GRASS GIS] #3136: move v.krige to addons

2016-08-29 Thread GRASS GIS 
#3136: move v.krige to addons
--+-
  Reporter:  martinl  |  Owner:  grass-dev@…
  Type:  task | Status:  new
  Priority:  blocker  |  Milestone:  7.2.0
 Component:  Addons   |Version:  unspecified
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by neteler):

 * priority:  normal => blocker


--
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] #3136: move v.krige to addons

2016-08-29 Thread GRASS GIS 
#3136: move v.krige to addons
--+-
  Reporter:  martinl  |  Owner:  grass-dev@…
  Type:  task | Status:  new
  Priority:  blocker  |  Milestone:  7.2.0
 Component:  Addons   |Version:  unspecified
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by mlennert):

 Replying to [ticket:3136 martinl]:
 > I suggest to move `v.krige` from main repository to addons before
 releasing 7.2.0. The module is not mature enough, and relies on external
 dependency (`rgrass7`). Such module should be distributed as addons and
 not as a part of core distribution.

 +1

 But this also means that GRASS GIS does not have any native kriging
 anymore, only 2 extensions (v.krige and v.kriging). It would be great to
 one day have a native implementation in core.

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Planning of GRASS GIS 6.4.6 release

2016-08-29 Thread Moritz Lennert 

On 17/08/16 09:30, Markus Neteler wrote:

On Thu, Aug 11, 2016 at 11:18 AM, Markus Neteler  wrote:

Hi,

gentle reminder that the 6.4.6 release is due.

Coordination is done here:
http://trac.osgeo.org/grass/wiki/Grass6Planning

Open bugs concerning GRASS 6.x
https://trac.osgeo.org/grass/report/16

News page (to be completed) at:
https://trac.osgeo.org/grass/wiki/Release/6.4.6-News

Any objections to prepare RC1?


Now available at
https://grass.osgeo.org/grass64/source/
--> https://grass.osgeo.org/grass64/source/grass-6.4.6RC1.tar.gz

Please test it!


The release having been tagged and source code already available, what 
is left that needs to be done for releasing 6.4.6 ?


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

Re: [GRASS-dev] Planning of GRASS GIS 6.4.6 release

2016-08-29 Thread Markus Neteler 
On Mon, Aug 29, 2016 at 3:16 PM, Moritz Lennert
 wrote:
...
> The release having been tagged and source code already available, what is
> left that needs to be done for releasing 6.4.6 ?

I have the announcement almost done. So, sit & wait that I get a
moment later today to upload the stuff :-)

The FOSS4G 2016 only ended yesterday, hence the delay.

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

Re: [GRASS-dev] Towards SVN - git integration

2016-08-29 Thread Pietro 
Hi Markus,

On Mon, Aug 29, 2016 at 1:12 PM, Markus Neteler  wrote:
> (back to this thread as it comes with a better subject title)
> there was already a GRASS git repo, see
> https://lists.osgeo.org/pipermail/grass-dev/2016-June/080687.html
> --> https://git.osgeo.org/gogs/grass/grassgis
>
> it seems to be outdated but I'll ask Sandro about this.
> Or Pietro Z knows?

Actually I just synced manually (git svn fetch), perhaps we can simply
configure GRASS server that for each commit just sync the git
repository.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Planning of GRASS GIS 6.4.6 release

2016-08-29 Thread Moritz Lennert 

On 29/08/16 15:19, Markus Neteler wrote:

On Mon, Aug 29, 2016 at 3:16 PM, Moritz Lennert
 wrote:
...

The release having been tagged and source code already available, what is
left that needs to be done for releasing 6.4.6 ?


I have the announcement almost done. So, sit & wait that I get a
moment later today to upload the stuff :-)

The FOSS4G 2016 only ended yesterday, hence the delay.


It was not a critique of the delay, but a inquiry to know if you need 
help with anything. ;-)


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

[GRASS-dev] Results of GRASS-GIS' PSC-2016 Election

2016-08-29 Thread Nikos Alexandris 

Dear GRASS GIS community,

the new Project Steering Committee is composed by the following nine
members:

1  Markus Neteler62
2  Helena Mitasova   53
3  Martin Landa  52
4  Anna Petrasova45
5  Moritz Lennert41
6  Margherita Di Leo 39
7  Michael Barton35
8  Peter Löwe33
9  Vaclav Petras 31

Congratulations!


A warm Thank You for their candidacy, and dedication to the project, goes
to:

-  Helmut Kurdnovsky 30
-  Yann Chemin   29
-  Veronica Andreo   28
-  Micha Silver  20


To keep track and for the sake of completeness, all relevant
communications will be published in one wiki-page (in trac).



Details

* The election URL: https://vote.heliosvoting.org/helios/e/GRASS-GIS-PSC-2016 
* Election Fingerprint: es9DDU1oPIxtyV9DE/cl402ctbm5PwaFhmLrruzsAJU


Remember, the entire election process was/is encrypted. The CRO, being
the administrator of this "private" election, could only verify which of
the invited members did vote. That and nothing more.


*Ballots*

Helios' voting system features "Audited Ballots". More information at:

https://vote.heliosvoting.org/helios/elections/397c5ce0-67c2-11e6-8e87-3e719e3f8c36/audited-ballots/.


*Election tally*

Even more, anyone should be able to verify the election tally at "Helios
Election Verifier":

https://vote.heliosvoting.org/verifier/verify.html?election_url=/helios/elections/397c5ce0-67c2-11e6-8e87-3e719e3f8c36.


*Trustee*

The trustee for this election was:

Trustee #1: Helios Voting Administrator
Public Key Fingerprint: 0mYM9DB3TVWlbURGBXiMnCb12Vsf4OJoFXBODOPl9os

Trustees are responsible for decrypting the election result. Each
trustee generates a keypair and submits the public portion to Helios.
When it's time to decrypt, each trustee needs to provide their secret
key.

For this election, however, the automcatically selected, by the system,
trustee was selected and no other persons where involved in this
process.


*Broken Links?*

If any of the links do not lead anywhere, please contact the CRO
publicly, in example by responding to this post.

Voters who casted a ballot, will receive another message sent via
Helios' directly.

For more, there is a FAQ: https://vote.heliosvoting.org/faq



Final words

As a CRO, I tried to serve this role as best possible.  Looking back on
the last few weeks, and having various off-list discussions, while at
Bonn last week, I identify and reflect on mistakes and things I could
have done better.

In time, I will try to collect some of the experiences and compose a
wiki-page (in trac).  However, I'd like to stress the following:  I feel
and think that I did not insist as much as I should, to assist in
profiling better the candidates.

There is this important question, asked by Micha Silver end of July (see
https://lists.osgeo.org/pipermail/grass-user/2016-July/074529.html),
"what we should expect from PSC members?"

Some of the candidates went a bit deeper in presenting themselves.
Others were less lengthy in their writing. All good.

However, I propose herewith, for the next PSC election, the following: set as a
requirement, for each candidate, to answer this very question as being
asked from the community: "What should the community expect from your
PSC membership?".


Thank you.
GRASS-GIS' CRO

As Nikos, thank you to the previous PSC for accepting me as the CRO this
year.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] New addon: v.in.pygbif from Code Sprint Bonn

2016-08-29 Thread Blumentrath, Stefan 
Dear Code-sprinters (and others),

Thanks for the awesome event and the great time in Bonn!
It was really exciting and a lot of fun working together with all of you. The 
experience definitely - more than - compensated travel costs and conference fee!

With the kind support from Lucca and Vero, the v.in.pygbif addon I was working 
on in Bonn is now finally usable and committed to addons.
v.in.pygbif builds upon Helmuts v.in.gbif addon and adds the possibility to 
query and fetch species occurrence data directly from GBIF.
In fact, it is more or less a graphical frontend to the pygbif package 
(http://pygbif.readthedocs.io/en/latest/index.html), which thus is a dependency 
of v.in.pygbif.

The GBIF data which is provided in WGS84 is re-projected into the projection of 
the current location at import. Import of global occurrences is by default 
limited to current computational region. This limit can be skipped in latlon 
locations.
Here my question is: Should I allow for unlimited/restricted import also in 
other CRS with global application? If yes, could you point me to EPSG codes of 
CRS you like me to add?

v.in.pygbif offers most of the relevant filter options from pygbif. I did some 
more testing yesterday, but still not all options are fully tested (also 
because the content of the returns from GBIF API are hard to predict)...
Anyway, I just pushed v.in.pygbif to addons together with a basic 
documentation. So, I would be glad for any test and report of issues / 
enhancements.

Many thanks again to Lucca and Vero for extensive testing and help along the 
way.

Known toDo`s are:

-Code clean up (e.g. some lines are a bit long)

-Add a cleanup routing when the user cancels / kills the process

-Handle layers in input mask map

-Proper implement shell script output for matching of taxon names

I hope it is of use for some of you...

Kind regards,
Stefan

P.S.: I would wish that the GBIF API would also provide information about the 
coordinate precision, which should be available in GBIF. Unfortunately this 
information does not seem to be available through the GBIF API :(.


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

Re: [GRASS-dev] [GRASS-user] Results of GRASS-GIS' PSC-2016 Election

2016-08-29 Thread Micha Silver 

Congrads to the members of the new PSC.

The community as a whole can rest assured that further development of 
GRASS will stay on track.


-- Original Message -- Subject: [GRASS-user] Results of 
GRASS-GIS' PSC-2016 Election Date: Mon, 29 Aug 2016 17:26:23 +0200 To: 
Grass-psc, Grass-user, Grass-dev From: Nikos Alexandris

Dear GRASS GIS community,

the new Project Steering Committee is composed by the following nine
members:

1  Markus Neteler62
2  Helena Mitasova   53
3  Martin Landa  52
4  Anna Petrasova45
5  Moritz Lennert41
6  Margherita Di Leo 39
7  Michael Barton35
8  Peter Löwe33
9  Vaclav Petras 31

Congratulations!


A warm Thank You for their candidacy, and dedication to the project, goes
to:

-  Helmut Kurdnovsky 30
-  Yann Chemin   29
-  Veronica Andreo   28
-  Micha Silver  20


To keep track and for the sake of completeness, all relevant
communications will be published in one wiki-page (in trac).



Details

* The election URL: 
https://vote.heliosvoting.org/helios/e/GRASS-GIS-PSC-2016 * Election 
Fingerprint: es9DDU1oPIxtyV9DE/cl402ctbm5PwaFhmLrruzsAJU


Remember, the entire election process was/is encrypted. The CRO, being
the administrator of this "private" election, could only verify which of
the invited members did vote. That and nothing more.


*Ballots*

Helios' voting system features "Audited Ballots". More information at:

https://vote.heliosvoting.org/helios/elections/397c5ce0-67c2-11e6-8e87-3e719e3f8c36/audited-ballots/. 




*Election tally*

Even more, anyone should be able to verify the election tally at "Helios
Election Verifier":

https://vote.heliosvoting.org/verifier/verify.html?election_url=/helios/elections/397c5ce0-67c2-11e6-8e87-3e719e3f8c36. 




*Trustee*

The trustee for this election was:

Trustee #1: Helios Voting Administrator
Public Key Fingerprint: 0mYM9DB3TVWlbURGBXiMnCb12Vsf4OJoFXBODOPl9os

Trustees are responsible for decrypting the election result. Each
trustee generates a keypair and submits the public portion to Helios.
When it's time to decrypt, each trustee needs to provide their secret
key.

For this election, however, the automcatically selected, by the system,
trustee was selected and no other persons where involved in this
process.


*Broken Links?*

If any of the links do not lead anywhere, please contact the CRO
publicly, in example by responding to this post.

Voters who casted a ballot, will receive another message sent via
Helios' directly.

For more, there is a FAQ: https://vote.heliosvoting.org/faq



Final words

As a CRO, I tried to serve this role as best possible.  Looking back on
the last few weeks, and having various off-list discussions, while at
Bonn last week, I identify and reflect on mistakes and things I could
have done better.

In time, I will try to collect some of the experiences and compose a
wiki-page (in trac).  However, I'd like to stress the following: I feel
and think that I did not insist as much as I should, to assist in
profiling better the candidates.

There is this important question, asked by Micha Silver end of July (see
https://lists.osgeo.org/pipermail/grass-user/2016-July/074529.html),
"what we should expect from PSC members?"

Some of the candidates went a bit deeper in presenting themselves.
Others were less lengthy in their writing. All good.

However, I propose herewith, for the next PSC election, the following: 
set as a

requirement, for each candidate, to answer this very question as being
asked from the community: "What should the community expect from your
PSC membership?".


Thank you.
GRASS-GIS' CRO

As Nikos, thank you to the previous PSC for accepting me as the CRO this
year.
___
grass-user mailing list
grass-u...@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user


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

Re: [GRASS-dev] Planning of GRASS GIS 6.4.6 release

2016-08-29 Thread Markus Neteler 
On Mon, Aug 29, 2016 at 5:20 PM, Moritz Lennert
 wrote:
> On 29/08/16 15:19, Markus Neteler wrote:
>>
>> On Mon, Aug 29, 2016 at 3:16 PM, Moritz Lennert
>>  wrote:
>> ...
>>>
>>> The release having been tagged and source code already available, what is
>>> left that needs to be done for releasing 6.4.6 ?
>>
>>
>> I have the announcement almost done. So, sit & wait that I get a
>> moment later today to upload the stuff :-)
>>
>> The FOSS4G 2016 only ended yesterday, hence the delay.
>
>
> It was not a critique of the delay, but a inquiry to know if you need help
> with anything. ;-)

Sure, no problem! In general help is seeked to share the workload of
posting the announcement as a press release.
The doc/howto_release.txt in the course code contains the links. BUT:
I can happily do that since it is the end of GRASS GIS 6 releases
anyway, so no big hype is needed here. Also the creation of binaries
is less important here perhaps.

 Getting related help for the next G7 releases would be great, i.e.
- write a catchy announcement
- add nice screenshot(s) to it
- provide binaries.

However, we may discuss that in the 7.0.5 planning email thread to not
mix it up with this one here.

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

Re: [GRASS-dev] Towards SVN - git integration

2016-08-29 Thread Markus Neteler 
On Mon, Aug 29, 2016 at 4:43 PM, Pietro  wrote:
> Hi Markus,
>
> On Mon, Aug 29, 2016 at 1:12 PM, Markus Neteler  wrote:
>> (back to this thread as it comes with a better subject title)
>> there was already a GRASS git repo, see
>> https://lists.osgeo.org/pipermail/grass-dev/2016-June/080687.html
>> --> https://git.osgeo.org/gogs/grass/grassgis
>>
>> it seems to be outdated but I'll ask Sandro about this.
>> Or Pietro Z knows?
>
> Actually I just synced manually (git svn fetch),

ah, I see.

> perhaps we can simply
> configure GRASS server that for each commit just sync the git
> repository.

Would Travis-CI provide that triggering?
Or, what needs to be done on grass.osgeo.org to achieve that?

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

Re: [GRASS-dev] [GRASS-user] Results of GRASS-GIS' PSC-2016 Election

2016-08-29 Thread Veronica Andreo 
Congratulations to the new GRASS PSC!

Thanks to all those that participated with their nominations and votes, and
thanks Nikos for your work as CRO!

Let all of us keep working together for this great project :)

Cheers!
Vero

El ago. 29, 2016 10:11 PM, "Micha Silver"  escribió:

> Congrads to the members of the new PSC.
>
> The community as a whole can rest assured that further development of
> GRASS will stay on track.
> -- Original Message -- Subject: [GRASS-user] Results of GRASS-GIS'
> PSC-2016 Election Date: Mon, 29 Aug 2016 17:26:23 +0200 To: Grass-psc,
> Grass-user, Grass-dev From: Nikos Alexandris
>
> Dear GRASS GIS community,
>
> the new Project Steering Committee is composed by the following nine
> members:
>
> 1  Markus Neteler62
> 2  Helena Mitasova   53
> 3  Martin Landa  52
> 4  Anna Petrasova45
> 5  Moritz Lennert41
> 6  Margherita Di Leo 39
> 7  Michael Barton35
> 8  Peter Löwe33
> 9  Vaclav Petras 31
>
> Congratulations!
>
>
> A warm Thank You for their candidacy, and dedication to the project, goes
> to:
>
> -  Helmut Kurdnovsky 30
> -  Yann Chemin   29
> -  Veronica Andreo   28
> -  Micha Silver  20
>
>
> To keep track and for the sake of completeness, all relevant
> communications will be published in one wiki-page (in trac).
>
>
>
> Details
>
> * The election URL: https://vote.heliosvoting.org/
> helios/e/GRASS-GIS-PSC-2016 * Election Fingerprint: 
> es9DDU1oPIxtyV9DE/cl402ctbm5PwaFhmLrruzsAJU
>
>
> Remember, the entire election process was/is encrypted. The CRO, being
> the administrator of this "private" election, could only verify which of
> the invited members did vote. That and nothing more.
>
>
> *Ballots*
>
> Helios' voting system features "Audited Ballots". More information at:
>
> https://vote.heliosvoting.org/helios/elections/397c5ce0-
> 67c2-11e6-8e87-3e719e3f8c36/audited-ballots/.
>
>
> *Election tally*
>
> Even more, anyone should be able to verify the election tally at "Helios
> Election Verifier":
>
> https://vote.heliosvoting.org/verifier/verify.html?election_
> url=/helios/elections/397c5ce0-67c2-11e6-8e87-3e719e3f8c36.
>
>
> *Trustee*
>
> The trustee for this election was:
>
> Trustee #1: Helios Voting Administrator
> Public Key Fingerprint: 0mYM9DB3TVWlbURGBXiMnCb12Vsf4OJoFXBODOPl9os
>
> Trustees are responsible for decrypting the election result. Each
> trustee generates a keypair and submits the public portion to Helios.
> When it's time to decrypt, each trustee needs to provide their secret
> key.
>
> For this election, however, the automcatically selected, by the system,
> trustee was selected and no other persons where involved in this
> process.
>
>
> *Broken Links?*
>
> If any of the links do not lead anywhere, please contact the CRO
> publicly, in example by responding to this post.
>
> Voters who casted a ballot, will receive another message sent via
> Helios' directly.
>
> For more, there is a FAQ: https://vote.heliosvoting.org/faq
>
>
>
> Final words
>
> As a CRO, I tried to serve this role as best possible.  Looking back on
> the last few weeks, and having various off-list discussions, while at
> Bonn last week, I identify and reflect on mistakes and things I could
> have done better.
>
> In time, I will try to collect some of the experiences and compose a
> wiki-page (in trac).  However, I'd like to stress the following:  I feel
> and think that I did not insist as much as I should, to assist in
> profiling better the candidates.
>
> There is this important question, asked by Micha Silver end of July (see
> https://lists.osgeo.org/pipermail/grass-user/2016-July/074529.html),
> "what we should expect from PSC members?"
>
> Some of the candidates went a bit deeper in presenting themselves.
> Others were less lengthy in their writing. All good.
>
> However, I propose herewith, for the next PSC election, the following: set
> as a
> requirement, for each candidate, to answer this very question as being
> asked from the community: "What should the community expect from your
> PSC membership?".
>
>
> Thank you.
> GRASS-GIS' CRO
>
> As Nikos, thank you to the previous PSC for accepting me as the CRO this
> year.
> ___
> grass-user mailing list
> grass-u...@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user
>
>
>
> ___
> grass-user mailing list
> grass-u...@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] grass 7.2 planning

2016-08-29 Thread Markus Neteler 
On Fri, May 27, 2016 at 12:02 PM, Markus Neteler  wrote:
> On Tue, May 24, 2016 at 7:39 PM, Markus Neteler  wrote:
...
> -  I also created a DRAFT: 
> https://trac.osgeo.org/grass/wiki/Release/7.2.0-News
...
> - important: please add fixes and your favourite improvements to the
> 7.2.0-News page (too much for one person to check)

Please :-)

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

Re: [GRASS-dev] [GRASS GIS] #2229: error in projection definition

2016-08-29 Thread GRASS GIS 
#2229: error in projection definition
-+-
  Reporter:  vincent |  Owner:  grass-dev@…
  Type:  defect  | Status:  new
  Priority:  normal  |  Milestone:  7.0.5
 Component:  Projections/Datums  |Version:  svn-releasebranch70
Resolution:  |   Keywords:  pseudomercator
   CPU:  Unspecified |   Platform:  Unspecified
-+-

Comment (by neteler):

 FYI: New details about lib/proj/ have been added to

 https://trac.osgeo.org/grass/browser/grass/trunk/lib/proj/README.txt

 along with the proj related CSV removal in r69211. Please test again.

--
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] #2757: r.import: ERROR: Input raster map is outside current region

2016-08-29 Thread GRASS GIS 
#2757: r.import: ERROR: Input raster map is outside current region
--+-
  Reporter:  neteler  |  Owner:  grass-dev@…
  Type:  defect   | Status:  reopened
  Priority:  normal   |  Milestone:  7.0.5
 Component:  Python   |Version:  svn-trunk
Resolution:   |   Keywords:  r.import
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by neteler):

 Yes (for the full test procedure, see original report above)

 {{{
 GRASS 7.3.svn (nc_spm_08_grass7):~ > g.region -dp
 projection: 99 (Lambert Conformal Conic)
 zone:   0
 datum:  nad83
 ellipsoid:  a=6378137 es=0.006694380022900787
 north:  32
 south:  1
 west:   12
 east:   935000
 nsres:  500
 ewres:  500
 rows:   620
 cols:   1630
 cells:  1010600

 GRASS 7.3.svn (nc_spm_08_grass7):~ > r.import input=bio1.bil
 output=bioclim1 resample=bilinear extent=region resolution=region
 Proceeding with import of 1 raster bands...
 WARNING: Fixing subtle input data rounding error of north boundary
  (2.84217e-14>2.8e-07)
 Importing raster map ...
  100%
 Estimated target resolution for input band : 4021.78765331
 Using current region resolution for input band : nsres=500.0,
 ewres=500.0
 Reprojecting ...
 ERROR: Input raster map is outside current region
 ERROR: Unable to to reproject raster 
 }}}

--
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] #1966: filesystem cruft from wingrass installer

2016-08-29 Thread GRASS GIS 
#1966: filesystem cruft from wingrass installer
+--
  Reporter:  hamish |  Owner:  grass-dev@…
  Type:  defect | Status:  closed
  Priority:  trivial|  Milestone:  7.0.5
 Component:  Packaging  |Version:  svn-trunk
Resolution:  fixed  |   Keywords:  wingrass
   CPU:  All|   Platform:  MSWindows XP
+--
Changes (by neteler):

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


--
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] #2540: [PATCH] Add options to r.out.gdal to suppress GRASS specific metadata items

2016-08-29 Thread GRASS GIS 
#2540: [PATCH] Add options to r.out.gdal to suppress GRASS specific metadata 
items
--+-
  Reporter:  rouault  |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.0.5
 Component:  Raster   |Version:  svn-trunk
Resolution:  fixed|   Keywords:  r.out.gdal
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by neteler):

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


--
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] #2752: t.remove: add dual-step removal as in g.remove

2016-08-29 Thread GRASS GIS 
#2752: t.remove: add dual-step removal as in g.remove
--+-
  Reporter:  neteler  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.4.0
 Component:  Temporal |Version:  svn-trunk
Resolution:   |   Keywords:  t.remove
   CPU:  All  |   Platform:  All
--+-

Comment (by neteler):

 Why not have it in 7.2?

--
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] #2234: wxGUI d.mon and g.gui monitor rendering is slow

2016-08-29 Thread GRASS GIS 
#2234: wxGUI d.mon and g.gui monitor rendering is slow
--+
  Reporter:  wenzeslaus   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  minor|  Milestone:  7.4.0
 Component:  wxGUI|Version:  unspecified
Resolution:   |   Keywords:  rendering, display
   CPU:  Unspecified  |   Platform:  All
--+

Comment (by neteler):

 Anything left here? It is wontfix for 7.0.x and done for 7.2.0, right?

 (And #2033 is stalled for 3 years...)

--
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] #2247: bivariate scatterplot: undefined variable issue

2016-08-29 Thread GRASS GIS 
#2247: bivariate scatterplot: undefined variable issue
--+-
  Reporter:  neteler  |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  minor|  Milestone:  7.0.5
 Component:  wxGUI|Version:  svn-releasebranch70
Resolution:  worksforme   |   Keywords:  scatterplot
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by neteler):

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


Comment:

 Seems to be gone, 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] #2229: error in projection definition

2016-08-29 Thread GRASS GIS 
#2229: error in projection definition
-+-
  Reporter:  vincent |  Owner:  grass-dev@…
  Type:  defect  | Status:  new
  Priority:  normal  |  Milestone:  7.0.5
 Component:  Projections/Datums  |Version:  svn-releasebranch70
Resolution:  |   Keywords:  pseudomercator
   CPU:  Unspecified |   Platform:  Unspecified
-+-

Comment (by vincent):

 still the same issue with r69289

--
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] #3136: move v.krige to addons

2016-08-29 Thread GRASS GIS 
#3136: move v.krige to addons
--+-
  Reporter:  martinl  |  Owner:  grass-dev@…
  Type:  task | Status:  new
  Priority:  blocker  |  Milestone:  7.2.0
 Component:  Addons   |Version:  unspecified
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by lucadelu):

 Yes, I think we could need, it could be a next year GSoC.

 Here some link to Python libraries if needed
 [https://github.com/bsmurphy/PyKrige PyKrige],
 [https://sourceforge.net/p/geoms2/wiki/Kriging/ simple kriging] or another
 [http://connor-johnson.com/2014/03/20/simple-kriging-in-python/ simple
 implementation]

--
Ticket URL: 
GRASS GIS 

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