LP DAAC - afriesz wrote:
> @timothy.w.hilton,
>
> When I paste the URL you provided directly into the browser, I get a 400 error as
> well. This is because the characters in the parameters you are passing (everything
> after the ?) need to be encoded. Try this URL >
> https://opendap.cr.usgs.gov/opendap/hyrax/MOD13Q1.061/h29v13.ncml.ascii?time%5B2:1:10%5D
>
> Note that the brackets around the time start:step:end are now using HTML URL
> encoding.
OK, this sheds some light on it. Many thanks for this piece of information.
> If you were using a client of some sort, this would be done for you. I'm assuming you
> are pasting the URL directly into the browser.
I tried both wget (`wget --user timothy.w.hilton --ask-password https://opendap.cr.usgs.gov/opendap/hyrax/MOD13Q1.061/h29v13.ncml.ascii?time[2:1:10]`) as well as pasting into a browser, and got 400 from both methods. I notice now that the URL with the brackets works using the Python requests module; it must substitute the characters internally.
> Another think to note with the OPeNDAP endpoint you are hitting. The endpoint
> provides access to the full timeseries from one endpoint, but you are not able to
> request the full timeseries in a single request. If you request the full timeseries
> you will receive an error resulting from a timeout that occurs when you make such a
> request. We will need to consider submitting multiple requests for the timeseries.
> I've had some success with about 100 time steps within a request, but you'll need to
> play around with that to see what consistently works for your workflow.
Noted, thanks. I'm breaking up the files for the actual data downloads. The URL above was simply requesting the timestamps so I could figure out which files I needed.
> @timothy.w.hilton,
>
> When I paste the URL you provided directly into the browser, I get a 400 error as
> well. This is because the characters in the parameters you are passing (everything
> after the ?) need to be encoded. Try this URL >
> https://opendap.cr.usgs.gov/opendap/hyrax/MOD13Q1.061/h29v13.ncml.ascii?time%5B2:1:10%5D
>
> Note that the brackets around the time start:step:end are now using HTML URL
> encoding.
OK, this sheds some light on it. Many thanks for this piece of information.
> If you were using a client of some sort, this would be done for you. I'm assuming you
> are pasting the URL directly into the browser.
I tried both wget (`wget --user timothy.w.hilton --ask-password https://opendap.cr.usgs.gov/opendap/hyrax/MOD13Q1.061/h29v13.ncml.ascii?time[2:1:10]`) as well as pasting into a browser, and got 400 from both methods. I notice now that the URL with the brackets works using the Python requests module; it must substitute the characters internally.
> Another think to note with the OPeNDAP endpoint you are hitting. The endpoint
> provides access to the full timeseries from one endpoint, but you are not able to
> request the full timeseries in a single request. If you request the full timeseries
> you will receive an error resulting from a timeout that occurs when you make such a
> request. We will need to consider submitting multiple requests for the timeseries.
> I've had some success with about 100 time steps within a request, but you'll need to
> play around with that to see what consistently works for your workflow.
Noted, thanks. I'm breaking up the files for the actual data downloads. The URL above was simply requesting the timestamps so I could figure out which files I needed.
Statistics: Posted by timothy.w.hilton — Wed Dec 20, 2023 8:38 pm America/New_York