When using elevation service (web api), I get errors whenever a point is located in the sea. Eg:
On line operations, result is:
- if all points are in the sea, error code is 4002
- if only some points are in the sea, response contains a geometry with points for which elevation is known, but points in the sea are omitted from the geometry.
Is this the expected behavior?
It seems sea is outside of elevation boundaries, but still the behavior should be more consistent so that it is easier to process on client side:
- point request should return a specific “unknown” error code (to be distinguishable from execution errors)
- line should always return a geometry with same number of points as the request, points with unknown elevation may simply have no elevation data (only coordinates)
Does this look reasonable?
Any chance to have sea/ocean area covered by elevation service?