OpenCV.projectPoints input type are confusing (maybe incorrect?)

[tomerarnon]

OpenCV documentation for projectPoints describes all of the InputArray parameters as vectors or matrices. This agrees with how I see the function used by others in python from cv2.
The julia type signature of OpenCV.projectPoints requires AbstractArray{T, 3} for all of these, and it's not clear why these extra dimensions are needed or how they will be handled. This is the signature listed by methods(projectPoints):

projectPoints(objectPoints::Union{OpenCV.CxxMat, AbstractArray{T, 3} where T<:Union{Float32, Float64, Int16, Int32, Int8, UInt16, UInt8}},
              rvec::Union{OpenCV.CxxMat, AbstractArray{T, 3} where T<:Union{Float32, Float64, Int16, Int32, Int8, UInt16, UInt8}},
              tvec::Union{OpenCV.CxxMat, AbstractArray{T, 3} where T<:Union{Float32, Float64, Int16, Int32, Int8, UInt16, UInt8}},
              cameraMatrix::Union{OpenCV.CxxMat, AbstractArray{T, 3} where T<:Union{Float32, Float64, Int16, Int32, Int8, UInt16, UInt8}},
              distCoeffs::Union{OpenCV.CxxMat, AbstractArray{T, 3} where T<:Union{Float32, Float64, Int16, Int32, Int8, UInt16, UInt8}}
              ; imagePoints, jacobian, aspectRatio)

[yakir12]

I came here for similar reason but specifically for the arguments of calibrateCamera.

Can you please post an example of a correct instance of the arguments for projectPoints or calibrateCamera?

I can't even seem to be able to create anything that fits the objectPoints::Union{OpenCV.CxxMat, AbstractArray{T, 3} where T<:Union{Float32, Float64, Int16, Int32, Int8, UInt16, UInt8}} "bill"...