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 &
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
On 16/09/15 01:53, Vaclav Petras wrote:
On Tue, Sep 15, 2015 at 6:06 AM, Moritz Lennert
> wrote:
On 14/09/15 15:53, Vaclav Petras wrote:
Hi,
is there some documentation on how to use the display library,
#2448: Fontconfig error with cairo on Windows
--+---
Reporter: annakrat | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.2
Component: Display |
On 16-09-15 09:49, Moritz Lennert wrote:
On 15/09/15 20:08, Paulo van Breugel wrote:
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
On 15/09/15 20:08, Paulo van Breugel wrote:
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
#2743: v.net.steiner core dump
-+-
Reporter: clara| Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone:
Component: Default |Version: 7.0.0
Keywords: |CPU: x86-64
Platform:
Looking closer at lastools/laslib and liblas, I think I got it partly right -
the tools are funtionally the same between the two, but the libraries have very
different headers (API). I was interested in getting las into my QGIS package,
which uses the tools, not the library, and I didn't
On Wed, Sep 16, 2015 at 9:41 AM, William Kyngesburye
wrote:
> So the question is if GRASS supports one or the other library or both, or
> does it also use the tools in a script so it doesn't matter.
GRASS uses only the library, not the tools, and is designed/tested/known
On 16 September 2015 at 13:50, Moritz Lennert wrote:
>
> I think that at such an occasion it also would be very interesting to get a
> series of non-programmers together to work on a training manual for GRASS,
> in the same line as the QGIS training manual [1]. I've
10 matches
Mail list logo