Server not WMS compliant for non-existing elevation levels

Issue #204 new
Joern Ungermann created an issue

For elevation/level values, for which no data values are given, the server currently selects the data belonging to the next lower level. According to specification, it should not do that, but give an Error. Alternatively, the WMS specification allows the Server to specify that it will give the Nearest available level instead. In this case, it needs to indicate this behaviour in its capability document and also give an HTML warning.

The current behaviour of rounding down isn't very sensible. As a quick fix, we could raise an Exception if the level is not present. In case of floating point values, we probably need to define a sensible error margin due to the float->ascii->float conversion involved.

The more useful behaviour would probably be returning the nearest value, but according to specification, which implies informing the client about it in HTML warnings.

Comments (4)

  1. Reimar Bauer
    • changed milestone to 1.9.0

    For elevation/level values, for which no data values are given, the server currently selects the data belonging to the next lower level. According to specification, it should not do that, but give an Error. Alternatively, the WMS specification allows the Server to specify that it will give the Nearest available level instead. In this case, it needs to indicate this behaviour in its capability document and also give an HTML warning.

    The current behaviour of rounding down isn't very sensible. As a quick fix, we could raise an Exception if the level is not present. In case of floating point values, we probably need to define a sensible error margin due to the float->ascii->float conversion involved.

    The more useful behaviour would probably be returning the nearest value, but according to specification, which implies informing the client about it in HTML warnings.

  2. Log in to comment