Skip to content
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

Some Argo tracks display points outside of their expected range #944

Closed
JustinElms opened this issue Jan 14, 2022 · 1 comment · Fixed by #1163
Closed

Some Argo tracks display points outside of their expected range #944

JustinElms opened this issue Jan 14, 2022 · 1 comment · Fixed by #1163
Labels
Bug Something's wrong.

Comments

@JustinElms
Copy link
Contributor

Describe the bug
When working on a fix that would allow observation tracks to cross the international date line I found that some of these datasets contain points far outside of the track's expected path. A number of tracks in the pacific appear to contain points in the Atlantic and over Asia. At this time I'm not sure if these additional points are present in the datasets or errors created in the Navigator's code.

To Reproduce
It's easiest to view these tracks using the 'Draw Area' function under the Observations drop-down menu then selecting a large are in the Pacific ocean that intersect the international date line. When the observations window appears, select tracks, set the date range to 2020-01-01 to present day, and set the track simplification to day or week. Under Platform Filer/Platform Type select Argo Float then click apply. A number of Argo tracks will appear, may of which contain points outside of the expected track as shown below.

Expected behavior
Tracks should appear in an realistic way, not jumping back and forth around the globe.

Screenshots
broken_argo_track2
broken_argo_track

Desktop (please complete the following information):

  • OS: Windows/Ubuntu
  • Browser Chrome/Edge
  • Version 96.0.4664.45
@JustinElms JustinElms added the Bug Something's wrong. label Jan 14, 2022
@JustinElms
Copy link
Contributor Author

Still an issue as of v9.1. Also seems to occur in tracks that from <360 to >0 lat.
image

@JustinElms JustinElms linked a pull request Sep 6, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something's wrong.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant