Hi,
is there any reason not to exit with a fatal error if the user tries to
run v.to.db option=azimuth from a lat/lon location? (the result is
useless)
an alternative is to use libproj to calculate forward and backward
azimuth geodesic angles, and send that to two DB columns. Until that is
done,
Hamish wrote:
> is there any reason not to exit with a fatal error if the user tries to
> run v.to.db option=azimuth from a lat/lon location? (the result is
> useless)
Also, in an ongoing effort to stop people shooting themselves in the foot,
I would suggest to add a warning to v.to.db option=per
On Tue, Apr 12, 2011 at 10:55 PM, Hamish wrote:
> Hi,
>
> is there any reason not to exit with a fatal error if the user tries to
> run v.to.db option=azimuth from a lat/lon location? (the result is
> useless)
>
> an alternative is to use libproj to calculate forward and backward
> azimuth geodesi
I agree with Hamish on this as well. Please add the suggested
warnings. Perhaps we can provide and link, and/or condensed summary of
the following wikipedia article:
http://en.wikipedia.org/wiki/How_Long_Is_the_Coast_of_Britain%3F_Statistical_Self-Similarity_and_Fractional_Dimension
Thanks,
Dylan
