Add geological time CPTs

[Esteban82]

This PR adds CPTs to the cache for the example in this issue: GenericMappingTools/gmt-examples#47 (comment)

My doubt is if what CPTs should we add. Only the epochs? Some or all of them? I would go with all but the two first.

Link: http://www.seaviewsensing.com/pub/cpt-city/heine/

Secondary, what name should we use for the CPT? The original name (GTS2012_epochs.cpt) or a shorter name (epochs.cpt)? or something else?

[joa-quim]

After all this time this is as if it started from anew. Why dropping the first two?

As for the name, why not geological?

[Esteban82]

The first two are only from the 171 to 66.5 Ma.

66.5	242	250 140	74.0	242	250 140	; Maastrichtian
74.0	230	244	127	84.0	230	244	127	; Campanian
84.0	179	222	83	88.0	179	222	83	; Santonian
88.0	204	233	104	89.0	204	233	104	; Coniacian
89.0	191	227	93	92.0	191	227	93	; Turonian
92.0	179	222	83	96.0	179	222	83	; Cenomanian
# 96.0	140	205	87	; Lower Cretaceous
96.0	204	234	151	108.0	204	234	151	; Albian
108.0 	191	228	138	113.0	191	228	138	; Aptian
113.0	179	223	127	116.5	179	223	127	; Barremian
116.5	166	217	117	121.0	166	217	117	; Hauterivian
121.0	153	211	106	128.0	153	211	106	; Valangian
128.0 	140	205	96	131.0 	140	205	96	; Ryazanian
# 131.0	52	178	201	;Jurassic 
# 131.0	179	227	238 	; Upper Jurassic 
131.0	217	241	247	136.0	217	241	247	; Volgian
136.0	204	236	244	145.0	204	236	244	; Kimmeridgian
145.0	191	231	241	152.0	191	231	241	; Oxfordian	
# 152.0	128	207	216	; Middle Jurassic 
152.0	191	231	229	157.0	191	231	229	; Callovian	
157.0	179	226	227	165.0	179	226	227	; Bathonian	
165.0	166	221	224	171.0	166	221	224	; Bajocian	
171.0	154	217	221	179.0	154	217	221	; Aalenian 
B	black

[Esteban82]

I think the question is whether we want to provide just one for the example or more than one so that they are available.

If we are only going to use one, then geological could be it. If there are more than one, then I think a more specific name would be better (such as eons, era, periods, epochs, ages).

I think we can start with a single CPT (with a specific name) and then add more later.

[joa-quim]

Well, I think we should add them all and keep the original names.

[Esteban82]

Ok, I agree. I will rename it.

[Esteban82]

I will mention Christian Heine (@chhei) to see if he has any comments.

[Esteban82]

I've just added all the CPS with its original names. It is ready for review.

[joa-quim]

They should be added to share\cpt\geological too.

[Esteban82]

They should be added to share\cpt\geological too.

ok, I will make a PR in the gmt repository.

[chhei]

Sorry folks - late to the discussion. Very much appreciate the inclusion of the geological time scale CPTs. I have a complete and updated CPT for the ICS Geological time scale v2022v2 which I can contribute. Indeed the earlier ones were not complete sets and limited to an older version of the timescale.

Am currently out of office but can provide the files towards ea Sept. As naming convention I suggest to use <timescale acronym>_<level>.cpt where timescale acronym is something like ICS-GTS2022v2 that identifies the timescale origin (one example) and level to be that of the chronostratigraphic/geochronologic unit (e.g. Erathem`Era, Stage/Ageetc) so that we end up with something likeICS-GTS2022v2_Stage.cpt`. Happy to change if that is deemed to long/cumbersome.

[Esteban82]

Great @chhei. I think we can wait for your new CPTs.

[Esteban82]

Hi @chhei! Just a friendly ping to check if you could share the updated CPTs when you get a chance.

[chhei]

@Esteban82 - apologies - yes: feel free to copy those from my repository here: https://code.paleoearthlabs.org/geotimecpts/

The current version includes the full GTS 2022v2 plus some updates to the older files which make naming and header more consistent. I've released these under GNU GPLv3. Pls let me know whether there are issues re the licenses and also pls feed back any suggestions re naming/directory setup etc.

[Esteban82]

Thanks @chhei !!

[joa-quim]

Thank you Christian. But regarding the license I am a bit confused. If it was code, we could not accept a GPL licensed one, but for a text file (that's what CPTs are) I confess that I do not see the implications of a GPL license. It would be simpler if they were licensed with a Creative Commons license like those in cpt-city.

[chhei]

@joa-quim - there is also some code associated with the repo hence the choice. However, agree with your point that a CC license is overall better suited for the cpts. Will change.

[joa-quim]

Thanks for the explanation ... and the change :)

And, BTW, I had troubles with the site. It permanently loops on Checking to see if you are a robot... When it finishes and shows the Press OK to continue, it goes back to the checking step.

[chhei]

Thanks for the explanation ... and the change :)

No worries.

And, BTW, I had troubles with the site. It permanently loops on Checking to see if you are a robot... When it finishes and shows the Press OK to continue, it goes back to the checking step.

yes, same here. The new version of the Fossil SCM tool has a more aggressive bot defense. I've added a table at the front page which allows to directly access the directories with the CPT files in there. Pls try that. If that doesn't work, try accessing the files via the timeline to the commit/directory. I will look into the settings and see whether there's ways to change this behaviour.

[joa-quim]

Hmm, I can't manage to download files. Everywhere there is a download option it pops up that Checking to see if you are a robot... loop.

[chhei]

Argh - sorry about that. Please try again. I've now excluded the 'File' page in the settings. Worked for me in private broswer (FF) and TOR and also from corporate network (MS Edge).

[joa-quim]

Yep, it works fine now (but the two CPTs under ICS_GTS2004 are still GPL'd)

[chhei]

Thanks @joa-quim - license on cpts should be fixed now. In terms of issues with downloads, there's also a downstream mirror at Sourcehut.