Re: [GRASS-dev] [GRASS GIS] #3591: r.import does not recognize selected file

[GRASS GIS]

#3591: r.import does not recognize selected file
--+-
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  major|  Milestone:  7.6.0
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:  r.import
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by cmbarton):

 It's the GUI wrapper.

-- 
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] #3606: m.nviz.image produces a screenshot

[GRASS GIS]

#3606: m.nviz.image produces a screenshot
---+-
  Reporter:  epifanio  |  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  major |  Milestone:
 Component:  Display   |Version:  svn-trunk
Resolution:|   Keywords:
   CPU:  x86-64|   Platform:  Linux
---+-

Comment (by hcho):

 Replying to [comment:4 epifanio]:
 > Applied the patch on latest trunk rev. num.: 72990
 >
 > print out the following output:
 >
 >
 > {{{
 > GRASS 7.5.svn (nc_basic_spm_grass7):~ > m.nviz.image
 elevation_map=elevation output=elev perspective=15 --o
 > Loading raster map ...
 >  100%
 > Loading raster map ...
 >  100%
 > Translating colors from raster map ...
 >  100%
 > buffer: both
 > buffer: both
 > buffer: both
 > buffer: both
 > buffer: both
 > buffer: both
 > buffer: both
 > buffer: swap
 > buffer: both
 > m.nviz.image complete. File  created.
 >
 > }}}
 >
 > My grass_trunk is configured without X11 support:

 This is my output:
 {{{
 buffer: back
 buffer: both
 buffer: back
 buffer: both
 buffer: back
 buffer: both
 buffer: back
 buffer: swap
 buffer: back
 }}}

 In your case, GS_set_draw(GSD_BACK) never worked. That's weird. Please add
 {{{fprintf(stderr, "draw where: %d\n", where);}}} in line 2465 in
 lib/ogsf/gs2.c. GSD_FRONT 1, GSD_BACK 2, and GSD_BOTH 3 are defined in
 include/ogsf.h.

 Anyway, I think you need X11 support because Nviz requires some Xlib
 functions (XOpenDisplay, XCreatePixmap, XFree, ...) in lib/nviz/render.c.
 Please try it again with X11 support enabled. Is there any specific reason
 why you disabled it?

-- 
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] #3591: r.import does not recognize selected file

[GRASS GIS]

#3591: r.import does not recognize selected file
--+-
  Reporter:  cmbarton |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  major|  Milestone:  7.6.0
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:  r.import
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by mmetz):

 * milestone:   => 7.6.0


Comment:

 Is this a problem of the GUI of r.import or of r.import itself, i.e. does
 the error appear when run on the CLI or when run in the GUI?

-- 
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] #3585: Don't require -c for --tmp-location

[GRASS GIS]

#3585: Don't require -c for --tmp-location
-+-
  Reporter:  wenzeslaus  |  Owner:  grass-dev@…
  Type:  | Status:  new
  enhancement|
  Priority:  normal  |  Milestone:  8.0.0
 Component:  Startup |Version:  svn-trunk
Resolution:  |   Keywords:  init, grass.py, location, tmp-
   CPU:  |  location, CRS, CLI, gsoc2018
  Unspecified|   Platform:  Unspecified
-+-

Comment (by neteler):

 Short feedback: I've started to use `--tmp-location`, it works nicely!

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [release planning] 7.6.0

[Michael Barton]

I think there has been no change yet. Normally, Anna would ask me to test any 
major fixes. 

The other item I forgot about and just now ran into is that the import modules 
are broken. We can still use r.in.gdal, v.in.ogr, etc, but not the nice 
integrated modules. My guess from the error is that this will be a fairly 
simple fix. I did a bug report on Trac awhile back. 

My other guess is that the problems are mostly (all?) from deprecated or 
non-'standard' wx code that does not work correctly in wxPython 3+. Since all 
of GRASS will need to migrate to this soon, it will be good to get it cleared 
up.

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

On 7/15/18, 1:05 PM, "neteler.os...@gmail.com on behalf of Markus Neteler" 
 wrote:

On Tue, Jun 12, 2018 at 1:10 AM, Michael Barton  
wrote:
> Anna is making significant headway in fixing remaining serious bugs in 
the GUI, although she has a lot of other things taking up her time. I just 
compiled and uploaded a new 7.5 svn binary with these fixes.
>
> The main remaining one is the vector digitizer (hopefully the interactive 
image classification module is the same problem). It would be really nice to 
have a working digitizer in the next stable version.

... what is the current state here?

thanks
Markus


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

Re: [GRASS-dev] [release planning] 7.6.0

[Markus Neteler]

On Tue, Jun 12, 2018 at 1:10 AM, Michael Barton  wrote:
> Anna is making significant headway in fixing remaining serious bugs in the 
> GUI, although she has a lot of other things taking up her time. I just 
> compiled and uploaded a new 7.5 svn binary with these fixes.
>
> The main remaining one is the vector digitizer (hopefully the interactive 
> image classification module is the same problem). It would be really nice to 
> have a working digitizer in the next stable version.

... what is the current state here?

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

Re: [GRASS-dev] Report assigned color table for a map

[Markus Neteler]

On Mon, Jul 9, 2018 at 10:53 AM, Nikos Alexandris
 wrote:
> How do we know a map has already a color table assigned?
> Wouldn't this be "important" to have it reported by `r.info`, for example?

Yes, would make sense to me (also in r3.info).

This code snippet may do it (raster/r.colors/edit_colors.c, line 322:)

# for r.info:
int have_colors;
have_colors = Rast_read_colors(name, mapset, &colors);


# for r3.info
int have_colors;
have_colors = Rast3d_read_colors(name, mapset, &colors);

Would you write a patch?

> Also, `r.colors` does "-w Only write new color table if it does not
> already exist". But how do we report an "existing" color table (of
> course, except of manually checking if a map's name file exists in
> colr)?
>
> By the way, maybe this one message can be changed to:
> "-w  Create only if the map has no color table assigned"

maybe something like
"-w  Create color table only none yet assigned"

?

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

Re: [GRASS-dev] GRASS-GIS connection to mongo

[Markus Neteler]

Hi,

On Fri, Jul 13, 2018 at 11:58 PM, Lorenzo Bottaccioli
 wrote:
>  Hi,
>
> Is it possible to connect Grass-gis with mongodb? If not any chance to have
> it implemented?

While not having any experience, did you check to connect via GDAL/OGR?

See
http://www.gdal.org/drv_mongodb.html

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

[GRASS-dev] [SoC] Week 9 Report - Full support of Python 3 in GRASS GIS

[Sanjeet]

Hi everyone,

This is my week Week 9 report for the project "Full support of Python
3 in GRASS GIS"

1) What did I complete this week?

Fixed 'temporal' library's connection issue (t.connect) [0]
Tested the code with temporal t.connect tests
Fixed code for relative paths
Fixed g.gui.animation part of gui [1]
Wrote two new tests for trunk/scripts (testing pending)

2) What am I going to achieve for the next week?

Fix deprecated code in GUI library
Fix other gui command files
Keep working on temporal library
Test all the reamining files in temporal testsuite

3) Is there any blocking issue?
Not at the moment.

The link to my wiki page is here [2].

[0] 
https://github.com/sanjeetbhatti/FullSupportPython3/blob/master/grass_trunk/lib-python-temporal/patch_temporal.diff
[1] 
https://github.com/sanjeetbhatti/FullSupportPython3/blob/master/grass_trunk/gui/patch_gui.diff
[2] https://trac.osgeo.org/grass/wiki/GSoC/2018/FullSupportPython3#Week9

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

Re: [GRASS-dev] [GRASS GIS] #3606: m.nviz.image produces a screenshot

[GRASS GIS]

#3606: m.nviz.image produces a screenshot
---+-
  Reporter:  epifanio  |  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  major |  Milestone:
 Component:  Display   |Version:  svn-trunk
Resolution:|   Keywords:
   CPU:  x86-64|   Platform:  Linux
---+-

Comment (by epifanio):

 Applied the patch on latest trunk rev. num.: 72990

 print out the following output:


 {{{
 GRASS 7.5.svn (nc_basic_spm_grass7):~ > m.nviz.image
 elevation_map=elevation output=elev perspective=15 --o
 Loading raster map ...
  100%
 Loading raster map ...
  100%
 Translating colors from raster map ...
  100%
 buffer: both
 buffer: both
 buffer: both
 buffer: both
 buffer: both
 buffer: both
 buffer: both
 buffer: swap
 buffer: both
 m.nviz.image complete. File  created.

 }}}

 My grass_trunk is configured without X11 support:


 {{{
 GRASS is now configured for:  x86_64-pc-linux-gnu

   Source directory:   /home/epinux/dev/grass7_trunk
   Build directory:/home/epinux/dev/grass7_trunk
   Installation directory: ${prefix}/grass-7.5.svn
   Startup script in directory:${exec_prefix}/bin
   C compiler: gcc -g -O2
   C++ compiler:   c++ -g -O2
   Building shared libraries:  yes
   OpenGL platform:X11

   MacOSX application: no
   MacOSX architectures:
   MacOSX SDK:

   BLAS support:   yes
   BZIP2 support:  yes
   C++ support:yes
   Cairo support:  yes
   DWG support:no
   FFTW support:   yes
   FreeType support:   yes
   GDAL support:   yes
   GEOS support:   yes
   LAPACK support: yes
   Large File support (LFS):   yes
   libLAS support: yes
   MySQL support:  no
   NetCDF support: yes
   NLS support:no
   ODBC support:   yes
   OGR support:yes
   OpenCL support: no
   OpenGL support: yes
   OpenMP support: yes
   PDAL support:   yes
   PNG support:yes
   POSIX thread support:   yes
   PostgreSQL support: yes
   Readline support:   yes
   Regex support:  yes
   SQLite support: yes
   TIFF support:   yes
   X11 support:no
   Zstandard support:  yes

   using old PROJ 4 API

 }}}

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] GSoC 2018 report week 09 - GRASS GIS module for Sentinel-2 cloud and shadow detection

[Roberta Fagandini]

Hi all!
I'm Roberta Fagandini and I'm working on my GSoC project, a GRASS GIS
module for Sentinel-2 cloud and shadow detection.
This is my report for the ninth week of coding (second evaluation).

1) What did I complete this week?

   - Finished implementing the GUI [0]
   - Made some changes to the code depending on the GUI requirements (add
   controls and check on input, output, etc.) [0]
   - Tested the module and fixed bugs
   - Discussed with mentors about next steps and we decided to not
   implement the cloud and shadow detection procedure in the new module
   i.sentinel.preproc
   - Added to i.sentinel.preproc a flag option to automatically create the
   text file to be used as input in the module i.sentinel.mask [0]
   - Made small changes to i.sentinel.mask in order to make it compatible
   with the output of i.sentinel.preproc [1]

2) What am I going to achieve for next week?

   - Integrate the download and import of Sentinel 2 images into the new
   GRASS module (i.sentinel.preproc)
   - Start writing the manual page
   - Create a real complete GRASS GIS module that can be installed with
   g.extension from my GitHub repository


3) Is there any blocking issue?
No at the moment even though I'm a little late on the roadmap because also
the implementation of the GUI took slightly more time than expected (made
some changes to the code depending on the GUI requirements).

Here the links to my GitHub repository [2] and wiki page [3]

Kind regards,
Roberta

[0] 
*https://github.com/RobiFag/GRASS_clouds_and_shadows/commit/f60952c701e87d21a7010494dec10ec603446a1f
*
[1] 
*https://github.com/RobiFag/GRASS_clouds_and_shadows/commit/e2b6978651efe063d1beed603ae2bd8341b9264e
*
[2] https://github.com/RobiFag/GRASS_clouds_and_shadows
[3] https://trac.osgeo.org/grass/wiki/GSoC/2018/CloudsAndShadowsDetection
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3604: errors running r.category.trim

[GRASS GIS]

#3604: errors running r.category.trim
--+-
  Reporter:  Alister  |  Owner:  pvanbosgeo
  Type:  defect   | Status:  assigned
  Priority:  normal   |  Milestone:
 Component:  Addons   |Version:  7.4.0
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by pvanbosgeo):

 Hi Alister, I can't find the problem; I also tried some of my own raster
 layers without problems. Would it be possible to send a small test raster
 layer so I can try out what goes wrong?

-- 
Ticket URL: 
GRASS GIS 

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