search

FDSN / SeedLink

https://docs.fdsn.org/projects/seedlink/
Creative Commons Zero v1.0 Universal
1 stars 1 forks source link

Suggestion: be explicit on how custom Source Identifiers are handled #3

Closed luca-s closed 9 months ago

luca-s commented 2 years ago

I have one suggestion regarding the paragraph "Station ID and streamID". In there the expected station ID and stream ID format is discussed (NET_STA and LOC_B_S_SS). I would suggest to add a sentence that explains how to deal with custom source identifiers that do not follow the FDSN format. For example, stating that custom (that do not follow the format) source identifiers are not supported would suffice.

andres-h commented 1 year ago

Feedback from proposal team

The protocol specification should not place requirements on station and stream IDs. Contrary to the suggestion in the ticket, we should explicitly state that these are agnostic to other standards, and the miniSEED identifiers are the expected use case with those data payloads but that others may be used in the future, or within closed ecosystems.

Change of specification

Add extended explanation to “Station ID and stream ID”.

crotwell commented 10 months ago

+1 on proposed change.