Menu Items
A Menu Item describes one set of data to load into a Project View's 3D scene: an Entity Type, an Assembly, a Tileset, a KML file and so on. Users toggle them in Navigator's panel, and Bookmarks enable them by ID.
Menu Items don't have their own records. They sit within their Project View record.
This article will cover where Menu Items are stored, the settings every Menu Item shares, and the settings for each Menu Item type.
Where Menu Items are stored
Menu Items live in the "menuItems" array of a Project View's "Settings". There are no requests for a single Menu Item, so you create, update and delete them by saving the Project View with the changed array. You can read about saving Project Views in Project Views and Bookmarks.
A Bookmark enables Menu Items by listing their "id" values in its "menuItemIds" setting. Enabling a folder also enables its children. You can read about "menuItemIds" and per-Bookmark overrides in Bookmark: Menu Items.
Data model
Below are the settings that are consistent between the different Menu Item types. Each type adds its own settings, described in the sections below.
When Navigator opens a Project View in model space, only "ModelTileset" and "Assembly" Menu Items can be enabled.
Zoom control
Menu Items that render Entities one by one ("BruceEntity", "EntitiesIds" and "DataLab") use a "CameraZoomSettings" array to decide how each Entity looks at different distances from the camera. An Entity outside every row's range is not drawn, so the largest "MaxZoom" is how far away the Entities stay visible.
You can read about Style records in Entity Styles.
Item: Folder
A folder only groups other Menu Items. It loads nothing itself.
Item: Entity Type
Loads the Entities of an Entity Type that are around the viewport, and requests more as the camera moves. You can read about the attribute filter in Entities, and about historic records in Entity historic data.
Point, icon and 3D model Entities can be clustered when they are close together and the camera is far away.
Navigator can let users create new Entities of the type by clicking in the scene. The authoring settings decide how a new record relates to the Entity that was clicked.
When a Menu Item of this type has a Tileset set, Operator saves it as the "EntitiesTileset" type below instead.
Item: Entity Type Tileset
Loads a Tileset built from an Entity Type's Entities, instead of requesting the Entities one by one. Only the 3D model part of a Style applies to it.
Item: Entity IDs
If you want to keep things simple and render a specific set of Entities, you can use this type. It uses the same zoom control as the Entity Type item.
Item: DataLab query
Loads the Entities that a DataLab query's primary selection criteria match around the viewport. It uses the same zoom control as the Entity Type item. You can read about creating queries in DataLab queries.
Item: Assembly
Loads an Assembly imported into Nextspace (IFC, RVT and the like). When the Assembly has a Tileset, the Menu Item is the "ModelTileset" type and the Tileset is loaded. When it has none, the Menu Item is the "Assembly" type and the Assembly's Entities are loaded one by one from its hierarchy. Operator picks the type when you save, based on whether "tileset.TilesetID" is set.
The settings below only apply to the "ModelTileset" type. An Assembly can contain Entities from a range of Entity Types, so Styles can be mapped per Entity Type.
Item: Point cloud
Loads a point cloud imported from a LAS or LAZ file.
Item: Cesium Tileset
Loads a static Nextspace Tileset, an XGrids splat, or an external Cesium Tileset by URL.
Item: Cesium Ion asset
Loads a Cesium Ion asset by its asset ID. Unlike the Cesium Tileset item, the Style settings are always applied.
Item: I3S Tileset
Loads an ArcGIS I3S scene layer. Both URLs are required, and the Menu Item loads nothing when either is missing.
Item: KML file
Loads one or more KML files into the scene. This is purely visual: the shapes are not Entity records.
Item: OSM Buildings
This is a data-set provided by Cesium. Learn more about IP rights and usage at Cesium OSM Buildings.
This Menu Item will load the Cesium OSM Buildings tileset into the scene. It is recommended to pair this with the Cesium World Terrain to ensure buildings are on the ground.
Item: Google Photorealistic 3D Tiles
This is a data-set provided by Google. Learn more about IP rights and usage at Google 3D Photorealistic tiles.
Your account (organisation) must have a Cesium Ion key or a Google Photogrammetry key in Operator's application keys. When it has a Cesium Ion key, we load the tiles through Cesium Ion. It is recommended to hide the globe when this is enabled.
Item: Google Places search
This is a data-set provided by Google. Learn more about IP rights and usage at Google Places API.
This Menu Item searches Google Places for a keyword around the viewport and draws each result as an icon. Requests go through the Bruce API, which uses the Google API key in your account's application keys in Operator. Without that key nothing is drawn.