opengeospatial / opengeospatial/timeseriesML

TimeseriesMetadata CommentBlock addition

Open
#29 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

To be implemented
Dominant language
No language data
Stars
2
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Under one of the XML Encoding updates, a DataType CommentBlock was added to TimeseriesMetadata in order to add detail to specific subsections of the timeseries (defined by the applicablePeriod:TM_Period

Image

I also found a comment from Paul in the doc:

In order to accommodate metadata applicable to an irregularly spaced whole timeseries for Domain- Range encoding, an amendment to increase the cardinality of timeseriesMetadata from "1" to "unbounded" has been added to timeseriesDR.xsd.

The amendment allows for dividing the entire irregularly spaced timeseries with different time spacings into segments that do contain regularly spaced time steps. Metadata can then be used to describe each of these individual segments.

With that requirement in mind, I'm wondering if it wouldn't make sense to remodel by merging the concepts from CommentBlock into TimeseriesMetadata, up the cardinality from TVP to "unbounded" as described for DR.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the existing TimeseriesMetadata and CommentBlock definitions from the XML Encoding updates, along with the timeseriesDR.xsd amendment that raises timeseriesMetadata cardinality to unbounded. Compare how applicablePeriod and irregularly spaced segments are represented, then seek agreement on the model; done means the merged structure and cardinality are clearly specified.

Written by the indexing model from the issue text.

Assessment

Tech stack
xml
Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.