ioos / colocate

Co-locate oceanographic data by establishing constraints
MIT License
5 stars 9 forks source link

Investigate headers for erddap requests #20

Open MathewBiddle opened 3 years ago

MathewBiddle commented 3 years ago

Sometimes we get false negative returns on the search. The script says there is no data, but in fact, there is. @mwengren proposed investigating the headers assigned at:

https://github.com/oceanhackweek/ohw19-project-co_locators/blob/cdf02cde50f2183901962893ef2b26baba103077/colocate/erddap_query.py#L10-L13

For example, the function says no data exists at this endpoint: https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_682074.csv?latitude,longitude&time%3E=1327622400.0&time%3C=1577750400.0&longitude%3E=-123.628173&longitude%3C=-122.02382599999999&latitude%3E=47.25972200000001&latitude%3C=48.32253399999999&distinct()

When it does: https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_682074.htmlTable?latitude,longitude&time%3E=1327622400.0&time%3C=1577750400.0&longitude%3E=-123.628173&longitude%3C=-122.02382599999999&latitude%3E=47.25972200000001&latitude%3C=48.32253399999999&distinct()