Hi Daniel,
Guess I should've investigated the data a bit closer, but I found a quick
workaround so I didn't really bother too much.
I generate these vectors with a little app. It should be easy enough to
detect these dodgy points before sending them to grass.
Thanks!
Andre
On Dec 15, 2007
I think that would be OK.
If you send the patch to the list I'll commit it to trunk and the 6.3
release branch.
--Wolf
On 16.12.2007 13:16, Daniel Bundala wrote:
Dylan,
I was thinking about the problem last night and a solution I have come
up with is the following.
As I mentioned in my
On Sunday 16 December 2007 03:16:52 am Daniel Bundala wrote:
Dylan,
I was thinking about the problem last night and a solution I have come
up with is the following.
As I mentioned in my previous post, a solution is to translate the
corresponding points little bit. I do not know how good
Hello,
I am not 100% certain as I did not test it, but I think that the
problem is that the very last line in myvect map contains 2 points at
the exactly same position (131.5, 67.5). Actually, you are so lucky to
get this (faulty?) behaviour:) because this occurs only if there is
exactly one
Good day guys,
I came across a problem in the v.generalize module. I do the following:
v.generalize [EMAIL PROTECTED] output=myvect_smooth type=line method=hermite
threshold=10
I then do a v.out.svg and noticed the following line in the svg file:
path gg:cat=31 d=M 111.50 -80.50 l
I've attached the myvect and myvect_smooth files.
Thanks for the help!!
On Dec 14, 2007 4:53 PM, Moritz Lennert [EMAIL PROTECTED]
wrote:
On 14/12/07 15:37, Andre Hauptfleisch wrote:
I'll try to upload the vector layer I used to an ftp site. What would
the best output format be? DXF?
You
