Opened 14 years ago
Last modified 9 years ago
#1351 new defect
v.build error in split_q.c
Reported by: | epatton | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 6.4.6 |
Component: | Vector | Version: | svn-develbranch6 |
Keywords: | v.build, topology | Cc: | |
CPU: | x86-32 | Platform: | Linux |
Description
Hello,
I'm trying to rebuild topology on a vector, and when doing so, I run into the attached error (full backtrace from gdb).
Aside from the error itself, it's quite odd that the vector's topology is damaged in the first place; I guess that's a separate issue.
Attachments (1)
Change History (3)
by , 14 years ago
Attachment: | v.build.error.txt added |
---|
comment:1 by , 14 years ago
comment:2 by , 9 years ago
Milestone: | 6.4.2 → 6.4.6 |
---|
Note:
See TracTickets
for help on using tickets.
Replying to epatton:
I guess that the import did not finish successfully and left behind a broken vector, indicated by that warning about a coor file size mismatch.
This assertion error
occurred in the past in some cases of reprojection. Since the vector name is GSHHS_land, I guess that it has been imported with v.in.gshhs which does projection on the fly but does not check if the reprojection is legal. If this GSHHS_Land vector has been imported with v.in.gshhs into a non-latlon projection, then it needs to be confirmed first that the extent chosen for import can actually be represented in the target location. If not, v.build is actually right in refusing to build topology, although the error message is as cryptic as it can get.
Markus M