You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
A format for this was developed in the CCS project. It was even given a
name, Open Vehicle Data Set, OVDS. It is found in the OVDS directory at
https://github.com/COVESA/ccs-components
BR
Ulf
On Wed, May 3, 2023, 09:52 Erik Jaegervall ***@***.***> wrote:
*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 <https://github.com/UlfBj> @SebastianSchildt
<https://github.com/SebastianSchildt> @adobekan
<https://github.com/adobekan> @slawr <https://github.com/slawr> @paulboyes
<https://github.com/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"
—
Reply to this email directly, view it on GitHub
<#17>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJERQQJHOSZBHCJMQTICJ3DXEIFCLANCNFSM6AAAAAAXUBEDNQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
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
The text was updated successfully, but these errors were encountered: