bgodette wrote:Except that it's not. It's a side effect of eventual consistency and has nothing to do with anything but WME's backend's current propagation delay at the time you save modification(s) to a segment(s).freade wrote:User BellHouse found the source of the problem related to Elevation Being Set to Null, it is caused by JNF (Junction Node Fixer). Just disable it and the problem is gone.
Normally this is masked by JNF's issuing a second reload after a successful save, but sometimes you might get data served from a different server that isn't yet consistent.
Just to put this into another light: I did not mean to say that there is a bug in JNF leading to the null elevation data. I said JNF triggers this issue, and I might add it is not always doing so, and it might not only be JNF doing this. But - in my experience - JNF does have a high tendency of provoking this issue, for reasons way out my understanding.
But now the check for irregular elevation data has been switched off in Validator 0.9.3, so we can let this issue sleep again.