This repository has been archived by the owner on Jun 13, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
eastings are flipped when
flip_around_dateline
isTRUE
, resultingloc_x
containing "incorrect" eastings and UTM zones. While this is accounted for by later functions, direct plotting of supplied eastings and UTM zone will place data in the wrong location on a map (e.g. eastings in knot panel of Data_and_knots.png are not correct for the lat/lon coordinates in the extrapolation panels whenflip_around_dateline == T
). Functionconvert_utm_to_ll
takes supplied UTM coordinates and zones and converts them back to lat-long coordinates, reversing the "flip_around_dateline" if required, so that a corrected lat-long for knot locations is available to users. Corrected values are stored as a separate data.frame bySpatial_Information_Fn.R
Function has been checked for regions that do and do not flip around dateline, and ran
VAST--single-species_example.Rmd
with updatedSpatialDeltaGLMM
package to verify that it still works.