Azure Kinect DK NotEnoughSpatialData about azure_spatial_anchors_ros

[soeroesg]

one reason can be that the ASA library cannot look up the poses of the images in the TF because the timestamps of the images and poses are different. check that the timestamps of the images and the corresponding poses are the same (or very close to each other) and try to increase tf_lookup_timeout in the launchfile

Also check the same with the camera_info, and try passing use_approx_sync_policy:=true

[159chenJie159]

Did you fix the error, I also encountered this error using Realense's D435 camera, D435 has no imu.And I also used image proc to get the undistorted grayscale images. I don't know exactly how this problem came about, whether it was my setting up wrong "world_frame_id" or "camera_frame_id".

[EricVoll]

Hi @JaVo93
Not enough spatial data is an error that usually is returned when the device hasn't uploaded enough data yet: link

So the solution should be relatively easy - just collect more view points before attempting to create an anchor. Does that solve the problem?