You can add urban objects to your environment. The datasets used to create these
objects can contain either a single 3D model, or multiple 3D models.
Before you begin:
The datasource must contain all the 3D models, whether in a zipped file or not, and the
shapefile.
You cannot create prepared vector datasets containing more
than 20 000 000
geometries.
The following formats are supported: DBF, PRJ, SHP, SHX (for the shapefile), and 3DXC
(for the 3D model).
In the shapefile, make sure the .3dxc file containing the 3D model to be loaded for each
point is declared in the FILENAME field. For example,
“MyFile”: “my3Dmodel.3dxc”, or “MyFile”:
“my3Dmodel”.
If the datasource already has a FILENAME field that does not specify
the name of the .3dxc file to be used, modify the datasource to rename the field.
From the Referential section of the action bar, click Create Urban Furniture.
Define the following parameters:
Option
Description
Dataset Name
Name of the dataset.
Publish dataset
Select this check box to publish the dataset on the server. This lets you publish your
experience to a City navigation experience afterward.
Published datasets
are identified by the symbol in the Published column of the
City Referential panel.
Dissociate access rights
Select this check box to dissociate access rights to a dataset from its
associated dataset document. The dataset can still be accessed and its
content can be visualized but the associated datasource cannot be
downloaded. A new dataset document is created instead and is used to compute
access rights to the dataset.
This option is especially relevant when you
need to share datasets with confidential data, for example.
When
the check box is selected, a list is displayed to let you choose the
collaborative space in which the new dataset document must be created.
By default, the collaborative space containing the original dataset
document is selected.
After clicking OK to
close the creation dialog box, an empty dataset document is created in
3DSpace with the same name as the dataset. The dataset can then be read as
soon as the new dataset document can be read.
The icon is displayed in the City Referential panel to reflect the new
status and the Properties panel shows information
about the new document.
Levels
Lets you define the subdivision levels of the quadtree. For each level you add, the corresponding size (in meters) for each tile is displayed in the Tile Size area on the right.
The tile size depends on the referential's bounding box.
Predefined Attributes
Lets you associate predefined attributes contained in the imported
document to those used by the server.
All these attributes are optional.
Their behavior is the default when no mapping is defined, or when the
attribute you define does not comply with the constraints assigned to
each of these predefined attributes.
Exposed Attributes
Additional datasource attributes that will remain associated to the dataset.
This means
that the selected attributes are displayed in the Attributes list in the
Properties panel.
Note:
Predefined attributes
are reserved terms. This means that you cannot expose an attribute
using the name and case of a predefined attribute, whatever the
dataset type. If you try to do so, an error occurs and the dataset
cannot be created. For example, you cannot expose an attribute named
SCALE if these attribute is already a predefined attribute. To be
able to expose the attribute, you must rename it first.
Below are listed the attributes that are predefined for the Urban
Furniture dataset type:
Attribute Name
Description
Constraints
Default Behavior
STRID
An external ID given by the user.
String
Has to be unique among all GeoItems of a single source.
Only
the first GeoItem is kept if there is a non-unique STRID.
The index in the layer is set. No update is possible (you can only
regenerate it).
NAME
Name defined by the user.
String
Any other format will be set to "String".
The string is empty.
FILENAME
Lets you choose from a list the datasource attribute to be used to create
the dataset. FILENAME contains the 3D models as declared
in the shapefile.
If you do not select any attribute in the
FILENAME list:
If the datasource does not contain any FILENAME field
in its shapefile, then the first resource found is used to create the
dataset. A single 3D model is added to the experience.
If the datasource contains a FILENAME field in its
shapefile, then this field is used as follows:
If all the resources exist, the dataset is created. You can have
either a single 3D model, or multiple models in your experience.
If at least one resource exists, the dataset is created but it does
not contain the features pointing to missing resources.
If you select an attribute in the FILENAME
list (for example, myfile, String, or
FILENAME):
If all the resources exist, the dataset is created. You can have either
a single 3D model, or multiple models in your experience.
If at least one resource exists, the dataset is created but it does not
contain the features pointing to missing resources.
Important:
Make sure the attribute you select in the list corresponds to an
existing resource. Otherwise, the dataset cannot be created.
If you do not select any attribute in the
FILENAME list, the default "single model"
behavior applies and only the first 3D model is added everywhere in the
experience.
String
Relative path to a file in resource.
If no explicit value is defined, it is set to the first 3DXC found in the
resource.
Otherwise, the string is empty.
ALTITUDE
Defines the altitude at which the GeoItem is grounded.
The unit used is
the one of the referential, except for 2D geometries.
Real
No attribute for 3D geometries.
The attribute is set to 0.0 for 2D
geometries.
ORIENT
Defines the pan, tilt and roll orientation of the GeoItem.
Formatted string
3 Real separated by a space.
The attribute is set to 0.0 0.0 0.0.
SCALE
3-axis scale information.
Formatted string
3 Real separated by a space.
The attribute is set to 1.0 1.0 1.0.
StreamPriority
Number value used to order GeoItems.
GeoItems with highest values are
returned in tiles at Start Level.
Real
The attribute is set to 0.0.
LifespanStart
Date from which the GeoItem is valid.
Date or string (with date format).
The accepted date format is: yyyy/MM/dd HH:mm:ss.SSSSSS
+HH:mm.
Valid date separators are ‘/’ or ‘-’.
Valid date-time separators are space or ‘T’.
Valid time-time offset separators are space or ‘Z’.
Valid time offset operators are ‘-’ or ‘+’. No operator is equivalent to the
‘+’ operator.
Note:
The time offset is directly applied to the save date and is not
kept.
Should be set before LifeSpanEnd.
The attribute is set to the start time.
As dates are limited to positive integers and four-digit numbers of the Gregorian calendar, the start time is January 1st in year 0.
LifespanEnd
Date to which the GeoItem is valid.
Date or string (with date format).
The accepted date format is: yyyy/MM/dd HH:mm:ss.SSSSSS
+HH:mm.
Valid date separators are ‘/’ or ‘-’.
Valid date-time separators are space or ‘T’.
Valid time-time offset separators are space or ‘Z’.
Valid time offset operators are ‘-’ or ‘+’. No operator is equivalent to the
‘+’ operator.
Note:
The time offset is directly applied to the save date and is not
kept.
Should be set afterLifeSpanStart.
The attribute is set to the end time.
As dates are limited to positive integers and four-digit numbers of the Gregorian calendar, the end time is December 31st in year 9999.
In addition to these predefined attributes, there are some internal and
automatically set attributes. Such attributes are not associated to any dataset type
because they cannot be set by the user. They are automatically assigned to
GeoItems.
Internal Attribute Name
Description
Constraints
Default Behavior
uuid
A guaranteed unique ID.
String
Automatically set.
A guaranteed unique ID.
SourceFileName
The name of the datasource file from which the GeoItem is created
is used.
String
Automatically set.
The name of the datasource file from which the GeoItem is created
is used.
Click OK.
A pop-up message informs you when the creation is successful and the City Referential panel opens (this is the case whenever a dataset is created).
An alert is also displayed under the top bar to inform you about the preparation status (success or failure). This alerts is displayed for a few seconds but you can click from the top bar to open the 3DNotification Center and display your notification history. For more information, see Dashboard Top Bar.
Note:
As this notification is displayed only when the dataset is prepared, it might not be immediately displayed for large datasets that take time to be processed.
From the Available City Datasets area of the
City Referential panel, drag the dataset to the referential
when its status switches to Ready.
The dataset is displayed in the tree on the left and the associated objects
appear on the selected referential. Example with a single 3D model (default behavior) Example with multiple 3D models
.
symbol in the Published column of the
City Referential panel. 
icon is displayed in the City Referential panel to reflect the new
status and the Properties panel shows information
about the new document.
from the top bar to open the 3DNotification Center and display your notification history. For more information, see Dashboard Top Bar. Note: As this notification is displayed only when the dataset is prepared, it might not be immediately displayed for large datasets that take time to be processed.
