-
Notifications
You must be signed in to change notification settings - Fork 181
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
WV-3042 Support TEMPO layer #5037
Conversation
…ction_Granule.jpg
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed the base to develop (hopefully that didn't break anything).
I am noticing some issues with the granules but I also don't think the issue is because of this PR itself, so what I'm reporting might warrant a new ticket.
- If I load the URL in the PR, the granules seem to function well on the map.
- If I load http://localhost:3000, add a granule layer, I get an error message and when I close those message it states the CMR cannot be reached at this time.
- If i load http://localhost:3000, change the date to March 5, add a granule layer, I do not get an error message, and granules load on the map.
@minniewong Yeah, that probably calls for a new ticket. Could it be related to the |
@@ -12,7 +12,7 @@ | |||
"HLS_False_Color_Vegetation_Landsat", | |||
"HLS_False_Color_Urban_Landsat", | |||
"HLS_Shortwave_Infrared_Landsat", | |||
"HLS_NDVI_Landsat", | |||
"HLS_NDVI_Landsat", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we fix this indentation?
fix indentation
Description
Support TEMPO as a Granule Browse Layer
How To Test
git checkout WV-3042-TEMPO
npm run build
npm run watch