opengeospatial / opengeospatial/timeseriesML

TimeSeries result types

Open
#28 2 comments 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

Stupid smart question - in the TSML doc (7.5), there's a list of potential result types (measures, categories, vectors and composite)
Apart from the fact that I struggle between vector and composite (partially because the vector example is bad, wind speed and direction are very different concepts), I wonder if we want to introduce such a limitation on result types. To my view, other result types would be just as valid, e.g. images

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

Start with section 7.5 of the TSML document and review the listed result types, especially vector and composite. Clarify whether the result-type list is intended to be exhaustive and how additional types such as images should be represented; done means the specification direction and resulting documentation changes are agreed.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.