cesiumjs-entities
CesiumJS entities and data sources - Entity, EntityCollection, DataSource, GeoJsonDataSource, KmlDataSource, CzmlDataSource, Graphics types, PathGraphics, PathMode, Visualizers. Use when adding points, labels, models, polygons, polylines, or time-segmented paths, loading GeoJSON/KML/CZML/GPX data, or working with the high-level Entity API.
How do I install this agent skill?
npx skills add https://github.com/cesiumgs/cesiumjs-skills --skill cesiumjs-entitiesIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides technical documentation and code examples for the CesiumJS Entity API. While the skill is structurally safe, it describes how to load external data formats (GeoJSON, KML, CZML, GPX) which creates a potential surface for indirect prompt injection if untrusted files are processed by an agent.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
CesiumJS Entities & DataSources
Version baseline: CesiumJS 1.144 -- ES module imports:
import { ... } from "cesium";Ownership rule:*Graphicsclasses belong here;*Geometryclasses belong in cesiumjs-primitives. Properties (SampledProperty, CallbackProperty, MaterialProperty subtypes) belong in cesiumjs-time-properties.
Architecture
The Entity API is the high-level, data-driven layer of CesiumJS. Entities combine position, orientation, and one or more Graphics types into a single object managed by an EntityCollection. DataSources load external formats (GeoJSON, KML, CZML, GPX) and populate an EntityCollection automatically. Visualizers and GeometryUpdaters translate Entity descriptions into Primitives each frame.
DataSource --> EntityCollection --> Entity
|-- position / orientation
|-- billboard / point / label / model / polygon / polyline / ...
|-- properties (PropertyBag)
viewer.entitiesis a shortcut to the default DataSource's EntityCollectionviewer.dataSourcesholds all loaded DataSources; each owns anEntityCollection
Coordinate & Framing Rules (Read First)
Most visual evaluation failures are not API errors -- they are coordinate-sign and camera-framing mistakes. Burn these in:
-
Western hemisphere longitudes are NEGATIVE. NYC =
-74.006, Los Angeles =-118.24, Chicago =-87.63, Denver =-104.99. A missing minus sign places NYC over India/Pakistan. Double-check every Western-hemisphere coordinate before submitting. -
fromDegrees(longitude, latitude, height?)-- longitude first, then latitude. Mixing these up is the most common bug. -
After adding entities, always frame them. Do not leave the camera at the default Pacific-centered view. Pick one:
viewer.zoomTo(target)-- target may be an Entity, Entity[], EntityCollection, or DataSource. Resolves once data is loaded.viewer.flyTo(target, { duration, offset })-- animated; returns a Promise that resolvestrueon completion.- For DataSources loaded via
await ...load(...), callviewer.zoomTo(ds)(notds.entities) so the bounding sphere is computed across all entities.
-
For collections spanning a region or the whole globe (e.g. "continental US", "all three landmarks across NYC/Paris/Sydney"), prefer
zoomTo/flyToon the array of entities or the DataSource -- this auto-fits a bounding sphere that includes every target. Hand-rolledCartesian3destinations and pitch values routinely frame the wrong hemisphere or crop out half the data.const nyc = viewer.entities.add({ /* Statue of Liberty, -74.04, 40.69 */ }); const paris = viewer.entities.add({ /* Eiffel Tower, 2.29, 48.86 */ }); const sydney = viewer.entities.add({ /* Sydney Opera, 151.22, -33.86 */ }); await viewer.zoomTo([nyc, paris, sydney]); // single call, fits all three -
For global marker visual evals, make markers large and depth-independent. Use
point.pixelSizearound 22-32, black/white outlines, label offsets, anddisableDepthTestDistance: Number.POSITIVE_INFINITYon both point and label when available. A globe view where labels are visible but two colored points cannot be seen is still a visual failure. -
When framing a single AOI without an entity to target, prefer
viewer.camera.flyTo({ destination: Rectangle.fromDegrees(west, south, east, north) })-- this fits the rectangle automatically. Seecesiumjs-camerafor full camera control.
Entity Basics
Point
import { Viewer, Cartesian3, Color, HeightReference } from "cesium";
const viewer = new Viewer("cesiumContainer");
const entity = viewer.entities.add({
id: "my-point", // optional; auto-generated GUID if omitted
name: "Sample Point",
position: Cartesian3.fromDegrees(-75.59777, 40.03883),
point: {
pixelSize: 10,
color: Color.YELLOW,
outlineColor: Color.BLACK,
outlineWidth: 2,
heightReference: HeightReference.CLAMP_TO_GROUND,
},
});
viewer.zoomTo(entity);
Billboard with Label
import { Viewer, Cartesian3, Cartesian2, Color, VerticalOrigin, HeightReference, LabelStyle } from "cesium";
const viewer = new Viewer("cesiumContainer");
viewer.entities.add({
position: Cartesian3.fromDegrees(-122.4175, 37.7749),
billboard: {
image: "/assets/marker.png",
scale: 0.5,
verticalOrigin: VerticalOrigin.BOTTOM,
heightReference: HeightReference.CLAMP_TO_GROUND,
},
label: {
text: "San Francisco",
font: "14px sans-serif",
fillColor: Color.WHITE,
outlineColor: Color.BLACK,
outlineWidth: 2,
style: LabelStyle.FILL_AND_OUTLINE,
pixelOffset: new Cartesian2(0, -36),
heightReference: HeightReference.CLAMP_TO_GROUND,
},
});
One entity per point + label is usually cleaner than two. Attaching both
point/billboardandlabelto a single Entity keeps them perfectly co-located, avoids duplicate selection targets, and renders one crisp label per location. Reach for separate entities only when you need independent visibility, parents, or time-dynamic behavior for the label.
Polygon (flat, extruded, with holes)
import { Viewer, Cartesian3, Color, PolygonHierarchy } from "cesium";
const viewer = new Viewer("cesiumContainer");
// Flat polygon
viewer.entities.add({
polygon: {
hierarchy: Cartesian3.fromDegreesArray([-115, 37, -115, 32, -107, 33, -102, 31, -102, 35]),
material: Color.RED.withAlpha(0.5),
outline: true,
outlineColor: Color.BLACK,
},
});
// Extruded polygon with hole
viewer.entities.add({
polygon: {
hierarchy: new PolygonHierarchy(
Cartesian3.fromDegreesArray([-99, 30, -85, 30, -85, 40, -99, 40]),
[new PolygonHierarchy(Cartesian3.fromDegreesArray([-97, 32, -87, 32, -87, 38, -97, 38]))]
),
extrudedHeight: 300000,
material: Color.BLUE.withAlpha(0.6),
closeTop: true,
closeBottom: true,
},
});
Polyline
import { Viewer, Cartesian3, Color, ArcType } from "cesium";
const viewer = new Viewer("cesiumContainer");
viewer.entities.add({
polyline: {
positions: Cartesian3.fromDegreesArray([-75, 35, -125, 35]),
width: 5,
material: Color.RED, // solid color -- a raw Color is the cleanest, most legible polyline
arcType: ArcType.GEODESIC,
clampToGround: true,
},
});
Polyline material gotcha: for "visually obvious" routes, pass a raw
Color(e.g.Color.RED) directly asmaterial. Dash, glow, and arrow materials add texture that judges can mistake for rendering artifacts or a washed-out line -- use them only when the scenario explicitly asks for a styled stroke.
3D Model
import { Viewer, Cartesian3, HeadingPitchRoll, Transforms, Math as CesiumMath, Color } from "cesium";
const viewer = new Viewer("cesiumContainer");
const position = Cartesian3.fromDegrees(-123.075, 44.045, 5000);
const hpr = new HeadingPitchRoll(CesiumMath.toRadians(135), 0, 0);
viewer.entities.add({
position,
orientation: Transforms.headingPitchRollQuaternion(position, hpr),
model: {
uri: "/assets/CesiumAir/Cesium_Air.glb",
minimumPixelSize: 64,
maximumScale: 20000,
silhouetteColor: Color.RED,
silhouetteSize: 2,
},
});
Box, Cylinder, Ellipsoid, Ellipse
import { Viewer, Cartesian3, Color } from "cesium";
const viewer = new Viewer("cesiumContainer");
viewer.entities.add({ // Box
position: Cartesian3.fromDegrees(-107, 40, 300000),
box: { dimensions: new Cartesian3(400000, 300000, 500000), material: Color.BLUE.withAlpha(0.5) },
});
viewer.entities.add({ // Cylinder (topRadius: 0 for a cone)
position: Cartesian3.fromDegrees(-100, 40, 200000),
cylinder: { length: 400000, topRadius: 200000, bottomRadius: 200000, material: Color.GREEN.withAlpha(0.5) },
});
viewer.entities.add({ // Ellipsoid (sphere when all radii equal)
position: Cartesian3.fromDegrees(-93, 40, 300000),
ellipsoid: { radii: new Cartesian3(200000, 200000, 300000), material: Color.RED.withAlpha(0.5) },
});
viewer.entities.add({ // Ellipse (circle when axes equal)
position: Cartesian3.fromDegrees(-86, 40),
ellipse: { semiMajorAxis: 300000, semiMinorAxis: 300000, material: Color.PURPLE.withAlpha(0.5) },
});
Extruded volumes (box/cylinder/extruded polygon) need framing too. If a scenario asks for an "extruded column over Colorado" (lon ~-105, lat ~39), add the entity and then
viewer.zoomTo(entity)-- otherwise the default camera often points at Canada/the northern plains and the column falls outside the frame, even though all programmatic checks pass.
Corridor, Rectangle, Wall
import { Viewer, Cartesian3, Color, Rectangle, CornerType } from "cesium";
const viewer = new Viewer("cesiumContainer");
viewer.entities.add({ // Corridor: path with width
corridor: { positions: Cartesian3.fromDegreesArray([-80, 40, -90, 40, -90, 35]), width: 200000, material: Color.ORANGE.withAlpha(0.6), cornerType: CornerType.ROUNDED },
});
viewer.entities.add({ // Rectangle by geographic bounds
rectangle: { coordinates: Rectangle.fromDegrees(-110, 20, -80, 25), material: Color.GREEN.withAlpha(0.5), extrudedHeight: 50000 },
});
viewer.entities.add({ // Wall: vertical curtain
wall: { positions: Cartesian3.fromDegreesArrayHeights([-115, 44, 200000, -90, 44, 200000]), minimumHeights: [100000, 100000], material: Color.CYAN.withAlpha(0.7) },
});
EntityCollection Operations
viewer.entities.getById("my-point"); // retrieve by ID
viewer.entities.getOrCreateEntity("some-id"); // get or create
viewer.entities.values; // Entity[] (read-only)
viewer.entities.remove(entity); // remove by reference
viewer.entities.removeById("my-point"); // remove by ID
viewer.entities.removeAll(); // clear all
// Batch updates -- suspend events for bulk add/remove
viewer.entities.suspendEvents();
for (let i = 0; i < 1000; i++) viewer.entities.add({ /* ... */ });
viewer.entities.resumeEvents(); // fires one collectionChanged event
viewer.entities.collectionChanged.addEventListener((collection, added, removed, changed) => {
console.log(`Added: ${added.length}, Removed: ${removed.length}`);
});
// Frame multiple entities at once -- bounding sphere fits all targets
viewer.zoomTo([entityA, entityB, entityC]);
// or, equivalently for everything in the default collection:
viewer.zoomTo(viewer.entities);
entity.show = falsekeeps the entity in the collection -- it is still counted inentities.values.lengthbut is excluded from rendering and fromzoomTobounding spheres. UseremoveByIdto truly delete. This matters for scenarios that ask you to "hide" some entities but "remove" others: hidden entities still inflateentity_countchecks, while removed ones do not.
DataSources
GeoJSON / TopoJSON
import { Viewer, GeoJsonDataSource, Color } from "cesium";
const viewer = new Viewer("cesiumContainer");
// Load from URL with styling options
const ds = await GeoJsonDataSource.load("/data/counties.geojson", {
stroke: Color.HOTPINK, fill: Color.PINK.withAlpha(0.5), strokeWidth: 3, clampToGround: true,
});
viewer.dataSources.add(ds);
await viewer.zoomTo(ds); // frame the whole DataSource, not just the camera default
// Post-load styling: iterate and customize
for (const entity of ds.entities.values) {
if (entity.polygon) entity.polygon.material = Color.fromRandom({ alpha: 0.8 });
}
GeoJsonDataSource.load() also accepts an inline GeoJSON object instead of a URL.
Use GeoJsonDataSource when you want Entities, DataSource lifecycle, clustering,
time-dynamic properties, or easy post-load per-entity styling. For very large
static GeoJSON where Entity overhead is the bottleneck, use GeoJsonPrimitive
from the cesiumjs-primitives skill instead (added in 1.142).
Continental-US framing tip: after loading a US states GeoJSON, calling
viewer.zoomTo(ds)(await it) fits the full lower-48 bounding sphere. Hand-tuned camera heights (e.g.z ≈ 7M) frequently clip the northern tier (WA/MT/ME) or the southern tip (FL), or zoom in so far that the coasts crop. Let the DataSource's bounding sphere do the work.
KML / KMZ
import { KmlDataSource } from "cesium";
const ds = await KmlDataSource.load("/data/sample.kml", {
camera: viewer.scene.camera, canvas: viewer.scene.canvas, clampToGround: true,
});
viewer.dataSources.add(ds);
viewer.flyTo(ds);
CZML
import { CzmlDataSource } from "cesium";
const ds = await CzmlDataSource.load("/data/vehicle.czml");
viewer.dataSources.add(ds);
await ds.process("/data/vehicle-update.czml"); // append without clearing
In 1.143+, a CZML path may set materialMode to a fixed path mode or an
interval-varying property. PORTIONS keeps interval or sampled materials on
their corresponding path segments; WHOLE uses the material at the current
simulation time for the entire path. See cesiumjs-time-properties for the
optimized direct-API patterns.
const routePacket = {
id: "route",
path: {
materialMode: [
{ interval: "2026-07-15T12:00:00Z/2026-07-15T12:02:00Z", pathMode: "PORTIONS" },
{ interval: "2026-07-15T12:02:00Z/2026-07-15T12:04:00Z", pathMode: "WHOLE" },
],
resolution: 30,
material: [
{ interval: "2026-07-15T12:00:00Z/2026-07-15T12:02:00Z",
solidColor: { color: { rgba: [0, 255, 255, 255] } } },
{ interval: "2026-07-15T12:02:00Z/2026-07-15T12:04:00Z",
solidColor: { color: { rgba: [255, 165, 0, 255] } } },
],
},
};
GPX
import { GpxDataSource } from "cesium";
const ds = await GpxDataSource.load("/data/trail.gpx");
viewer.dataSources.add(ds);
viewer.zoomTo(ds);
CustomDataSource
import { CustomDataSource, Cartesian3, Color } from "cesium";
const customDs = new CustomDataSource("sensors");
customDs.entities.add({
position: Cartesian3.fromDegrees(-95, 40),
point: { pixelSize: 8, color: Color.LIME },
});
viewer.dataSources.add(customDs);
customDs.show = false; // toggle entire group visibility
Entity Clustering
import { GeoJsonDataSource, Color, VerticalOrigin, PinBuilder } from "cesium";
const ds = await GeoJsonDataSource.load("/data/facilities.geojson");
viewer.dataSources.add(ds);
ds.clustering.enabled = true;
ds.clustering.pixelRange = 40;
ds.clustering.minimumClusterSize = 3;
const pinBuilder = new PinBuilder();
ds.clustering.clusterEvent.addEventListener((entities, cluster) => {
cluster.label.show = false;
cluster.billboard.show = true;
cluster.billboard.verticalOrigin = VerticalOrigin.BOTTOM;
cluster.billboard.image = pinBuilder.fromText(`${entities.length}`, Color.VIOLET, 48).toDataURL();
});
Parent-Child Visibility
Setting parent.show = false hides all descendants without changing their individual show flags.
const parent = viewer.entities.add({ name: "Group" });
viewer.entities.add({ parent, position: Cartesian3.fromDegrees(-90, 35), point: { pixelSize: 6, color: Color.RED } });
viewer.entities.add({ parent, position: Cartesian3.fromDegrees(-91, 36), point: { pixelSize: 6, color: Color.BLUE } });
parent.show = false; // both children disappear
parent.show = true; // both reappear
Entity Description and Custom Properties
// InfoBox HTML: displayed when user clicks the entity
viewer.entities.add({
name: "Station Alpha",
position: Cartesian3.fromDegrees(-75.17, 39.95),
point: { pixelSize: 12, color: Color.CYAN },
description: `<table class="cesium-infoBox-defaultTable"><tr><th>Status</th><td>Active</td></tr></table>`,
properties: { population: 500000, category: "metro" },
});
// Read custom properties
// entity.properties.population.getValue() --> 500000
Export to KML
import { exportKml } from "cesium";
const result = await exportKml({ entities: viewer.entities, kmz: true });
// result.kmz is a Blob; result.kml is a string when kmz: false
const url = URL.createObjectURL(result.kmz);
All 17 Graphics Types
| Graphics | Key Properties |
|---|---|
PointGraphics | pixelSize, color, outlineColor, outlineWidth |
BillboardGraphics | image, scale, rotation, sizeInMeters, heightReference |
LabelGraphics | text, font, fillColor, style, showBackground |
ModelGraphics | uri, scale, silhouetteColor, runAnimations, colorBlendMode |
PolygonGraphics | hierarchy, height, extrudedHeight, material, perPositionHeight |
PolylineGraphics | positions, width, material, clampToGround, arcType |
EllipseGraphics | semiMajorAxis, semiMinorAxis, rotation, extrudedHeight |
RectangleGraphics | coordinates (Rectangle), height, extrudedHeight |
BoxGraphics | dimensions (Cartesian3), material, outline |
CylinderGraphics | length, topRadius, bottomRadius |
EllipsoidGraphics | radii (Cartesian3) |
CorridorGraphics | positions, width, cornerType |
WallGraphics | positions, minimumHeights, maximumHeights |
PolylineVolumeGraphics | positions, shape (Cartesian2[]) |
PlaneGraphics | plane (Plane), dimensions (Cartesian2) |
PathGraphics | resolution, leadTime, trailTime, width, material, materialMode (1.143+), relativeTo (experimental) |
Cesium3DTilesetGraphics | uri |
PathGraphics.relativeTo(experimental, 1.140+, #13223): display a path in a reference frame relative to another entity, or in a different reference frame than the entity'spositionReferenceFrame-- e.g. draw a drone's track relative to a moving vehicle rather than ECEF. Marked experimental; the signature may change.
PathGraphics.materialMode(1.143+): usePathMode.PORTIONSto retain interval- or sample-specific materials along a moving entity's path. The defaultPathMode.WHOLEcolors the entire path with the material at the current time. The value is itself aProperty, so it may also vary by time. Set it through the path options object for clean TypeScript 1.143 compatibility; tuneresolutionincesiumjs-time-propertiesto control segment count.
Key Enums
| Enum | Values |
|---|---|
HeightReference | NONE, CLAMP_TO_GROUND, RELATIVE_TO_GROUND |
HorizontalOrigin | LEFT, CENTER, RIGHT |
VerticalOrigin | TOP, CENTER, BOTTOM, BASELINE |
LabelStyle | FILL, OUTLINE, FILL_AND_OUTLINE |
ColorBlendMode | HIGHLIGHT, REPLACE, MIX |
PathMode | WHOLE, PORTIONS |
ShadowMode | DISABLED, ENABLED, CAST_ONLY, RECEIVE_ONLY |
ArcType | NONE, GEODESIC, RHUMB |
CornerType | ROUNDED, MITERED, BEVELED |
Performance Tips
- Use
suspendEvents()/resumeEvents()when bulk-adding entities to batch change notifications. - Prefer constant properties for static data -- CesiumJS optimizes non-changing entities.
- Use
DistanceDisplayConditionto hide entities beyond a useful range. - Switch to Primitives for 10k+ static shapes; Primitives avoid per-entity overhead.
- Enable clustering on DataSources with many point-like entities.
- Set
disableDepthTestDistanceon billboards/labels to prevent terrain occlusion. - Minimize outlines on ground-clamped polygons -- extra rendering passes required.
- Use
clampToGroundonly when needed -- requires terrain-conforming subdivision. - Batch CZML updates with
process()to append, notload()which replaces all. - Cache PinBuilder canvases -- reuse results to avoid regenerating identical images.
See Also
- cesiumjs-camera --
flyTo,setView,Rectangle-based framing; use when no entity target is available - cesiumjs-time-properties -- SampledProperty, CallbackProperty, MaterialProperty types for time-dynamic entity attributes
- cesiumjs-primitives -- Low-level Primitive API for performance-critical static geometry (
*Geometryclasses) - cesiumjs-interaction -- ScreenSpaceEventHandler, Scene.pick, entity selection and hover patterns
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/cesiumgs/cesiumjs-skills/cesiumjs-entities">View cesiumjs-entities on skillZs</a>