-
Notifications
You must be signed in to change notification settings - Fork 1
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
Map component doesn't set the temperature type in EMIKAT local temperature layers. #62
Comments
@therter how is the 'styles' parameter treated? Is it removed from the request URI? |
I'm still getting the same data for all three layers on https://csis.myclimateservice.eu/study/35/step/1524/view/maps |
Please reload the page and try again. Now you should see different data |
The layers from emikat have the following urls:
The layer from your image is the layer "Agricultural Areas in Europe". This layer comes from another wms: |
I dont unterstand, I get 3 different pictures. |
Before the last update of the map-component, the style parameter was ignored by the map-component. This was not a emikat problem and the problem is fixed. So I think, I can close this issue |
related to clarity-h2020/data-package#45
EMIKAT produces three different temperature maps (and possibly also a "discomfort" map too?). I have defined separate resources for each of them, but the map is the same for all three of them.
This is how it SHOULD look like:
Apparent temperature is the lowest.
https://service.emikat.at/geoserver/clarity/wms?service=WMS&version=1.1.0&request=GetMap&layers=clarity%3Aview.2974&bbox=4672000.0%2C1979500.0%2C4687500.0%2C1988000.0&width=768&height=421&srs=EPSG%3A3035&format=image%2Fgif&CQL_FILTER=STUDY_VARIANT%3D%27BASELINE%27%20and%20TIME_PERIOD=%27Baseline%27%20AND%20EMISSIONS_SCENARIO=%27Baseline%27%20AND%20EVENT_FREQUENCY=%27Rare%27%20AND%20SZ_ID=2846&styles=T_A
Mean radiant temperature the highest: (replace T_A with T_MRT)
and the T_UTCI is in the middle
At the moment, CSIS shows the same map for all three.
The text was updated successfully, but these errors were encountered: