Hi Fabian, hi Philipp,
good to see that development of QuakeML is still active! However, I have
some critical comments:
A) I find it extremely hard to keep track of changes introduced in
recent times. You mention bugfixes and clean-up to elements of QuakeML
1.2.. where can I find a list of changes?
B) Is the version control system to keep track of changes publicly
visible somewhere? I would strongly encourage to have some sort of
schema file (probably rather RelaxNG than XSD, see earlier pro…
[more]
Dear fdsn-wg2,
currently, the working group is discussing several minor updates to the stationXML specification. The proposals aim at fixing some issues; however, notable structural shortcomings of the base fdsn stationXML 1.0 [1] as well as in the "station availability" extension are not addressed.
While of the current proposals aim at homogenizing the representation of similar concepts [2], others increase the heterogeneity of the representation of similar information [3].
Further, sever…
[more]
Hello WG2,
The schema modification for the approved by WGII (www.fdsn.org/wgIII/V1.0-21Jul2014-DOIFDSN.pdf <http://www.fdsn.org/wgIII/V1.0-21Jul2014-DOIFDSN.pdf>) has been implemented and is ready for technical review.
Reinoud, I suggest a two week deadline for this review.
The Github pull request is here:
https://github.com/FDSN/StationXML/pull/3 <https://github.com/FDSN/StationXML/pull/3>
A direct view of the changes is here:
https://github.com/FDSN/StationXML/pull/3/files <https://git…
[more]
Hello WG-II,
As requested at the 2015 working group meeting, below are StationXML changes proposed by the IRIS DMC.
If approved by the WG, the DMC will prepare a modified schema for technical review through a pull request on Github.
regards,
Chad
IRIS DMC
Proposed StationXML changes from the IRIS DMC:
1) Allow the Station::CreationDate element to be optional.
Rationale: This value denotes when a station/site was originally installed and is distinct from the startDate attribute used to no…
[more]
...new subject line to keep separate proposals separate...
Hi
Seems like a good idea to me. Perhaps the DOI working group should create a
github pull request?
thanks,
PHilip
On Mon, Jul 20, 2015 at 12:38 AM, Catherine Pequegnat <
Catherine.Pequegnat@ujf-grenoble.fr> wrote:
> Good morning,
>
> The working group DOI for FDSN network has recommended the mention of the
> PID in stationXML
> cf www.fdsn.org/wgIII/V1.0-21Jul2014-DOIFDSN.pdf
> (p12)
>
> Could this extension be part of the next st…
[more]
...new subject line to keep separate proposals separate...
Hi
I feel it would be ok to add Vault and Geology to Channel, with
documentation that says that if it is specified in both Station and Channel
then the Channel takes precedence. Having it in both places would allow
backwards compatibility and allow the majority of stations where these are
common to only specify it once.
thanks
Philip
On Mon, Jul 20, 2015 at 12:32 AM, Catherine Pequegnat <
Catherine.Pequegnat@ujf-grenoble.fr> wrote:
…
[more]
Hi
I have another proposal to update FDSN StationXML and wanted to toss it
out.
1) Change NumeratorCoefficient in FIRType to use attribute "number" instead
of "i" and add attribute "number" to Numerator and Demoninator in
CoefficientsType.
Currently
PoleZero in PolesZerosType are numbered with "number",
NumeratorCoeffiecient is numbered in FIRType with "i",
Numerator and Demoninator are not numbered in CoefficientsType,
Coefficient is numbered with "number" in PolynomialType
It would be nic…
[more]
Hello WG II,
This email is to gather parties interested in a JSON representation of important (core) FDSN station metadata. The intention is a develop a schema with all interested parties and jointly propose it to WG II as an FDSN format and to WG III for support in fdsnws-station as an output format.
If you would like to be included in pre-proposal discussions please let me know by 24 July. Alternatively, you can contribute to the discussion through Github project issues.
IRIS has develo…
[more]