Opened 12 years ago
Closed 12 years ago
#1928 closed defect (fixed)
after v.transform v.to.db gives incorrect length
Reported by: | pertusus | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 6.4.3 |
Component: | Vector | Version: | svn-releasebranch64 |
Keywords: | Cc: | ||
CPU: | Unspecified | Platform: | Linux |
Description
I import a dxf without georeferenced information, then scale it with v.transform. After that the line length obtained through v.to.db is wrong. If I export the line with v.out.ascii and reimport it, the length is correct.
A tarball to reproduce is attached.
tar xzvf bug_grass.tar.gz cd bug_grass ./reproduce.sh
The script will show the lengths that are much lower than the correct length (should be like 3300 for the first line, for instance).
Attachments (1)
Change History (6)
by , 12 years ago
Attachment: | bug_grass.tar.gz added |
---|
follow-up: 2 comment:1 by , 12 years ago
Replying to pertusus:
I import a dxf without georeferenced information, then scale it with v.transform. After that the line length obtained through v.to.db is wrong.
The bug in v.to.db is that it does not use geodesic distance calculations in latitude-longitude projections. Fixed in trunk r55729.
Markus M
comment:2 by , 12 years ago
Replying to mmetz:
Replying to pertusus:
I import a dxf without georeferenced information, then scale it with v.transform. After that the line length obtained through v.to.db is wrong.
The bug in v.to.db is that it does not use geodesic distance calculations in latitude-longitude projections.
Applies to 3D vectors only.
follow-up: 4 comment:3 by , 12 years ago
It works now. It also affects 6.4.3svn. Do you want that I apply the changeset patch and test there?
comment:4 by , 12 years ago
comment:5 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Tested too in 6.4.3 svn branch, it works, closing now, thanks.
reproduced for the bug