I think it has been mentioned before, with all the other feature-requests regarding sub-levels.
When selecting a level, a sub-level belongs to that level. When grabbing the measure tool to set the elevation, clicking on the model results instead of setting the elevation as: level_elevation + (or -) the measurement, it sets the elevation to the measured height, and setting a + or -, depending on wether it’s higher or lower than the parent level. And it’s placed according its value higher or lower. So it’s weird, it’s taking the absolute elevation, with a + or - in front, and it’s relative to a level, placed higher than other levels or sublevels that actually have larger absolute elevation.
The expected would be clicking in the model, setting the elevation to level_elevation ± the measurement.
Of course the above would be solved with absolute and relative field.
Please try to reproduce it, and you will understand, if the above does not make sense.
