It seems that the discrete tracks in the well-log viewer are moving their data one step too early; this is mostly notable on discrete logs with low steps, such as the Volve Blocking example data.
The log-viewer is showing H12 at MD [3756, 3821], but should instead be showing it at [3821, 3829]. This offset continues for the entire curve, which stops at 3920, instead of 4130
// volve_blocking_zonelog_logs.json
"data": [
[
3756.3505660463766,
null
],
[
3821.5805660478004,
2 // H12
],
[
3829.8305660479805,
3 // H11
],
[
3832.460566048038,
4 // H10
],
// ... ...
[
3920.150566049952,
14 // BELOW
],
[
4130.990566054554,
14 // BELOW
]
]
| Starts at 3756 |
Goes to "H11" at 3821 |
Ends at 3920 |
 |
 |
 |
I also checked the log-curve layer in the SubsurfaceViewer, and there the logs are correctly displayed. so its likely just an index issue in one of the log viewer utils

It seems that the discrete tracks in the well-log viewer are moving their data one step too early; this is mostly notable on discrete logs with low steps, such as the Volve Blocking example data.
The log-viewer is showing H12 at MD
[3756, 3821], but should instead be showing it at[3821, 3829]. This offset continues for the entire curve, which stops at3920, instead of4130I also checked the log-curve layer in the SubsurfaceViewer, and there the logs are correctly displayed. so its likely just an index issue in one of the log viewer utils