About Datasets

A dataset is an object that represents an amount of viewable data. There are two kinds of datasets: "prepared datasets" and "datasets in preview" (or "datasources").

Prepared datasets are viewable prepared items that appear in the Referential panel.

Datasets in preview are items added to the current experience through 3DSpace or 3DDrive indexing, or created by the user (such as bookmarks).

This page discusses:

Overview
Dataset Types
Datasources (Datasets in Preview)

Overview

A dataset is represented by the following elements:

Name (a unique identifier by tenant)
State (displayed in the Available City Datasets area of the Referential Panel)
A state is associated to the dataset and gives information about its use because the dataset is asynchronously built.
ENOVIA document id of the datasource
Dataset type
Referential
List of datasources
List of exposed attributes.

Dataset Types

Dataset types represent data and how they appear. Each type has its own specificity and influences the way data appears.


Type	Description
Building	Generic building: a building modeled with a parametric system based on a series of rules (or "parameters") such as a building footprint or height. This building is generated from a 2D outline extracted from cadastral data. Specific building: a complete 3D model that represents a building. It is already georeferenced and does not need any altitude or rotation information. Tiled specific building: a building made of building tiles (in .3dxc format) that represents one level of the referential's quadtree. This gives a grid covering the referential. Note: The .3dxc file associated to a cell must cover the whole cell surface, otherwise an error might occur. This building is generated from an ENOVIA document containing one or more ZIP files with all the building tiles and a JSON file (with the .ctds extension) describing the referential and the dataset.
Image/Map	The image represents the visual part of the Earth's surface; it can be an orthophoto or a cartography picture.
ImageProxy	The map is used to query servers providing geo-spatial raster data on a given area, in a given projection. The supported OGC (Open Geospatial Consortium) standard procotols are: WMS (Web Map Service): for requesting georeferenced map images from distributed geospatial databases. For more information, see http://www.opengeospatial.org/standards/wms. WMTS (Web Map Tile Service): for distributing tile sets of geospatial data. For more information, see http://www.opengeospatial.org/standards/wmts. The source must be a file retrieved from the `GetCapabilities` method. The file must have a .wms or .wmts extension.
POI	Very similar to the simple feature type, it is typed to have a specialization. The source has no mandatory attributes, just a point representing a position and a weight. The default icon is but it can be customized. To do so, the shapefile must contain the icon file to be used. This icon file must be is PNG (RGBA) format with a 1:1 ratio. The recommended size is 128 pixels.
Routing	Describes a routing network (pedestrian routes, routing used by cars, and so on). This network is not visible through the 3D view but is used for routing algorithms
Simple Feature	A list of geometric features (a point, or a polygon) with metadata, like an Excel sheet. It stores a simple feature source "as-is" (without any processing or conversion). The source has no mandatory attributes, just a geometry representing a position. Only exposed attributes are needed.
SimpleFeatureProxy	A list of geometric features created from a WFS server.
Terrain	Represents the form of the Earth's surface. Raster terrain: built from a height map (DTM) and in this case, only a simple image is necessary. Geometric terrain: represents one level of the referential quadtree where the DTM (Digital Terrain Modeling) is made of terrain tiles (.3dxc files) instead of image tiles. It is a pre-tiled dataset with one 3D file per tile. This gives a grid covering the referential, and the .3dxc file associated to a cell must cover the whole cell surface. It is generated from an ENOVIA document containing one or more ZIP files with all the terrain tiles and a JSON file (with the .ctds extension) describing the referential and the dataset.
Tree	Represented as a crossquad and a texture index among a texture atlas of 4 x 4 trees. The associated texture file must be in PNG format with a maximum size of 2048 x 2048: The atlas is indexed to retrieve the texture more easily: The source must be a simple feature with an atlas id.
Urban Furniture	Represented as a positioned 3D model (which can be rotated around the Z axis). The source must be a Simple Feature with an atlas id.

Exposed Attributes

When creating a vector dataset, you can choose to expose or not some of its attributes.

Three columns are displayed:

The first column (on the left) lets you select the set of attributes to be exposed. Note that multiselection is possible.
Tip: Click the column header to select (or deselect) all attributes at once.
The Output Attributes column lets you enter the name under which you want the attribute to be exposed in the dataset. To do so, click twice the name to be modified to make it editable, and then enter the new attribute name.
The Input Attributes column displays the names found in the SHP source file. The names in this column are displayed for your information only, they cannot be modified.

Datasources (Datasets in Preview)

Datasources represent raw data that you want to display in the client application. It must be previously stored on 3DSpace.

The source contains a state to inform the user. This state can be: In Progress, Ready, or Error.

The source is represented by the following elements:

ENOVIA document ID
Start level
End level.
AEC Data: 3DEXPERIENCE data generated through Civil Engineering 3D Design. Only models with a geolocation are supported.

Supported Formats

Datasources are often huge and therefore, they cannot be displayed "as-is". Not all file types are supported.

3D Model Insertion

Below are listed the supported formats.


Format	Comments	Supported
3DX, 3DXC
3DXML (EXtensible Markup Language), CGR (CATIA Graphic Representation)	3DXML 4.3 (XML/CGR tessellation)
COLLADA (COLLAborative Design Activity) with a .dae extension	No texture
OBJ	No texture

Dataset Creation

The formats listed below are interpreted with the GDAL library.


Format/Data Type	Comments	Supported
GeoTIFF (Georeferenced Tagged Image File Format)	Image file with a .tiff extension embedding georeferencing information. This file can contain: a single-float band to represent the elevation of the Earth's surface (the terrain) 3- or 4-Byte bands to represent a visible part of the Earth's surface (three bands RGB, 4 bands for RGBA). This format can be used for creating raster datasets
GeoJSON (Geographic JSON)	File with a .geojson extension. This format can be used for creating vector datasets.	Note: SLD (Styled Layer Descriptor) files (with a .sld extension) can be used to express vector styling of datasources. For more information, see http://www.opengeospatial.org/standards/sld.
SHP (Shapefile)	Standardized by ESRI. It corresponds to a set of files and the following file extensions are mandatory: .shp, .dbf, .shx and .prj. This format can be used for creating vector datasets.	Note: SLD (Styled Layer Descriptor) files (with a .sld extension) can be used to express vector styling of datasources. For more information, see http://www.opengeospatial.org/standards/sld. The SLD file can also reference external graphics (in PNG or JPEG format) for polygon texturing. For relative URLs, external graphics must be located directly under the document, no folder or hierarchy can be created in the 3DSpace document. If a hierarchy is required, use a zipped archive.
WFS	An XML file retrieved from the data returned by the `GetCapabilities` request to a WFS server. For more information, see http://www.ogcnetwork.net/node/180.

Preview of Simple Features in GIS Files

You can preview geometries and their associated properties contained in a file without needing to create a dataset in the referential.

To preview geometries, you must:

On premises only: Upload the file in 3DSpace first.

On the cloud only: Upload the file either in:

3DSpace
3DDrive

The following formats are supported for previewing simple features.

Format Comments Supported

CSV (Comma Separated Values)

A .csv extension containing latitude and longitude columns with WGS84 coordinates in decimal degrees.

For more information, see http://www.gdal.org/drv_csv.html.

If these attributes exceed the valid range, the gdal_invalid_geo flag is set to INVALID.

All .csv files are read (one NETVIBES object per feature with its attributes) but only those with lat and lon attributes will have geometry.

More precisely, these files must have a semicolon as field separator, UTF-8 text encoding, and a dot as decimal separator for floating numbers.

Partial

FGDB (File Geodatabase)

A .zgdb extension containing at least one .gdb file or folder.

A .zgdb is a zipped file named .zgdb instead of .zip.

For more information, see http://www.gdal.org/drv_filegdb.html.

Partial

Only simple features are read, not the style.

GeoJSON (Geographic JSON)

A format for encoding geographic data structures.

SLD does not appear for datasources.

GML (Geography Markup Language)

A subset of XML (.gml extension) for expressing geographical features.

For more information, see http://www.gdal.org/drv_gml.html.

The projection must be defined in each file and for each feature (as for files written through FME). If no such projection is found in the GML file, coordinates are expressed in WGS84 (latitude and longitude in decimal degrees).

Important: Coordinates are always read as Easting/Northing, which means that for the latitude and longitude system, longitude is given first.

Partial

Only simple features are read, not the style.

KML (Keyhole Markup Language)

Only a subset of KML is supported: except Simple Feature data, all other data is ignored (see http://www.gdal.org/drv_kml.html and "KML Reading" for limitations).

Partial

Only simple features are read, not the style.

SHP (Shapefile)

Standardized by ESRI. It corresponds to a set of files and the following file extensions are mandatory: .shp, .dbf, .shx and .prj.

SLD does not appear for datasources.

Below is the list of supported geometries:

Point
LineString
Polygon
MultiPolygon.

Important: When you drag a document containing many files from 3DSpace or 3DDrive to your experience, only one file is previewed from the dragged document. To determine which file is to be previewed, the formats are ranked in the following order of priority:

.geojson
.shp
.kml
.zgbd
.gml
.csv

If there are two files with the same format that takes precedence over the other formats, the priority is given to the file whose name comes first in alphabetical order. For example:

If the document contains one file of each format, the .geojson file is previewed.
If the document contains a .kml and .csv file, the .kml is previewed.

In the document, if the file of the format that takes precedence over the others is invalid, the preview fails and no further attempt is made.

Attribute Mapping

The mapping type of an attribute must be consistent with the datasource type.


Datasource Type	String	Boolean	Date	Real	Integer
Mapping Type
String
Boolean
Date
Real
Integer