uw-macrostrat / geo-timescale Goto Github PK

Thanks for the great timescale!

Would it be possible to add a license?

I know it is a quite old repo, but it seems a couple of people (including me) are interested in updating it to a newer d3 version.

Many thanks!

Hi, just a minor something that I noticed that would be nice to fix. When clicking on the current time period (ie Phanerozoic in the demo view), the display text disappears while reloading similar to what happens when zooming in (ie clicking on carboniferous in the demo). I was wondering if it would be possible to add a check that avoids reloading in this way if the timescale is not zooming in or out?

Many thanks for this great project.

I don't know whether this is the right place for this, but I just wasnted to leave a big THANK YOU somewhere for you guys (@davenquinn, @JulesBlm)!

I am really grateful that you shared and updated this time scale. I just started this year with writing my own code and this repo allowed me to finally deploy my first own project. The time scale is just perfect to navigate through our archive of climate model simulations throughout the Phanerozoic.

Just wanted to let you know that your work enabled this in the first place. In case you are interested, you can see how I use the time scale at climatearchive.org.

Many thanks again,

Seb

When clicking very short intervals like the Holocene (0.0117 ma) or any of its child intervals (Greenlandian, Northgrippian, or Meghalayan), causes the the rectangles of the two top level parents (Geologic Time & Phanerozoic) to be positioned incorrectly.

I've posted a question about this bug on the: Observable forum and it was suggested by user 'mootari' that it might be due to precision problems (ie numerical instabilities). When the transition is slowed down – as suggested by mootari – the "Geologic Time" label noticeably starts shaking when clicking shorter intervals (f.e. Late Pleistocene) and in the case of Holocene and child intervals, the parent rectangles disappear after some time. This is especially apparent when the transition duration is increased.

I've made a debug notebook on Observable which reveals that the incorrect placement occurs somewhere halfway in the transition and that it affects all level 1 label placements.

This is a great application. I am having difficulty converting to d3 V6, in the .drag operation - the .origin operation gets "not a function" error. A working V6 version or pointer to examples of d3 drag with .origin would be appreciated. Thanks!

Code not working:
//var drag = d3.behavior.drag() << code from V3
var drag = d3.drag()
.origin(function() { // << Command throwing not a function error
var t = d3.select(".timescale g");
return {x: -newX, y: 0};
})
.on("start", (event, d) => {
dragStart = [d3.event.sourceEvent.pageX, d3.event.sourceEvent.pageY];
transformStart = d3.transform(d3.select(".timescale").select("g").attr("transform")).translate;
d3.event.sourceEvent.stopPropagation();
})
.on("drag", (event, d) => {
var currentDrag = [d3.event.sourceEvent.pageX, d3.event.sourceEvent.pageY];
newX = (dragStart[0] - currentDrag[0]);
d3.select(".timescale").select("g")
.attr("transform", function() {
return "translate(" + [ parseInt(transformStart[0] + -newX), 0 ] + ")scale(" +
});
});