Description
You can create objects storing a list of geometric features (points, lines or polygons) with associated metadata.
Supported formats
Here is the list of supported formats when you want to create prepared datasets out of datasources.
| Format/Data Type | Comments |
|---|---|
| GeoJSON (Geographic JSON) | File with a .geojson extension. This format can be used for creating vector datasets. |
| 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. |
| WFS | An XML file retrieved from the data returned by the GetCapabilities request to a WFS server. For more information, see OGC WFS Standard. |
Application in City Discover
There’s two ways to display a Simple Feature in City Discover:
- By creating a Simple Feature dataset in City Referential.
- By uploading the source file(s) in 3DSpace or 3DDrive.
1. Create a Simple Feature dataset in City Referential - Only with CRM role.
- In the Datasets tab, from the page toolbar, click + Create Dataset.
- Select the Simple Features type dataset.
- From your local, drag and drop your file(s) into the popup.
- After the dataset configuration [2] in City Referential, retrieve it in the City Discover’s Referential Panel.
- Just drag it to the 3D view.
The video shows a shapefile datasource from local machine, uploaded, transferred, configured and dropped to City Discover 3D View.
2. Using 3DSpace or 3DDrive [3].
- Just drag and drop the uploaded file(s) to the City Discover 3D view.
- These data will appear in a temporary layer (Temporary Items > User Added Items*).
*Please note that the data inside the temporary folder cannot be saved in the experience. To preserve them, move them out the temporary folder.
- These elements loaded in the Experience are not configurable in terms of appearance or disappearance distance.
For reasons of visualization performance, limit their number within the same Experience.
Quadtree subdivision levels & Number of elements per tile
1. Start and End levels
During the dataset configuration, these parameters define the minimum and maximum subdivision levels of the quadtree.
The Start level defines the zoom level on which the quadtree starts dividing.
The End level defines the zoom level on which the quadtree stops dividing.
Parameter configuration user interface
This makes it possible to optimize data loading within the application.
Apply a low Start level value for data that needs to be seen from a distance, and a high start level value for data that needs to be seen closer.
Quadtree visualization example
2. Number of elements per tile.
Defines the number of elements that you want to see in each tile of the dataset.
The maximum number of elements per tile is 1000.
Parameter configuration user interface
This configuration, like the start & end level, allows data loading to be optimized.
