<html style="direction: ltr;">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<style>body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
</head>
<body style="direction: ltr;"
bidimailui-detected-decoding-type="UTF-8" bgcolor="#FFFFFF"
text="#000000">
On 26/11/2011 22:09, Daniel Lee wrote:
<blockquote
cite="mid:CAJHDHfogiNHorua=+rLpemEO3_htyFuyMCLqaTe7QWgtvNSpUw@mail.gmail.com"
type="cite">Okay, sorry to bug again, but now I do have kind of
the same problem again. Here we go:
<div><br>
</div>
<div>v.out.ogr only gives me the field cat in the attribute table,
all other fields are gone:</div>
<div>v.out.ogr input=Buildings@PERMANENT type=area
dsn=/tmp/buildings.shp layer=2 --overwrite</div>
<div><br>
</div>
<div>The geometries are exported, but no attributes from layer 2
come with. In GRASS I can see that the attributes are readable
in layer 2. I really need these attributes in the shapefile, or
I need to be able to export the geometries directly, together
with the attributes, to PostGIS - the goal is to show them in a
Geoserver. Any ideas?</div>
<div><br>
</div>
</blockquote>
<br>
Does the PostGIS "buildings" table have a "geometry" column (usually
'the_geom') ?<br>
If v.out.ogr is successful this PostGIS table will be a spatial
table. All you need to do is include the geometry column when
creating the views, and these views should be displayable in
Geoserver.<br>
<br>
The multiple cat rows are probably due to the OUTER JOIN...<br>
<br>
<br>
<blockquote
cite="mid:CAJHDHfogiNHorua=+rLpemEO3_htyFuyMCLqaTe7QWgtvNSpUw@mail.gmail.com"
type="cite">
<div>Oh, and a tip for anyone that struggles with similar things:
I just revised my SQL script to make the views so that entries
in the table buildings_globalstrahlung_dachflaeche that don't
have a matching entry in gebaeude_nutzflaeche still come with
into the new view. I did that by, rather than using the operator
JOIN, using OUTER JOIN.</div>
<br>
This mail was received via Mail-SeCure System.<br>
</blockquote>
<p><br>
</p>
</body>
</html>