-
Notifications
You must be signed in to change notification settings - Fork 356
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
MobX Change detection (Delta) - v3 #4390
Comments
Ana:
Nanda:
Other feedback (marie/ana)
Vic: wants to ensure any steps moving forward w/ Delta have long term planning of how they all fit together |
19/06/2020 |
~Wed morning @na9da to pass delta off to Wing & Regina |
@soyarsauce to clarify w/ @AnaBelgun on delta deliverables re: the two delta services, including the timeline for legend functionality |
Considerations on legends' implementation. The challenge to tackle is to display 2 legends (legend 1 for initial imagery layer, and legend 2 for the result imagery layer). There are several options, depending on the service set up:
Method 1: Use the advertised style legend url and pass the undocumented ndates parameter: https://ows.dev.dea.ga.gov.au/legend/s2a_ard_granule_nbar_t/NBR/legend.png?ndates=2 Method 2: Use the GetLegendGraphic method and pass the styles and date parameters, as you would do with GSKY which doesn't advertise a style legend url. |
Critical thing left for this is the tangential relation of WMS legends in workbench Nick is fixing |
Remaining backlogged items in v4 #4644, can confirm blocked issues are resolved |
This epic reflects design and development post user testing done on 19-21 May 2020.
The text was updated successfully, but these errors were encountered: