Closed patrickkaleta closed 5 years ago
@bernhardsk Most likely a problem with EMIKAT WMS.
Loading the impact layers takes sometimes up to over a minute:
For comparison, loading the hazard layers is much faster (only around 200ms):
@bernhardsk @humerh This is one example of how the URLs look like, that are used by the map-component to get the impact layers. Is this the right URL to get the impact layers or are there other ways on how to get that layer much faster?
@humerh just provided me with this URL to get the impact layer, which only took me around 7 seconds to load.
@therter could you please have a look at this URL (after the review) and checker whether it would be possible to use this format for a request to Emikat?
This format is used. But there the map-component use tiles. So there will be several simultaneous requests. And I think that is the reason for the bad response time. But will I try to configure the map-component so that it use only one tile.
@bernhardsk You can also add the Cache-Control response header to your WMS response to avoid the reloading from the server every time, you activate the map layer
In geoserver, you can do this by selecting the layer (click on the layer link on the left side and click then on the name of the layer)
and activate the "Response Cache Headers" checkbox and set the caching time in seconds
Dear Thorsten, thank you for this info. Heinrich changed the setting. I tested it in CSIS. Already loaded layers now appear instantly.
The initial loading time is now at around 7-8 seconds per newly requested layer instead of 1,5 minutes, so thank you for changing the way in which the tiles are handled.
At first this map widget shows nothing, then after a VERY long wait just a few tiles appear.
This is for the "damage level 1, event 1". The naming convention is also strange; events have names but these names either aren't used or the widget isn't even aware of them?