Skip to content
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

Support checking for and re-collecting updated data #51

Open
chad-earthscope opened this issue Oct 13, 2018 · 0 comments
Open

Support checking for and re-collecting updated data #51

chad-earthscope opened this issue Oct 13, 2018 · 0 comments
Labels
enhancement New feature or request

Comments

@chad-earthscope
Copy link
Contributor

As of 0.0.6, updated data is not checked for.

Rover could use showlastupdate=true in the call to the availability service, which will then result in a most-recent-update update column to be included in the response. This date-time value should be compared to the updated date-time value in the local index to determine whether the local copy is the latest. These data should then be replaced.

How to replace data. Data could be replaced at the station-day granularity (potentially re-downloading channels that have not been updated); basically re-fetching all data in for the given station-day according to the subscription/request, replacing the station-day file and re-indexing it.

Another option, have rover carve out the data that needs to be replaced based on the byte ranges in the index (no miniSEED parsing needed) and re-refetching just the updated channels that are then appended to the station-day file per a normal retrieve. This cold leverage the "data removal" functionality in #21.

@chad-earthscope chad-earthscope added the enhancement New feature or request label Apr 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant