Repository navigation
MNT: Update IERS A URLs due to USNO prolonged maintenance - #9443
Conversation
as suggested by @eteq.
|
I don't think it needs a changelog, but can always add one at the time of release. |
|
Is USNO the canonical source of the numbers? If yes, we might indeed want to revisit. If they are not, and just one of the equal sources, then we don't even need to revisit. IMO. |
|
(Well, I've added the label, but anyone having an opinion on it, please remove it. Maybe even it's an internal detail we need to mention in the changelog as older release might complain about the non working url 🤷♀ ) |
|
Re: canonical source -- USNO might actually be canon, if I interpreted https://www.iers.org/IERS/EN/Publications/Bulletins/bulletins.html correctly. |
|
My understanding is that USNO is the canonical source. |
|
OK, so I go ahead and merge this now. Thank you @pllim! |
MNT: Update IERS A URLs due to USNO prolonged maintenance
|
@bsipocz Is there any word on whether there's going to be a new release with this fix in it anytime soon? We are starting to be significantly limited by this. |
|
yes, hopefully the weekend or early next week will be 2.0.16 and 3.2.3. It'll take time though to propagate the releases through conda, etc. |
MNT: Update IERS A URLs due to USNO prolonged maintenance
|
To leave a bit more info here: I have asked USNO and they confirmed the "canonical backup" is the CDDIS server. At least for me the CDDIS server is much faster than the IERS one. So I'm going to try swapping the two in a follow-on PR. |
|
@eteq - I've quite at the end of doing the release. So even if you switch the URLs, not it really must be 4.0 only. |
Description
This pull request is to address the impending prolonged USNO downtime, causing current IERS A table to be inaccessible unless we switch the URLs (the main one and its mirror) to non-USNO service providers.
Fixes #9427
p.s. I don't know how to put in a change log since this needs to be backported to 2.x, so it wouldn't make sense for me to insert the change log under 4.0? Do we even need a change log?
p.p.s. Do we need a follow up issue to revisit the URLs after April 2020?
cc @bhazelton and @bmorris3