-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Imagery Layers] NIRVSSOMCT-271 Placeholder #5324
Comments
Verified NOT fixed Testathon 06-15-22: example imagery is not displaying layer art properly (source URLs were 404ing from /testathon). The dropdown palette layout is also broken: @charlesh88 Will add testing notes once a fix is in and screen caps can be included. |
Testathon 07-11-22: verified NOT fixed, same problem as before with layer art not being displayed and throwing 404 errors in the console. |
We will need to address this feature as a new, untested feature in 2.1.0 |
This is because the example images are not being copied into the deployment directory. The issue is, they shouldn't be deployed into production environments, and we certainly should not have any configuration in a production environment that copies them into the deployment directory. One option here might be to host the example overlays from our public webserver (github pages) so they're accessible from anywhere with no deployment-specific configuration. |
If helpful, you could also/alternatively set up an |
@wbnns That's a great, suggestion, thank you! |
Testing InstructionsThis can only be verified locally.
|
VIPERRQSTS-203 describes a new "grid overlay" specifically for the viper-openmct project which will allows this to be verified in that environment. |
Verified fixed locally. |
Placeholder for NIRVSSOMCT-271
Using Example Imagery or an imagery endpoint, verify the following:
A layers menu button with dropdown appears.
Checking and unchecking layers hides layers as expected.
The text was updated successfully, but these errors were encountered: