Supported Formats¶

FieldTwin Design is able to ingest data from a multitude of input sources such as various file formats and online data/web services. This is an overview over the various formats we support:

Screenshot

3D Models¶

To allow for real time collaborative field design using modern cloud and browser based technology allowing you access from anywhere at anytime we offer a Generic Library of 3D models that are optimized for online streaming. The format used is:

.gltf

You can read more about the standard here:

https://www.khronos.org/gltf/

To create your own private asset libraries and have them available to your instance, please contact us for more information as we support most 3D Engineering formats in the 3D model optimisation, conversion and asset publishing process.

2D Images¶

We support imagery to be added to your field layout as layers. The image formates supported are:

JPG , PNG , GIF , BMP

For more information see Picture

Media¶

All image and video formats supported by Chrome

3D Surfaces¶

This allows you to add Bathymetry and/or Survey data to your Field layout in GeoTiff or X,Y,Z (point-cloud) format. You can add multiple Bathymetry/Surveys to a sub-project. FieldTwin will then height- or depth-sample if you will each Bathymetry layer individually, and where there is no Bathymetry data the default “Sea Level” value from the Project settings will be used.

Point Clouds¶

.txt , .xyz , and .geoJSON

You can create 3D surface layer out of point data in .xyz, we can also read geoTiff and .dem files.

For more information see 3D Surface

Surface Raster formats¶

Read more about the raster formats we handle here :

www.gdal.org/formats_list.html

Rules Engine¶

The Rules Engine allows you to create a set of rules with conditions when you import data from either a file such as a Shape, CSV or a MS Excel file. Or you can connect directly to an ArcGIS Map server. The rules you create based on the input data will trigger corresponding FieldTwin Actions.

FieldTwin can then auto-create a field layout including 3D assets and connections using your set of import rules. You can also import and export your rule set to use it in multiple projects.

A typical use case could be to auto create brownfield assets or connections for tie in, slot in considerations etc.

For more information see Rules Engine

Pipelines¶

If you want to ingest pipeline data this can be done by importing a connection profile in x,y,z ASCII format.

For more information see Support for Text and x,y,z files

You can also import connections or pipelines from files as follows:

GeoJSON¶

For more information see Support for GeoJSON files

Shape file import¶

For more information see Support for SHP files import

Import Profile from WFS¶

For more information see Import Profile From WFS

Well trajectories¶

We support the most common well data formats from applications such as Compass, DecisionSpace etc. Typically well trajectories are ingested from text files, or through the API.

For more information see Well from File

Web Mapping Service (WMS)¶

The use of geography data is becoming more and more important for oil and gas operators and service providers to make informed decisions. This can be in terms of locating and extracting new resources, better field design and planning, information retrieval and offers deeper insight into relationships and patterns as part of everyday operations. You can add a map layer to FieldTwin Design using WMS (Web Mapping Service) Data.

For more information see WMS