Report bugs, things to improve

[claudiahahn]

@p-a-s-c-a-l, I have opened this issue to be able to report small things regarding CSIS. Feel free to put the content somewhere else, but I think it is helpfull to collect comments from people/ partners who start using CSIS somewhere. I have entered my other comments in already existing github issues (hopefully the right ones).

https://csis.myclimateservice.eu/study/1/step/3/view/introduction#sdfootnote1sym

• Reference 1 and 2 not correct I guess (link to copernicus website and eurostat should be there, instead: modelling framework paper and lessons learned from 2007 uk flood?)

[DenoBeno]

The text can be edited here: https://csis.myclimateservice.eu/taxonomy/term/3/edit

This is what it looks like at the moment (posted as code to show html formatting tags too):

<p>The hazard characterisation is derived by climate indices that provide an evaluation of relevant parameters for temperature and precipitation and their variation in a climate change perspective. These climate indices are calculated using the EURO-CORDEX dataset which has a spatial resolution of 0.11° (approximately 10 km over Europe). In order to determine the effect of urban adaptation on the potential variation of such climate signals, this information needs to be downscaled on an urban level, i.e. with a finer-grained spatial resolution and considering the influence of urban microclimate variables. This procedure allows to increase the resolution of final outcome of heat wave and pluvial local effect from 10 km to 500 m, since the result is projected on a European reference grid with a resolution of 500 × 500 m.</p>

<p>To this aim, a specific algorithm has been developed and applied, based on a broad literature review and original development, which links the broad-scale climate pattern to small-scale urban features. This method uses as additional input, building, infrastructure and landscape characteristics along with population distribution. This additional data is available for many cities and towns across Europe through platforms such as the Copernicus Land Monitoring Service<sup><font face="Calibri, serif"><b><a class="sdfootnoteanc" href="#sdfootnote1sym" name="sdfootnote1anc" style="font-size:90%; color:#0000ff"><sup>1</sup></a></b></font></sup> dataset UrbanAtlas and EuroStat<sup><font face="Calibri, serif"><b><a class="sdfootnoteanc" href="#sdfootnote1sym" name="sdfootnote1anc" style="font-size:90%; color:#0000ff"><sup>2</sup></a></b></font></sup> .</p>

<p>This method is used here as a proof of concept and designed as a feature of the CSIS screening tool, limited to heat and flooding hazards, as most recurring climate change related hazard across Europe.</p>

<p><span style="font-size:10pt"><span style="page-break-before:always"><span style="font-family:&quot;Calibri&quot;,serif"><a class="sdfootnotesym" href="#sdfootnote1anc" name="sdfootnote1sym" style="color:#0000ff">1</a> </span></span> L. S. Smith, Q. Liang and P. F. Quinn, “A flexible hydrodynamic modelling framework for GPUs and CPUs: Application to the Carlisle 2005 floods,” in International Conference on Flood Resilience: Experiences in Asia and Europe, Newcastle University, 2013.</span></p>

<p><span style="font-size:10pt"><span style="page-break-before:always"><span style="font-family:&quot;Calibri&quot;,serif"><a class="sdfootnotesym" href="#sdfootnote1anc" name="sdfootnote1sym" style="color:#0000ff">2</a><sup>�</sup> </span></span></span> M. Pitt, “The Pitt Review: Learning lessons from the 2007 floods, London, UK,” Cabinet Office, London, UK, 2008.</p>

[DenoBeno]

Just text:

The hazard characterisation is derived by climate indices that provide an evaluation of relevant parameters for temperature and precipitation and their variation in a climate change perspective. These climate indices are calculated using the EURO-CORDEX dataset which has a spatial resolution of 0.11° (approximately 10 km over Europe). In order to determine the effect of urban adaptation on the potential variation of such climate signals, this information needs to be downscaled on an urban level, i.e. with a finer-grained spatial resolution and considering the influence of urban microclimate variables. This procedure allows to increase the resolution of final outcome of heat wave and pluvial local effect from 10 km to 500 m, since the result is projected on a European reference grid with a resolution of 500 × 500 m.

To this aim, a specific algorithm has been developed and applied, based on a broad literature review and original development, which links the broad-scale climate pattern to small-scale urban features. This method uses as additional input, building, infrastructure and landscape characteristics along with population distribution. This additional data is available for many cities and towns across Europe through platforms such as the Copernicus Land Monitoring Service1 dataset UrbanAtlas and EuroStat2 .

This method is used here as a proof of concept and designed as a feature of the CSIS screening tool, limited to heat and flooding hazards, as most recurring climate change related hazard across Europe.

1 L. S. Smith, Q. Liang and P. F. Quinn, “A flexible hydrodynamic modelling framework for GPUs and CPUs: Application to the Carlisle 2005 floods,” in International Conference on Flood Resilience: Experiences in Asia and Europe, Newcastle University, 2013.

2� M. Pitt, “The Pitt Review: Learning lessons from the 2007 floods, London, UK,” Cabinet Office, London, UK, 2008.

[DanielRodera]

Thank you @claudiahahn for reporting the issue, I have changed the references

[claudiahahn]

@DanielRodera Thank you!

[claudiahahn]

Very small issue: "maintenance" is spelled wrong on the following page:
https://csis.myclimateservice.eu/study/35/step/1525/view/introduction:
"Overviews of of already defined nodes of different types are available under "Mainteinance""

It should be maintenance, instead of "mainteinance" and "of" instead of "of of"

[DenoBeno]

OK, thanks. Fixed.

[p-a-s-c-a-l]

done

[DenoBeno]

Strange, I thought that I have posted a report complaining about the color coding of the hazard indice maps earlier today here. In short, my recommendation is to use multicolor coding, but to avoid repeating similar colors as it's the case now (dark blue, light blue, dark blue, light bluish/turquoise). We still have maps where most of the map is just a single color.

In the meantime, I have also discovered further errors:

• snow days is not showing anything.
• Highest 1-day/5 day precipitation figures are in days, suppose they should be in mm?

[DenoBeno]

@claudiahahn, @mattia-leone : What is T_A? Ambient or apparent temperature? Ins what does this mean? (if "apparent", how is this different from UTCI?)

[p-a-s-c-a-l]

In short, my recommendation is to use multicolor coding, but to avoid repeating similar colors as it's the case now (dark blue, light blue, dark blue, light bluish/turquoise).

Colour Coding is something that has to be implemented in GeoServer (SLD). Now that layers are moved from METEOGRID to ATOS this issue could be addressed by @DanielRodera

[RobAndGo]

Hi @DenoBeno,
T_A refers to "Apparent Temperature" and is defined as:

T_A = 0.716 x UTCI - 1.48

That is, the apparent temperature, which is the temperature felt by humans, is correlated with the UTCI using the above relation (taken from a paper Blazejczyk, K., Epstein, Y., Jendritzky, G., Staiger, H., & Tinz, B. (2012). Comparison of UTCI to selected thermal indices. International journal of biometeorology, 56(3), 515-535.)

I think the reason that both are supplied is in case the users are more familiar with using one or the other.

And for completeness, UTCI is calculated as
UTCI = 3.21 + 0.872 x Ta + 0.2459 x Tmrt - 2.5078 x (0.3) - 0.0176 x (50%)
where:
Ta = air temperature (°C)
Tmrt = mean radiant temperature (°C)
The role of wind speed and relative humidity come into it with the numbers is brackets. i.e. constant values are assumed with:
wind speed at a height of 1.1m = 0.3 m/s
relative humidity = 50%

[RobAndGo]

@DenoBeno
I think the problem with the "snow days" is that the data has not been processed yet by Meteogrid (@ghilbrae @LauraMTG). That is, the data is not available on the Meteogrid geoserver:
https://clarity.meteogrid.com/geoserver/web/wicket/bookmarkable/org.geoserver.web.demo.MapPreviewPage?3

This was one of the last data sets that I uploaded and can be found on the clarity ftp here:
/clarityftp/europe/hazard_indices/precipitation/snow-days

And you are correct in that the units of the "Highest 1-day/5 day precipitation" should be in mm. In fact, this is something which I forgot to do for each index - that is I need to add the units for each index in the description.

Edit: Units have now been added to the climate indices in CSIS.

[DenoBeno]

thanks

[DenoBeno]

Last week, I have stumbled into a very strange issue. It's IMO almost a "showstopper", but more interestingly, it's something I have never seen in Drupal except on CSIS.

- paging links aren't shown

E.g. on https://csis.myclimateservice.eu/adaptation-options, first 25 adaptation options are shown but no links to the next page is presented to users.

Probably the same in https://csis.myclimateservice.eu/solution-offers and https://csis.myclimateservice.eu/showcases - I didn't check if they have paging enabled or not.

As long as the number of elements is small, we can use "show all" option, but this needs to be addressed.

[patrickkaleta]

Last week, I have stumbled into a very strange issue. It's IMO almost a "showstopper", but more interestingly, it's something I have never seen in Drupal except on CSIS.

- paging links aren't shown

E.g. on https://csis.myclimateservice.eu/adaptation-options, first 25 adaptation options are shown but no links to the next page is presented to users.

Probably the same in https://csis.myclimateservice.eu/solution-offers and https://csis.myclimateservice.eu/showcases - I didn't check if they have paging enabled or not.

As long as the number of elements is small, we can use "show all" option, but this needs to be addressed.

Took care of that. If such an error occurs, just remove remove the pager and add it back again.

[DenoBeno]

I have tested the options we have for the simple screening and encountered several issues. Most, if not all of these have been reported by me before but nothing has changed so far:

See https://csis.myclimateservice.eu/study/138/step/4143/view/summary for examples I have in mind.

First, OUR SCALES ARE TERRIBLE. I have reported this before, again and again, but nothing changes.

1. A scale that starts with blue, then changes to purple and then back to blue, before starting to change colors is a sheer madness. How an I supposed to differentiate between lower and upper blue?
2. A "consecutive something days" scale that goes from 0 to 200 is IMO quite useless too. If I have more than 100 consecutive dry days, that's 3 months without rain. Any forest that I might still have will burn, like it does in Italy these today. How about consecutive summer days?
   Consecutive
3. Rainfall values are still in days (should be mms, e.g. for "maximal 5 days percipitation")

Second, CLC2012 layers are unreliable. Sometimes I get them, sometimes not.
Third, our input layers still don't show up in the screenshot.

[p-a-s-c-a-l]

Styles/Scales are configured on GeoServer. Maybe @DanielRodera is able to address his with help from @RobAndGo.

Second, CLC2012 layers are unreliable. Sometimes I get them, sometimes not.

We could try to import CLC into ATOS GeoServer instance , so we have full control over it. Means, we can also change the legend. CLC should be available as open data (Shapfile, etc.).

Third, our input layers still don't show up in the screenshot.

Yes, they are still loaded from the old GeoServer which does not have https enabled. This will be resolved soon.

[RobAndGo]

I thought this may be a problem of links not being correct after the migration to the new geoserver by METEOGRID? I thought this was mentioned on Monday by @ghilbrae and that any issues should be reported to her.

[p-a-s-c-a-l]

It is correct that the new GeoServer is currently lacking the styling ('scales').

But the migration is not done yet. We still use the old instance. So this an independent problem with the current styling.

[ghilbrae]

We are updating the layers with the correct styles this week, so you'll find layers with correct styles and layers without.
A different matter is that there may still be layers, even updated ones, that may have styles that you don't like or that could be improved in some ways. That is something that we know nothing about, we'd need you to tell us exactly which layers and which scale/style you want for them.

[p-a-s-c-a-l]

closing this 'mega issue' in favour of more focussed ones.