Re: [GRASS-dev] addon mismatch

[Paulo van Breugel]

On 10-09-15 16:29, Markus Neteler wrote:

On Thu, Sep 10, 2015 at 4:15 PM, Vaclav Petras  wrote:

On Thu, Sep 10, 2015 at 10:01 AM, Helmut Kudrnovsky  wrote:

e.g. the addon v.in.gbif

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.gbif

it seems the addon is built ok:

...

but the manual can't be find here:

https://grass.osgeo.org/grass70/manuals/addons/

...

I think it is because it is missing in this Makefile:

...

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/Makefile

yes, that's the reason (likewise for others).


I'm not sure if there is a documentation for this. We probably miss, how the
create an addon.

I have started a section here:
https://trac.osgeo.org/grass/wiki/Submitting#GRASSGISAddons


A related / similar issue, I have added an add-on 
https://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.biodiversity 
and added it to the parent Make file. I can't recall having done 
anything else then just uploading an add-on in the past, but it is not 
available through g.extension, nor does it show up in the online manual 
pages. From the links mentioned above, I am not clear what else I should 
do, or whether I did something wrong during upload?





Markus
___
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

Re: [GRASS-dev] [GRASS GIS] #2448: Fontconfig error with cairo on Windows

[GRASS GIS]

#2448: Fontconfig error with cairo on Windows
--+---
  Reporter:  annakrat |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.0.2
 Component:  Display  |Version:  7.0.0
Resolution:   |   Keywords:  font, text, legend, scale bar
   CPU:  Unspecified  |   Platform:  MSWindows 8
--+---

Comment (by hellik):

 Replying to [comment:47 annakrat]:
 > Replying to [comment:44 hellik]:
 > > Replying to [comment:42 annakrat]:
 > > >
 > > > Unfortunately, no change. I wonder if the problem is something
 different then permissions.
 > >
 > > I'm quite sure that it is a file writing permission issue in a usually
 non-writeable folder (c:\Program Files\your program\folder to change
 something) in win 8 and above.
 > >
 > > tested it on several win 7 boxes here, it works fine. unfortunately no
 win 8 oder win 10 box here on my side.
 >
 > If you want to spend even more time on it, you can download/use windows
 10 for free, and run it in virtual box. But it is not just windows 10
 issue from what I've seen.

 see r66166

 Log:
 GRASS-Installer.nsi.tmpl: attempt to fix #2448
 make folder and file writeable before run g.mkfontcap
 change after g.mkfontcap run back to only readable

 it's only in trunk, can you the test one of the next dailys?

--
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] #2739: Allow wildcards in multiple map input and evaluate to map lists accordingly

[GRASS GIS]

#2739: Allow wildcards in multiple map input and evaluate to map lists 
accordingly
-+-
 Reporter:  sbl  |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  normal   |  Milestone:
Component:  Default  |Version:  unspecified
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 For GRASS beginners and people who stick to the GUI the ability to use
 wildcards in multiple map input might be handy.

 People who are not afraid of the command line can of course easily pipe
 g.list output to modules with multiple input or re-use the latter from
 file like e.g. in temporal modules.

 An idea would be to allow something like this:
 {{{
 # Example: calculate average temperature for Norway`s national day
 r.series input=temperature_*_05_17
 output=norway_national_day_temperature_avg method=average
 }}}
 in the GUI or command line, where wildcards are evaluated to a list of
 available maps following that pattern.
 Since the asterisk is not allowed in map names, it might used to trigger a
 respective g.list operation whenever it appears in a multiple map input …


 One suggestion would be to reuse a dialog for selecting multiple maps
 using regular expressions (accessible from layer manager) and have a small
 button near the map entry in the autogenerated dialogs which would open
 this dialog and transfer the resulting map series back in the map entry
 field. So this would be implemented on the GUI level.

 Another suggestion would be to implement this on parser level.
 Both have some pluses and minuses.

 Anyway, a potential risk is that result might be - especially for
 beginners - difficult to anticipate. That may result in unexpected
 behavior, esp when several mapsets are in the search path ...

 See also: https://lists.osgeo.org/pipermail/grass-
 dev/2015-September/076222.html

--
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] #2448: Fontconfig error with cairo on Windows

[GRASS GIS]

#2448: Fontconfig error with cairo on Windows
--+---
  Reporter:  annakrat |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.0.2
 Component:  Display  |Version:  7.0.0
Resolution:   |   Keywords:  font, text, legend, scale bar
   CPU:  Unspecified  |   Platform:  MSWindows 8
--+---

Comment (by hellik):

 Replying to [comment:46 wenzeslaus]:
 > >
 > > - another flag e.g. to write fontcap file to %APPDATA%GRASS7 where
 already the addons are stored
 >
 > How would this work in a multi-user environment?

 there is the ''C:\Users\All Users'' folder.

--
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] #2448: Fontconfig error with cairo on Windows

[Paul Kelly]

On Thu, 10 Sep 2015, GRASS GIS wrote:


see https://grass.osgeo.org/grass70/manuals/g.mkfontcap.html

there is a -s flag:

-s  Write font configuration file to standard output instead of
$GISBASE/etc

a feasable way may be:

- another flag e.g. to write fontcap file to %APPDATA%GRASS7 where already
the addons are stored
- all the modules which are working with fonts seems to search for the
fontcap file in $GISBASE/etc; adding a second search path (e.g.
%APPDATA%GRASS7) to these modules if the file is not available in
$GISBASE/etc


Similar to this, I was just going to suggest why don't you set the 
GRASS_FONT_CAP environment variable to a path that *is* writable. Then 
g.mkfontcap, and all the modules that use the fontcap, will simply use 
that instead of the fontcap in $GISBASE/etc. This mechanism is explicitly 
designed for the situation where a user doesn't have write access to 
$GIBASE/etc and needs to override the system fontcap file.


However, I don't think this is a good solution if the installation is 
required to be available to other users on the same Windows machine as the 
writable path will likely only be available to that user, if I understand 
correctly.


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

Re: [GRASS-dev] [GRASS GIS] #2448: Fontconfig error with cairo on Windows

[GRASS GIS]

#2448: Fontconfig error with cairo on Windows
--+---
  Reporter:  annakrat |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.0.2
 Component:  Display  |Version:  7.0.0
Resolution:   |   Keywords:  font, text, legend, scale bar
   CPU:  Unspecified  |   Platform:  MSWindows 8
--+---

Comment (by hellik):

 Replying to [comment:46 wenzeslaus]:
 > Replying to [comment:45 hellik]:
 > > Replying to [comment:43 wenzeslaus]:
 > > > Replying to [comment:42 annakrat]:
 > > > > Replying to [comment:41 hellik]:
 > > > > > I've done some research, file permissions changed a lot between
 Windows versions (7,8,10).
 > > > >
 > > > > Unfortunately, no change. I wonder if the problem is something
 different then permissions. The problem is I don't get any error during
 installation. Maybe we could print more messages during the font
 configuration? Thanks for all the work on this.
 > > >
 > > > What about that hardcoding of some fonts for MS Windows into a MS
 Windows specific file? This is a great workaround and I have no idea how
 it should be done but it seems that it is appropriate on a platform where
 API is changing often and is under-documented.
 >
 > Shouldn't be there a file with the default GRASS fonts somewhere
 already? Or is everything generated?

 see https://trac.osgeo.org/grass/ticket/2448#comment:33

 yes, the file is there (e.g. ''C:\Program Files\GRASS GIS
 7.1.svn\etc\fontcap''), but the content of the file refers to the OSGeo4W-
 build environment (e.g.
 cyrilc|Cyrillic|0|c:\osgeo4w\usr\src\grass701\dist.i686-pc-
 mingw32\fonts\cyrilc.hmp|0|utf-8|) , and includes not the installation
 path.

 for this situation: the nsis-winGRASS installer normally invokes a g
 .mkfontcap-run, which updates the fontcap file; unfortunately in newer
 windows version the file write permissions in e.g. C:\Program Files\your
 software\somefolder for installer subprocesses has changed.

 IMHO there is some safety issue if write permission to the whole
 ''C:\Program Files\GRASS GIS 7.1.svn\etc\'' folder is granted to all users
 after installation.

 therefore Microsoft has implemented the %APPDATA% to store there changing
 application files.

 so a workaround may be,

 (1) grant write access to the whole folder
 (2) run g.mkfontcap
 (3) change afterwards again back to no write access

 unfortunately you can't run g.mkfontcap successfully afterwards during a
 GRASS session

--
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] #2448: Fontconfig error with cairo on Windows

[GRASS GIS]

#2448: Fontconfig error with cairo on Windows
--+---
  Reporter:  annakrat |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.0.2
 Component:  Display  |Version:  7.0.0
Resolution:   |   Keywords:  font, text, legend, scale bar
   CPU:  Unspecified  |   Platform:  MSWindows 8
--+---

Comment (by annakrat):

 Replying to [comment:44 hellik]:
 > Replying to [comment:42 annakrat]:
 > >
 > > Unfortunately, no change. I wonder if the problem is something
 different then permissions.
 >
 > I'm quite sure that it is a file writing permission issue in a usually
 non-writeable folder (c:\Program Files\your program\folder to change
 something) in win 8 and above.
 >
 > tested it on several win 7 boxes here, it works fine. unfortunately no
 win 8 oder win 10 box here on my side.

 If you want to spend even more time on it, you can download/use windows 10
 for free, and run it in virtual box. But it is not just windows 10 issue
 from what I've seen.

--
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] #2720: r.in.gdal don't start on wingrass 7.0.1

[GRASS GIS]

#2720: r.in.gdal don't start on wingrass 7.0.1
+---
  Reporter:  aperi2007  |  Owner:  grass-dev@…
  Type:  defect | Status:  new
  Priority:  normal |  Milestone:  7.0.2
 Component:  wxGUI  |Version:  7.0.1
Resolution: |   Keywords:  unicode, wingrass
   CPU:  x86-64 |   Platform:  MSWindows 7
+---

Comment (by martinl):

 Replying to [comment:4 annakrat]:
 > I backported r64372 and r64373, that should fix it.

 Please could anyone confirm it? If so, we should probably schedule release
 7.0.2 sooner than expected.

--
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] #2448: Fontconfig error with cairo on Windows

[GRASS GIS]

#2448: Fontconfig error with cairo on Windows
--+---
  Reporter:  annakrat |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.0.2
 Component:  Display  |Version:  7.0.0
Resolution:   |   Keywords:  font, text, legend, scale bar
   CPU:  Unspecified  |   Platform:  MSWindows 8
--+---

Comment (by wenzeslaus):

 Replying to [comment:45 hellik]:
 > Replying to [comment:43 wenzeslaus]:
 > > Replying to [comment:42 annakrat]:
 > > > Replying to [comment:41 hellik]:
 > > > > I've done some research, file permissions changed a lot between
 Windows versions (7,8,10).
 > > >
 > > > Unfortunately, no change. I wonder if the problem is something
 different then permissions. The problem is I don't get any error during
 installation. Maybe we could print more messages during the font
 configuration? Thanks for all the work on this.
 > >
 > > What about that hardcoding of some fonts for MS Windows into a MS
 Windows specific file? This is a great workaround and I have no idea how
 it should be done but it seems that it is appropriate on a platform where
 API is changing often and is under-documented.

 Shouldn't be there a file with the default GRASS fonts somewhere already?
 Or is everything generated?

 > a feasable way may be:
 >
 > - another flag e.g. to write fontcap file to %APPDATA%GRASS7 where
 already the addons are stored

 How would this work in a multi-user environment?

--
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] #2448: Fontconfig error with cairo on Windows

[GRASS GIS]

#2448: Fontconfig error with cairo on Windows
--+---
  Reporter:  annakrat |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.0.2
 Component:  Display  |Version:  7.0.0
Resolution:   |   Keywords:  font, text, legend, scale bar
   CPU:  Unspecified  |   Platform:  MSWindows 8
--+---

Comment (by hellik):

 Replying to [comment:43 wenzeslaus]:
 > Replying to [comment:42 annakrat]:
 > > Replying to [comment:41 hellik]:
 > > > I've done some research, file permissions changed a lot between
 Windows versions (7,8,10).
 > >
 > > Unfortunately, no change. I wonder if the problem is something
 different then permissions. The problem is I don't get any error during
 installation. Maybe we could print more messages during the font
 configuration? Thanks for all the work on this.
 >
 > What about that hardcoding of some fonts for MS Windows into a MS
 Windows specific file? This is a great workaround and I have no idea how
 it should be done but it seems that it is appropriate on a platform where
 API is changing often and is under-documented.

 see https://grass.osgeo.org/grass70/manuals/g.mkfontcap.html

 there is a -s flag:

 -s  Write font configuration file to standard output instead of
 $GISBASE/etc

 a feasable way may be:

 - another flag e.g. to write fontcap file to %APPDATA%GRASS7 where already
 the addons are stored
 - all the modules which are working with fonts seems to search for the
 fontcap file in $GISBASE/etc; adding a second search path (e.g.
 %APPDATA%GRASS7) to these modules if the file is not available in
 $GISBASE/etc

--
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] #2448: Fontconfig error with cairo on Windows

[GRASS GIS]

#2448: Fontconfig error with cairo on Windows
--+---
  Reporter:  annakrat |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.0.2
 Component:  Display  |Version:  7.0.0
Resolution:   |   Keywords:  font, text, legend, scale bar
   CPU:  Unspecified  |   Platform:  MSWindows 8
--+---

Comment (by hellik):

 Replying to [comment:42 annakrat]:
 >
 > Unfortunately, no change. I wonder if the problem is something different
 then permissions.

 I'm quite sure that it is a file writing permission issue in a usually
 non-writeable folder (c:\Program Files\your program\folder to change
 something) in win 8 and above.

 tested it on several win 7 boxes here, it works fine. unfortunately no win
 8 oder win 10 box here on my side.

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Wildcards in multiple map input?

[Moritz Lennert]

On 10/09/15 16:07, Blumentrath, Stefan wrote:

Hi Anna,

Thanks for your reply. The closest I found was this:

https://trac.osgeo.org/grass/ticket/1251

Might be dangerous to use an asterisk at command / parser level as the
result of the evaluation (meaning the resulting list of maps) is not
necessarily known to the user in advance (or may be different from what
he or she expects)!?


Especially when maps from other mapsets might be read as well. I agree 
that this is a potentially dangerous feature and believe that a solution 
on GUI level, with possibility of intermediate control by the user of 
the list of selected maps, might be safer.


Moritz

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

Re: [GRASS-dev] [GRASS GIS] #2738: sigfile problem with i.gensigset

[GRASS GIS]

#2738: sigfile problem with i.gensigset
---+-
  Reporter:  carminem  |  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  major |  Milestone:
 Component:  Imagery   |Version:  7.0.1
Resolution:|   Keywords:
   CPU:  x86-64|   Platform:  Linux
---+-

Comment (by annakrat):

 Could be 2 different problems. Could you switch on debug mode?

--
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] #2738: sigfile problem with i.gensigset

[GRASS GIS]

#2738: sigfile problem with i.gensigset
---+-
  Reporter:  carminem  |  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  major |  Milestone:
 Component:  Imagery   |Version:  7.0.1
Resolution:|   Keywords:
   CPU:  x86-64|   Platform:  Linux
---+-
Changes (by carminem):

 * Attachment "x63907_g_EL_sub_sig" 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] #2738: sigfile problem with i.gensigset

[GRASS GIS]

#2738: sigfile problem with i.gensigset
--+-
 Reporter:  carminem  |  Owner:  grass-dev@…
 Type:  defect| Status:  new
 Priority:  major |  Milestone:
Component:  Imagery   |Version:  7.0.1
 Keywords:|CPU:  x86-64
 Platform:  Linux |
--+-
 When I launch i.gensigset I receive this error as popup:
 'ascii' codec can't decode byte 0xc3 in position 10: ordinal not in
 range(128)
 Then I compile all the field required from the form but grass is not able
 to produce the sigfile, the only two line written are reported:

 title: Rasterized vector map from labels[[BR]]
 nbands: 47

 I use grass 7.0.1 in ubuntu 14.04.

--
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] #2737: importing vector and raster problem

[GRASS GIS]

#2737: importing vector and raster problem
+-
  Reporter:  carminem   |  Owner:  grass-dev@…
  Type:  defect | Status:  closed
  Priority:  critical   |  Milestone:
 Component:  Default|Version:  7.0.1
Resolution:  duplicate  |   Keywords:
   CPU:  x86-64 |   Platform:  Linux
+-
Changes (by annakrat):

 * status:  new => closed
 * resolution:   => duplicate
 * component:  wxGUI => Default
 * milestone:  7.0.2 =>


Comment:

 Duplicate of #2720.

--
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] #2737: importing vector and raster problem

[GRASS GIS]

#2737: importing vector and raster problem
---+-
  Reporter:  carminem  |  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  critical  |  Milestone:  7.0.2
 Component:  wxGUI |Version:  7.0.1
Resolution:|   Keywords:
   CPU:  x86-64|   Platform:  Linux
---+-
Changes (by martinl):

 * milestone:  7.0.1 => 7.0.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] #2737: importing vector and raster problem

[GRASS GIS]

#2737: importing vector and raster problem
---+-
  Reporter:  carminem  |  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  critical  |  Milestone:  7.0.1
 Component:  wxGUI |Version:  7.0.1
Resolution:|   Keywords:
   CPU:  x86-64|   Platform:  Linux
---+-
Changes (by martinl):

 * component:  Default => wxGUI
 * milestone:   => 7.0.1


Old description:

> When I launch v.in.ogr and r.in.gdal I receive this error:
>
> D1/5: grass.script.core.start_command(): g.gisenv -n
> D1/5: G_set_program_name(): g.gisenv
> D2/5: G_option_to_separator(): key = separator -> sep = '
> '
> Traceback (most recent call last):
>   File "/usr/lib/grass70/gui/wxpython/lmgr/frame.py", line 310, in
> 
> lambda event: self.RunSpecialCmd(event.cmd))
>   File "/usr/lib/grass70/gui/wxpython/lmgr/frame.py", line 617, in
> RunSpecialCmd
> self.OnImportGdalLayers(event = None, cmd = command)
>   File "/usr/lib/grass70/gui/wxpython/lmgr/frame.py", line 1679, in
> OnImportGdalLayers
> dlg = GdalImportDialog(parent = self, giface = self._giface)
>   File "/usr/lib/grass70/gui/wxpython/gui_core/dialogs.py", line 1878, in
> __init__
> " ({mightNotWork})".format(mightNotWork=mightNotWork)))
> UnicodeEncodeError: 'ascii' codec can't encode character u'\xf9' in
> position 37: ordinal not in range(128)
>
> I use grass 7.0.1 in ubuntu 14.04.

New description:

 When I launch v.in.ogr and r.in.gdal I receive this error:

 {{{
 D1/5: grass.script.core.start_command(): g.gisenv -n
 D1/5: G_set_program_name(): g.gisenv
 D2/5: G_option_to_separator(): key = separator -> sep = '
 '
 Traceback (most recent call last):
   File "/usr/lib/grass70/gui/wxpython/lmgr/frame.py", line 310, in
 
 lambda event: self.RunSpecialCmd(event.cmd))
   File "/usr/lib/grass70/gui/wxpython/lmgr/frame.py", line 617, in
 RunSpecialCmd
 self.OnImportGdalLayers(event = None, cmd = command)
   File "/usr/lib/grass70/gui/wxpython/lmgr/frame.py", line 1679, in
 OnImportGdalLayers
 dlg = GdalImportDialog(parent = self, giface = self._giface)
   File "/usr/lib/grass70/gui/wxpython/gui_core/dialogs.py", line 1878, in
 __init__
 " ({mightNotWork})".format(mightNotWork=mightNotWork)))
 UnicodeEncodeError: 'ascii' codec can't encode character u'\xf9' in
 position 37: ordinal not in range(128)
 }}}

 I use grass 7.0.1 in ubuntu 14.04.

--

--
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] #2737: importing vector and raster problem

[GRASS GIS]

#2737: importing vector and raster problem
--+-
 Reporter:  carminem  |  Owner:  grass-dev@…
 Type:  defect| Status:  new
 Priority:  critical  |  Milestone:
Component:  Default   |Version:  7.0.1
 Keywords:|CPU:  x86-64
 Platform:  Linux |
--+-
 When I launch v.in.ogr and r.in.gdal I receive this error:

 D1/5: grass.script.core.start_command(): g.gisenv -n
 D1/5: G_set_program_name(): g.gisenv
 D2/5: G_option_to_separator(): key = separator -> sep = '
 '
 Traceback (most recent call last):
   File "/usr/lib/grass70/gui/wxpython/lmgr/frame.py", line 310, in
 
 lambda event: self.RunSpecialCmd(event.cmd))
   File "/usr/lib/grass70/gui/wxpython/lmgr/frame.py", line 617, in
 RunSpecialCmd
 self.OnImportGdalLayers(event = None, cmd = command)
   File "/usr/lib/grass70/gui/wxpython/lmgr/frame.py", line 1679, in
 OnImportGdalLayers
 dlg = GdalImportDialog(parent = self, giface = self._giface)
   File "/usr/lib/grass70/gui/wxpython/gui_core/dialogs.py", line 1878, in
 __init__
 " ({mightNotWork})".format(mightNotWork=mightNotWork)))
 UnicodeEncodeError: 'ascii' codec can't encode character u'\xf9' in
 position 37: ordinal not in range(128)

 I use grass 7.0.1 in ubuntu 14.04.

--
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] #2448: Fontconfig error with cairo on Windows

[GRASS GIS]

#2448: Fontconfig error with cairo on Windows
--+---
  Reporter:  annakrat |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.0.2
 Component:  Display  |Version:  7.0.0
Resolution:   |   Keywords:  font, text, legend, scale bar
   CPU:  Unspecified  |   Platform:  MSWindows 8
--+---

Comment (by wenzeslaus):

 Replying to [comment:42 annakrat]:
 > Replying to [comment:41 hellik]:
 > > I've done some research, file permissions changed a lot between
 Windows versions (7,8,10).
 >
 > Unfortunately, no change. I wonder if the problem is something different
 then permissions. The problem is I don't get any error during
 installation. Maybe we could print more messages during the font
 configuration? Thanks for all the work on this.

 What about that hardcoding of some fonts for MS Windows into a MS Windows
 specific file? This is a great workaround and I have no idea how it should
 be done but it seems that it is appropriate on a platform where API is
 changing often and is under-documented.

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] addon mismatch

[Helmut Kudrnovsky]

Markus Neteler wrote
> On Thu, Sep 10, 2015 at 4:38 PM, Helmut Kudrnovsky <

> hellik@

> > wrote:
>> but in
>>
>> https://grass.osgeo.org/addons/grass7/logs/summary.html
>>
>> there is
>>
>> vector/v.in.gns SUCCESS log
> 
> Yes, this is built on Martin L's Windows server AFAIK.
> 
>> but v.in.gns isn't activated in
>>
>> https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/Makefile#L25
>>
>> any idea?
> 
> Guess he just loops over *all* modules on his Windows machine while
> the manual magic runs on the Linux server which respects the
> Makefiles.
> 
> HTH,
> Markus
> ___
> grass-dev mailing list

> grass-dev@.osgeo

> http://lists.osgeo.org/mailman/listinfo/grass-dev

see https://grass.osgeo.org/grass70/manuals/addons/

 v.in.gns is there , although not in the make file



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/addon-mismatch-tp5223525p5223548.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] r.resample.rst behavior does not match manual

[Markus Neteler]

On Sun, Aug 30, 2015 at 9:54 AM, Blumentrath, Stefan
 wrote:
> Hi Michael,
>
>
>
> The second sentence you cite from the manual seems indeed a bit imprecise.
>
> It should probably say something like:
>
> “The extent of all resulting raster maps is taken from the settings of the
> current region (which may be different from the extent of the input raster
> map). The resolution of the current region however has to follow cleanly the
> resolution of the input map”

I have added a modified version of above suggestion to the manual in
https://trac.osgeo.org/grass/changeset/66163

Further improvements are always welcome.

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

Re: [GRASS-dev] addon mismatch

[Markus Neteler]

On Thu, Sep 10, 2015 at 4:38 PM, Helmut Kudrnovsky  wrote:
> but in
>
> https://grass.osgeo.org/addons/grass7/logs/summary.html
>
> there is
>
> vector/v.in.gns SUCCESS log

Yes, this is built on Martin L's Windows server AFAIK.

> but v.in.gns isn't activated in
>
> https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/Makefile#L25
>
> any idea?

Guess he just loops over *all* modules on his Windows machine while
the manual magic runs on the Linux server which respects the
Makefiles.

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

Re: [GRASS-dev] addon mismatch

[Helmut Kudrnovsky]

Markus Neteler wrote
> On Thu, Sep 10, 2015 at 4:15 PM, Vaclav Petras <

> wenzeslaus@

> > wrote:
>> On Thu, Sep 10, 2015 at 10:01 AM, Helmut Kudrnovsky <

> hellik@

> > wrote:
>>> e.g. the addon v.in.gbif
>>>
>>> https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.gbif
>>>
>>> it seems the addon is built ok:
> ...
>>> but the manual can't be find here:
>>>
>>> https://grass.osgeo.org/grass70/manuals/addons/
> ...
>> I think it is because it is missing in this Makefile:
> ...
>> https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/Makefile
> 
> yes, that's the reason (likewise for others).
> 
>> I'm not sure if there is a documentation for this. We probably miss, how
>> the
>> create an addon.
> 
> I have started a section here:
> https://trac.osgeo.org/grass/wiki/Submitting#GRASSGISAddons
> 
> Markus
> ___
> grass-dev mailing list

> grass-dev@.osgeo

> http://lists.osgeo.org/mailman/listinfo/grass-dev


but in 

https://grass.osgeo.org/addons/grass7/logs/summary.html

there is 

vector/v.in.gns SUCCESS log

but v.in.gns isn't activated in 

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/Makefile#L25

any idea?



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/addon-mismatch-tp5223525p5223541.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #2448: Fontconfig error with cairo on Windows

[GRASS GIS]

#2448: Fontconfig error with cairo on Windows
--+---
  Reporter:  annakrat |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.0.2
 Component:  Display  |Version:  7.0.0
Resolution:   |   Keywords:  font, text, legend, scale bar
   CPU:  Unspecified  |   Platform:  MSWindows 8
--+---

Comment (by annakrat):

 Replying to [comment:41 hellik]:
 >
 > I've changed
 > [GRASS-SVN] r66148 - grass/trunk/mswindows
 > [GRASS-SVN] r66149 - grass/branches/releasebranch_7_0/mswindows
 >
 > Can you test the next Installer?
 >
 > I've done some research, file permissions changed a lot between Windows
 versions (7,8,10).

 Unfortunately, no change. I wonder if the problem is something different
 then permissions. The problem is I don't get any error during
 installation. Maybe we could print more messages during the font
 configuration? Thanks for all the work on 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] addon mismatch

[Helmut Kudrnovsky]

Markus Neteler wrote
> On Thu, Sep 10, 2015 at 4:15 PM, Vaclav Petras <

> wenzeslaus@

> > wrote:
>> On Thu, Sep 10, 2015 at 10:01 AM, Helmut Kudrnovsky <

> hellik@

> > wrote:
>>> e.g. the addon v.in.gbif
>>>
>>> https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.gbif
>>>
>>> it seems the addon is built ok:
> ...
>>> but the manual can't be find here:
>>>
>>> https://grass.osgeo.org/grass70/manuals/addons/
> ...
>> I think it is because it is missing in this Makefile:
> ...
>> https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/Makefile
> 
> yes, that's the reason (likewise for others).

oh, yes I remember darkly ;-), I'll add it.

thanks



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/addon-mismatch-tp5223525p5223536.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] addon mismatch

[Markus Neteler]

On Thu, Sep 10, 2015 at 4:15 PM, Vaclav Petras  wrote:
> On Thu, Sep 10, 2015 at 10:01 AM, Helmut Kudrnovsky  wrote:
>> e.g. the addon v.in.gbif
>>
>> https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.gbif
>>
>> it seems the addon is built ok:
...
>> but the manual can't be find here:
>>
>> https://grass.osgeo.org/grass70/manuals/addons/
...
> I think it is because it is missing in this Makefile:
...
> https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/Makefile

yes, that's the reason (likewise for others).

> I'm not sure if there is a documentation for this. We probably miss, how the
> create an addon.

I have started a section here:
https://trac.osgeo.org/grass/wiki/Submitting#GRASSGISAddons

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

Re: [GRASS-dev] Wildcards in multiple map input?

[Blumentrath, Stefan]

Hi Anna,

Thanks for your reply. The closest I found was this:
https://trac.osgeo.org/grass/ticket/1251

Might be dangerous to use an asterisk at command / parser level as the result 
of the evaluation (meaning the resulting list of maps) is not necessarily known 
to the user in advance (or may be different from what he or she expects)!?

Anyway, if you consider it a useful feature I will open a ticket …

Cheers
Stefan


From: Anna Petrášová [mailto:kratocha...@gmail.com]
Sent: 10. september 2015 15:44
To: Blumentrath, Stefan 
Cc: GRASS developers list (grass-dev@lists.osgeo.org) 
; Andrew McAninch ; Radim 
Blazek (radim.bla...@gmail.com) 
Subject: Re: [GRASS-dev] Wildcards in multiple map input?



On Wed, Sep 9, 2015 at 7:06 AM, Blumentrath, Stefan 
mailto:stefan.blumentr...@nina.no>> wrote:
Hi,

For the QGIS-GRASS-plugin update Radim, Pedro, Andrew and me were discussion 
how to implement multiple selections for map input in the UI in QGIS.

In this context I was thinking that the ability to use wildcards would be 
really handy for GRASS newcomers. People who are not afraid of the command line 
can of course easily pipe g.list output to modules with multiple input or 
re-use the latter from file like e.g. in temporal modules.

My idea would be to allow something like this:
r.series input=temperature_*_05_17 output=norway_national_day_temperature_avg 
method=average (in order to calculate average temperature for Norways national 
day for example)
in the GUI and/or command line, where wildcards are evaluated to a list of 
available maps following that pattern.
The “*” is not allowed in map names, right, so, whenever it appears in a 
multiple map input it might used to trigger a respective g.list operation…

My question is:
Would it be of interest and feasible to add such a feature to GRASS?
Just an idea to make things easier for beginners and those who only use the 
GUI...

I thought there was a ticket about this, but I can't find it. The suggestion I 
remember (but it never got implemented) is to reuse a dialog for selecting 
multiple maps using regular expressions (accessible from layer manager) and 
have a small button near the map entry in the autogenerated dialogs which would 
open this dialog and transfer the resulting map series back in the map entry 
field. So this would be implemented on the GUI level. Your suggestion would be 
implemented on parser level. I guess both have some pluses and minuses.

Anna



Cheers
Stefan


___
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

Re: [GRASS-dev] Wildcards in multiple map input?

[Anna Petrášová]

On Thu, Sep 10, 2015 at 10:07 AM, Blumentrath, Stefan <
stefan.blumentr...@nina.no> wrote:

> Hi Anna,
>
>
>
> Thanks for your reply. The closest I found was this:
>
> https://trac.osgeo.org/grass/ticket/1251
>

that's a different one... Maybe I don't remember it correctly

>
>
> Might be dangerous to use an asterisk at command / parser level as the
> result of the evaluation (meaning the resulting list of maps) is not
> necessarily known to the user in advance (or may be different from what he
> or she expects)!?
>
>
>
> Anyway, if you consider it a useful feature I will open a ticket …
>

yes, thanks

>
>
> Cheers
>
> Stefan
>
>
>
>
>
> *From:* Anna Petrášová [mailto:kratocha...@gmail.com]
> *Sent:* 10. september 2015 15:44
> *To:* Blumentrath, Stefan 
> *Cc:* GRASS developers list (grass-dev@lists.osgeo.org) <
> grass-dev@lists.osgeo.org>; Andrew McAninch ; Radim
> Blazek (radim.bla...@gmail.com) 
> *Subject:* Re: [GRASS-dev] Wildcards in multiple map input?
>
>
>
>
>
>
>
> On Wed, Sep 9, 2015 at 7:06 AM, Blumentrath, Stefan <
> stefan.blumentr...@nina.no> wrote:
>
> Hi,
>
>
>
> For the QGIS-GRASS-plugin update Radim, Pedro, Andrew and me were
> discussion how to implement multiple selections for map input in the UI in
> QGIS.
>
>
>
> In this context I was thinking that the ability to use wildcards would be
> really handy for GRASS newcomers. People who are not afraid of the command
> line can of course easily pipe g.list output to modules with multiple input
> or re-use the latter from file like e.g. in temporal modules.
>
>
>
> My idea would be to allow something like this:
>
> r.series input=temperature_*_05_17
> output=norway_national_day_temperature_avg method=average (in order to
> calculate average temperature for Norways national day for example)
>
> in the GUI and/or command line, where wildcards are evaluated to a list of
> available maps following that pattern.
>
> The “*” is not allowed in map names, right, so, whenever it appears in a
> multiple map input it might used to trigger a respective g.list operation…
>
>
>
> My question is:
>
> Would it be of interest and feasible to add such a feature to GRASS?
>
> Just an idea to make things easier for beginners and those who only use
> the GUI...
>
>
>
> I thought there was a ticket about this, but I can't find it. The
> suggestion I remember (but it never got implemented) is to reuse a dialog
> for selecting multiple maps using regular expressions (accessible from
> layer manager) and have a small button near the map entry in the
> autogenerated dialogs which would open this dialog and transfer the
> resulting map series back in the map entry field. So this would be
> implemented on the GUI level. Your suggestion would be implemented on
> parser level. I guess both have some pluses and minuses.
>
>
>
> Anna
>
>
>
>
>
>
>
> Cheers
>
> Stefan
>
>
>
>
> ___
> 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

Re: [GRASS-dev] addon mismatch

[Vaclav Petras]

On Thu, Sep 10, 2015 at 10:15 AM, Vaclav Petras 
wrote:
>
>
>
> On Thu, Sep 10, 2015 at 10:01 AM, Helmut Kudrnovsky  wrote:
> >
> > hi,
> >
> > in https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector
there is
> >
> > e.g. the addon v.in.gbif
> >
> >
https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.gbif
> >
> > it seems the addon is built ok:
> >
> > http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/
> > http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/logs/
> >
http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/logs/v.in.gbif.log
> >
> > but the manual can't be find here:
> >
> > https://grass.osgeo.org/grass70/manuals/addons/
> >
> > and the pre-built addon can't be found by g.extension in a
winGRASS7.0.svn
> > session.
> >
> > any idea?
>
> I don't have a clear idea how the system works but this addon is not even
mentioned in
>
> https://grass.osgeo.org/addons/grass7/logs/summary.html
>
> I think it is because it is missing in this Makefile:
>
> https://trac.osgeo.org/grass/browser/grass-addons/grass7/Makefile

I'm sorry, I meant this Makefile:

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/Makefile

> I'm not sure if there is a documentation for this. We probably miss, how
the create an addon.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] addon mismatch

[Vaclav Petras]

On Thu, Sep 10, 2015 at 10:01 AM, Helmut Kudrnovsky  wrote:
>
> hi,
>
> in https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector there
is
>
> e.g. the addon v.in.gbif
>
> https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.gbif
>
> it seems the addon is built ok:
>
> http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/
> http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/logs/
>
http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/logs/v.in.gbif.log
>
> but the manual can't be find here:
>
> https://grass.osgeo.org/grass70/manuals/addons/
>
> and the pre-built addon can't be found by g.extension in a winGRASS7.0.svn
> session.
>
> any idea?

I don't have a clear idea how the system works but this addon is not even
mentioned in

https://grass.osgeo.org/addons/grass7/logs/summary.html

I think it is because it is missing in this Makefile:

https://trac.osgeo.org/grass/browser/grass-addons/grass7/Makefile

I'm not sure if there is a documentation for this. We probably miss, how
the create an addon.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] r.resample.rst behavior does not match manual

[Vaclav Petras]

On Sun, Sep 6, 2015 at 1:01 PM, Michael Barton 
wrote:

> Thanks for all the responses and fixes. I should have some time in the
> next week to look at these.
>

Please see also my comments in "r.in.lidar: height aboveground" where I say:

r.resamp.rst should honor the resolution of the data since we are
resampling from that resolution or at least it should have a flag for it.
Similarly to r.in.lidar, we often want to resample to match some existing
raster which we can only do using region.

Does somebody think my idea is worth creating a patch? Did somebody looked
to the source code already?

Best,
Vaclav

https://lists.osgeo.org/pipermail/grass-dev/2015-September/076188.html


>
> 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 Sep 6, 2015, at 6:26 AM, Markus Neteler  wrote:
> >
> > On Mon, Aug 31, 2015 at 1:55 AM, Michael Barton 
> wrote:
> >> Thanks for the clarification Stefan.
> >>
> >> It sounds like, unlike other resampling commands (unless they, too, are
> in
> >> error), r.resample.rst needs to be run at the resolution of the original
> >> map, not the output map.
> >
> > Yes. It has been implemented like that (not sure if there is any
> > technical reason), yet going a bit against the "normal" workflow.
> >
> >> The output resolution will be determined by the
> >> command, not by the region settings. This should go into the manual too,
> >> along with the revised text you suggested.
> >
> > Stefan, Michael, please send a text snipped to me for the manual.
> >
> >> In a somewhat related question, do you have any idea how
> r.resample.filter
> >> works? The manual is not very informative
> >
> > True - thanks to my long term inbox I found material here
> > https://trac.osgeo.org/grass/ticket/1401#comment:8
> >
> > and merged it into the manual page:
> > https://grass.osgeo.org/grass70/manuals/r.resamp.filter.html
> > https://grass.osgeo.org/grass71/manuals/r.resamp.filter.html
> >
> > (please revise as needed).
> >
> >> and I couldn’t get any useful
> >> downscaling results (lower to higher resolution) with my spot tests.
> >
> > Adding some examples there would be important.
> >
> >> r.resample.interp doesn’t seem to give expected results either. I’ll do
> a
> >> test with demo data when I have a few minutes this week. I did get very
> good
> >> downscaling results with r.resample.bspline, but it took a very long
> time.
> >
> > Perhaps time to expand
> >
> https://grasswiki.osgeo.org/wiki/Interpolation#Resampling_of_raster_maps_to_finer_resolution
> > ?
> >
> > Markus
>
> ___
> 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] addon mismatch

[Helmut Kudrnovsky]

hi,

in https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector there is 

e.g. the addon v.in.gbif

https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.gbif

it seems the addon is built ok:

http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/
http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/logs/
http://wingrass.fsv.cvut.cz/grass70/addons/grass-7.0.1svn/logs/v.in.gbif.log

but the manual can't be find here:

https://grass.osgeo.org/grass70/manuals/addons/

and the pre-built addon can't be found by g.extension in a winGRASS7.0.svn
session.

any idea?



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/addon-mismatch-tp5223525.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Wildcards in multiple map input?

[Anna Petrášová]

On Wed, Sep 9, 2015 at 7:06 AM, Blumentrath, Stefan <
stefan.blumentr...@nina.no> wrote:

> Hi,
>
>
>
> For the QGIS-GRASS-plugin update Radim, Pedro, Andrew and me were
> discussion how to implement multiple selections for map input in the UI in
> QGIS.
>
>
>
> In this context I was thinking that the ability to use wildcards would be
> really handy for GRASS newcomers. People who are not afraid of the command
> line can of course easily pipe g.list output to modules with multiple input
> or re-use the latter from file like e.g. in temporal modules.
>
>
>
> My idea would be to allow something like this:
>
> r.series input=temperature_*_05_17
> output=norway_national_day_temperature_avg method=average (in order to
> calculate average temperature for Norways national day for example)
>
> in the GUI and/or command line, where wildcards are evaluated to a list of
> available maps following that pattern.
>
> The “*” is not allowed in map names, right, so, whenever it appears in a
> multiple map input it might used to trigger a respective g.list operation…
>
>
>
> My question is:
>
> Would it be of interest and feasible to add such a feature to GRASS?
>
> Just an idea to make things easier for beginners and those who only use
> the GUI...
>

I thought there was a ticket about this, but I can't find it. The
suggestion I remember (but it never got implemented) is to reuse a dialog
for selecting multiple maps using regular expressions (accessible from
layer manager) and have a small button near the map entry in the
autogenerated dialogs which would open this dialog and transfer the
resulting map series back in the map entry field. So this would be
implemented on the GUI level. Your suggestion would be implemented on
parser level. I guess both have some pluses and minuses.

Anna



>
> Cheers
>
> Stefan
>
>
>
> ___
> 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

Re: [GRASS-dev] sugestions for an interactive 2 points loop gathering

[Helmut Kudrnovsky]

Yann Chemin-3 wrote
> Hi,
> 
> I would like to build an interactive module that would just gather two
> points (a center and a peripheric distance) in a loop fashion and add that
> to a text file in X1,Y1,X2,Y2.
> 
> I am not familiar with the GUI programming as it is to date, but happy to
> learn the needed.
> 
> Cheers,
> Yann
> 
> ___
> grass-dev mailing list

> grass-dev@.osgeo

> http://lists.osgeo.org/mailman/listinfo/grass-dev

maybe a starting point for an interactive set of coordinates 
#%option G_OPT_M_COORDS

see an example e.g. addon r.basin 



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/sugestions-for-an-interactive-2-points-loop-gathering-tp5223469p5223479.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] sugestions for an interactive 2 points loop gathering

[Yann Chemin]

Hi,

I would like to build an interactive module that would just gather two
points (a center and a peripheric distance) in a loop fashion and add that
to a text file in X1,Y1,X2,Y2.

I am not familiar with the GUI programming as it is to date, but happy to
learn the needed.

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

[GRASS-dev] Images in manual pages

[Markus Neteler]

Hi devs,

concerning new images in manual pages, please be sure to follow our style guide
https://trac.osgeo.org/grass/wiki/Submitting/Docs#Images

- Image size: 600 pixel width (height depends on that)
- compress PNG images with:
   optipng -o5 file.png

I saw some tiny images submitted, they are rather useless then because
of too low quality.
(well, some were also too large).

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