ArcGIS Maps SDK for JavaScript Development

Problem to Solve

When building apps with ArcGIS Maps SDK for JavaScript, the hard part is not rendering a map but choosing the right combination of @arcgis/core views, layers, renderers, components, and spatial analyses. This skill targets those decisions: when SceneLayer, IntegratedMeshLayer, or GraphicLayer should be preferred, how to integrate RenderNode custom WebGL, how to apply ClassBreaksRenderer, UniqueValueRenderer, and visual variables, and which services support Viewshed or Line of Sight.

How It Works

• 3D-first workflow: starts from SceneView, supports Tianditu basemaps, component-based initialization, and local resources for buildings, point clouds, voxels, and integrated meshes.
• Layers and symbology: covers FeatureLayer, ImageryLayer, SceneLayer, PointCloudLayer, IntegratedMeshLayer, and VoxelLayer, then applies data-driven visualization with color, size, opacity, and rotation variables.
• Custom WebGL: works with RenderNode and Mesh for vertices, indices, UVs, normals, and custom drawing.
• Spatial analysis and UI: includes elevation profile, line of sight, viewshed, shadow cast, aggregate points, plus Search, Legend, LayerList, Sketch, and Editor.
• Implementation path: moves from requirement analysis, environment check, layer selection, and code implementation to disposal, listener cleanup, and chunked loading for large datasets.

Boundaries

This skill is focused on front-end map rendering and SDK integration, not GIS service publishing, coordinate-system governance, or backend spatial database design. Tianditu basemaps require an API key; spatial analyses usually depend on corresponding analysis services; and @arcgis/map-components or @arcgis/charts-components still need version and compatibility checks.