-
Notifications
You must be signed in to change notification settings - Fork 21
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
add frame_id to RawImage, CompressedImage, and CameraCalibration #61
Conversation
src/schemas.ts
Outdated
name: "frame_id", | ||
type: { type: "primitive", name: "string" }, | ||
description: | ||
"Frame of reference for the camera. The origin of the frame is the optical center of the camera. +x points to the right in the image, +y points down, and +z points into the plane of the image.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it worth calling out that CameraCalibration should be in the same frame as its corresponding image? What happens if the CameraCalibration is a different frame?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No idea really. Probably bad things.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems reasonable. Might be worth thinking through:
foxglove/studio#4323 (comment)
And whether there are other useful or common ways of tying cameras to calibration data and/or frames.
Public-Facing Changes
Added
frame_id
to RawImage, CompressedImage, and CameraCalibrationDescription
Closes #59
Unblocks foxglove/studio#4323