agentleFS
Sign inStart free
geoai-latamgeoai-latam/SKILL_JS5_ARCGIS/skills/arcgis-3d-layers/AGENTS.md

SKILL_JS5_ARCGIS / arcgis-3d-layers

AGENTS.md1 starsChanged 6 months agoMITView on GitHub

Quick-reference for 3D layers. Read before loading 3D content. 1. Data type? i3s objects → SceneLayer; i3s mesh → IntegratedMeshLayer; 3D Tiles mesh (3DTilesServer/tileset.json) → IntegratedMesh3DTilesLayer; LiDAR → PointCloudLayer; gaussian splat → GaussianSplatLayer on a published tileset.json or portalItem, never a .ply. 2. View? Must be a SceneView / <arcgis-scene>. 3. On terrain? Set map.ground = "world-elevation".

The file

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    View?: Must be a SceneView / <arcgis-scene>.

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Agent Guide: arcgis-3d-layers

Quick-reference for 3D layers. Read before loading 3D content.

Quick Decision Tree

  1. Data type? i3s objects → SceneLayer; i3s mesh → IntegratedMeshLayer; 3D Tiles mesh (3DTilesServer/tileset.json) → IntegratedMesh3DTilesLayer; LiDAR → PointCloudLayer; gaussian splat → GaussianSplatLayer on a published tileset.json or portalItem, never a .ply.
  2. View? Must be a SceneView / <arcgis-scene>.
  3. On terrain? Set map.ground = "world-elevation".

Setup Checklist

  • Use a SceneView (<arcgis-scene>), never a MapView.
  • Set ground for terrain alignment.
  • Leave qualityProfile to the SDK (set per device); expose it only as a user setting.
  • After await layer.load(), check fullExtent is not the whole world (silent bad source).
  • Load gaussian splats on demand (GPU-heavy).

Anti-patterns (one-liner reminders)

  • ❌ Adding 3D layers to a MapView.
  • ❌ Loading every heavy 3D layer at startup, or hard-coding qualityProfile.
  • ❌ GaussianSplatLayer({ url: "….ply" }): resolves load() and draws nothing.
  • ❌ opacity on mesh/point-cloud/splat layers in a SceneView: not supported.
  • ❌ Forgetting ground so meshes float/sink.

Files in This Skill

  • SKILL.md / SKILL.es.md — full guides
  • references/api-detail.md — 3D layer signatures
  • references/examples.md — SceneLayer / mesh / splat
  • references/pitfalls.md — extended troubleshooting
  • scripts/snippet-scenelayer.ts, snippet-gaussiansplat.ts, snippet-integratedmesh.ts

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free