Open rsignell-usgs opened 6 years ago
This appears to be a UFrame issue as no datasets have updated since Saturday, December 9. I will look into it deeper tomorrow and get back to you with an update.
ping @jhtrowbridge
@kerfoot kerfoot , looks like this has been fixed?
An advanced search for data in the last day now returns 276 datasets: https://erddap-uncabled.oceanobservatories.org/uncabled/erddap/search/advanced.html?page=1&itemsPerPage=1000&searchFor=&protocol=%28ANY%29&cdm_data_type=%28ANY%29&institution=%28ANY%29&ioos_category=%28ANY%29&keywords=%28ANY%29&long_name=%28ANY%29&standard_name=%28ANY%29&variableName=%28ANY%29&maxLat=&minLon=&maxLon=&minLat=&minTime=2017-12-28&maxTime=
a query for all the data in the last day from this Pioneer profiler:
indicates the most recent data for this dataset on ERDDAP is about 15-16 hours old.
@kerfoot , is that the expected lag time?
@rsignell-usgs The last record for this instrument that has been ingested by UFrame is from 2017-12-2819:39:17Z. The last record available on ERDDAP is from 2017-12-2819:39:17Z. So this data set is up to date. I don't have any way to check the raw data to see if this is an ingest issue or telemetry issue. Can't say whether it's "expected" or not, but the dataset is up to date with respect to what has been ingested.
@kerfoot, This search for
sea_water_temperature
in the last week returned nothing. https://erddap-uncabled.oceanobservatories.org/uncabled/erddap/search/advanced.html?page=1&itemsPerPage=1000&searchFor=&protocol=%28ANY%29&cdm_data_type=%28ANY%29&institution=%28ANY%29&ioos_category=%28ANY%29&keywords=%28ANY%29&long_name=%28ANY%29&standard_name=sea_water_temperature&variableName=%28ANY%29&maxLat=&minLon=&maxLon=&minLat=&minTime=2017-12-04&maxTime=What is the ETA for having data delivered on ERDDAP with latency less than 12 hours?