[PATCH] v.to.db compactness gives wrong results in feet location
|Reported by:||annakrat||Owned by:|
|Keywords:||v.to.db, units, area, compactness||Cc:|
I was looking in the source code of v.to.db to understand if computed area is in meters squared or location units (feet in my case). I realized area is converted to meters squared, however, perimeter seems to be in map units (feet). Therefore compactness is wrong when units are not meters (latlon is fine I guess). Setting feet as units doesn't influence compactness computation.
Currently the library functions for computing area and perimeter don't behave consistently.
Change History (12)
comment:1 by , 8 years ago
|Summary:||v.to.db compactness gives wrong results in feet location → [PATCH] v.to.db compactness gives wrong results in feet location|