Hi,
sorry for joining this discussion late, I was away all last week,
but will now be available for support via email.
First of all, congrats on being accepted to the GSoC!
Second, I agree that users need to be able to have two distinct modules,
otherwise they will wonder where to find their
#154: google search for grass windows yields only old pages
-+--
Reporter: steko| Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: minor| Milestone:
Markus Neteler ha scritto:
Robert,
I have added a (draft) Makefile to that directory. Please check.
I've make some changes to Makefile, because before the Makefile created
a uncorrect directory.
Now there is only one more problem:
*the clean lines don't remove correctly the binaries*
#155: ps.map: the M highlight problem
--+-
Reporter: perk | Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: minor |
#155: ps.map: the M highlight problem
--+-
Reporter: perk | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: minor| Milestone: 6.4.0
On Sat, May 3, 2008 at 5:33 AM, Hamish [EMAIL PROTECTED] wrote:
Markus Neteler wrote:
It seems that the precision gets somewhere lost in
db_convert_column_value_to_string()
i.e. lib/db/dbmi_base/columnfmt.c
but I don't find where is is rounded.
lib/db/dbmi_base/valuefmt.c
Helena Mitasova wrote:
High Mateus,
we would love to see at least a direct input of LAS data into GRASS
using the libLAS library! Other tools would be welcome too.
Helena,
That's great!
Many general GRASS modules are great for lidar data processing and
analysis and there is also a set of
roberto.marzocchi wrote:
I've write a grass script
(https://svn.osgeo.org/grass/grass-addons/raster/r.inund.fluv/) In my
grass script I use four implemented fortran codes.
Now this script is in Add_ons repository, but there isn't a Makefile.
I've written an install.sh script.
With
High Mateus,
we would love to see at least a direct input of LAS data into GRASS
using the libLAS library!
Other tools would be welcome too.
There is a growing number of GRASS users who work with lidar data (I
have been using lidar data with GRASS for my research for over 7
years now,
Dylan Beaudette wrote:
On Saturday 03 May 2008 03:14:50 pm Mateusz Loskot wrote:
Helena Mitasova wrote:
Thanks for asking and I hope we will see LAS support in GRASS soon (I
have plenty of data to test it),
I'd be happy if I could help.
I am very interested in any
integration of libLAS
On Saturday 03 May 2008 03:14:50 pm Mateusz Loskot wrote:
Helena Mitasova wrote:
High Mateus,
we would love to see at least a direct input of LAS data into GRASS
using the libLAS library! Other tools would be welcome too.
Helena,
That's great!
Many general GRASS modules are great
Yann Chemin wrote:
I could not find it for parameters in float format (G_OPT_F_INPUT?)
lib/gis/parser.c already defines G_OPT_F_* for input and output files,
and field separators for those files. Don't use that for floating point
input values.
for example...
...
input =
2008/5/4 Hamish [EMAIL PROTECTED]:
Yann Chemin wrote:
I could not find it for parameters in float format (G_OPT_F_INPUT?)
lib/gis/parser.c already defines G_OPT_F_* for input and output files,
and field separators for those files. Don't use that for floating point
input values.
OK,
13 matches
Mail list logo
