add Chronographic authority

[mjy]

Migrated from TW-26.

[mjy]

Steps:

• Download https://paleobiodb.org/data1.2/intervals_doc.html Chrono, turn it into YML, or setup the API
• Create AssertedGeologicalTimeDistribution
• Fields: otu_id, min_my, max_my
• Let users pick a Geological Time range as a way to fill in numeric min/max
• Infer geological times based on assertions

[MJTPaleo]

chronostrat&lithostrat.xlsx

Chronostratigraphic information by Sam Heads attached, as requested. Second tab is on Lithostratigraphic information - shows an example of how things could be coded to make them easy to use: for example, if someone were to type in Crato Formation and select Nova Olinda member, it would auto populate its age (Lower Cretaceous). I don't know if that is possible to do, but that could be a feature request for the future?

Thanks! Jared

[mjy]

Thanks @MJTPaleo. I undersand the concept here.

Is there any reason not to draw from this for the chrono table: www.stratigraphy.org/ICSChart/ChronostratChart2012.pdf? (or a more current update)?

The chrono data will be stored hierarchically, so picking the finest level will auto-fill in times, and the higher categories.

Binding the chrono data to the litho is going to be slightly trickier. It could be that as real data become entered (litho and values from Paleo) they are "bound" together. Those combinations could be presented to the user for easy of picking and re-use. In this scenario we don't build a new table, we just make it easier for the user to pick existing assertions.

[MJTPaleo]

Chatted with Sam. He said that sounds fine, as long as we are able to select an age such as "Lower Cretaceous" rather than just having a time range. Most people will look for paleo specimens by searching Jurassic and the type of specimen and not via 201.3-145ma range.

I think the idea of binding them together upon entry seems reasonable, especially if that's the easiest way to do it? That would mean that I just have to do it once with each new specimen, but any subsequent specimens from a particular locality would auto-populate, right?

Let me know if that sounds reasonable. Thanks for your help on this!

[proceps]

[debpaul]

@MJTPaleo @mjy @jlpereira @proceps See for examples and possible code already using vue.js

• https://stratigraphy.org/timescale/
• https://stratigraphy.org/chart
• https://github.com/CSIRO-enviro-informatics/interactive-geological-timescale
  • note This is a vue.js application, built using node.js.
• https://vocabs.ardc.edu.au/repository/api/lda/csiro/international-chronostratigraphic-chart/2018-revised-corrected/resource?uri=http://resource.geosciml.org/vocabulary/timescale/gts2018

[mjy]

@debpaul please link to Ben Norton's work when it becomes available here.