Put in architecture for having multple depths but not finalized so it always looks nice... needs work

JustinGOSSES / wellioviz

d3.js v5 visualization of well logs

https://justingosses.github.io/wellioviz/#introduction

Apache License 2.0

49 stars 12 forks source link

Put in architecture for having multple depths but not finalized so it always looks nice... needs work #14

Open JustinGOSSES opened 4 years ago

JustinGOSSES commented 4 years ago

Change how depths are handled to ensure you can have multiple depth curves per well.

JustinGOSSES commented 4 years ago

Change DepthCurve name to be associated with another well log curve
Have it be an array of depth curve names
Have it be okay to just be one depth curve name, even if there are multiple curve names
Have the curvebox2 code be able to find the max and min across different well log curves

Mostly need to change :

TEMPLATE
CURVEBOX2 function

JustinGOSSES commented 4 years ago

NOTES: Various sizes & positions impact getting y axis to look nice with both single and double depth margin.left ~ has been 60 pixel value yaxis translate value ~ translate(${margin.left*.333},0)) yaxis text appended translate value ~ .attr("y", 0 - (margin.left*0.6)) yaxis text size & number size ~ ~ .attr("dy", ".75em")

Would be nice in some ways if margins on left side where y axes are just changed when you selected to show two depths, but that would probably end up being a huge pain for someone who didn't work that exact sizing behavior, so not the greater way. Better to require developers to be explicit with everything.

kernant commented 4 years ago

add new data type "reference_track" and handle in there Make visual distinction of when "real" depth track ends (exaggerated example below)

JustinGOSSES commented 4 years ago

Have this working so I know the architecture fine but not exposed to users yet as I need to add some additional options for CSS sizing/positioning. Putting slightly lower in priority as I know architecture is fine now.