How do I visualize data in AO? 

You must upload data to a project to visualize it in AO.  This article focuses on how specific file types are supported and preparation of those files.  

See the videos here. 

Coordinate System Support

What projection must my data be in to be visualized in AO? 

Horizontal:

AO uses the EPSG Geodetic Parameter Dataset database to define and identify the horizontal coordinate system for all datasets. Note although AO supports the full set of standard EPSG codes, it does not support engineering (i.e. non-Earth referenced) coordinate systems.

Vertical:

AO also uses Vertical Datums as defined in the EPSG database.

Notes: 

• Be careful to select the EPSG definition in the correct units and direction for your data. There are EPSG entries for many common CRSs in both meters and feet and both Z-up and Z-down conventions.
• Absolute Ocean displays all data in a global context at all times. To do so, the base coordinate system of this 3D environment is the World Geodetic System 1984 (WGS 84). When data is visualized in AO, we must transform your data, to the best of our abilities, to WGS 84. The accuracy of this transformation will vary considerably based on location and input parameters (i.e. identifying an incorrect datum for the source). The source data is not modified in any way, the representation on your screen is a separate product we derive from the source data.

Supported File Formats

Images and Grids

GeoTIFF (TIF/TIFF)

A public domain format that stores imagery or elevations with embedded georeferencing information. AO supports GeoTIFF version 1.1. We support:

• Elevation
  • 1-band 32-bit floating point
• Images
  • 1-band (intensity)
  • 2-band (intensity + alpha)
  • 3-band (color)
  • 4-band (color + alpha)
  • 5-band (color + alpha + intensity)

MTX (MTX)

When rendering MTX files, you need to provide the right EPSG code, we are unable to read this from the MTX file.  If you have access to the full HYPACK project, you can find this in the Geodesy block of the Project.ini file (look for "Ellipsoid, Projection, and Zone Name").  The Project.ini file can be found in HYPACK from File > View Project INI File.

Point Clouds

LAS (LAS/LAZ)

An open, binary format that enables georeferencing information to be embedded within point cloud data. Supported versions include 1.2 - 1.4.

ASCII XYZ (XYZ/CSV/TXT)

An ASCII text file containing multiple columns of data with the same delimiter between each column. At least 3 columns are needed, representing X, Y, and Z. If no column headers are provided, the first three columns will be assumed to be X, Y and Z, respectively. Columns can contain headers in the first row, but must consist of the following strings; if other columns are included they will be omitted:

• X - 'easting', 'longitude', 'lon', 'long', or 'x'
• Y - 'northing', 'latitude', 'lat', or 'y'
• Z - 'depth', 'z', or 'elevation'

Data must conform to these specifications:

• X data should be in the Easting or Longitude Direction 
• Y data should be in the Northing or Latitude Direction 
• Z data should be in the Elevation or Depth Direction

Vector files

Vector files contain points, lines and/or polygons to represent different features on the map, and are usually much smaller (in terms of file size) than point clouds, images or grids.

ESRI Shapefile (SHP)

ESRI shapefiles can be visualized and require the following side cars:  dbf, prj, shx.  These side car files should have the same name and be located in the same directory as the .shp file.

Please note that we do not currently use the z-coordinate, all geometry will be displayed at a height of 0.

Google (KML/KMZ)

Within the KML/KMZ format there are a wide variety of options for different data types and actions on those data types. We have prioritized supporting the vector components of KML/KMZ files as described in the list below. Additionally, KML/KMZ files often contain a reference to an external dataset (e.g. an image) or an external resource (e.g. a web service). For security reasons external resources are not supported for visualizing. External datasets are only supported for the KMZ format if the referenced datasets are also stored inside the KMZ file.

Note we currently only support KML/KMZ files stored in the WGS 84 coordinate system.

Supported KML/KMZ data types:

• Placemarks (Points)
• Paths (Lines)
• Polygons
• Images (KMZ only)

Unsupported KML/KMZ data types:

• Ground Overlays
• 3D Models
• Time-varying data
• Regions

Additional unsupported KML/KMZ features:

• Password protected KML files
• Using altitudeMode of relativeToGround
• Camera and LookAt options

GeoJSON (GEOJSON)

GeoJSON files can contain a variety of geometry (points/lines/areas) as well as additional properties. Currently we only support display of geometry information from this format, any additional properties defined for the geometries will not be displayed.