Daily station specific RINEX files and spatial queries are not supported

[frigusgulo]

Stories:

As a user, I want to identify all stations within a given radius of a lat/lon position and download the RINEX files to my file system.

As a user, I want to identify what networks contain stations within a spatial query

As a user, I want to access station meta-data within a spatial query

As a user, I need to specify the rinex version in dependency specs and potentially the network.

As a developer, I want to seamlessly append networks to the catalog and keep api queries for specific networks seperate.

[GeorgeTownsendd]

Hi Frankie! I hope you're well.

I'm George, a student and user/contributor of the gnssrefl library: https://github.com/kristinemlarson/gnssrefl

GNSSommelier has the potential to replace a whole stack of code in gnssrefl. E.g. you have the functionality for most of the orbit downloads.

RINEX obs download support, as you have mentioned in this issue, would be a big win as well. Offloading orbs+rinex downloads to GNSSSommelier would make the codebase much cleaner and save >2000 LOC.

May I also ask if there is any timeline on support for GNSSommlier? Ideally gnssrefl could trust the dependancy in the ~longer term, because the main benefit would be reducing our own code churn.

See here my thread on the gnssrefl repo for this potential integration: kristinemlarson/gnssrefl#412

Thank you for maintaining the package! :)

Cheers

P.S. btw, an important use case for us is downloading 1-Hz RINEX data, often distributed in 15 minute files. We need these because sometimes the daily RINEX files do not contain the L2C observable.