Re: [GRASS-user] Trouble importing raster dataset

[Thomas Adams]

Markus,

I'm not sure what I had done wrong previously when I sent my last email,
but the steps:

http://www.cgiar-csi.org/data/global-aridity-and-pet-database

gdal_translate -a_ullr -180 90 180 -60 w001001.adf w001001.adf.fixed
r.in.gdal 
input=/home/thomas.adams/data/PET_he_monthly/pet_he_12/w001001.adf.fixed
output=pet_he_12

worked fine. Thank you!

Best,
Tom

On Wed, Jul 6, 2016 at 3:33 PM, Markus Neteler  wrote:

> Hi,
>
> On Tue, Jul 5, 2016 at 11:36 PM, Thomas Adams  wrote:
> > Here is more info from error from gdalinfo...
> >
> > gdalinfo w001001.adf
> ...
> > Coordinate System is:
> > GEOGCS["WGS 84",
> > DATUM["WGS_1984",
> > SPHEROID["WGS 84",6378137,298.257223563,
> ...
> > AUTHORITY["EPSG","9108"]],
> > AUTHORITY["EPSG","4326"]]
> > Origin = (-180.000,90.07823109627)
> > Pixel Size = (0.00833767951,-0.00833767951)
> > Corner Coordinates:
> > Upper Left  (-180.000,  90.078) (180d 0' 0.00"W, 90d 0' 0.03"N)
>
> ^-- as you can see it exceeds the north pole (> 90.0 degN)
>
> > Lower Left  (-180.000, -60.000) (180d 0' 0.00"W, 60d 0' 0.00"S)
> > Upper Right ( 180.188,  90.078) (180d 0' 0.07"E, 90d 0' 0.03"N)
>
> ... in addition, it exceeds 180W as well. Essentially a broken dataset.
>
> Solutions:
> https://grass.osgeo.org/grass70/manuals/r.in.gdal.html
> * use flag
>   -l Force Lat/Lon maps to fit into geographic coordinates (90N,S; 180E,W)
>
> or see the trick of applying
> gdal_translate -a_ullr ...
>
> which I added here (the WorldClim data suffer from the same issue):
> https://grass.osgeo.org/grass70/manuals/r.in.gdal.html#worldclim.org-data
>
> HTH
> Markus
>
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Help for v.lidar.mcc

[Blumentrath, Stefan]

Hi Rafaela,

100mio Points should not be a problem for GRASS in principle.
 
However, in order to be able to answer more specific we would need more info 
from you, amongst others:
 - output from g.region -up
 - the settings you use in v.lidar.mcc
 - does your point cloud have an attribute table.
 - your system resources (ram and cores)

Generally, I see at least two possible options:

1) You could try v.in.pdal 
(https://trac.osgeo.org/grass/browser/grass/trunk/vector/v.in.pdal/v.in.pdal.html).
 Or

2) assuming that memory is the limiting factor, you could subdivide your area 
of interest into tiles and process each tile (make sure you have enough overlap 
at the edges).

There might be room for some minor performance improvements in v.lidar.mcc 
too...

Cheers
Stefan


-Original Message-
From: grass-user [mailto:grass-user-boun...@lists.osgeo.org] On Behalf Of 
Moritz Lennert
Sent: 26. juli 2016 12:17
To: Rafaela Soares ; grass-user@lists.osgeo.org; 
Newcomb, Doug 
Subject: Re: [GRASS-user] Help for v.lidar.mcc

On 25/07/16 23:55, Rafaela Soares wrote:
> Hi all,
> I have three point clouds generated from UAV images. I need these 
> filter point clouds, and for this I used the v.lidar.mcc command is 
> separate ground and non-ground.
> So, my new point cloud is more dense. Have more of 100 million points 
> and the v.lidar.mcc seems to be working (this processing to more than 
> one week and not changed, and the computer's performance looks the 
> same in the task manager).
> Can anybody help me? Someone already filtered one point cloud so dense?

https://lists.osgeo.org/pipermail/grass-dev/2016-July/081279.html

I can't help you with an answer, though...

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

Re: [GRASS-user] GRASS for Mac 64bit, wxPython 3, maybe fix for SIP problem - please test

[Michael Barton]

This is the SIP bug.

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 Jul 26, 2016, at 6:45 AM, Agustin Diez Castillo  wrote:
> 
> I finally updated one of our machines to 10.11.5 and before disabling SIP I 
> got the same message.
> The only copy of libwx_osx_cocoau-*.dylib that I have in this mac is inside 
> Qgis
> 
> Reproducing Michael’s path and linking his libwx_osx_cocoau-3.0.0.2.0 to the 
> ones in Qgis starts a non-funtcional gui.
> 
> 
> Starting GRASS GIS...
> Traceback (most recent call last):
>  File "/Applications/GRASS-7.3.app/Contents/MacOS/gui/wxpython/gis_set.py", 
> line 31, in 
>from core import globalvar
>  File 
> "/Applications/GRASS-7.3.app/Contents/MacOS/gui/wxpython/core/globalvar.py", 
> line 96, in 
>import wx
>  File "/Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/__init__.py", 
> line 45, in 
>from wx._core import *
>  File "/Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/_core.py", 
> line 4, in 
>import _core_
> ImportError: 
> dlopen(/Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/_core_.so, 
> 2): Library not loaded: 
> /Users/cmbarton/grass_source/wxp3/Users/cmbarton/grass_source/wxp3/lib/libwx_osx_cocoau-3.0.0.2.0.dylib
>  Referenced from: 
> /Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/_core_.so
>  Reason: image not found
> ERROR: Error in GUI startup. See messages above (if any) and if necessary, 
> please report this error to the GRASS developers.
> On systems with package manager, make sure you have the right GUI package, 
> probably named grass-gui, installed.
> To run GRASS GIS in text mode use the -text flag.
> Exiting...
> logout
> Saving session...
> ...copying shared history...
> ...saving history...truncating history files...
> ...completed.
> Deleting expired sessions...none found.
> 
> 
> El 14Jun, 2016, a las 3:13 PM, Adam Dershowitz  
> escribió:
> 
>> I just tried it, and see the same error as before:
>> 
>> $ '/Applications/GRASS-7.3.app/Contents/MacOS/grass.sh'; exit
>> Rebuilding Addon HTML manual pages index...
>> Rebuilding Addon menu...
>> Python 2.7.10 found.
>> Cleaning up temporary files...
>> Starting GRASS GIS...
>> Traceback (most recent call last):
>> File "/Applications/GRASS-7.3.app/Contents/MacOS/gui/wxpython/gis_set.py", 
>> line 31, in 
>>   from core import globalvar
>> File 
>> "/Applications/GRASS-7.3.app/Contents/MacOS/gui/wxpython/core/globalvar.py", 
>> line 96, in 
>>   import wx
>> File "/Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/__init__.py", 
>> line 45, in 
>>   from wx._core import *
>> File "/Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/_core.py", 
>> line 4, in 
>>   import _core_
>> ImportError: 
>> dlopen(/Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/_core_.so, 
>> 2): Library not loaded: 
>> /Users/cmbarton/grass_source/wxp3/Users/cmbarton/grass_source/wxp3/lib/libwx_osx_cocoau-3.0.0.2.0.dylib
>> Referenced from: 
>> /Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/_core_.so
>> Reason: image not found
>> ERROR: Error in GUI startup. See messages above (if any) and if necessary, 
>> please report this error to the GRASS developers.
>> On systems with package manager, make sure you have the right GUI package, 
>> probably named grass-gui, installed.
>> To run GRASS GIS in text mode use the -text flag.
>> Exiting...
>> logout
>> Saving session...
>> ...copying shared history...
>> ...saving history...truncating history files...
>> ...completed.
>> 
>> 
>> [Process completed]
>> 
>> 
>> 
>> 
>> Good luck with the other attempt.  I’m happy to test it out, once you get it 
>> in the right form.
>> 
>> -- Adam
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> On 6/13/16, 6:00 PM, "Michael Barton"  wrote:
>> 
>>> It's been a busier day than I anticipated. But I've got a clean binary of 
>>> GRASS 7.3 64bit, using wxPython 3.0.2.0 on my website now. I doubt that 
>>> this will work any better under SIP, but perhaps...
>>> 
>>> 
>>> 
>>> Please try if you can. I appreciate the tests.
>>> 
>>> 
>>> 
>>> I'm also working on another angle, with the help of a software engineer 
>>> here at ASU. Working from my notes, he seems to have compiled GRASS under 
>>> El Capitan, with SIP enabled and it works fine. He will be working on a 
>>> package that we can make available for testing. I just had a long 
>>> discussion with him and there are some caveats.
>>> 
>>> 
>>> 
>>> 1. GRASS would not compile with some of the 32 bit frameworks that can be 
>>> installed from my site. So he recompiled all 

Re: [GRASS-user] [GRASS-dev] Comment regarding PSC election

[Michael Barton]

This is no disruption or mess. These are important topics to continue 
discussing.

Michael Barton
School of Human Evolution  Change
Center for Social Dynamics & Complexity
Arizona State University

...Sent from my iPad

On Jul 26, 2016, at 12:21 AM, Veronica Andreo 
> wrote:


Hello Nikos, Lu

Thanks for your answers :)

I didn't intend to create any mess neither disrupt nor put in danger the 
ongoing election process, but to merely express my opinion. I'm sorry if I made 
a mess by doing so. It's a pity that the matter didn't reach dev or user lists 
before so I could have said it earlier, though I understand not everything is 
to be discussed publicly.

Yes, Lu, I understand there must be rules, of course... But that doesn't mean 
they are always fair/inclusive or that one has to agree with all of them or 
that they cannot change in the future (I passed 18 long ago :))

I could also ask for add-ons writing access, but even if I was granted that, it 
would feel like fake... since indeed I've never contributed an add-on. I don't 
think it is wise either to inflate developer community with ppl that have not 
contributed an add-on, and that would not even be fair to those that have 
indeed done so. I would just like to have the right to vote as the (bothersome) 
user I am... I mean, maybe I'm the only one, dunno, but if not interested or 
committed to the project why would someone else or anyone in any case want to 
involve him/herself into this? :P

So, in conclusion, not to make it endless, it would be great if upon 
request/approval users could vote either in this occasion or in future 
elections... GRASS is shipped with contributors and contributors-extra files, 
maybe those are good starting points, no? :)

Thanks a lot!

Best,
Vero

El jul. 25, 2016 10:41 PM, "Luca Delucchi" 
> escribió:
On 25 July 2016 at 19:26, Veronica Andreo 
> wrote:
> Hello everyone,
>

Hi Vero,

>
> This is my personal opinion and no more than that, but I just think it is a
> bit unfair that for not having svn writing access I'm not able to vote. I
> don't understand how, as user, I'm entitled to nominate a person for PSC,
> but then, I cannot vote. I mean, there are several people with writing
> access that have remained inactive for a long time (no contributions to svn,
> no answering emails, no commenting on tickets or whatsoever), and IMHO,
> while not a developer, I've been pretty active the past 2-3 years. This is
> the first time I don't see/feel the community spirit that I've always
> praised GRASS for and that was one of the main reasons why I involved myself
> in it and spread the love for the project everywhere I went... and that's
> sad from my point of view.
>

I understand that you would like to votes, and I think you should
vote, but some rules should be present, something like 18 to vote (at
least in Italy)
Maybe you could ask for svn addons access, I think PSC could approve
this, you worked for documentation and you could help also in
translation.

>
> Thanks so much to all of you for making GRASS GIS the great software it is
> :)
>
> Best,
> Vero
>


--
ciao
Luca

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

Re: [GRASS-user] GRASS for Mac 64bit, wxPython 3, maybe fix for SIP problem - please test

[Agustin Diez Castillo]

I finally updated one of our machines to 10.11.5 and before disabling SIP I got 
the same message.
The only copy of libwx_osx_cocoau-*.dylib that I have in this mac is inside Qgis

Reproducing Michael’s path and linking his libwx_osx_cocoau-3.0.0.2.0 to the 
ones in Qgis starts a non-funtcional gui.


Starting GRASS GIS...
Traceback (most recent call last):
  File "/Applications/GRASS-7.3.app/Contents/MacOS/gui/wxpython/gis_set.py", 
line 31, in 
from core import globalvar
  File 
"/Applications/GRASS-7.3.app/Contents/MacOS/gui/wxpython/core/globalvar.py", 
line 96, in 
import wx
  File "/Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/__init__.py", 
line 45, in 
from wx._core import *
  File "/Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/_core.py", 
line 4, in 
import _core_
ImportError: 
dlopen(/Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/_core_.so, 2): 
Library not loaded: 
/Users/cmbarton/grass_source/wxp3/Users/cmbarton/grass_source/wxp3/lib/libwx_osx_cocoau-3.0.0.2.0.dylib
  Referenced from: 
/Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/_core_.so
  Reason: image not found
ERROR: Error in GUI startup. See messages above (if any) and if necessary, 
please report this error to the GRASS developers.
On systems with package manager, make sure you have the right GUI package, 
probably named grass-gui, installed.
To run GRASS GIS in text mode use the -text flag.
Exiting...
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
Deleting expired sessions...none found.


El 14Jun, 2016, a las 3:13 PM, Adam Dershowitz  
escribió:

> I just tried it, and see the same error as before:
> 
> $ '/Applications/GRASS-7.3.app/Contents/MacOS/grass.sh'; exit
> Rebuilding Addon HTML manual pages index...
> Rebuilding Addon menu...
> Python 2.7.10 found.
> Cleaning up temporary files...
> Starting GRASS GIS...
> Traceback (most recent call last):
>  File "/Applications/GRASS-7.3.app/Contents/MacOS/gui/wxpython/gis_set.py", 
> line 31, in 
>from core import globalvar
>  File 
> "/Applications/GRASS-7.3.app/Contents/MacOS/gui/wxpython/core/globalvar.py", 
> line 96, in 
>import wx
>  File "/Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/__init__.py", 
> line 45, in 
>from wx._core import *
>  File "/Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/_core.py", 
> line 4, in 
>import _core_
> ImportError: 
> dlopen(/Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/_core_.so, 
> 2): Library not loaded: 
> /Users/cmbarton/grass_source/wxp3/Users/cmbarton/grass_source/wxp3/lib/libwx_osx_cocoau-3.0.0.2.0.dylib
>  Referenced from: 
> /Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/_core_.so
>  Reason: image not found
> ERROR: Error in GUI startup. See messages above (if any) and if necessary, 
> please report this error to the GRASS developers.
> On systems with package manager, make sure you have the right GUI package, 
> probably named grass-gui, installed.
> To run GRASS GIS in text mode use the -text flag.
> Exiting...
> logout
> Saving session...
> ...copying shared history...
> ...saving history...truncating history files...
> ...completed.
> 
> 
> [Process completed]
> 
> 
> 
> 
> Good luck with the other attempt.  I’m happy to test it out, once you get it 
> in the right form.
> 
> -- Adam
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On 6/13/16, 6:00 PM, "Michael Barton"  wrote:
> 
>> It's been a busier day than I anticipated. But I've got a clean binary of 
>> GRASS 7.3 64bit, using wxPython 3.0.2.0 on my website now. I doubt that this 
>> will work any better under SIP, but perhaps...
>> 
>> 
>> 
>> Please try if you can. I appreciate the tests.
>> 
>> 
>> 
>> I'm also working on another angle, with the help of a software engineer here 
>> at ASU. Working from my notes, he seems to have compiled GRASS under El 
>> Capitan, with SIP enabled and it works fine. He will be working on a package 
>> that we can make available for testing. I just had a long discussion with 
>> him and there are some caveats.
>> 
>> 
>> 
>> 1. GRASS would not compile with some of the 32 bit frameworks that can be 
>> installed from my site. So he recompiled all frameworks dual architecture 
>> 32/64 bit.
>> 
>> 2. Like me, he compiled wxPython from source to a folder outside the 
>> sensitive system folders that SIP is protecting.
>> 
>> 3. He is going to try the new Mac package maker system (pkgbuild) to create 
>> a complete package with all dependencies packaged together for distribution. 
>> They will all install into a new GRASS framework to avoid conflicts with any 
>> other software.
>> 
>> 
>> 
>> He's also setting up a virtual machine for me that I can use to test 
>> compiling GRASS under El Capitan and SIP, using frameworks and other 
>> dependencies as they are now. So we can see how that goes.
>> 
>> 
>> 
>> Wish us luck with this.
>> 

Re: [GRASS-user] Help for v.lidar.mcc

[Moritz Lennert]

On 25/07/16 23:55, Rafaela Soares wrote:

Hi all,
I have three point clouds generated from UAV images. I need these filter
point clouds, and for this I used the v.lidar.mcc command is separate
ground and non-ground.
So, my new point cloud is more dense. Have more of 100 million points
and the v.lidar.mcc seems to be working (this processing to more than
one week and not changed, and the computer's performance looks the same
in the task manager).
Can anybody help me? Someone already filtered one point cloud so dense?


https://lists.osgeo.org/pipermail/grass-dev/2016-July/081279.html

I can't help you with an answer, though...

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

Re: [GRASS-user] [GRASS-dev] Comment regarding PSC election

[Nikos Alexandris]

* Veronica Andreo  [2016-07-26 09:21:52 +0200]:


Hello Nikos, Lu

Thanks for your answers :)

I didn't intend to create any mess neither disrupt nor put in danger the
ongoing election process, but to merely express my opinion. I'm sorry if I
made a mess by doing so. It's a pity that the matter didn't reach dev or
user lists before so I could have said it earlier, though I understand not
everything is to be discussed publicly.


Vero, expressing yourself, the way you did, in the public mailing
list(s), is a paradigm to mimic.

Thank You for doing so.

Nikos

[rest deleted]
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] [GRASS-dev] Comment regarding PSC election

[Moritz Lennert]

On 26/07/16 09:21, Veronica Andreo wrote:

Hello Nikos, Lu

Thanks for your answers :)

I didn't intend to create any mess neither disrupt nor put in danger the
ongoing election process, but to merely express my opinion. I'm sorry if
I made a mess by doing so. It's a pity that the matter didn't reach dev
or user lists before so I could have said it earlier, though I
understand not everything is to be discussed publicly.


No mess at all. Your points are perfectly valid and merit discussion.



Yes, Lu, I understand there must be rules, of course... But that doesn't
mean they are always fair/inclusive or that one has to agree with all of
them or that they cannot change in the future (I passed 18 long ago :))

I could also ask for add-ons writing access, but even if I was granted
that, it would feel like fake... since indeed I've never contributed an
add-on. I don't think it is wise either to inflate developer community
with ppl that have not contributed an add-on, and that would not even be
fair to those that have indeed done so. I would just like to have the
right to vote as the (bothersome) user I am... I mean, maybe I'm the
only one, dunno, but if not interested or committed to the project why
would someone else or anyone in any case want to involve him/herself
into this? :P

So, in conclusion, not to make it endless, it would be great if upon
request/approval users could vote either in this occasion or in future
elections... GRASS is shipped with contributors and contributors-extra
files, maybe those are good starting points, no? :)


This is indeed the direction the PSC is thinking about right now.

The big question is obviously the definition of the community, and of 
its members. We don't have such a definition for GRASS at this stage 
(e.g. equivalent to the charter membership in OSGeo), and so the easiest 
(but as you highlight probably not the best) was to use svn-access as a 
proxy.


Thanks for being "bothersome" ! ;-)

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

Re: [GRASS-user] [GRASS-dev] Comment regarding PSC election

[Veronica Andreo]

Hello Nikos, Lu

Thanks for your answers :)

I didn't intend to create any mess neither disrupt nor put in danger the
ongoing election process, but to merely express my opinion. I'm sorry if I
made a mess by doing so. It's a pity that the matter didn't reach dev or
user lists before so I could have said it earlier, though I understand not
everything is to be discussed publicly.

Yes, Lu, I understand there must be rules, of course... But that doesn't
mean they are always fair/inclusive or that one has to agree with all of
them or that they cannot change in the future (I passed 18 long ago :))

I could also ask for add-ons writing access, but even if I was granted
that, it would feel like fake... since indeed I've never contributed an
add-on. I don't think it is wise either to inflate developer community with
ppl that have not contributed an add-on, and that would not even be fair to
those that have indeed done so. I would just like to have the right to vote
as the (bothersome) user I am... I mean, maybe I'm the only one, dunno, but
if not interested or committed to the project why would someone else or
anyone in any case want to involve him/herself into this? :P

So, in conclusion, not to make it endless, it would be great if upon
request/approval users could vote either in this occasion or in future
elections... GRASS is shipped with contributors and contributors-extra
files, maybe those are good starting points, no? :)

Thanks a lot!

Best,
Vero

El jul. 25, 2016 10:41 PM, "Luca Delucchi"  escribió:

> On 25 July 2016 at 19:26, Veronica Andreo  wrote:
> > Hello everyone,
> >
>
> Hi Vero,
>
> >
> > This is my personal opinion and no more than that, but I just think it
> is a
> > bit unfair that for not having svn writing access I'm not able to vote. I
> > don't understand how, as user, I'm entitled to nominate a person for PSC,
> > but then, I cannot vote. I mean, there are several people with writing
> > access that have remained inactive for a long time (no contributions to
> svn,
> > no answering emails, no commenting on tickets or whatsoever), and IMHO,
> > while not a developer, I've been pretty active the past 2-3 years. This
> is
> > the first time I don't see/feel the community spirit that I've always
> > praised GRASS for and that was one of the main reasons why I involved
> myself
> > in it and spread the love for the project everywhere I went... and that's
> > sad from my point of view.
> >
>
> I understand that you would like to votes, and I think you should
> vote, but some rules should be present, something like 18 to vote (at
> least in Italy)
> Maybe you could ask for svn addons access, I think PSC could approve
> this, you worked for documentation and you could help also in
> translation.
>
> >
> > Thanks so much to all of you for making GRASS GIS the great software it
> is
> > :)
> >
> > Best,
> > Vero
> >
>
>
> --
> ciao
> Luca
>
> www.lucadelu.org
>
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user