Skip to content

fix UHSLC retrieval testcase #1178

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

Open
veenstrajelmer opened this issue May 1, 2025 · 0 comments
Open

fix UHSLC retrieval testcase #1178

veenstrajelmer opened this issue May 1, 2025 · 0 comments

Comments

@veenstrajelmer
Copy link
Collaborator

veenstrajelmer commented May 1, 2025

It seems there is something wrong on the server side, the following error is raised when retrieving uhslc_id=3 (or 1 to 5):

HTTPError: Error {
code=404;
message="Not Found: Your query produced no matching results. (uhslc_id=3 is outside of the variable's actual_range: 6 to 915)";
}

According to the legacy data portal, there is a station 3 (Baltra) present that has data in the requested period.

The code to reproduce:

import pandas as pd
from erddapy import ERDDAP
# method from https://ioos.github.io/erddapy/ and [https://ioos.github.io/erddapy/02-extras-output.html#](https://ioos.github.io/erddapy/02-extras-output.html)
# setup server connection, this takes no time so does not have to be cached
server = "https://uhslc.soest.hawaii.edu/erddap"
e = ERDDAP(server=server, protocol="tabledap", response="nc") #opendap is way slower than nc/csv/html
e.dataset_id = 'global_hourly_rqds'
# set erddap constraints
e.constraints = {}
e.constraints["uhslc_id="] = 3
e.constraints["time>="] = pd.Timestamp('2018-01-01')
e.constraints["time<="] = pd.Timestamp('2018-02-01')
ds = e.to_xarray()

Additional information
When I change to uhlsc_id=6, I get an error that makes sense since Enewetok does not contain data in the requested period:

HTTPError: Error {
code=404;
message="Not Found: Your query produced no matching results. (nRows = 0)";
}

When I change to uhslc_id=7, there is data retrieved as expected, no error is raised.

Approach
2025-05-01: Emailed UHSLC maintainers to ask if they could check their system, it seems that the actual_range is incorrect.

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

No branches or pull requests

1 participant