Have a complete list of global tide gauge locations

[jetesdal]

The current global tide gauge file in momlevel only includes a subset of locations. Having access to a complete list of global tide gauge locations would allow for more comprehensive analysis and comparisons with GFDL models.

A first step would be to take the location.lst file that is available in FACTS and convert it to the same format as the existing csv file in resources. The location.lst file only includes information for PSMSL_site, PSMSLID, lat, and lon, so the missing information (Country, NOAA_name, NOAAID) would need to be filled in or left blank. Another option could be to retrieve the table from the PSMSL webpage.

[clittleaer]

Hi Jan-Erik -- I've done this using a matlab script to read PSMSL data (provided by PSMSL) and spit out a .csv file, that is then read into python and can be used with momlevel extraction tools. what's the best way to bring this capability into momlevel? a new csv file, or the matlab code with the tide gauge data? (I also have some tide gauge processing scripts in python i'm eventually planning to bring into momlevel).

*note that this brings in the tide gauge time series data, which may be more than you're looking to do here if you just want to locations

[jetesdal]

Hi @clittleaer! Thank you for your input! Having momlevel the capability to retrieve tide gauge time series data sounds exciting. I think this would be a great addition to the momlevel repository, but I have to defer to @jkrasting if this will be in the scope of momlevel.

In terms of the current issue, I was thinking of just having a csv file that includes all tide gauge locations with the following header: Country, PSMSL_site, NOAA_name, PSMSLID, NOAAID, lat, lon. These are the required fields that momlevel.extract_tidegauge() expects.

A table with this information is available on the PSMSL website (https://psmsl.org/data/obtaining/), but I couldn't find a downloadable version of the table. I am currently working on a python script that retrieves the table from the HTML source code and converts it to a csv table. I like your idea to have momlevel itself extract the data. Once I get the script working I can share it and we could think of how to implement it, if desired.

[jkrasting]

The current “global” file is meant to reflect tide gauge locations that were analyzed in IPCC AR6 and the SROC. Some of these sites pose an issue for model comparison as they are not all located directly on the coastline and might be set in embayments or upriver. Given this caveat, a new file containing all of the PSMSL locations would be useful and I think your strategy is a good one @jetesdal. Do you happen to know if the FACTS set of locations is identical to the complete PSMSL site list? Looping @bobkopp into the discussion.

@clittleaer - a set of routines to obtain and process the observed TG data would be awesome and is within the scope and spirit of momlevel. I recall the processing routines will make the observed tide gauge data more comparable to model output, correct?

To sum up,

1. A complete global csv list of PSMSL sites, FACTS sites, (or both) are needed in addition to the existing global file
2. An expanded set of global coastally-adjacent locations that are most comparable to model simulations is needed
3. Routines to obtain and process TG are within momlevel’s scope and will help with evaluating model simulations

[bobkopp]

The FACTS list will omit some shorter PSMSL records - I don’t remember what the cutoff was, but it probably was around 30 years minimum of data.

We do have a file in https://github.com/bobkopp/LocalizeSL/blob/master/IFILES/extremes/GPDfits_withunc.tsv that matches PSMSL and NOAA ids for a subset of tide gauges, if that’s useful.

[clittleaer]

thanks @jkrasting and @bobkopp! (hi Bob!) i guess it makes sense for me to learn about FACTS processing of tide gauge records, to figure out what's belongs within momlevel (e.g. with a target of model comparison/evaluation), and what overlaps with FACTS (with a target of sea level projections?). Bob, are the FACTS tide gauge analysis/processing code/modules designed or intended to be used outside of FACTS? Is FACTS public/open source yet?

Also, is this the right place to have the discussion (may be a little "OT" as my daughter would say)? If not, we can move to email!

[bobkopp]

Hi Chris!

FACTS is here: https://github.com/radical-collaboration/facts

And described here: https://egusphere.copernicus.org/preprints/2023/egusphere-2023-14/

[clittleaer]

Cool, Bob, congrats on getting the code up and paper submitted! That’s going to take a while for me to digest but I will dig in soon. Let me know if you’ve though about whether the tide gauge analysis code in there (which I assume involves some processing in order to get at the flood frequency distributions and VLM and maybe some other goals) is envisioned to be modular, and used outside the larger framework. I can make this question more specific after learning about what the code does so no rush if the answer is “it depends”. _Chris From: Bob Kopp ***@***.***> Date: Thursday, February 16, 2023 at 4:22 PM To: jkrasting/momlevel ***@***.***> Cc: Little, Christopher ***@***.***>, Mention ***@***.***> Subject: Re: [jkrasting/momlevel] Have a complete list of global tide gauge locations (Issue #50) Hi Chris! FACTS is here: https: //github. com/radical-collaboration/facts And described here: https: //egusphere. copernicus. org/preprints/2023/egusphere-2023-14/ — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving Hi Chris! FACTS is here: https://github.com/radical-collaboration/facts<https://urldefense.com/v3/__https:/github.com/radical-collaboration/facts__;!!CAFLEWIB!DpG4vx9ZCgeD0TnGfUZ2ELw1f3HYSsqb2qHL3W98rHTIwoLUwWzy4WHsgF_BsfSWM0hO9kbJXmfaMKalY8p9$> And described here: https://egusphere.copernicus.org/preprints/2023/egusphere-2023-14/<https://urldefense.com/v3/__https:/egusphere.copernicus.org/preprints/2023/egusphere-2023-14/__;!!CAFLEWIB!DpG4vx9ZCgeD0TnGfUZ2ELw1f3HYSsqb2qHL3W98rHTIwoLUwWzy4WHsgF_BsfSWM0hO9kbJXmfaMNxvD_G-$> — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/jkrasting/momlevel/issues/50*issuecomment-1433730733__;Iw!!CAFLEWIB!DpG4vx9ZCgeD0TnGfUZ2ELw1f3HYSsqb2qHL3W98rHTIwoLUwWzy4WHsgF_BsfSWM0hO9kbJXmfaMFQ54Vbu$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AS4ZBMIKX3WNCRZDWETNRYLWX2LBTANCNFSM6AAAAAAU4AFQSY__;!!CAFLEWIB!DpG4vx9ZCgeD0TnGfUZ2ELw1f3HYSsqb2qHL3W98rHTIwoLUwWzy4WHsgF_BsfSWM0hO9kbJXmfaMKzi1VdA$>. You are receiving this because you were mentioned.Message ID: ***@***.***>

…

________________________________ This email is intended solely for the recipient. It may contain privileged, proprietary or confidential information or material. If you are not the intended recipient, please delete this email and any attachments and notify the sender of the error.