Re: [GRASS-dev] r.in.lidar not running in Mac binaries for 7.1

That’s what I’m using. I’d previously compiled libLAS with gdal 1.10. There are a number of pieces to compiling libLAS in C++, including compiling Boost, and a number of places for things to go wrong. Michael C. Michael Barton Director, Center for Social Dynamics & Complexit

Re: [GRASS-dev] r.in.lidar not running in Mac binaries for 7.1

On Sep 16, 2015 4:40 AM, "Michael Barton" wrote: > > So far I'm stuck on compiling liblas with new gdal and no one has had any advice for a way forward. Maybe stick to GDAL 1.11 for now? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http:

[GRASS-dev] FOSS4G 2016 code sprint

Hi devs, first of all greetings from Seoul, I know that this topic is for the next year, but organization of FOSS4G 2016 is started and already in Como during FOSS4G Europe 2015 I was approached by Astrid Emde (the code sprint head) asking if we would like to have a longer code sprint during the e

Re: [GRASS-dev] r.in.lidar not running in Mac binaries for 7.1

So far I'm stuck on compiling liblas with new gdal and no one has had any advice for a way forward. If that can happen, I can recompile with new liblas. That is why I was hoping for laslib. It may be that I just did not link it correctly. I'm open to advice. Michael Barton School of Human Evolu

[GRASS-dev] r.in.lidar not running in Mac binaries for 7.1

[Was: Re: [GRASS-dev] New Mac binaries uploaded] Hi Michael, On Mon, Aug 24, 2015 at 11:45 PM, Michael Barton wrote: > That would be wonderful. I sort of got that impression too. But will the > GRASS lidar tools be able to use LASlib instead of Liblas? > the binary in Dropbox has lasinfo et al

Re: [GRASS-dev] Display library documentation?

On Tue, Sep 15, 2015 at 6:06 AM, Moritz Lennert < mlenn...@club.worldonline.be> wrote: > On 14/09/15 15:53, Vaclav Petras wrote: > >> Hi, >> >> is there some documentation on how to use the display library, i.e. how >> to write a d.* module? >> > > I imagine you looked at > https://grass.osgeo.org

Re: [GRASS-dev] [GRASS GIS] #2065: grass70 not detecting latest source build of libLAS (1.7.0)

#2065: grass70 not detecting latest source build of libLAS (1.7.0) +- Reporter: rashadkm | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 7.1.0 Component: Compiling |Version:

[GRASS-dev] all categories copied over to new map

Suppose I have a categorical raster map and I want to 'cut out' a subset (with g.region to set a small region and r.mapcalc to create the new map). This map has a smaller number of categories, as is shown using e.g., r.category. However, when plotting the legend, all the categories of the origi

Re: [GRASS-dev] TGRASS: mapset management question

On Tue, Sep 15, 2015 at 3:06 AM, Sören Gebbert wrote: > > However, the warning about mapset access is generated in > "lib/temporal/lib/connect.c" which checks the output of > G_mapset_permissions2. I will remove this check > since only the owner is checked, not access permissions. Be aware of the

Re: [GRASS-dev] [GRASS GIS] #2065: grass70 not detecting latest source build of libLAS (1.7.0)

#2065: grass70 not detecting latest source build of libLAS (1.7.0) +- Reporter: rashadkm | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 7.1.0 Component: Compiling |Version:

Re: [GRASS-dev] [GRASS GIS] #2065: grass70 not detecting latest source build of libLAS (1.7.0)

#2065: grass70 not detecting latest source build of libLAS (1.7.0) +- Reporter: rashadkm | Owner: grass-dev@… Type: defect | Status: closed Priority: normal | Milestone: 7.1.0 Component: Compiling |Version:

[GRASS-dev] i.cluster: report file has wrong linebreaks on Windows

Hi, what is the needed change to change i.cluster to write "new lines" chars in a way that the resulting ASCII file is properly formatted also on Windows? thanks Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/

Re: [GRASS-dev] Display library documentation?

On 14/09/15 15:53, Vaclav Petras wrote: Hi, is there some documentation on how to use the display library, i.e. how to write a d.* module? I imagine you looked at https://grass.osgeo.org/programming7/displaylib.html ? I've tried reading d.vect code but I miss the general rules and concept

[GRASS-dev] [GRASS GIS] #2742: r.fill.dir crash with larger dataset

#2742: r.fill.dir crash with larger dataset -+- Reporter: neteler | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.0.2 Component: Raster |Version: svn-releasebr

Re: [GRASS-dev] [GRASS GIS] #1708: r.fill.dir leaves unresolved areas

#1708: r.fill.dir leaves unresolved areas +- Reporter: marchesinivan | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.0.2 Component: Raster |Version: svn-trun

Re: [GRASS-dev] [GRASS GIS] #2065: grass70 not detecting latest source build of libLAS (1.7.0)

On Sep 15, 2015 1:27 AM, "GRASS GIS" wrote: > > #2065: grass70 not detecting latest source build of libLAS (1.7.0) > +- > Reporter: rashadkm | Owner: grass-dev@… > Type: defect | Status: closed > Priority: normal |

Re: [GRASS-dev] TGRASS: mapset management question

Hi 2015-09-14 23:51 GMT+02:00 Vaclav Petras : > > On Mon, Sep 14, 2015 at 4:53 PM, Markus Neteler wrote: >> >> >> If the point of using that env var is to simply suppress the warning >> in the upper case, then maybe G_suppress_warnings(1) is better? >> Something like >> >> Index: lib/python/tempo