The ARBlip spec is,in many ways the core of the project. Its the data and formating needing to position one digital object in real world space.
An over view of the ARBlip idea can be seen here;http://arwave.org/pages/specification.php
What this thread is intended for is a expanding reference of the current state of the spec, so that as separate clients develop they will read/write to the same evolving standard.
While its the long term intention to use blip annotations to store the data, untill the WiaB client and APIs are matured we are simply storing the data as a hash separated sting in the following format;#ARWAVE#[Longitude]#[Latitude]#[Altitude]#[URL or Text string]#[MIME TYPE]#
[Longitude] = Decimal longitude value, double precision.
[Latitude] = Decimal Latitude value, double precision.
[Altitude] = Decimal Altitude value, expressed in meters.
[URL or Text string] = Either a url pointing to a http hosted 3DS or OBJ object, or a inline string to use as a billboard sprite. 3D files should have their textures in the same directory as the linked mesh in order to be loaded correctly.
[MIME TYPE] = The mime type of the file. (eh, http://www.webmaster-toolkit.com/mime-types.shtml
). No type needed for text/billboards.Example's;#ARWAVE#51.558876801318085#5.078215599060059#0#http://www.atresica.nl/images/largebuilding/building.3DS#application/x-3ds#
- Positions a 3DS file at 51.558876801318085 , 5.078215599060059#ARWAVE#51.558876801318085#5.078215599060059#0#any text here#
- Positions the text at 51.558876801318085 , 5.078215599060059