MSWMS Layer problems difficult to debug

We had recently two instances of difficult to debug problems on the server side.

a) The server did not show any layers

b) The server showed a layer, but did not offer any elevation layers.

‌

ad a) the problem was a typo in the supplied dataset name, i.e. the dataset supplied to the layers was not defined and such no files were assigned. This serious misconfiguration should result in a diagnostic message and probably an abort of the startup process.

ad b) the issue is not located. But generally, the layer offers timesteps/elevations that are common over all used datasets. It would be useful to see, e.g. the number of timesteps for the individual variables and the intersection to see, from which sub-variable the problem of no timesteps originates. This should be a debug-level output.

Comments (2)