-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unprojected distance? #16
Comments
E.g., something along the lines of the code below
|
Hey @RomanAbashin, And thanks for the code chunk, that'd be the only spot to change it in I'll look into this and update here. Thanks! |
@RomanAbashin I've started implementing this in #26. I started testing this with the package's example data, with original UTM coordinates back in WGS84 but if you had some of your own data you wanted to try it out with - please let me know what you think. I've opted for |
I'll need to add some checks in the function to warn if unprojected coordinates were provided without turning the "lonlat" switch on, add some tests, and update the vignettes that state throughout UTM coordinates are expected. |
Hey guys,
would it not make sense to utilize unprojected distance calculation methods? (e.g., Haversine, geodesic, ... as implemented in
geosphere
)Right now you have to project the coordinates. This makes sense for localized analyses but falls short when you work with larger areas and thresholds which cross UTM zones.
The text was updated successfully, but these errors were encountered: