Re: [GRASS-dev] [GRASS GIS] #3980: Error Reading list of LiDAR files in r.in.lidar 7.6.1, 7.8.1 on Windows 10

[GRASS GIS]

#3980: Error Reading list of LiDAR files in r.in.lidar 7.6.1, 7.8.1 on Windows 
10
---+-
  Reporter:  dnewcomb  |  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  normal|  Milestone:  7.8.2
 Component:  Default   |Version:  git-releasebranch78
Resolution:|   Keywords:
   CPU:  x86-64|   Platform:  MSWindows
---+-
Changes (by wenzeslaus):

 * keywords:  Python input file list =>


Comment:

 Replying to [comment:4 dnewcomb]:
 > Checking back,  running from the command line and not the GUI resulted
 in successful completion of the command for 1870 tiles on Windows.  I can
 confirm that the errors above  seem to be related to just the gui.

 Can you perhaps close this one as invalid and, if you can reproduce it,
 create a new one with steps how to reproduce it (and link it here).

 > One side note, instead of seeing a standard percent completion updated
 for the duration of the command, a repeating 100% was printed while the
 command was processing.  I assume that it was reporting 100% as each tile
 was completed?

 Makes sense. You can create a ticket for that.

 Replying to [comment:3 marisn]:
 > Check the version of libLAS as there where bugs in its C API causing
 segfaults:...

 Thanks for the update and the PR too!

-- 
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] #3940: Error Reading settings from Roaming file

[GRASS GIS]

#3940: Error Reading settings from Roaming file
---+
  Reporter:  dnewcomb  |  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  normal|  Milestone:  7.8.2
 Component:  wxGUI |Version:  git-releasebranch78
Resolution:|   Keywords:  Error Reading Settings
   CPU:  x86-64|   Platform:  MSWindows
---+

Comment (by dnewcomb):

 Installed on different computer that had previously had GRASS 7.6.1
 installed and did not see the same message.

 Original computer had previously had an installation of 7.4.1.  Possible
 conflict with remnants of 7.4.1 installation?

-- 
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] #3940: Error Reading settings from Roaming file

[GRASS GIS]

#3940: Error Reading settings from Roaming file
---+
  Reporter:  dnewcomb  |  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  normal|  Milestone:  7.8.2
 Component:  wxGUI |Version:  git-releasebranch78
Resolution:|   Keywords:  Error Reading Settings
   CPU:  x86-64|   Platform:  MSWindows
---+
Changes (by dnewcomb):

 * Attachment "wx" added.

 wx file as requsted

-- 
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] #3980: Error Reading list of LiDAR files in r.in.lidar 7.6.1, 7.8.1 on Windows 10

[GRASS GIS]

#3980: Error Reading list of LiDAR files in r.in.lidar 7.6.1, 7.8.1 on Windows 
10
---+
  Reporter:  dnewcomb  |  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  normal|  Milestone:  7.8.2
 Component:  Default   |Version:  git-releasebranch78
Resolution:|   Keywords:  Python input file list
   CPU:  x86-64|   Platform:  MSWindows
---+

Comment (by dnewcomb):

 Checking back,  running from the command line and not the GUI resulted in
 successful completion of the command for 1870 tiles on Windows.  I can
 confirm that the errors above  seem to be related to just the gui.

 One side note, instead of seeing a standard percent completion updated for
 the duration of the command, a repeating 100% was printed while the
 command was processing.  I assume that it was reporting 100% as each tile
 was completed?

 The raster product appears to have been created successfully.

-- 
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] #2639: grass command should read commands from stdin as an interpreter would do

[GRASS GIS]

#2639: grass command should read commands from stdin as an interpreter would do
-+-
  Reporter:  wenzeslaus  |  Owner:  grass-dev@…
  Type:  | Status:  new
  enhancement|
  Priority:  normal  |  Milestone:  8.0.0
 Component:  Startup |Version:  unspecified
Resolution:  |   Keywords:  interface, CLI, script, batch job,
   CPU:  |  GRASS_BATCH_JOB, init, standard input
  Unspecified|   Platform:  All
-+-

Comment (by neteler):

 Replying to [comment:8 wenzeslaus]:
 > It still could be less verbose:

 A new flag `--quiet` comes to mind...

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Keywords for r.null and in general

[Markus Neteler]

Hi,

On Tue, Nov 26, 2019 at 1:18 PM Veronica Andreo  wrote:
>
> Hi Vaclav
>
> El mar., 26 nov. 2019 a las 0:18, Vaclav Petras () 
> escribió:
>>
>> Hi all,
>>
>> I'm just seeking quick feedback on keywords for r.null module and adding 
>> some general questions for discussion if needed. I just added r.null.all to 
>> addons (do r.null for multiple maps) with keywords:
>>
>> raster
>> map management
>> null data
>> no-data
>>
>> while MarkusN pointed out in the PR that r.null has only
>>
>> raster
>> null data
>>
>> Does the above make sense? The PR for it is easy, but the question here are 
>> more general, so I wonder how people are using the keywords. (As a reminder, 
>> first keywords is module family (raster, vector, ...), second is topic, 
>> third and others are just normal keywords.)
>>
>> 1) Should be we have synonyms in keywords, i.e., both null data and no-data 
>> 2) Should we repeat the words from the name of module, i.e., null or null 
>> data? 3) Should different spellings be included, e.g., no-data and NoData?
>>
>> I'm saying yes first two questions, so that's why I included raster, map 
>> management, null data, no-data.
>
>
> I also tend to say yes to 1) and 2)

yes to 1) and 2)

> Regarding 3), I'm not sure about different spellings, but I'm in for synomyns

IMHO different spellings are confusing, so 3) no also from my point of view

4) synomyns

yes

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

Re: [GRASS-dev] [GRASS GIS] #3944: Manage access to mapsets gui missing checkboxes

[GRASS GIS]

#3944: Manage access to mapsets gui missing checkboxes
---+-
  Reporter:  dnewcomb  |  Owner:  grass-dev@…
  Type:  defect| Status:  closed
  Priority:  normal|  Milestone:  7.8.2
 Component:  Default   |Version:  git-releasebranch78
Resolution:  fixed |   Keywords:  gui mapset access
   CPU:  x86-64|   Platform:  MSWindows
---+-
Changes (by annakrat):

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


Comment:

 Fixed and backported.

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] PyCharm 2019 with Grass 7.8.1

[Stefan Blumentrath]

Hi Zoltan,

did you try https://github.com/zarch/grass-session
That should simplify running GRASS algorithms using GRASS more as a library.

Cheers
Stefan

Fra: grass-dev  på vegne av Zoltan Szecsei 

Sendt: tirsdag 26. november 2019 13:34
Til: grass-dev@lists.osgeo.org 
Emne: [GRASS-dev] PyCharm 2019 with Grass 7.8.1

Hi,
I've just installed QGIS/GRASS etc with Osgeo4w64, but am struggling to
find out how to set up PyCharm to do some grasspy scripting with.
(import grass.scripting as gscript fails - I have set GISBASE, GRASSBIN
and PATH to various C:\OSGeo4W64\apps\grass\grass78 folders)

I need to run r.thin over 2800 tif images, so figured a python loop
should do it.

Any pointers would be welcome.

Thanks and regards,
Zoltan

--

=
Zoltan Szecsei GPrGISc 0031
Geograph (Pty) Ltd.
GIS and Photogrammetric Services

P.O. Box 7, Muizenberg 7950, South Africa.

Mobile: +27-83-6004028 (WhatsApp only)
Qatar:  +974 5083 2722 www.geograph.co.za
=

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

[GRASS-dev] PyCharm 2019 with Grass 7.8.1

[Zoltan Szecsei]

Hi,
I've just installed QGIS/GRASS etc with Osgeo4w64, but am struggling to 
find out how to set up PyCharm to do some grasspy scripting with.
(import grass.scripting as gscript fails - I have set GISBASE, GRASSBIN 
and PATH to various C:\OSGeo4W64\apps\grass\grass78 folders)


I need to run r.thin over 2800 tif images, so figured a python loop 
should do it.


Any pointers would be welcome.

Thanks and regards,
Zoltan

--

=
Zoltan Szecsei GPrGISc 0031
Geograph (Pty) Ltd.
GIS and Photogrammetric Services

P.O. Box 7, Muizenberg 7950, South Africa.

Mobile: +27-83-6004028 (WhatsApp only)
Qatar:  +974 5083 2722 www.geograph.co.za
=

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

Re: [GRASS-dev] Keywords for r.null and in general

[Veronica Andreo]

Hi Vaclav

El mar., 26 nov. 2019 a las 0:18, Vaclav Petras ()
escribió:

> Hi all,
>
> I'm just seeking quick feedback on keywords for r.null module and adding
> some general questions for discussion if needed. I just added r.null.all to
> addons (do r.null for multiple maps) with keywords:
>
> raster
> map management
> null data
> no-data
>
> while MarkusN pointed out in the PR that r.null has only
>
> raster
> null data
>
> Does the above make sense? The PR for it is easy, but the question here
> are more general, so I wonder how people are using the keywords. (As a
> reminder, first keywords is module family (raster, vector, ...), second is
> topic, third and others are just normal keywords.)
>
> 1) Should be we have synonyms in keywords, i.e., both null data and
> no-data 2) Should we repeat the words from the name of module, i.e., null
> or null data? 3) Should different spellings be included, e.g., no-data and
> NoData?
>
> I'm saying yes first two questions, so that's why I included raster, map
> management, null data, no-data.
>

I also tend to say yes to 1) and 2)
Regarding 3), I'm not sure about different spellings, but I'm in for
synomyns

my 0.2 cents
Vero

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