[GRASS-user] v.to.3d for boundary?

Hi all,

I’d like to put a boundary/centroid - into 3D with v.to.3d.

Command: v.to.3d --overwrite input=l_00004_buf_diss@Duna output=l_00004_buf_diss_3d height=110

I runs without major erro, however writes this:

v.to.3d --overwrite input=l_00004_buf_diss@Duna output=l_00004_buf_diss_3d height=110
WARNING: Vector map <l_00004_buf_diss_3d> already exists and will be overwritten
Transforming features…
Copying attributes…
Building topology for vector map l_00004_buf_diss_3d@Duna
Registering primitives…
One primitive registered
One vertex registered
Building areas…
0 areas built
0 isles built
Attaching islands…
Attaching centroids…
Number of nodes: 0
Number of primitives: 1
Number of points: 0
Number of lines: 0
Number of boundaries: 0
Number of centroids: 1
Number of areas: 0
Number of isles: 0
WARNING: Number of centroids exceeds number of areas: 1 > 0
WARNING: Number of centroids outside area: 1
Vertical extent of vector map <l_00004_buf_diss_3d>: B: 110.000000 T: 110.000000

the original vector map is this:

Map format: native
Type of map: vector (level: 2)
Number of points: 0 Number of centroids: 1
Number of lines: 0 Number of boundaries: 198
Number of areas: 1 Number of islands: 1
Map is 3D: No
Number of dblinks: 0

So, it seems that my area (boundaries) disappear during the conversion…

Topology is correct… what is the problem?

GRASS version info:

GRASS 7.0.3 (2016)

./configure --prefix=/opt/grass --with-freetype-includes=/usr/include/freetype2 --with-wxwidgets --with-readline --with-pthread --with-netcdf --with-nls --with-geos --with-postgres --with-liblas
libgis Revision: 67364
libgis Date: 2015-12-24 16:07:44 +0100 (Thu, 24 Dec 2015)
PROJ.4: 4.9.2
GDAL/OGR: 2.0.2
GEOS: 3.5.0
SQLite: 3.12.1

Thanks

Robert

(attachments)

area_sample.JPG

Hi,

2016-06-06 10:00 GMT+02:00 Robert Kuszinger <kuszinger@giscom.hu>:

Command: v.to.3d --overwrite input=l_00004_buf_diss@Duna
output=l_00004_buf_diss_3d height=110

try to append `layer=-1`. Martin

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

Hi,

2016-06-06 11:30 GMT+02:00 Robert Kuszinger <kuszinger@giscom.hu>:

thanks... it works now... hmm on GUI it was set to layer=1 (where all the
goodies are) but now it works with =-1.
Is it a default handling error in v.to.3d?

Anyway, your workaround helped a lot and thanks for that :slight_smile:

that's the way how the most vector modules behave. The features
without category are skipped. The module should print at least warning
about skipped feature and suggest workaround (layer=-1). Feel free to
report it as a new ticket.

Martin

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

On Mon, Jun 6, 2016 at 11:36 AM, Martin Landa <landa.martin@gmail.com> wrote:

Hi,

2016-06-06 11:30 GMT+02:00 Robert Kuszinger <kuszinger@giscom.hu>:

thanks... it works now... hmm on GUI it was set to layer=1 (where all the
goodies are) but now it works with =-1.
Is it a default handling error in v.to.3d?

Anyway, your workaround helped a lot and thanks for that :slight_smile:

that's the way how the most vector modules behave. The features
without category are skipped.

I would suggest to add type=area to the recognized type options of
v.to3d and make the default answer type=point,line,area. This way
boundaries without category can be automatically pulled in if they
belong to an area with a category in the selected layer. Code to do
this exists in many other modules, e.g. v.extract.

The module should print at least warning
about skipped feature and suggest workaround (layer=-1). Feel free to
report it as a new ticket.

Martin

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user