Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VSS storage format #17

Open
erikbosch opened this issue May 3, 2023 · 1 comment
Open

VSS storage format #17

erikbosch opened this issue May 3, 2023 · 1 comment

Comments

@erikbosch
Copy link
Collaborator

This topic originates from a mail from Tata

A guy from Tata asked for how to represent large set of data in VSS and how to validate it. We do not have any answers yet. Would it be interesting for COVESA to define a "reference storage format", in CSV, JSON, or whatever? That possibly could be used for data exchange and/or persistence.

This is a bit related to a topic that comes up now and then - if COVESA shall specify/recommend metadata in observations. For example it would be possible for us to define terms like "accuracy" and how to specify/interpret it which possibly also could be included. If COVESA would come up with a format we could possibly also add some (Python) tooling that validates that all data are aligned with the "current" VSS specification, like all signals exist and values are OK for the type.

FYI: @UlfBj @SebastianSchildt @adobekan @slawr @paulboyes

Signal, Value, Timestamp
Vehicle.Speed, 123.45, "2023-05-03 12:12:00 UTC"
Vehicle.Speed, 123.67, "2023-05-03 12:12:02 UTC"
@UlfBj
Copy link

UlfBj commented May 3, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants