Getting Started With ARML

The Wikitude browser supports three formats for customised AR content. These are KML files, ARML files and ARchitect files. As it so happens, the various formats offer different levels of functionality, with KML offering the least and ARchitect offering the full functionality of the Wikitude SDK.

After a successful deployment of the KML version in the Wikitude browser, and noting it’s limitations, the next step is to develop a world in ARML, which has further capabilities than KML. As development progresses, it will also be important to document these differences and the overall advantage of ARML over KML.

To get started with ARML, we would be using the ARML 1.0 specification, rather than ARML 2.0. This decision, is based on the fact that Wikitude fully supports ARML 1.0 while ongoing efforts are being made to support ARML 2.0. For the sake of this project, therefore, the ARML 1.0 standard will be adopted. Continue reading “Getting Started With ARML”

Wikitude Devzone: Building My First World

I’ve joined the Wikitude Devzone and now have access to the tools and resources needed to build my first AR world. This world will be embedded in the Wikitude browser and will not contain any native Android code. This post, will cover the process of developing the AR world.

The AR world files can be uploaded using KML (Keyhole Markup Language), ARML (Augmented Reality Markup Language – an extension of KML) or the ARchitect Engine (using HTML5, JavaScript and CSS). The first step will be to build our AR World. To achieve this, we will make use of KML and Google Maps. We will locate the required POIs using Google Maps use the information gathered as the basis for creating the KML files.

While creating your AR world you can select a maximum of 3 categories to increase the chances of your world being discovered. Continue reading “Wikitude Devzone: Building My First World”

A Diversion To KML

KML stands for Keyhole Markup Language. It is a file format which enables the storing and display of geographical data. The stored data can be viewed in an Earth browser, such as Google Earth, Google Maps and Google Maps for mobile. You can read more about KML here

KML is based on the XML format and uses nested tags which are case-sensitive. The KML reference should be strictly followed, both syntactically as well as according to the same order. Google Maps has been selected as the method of display as the Wikitude SDk uses Google Maps, rather than Google Earth.

In Google Maps, a custom map was created with the following locations:

  • The Roland Levinsky Building (University reception)
  • Isaac Foot Building (Student Funding)
  • Babbage Building (Open Access Computing Rooms)
  • Charles Seale-Hayne Library
  • The University Medical Centre
  • Smeaton Building (Computing office building)

There are two options when creating the map – either to  draw the points in the maps manually or to search for the locations. It appears that both will be necessary to bring full functionality to the application as some locations are not currently listed on Google Maps. However, for the purpose of ‘proof of concept’ the 6 locations listed above will be added to the custom map by conducting named searches.

The map was successfully created and the KML file uploaded publicly here. The purpose of this post has been achieved and now the tutorial will return to the previous post where we intend to make use of the KML file.

Getting Started With The Wikitude SDK – 2

In the previous post we downloaded the Wikitude Browser for Android and documented the whole process of testing. This post will cover platform verification. This will entail putting our own data on the Wikitude platform with the aim of having it displayed and interacting with it in the from the Wikitude browser. The first thing to do will be to find out the requirements for including personalised data to the Wikitude platform.

P.S It is worth finding out if indeed the application can be tested during the preview day sessions – licensing restrictions might prevent this. In addition to this, the need for internet connection (cost of data?); it is worth finding out if it works only with wi-fi or can also work on the user’s mobile data plan. If wi-fi is the only option, will preview day attendees be allowed access to the University wi-fi?

Also worth confirming, is if the application works indoors in all areas, or at least major areas, including the Smeaton building, the Roland Levinsky building. Also worth noting if floor levels have any effect on performance.

It appears the Wikitude SDK has been updated to work across all major platforms – Android, iOS and BlackBerry 10.

Continue reading “Getting Started With The Wikitude SDK – 2”

Getting Started With The Wikitude SDK

So, before I start actual development of the AR app, I first have to test the apps developed by the third party, in essence to test the development SDK. This post will cover the process of downloading the Wikitude AR browser and the notes, including issues, benefits noticed during the application test. Subsequent posts will cover the download and test of the native Android apps.

The Wikitude browser can be downloaded from Google play here. Note that this is different from the Wikitude Family Browser which can not be downloaded from the UK.

The app has been downloaded to my device. It is important to note here that there are minimum requirements to install the app:

  • Android 2.1 or higher
  • OpenGL ES 2.0 and higher
  • Camera
  • Compass

I shall now step out of the building and record my notes as I interact with the application.

You can read about the suitability of choice of platform here.

Upon successful testing, the next stage will be platform verification.

Hello, Augmented Reality

For some reason, I have a particular interest in developing Android applications. I seem fascinated with the whole process – writing the code, launching and testing on the emulator, porting the application to a physical device, uploading to the apps market and finally watching the number of downloads and reviews go up. Truth be told, I haven’t gone past the first three steps. I’m optimistic that I will – very soon.

Be that as it may, for my final year project I chose to develop an android application. Not just any android application. I chose an ambitious project – to develop an Augmented Reality application. If you are quite up-to-date with technology trends you’ll be well aware that while AR is not a new technology in itself, it’s definitely one of the trends being currently explored by quite a number of organisations. One of the most recent probably being Continue reading “Hello, Augmented Reality”