Last version of Updated_Catalog might discard too many stations

[tomsail]

There is a problem in discarding stations that have same set of lat/lon or too close to each other.
Some - not exhaustive - reasons

1. some stations may have had multiple deployments over time, from the same or different providers and are identified with different names
2. some might have different ioc_codes but be the same station with different instruments (ex: sete and sete2).

https://github.com/oceanmodeling/seaset/blob/main/Notebooks/Updated_Catalog.ipynb

I suggest to:

• export a csv version of the table when obtaining the grouped_df dataframe --> for data retrieval purposes
• export a csv version at the end of the notebook like already implemented --> For modelling purposes

[tomsail]

Update on this: the same problem was seen when analyzing results from models and observed data from ioc_cleanup (for prin and prin2 stations)

Actions suggested:

• Drop the PR I initiated and restart from the official repo
• Provide a function create_seaset() to initiate a first version of the seaset catalog, without dropping any ioc_code. This function would have to be run only once to generate a reference catalog.
• Provide a functionupdate_seaset() to add new stations and attribute them a new unique provider, if not already present in the database.
• Provide a function id, dist = get_seaset_id(lat,lon) that return the N unique seaset ids for the coords entered and vice versa lat, lon = get_coords(id) that return coordinates for the seaset id returned.
• Order notebooks, scripts and functions in the correct directories

[pmav99]

Assuming that seaset is a GeoDataFrame (or at least a DataFrame with lon/lat columns), then we should think carefully which functions are really needed, because some of them are trivial to implement. For example get_coords(id) is just seaset[seaset.id==id].geometry or similar,