Re: [GRASS-dev] [GRASS GIS] #3038: Decide if validity check in r.in.lidar should be an additional filter or a filter enabled by default

[GRASS GIS]

#3038: Decide if validity check in r.in.lidar should be an additional filter or 
a
filter enabled by default
-+-
  Reporter:  wenzeslaus  |  Owner:  grass-dev@…
  Type:  task| Status:  new
  Priority:  normal  |  Milestone:  7.2.0
 Component:  Raster  |Version:  svn-trunk
Resolution:  |   Keywords:  r.in.lidar, r3.in.lidar,
   CPU:  |  v.in.lidar, libLAS, PDAL
  Unspecified|   Platform:  Unspecified
-+-

Comment (by wenzeslaus):

 Replying to [comment:1 mlennert]:
 > ...the general rule of no API changes within the same major number
 releases...

 It is changing behavior because the output might be different. However, it
 does not break scripts in general, although you might just get more points
 or invalid points depending on your data. So. if it is an API break
 depends on how much you care about invalid points in your data. The two
 people on GIS SE didn't know about point validity and they actually want
 all the points. I personally wouldn't know about validity if I didn't know
 about the function call in the source code. (This is a call for anybody
 who would be negatively affected by the change.)

 Moreover, we don't promise validity G7:r.in.lidar filtering in the manual,
 so the claim can be that invalid point filtering not behavior one should
 rely upon.

 > ...points are also declared invalid if the no scan angle is stored at
 all, i.e. there are two different kinds of invalidity: those which are
 based on a too large angle (and liblas seems to be quite restrictive,
 limiting this to -90 - 90 - whereas more recent [http://www.asprs.org/wp-
 content/uploads/2010/12/LAS_1_4_r13.pdf LAS specifications] allow -180 -
 180).

 The mess around it suggests that there is no clearly defined validity.
 When validity itself is not clearly defined in standard and it changes for
 individual properties with different format versions, what the library is
 actually doing and how it behaves (will behave) with different format
 versions? This seems to me like a buggy feature which should be disabled.


 > * Add a flag to ignore validity checks

 I still think that this change in the API is worth it. It might be even a
 fix. So, I'm still for the opposite flag.

 > * Understand why scan angle 0 is declared invalid ... and solve that

 We can do some checks ourselves which would likely change the results/API
 as well. But I don't know what to study anyway and if it is even worth it
 as the practice may be really different from the theory here.

 > * In the long run: determine whether libLAS is still a good choice...

 Right. I think PDAL (which BTW doesn't have any validity check) is a good
 replacement, but I wasn't able to touch it for some time (#2732).

--
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] #1410: scalebar displays multiples north arrows

[GRASS GIS]

#1410: scalebar displays multiples north arrows
--+-
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.0.5
 Component:  Display  |Version:  svn-trunk
Resolution:  fixed|   Keywords:  d.barscale, ll, north arrow
   CPU:  Unspecified  |   Platform:  All
--+-
Changes (by annakrat):

 * 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] #1242: vector fills and line widths not displaying in latlon regions

[GRASS GIS]

#1242: vector fills and line widths not displaying in latlon regions
-+-
  Reporter:  cmbarton|  Owner:  grass-dev@…
  Type:  defect  | Status:  closed
  Priority:  normal  |  Milestone:  7.0.5
 Component:  Display |Version:  svn-trunk
Resolution:  fixed   |   Keywords:  vector, display, d.vect,
   CPU:  |  d.northarrow, cartography, gsoc2016
  Unspecified|   Platform:  Unspecified
-+-
Changes (by annakrat):

 * 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] #1242: vector fills and line widths not displaying in latlon regions

[GRASS GIS]

#1242: vector fills and line widths not displaying in latlon regions
-+-
  Reporter:  cmbarton|  Owner:  grass-dev@…
  Type:  defect  | Status:  new
  Priority:  normal  |  Milestone:  7.0.5
 Component:  Display |Version:  svn-trunk
Resolution:  |   Keywords:  vector, display, d.vect,
   CPU:  |  d.northarrow, cartography, gsoc2016
  Unspecified|   Platform:  Unspecified
-+-

Comment (by annakrat):

 In [changeset:"68551" 68551]:
 {{{
 #!CommitTicketReference repository="" revision="68551"
 d.northarrow: fix multiplication of arrow in latlon regions, see #1242 and
 #1410 (merge from trunk, r68531)
 }}}

--
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] #1410: scalebar displays multiples north arrows

[GRASS GIS]

#1410: scalebar displays multiples north arrows
--+-
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.0.5
 Component:  Display  |Version:  svn-trunk
Resolution:   |   Keywords:  d.barscale, ll, north arrow
   CPU:  Unspecified  |   Platform:  All
--+-

Comment (by annakrat):

 In [changeset:"68551" 68551]:
 {{{
 #!CommitTicketReference repository="" revision="68551"
 d.northarrow: fix multiplication of arrow in latlon regions, see #1242 and
 #1410 (merge from trunk, r68531)
 }}}

--
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] #1410: scalebar displays multiples north arrows

[GRASS GIS]

#1410: scalebar displays multiples north arrows
--+-
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.0.5
 Component:  Display  |Version:  svn-trunk
Resolution:   |   Keywords:  d.barscale, ll, north arrow
   CPU:  Unspecified  |   Platform:  All
--+-

Comment (by annakrat):

 In [changeset:"68550" 68550]:
 {{{
 #!CommitTicketReference repository="" revision="68550"
 d.northarrow: fix multiplication of arrow in latlon regions, see #1242 and
 #1410 (merge from trunk, r68531)
 }}}

--
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] #1242: vector fills and line widths not displaying in latlon regions

[GRASS GIS]

#1242: vector fills and line widths not displaying in latlon regions
-+-
  Reporter:  cmbarton|  Owner:  grass-dev@…
  Type:  defect  | Status:  new
  Priority:  normal  |  Milestone:  7.0.5
 Component:  Display |Version:  svn-trunk
Resolution:  |   Keywords:  vector, display, d.vect,
   CPU:  |  d.northarrow, cartography, gsoc2016
  Unspecified|   Platform:  Unspecified
-+-

Comment (by annakrat):

 In [changeset:"68550" 68550]:
 {{{
 #!CommitTicketReference repository="" revision="68550"
 d.northarrow: fix multiplication of arrow in latlon regions, see #1242 and
 #1410 (merge from trunk, r68531)
 }}}

--
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] #3011: OSGeo4W-winGRASS71 r68376: starting wxgui fails

[GRASS GIS]

#3011: OSGeo4W-winGRASS71 r68376: starting wxgui fails
---+-
  Reporter:  hellik|  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  critical  |  Milestone:  7.2.0
 Component:  wxGUI |Version:  svn-trunk
Resolution:|   Keywords:
   CPU:  x86-64|   Platform:  MSWindows 7
---+-

Comment (by annakrat):

 Can someone confirm the fix and close this?

--
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] #3046: Cannot set display font

[GRASS GIS]

#3046: Cannot set display font
--+--
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  major|  Milestone:  7.0.5
 Component:  wxGUI|Version:  7.0.4
Resolution:   |   Keywords:  display font
   CPU:  Unspecified  |   Platform:  MacOSX
--+--

Comment (by annakrat):

 In [changeset:"68549" 68549]:
 {{{
 #!CommitTicketReference repository="" revision="68549"
 wxGUI: fix font dialogs on Mac, see #3046, merged from trunk r68532,
 r68535, r68545
 }}}

--
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] #3046: Cannot set display font

[GRASS GIS]

#3046: Cannot set display font
--+--
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  major|  Milestone:  7.0.5
 Component:  wxGUI|Version:  7.0.4
Resolution:  fixed|   Keywords:  display font
   CPU:  Unspecified  |   Platform:  MacOSX
--+--
Changes (by annakrat):

 * 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] #3046: Cannot set display font

[GRASS GIS]

#3046: Cannot set display font
--+--
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  major|  Milestone:  7.0.5
 Component:  wxGUI|Version:  7.0.4
Resolution:   |   Keywords:  display font
   CPU:  Unspecified  |   Platform:  MacOSX
--+--

Comment (by annakrat):

 In [changeset:"68548" 68548]:
 {{{
 #!CommitTicketReference repository="" revision="68548"
 wxGUI: fix font dialogs on Mac, see #3046, merged from trunk r68532,
 r68535, r68545
 }}}

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] GSoC 2016

[Blumentrath, Stefan]

Hei Mayank and Rashad,

And thanks for this very cool GSoC project!
Do you take some inspiration from RStudio Server? We use it and are quite happy 
with it. Nice features there are (for my taste) the editor, the console and 
git/svn integration? And also GRASS is most sexy with the command line at hand. 
But I can imagine that such things are not feasible within this project?...

Kind regards,
Stefan

From: grass-dev [mailto:grass-dev-boun...@lists.osgeo.org] On Behalf Of Mayank 
Agrawal
Sent: 22. mai 2016 09:14
To: grass-dev@lists.osgeo.org
Subject: [GRASS-dev] GSoC 2016

Hi all,

I am Mayank Agrawal and I am a research student in Lab for Spatial Informatics 
in International Institute of Information Technology, Hyderabad,India. I am 
working on GRASS GIS project for GSoC 2016. My proposal is WebGrass, which will 
focus on the development of web based GUI for the Grass, where people can use 
Grass modules through a web browser without actually installing GRASS. GRASS 
will be running on a server. The user interface will be built using wt web 
toolkit.


Here
 is the Abstract.

Source code is hosted on Github and 
here is my fork under the 
branch gsoc2016.

Here is my first pull 
request

We are using 
Gitter
 for our communication.

This is the wiki on GRASS 
Trac.
And project WebGrass is running Here on server.




Sent with 
MailTrack
[Image removed by sender.]
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS testsuite

[Sören Gebbert]

Hi Michael,
the GRASS gunittest framework is exactly what you are looking for. Please
have a look at its excellent documentation:
https://grass.osgeo.org/grass71/manuals/libpython/gunittest_running_tests.html
https://grass.osgeo.org/grass71/manuals/libpython/gunittest_testing.html

However, the test coverage is not very high for raster and vector modules.
Feel free to implement new tests for all modules that you would like to
have tested.

Here is a recent test run, that shows all modules that were tested:
http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2016-05-24-07-00/report_for_nc_basic_spm_grass7_nc/testfiles.html

Best regards
Soeren

2016-05-31 23:08 GMT+02:00 Michael Barton :

> I've never tried the GRASS test suite, but thought it could be a better
> way to check binary builds than the ad hoc tests I make now. But I'm not
> sure how to use it. I looked at the GRASS WIKI but everything about the
> test suite has been deprecated, even thought it still ships with the GRASS
> code base.
>
> Is it still in use?
>
> The GRASS gunittest page seems to be about a way to test individual
> modules, or to test changes to the source code.
>
> My goal is to test a binary to make sure that things work properly before
> I distribute.
>
> Any advice?
>
> Michael
>
> 
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Professor of Anthropology, School of Human Evolution & Social Change
> Head, Graduate Faculty in Complex Adaptive Systems Science
> Arizona State University
>
> voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GRASS testsuite

[Michael Barton]

I've never tried the GRASS test suite, but thought it could be a better way to 
check binary builds than the ad hoc tests I make now. But I'm not sure how to 
use it. I looked at the GRASS WIKI but everything about the test suite has been 
deprecated, even thought it still ships with the GRASS code base.

Is it still in use?

The GRASS gunittest page seems to be about a way to test individual modules, or 
to test changes to the source code.

My goal is to test a binary to make sure that things work properly before I 
distribute.

Any advice?

Michael


C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu















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

Re: [GRASS-dev] [GRASS GIS] #3046: Cannot set display font

[GRASS GIS]

#3046: Cannot set display font
--+--
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  major|  Milestone:  7.0.5
 Component:  wxGUI|Version:  7.0.4
Resolution:   |   Keywords:  display font
   CPU:  Unspecified  |   Platform:  MacOSX
--+--

Comment (by cmbarton):

 Custom font dialogs for Mac now work great in GRASS trunk r68543.

 Thanks!

 Michael

--
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] #3046: Cannot set display font

[GRASS GIS]

#3046: Cannot set display font
--+--
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  major|  Milestone:  7.0.5
 Component:  wxGUI|Version:  7.0.4
Resolution:   |   Keywords:  display font
   CPU:  Unspecified  |   Platform:  MacOSX
--+--

Comment (by cmbarton):

 Here are 2 wxWidget tickets for the problem. One suggests a possible
 workaround and the other suggests it may be fixed in the next version of
 wxPython.

 http://trac.wxwidgets.org/ticket/13908

 http://trac.wxwidgets.org/ticket/16643

 Michael

--
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] #3046: Cannot set display font

[GRASS GIS]

#3046: Cannot set display font
--+--
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  major|  Milestone:  7.0.5
 Component:  wxGUI|Version:  7.0.4
Resolution:   |   Keywords:  display font
   CPU:  Unspecified  |   Platform:  MacOSX
--+--

Comment (by annakrat):

 In [changeset:"68545" 68545]:
 {{{
 #!CommitTicketReference repository="" revision="68545"
 wxGUI: remove condition for wxpython3, native font dialog doesn't work
 with any version on Mac, see #3046
 }}}

--
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] #3046: Cannot set display font

[GRASS GIS]

#3046: Cannot set display font
--+--
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  major|  Milestone:  7.0.5
 Component:  wxGUI|Version:  7.0.4
Resolution:   |   Keywords:  display font
   CPU:  Unspecified  |   Platform:  MacOSX
--+--

Comment (by annakrat):

 Replying to [comment:5 cmbarton]:
 > I just compiled GRASS trunk (7.3) and tested. There does not seem to be
 any change in the preferences behavior. Map Display font button opens
 custom font selection list and Appearance font button opens wxPython font
 manager (and locks up GUI). Am I testing the wrong code base?

 The display font was not working, as you reported. As for the other font,
 I assume you have wxPython 2.8 and I think I limited the changes to
 wxPython 3, because I forgot it's problem in 2.8 as well, I will change
 it.

--
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] #1242: vector fills and line widths not displaying in latlon regions

[GRASS GIS]

#1242: vector fills and line widths not displaying in latlon regions
-+-
  Reporter:  cmbarton|  Owner:  grass-dev@…
  Type:  defect  | Status:  new
  Priority:  normal  |  Milestone:  7.0.5
 Component:  Display |Version:  svn-trunk
Resolution:  |   Keywords:  vector, display, d.vect,
   CPU:  |  d.northarrow, cartography, gsoc2016
  Unspecified|   Platform:  Unspecified
-+-

Comment (by cmbarton):

 I can confirm that these are all fixed in GRASS trunk r68543. No multiple
 north arrows, vector area fills and borders behave properly. Thanks much!

 Michael

--
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] #3046: Cannot set display font

[GRASS GIS]

#3046: Cannot set display font
--+--
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  major|  Milestone:  7.0.5
 Component:  wxGUI|Version:  7.0.4
Resolution:   |   Keywords:  display font
   CPU:  Unspecified  |   Platform:  MacOSX
--+--

Comment (by cmbarton):

 I just compiled GRASS trunk (7.3) and tested. There does not seem to be
 any change in the preferences behavior. Map Display font button opens
 custom font selection list and Appearance font button opens wxPython font
 manager (and locks up GUI). Am I testing the wrong code base?

--
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] #3017: support for background option for grid labels in d.grid

[GRASS GIS]

#3017: support for background option for grid labels in d.grid
--+---
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.3.0
 Component:  Display  |Version:  unspecified
Resolution:   |   Keywords:  d.grid, gsoc2016, cartography
   CPU:  Unspecified  |   Platform:  Unspecified
--+---
Changes (by lazaa):

 * Attachment "d.grid3.diff" added.

 Labels are displayed in front of grid lines.

--
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] #3017: support for background option for grid labels in d.grid

[GRASS GIS]

#3017: support for background option for grid labels in d.grid
--+---
  Reporter:  veroandreo   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.3.0
 Component:  Display  |Version:  unspecified
Resolution:   |   Keywords:  d.grid, gsoc2016, cartography
   CPU:  Unspecified  |   Platform:  Unspecified
--+---

Comment (by lazaa):

 Replying to [comment:9 annakrat]:
 > Replying to [comment:8 veroandreo]:
 > > Hi, I'm happy to have background option in d.grid :)
 > >
 > > I did a quick test and I attach an example below. I noted that when
 choosing white background for grid labels, I loose part of the map in the
 east (See no-transparency in fig 1 vs transparency in fig 2). So,
 background of labels seems to be a continuous white strip for Y
 coordinate, while it's fine for X coordinate.
 >
 > I can confirm this, the size of the background rectangle still needs
 fixing, the problem showed up only in latlon for me.

 I tried to find the problem, but I didn't succeed :(

 > >
 > > On the other hand, grid lines overlap the white background of labels,
 while IMHO, label should always be in front.
 >
 > Yes, the horizontal labels are fine, just the vertical ones are below
 the grid lines.

 I fixed this problem. Now the grid lines are drawn first (both vertical
 and horizontal) and after that are drawn labels so at final they are shown
 in front.

 > >
 > > I personally don't like the border tickmarks of d.grid but when
 disabling them, labels remain aligned as if there were border tickmarks
 (last fig). Maybe they could be aligned more close to the border (if not
 against it) as in ps.map.
 > >
 > > And, would that be possible to also change font of labels?? :)
 > >
 > You can do that from GUI settings - you set display font for all d.*
 commands.

--
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] #3042: Patches to make the build reproducible (fileordering, randomness)

[GRASS GIS]

#3042: Patches to make the build reproducible (fileordering, randomness)
--+-
  Reporter:  sebastic |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  critical |  Milestone:  7.0.5
 Component:  Compiling|Version:  7.0.4
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Linux
--+-

Comment (by glynn):

 Replying to [ticket:3042 sebastic]:

 > 2) Randomness issue: html/colortables/random.png is built using a
 pseudo-random generator seeded with build-time value. See patch `04
 -srand48_auto-from-SOURCE_DATE_EPOCH.patch` that uses the [https
 ://reproducible-builds.org/specs/source-date-epoch/ SOURCE_DATE_EPOCH]
 environment variable (when set) to set a seed from last `debian/changelog`
 entry date.

 While I agree with the idea, G_srand48_auto() shouldn't be using this
 variable directly, but something more appropriate, e.g. GRASS_RANDOM_SEED
 (or GRASS_RND_SEED, which is what r.mapcalc used prior to the RNG
 changes).

 Debian can then set that variable from $SOURCE_DATE_EPOCH as part of their
 build process.

 In theory, modules which use randomness should be providing a command-line
 option to get the seed, with G_srand48_auto() only being used if the user
 specifically wants a non-deterministic seed. But that probably isn't going
 to happen in the foreseeable future.

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [SoC]Week-1 WebGrass

[Rashad Kanavath]

Hello Luca,

You can test it now.

But I think you need a fresh rebuild. the default of GRASS_DATA_DIR is
$HOME/grassdata.



On Mon, May 30, 2016 at 2:21 PM, Rashad Kanavath  wrote:

>
>
> On Mon, May 30, 2016 at 2:19 PM, Luca Delucchi 
> wrote:
>
>> On 30 May 2016 at 14:15, Rashad Kanavath 
>> wrote:
>> > No.
>> >
>>
>> ok,
>>
>> > I need to add it. Mayank will be working on other task this week. He is
>> > right now on building layer manager
>> >
>>
>> let us know when it will be ready to test, thanks
>>
>
> Sure. Will do.
>
>>
>> --
>> ciao
>> Luca
>>
>> www.lucadelu.org
>>
>
>
>
> --
> Regards,
>Rashad
>



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

Re: [GRASS-dev] v.reclass more columns

[Luca Delucchi]

On 31 May 2016 at 12:22, Moritz Lennert  wrote:
> On 31/05/16 11:18, Luca Delucchi wrote:
>>
>> Hi devs,
>>
>> Is it possible to extend the column option in v.reclass to accept more
>> than one column?
>
>
> But if you combine several columns, you would have to define rules. And this
> is exactly what the rules parameter is for which let's you define SQL-like
> rules combining as many columns as you want ?
>

But I would like to use something like a GROUP BY statement, and I
don't know the values of cat in advance, should be this possible?

>> sometimes is really useful to reclass/dissolve using more columns and
>> also it is useful to keep more data in the attribute table.
>
> The problem is if you combine several features into one category, then which
> attributes should you keep ?
>

I want to combine several features into one category only if the
attributes are the same, so it should keep all the attributes

> Moritz

-- 
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] v.reclass more columns

[Moritz Lennert]

On 31/05/16 11:18, Luca Delucchi wrote:

Hi devs,

Is it possible to extend the column option in v.reclass to accept more
than one column?


But if you combine several columns, you would have to define rules. And 
this is exactly what the rules parameter is for which let's you define 
SQL-like rules combining as many columns as you want ?


> sometimes is really useful to reclass/dissolve using more columns and
> also it is useful to keep more data in the attribute table.

The problem is if you combine several features into one category, then 
which attributes should you keep ?


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

Re: [GRASS-dev] [GRASS GIS] #3043: Change default color table

[GRASS GIS]

#3043: Change default color table
--+---
  Reporter:  wenzeslaus   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  blocker  |  Milestone:  7.2.0
 Component:  Raster   |Version:  svn-trunk
Resolution:   |   Keywords:  r.colors, d.rast, rainbow
   CPU:  Unspecified  |   Platform:  Unspecified
--+---

Comment (by mlennert):

 Replying to [comment:10 wenzeslaus]:
 > Replying to [comment:5 mlennert]:
 > > I think that if we provide a default color table (here ''map'') of
 which we say that it is good (better than rainbow), we should make our
 criteria more explicit.
 >
 > Article on Gnuplotting (citing Moreland, 2009) lists these features for
 a default color table and I'm adding my notes in the nested lists:

 Wow, you're really putting a lot of research into this. Thanks !

 I agree with all you are saying (I never defended rainbow as a good color
 table !), and if you all think that having a better (not good, as I don't
 think that exists, but better) default color table, then go for it. As
 said, if we change, then personally I would prefer grey (as this would
 force people to chose if they want color), but I hear what you are saying
 about the marketing aspect.

 One aspect your review doesn't seem to take into account is categorized
 maps. Many of the above arguments only relate to continuous, quantitative
 values, not qualitative data (and the landuse map in viridis is not very
 nice... ;-)), but I guess this is impossible to detect automatically, so
 different defaults for different types of maps does not make sense.

 So, for me, go ahead with whatever you feel is right...

--
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] v.reclass more columns

[Luca Delucchi]

Hi devs,

Is it possible to extend the column option in v.reclass to accept more
than one column?

sometimes is really useful to reclass/dissolve using more columns and
also it is useful to keep more data in the attribute table.

If this make sense I will open a ticket

-- 
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] [GRASS GIS] #3052: Watts to MegaJoules/Day conversion issue

[GRASS GIS]

#3052: Watts to MegaJoules/Day conversion issue
--+-
  Reporter:  cholmes  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.0.5
 Component:  Imagery  |Version:  unspecified
Resolution:   |   Keywords:  i.evapo.mh
   CPU:  Unspecified  |   Platform:  All
--+-
Changes (by martinl):

 * keywords:   => i.evapo.mh
 * component:  Default => Imagery


--
Ticket URL: 
GRASS GIS 

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