Log in or register to post comments

Target Image Relation to 3D Image

April 29, 2013 - 12:55am #8

I am in the pre-investigation phase for my application and plan to use Vuforia.  I am missing the part where the 3D camera viewed object is associated with the target image.  I understand that a target image is uploaded to the cloud database and that this image should trigger a letter, scene, character or whatever, however where is the relation?

In an application with thousands of "relations," image targets and so forth, I would imagine that saving the related 3D image in the application would be bad since it would significantly increase the size of the App.

Target Image Relation to 3D Image

April 29, 2013 - 1:27am #7

Hi, when an image target is recognized by Cloud Reco (i.e. when a matching image target is found on the Cloud DB), the SDK returns a SearchResult with some information about the recognized image target, in particular:

- the target unique ID (this is a string which uniquely identifies the target)

- the target metadata (this is a string which can represent any kind of user-defined information; the metadata is typically uploaded together with the image target into the Cloud Database)

So, typically, an application can read the metadata of the recognized target, and build some 3D augmentation based on the content of such metadata; for example, the CloudReco sample, the metadata contains some basic info about a book; based on this, the application connectes to a Book data server (which is just a special server for the sample, but it is not part of the CloudReco feature per-se) and retrieves the Book data based on the input metadata.

Once the Book data are retrieved, the sample creates a texture and displays it on top of the target.

More in general, you can think of your target metadata as the place where you can put any kind of information that you consider useful for your application;

for example, a metadata may contain the URL of a video (so that you can trigger the playback of such video), or it may contain the name of 3D model in some format (for instance "my_building.OBJ") so that the application can load that specific model and put it on top of the target.

The possibilities are endless, due to the openness of the metadata to suit any kind of scenario.

 

 

Target Image Relation to 3D Image

April 29, 2013 - 1:36am #6

Perfect, so it sounds like the 2d target image is what is uploaded to the Cloud with the Meta data file.  This meta data file should contain the location to the related image which can be another server, url or what ever.  The last thing that should be constructed is the action of the App when it reads this meta data when it is passed to the device?

Sound like I got it?

Target Image Relation to 3D Image

April 29, 2013 - 1:38am #5

Yes, you got it right.

Target Image Relation to 3D Image

April 29, 2013 - 1:47am #4

One more thing please.  Is there a sample for the IOS which is retrieving data from your Cloud and then executing the metadata which is retrieved?

Target Image Relation to 3D Image

April 29, 2013 - 1:55am #3

Yes, you can look at the CloudReco sample on iOS.

Then, if you have iOS-specific questions, you can post them in this forum section:

https://developer.vuforia.com/forum/ar-technical-discussion/ios

Target Image Relation to 3D Image

April 29, 2013 - 2:17am #2

The CloudReco sample does not build properly in IOS.  I am including the list of 19 erros which occur.

AttachmentSize
Plain text icon errors.txt5.15 KB

Target Image Relation to 3D Image

April 29, 2013 - 2:18am #1

Nevermind, stupid newguy mistake.  The simulator was selected and not my iPhone.  Works fine.

Log in or register to post comments