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 wenzeslaus):

 `viridis` is now available in trunk (try `r.colors`). This color table was
 developed for Matplotlib based on color properties and color perception
 and then it won the community voting. See the attachments to see how it
 behaves including gray scale print and simulated color blindness (I can
 share also the full resolution images).

 The number one unresolved thing from my point of view is that `viridis`
 has 256 entries (most of the other color tables in GRASS has less than 20)
 and some test should be done to see if there is some performance
 difference. Also two pairs of colors are actually the same for the same
 values. (These issues can be resolved any time later.) Finally, it seems
 that on some screens `viridis` starts with more blueish color which
 doesn't look that good while on some other with more violet color which
 probably the right way (and looks better) but that's more a local issue.

 Is anybody opposed to the change of default color table from `rainbow` to
 `viridis` in GRASS GIS for release 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] #3049: g.proj.html: remove link to g.setproj in GRASS 7

[GRASS GIS]

#3049: g.proj.html: remove link to g.setproj in GRASS 7
--+-
  Reporter:  sbl  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.0.5
 Component:  Docs |Version:  unspecified
Resolution:   |   Keywords:  g.proj
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by sbl):

 * Attachment "g.proj_71.diff" added.


--
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] #3049: g.proj.html: remove link to g.setproj in GRASS 7

[GRASS GIS]

#3049: g.proj.html: remove link to g.setproj in GRASS 7
--+-
  Reporter:  sbl  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.0.5
 Component:  Docs |Version:  unspecified
Resolution:   |   Keywords:  g.proj
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by sbl):

 * Attachment "g.proj_70.diff" added.


--
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] [GRASS GIS] #3049: g.proj.html: remove link to g.setproj in GRASS 7

[GRASS GIS]

#3049: g.proj.html: remove link to g.setproj in GRASS 7
-+-
 Reporter:  sbl  |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  normal   |  Milestone:  7.0.5
Component:  Docs |Version:  unspecified
 Keywords:  g.proj   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 g.setproj does not exist any more in GRASS 7 but is still linked in the
 manual of g.proj. The link should be removed?

--
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] [GRASS GIS] #3048: r.out.gdal does not write EPSG code of the projection

[GRASS GIS]

#3048: r.out.gdal does not write EPSG code of the projection
+-
 Reporter:  sbl |  Owner:  grass-dev@…
 Type:  defect  | Status:  new
 Priority:  normal  |  Milestone:  7.0.5
Component:  Raster  |Version:  svn-trunk
 Keywords:  r.out.gdal  |CPU:  Unspecified
 Platform:  All |
+-
 GeoTiffs produced with GRASS GIS 6.4, 7.0.4 and 7.1.svn do not contain the
 AUTHORITY parameter for the projection, which is thus not properly
 recognized by other tools (e.g. QGIS, but esp. GeoServer).

 Related discussion on the GDAL mailinglist can be found here:
 http://thread.gmane.org/gmane.comp.gis.gdal.devel/43019

 g.proj -w gave the projection information as in the GeoTIFF, though
 without any AUTHORITY parameters (as it is supposed to according to the
 manual). The AUTHORITY tags seem to be added by r.out.gdal, except for the
 authority parameter for the entire projection. Even if g.proj -g returns
 epsg=25832.

 Compared to GDALs GeoTIFFs also AXIS parameters are missing (see below).

 {{{

 GRASS 7.0.4svn (ETRS_32N):~ >g.proj -g
 name=ETRS89 / UTM zone 32N
 datum=etrs89
 ellps=grs80
 proj=utm
 zone=32
 towgs84=0,0,0,0,0,0,0
 no_defs=defined
 epsg=25832
 unit=meter
 units=meters
 meters=1
 GRASS 7.0.4svn (ETRS_32N):~ >
 GRASS 7.0.4svn (ETRS_32N):~ >r.out.gdal input=test output=$HOME/test.tif
 GRASS 7.0.4svn (ETRS_32N):~ >gdalinfo $HOME/test.tif
 (...)
 Coordinate System is:
 PROJCS["UTM Zone 32, Northern Hemisphere",
 GEOGCS["grs80",
 DATUM["European_Terrestrial_Reference_System_1989",
 SPHEROID["Geodetic_Reference_System_1980",6378137,298.257222101,
 AUTHORITY["EPSG","7019"]],
 TOWGS84[0,0,0,0,0,0,0],
 AUTHORITY["EPSG","6258"]],
 PRIMEM["Greenwich",0],
 UNIT["degree",0.0174532925199433]],
 PROJECTION["Transverse_Mercator"],
 PARAMETER["latitude_of_origin",0],
 PARAMETER["central_meridian",9],
 PARAMETER["scale_factor",0.9996],
 PARAMETER["false_easting",50],
 PARAMETER["false_northing",0],
 UNIT["metre",1,
 AUTHORITY["EPSG","9001"]]]
 Origin = (0.000,1.000)
 Pixel Size = (1.000,-1.000)
 (...)
 GRASS 7.0.4svn (ETRS_32N):~ >
 GRASS 7.0.4svn (ETRS_32N):~ >gdal_translate -a_srs EPSG:25832
 $HOME/test.tif $HOME/test2.tif
 GRASS 7.0.4svn (ETRS_32N):~ >gdalinfo $HOME/test2.tif
 (...)
 Coordinate System is:
 PROJCS["ETRS89 / UTM zone 32N",
 GEOGCS["ETRS89",
 DATUM["European_Terrestrial_Reference_System_1989",
 SPHEROID["GRS 1980",6378137,298.257222101,
 AUTHORITY["EPSG","7019"]],
 TOWGS84[0,0,0,0,0,0,0],
 AUTHORITY["EPSG","6258"]],
 PRIMEM["Greenwich",0,
 AUTHORITY["EPSG","8901"]],
 UNIT["degree",0.0174532925199433,
 AUTHORITY["EPSG","9122"]],
 AUTHORITY["EPSG","4258"]],
 PROJECTION["Transverse_Mercator"],
 PARAMETER["latitude_of_origin",0],
 PARAMETER["central_meridian",9],
 PARAMETER["scale_factor",0.9996],
 PARAMETER["false_easting",50],
 PARAMETER["false_northing",0],
 UNIT["metre",1,
 AUTHORITY["EPSG","9001"]],
 AXIS["Easting",EAST],
 AXIS["Northing",NORTH],
 AUTHORITY["EPSG","25832"]]
 Origin = (0.000,1.000)
 Pixel Size = (1.000,-1.000)
 (...)
 }}}

--
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] GSoC: Basic cartography suite in GRASS - Week 1

[Adam Laža]

Hi all,

below is my first week report.

Best regards,
Adam
Wiki page:
https://trac.osgeo.org/grass/wiki/GSoC/2016/BasicCartographySuiteInGRASS


Bounding period, April, 22 - May, 22

I got in touch with my mentors. We discussed some possibilities for
development.
I installed Ubuntu, GRASS and QtCreator on my laptop.
I got little bit stucked with QtCreator Debugger, but with my mentors help
it works now.
I looked at the bug #2494[1] and did a little research on it.
I fixed the bug #2436[2]. X-axis ticks labels now work in d.histogram.

Week 1, May, 23-27

1. What did you get done this week?

I worked on the module d.northarrow.
I solved the ticket #3018[3] and added option for custom north-arrow label.
I solved the ticket #3019[4] and added more north-arrow symbols.
I solved the ticket #3031[5] and added option for north-arrow symbol
rotation.
I fixed the bug #1242[6] module now works in Lat-Long projection too but I
need discuss the solution with my mentors.

I worked on the module d.barscale.
I solved the ticket #3016[7], added option length for custom barscale size,
option segment for setting number of segments of barscale,
added flag -u to display full unit name/only symbol. I need discuss the
solution with my mentors.
I solved the ticket #3020[8] and added flag for displaying a capital N with
a simple arrow over it next to the barscale.

I worked on the module d.grid.
I solved the ticket #3017[8] and added option to choose background color of
grid labels.

2. What do you plan on doing next week?
Next week I want to continue with others d.* modules and look on d.text and
d.vect modules.

3. Are you blocked on anything?
I don't think I am blocked on anything but I work in slow pace because all
d.* modules are written in C which I have few experience with.


[1]: https://trac.osgeo.org/grass/ticket/2494
[2]: https://trac.osgeo.org/grass/ticket/2463
[3]: https://trac.osgeo.org/grass/ticket/3018
[4]: https://trac.osgeo.org/grass/ticket/3019
[5]: https://trac.osgeo.org/grass/ticket/3031
[6]: https://trac.osgeo.org/grass/ticket/1242
[7]: https://trac.osgeo.org/grass/ticket/3016
[8]: https://trac.osgeo.org/grass/ticket/3020
[9]: https://trac.osgeo.org/grass/ticket/3017
___
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.grid.diff" added.

 Added option bg_color to choose background color of grid labels

--
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] #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
--+---
Changes (by wenzeslaus):

 * Attachment "color_tables_overview_small.jpg" added.

 Overview of different rasters visualized with proposed color tables with
 color blidness simulated by ImageMagic

--
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] [GRASS GIS] #3047: MySQL driver failed to install

[GRASS GIS]

#3047: MySQL driver failed to install
--+-
 Reporter:  fpouw |  Owner:  grass-dev@…
 Type:  defect| Status:  new
 Priority:  normal|  Milestone:  7.0.5
Component:  Database  |Version:  7.0.4
 Keywords:  mysql driver  |CPU:  Unspecified
 Platform:  MSWindows 7   |
--+-
 A recent install of GRASS7 is missing the MySQL driver.
 The result of db.driver does not list 'mysql' it and the db.connect
 command (executed without a driver specified) returns an error that
 'mysql' is out of the domain of accepted values.

--
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 - PyQt

[Ondřej Pešek]

Hi,

thanks for your response.

2016-05-25 17:26 GMT+02:00 Pietro :

>
> Perhaps, it could be useful to have a look at pygrass `Module` class [0],
> that already parse the generated xml and instantiate `Parameter` class [1]
> that validate the input from the user in the `_check_value` function [2].
> So should be possible to dynamically generate a `Qt Widget` from a
> `Parameter` instance and then compose everything in complete final
> `QtWidget`/`QtDialog`. If you think that  in the `Module` / `Parameter`
> class definition something is missing/wrong or bad implemented, after
> discussion, we can change it. They were not developed with this use case in
> mind and perhaps some changes are needed however I do think they are a
> starting point...
>
>
Thank you, 'Module' is really nice. I was working with 'task', but 'Module'
looks much better.



> I think that we should support both: PyQt and PySide, and I think you
> should use as primary choice for development Python3, support for Python2
> it is much easier to add later if needed.
>
>
Well, I have never worked with Python3. But of course I can try it. It
might be useful to learn it and if you think it's better. I have created
basics in Python2 but it was one week - so it's not thousands of lines. I
can still retype it. Thanks for idea.


I'm studying the rest (thanks, it really helps me),
Ondrej



Bez
virů. www.avast.com

<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3016: Add option to set scalebar length

[GRASS GIS]

#3016: Add option to set scalebar length
--+---
  Reporter:  annakrat |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.3.0
 Component:  Display  |Version:  unspecified
Resolution:   |   Keywords:  d.barscale, gsoc2016, cartography
   CPU:  Unspecified  |   Platform:  All
--+---
Changes (by lazaa):

 * Attachment "d.barscale.2.diff" added.

 Updated patch with flag -n to display small north-arrow symbol next to
 barscale.

--
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] #3020: Make N with arrow optional in d.barscale styles

[GRASS GIS]

#3020: Make N with arrow optional in d.barscale styles
-+-
  Reporter:  wenzeslaus  |  Owner:  grass-dev@…
  Type:  defect  | Status:  new
  Priority:  minor   |  Milestone:  7.3.0
 Component:  Display |Version:  unspecified
Resolution:  |   Keywords:  vector, d.barscale, cartography,
   CPU:  |  gsoc2016
  Unspecified|   Platform:  Unspecified
-+-
Changes (by lazaa):

 * Attachment "d.barscale.diff" added.

 Added flag -n to display small north-arrow symbol next to barscale.

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] next community sprint in Genova?

[Luca Delucchi]

On 27 May 2016 at 11:38, Luca Delucchi  wrote:
> Hi devs,
>
> I was asked if we want organize a community sprint next year in Genova?
>
> As 3 years ago there will be also the italian conference of GRASS and
> GFOSS users (where we could have some reserved time) and we could have
> a room at university for the entire working week. If we want to code
> also during the weekend I can find another room.
>

sorry I forgot the month, it should be February

-- 
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 7.2 planning

[Markus Neteler]

On Tue, May 24, 2016 at 7:39 PM, Markus Neteler  wrote:
> grass/branches/releasebranch_7_2

Related updates:
 - I have generated new grass72/ and grass73/ directories on the
server, with all the file timestamps maintained in the tarballs :)
-  I also created a DRAFT: https://trac.osgeo.org/grass/wiki/Release/7.2.0-News
-  updated most pages in the CMS for the new versions
-  added: 
https://grass.osgeo.org/news/57/15/New-GRASS-GIS-7-2-x-stable-release-branch-created/

trac related:
- Question: I don't remember how I made the "G7:" macro in trac for
release notes: we need to add now "G72:" there
- important: please add fixes and your favourite improvements to the
7.2.0-News page (too much for one person to check)

Thanks.

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

[GRASS-dev] next community sprint in Genova?

[Luca Delucchi]

Hi devs,

I was asked if we want organize a community sprint next year in Genova?

As 3 years ago there will be also the italian conference of GRASS and
GFOSS users (where we could have some reserved time) and we could have
a room at university for the entire working week. If we want to code
also during the weekend I can find another room.

Please let me know

-- 
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] #3016: Add option to set scalebar length

[GRASS GIS]

#3016: Add option to set scalebar length
--+---
  Reporter:  annakrat |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.3.0
 Component:  Display  |Version:  unspecified
Resolution:   |   Keywords:  d.barscale, gsoc2016, cartography
   CPU:  Unspecified  |   Platform:  All
--+---

Comment (by lazaa):

 Replying to [comment:1 wenzeslaus]:
 > I think the size should be specified in map units, for example user can
 say `size=250` to get 250m scale bar. This seems like a simple and
 actually a desired option. What are the units there probably depend on the
 rest of the implementation or interface of d.barscale. With the current
 implementation it would be probably meters by default but it should be
 feet when the `-f` is used.

 I added option{{{length}}}, so the size can be specified in map units. By
 defaults in meters, with {{{-f}}} flag in feet. I'm not sure it's the best
 solution. If user wants a barscale of size let's say 150 miles he has to
 convert 150 miles into feet.

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] v.info layer option

[Luca Delucchi]

On 26 May 2016 at 23:21, Markus Metz  wrote:
> Hi Luca,
>

Hi Markus

> apparently [0] the layer option is only needed for v.info -c (Print
> types/names of table columns for specified layer instead of info and
> exit). What information about a vector do you want to get? Note that
> vector objects (points, lines, boundaries, areas) are always present,
> even if they are not linked to a layer at all. Maybe v.category
> option=report is more appropriate for your needs?
>

yes v.category is the right answer, thanks

> A question like this should rather go to the user ml.
>

yes I suppose it, so I'm going to register there :-)

> Markus M
>

-- 
ciao
Luca

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