[GRASS5] running grass on macosx

i have looked hi and low but i can't find why this happened.
i have read the tutorial and many other tips and emails that i found using google. there is so much info out there that it is very complex. i installed gdal, proj, R-2.1.0<failed>
i also tried the latest from cvs but ran into too many files not found but are installed<jpeg,tiff,png,postgres,fftw>
i have macosx 10.4.1 on tibook using grass61cvs...same with grass60

child process exited abnormally
    while executing
"exec -- g.region vect=roads >@ stdout 2>@ stderr"
    ("eval" body line 1)
    invoked from within
"eval exec -- $cmd $args >@ stdout 2>@ stderr"
    (procedure "run" line 2)
    invoked from within
"run $cmd"
    (procedure "DmCmd::display" line 13)
    invoked from within
"DmCmd::display $node"
    ("cmd" arm line 2)
    invoked from within
"switch $type {
        group {
            DmGroup::display $node
    }
    raster {
        DmRaster::display $node
    }
    labels {
        DmLabels::display $node
..."
    (procedure "Dm::display_node" line 6)
    invoked from within
"Dm::display_node $n"
    (procedure "DmGroup::display" line 11)
    invoked from within
"DmGroup::display "root""
    (procedure "Dm::display" line 6)
    invoked from within
"Dm::display"
    ("uplevel" body line 1)
    invoked from within
"uplevel \#0 $cmd"
    (procedure "Button::_release" line 18)
    invoked from within
"Button::_release .mainframe.topf.tb0.bbox1.b0"
    (command bound to event)

in the startup window i get:

Welcome to GRASS 6.0.0 (2005)
GRASS homepage: http://grass.itc.it/
This version running thru: Bash Shell (/bin/bash)
Help is available with the command: g.manual -i
See the licence terms with: g.version -c
If required, restart the graphical user interface with: d.m &
When ready to quit enter: exit
GRASS 6.0.0 (spearfish):~ > NavGetReply failed, -128
using default visual which is TrueColor
ncolors: 16777216
Graphics driver [x0] started
ERROR: vector map <roads> not found

/|\

i have looked hi and low but i can't find why this happened.
i have read the tutorial and many other tips and emails that i found
using google. there is so much info out there that it is very complex.
i installed gdal, proj, R-2.1.0<failed>
i also tried the latest from cvs but ran into too many files not found
but are installed<jpeg,tiff,png,postgres,fftw>
i have macosx 10.4.1 on tibook using grass61cvs...same with grass60

Are you using the Lorenzo Moretti binaries, the MaxOSX binaries, or
something you compiled yourself?

GRASS 6.0.0 (spearfish):~ > NavGetReply failed, -128
using default visual which is TrueColor
ncolors: 16777216
Graphics driver [x0] started
ERROR: vector map <roads> not found

what does:

"g.list rast"

at the GRASS prompt show?

Hamish

>>>Are you using the Lorenzo Moretti binaries, the MaxOSX binaries, or
>>>something you compiled yourself?

..

>>cvs don't compile

..

>
>Is there a need to compile it? Lorenzo's binaries are brilliant.

..

no i just gave compiling a try after the binaries didn't work
out...how do i tell if they are lorenzos or whatever? i got them
here:http://www.public.asu.edu/~cmbarton/files/grass_osx/

That is a mirror of Lorenzo's site:
  http://wwwamb.bologna.enea.it/forgrass/

Did you use the library installer that came with the GRASS 6 app from
Lorenzo's and did it work? Copy the app to /Applications, not just run it
from the package window? Did you install Lorenzo's Tiger patch needed for
his 6.0.0 release?

Hamish

My site serves as a mirror of Lorenzo's when the connections to Europe are
slow. However, he has the newest binaries always. They should install in a
minute or two. There is no need to compile.

I'm in Europe currently, so I don't get the site updated as often as
Lorenzo does. However, I just put up the most recent binary package
(18-June-2005).

I've kept a series of earlier ones archived because of a problem with
v.in.ascii that has been reported. I don't know if it is fixed in the
current build or not.

Michael

On 6/20/05 10:03 AM, "Hamish" <hamish_nospam@yahoo.com> wrote:

Are you using the Lorenzo Moretti binaries, the MaxOSX binaries, or
something you compiled yourself?

..

cvs don't compile

..

Is there a need to compile it? Lorenzo's binaries are brilliant.

..

no i just gave compiling a try after the binaries didn't work
out...how do i tell if they are lorenzos or whatever? i got them
here:http://www.public.asu.edu/~cmbarton/files/grass_osx/

That is a mirror of Lorenzo's site:
  http://wwwamb.bologna.enea.it/forgrass/

Did you use the library installer that came with the GRASS 6 app from
Lorenzo's and did it work? Copy the app to /Applications, not just run it
from the package window? Did you install Lorenzo's Tiger patch needed for
his 6.0.0 release?

Hamish

____________________
C. Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
PO Box 872402
Arizona State University
Tempe, AZ 85287-2402
USA

Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton>

Michael,

That v.in.ascii problem is a big one for me -- I suppose it's the same problem I'm having trying to bring in point data. Are there any work arounds in the mean time?

Regards,
Tom

Michael Barton wrote:

My site serves as a mirror of Lorenzo's when the connections to Europe are
slow. However, he has the newest binaries always. They should install in a
minute or two. There is no need to compile.

I'm in Europe currently, so I don't get the site updated as often as
Lorenzo does. However, I just put up the most recent binary package
(18-June-2005).

I've kept a series of earlier ones archived because of a problem with
v.in.ascii that has been reported. I don't know if it is fixed in the
current build or not.

Michael

On 6/20/05 10:03 AM, "Hamish" <hamish_nospam@yahoo.com> wrote:

Are you using the Lorenzo Moretti binaries, the MaxOSX binaries, or
something you compiled yourself?
           

..
   

cvs don't compile
         

..
   

Is there a need to compile it? Lorenzo's binaries are brilliant.
       

..
   

no i just gave compiling a try after the binaries didn't work
out...how do i tell if they are lorenzos or whatever? i got them
here:http://www.public.asu.edu/~cmbarton/files/grass_osx/
     

That is a mirror of Lorenzo's site:
http://wwwamb.bologna.enea.it/forgrass/

Did you use the library installer that came with the GRASS 6 app from
Lorenzo's and did it work? Copy the app to /Applications, not just run it
from the package window? Did you install Lorenzo's Tiger patch needed for
his 6.0.0 release?

Hamish

____________________
C. Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
PO Box 872402
Arizona State University
Tempe, AZ 85287-2402
USA

Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton>

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

--
Thomas E Adams
National Weather Service
Ohio River Forecast Center
1901 South State Route 134
Wilmington, OH 45177

EMAIL: thomas.adams@noaa.gov

VOICE: 937-383-0528
FAX: 937-383-0033

Tom,

Hamish suggested reverting to an earlier version of GRASS.

You can also import the ascii data into another program (excel, open office, filemaker) and export it as dbf. Then you can use v.in.db to import it.

The thing is, I don’t know in which versions v.in.ascii is broken and in which it is OK.

Try the newest one (18 June) and one from the end of May (archived on my site).

Michael

On 6/20/05 4:37 PM, “Thomas Adams” Thomas.Adams@noaa.gov wrote:

Michael,

That v.in.ascii problem is a big one for me — I suppose it’s the same problem I’m having trying to bring in point data. Are there any work arounds in the mean time?

Regards,
Tom

Michael Barton wrote:

My site serves as a mirror of Lorenzo’s when the connections to Europe are
slow. However, he has the newest binaries always. They should install in a
minute or two. There is no need to compile.

I’m in Europe currently, so I don’t get the site updated as often as
Lorenzo does. However, I just put up the most recent binary package
(18-June-2005).

I’ve kept a series of earlier ones archived because of a problem with
v.in.ascii that has been reported. I don’t know if it is fixed in the
current build or not.

Michael

On 6/20/05 10:03 AM, “Hamish” hamish_nospam@yahoo.com mailto:hamish_nospam@yahoo.com wrote:

Are you using the Lorenzo Moretti binaries, the MaxOSX binaries, or
something you compiled yourself?

cvs don’t compile

Is there a need to compile it? Lorenzo’s binaries are brilliant.

no i just gave compiling a try after the binaries didn’t work
out…how do i tell if they are lorenzos or whatever? i got them
here:http://www.public.asu.edu/~cmbarton/files/grass_osx/

That is a mirror of Lorenzo’s site:
http://wwwamb.bologna.enea.it/forgrass/

Did you use the library installer that came with the GRASS 6 app from
Lorenzo’s and did it work? Copy the app to /Applications, not just run it
from the package window? Did you install Lorenzo’s Tiger patch needed for
his 6.0.0 release?

Hamish


C. Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
PO Box 872402
Arizona State University
Tempe, AZ 85287-2402
USA

Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton http://www.public.asu.edu/~cmbarton >


grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5


C. Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
PO Box 872402
Arizona State University
Tempe, AZ 85287-2402
USA

Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton>

That v.in.ascii problem is a big one for me -- I suppose it's the same
problem I'm having trying to bring in point data. Are there any work
arounds in the mean time?

Can you describe again the problem you are seeing?

Failure to import more than 50,000 points in 6.0.0? (out of memory)
Failure to import more than 3,000,000 points in 6.1-cvs? (out of memory)
Failure to import any points in 6.1-cvs? (see below)

Right now, I'm getting this. (fresh & latest CVS, in a new mapset)

GRASS:6.1-cvs > echo "1|2|3" | v.in.ascii out=test654
Maximum input row length: 6
Maximum number of columns: 3
Minimum number of columns: 3
column: 1 type: integer
column: 2 type: integer
column: 3 type: integer
DBMI-DBF driver error:
Incompatible value type.
Error in db_execute_immediate()

ERROR: Cannot insert values: insert into test654 values ( 1, '1', '2', '3')

GRASS:6.1-cvs > db.connect -p
driver:dbf
database:$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/
schema:(null)
group:(null)

thanks,
Hamish

think i found the problem...i was running XDarwin. deleting XDarwin and installing X11 seems to have fixed it. i can run glass6 and grass61cvs now as well as OpenOSX Grass

i have looked hi and low but i can't find why this happened.
i have read the tutorial and many other tips and emails that i found using google. there is so much info out there that it is very complex. i installed gdal, proj, R-2.1.0<failed>
i also tried the latest from cvs but ran into too many files not found but are installed<jpeg,tiff,png,postgres,fftw>
i have macosx 10.4.1 on tibook using grass61cvs...same with grass60

child process exited abnormally
   while executing
"exec -- g.region vect=roads >@ stdout 2>@ stderr"
   ("eval" body line 1)
   invoked from within
"eval exec -- $cmd $args >@ stdout 2>@ stderr"
   (procedure "run" line 2)
   invoked from within
"run $cmd"
   (procedure "DmCmd::display" line 13)
   invoked from within
"DmCmd::display $node"
   ("cmd" arm line 2)
   invoked from within
"switch $type {
       group {
           DmGroup::display $node
   }
   raster {
       DmRaster::display $node
   }
   labels {
       DmLabels::display $node
..."
   (procedure "Dm::display_node" line 6)
   invoked from within
"Dm::display_node $n"
   (procedure "DmGroup::display" line 11)
   invoked from within
"DmGroup::display "root""
   (procedure "Dm::display" line 6)
   invoked from within
"Dm::display"
   ("uplevel" body line 1)
   invoked from within
"uplevel \#0 $cmd"
   (procedure "Button::_release" line 18)
   invoked from within
"Button::_release .mainframe.topf.tb0.bbox1.b0"
   (command bound to event)

in the startup window i get:

Welcome to GRASS 6.0.0 (2005)
GRASS homepage: http://grass.itc.it/
This version running thru: Bash Shell (/bin/bash)
Help is available with the command: g.manual -i
See the licence terms with: g.version -c
If required, restart the graphical user interface with: d.m &
When ready to quit enter: exit
GRASS 6.0.0 (spearfish):~ > NavGetReply failed, -128
using default visual which is TrueColor
ncolors: 16777216
Graphics driver [x0] started
ERROR: vector map <roads> not found

/|\

Hamish,

I just updated GRASS6 from cvs and for me your example runs:
(looking at your prompt GRASS:6.1-cvs and mine GRASS 6.0.cvs am I using
a different version of GRASS? - I will check with Markus tomorrow).
Can somebody else run the same thing as shown below?

Helena

GRASS 6.0.cvs (wakestate):~/lgrass > echo "1|2|3" | v.in.ascii out=test456
Maximum input row length: 6
Maximum number of columns: 3
Minimum number of columns: 3
column: 1 type: integer
column: 2 type: integer
column: 3 type: integer
Building topology ...
1 primitives registered
Building areas: 100%
0 areas built
0 isles built
Attaching islands:
Attaching centroids: 100%
Topology was built.
Number of nodes : 1
Number of primitives: 1
Number of points : 1
Number of lines : 0
Number of boundaries: 0
Number of centroids : 0
Number of areas : 0
Number of isles : 0

On Jun 21, 2005, at 9:23 PM, Hamish wrote:

That v.in.ascii problem is a big one for me -- I suppose it's the same
problem I'm having trying to bring in point data. Are there any work
arounds in the mean time?

Can you describe again the problem you are seeing?

Failure to import more than 50,000 points in 6.0.0? (out of memory)
Failure to import more than 3,000,000 points in 6.1-cvs? (out of memory)
Failure to import any points in 6.1-cvs? (see below)

Right now, I'm getting this. (fresh & latest CVS, in a new mapset)

GRASS:6.1-cvs > echo "1|2|3" | v.in.ascii out=test654
Maximum input row length: 6
Maximum number of columns: 3
Minimum number of columns: 3
column: 1 type: integer
column: 2 type: integer
column: 3 type: integer
DBMI-DBF driver error:
Incompatible value type.
Error in db_execute_immediate()

ERROR: Cannot insert values: insert into test654 values ( 1, '1', '2', '3')

GRASS:6.1-cvs > db.connect -p
driver:dbf
database:$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/
schema:(null)
group:(null)

thanks,
Hamish

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

Helena Mitasova
Dept. of Marine, Earth and Atm. Sciences
1125 Jordan Hall, NCSU Box 8208,
Raleigh NC 27695
http://skagit.meas.ncsu.edu/~helena/

I was indeed running an old version - with 6.1 I get the same error with your example, but my data read OK,

(this is unrelated to the memory leak which starts to cause problems with 3milion+ points)

Helena

GRASS 6.0.cvs (wakestate):~/grasscvs6/grass-6.1.cvs/bin > echo "1|2|3" | ./v.in.ascii out=test4561
Maximum input row length: 6
Maximum number of columns: 3
Minimum number of columns: 3
column: 1 type: integer
column: 2 type: integer
column: 3 type: integer
DBMI-DBF driver error:
Incompatible value type.
Error in db_execute_immediate()

ERROR: Cannot insert values: insert into test4561 values ( 1, '1', '2',
        '3')

GRASS 6.0.cvs (wakestate):~/lgrass > ~/grasscvs6/grass-6.1.cvs/bin/v.in.ascii -zt nclidcc.ptstestxyz out=test61 fs=space z=3
Maximum input row length: 28
Maximum number of columns: 3
Minimum number of columns: 3
Building topology ...
16075 primitives registered
Building areas: 100%
0 areas built
0 isles built
Attaching islands:
Attaching centroids: 100%
Topology was built.
Number of nodes : 16075
Number of primitives: 16075
Number of points : 16075
Number of lines : 0
Number of boundaries: 0
Number of centroids : 0
Number of areas : 0
Number of isles : 0
GRASS 6.0.cvs (wakestate):~/lgrass > head nclidcc.ptstestxyz
2091304.41 730008.93 412.05
2091325.21 730001.13 411.08
2091345.45 730003.65 410.18

On Jun 22, 2005, at 12:03 AM, Helena Mitasova wrote:

Hamish,

I just updated GRASS6 from cvs and for me your example runs:
(looking at your prompt GRASS:6.1-cvs and mine GRASS 6.0.cvs am I using
a different version of GRASS? - I will check with Markus tomorrow).
Can somebody else run the same thing as shown below?

Helena

GRASS 6.0.cvs (wakestate):~/lgrass > echo "1|2|3" | v.in.ascii out=test456
Maximum input row length: 6
Maximum number of columns: 3
Minimum number of columns: 3
column: 1 type: integer
column: 2 type: integer
column: 3 type: integer
Building topology ...
1 primitives registered
Building areas: 100%
0 areas built
0 isles built
Attaching islands:
Attaching centroids: 100%
Topology was built.
Number of nodes : 1
Number of primitives: 1
Number of points : 1
Number of lines : 0
Number of boundaries: 0
Number of centroids : 0
Number of areas : 0
Number of isles : 0

On Jun 21, 2005, at 9:23 PM, Hamish wrote:

That v.in.ascii problem is a big one for me -- I suppose it's the same
problem I'm having trying to bring in point data. Are there any work
arounds in the mean time?

Can you describe again the problem you are seeing?

Failure to import more than 50,000 points in 6.0.0? (out of memory)
Failure to import more than 3,000,000 points in 6.1-cvs? (out of memory)
Failure to import any points in 6.1-cvs? (see below)

Right now, I'm getting this. (fresh & latest CVS, in a new mapset)

GRASS:6.1-cvs > echo "1|2|3" | v.in.ascii out=test654
Maximum input row length: 6
Maximum number of columns: 3
Minimum number of columns: 3
column: 1 type: integer
column: 2 type: integer
column: 3 type: integer
DBMI-DBF driver error:
Incompatible value type.
Error in db_execute_immediate()

ERROR: Cannot insert values: insert into test654 values ( 1, '1', '2', '3')

GRASS:6.1-cvs > db.connect -p
driver:dbf
database:$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/
schema:(null)
group:(null)

thanks,
Hamish

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

Helena Mitasova
Dept. of Marine, Earth and Atm. Sciences
1125 Jordan Hall, NCSU Box 8208,
Raleigh NC 27695
http://skagit.meas.ncsu.edu/~helena/

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

Helena Mitasova
Dept. of Marine, Earth and Atm. Sciences
1125 Jordan Hall, NCSU Box 8208,
Raleigh NC 27695
http://skagit.meas.ncsu.edu/~helena/

You can also import the ascii data into another program (excel, open
office, filemaker) and export it as dbf. Then you can use v.in.db to
import it.

This will probably not work if you have more than 32k or 65k points to
bring in; spreadsheets are horrible for large datasets. Just start up in
GRASS 6.0.0 to do the import & then switch back to 6.1 if the 6.1 import
is broken.

The thing is, I don¹t know in which versions v.in.ascii is broken and
in which it is OK.

I'm not sure if the insert into DB quoting problem is just happening to
me. Can anyone else who is self-compiling on Debian/sarge test? It
happens to me on multiple Debian/sarge machines with fresh CVS.

hmmm interesting. I've just tried a copy of 6.1 that was compiled March
2005 and it breaks too, although 6.0.0 is fine. I'm sure it only started
to break in the last few days, so I wonder if an upgraded library is to
blame somehow..?

Hamish

Right now, I'm getting this. (fresh & latest CVS, in a new mapset)

[SQL insert is incorrectly 'quoting' int & double fields]

GRASS:6.1-cvs > echo "1|2|3" | v.in.ascii out=test654
Maximum input row length: 6
Maximum number of columns: 3
Minimum number of columns: 3
column: 1 type: integer
column: 2 type: integer
column: 3 type: integer
DBMI-DBF driver error:
Incompatible value type.
Error in db_execute_immediate()

ERROR: Cannot insert values: insert into test654 values ( 1, '1', '2',

'3')

GRASS:6.1-cvs > db.connect -p
driver:dbf
database:$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/
schema:(null)
group:(null)

I apologize for these emails, but I think that we need to get v.in.ascii running because it is a core module
(there is no use for all the other great GRASS modules if you cannot import your data).

There was a change in in.c implemented 4 weaks ago see
http://freegis.org/cgi-bin/viewcvs.cgi/grass6/vector/v.in.ascii/
Could this have broken the example shown by Hamish?
His test runs if the data are read as 3d coordinates x,y,z but not if the third column is read as attribute

GRASS 6.0.cvs (wakestate):~/grasscvs6 > echo "1|2|3" |~/grasscvs6/grass-6.1.cvs/bin/v.in.ascii -zt out=test4561z z=3
Maximum input row length: 6
Maximum number of columns: 3
Minimum number of columns: 3
Building topology ...
1 primitives registered
Building areas: 100%
0 areas built
0 isles built
Attaching islands:
Attaching centroids: 100%
Topology was built.
Number of nodes : 1
Number of primitives: 1
Number of points : 1
Number of lines : 0
Number of boundaries: 0
Number of centroids : 0
Number of areas : 0
Number of isles : 0

GRASS 6.0.cvs (wakestate):~/grasscvs6 > echo "1|2|3" |~/grasscvs6/grass-6.1.cvs/bin/v.in.ascii out=test4561c
Maximum input row length: 6
Maximum number of columns: 3
Minimum number of columns: 3
column: 1 type: integer
column: 2 type: integer
column: 3 type: integer
DBMI-DBF driver error:
Incompatible value type.
Error in db_execute_immediate()

ERROR: Cannot insert values: insert into test4561c values ( 1, '1', '2',
        '3')

On Jun 22, 2005, at 12:32 AM, Helena Mitasova wrote:

I was indeed running an old version - with 6.1 I get the same error with your example, but my data read OK,

(this is unrelated to the memory leak which starts to cause problems with 3milion+ points)

Helena

GRASS 6.0.cvs (wakestate):~/grasscvs6/grass-6.1.cvs/bin > echo "1|2|3" | ./v.in.ascii out=test4561
Maximum input row length: 6
Maximum number of columns: 3
Minimum number of columns: 3
column: 1 type: integer
column: 2 type: integer
column: 3 type: integer
DBMI-DBF driver error:
Incompatible value type.
Error in db_execute_immediate()

ERROR: Cannot insert values: insert into test4561 values ( 1, '1', '2',
       '3')

GRASS 6.0.cvs (wakestate):~/lgrass > ~/grasscvs6/grass-6.1.cvs/bin/v.in.ascii -zt nclidcc.ptstestxyz out=test61 fs=space z=3
Maximum input row length: 28
Maximum number of columns: 3
Minimum number of columns: 3
Building topology ...
16075 primitives registered
Building areas: 100%
0 areas built
0 isles built
Attaching islands:
Attaching centroids: 100%
Topology was built.
Number of nodes : 16075
Number of primitives: 16075
Number of points : 16075
Number of lines : 0
Number of boundaries: 0
Number of centroids : 0
Number of areas : 0
Number of isles : 0
GRASS 6.0.cvs (wakestate):~/lgrass > head nclidcc.ptstestxyz
2091304.41 730008.93 412.05
2091325.21 730001.13 411.08
2091345.45 730003.65 410.18

On Jun 22, 2005, at 12:03 AM, Helena Mitasova wrote:

Hamish,

I just updated GRASS6 from cvs and for me your example runs:
(looking at your prompt GRASS:6.1-cvs and mine GRASS 6.0.cvs am I using
a different version of GRASS? - I will check with Markus tomorrow).
Can somebody else run the same thing as shown below?

Helena

GRASS 6.0.cvs (wakestate):~/lgrass > echo "1|2|3" | v.in.ascii out=test456
Maximum input row length: 6
Maximum number of columns: 3
Minimum number of columns: 3
column: 1 type: integer
column: 2 type: integer
column: 3 type: integer
Building topology ...
1 primitives registered
Building areas: 100%
0 areas built
0 isles built
Attaching islands:
Attaching centroids: 100%
Topology was built.
Number of nodes : 1
Number of primitives: 1
Number of points : 1
Number of lines : 0
Number of boundaries: 0
Number of centroids : 0
Number of areas : 0
Number of isles : 0

On Jun 21, 2005, at 9:23 PM, Hamish wrote:

That v.in.ascii problem is a big one for me -- I suppose it's the same
problem I'm having trying to bring in point data. Are there any work
arounds in the mean time?

Can you describe again the problem you are seeing?

Failure to import more than 50,000 points in 6.0.0? (out of memory)
Failure to import more than 3,000,000 points in 6.1-cvs? (out of memory)
Failure to import any points in 6.1-cvs? (see below)

Right now, I'm getting this. (fresh & latest CVS, in a new mapset)

GRASS:6.1-cvs > echo "1|2|3" | v.in.ascii out=test654
Maximum input row length: 6
Maximum number of columns: 3
Minimum number of columns: 3
column: 1 type: integer
column: 2 type: integer
column: 3 type: integer
DBMI-DBF driver error:
Incompatible value type.
Error in db_execute_immediate()

ERROR: Cannot insert values: insert into test654 values ( 1, '1', '2', '3')

GRASS:6.1-cvs > db.connect -p
driver:dbf
database:$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/
schema:(null)
group:(null)

thanks,
Hamish

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

Helena Mitasova
Dept. of Marine, Earth and Atm. Sciences
1125 Jordan Hall, NCSU Box 8208,
Raleigh NC 27695
http://skagit.meas.ncsu.edu/~helena/

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

Helena Mitasova
Dept. of Marine, Earth and Atm. Sciences
1125 Jordan Hall, NCSU Box 8208,
Raleigh NC 27695
http://skagit.meas.ncsu.edu/~helena/

Helena Mitasova
Dept. of Marine, Earth and Atm. Sciences
1125 Jordan Hall, NCSU Box 8208,
Raleigh NC 27695
http://skagit.meas.ncsu.edu/~helena/

think i found the problem...i was running XDarwin. deleting XDarwin
and installing X11 seems to have fixed it. i can run glass6 and
grass61cvs now as well as OpenOSX Grass

Good to know what the problem was.

Does XDarwin provide a standard X interface? i.e. are the

  if [ "$HOSTTYPE" = "macintosh" ] ; then

switches in lib/init/init.sh not generic enough?
Is your $HOSTTYPE "darwin"?

or is your (e.g.) Tcl/Tk assuming Apple's X11? I would think non-GUI
GRASS would be ok (d.mon, d.rast, etc).

Hamish

There was a change in in.c implemented 4 weaks ago see
http://freegis.org/cgi-bin/viewcvs.cgi/grass6/vector/v.in.ascii/
Could this have broken the example shown by Hamish?

That's the one. The coltype2 that gets sent to points_to_bin() on line
389 is only populated if the columns= option is used. Otherwise it is
being used uninitialized. No gcc warning for uninitialized pointers?

Changing that back to "coltype" makes it work again for me.

work-around: be sure to use columns=

Hamish

Hamish wrote:

think i found the problem...i was running XDarwin. deleting XDarwin
and installing X11 seems to have fixed it. i can run glass6 and
grass61cvs now as well as OpenOSX Grass
   
Good to know what the problem was.

Does XDarwin provide a standard X interface? i.e. are the

if [ "$HOSTTYPE" = "macintosh" ] ; then

switches in lib/init/init.sh not generic enough?
Is your $HOSTTYPE "darwin"?

echo $HOSTTYPE
powerpc

/|\

Hamish,

So, are you saying if I have x,y,z data, I should use columns=3? What if I have x,y,z,t data, where z is an elevation and t is some value? I assume columns=4? Does GRASS know the difference between z and t? Another question is how does this relate to gstat use within GRASS6; does gstat know the variable I'm interested in is t and not z?

Regards,
Tom

Hamish wrote:

There was a change in in.c implemented 4 weaks ago see
http://freegis.org/cgi-bin/viewcvs.cgi/grass6/vector/v.in.ascii/
Could this have broken the example shown by Hamish?
   
That's the one. The coltype2 that gets sent to points_to_bin() on line 389 is only populated if the columns= option is used. Otherwise it is being used uninitialized. No gcc warning for uninitialized pointers?

Changing that back to "coltype" makes it work again for me.

work-around: be sure to use columns=

Hamish

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

--
Thomas E Adams
National Weather Service
Ohio River Forecast Center
1901 South State Route 134
Wilmington, OH 45177

EMAIL: thomas.adams@noaa.gov

VOICE: 937-383-0528
FAX: 937-383-0033

So, are you saying if I have x,y,z data, I should use columns=3? What
if I have x,y,z,t data, where z is an elevation and t is some value?
I assume columns=4? Does GRASS know the difference between z and t?

from the help page:
Parameters:
[...]
  columns Columns definition for points mode in SQL style, for example:
     'x double precision, y double precision, cat int, name varchar(10)'
[...]
Flags:
  -z create 3D file
  -t Do not create table in points mode.

The column= parameter lets you name the attribute columns. I think the
code that is causing this bug was to let you override the automatically
determined column type. If you don't use columns= it just names them
str_1, int_1, int_2, etc.

If you have x,y,z data you can choose if you want it stored as a 3D
points file* (&/or without a DB table) or a 2D points file with one
containing a z attribute column of a numerical type. Additional columns
can be whatever you like, and most modules should give you the choice of
which column you want to use.

[*] use -z and z=

Another question is how does this relate to gstat use within GRASS6;
does gstat know the variable I'm interested in is t and not z?

No idea. If written for GRASS 6 then it *should* give you a choice.

Hamish

On Thu, June 23, 2005 3:36, Hamish said:

So, are you saying if I have x,y,z data, I should use columns=3? What
if I have x,y,z,t data, where z is an elevation and t is some value?
I assume columns=4? Does GRASS know the difference between z and t?

from the help page:
Parameters:
[...]
  columns Columns definition for points mode in SQL style, for example:
     'x double precision, y double precision, cat int, name varchar(10)'
[...]
Flags:
  -z create 3D file
  -t Do not create table in points mode.

The column= parameter lets you name the attribute columns. I think the
code that is causing this bug was to let you override the automatically
determined column type. If you don't use columns= it just names them
str_1, int_1, int_2, etc.

Would it be very hard to have the module give you the choice of using the
first line as the column names ?

Moritz

Would it be very hard to have the module give you the choice of using
the first line as the column names ?

Yes, that would be nice. For now the development version has a skip=
option which will save header info to the vector's history file (view
with 'v.info -h') and will also skip any lines starting with a '#'.

Hamish

Patch, my CVS account doesnot work:

Radim

--- in.c.orig 2005-06-23 10:51:21.777120402 +0200
+++ in.c 2005-06-23 11:00:04.465776241 +0200
@@ -364,6 +364,8 @@
                                break;
                        }
                    }
+ } else {
+ coltype2 = coltype;
                }

                if ( catcol < 0 ) {

On 6/22/05, Hamish <hamish_nospam@yahoo.com> wrote:

> There was a change in in.c implemented 4 weaks ago see
> http://freegis.org/cgi-bin/viewcvs.cgi/grass6/vector/v.in.ascii/
> Could this have broken the example shown by Hamish?

That's the one. The coltype2 that gets sent to points_to_bin() on line
389 is only populated if the columns= option is used. Otherwise it is
being used uninitialized. No gcc warning for uninitialized pointers?

Changing that back to "coltype" makes it work again for me.

work-around: be sure to use columns=

Hamish