Day 4: Future plans

The following is a list of possible changes for version 1.0, to be voted on (and added to) during the training course:

Language additions

  • Missing StationXML subelements

    • comments: id and subject

    • stage/filter ‘offset’ field?

    • …

  • non-linear drift processing element

    • decide format

  • Add option for GFZ-style permanent references?

    • <gfz:Identifier type=’hdl’>10881/sensor.a7561d1a-d518-475d-9733-30370432996c</gfz:Identifier>”)

    • Are ”identifiers” (in station, network and channel) and “resource_id” (in Equipment) sufficient?

  • allow calibration_dates in stage as well as in equipment?

    • stage files are where the changed parameters are kept

    • Could cause confusion/duplication. Also, how would we handle multi-stage calibrations? (dataloggers, …)

  • Add filter shortcuts?

    • Geophone, IIR, SYNC, RC …

Language changes

  • Make StationXML relation clearer (but break AROL compatibility)

    • StationXML element names => CamelCase?

    • Use FilterType as key rather than ”filter” + key?

      • Could simplify code

  • remove start_sync_instrument from timing_base and put in non-base elements? If not specified, defaults to the same value as start_sync_reference

  • un-require station:site? Required in StationXML but not always useful for OBS deployments

  • Change

    orientation:
    <code>:
        azimuth.deg:
        dip.deg:

    to

     orientation:
     code: ""
     azimuth.deg:
     dip.deg:

- Would be clearer, but do we need to allow multiple orientation codes
  (e.g., “1” and “N”)?

  • How to specify replacing rather than updating? Current solution is “^” prefix character.

    • Do we need a prefix character? Or could we automatically replace in specific situations?:

      • channel_definition

      • change of datalogger, sensor, or preamplifier base

    • Should it be generalized to other places? It is only in channel-modifications for now

    • Is “^” the best character?

Other

  • New command-line tools?

    • obsinfo-configurations: Print out all configurations available in a file, a directory, or a directory and its subdirectories

    • obsinfo-plot: plot station maps or instrument responses

      • instrumentation and below: frequency responses and impulse responses

      • subnetwork: station map, possibly with one frequency response per instrumentation type?

      • person, operator, network, timing, location: nothing

    • obsinfo-makeLibrary: make NRL or AROL libraries from instrumentation database.

  • Documentation

    • Add information file reference (imitate StationXML Reference)