riesgos/dlr-riesgos-frontend

Coloring damage states

MichaelLangbein opened this issue · 7 comments

We've reached an aggreement on how to style damage states. Still need Camilo's Amen for this, though.

  • Coloring based on w_damage, the number-of-buildings-weighted average damage state.
  • Need to include a no-data value. @nbrinckm : Can we for this set w_damage = -1?
  • We require two styles for damage-states: one for SARA and one for Suppasri.

Here's the styling for SARA:
styling_damagestates_sara

Here's the styling for Suppasri:
styling_damagestates_suppasri

@jcgomezz : is this categorization of damages for the Peru scenario alright in your eyes?

Ok, I added the buildings column in the shapefile. This one can then be handled in the visualization.

Tasks Michael:

  • Test if SLD files can be passed to GFZ WMS
  • Dynamically create SLD using the layer-name of the WPS-Deus-output
  • Pass along SLD as a POST body with every GetMap request

I think it is great to give the responsibility of the styling back to the demonstrator. However I'm a little concerned about performance as there us more network traffic and less chances to cache images. Maybe it is good enough for the demonstrator - but for a productive environment I would suggest to switch over to fixed sld files that we store on the geoserver in the future (at least for the default cases that everyone will see at first).

Ok, styles have been updates as per our last discussion. Awaiting feedback.

Here some samples, all for the same scenario: Lima, Mag. 9.0 / ID peru_70000011

Economic loss post eq:
economic_loss_post_eq

Exposure [SARA] post eq:
exposure_sara_post_eq

Economic loss post ts:
economic_loss_post_ts

Exposure [Suppasri] post ts:
exposure_suppasri_post_ts

Exposure [Medina] post ts:
exposure_medina_post_ts

This is done - thanks a lot @nbrinckm !

I think it is great to give the responsibility of the styling back to the demonstrator. However I'm a little concerned about performance as there us more network traffic and less chances to cache images. Maybe it is good enough for the demonstrator - but for a productive environment I would suggest to switch over to fixed sld files that we store on the geoserver in the future (at least for the default cases that everyone will see at first).

Couldn't agree more. Thanks for providing those styles directly on geoserver. When style changes are decided on and have proven themselves in review, we'll create a MR to update those styles on geoserver!