Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SDSS incorrect server link #2219

Closed
balashev opened this issue Nov 17, 2021 · 4 comments
Closed

SDSS incorrect server link #2219

balashev opened this issue Nov 17, 2021 · 4 comments
Labels

Comments

@balashev
Copy link

balashev commented Nov 17, 2021

Hello,

I encountered errors when trying to download quasar spectra using astroquery.sdss

It seems that broken links are generated when astroquery tries to download from sdss database, and "urllib.error.HTTPError: HTTP Error 404: Not Found" is generated.

For example, asking for (J130709.97+302818.71)

astroquery generates:
https://data.sdss.org/sas/dr14/boss/spectro/redux/v5_10_0/spectra/8276/spec-8276-57067-0092.fits,

while it should be
https://data.sdss.org/sas/dr14/eboss/spectro/redux/v5_10_0/spectra/8276/spec-8276-57067-0092.fits

where BOSS --> EBOSS.

The similar things are also happen for asking dr16 objects, either by coordinates or by plate-mjd-fiberID. For example, asking for SDSS.get_spectra(plate=9403,mjd=58018,fiberID=485) return None

Can anyone update the generation of the links in astroquery.SDSS to include the latest EBOSS releases?

@keflavich
Copy link
Contributor

this is solved by #2214 and is a duplicate of #1731.

@balashev
Copy link
Author

There is still a problem to load spectra from DR16 data release since it needs to add '/lite' of '/full' in the link address which is not supported by previous data releases.

@keflavich keflavich added the sdss label Nov 17, 2021
@keflavich
Copy link
Contributor

OK that sounds like potentially a new issue. I see in #2214 that /full is added, but /lite is not. @weaverba137 can you comment?

@keflavich keflavich reopened this Nov 17, 2021
@keflavich
Copy link
Contributor

Right, you've already commented on #2214 - let's keep discussion centralized there. I'm closing this again in favor of #2214 - we should handle both issues in one place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants