1. Home
  2. Docs
  3. Data Conversion
  4. AR Model Conversion

AR Model Conversion

The data conversion panel allows users to upload 3D datasets and convert them into AR friendly models to be later downloaded into the application.

Uploading 3D datasets using the data conversion panel

  1. Click the upload data button to open the upload panel.
  2. Browse the desired 3D dataset.
    • The desired file should adhere to the custom folder structure online in the previous section.
  3. Under the file format, select “AR Model Package”.
  4. Under the conversion service, select “Georeferenced conversion service”.
    • This option allows the user to georeference (position) the 3D model using the inbuilt location editor. This will modify the 3D model’s metadata and publish it into the GeoCityAR application.
  5. Enter a version name.
  6. Enter the category of the 3D model (e.g. Building, Underground Asset, Car).
  7. Select the filetype of the 3D model.
    • The data conversion panel only accepts two types of 3D models. The Collada (DAE) & Object-wavefront (OBJ) file types.
  8. Submit the 3D model.
    • Select the correct digital elevation model (DEM) based on the models’ proposed location. For example, if the model is located in the Melbourne CBD, select the matching DEM.
  9. Open the location editor to georeference the 3D model.
  10. Select between the address or latitude/longitude to position the 3D model.
  11. Apply the affine transformations (scale, rotation, translation) to fit the model into the desired parcel boundary.
  12. Select the correct height to display the model. This height represents the altitude of the 3D model above the mean sea level.
  13. Save the metadata. This will automatically update the 3D model’s parameters and publish the model into the GeoCityAR application.
  14. Open the GeoCityAR application and select the downloaded model’s page (“+” button). Select the published model and download it to the select model page.

Supported file formats

The GeoCityAR application supports various types of 3D models. Currently, the native support includes the Collada (DAE) and Object-wavefront (OBJ) files.

An important requirement of the uploading service is the custom folder structure. Both the Digital Twin data conversion panel and the GeoCityAR application require the user to maintain this folder structure when uploading new assets into the application. An overview of the custom folder structure is described below.

The parent folder contains the 3D model file (Collada, Object-wavefront file, etc) and the relevant textures for the model. The user can also upload a thumbnail image to be displayed inside the table cell referencing the model on the select model page. Overall, the file must be zipped and uploaded into the Digital Twin for georeferencing (positioning) before it is downloaded into the GeoCityAR application.