Cesium ion - Documentation

Once installed, you can confirm everything is operating as normal by running the following command:

This should produce output similar to the following. The important part is "microk8s is running". If you receive an error, review the Installing microk8s section.

helm3 should be enabled by default and nothing else is required to install and run the application. If it is not shown as enabled, you should run the following commands:

Microk8s installs kubectl and helm. You can run them as microk8s kubectl and kubectl helm to administer the cluster.

Cesium ion tiling needs access to both an input volume and an output volume. We will also configure the asset server to use the same output volume for hosting. Follow these steps to configure them:

When you are done the localPersistentVolumes section should contain the correct information based on your install.

We’ve provided several types of sample data for you to play with. But you need to copy the data to a place where the tiling pipeline can access it. For this tutorial, that’s the directory you created in step 8 above. Copy the included sample data to that directory now by running the following command:

Cesium ion requires a 3D Tiling Pipeline license, which is configured at the top of cesium-ion/values.yaml. By default it will be an empty string:

Install your license by performing the following steps:

Make sure you saved the changes to cesium-ion/values.yaml in the previous section and then install the chart by running the following command:

You should see output similar to the below.

The above indicates success. You can ignore the output for now as we’ll provide explicit next steps below.

If you received an error instead, run microk8s helm uninstall cesium-ion to ensure any partially installed components are removed. Then review this section to ensure you didn’t miss a step and try again.

For our first job, let us tile the reality capture OBJ model in /data/sources/Office_Park/Office_Park.obj. Cesium ion supports reality models in glTF, DAE, FBX, or OBJ format.

First, change the name: property at the top of my_first_job.yaml to cesium-ion-tiling-reality-model.

Next, find the command: section of my_first_job.yaml and replace the entire entry with the below. Remember that indentation is very important in yaml files. We’ve pre-indented the text for you, but command: should line up with the imagePullPolicy: Never above it.

While the 3D Tiling Pipeline reference guide has a full explanation of all options. Here is a brief summary of the above command:

We’re ready to create our first tileset. Save and close my_first_job.yaml and then launch the job by running the below command:

You should see a message similar to the below, indicating success:

This small model only takes a few seconds to complete, but you can check the status by running the below command:

Which will show output similar to the following:

The pod running your job will be named starting with cesium-ion-tiling-reality-model- and a unique suffix which will be different for you. The other pod is the asset server we created above and can be ignored.

If the status is Complete, the job already succeeded, Error indicates failure, and Running or anything else is considered in progress.

Once the job completes it will automatically clean itself up after 120 seconds unless you configure it with a different value. Before that time, you can run the below command to see the job log:

Normally there is no need to look at the logs unless you are debugging a problem or working with Cesium support.

Since we’ve started the asset server in development mode, you can now go back to the landing page in your browser and click on View all tilesets. The list should now contain a single tileset with an id of Office_Park. The id was determined by the --output parameter in the above command and you can configure it to be whatever you like. For example, it could be a database identifier to data in the application you are building.

Click on Office_Park and you should see the data running in a simple CesiumJS-based viewer:

You can also load this 3D Tiles tileset into your Cesium application or any client that supports 3D Tiles via the YOUR_SERVER_ADDRESS/v1/3dtiles/Office_Park/tileset.json url. See the Cesium Learning center for the exact details of loading 3D Tiles into your Cesium client.

Congratulations, you’ve tiled your first tileset! Let’s do a few more.

Cesium ion supports tiling of one or more raster imagery files into a tileset. Create a new job template named imagery.yaml by running the following command:

Open imagery.yaml in a text editor and change the command: section to the below:

We’ll rely on the auto-generated name this time. Launch the job by running:

After a few moments, go back to the View all tilesets page and refresh it. You should now see Courtyard listed in the assets. Click on it to view the data.

It should look similar to the below image:

This is a TileMapService (TMS) imagery tileset that can be loaded into any application that supports TMS layout via the YOUR_SERVER_ADDRESS/v1/imagery/Courtyard/ url.

Cesium ion supports tiling of one or more raster terrains into a single tileset. Create a new job template named terrain.yaml by running the following command:

Open terrain.yaml in a text editor and change the command: section to the below:

We’ll rely on the auto-generated name again. Launch the job by running:

After a minute, go back to the View all tilesets page and refresh it. You should now see ZionNationalPark listed in the assets. Click on it to view the data.

It should look similar to the below image:

This is a quantized-mesh terrain tileset that can be loaded into any application that supports quantized-mesh via the YOUR_SERVER_ADDRESS/v1/terrain/ZionNationalPark/ url.

Cesium ion supports tiling of one or more LAS or LAZ point clouds into a single tileset. Create a new job template named points.yaml by running the following command:

Open points.yaml in a text editor and change the command: section to the below:

We’ll rely on the auto-generated name again. Launch the job by running:

After a few moments, go back to the View all tilesets page and refresh it. You should now see House listed in the assets. Click on it to view the data.

It should look similar to the below image:

This is a 3D Tiles tileset that can be loaded into any application that supports 3D Tiles via the YOUR_SERVER_ADDRESS/v1/3dtiles/House/tileset.json url.

Cesium ion supports tiling of one or more glTF, DAE, FBX, or OBJ models into a single tileset. This option should be used whenever the model is not a reality mesh or similar large mesh. One example is BIM and CAD models.

Create a new job template named cad.yaml by running the following command:

Open cad.yaml in a text editor and change the command: section to the below:

We’ll rely on the auto-generated name again. Launch the job by running:

After a few moments, go back to the View all tilesets page and refresh it. You should now see OfficePlan listed in the assets. Click on it to view the data.

It should look similar to the below image: