Re: [GRASS-dev] [GRASS-user] Fwd: [Projects] OSGeo Annual General Meeting - projects please join and report (August 30 2018)

[Vaclav Petras]

Items for the presentation can be collected (and preserved!) at the
following wiki page which I created based on the description for the slides.

https://trac.osgeo.org/grass/wiki/AnnualReports/2018

Here is what we showed in 2017 (slides 33 & 34):

https://docs.google.com/presentation/d/1T9QRcCdyd8PLQnXB2VfZ2k3ReX-9CH_YXRg0VKqtgeQ/edit?usp=sharing
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Make Changes to Modules in Grass GIS

[Vaclav Petras]

On Fri, Aug 3, 2018 at 9:50 AM, Vidura Dantanarayana 
wrote:

> Hi all,
> I have installed ubuntu, downloaded the source code from
> https://grass.osgeo.org/grass74/source/grass-7.4.1.tar.gz and installed
> grass-dev package. Since I do not have experience with c can you again
> briefly explain how to do changes and compile the code. Is the workflow
> following is correct to do what I intended.
>
> 1) copy r.ros folder from grass-7.4.1/raster and rename it as r.new.ros
> 2) make relevant changes to main.c file in r.new.ros
>


Yes and yes.



> 3) compile the code with 'make' command.
>

You will need to provide parameters to help make find the GRASS GIS
installation and where to put the compiled module. The g.extension module
will do this for you if you do something like this:

g.extension extension=r.new.ros url=/path/to/r.new.ros



>
> * can you explain what the grass-dev package does.
>

Usually, for most packages on Linux, the files needed for development, e.g.
linking with the library, are not distributed together with the library and
program in the package without -dev (since unless you do development you
don't need them). If you install the grass-dev package you get, for example
the C header files for the libraries (that's actually most of what you
get). You can list all these files using:

dpkg --listfiles grass-dev

Additionally, you should also get all the compile-time dependencies of
GRASS GIS not only the runtime ones which is very useful.

HTH,
Vaclav


> Thank you. Have a nice day.
>
> BR,
> Vidura Dantanarayana
>
> ___
> 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] #3613: addons/r.convergence

[GRASS GIS]

#3613: addons/r.convergence
--+-
  Reporter:  selvaje  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:
 Component:  Addons   |Version:  unspecified
Resolution:   |   Keywords:  convergence
   CPU:  Unspecified  |   Platform:  Linux
--+-

Comment (by selvaje):

 files
 wget https://www.dropbox.com/s/72ndnxtpiqqhmvx/tmp.tar.gz
 wget
 https://www.dropbox.com/s/aw5szez5xspqjon/convergence_10KMmedian_MERIT.pdf

-- 
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] #3613: addons/r.convergence

[GRASS GIS]

#3613: addons/r.convergence
-+-
 Reporter:  selvaje  |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  normal   |  Milestone:
Component:  Addons   |Version:  unspecified
 Keywords:  convergence  |CPU:  Unspecified
 Platform:  Linux|
-+-
 Hi
 I noticed a strange behavior of r.convergence in some tiles of my digital
 elevation model.
 In few words if I process a single tile I obtain a convergence result if I
 combine 4 tiles and rerun r.convergence I obtain another result. Such
 behavior appear only in few tiles along the same longitudinal gradient
 (see pdf). Seams to me that is something related with the bounding box of
 the tiles and the calculation of the distance.
 I'm doubting that is something related to the tiling system because I have
 computed several other topographic variables and the problem appear only
 with r.convergence.

 I attach the tar.gz with the data and the script to reproduce the error.

 Thanks for the support
 Giuseppe
 GRASS GIS 7.3.svn

-- 
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] #3601: db.connect: default answers depend on current DB settings

[GRASS GIS]

#3601: db.connect: default answers depend on current DB settings
---+--
  Reporter:  mmetz |  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  normal|  Milestone:  7.4.2
 Component:  Database  |Version:  svn-trunk
Resolution:|   Keywords:  database, connection
   CPU:  All   |   Platform:  All
---+--

Comment (by mmetz):

 In [changeset:"73039" 73039]:
 {{{
 #!CommitTicketReference repository="" revision="73039"
 db.connect: use GRASS default, not current parameters as default answer,
 fix setting from default and from user options (see #3601; backport trunk
 r72942)
 }}}

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Fwd: [Projects] OSGeo Annual General Meeting - projects please join and report (August 30 2018)

[Luca Delucchi]

On 3 August 2018 at 15:48, Markus Neteler  wrote:
> Hi devs, all,
>

Hi,

> for the upcoming FOSS4G conference we shall prepare a quick (2 minute)
> project update for GRASS GIS, like last year.
>
> Who will be in Dar and willing to present our updates there?
>

I will be there and available.

> Happy to help collecting the material. Also catchy screenshots are
> always welcome!
>

yes please,  I have few time to work on it...

> thanks
> Markus
>


-- 
ciao
Luca

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

[GRASS-dev] Make Changes to Modules in Grass GIS

[Vidura Dantanarayana]

Hi all,
I have installed ubuntu, downloaded the source code from
https://grass.osgeo.org/grass74/source/grass-7.4.1.tar.gz and installed
grass-dev package. Since I do not have experience with c can you again
briefly explain how to do changes and compile the code. Is the workflow
following is correct to do what I intended.

1) copy r.ros folder from grass-7.4.1/raster and rename it as r.new.ros
2) make relevant changes to main.c file in r.new.ros
3) compile the code with 'make' command.

* can you explain what the grass-dev package does.
Thank you. Have a nice day.

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

[GRASS-dev] Fwd: [Projects] OSGeo Annual General Meeting - projects please join and report (August 30 2018)

[Markus Neteler]

Hi devs, all,

for the upcoming FOSS4G conference we shall prepare a quick (2 minute)
project update for GRASS GIS, like last year.

Who will be in Dar and willing to present our updates there?

Happy to help collecting the material. Also catchy screenshots are
always welcome!

thanks
Markus


-- Forwarded message --
From: Astrid Emde (OSGeo Secretary) 
Date: Thu, Aug 2, 2018 at 10:13 PM
Subject: [Projects] OSGeo Annual General Meeting - projects please
join and report (August 30 2018)
To: Projects 


Dear OSGeo projects & project officers,

the OSGeo Annual General Meeting (AGM) is scheduled for Thursday
morning August 30 at 8:00-9:00 in Dar Es Salaam (Tansania).

As Project/Committee officer we ask that you attend, or send a
delegate from your community. The FOSS4G organizers have given us one
hour for the meeting, leaving us each with around 2 mins!

This update is about your project and community, rather than about
your software. We are interested in how your community is doing, the
opportunities and challenges ahead, and how OSGeo can help.

The shared slide deck is available here (request edit access if required):

* 
https://docs.google.com/presentation/d/1imiG7x09ry7lGvmS15FCVq2Z7yaICY00fcpXBK27TXY/edit?usp=sharing

These slides replace the "Annual General Report"
(https://github.com/geotools/geotools/wiki/GeoTools-Annual-Report-2017)
used previously, you may wish to borrow that format for inspiration.
You still can make an annual report page with extended information if
you like and link to it.

If you are unable to attend we ask that you submit an annual general
report to the board email list and attend an IRC board meeting by
November 2018.

We are coordinating activities on the OSGeo Wiki
(https://wiki.osgeo.org/wiki/Annual_General_Meeting_2018). Please add
your project and name to the wiki if you can attend.

Best regards

Astrid Emde (OSGeo Secretary)

--
-
Astrid Emde
OSGeo Board Member and OSGeo Secretary
Open Source Geospatial Foundation
https://www.osgeo.org/member/astrid-emde/
astrid_e...@osgeo.org

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

Re: [GRASS-dev] [GRASS GIS] #3612: g.gui.tplot: error when calling from terminal

[GRASS GIS]

#3612: g.gui.tplot: error when calling from terminal
--+-
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:
 Component:  wxGUI|Version:  svn-trunk
Resolution:  fixed|   Keywords:  g.gui.tplot
   CPU:  Unspecified  |   Platform:  Linux
--+-
Changes (by veroandreo):

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


Comment:

 Replying to [comment:1 lucadelu]:
 > Please try r73032.

 It works now, no errors. Thanks!

 I close as fixed, since this is related to a new feature and IIUC it
 should not be backported. Reopen if needed.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] pygrass v.import_() strange error

[Yann Chemin]

Great, thanks a lot Pietro !

On Fri, Aug 3, 2018, 07:55 Pietro  wrote:

> Thank you Yann and Vaclav, I was not aware of this issue:
>
> On Thu, Aug 2, 2018 at 5:06 AM, Vaclav Petras 
> wrote:
>
>> >>> a.import()
>>   File "", line 1
>> a.import()
>>^
>> SyntaxError: invalid syntax
>>
>
> I've fixed the the code to support the use of underscore for python
> reserved words and add two doctests in  r73029.
>
> Best regards
>
> pietro
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] No 'count' method for r.statistics

[Nikos Alexandris]

* Markus Metz  [2018-08-01 20:33:33 +0200]:


On Wed, Aug 1, 2018 at 11:59 AM, Nikos Alexandris 
wrote:


`r.statistics` which was/is meant for categorical raster maps, does not
provide for a 'count' method.

`r.stats.zonal`, on the other hand, which is meant for floating point
raster maps, does so.

This is rather unexpected. 'Count'ing pixels should rather derive 'CELL'
maps and not 'FCELL'.

At the moment, I require an extra mapcalc using the int() function.

Any comments?


Counting pixels can produce a result that is too large for CELL (32 bit
integer), therefore storing the count as DCELL is a bit safer because it
can exactly store integers larger than the 32 bit maximum.

In short, use r.stats.zonal rather than r.statistics.

Markus M


I understand it now.

If integrating this extra "int()" conversion, in `r.stats.zonal`, is not
a smart/wanted thing to do, maybe we should add an explanation in the
`r.statistics` manual. Why 'count' is missing and why `r.stats.zonal` should
be used.

I can offer a patch for the manual if you agree.

My guess is that the development team has future plans regarding all r.stat*
modules, to merge and simplify as much as possible.

Thank you Markus!


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] [GRASS GIS] #3612: g.gui.tplot: error when calling from terminal

[GRASS GIS]

#3612: g.gui.tplot: error when calling from terminal
--+-
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:  g.gui.tplot
   CPU:  Unspecified  |   Platform:  Linux
--+-

Comment (by lucadelu):

 Please try r73032.

-- 
Ticket URL: 
GRASS GIS 

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