[GRASS-user] Solved: Still something wrong importing with v.in.ascii
Jorge Echeverri
jorge.echeverri at Stein.de
Thu Mar 22 13:11:25 EDT 2007
I found out it was really stupid. I rewrote my programm so that each
line is associated with its SECTION_ID and it works!!!
GRASS rules!!!
Am Donnerstag, den 22.03.2007, 17:53 +0100 schrieb
grassuser-request at grass.itc.it:
> Send grassuser mailing list submissions to
> grassuser at grass.itc.it
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://grass.itc.it/mailman/listinfo/grassuser
> or, via email, send a message with subject or body 'help' to
> grassuser-request at grass.itc.it
>
> You can reach the person managing the list at
> grassuser-owner at grass.itc.it
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of grassuser digest..."
>
>
> Today's Topics:
>
> 1. Still something wrong importing with v.in.ascii and
> connecting to DB (Jorge Echeverri)
> 2. ugly fonts in tk GUI (hajhouse)
> 3. RE: Adding a semi-transparent layer (Jos? Antonio Ruiz Arias)
> 4. python version of r.in.wms (Jachym Cepicky)
> 5. Re: r.surf.contour (Amaginary Studios)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 22 Mar 2007 15:54:54 +0100
> From: Jorge Echeverri <jorge.echeverri at Stein.de>
> Subject: [GRASS-user] Still something wrong importing with v.in.ascii
> and connecting to DB
> To: grassuser <grassuser at grass.itc.it>
> Message-ID: <1174575294.3974.22.camel at linux-a46z.site>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi,
>
> Regarding my question yesterday. I am again trying to depict the
> attributes already mentioned:
>
> 1.I performed a MySQL-query on tbl_node and tbl_line to obtain the
> couples of points defining a line and stored this in a .csv-file and
> into a new table in my database, tbl_attributes. This table also
> contains the attributes I need.
>
> tbl_attributes
> "SECTION_ID","X_ANFANG","Y_ANFANG","X_ENDE","Y_ENDE","Baujahr","Laenge","Gebiet","MTiefe","KNutzung","Material","PArt","PBreite","PHoehe","ANALYSIS_CHAPTER"
> 1,3400630.04,5718486.603,3400639.238,5718515.776,1982,30.59,"Niederaden",2.88,1,"Beton",1,300,300,1
> 182,3400639.238,5718515.776,3400648.641,5718546.057,1982,31.71,"Niederaden",3.77,1,"Beton",1,300,300,1
>
> 2. I created a new file with an awk-programm:
> L 2 11
> 3400630.04 5718486.603
> 3400639.238 5718515.776
> 1 1
> 6 6
> 7 7
> 8 8
> 9 9
> 10 10
> 11 11
> 12 12
> 13 13
> 14 14
> 15 15
> L 2 11
> 3400639.238 5718515.776
> 3400648.641 5718546.057
> 1 1
> 6 6
> 7 7
> 8 8
> 9 9
> 10 10
> 11 11
> 12 12
> 13 13
> 14 14
> 15 15
> Each line having a series of layers each associated to a category
> number!? Is this right?
>
> 3. I could load these data with v.in.ascii into GRASS
>
> 4. And I also could connect this vector file with the tbl_attributes in
> my DB
>
> The problem is when I try to display the data. Using QGIS I realised
> that the entire vector file takes the attributes from the first
> record!!??? I tried the same with GRASS using d.vect.thematic and have
> the same problem:( What did I do wrong? I don't find out the answer.
> Any ideas????
>
> Thanks
>
> Jorge
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-user/attachments/20070322/c045c961/attachment.html
More information about the grass-user
mailing list