augmented-reality

The iOS 12 application now allows us to create an ARReferenceObject , and using it, can reliably recognize a position and orientation of real-world object. We can also save the finished .arobject file. But : ARReferenceObject contains only the spatial features information needed for ARKit to recognize the real-world object, and is not a displayable 3D reconstruction of that object. sceneView.session.createReferenceObject(transform: simd_float4x4, center: simd_float3, extent: simd_float3) { (ARReferenceObject?, Error?) in // code } func export(to url: URL, previewImage: UIImage?) throws { } Is

I have an application of augmented reality in which I have stored information such us metro, gas stations, places of interest, etc. with the corresponding latitude and longitude. Now, according to the orientation of the device, I would show a marker for each site in the camera view of the device. Similar to Layar and Wikitude. It takes three days searching without stopping and have not found anyone to explain how to solve this problem. Since information on this topic is very sparse, and I recently solved this problem on the iPhone, I thought I would share my method for anyone that can make it

ARKit 2.0 updates many intrinsic (and extrinsic) parameters of the ARCamera from frame to frame. I'd like to know if it also takes Radial Lens Distortion into consideration (like in AVCameraCalibrationData class that ARKit doesn't use), and fix the video frames' distortion appropriately ( distort / undistort operations) for back iPhone and iPad cameras? var intrinsics: simd_float3x3 { get } As we all know, the Radial Lens Distortion greatly affects the 6 DOF pose estimation accuracy when we place undistorted 3D objects in distorted by a lens real world scene. var lensDistortionLookupTable:

I've read all Apple guides about ARKit , and watched a WWDC video . But I can't understand how do coordinate systems which are bind to: A real world A device A 3D scene connect to each other. I can add an object, for example a SCNPlane : let stripe = SCNPlane(width: 0.005, height: 0.1) let stripeNode = SCNNode(geometry: stripe) scene.rootNode.addChildNode(stripeNode) This will produce a white stripe, which will be oriented vertically, no matter how the device will be oriented at that moment. That means the coordinate system is somehow bound to the gravity! But if I try to print upAxis

I've recently implemented Perspective Transform in OpenCV to my app in Android . Almost everything works without issues but one aspect needs much more work to be done. The problem is that I do not know how to count the right aspect ratio of the destination image of Perspective Transform (it does not have to be set manually), so that it could count the aspect ratio of the image to the size of the real thing/image despite the angle of a camera . Note that the starting coordinates do not form trapezoid, it does form a quadrangle. If I have a photograph of a book taken from approximately 45

i'am trying to build a simple Augmented Reality App, so I start working with sensor Data. According to this thread ( Android compass example ) and example ( http://www.codingforandroid.com/2011/01/using-orientation-sensors-simple.html ), the calculation of the orientation using the Sensor.TYPE_ACCELEROMETER and Sensor.TYPE_MAGNETIC_FIELD doesn't really fit. So I'm not able to get "good" values. The azimut values doesn't make any sense at all, so if I just move the Phone upside the value changes extremly. Even if I just rotate the phone, the values doesn't represent the phones orientation. Has