Open
Description
Describe the feature
There are a lot of different timestamps in OSI:
- Common Timestamp: https://opensimulationinterface.github.io/osi-antora-generator/asamosi/latest/gen/structosi3_1_1Timestamp.html
- SensorView: https://opensimulationinterface.github.io/osi-antora-generator/asamosi/latest/gen/structosi3_1_1SensorView.html#ad30bef352de1b64dd211718c18c540f1
- SensorData::timestamp: https://opensimulationinterface.github.io/osi-antora-generator/asamosi/latest/gen/structosi3_1_1SensorData.html#a82adb4a7724d1e4835ae0921fab4080c
- SensorData::last_measurement_time: https://opensimulationinterface.github.io/osi-antora-generator/asamosi/latest/gen/structosi3_1_1SensorData.html#a9baaaa40491c5f241c117a7dacbe0d9d
- SensorData::system_time: https://opensimulationinterface.github.io/osi-antora-generator/asamosi/latest/gen/structosi3_1_1SensorData.html#ae64496913ffa0c41f154260cf48725e6
- SensorDetectionHeader::measurement_time: https://opensimulationinterface.github.io/osi-antora-generator/asamosi/latest/gen/structosi3_1_1SensorDetectionHeader.html#a7276bbdf40b2da4fed4397df62f167aa
It a bit hard to grasp the extent of the possibilities for timing information in OSI.
Describe the solution you would like
A dedicated page in the documentation explaining timing in OSI would be great. This could be done similarly to the coordinate systems page.
Describe alternatives you have considered
Everyone is confused on nobody uses timing is OSI correctly.
Describe the backwards compatibility
Only documentation, so no backwards compatibility issues.
Metadata
Metadata
Assignees
Labels
No labels