search

opengeospatial / CoverageJSON

Public repo for CoverageJSON project
Apache License 2.0
10 stars 8 forks source link

Clarifications to domain type specs #65

Closed jonblower closed 2 years ago

jonblower commented 2 years ago

Following development of the schema, we found that the text defining domain types needed some small clarifications

jonblower commented 2 years ago

@letmaik this should resolve https://github.com/covjson/covjson-validator/issues/28 (but I don't seem to be able to formally request a review from you)

jonblower commented 2 years ago

It should also resolve https://github.com/covjson/specification/issues/96

jonblower commented 2 years ago

@jonblower Is there a reason why the Trajectory and Section domain schemas have the t coordinate first? Not really technical, but x,y,z,t seems more conventional.

The t coordinate defines the natural ordering of the tuples, so we thought it made sense for this to be the first coordinate. It slightly improves human readability and is the most natural "primary key" for the coordinates (e.g. if you wanted to ingest the data into a database or DataFrame).

chris-little commented 2 years ago

Agreed at 2022-05-04 meeting to merge and close issue.