OB.DAAC file_search Utility Now Requires More Specificity

In order to prevent the kinds of large queries that were causing the database to fail by attempting to return everything to the user, the OB.DAAC file_search utility now requires a certain degree of specificity when sending requests, otherwise it will reject the request. For example, this query fails:

curl -s -d "sdate=2026-06-22&search=PM1ATTNR_NRT.A*.*.061&results_as_file=1" https://oceandata.sci.gsfc.nasa.gov/api/file_search

But these queries succeed:

curl -s -d "sdate=2026-06-22&edate=2026-06-26&dtid=512&search=PM1ATTNR_NRT.A*.*.061&results_as_file=1" https://oceandata.sci.gsfc.nasa.gov/api/file_search
curl -s -d "sdate=2026-06-22&edate=2026-06-26&sensor=AQUA&search=PM1ATTNR_NRT.A*.*.061&results_as_file=1" https://oceandata.sci.gsfc.nasa.gov/api/file_search
curl -s -d "sdate=2026-06-22&sensor=AQUA&search=PM1ATTNR_NRT.A*.*.061&results_as_file=1" https://oceandata.sci.gsfc.nasa.gov/api/file_search

This is because the last three queries provide those additional arguments.