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

Clarify meaning of the "updatedafter" request parameter (or drop it) #9

Open
kaestli opened this issue May 25, 2023 · 0 comments
Open

Comments

@kaestli
Copy link

kaestli commented May 25, 2023

It seams that the processing of the updatedafter request parameter is not sufficiently defined. The standards document says only:
"Limit to metadata updated after specified time; updates are data center specific."
I would expect that if I set an updatedafter date, I receive some type of partial inventory response, including modified metadata, but excluding unmodified.

However,

  • it is not clear whether the modification date refers to the date when a real modification happened (e.g. when an epoch was closed and a new one opened) or whether it refers to the point in time when this modification was added in the metadata offerings of the service provider.
  • it is not clear how partial a response is: If the gain of a channel of a station of the CH network changed, would I receive a stationXML just containing a network element with a station element with a single, modified channel element, or a network element, with a station element containing modified as well as unmodified channels, or would I receive the entire network with all modified and unmodified stations (while not receiving another network, where no station and no channel was modified)
  • How is deletion of data handled?

The definition StationXML probably does not suggest obvious answers to these questions, as the format does actually not contain "last modified" dates; the information would need to be derived from other parts of the service providing infrastructure.

As a result I guess, at the time being, the standard does not ensure two fdsn/station service implementations to behave identically.

I would probably recommend to drop this parameter entirely, unless StationXML is extended with modification dates the updatedafter behavioural description can refer to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant