import RouteLayer from "@arcgis/core/layers/RouteLayer.js";const RouteLayer = await $arcgis.import("@arcgis/core/layers/RouteLayer.js");- Since
- ArcGIS Maps SDK for JavaScript 4.23
RouteLayer is a layer for visualizing and solving routes. A solved route includes turn-by-turn directions, and can be stored and retrieved from ArcGIS Online or Enterprise, either as a portal item, or as part of a webmap.
A RouteLayer consists of two or more stops, and optionally, point, polygon, and polyline barriers. Results of a solved route are accessible from the directionLines, directionPoints, and routeInfo properties. Results include overall travel time, distance, and turn-by-turn directions.
Example
// Routing with the RouteLayer's default route service requires an apikey.const apiKey = "<your api key>";
// A minimum of two stops is required for routing.const stops = [ new Stop({ geometry: { x: -117.1825, y: 34.054722 }}), new Stop({ geometry: { x: -116.545278, y: 33.830278 }})];
// Create route layer and assign the stops. Only solved routelayers will be rendered.const routeLayer = new RouteLayer({ stops});
// Create a view and add the routelayer to the view's map.const view = new MapView({ container: "viewDiv", map: new Map({ basemap: "dark-gray-vector", layers: [ routeLayer ] })});
// Wait for the view to load since we'll be zooming to the extent of the zoomed solution.view.when().then(async () => { // Solve the route using routelayer stops and barries and additional properties from the parsed RouteParameters // object. Use the RouteParameters to provide the apiKey and other setting like directions language and travel // mode. const results = await routeLayer.solve({ apiKey });
// Use the returned result to update the RouteLayer. This method will overwrite the stops, barriers, directions and // routeInfo properties. routeLayer.update(results);
// Zoom to the extent of the solve route. view.goTo(routeLayer.routeInfo.geometry);});Constructors
Constructor
Parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| properties | | |
Properties
| Property | Type | Class |
|---|---|---|
blendMode inherited | ||
declaredClass readonly inherited | ||
| | ||
directionLines readonly | | |
directionPoints readonly | | |
effect inherited | ||
fullExtent readonly | | |
id inherited | ||
listMode inherited | ||
loaded readonly inherited | ||
loadError readonly inherited | ||
loadStatus readonly inherited | "not-loaded" | "loading" | "failed" | "loaded" | |
loadWarnings readonly inherited | any[] | |
maxScale inherited | ||
minScale inherited | ||
opacity inherited | ||
parent inherited | Map | Basemap | Ground | GroupLayer | CatalogDynamicGroupLayer | CatalogLayer | null | undefined | |
persistenceEnabled inherited | ||
| | ||
| | ||
| | ||
portalItem inherited | PortalItem | null | undefined | |
routeInfo readonly | | |
| | ||
| | ||
type readonly | "route" | |
uid readonly inherited | ||
| | ||
visibilityTimeExtent inherited | TimeExtent | null | undefined | |
visible inherited |
blendMode
- Type
- BlendMode
Blend modes are used to blend layers together to create an interesting effect in a layer, or even to produce what seems like a new layer. Unlike the method of using transparency which can result in a washed-out top layer, blend modes can create a variety of very vibrant and intriguing results by blending a layer with the layer(s) below it.
When blending layers, a top layer is a layer that has a blend mode applied. All layers underneath the top layer are background layers.
The default blending mode is normal where the top layer is simply displayed over the background layer. While this default behavior is perfectly acceptable,
the use of blend modes on layers open up a world of endless possibilities to generate creative maps.
The layers in a GroupLayer are blended together in isolation from the rest of the map.
In the following screenshots, the vintage shaded relief
layer is displayed over a firefly world imagery layer. The color blend mode
is applied to the vintage shaded relief and the result looks like a new layer.
Known Limitations
- In 3D SceneViews, the blendMode is supported on BaseTileLayer, ImageryTileLayer, OpenStreetMapLayer, TileLayer, VectorTileLayer, WCSLayer, WebTileLayer, WMTSLayer and GroupLayer.
- When working with GroupLayers in a 3D SceneView, the blendMode is only applied to the sublayers that support it.
- The blendMode is not supported in the Legend.
- See print for known printing limitations.
The following factors will affect the blend result:
- Order of all layers
- Layer opacity
- Opacity of features in layers
- Visibility of layers
- By default, the very bottom layer in a map is drawn on a transparent background. You can change the MapView's background color.
Read More
| Blend mode | Description |
|---|---|
| normal | The top layer is displayed over the background layer. The data of the top layer block the data of background layer where they overlap. |
| average | Takes the mathematical average of top and background layers. Result of average blend mode is often similar to the effect of setting the layer's opacity to 50%. |
Lighten blend modes:
The following blend modes create lighter results than all layers. In lighten blend modes, pure black colors in the top layer become transparent allowing the background layer to show through. White in the top layer will stay unchanged. Any color that is lighter than pure black is going to lighten colors in the top layer to varying degrees all way to pure white.
Lighten blend modes can be useful when lightening dark colors of the top layer or removing black colors from the result.
The plus, lighten and screen modes can be used to brighten layers that have faded or dark colors on a dark background.
| Blend mode | Description |
|---|---|
| lighten | Compares top and background layers and retains the lighter color. Colors in the top layer become transparent if they are darker than the overlapping colors in the background layer allowing the background layer to show through completely. Can be thought of as the opposite of darken blend mode. |
| lighter | Colors in top and background layers are multiplied by their alphas (layer opacity and layer's data opacity. Then the resulting colors are added together. All overlapping midrange colors are lightened in the top layer. The opacity of layer and layer's data will affect the blend result. |
| plus | Colors in top and background layers are added together. All overlapping midrange colors are lightened in the top layer. This mode is also known as add or linear-dodge. |
| screen | Multiplies inverted colors in top and background layers then inverts the colors again. The resulting colors will be lighter than the original color with less contrast. Screen can produce many different levels of brightening depending on the luminosity values of the top layer. Can be thought of as the opposite of the multiply mode. |
| color-dodge | Divides colors in background layer by the inverted top layer. This lightens the background layer depending on the value of the top layer. The brighter the top layer, the more its color affects the background layer. Decreases the contrast between top and background layers resulting in saturated mid-tones and blown highlights. |
Darken blend modes:
The following blend modes create darker results than all layers. In darken blend modes, pure white in the top layer will become transparent allowing the background layer to show through. Black in the top layer will stay unchanged. Any color that is darker than pure white is going to darken a top layer to varying degrees all the way to pure black.
The multiply blend mode is often used to highlight shadows, show contrast, or accentuate an aspect of a map. For example, you can use multiply blend mode on a topographic map
displayed over hillshade when you want to have your elevation show through the topographic layer. See the intro to layer blending sample.
The multiply and darken modes can be used to have dark labels of the basemap to show through top layers. See the darken blending sample.
The color-burn mode works well with colorful top and background layers since it increases saturation in mid-tones. It increases the contrast by tinting pixels in overlapping areas in
top and bottom layers more towards the top layer color. Use this blend mode, when you want an effect with more contrast than multiply or darken.
The following screenshots show how the multiply blend mode used for creating a physical map of the world that shows both boundaries and elevation.

| Blend mode | Description |
|---|---|
| darken | Emphasizes the darkest parts of overlapping layers. Colors in the top layer become transparent if they are lighter than the overlapping colors in the background layer, allowing the background layer to show through completely. |
| multiply | Emphasizes the darkest parts of overlapping layers by multiplying colors of the top layer and the background layer. Midrange colors from top and background layers are mixed together more evenly. |
| color-burn | Intensifies the dark areas in all layers. It increases the contrast between top and background layers, by tinting colors in overlapping area towards the top color. To do this it inverts colors of the background layer, divides the result by colors of the top layer, then inverts the results. |
Contrast blend modes:
The following blend modes create contrast by both lightening the lighter areas and darkening the darker areas in the top layer by using lightening or darkening blend modes to create the blend.
The contrast blend modes will lighten the colors lighter than 50% gray ([128,128,128]), and darken the colors darker than 50% gray. 50% gray will be transparent in the top layer.
Each mode can create a variety of results depending on the colors of top and background layers being blended together.
The overlay blend mode makes its calculations based on the brightness of the colors in the background layer while all of the other contrast blend modes make their calculations based on the brightness of the top layer.
Some of these modes are designed to simulate the effect of shining a light through the top layer, effectively projecting upon the layers beneath it.
Contrast blend modes can be used to increase the contrast and saturation to have more vibrant colors and give a punch to your layers.
For example, you can duplicate a layer and set overlay blend mode on the top layer to increase the contrast and tones of your layer.
You can also add a polygon layer with a white fill symbol over a dark imagery layer and apply soft-light blend mode to increase the brightness in the imagery layer.
The following screenshots show an effect of the overlay blend mode on a GraphicsLayer. The left image shows when the buffer graphics layer has the normal blend mode.
As you can see, the gray color for the buffer polygon is blocking the intersecting census tracts. The right image shows when the overlay blend mode is applied to the buffer graphics layer.
The overlay blend mode darkens or lightens the gray buffer polygon depending on the colors of the background layer while the census tracts layer is shining through.
See this in action.
| Normal blend mode | Overlay blend mode |
|---|---|
![]() | ![]() |
| Blend mode | Description |
|---|---|
| overlay | Uses a combination of multiply and screen modes to darken and lighten colors in the top layer with the background layer always shining through. The result is darker color values in the background layer intensify the top layer, while lighter colors in the background layer wash out overlapping areas in the top layer. |
| soft-light | Applies a half strength screen mode to lighter areas and half strength multiply mode to darken areas of the top layer. You can think of the soft-light as a softer version of the overlay mode. |
| hard-light | Multiplies or screens the colors, depending on colors of the top layer. The effect is similar to shining a harsh spotlight on the top layer. |
| vivid-light | Uses a combination of color-burn or color-dodge by increasing or decreasing the contrast, depending on colors in the top layer. |
Component blend modes:
The following blend modes use primary color components, which are hue, saturation and luminosity to blend top and background layers.
You can add a feature layer with a simple renderer over any layer and set hue, saturation, color or luminosity blend mode on this layer. With this technique, you create a brand new looking map.
The following screenshots show where the topo layer is blended with
world hillshade layer with luminosity blend mode.
The result is a drastically different looking map which preserves the brightness of the topo layer while adapting the hue and saturation of the hillshade layer.
| Blend mode | Description |
|---|---|
| hue | Creates an effect with the hue of the top layer and the luminosity and saturation of the background layer. |
| saturation | Creates an effect with the saturation of the top layer and the hue and luminosity of the background layer. 50% gray with no saturation in the background layer will not produce any change. |
| luminosity | Creates effect with the luminosity of the top layer and the hue and saturation of the background layer. Can be thought of as the opposite of color blend mode. |
| color | Creates an effect with the hue and saturation of the top layer and the luminosity of the background layer. Can be thought of as the opposite of luminosity blend mode. |
Composite blend modes:
The following blend modes can be used to mask the contents of top, background or both layers.
Destinationmodes are used to mask the data of the top layer with the data of the background layer.Sourcemodes are used to mask the data of the background layer with the data of the top layer.
The destination-in blend mode can be used to show areas of focus such as earthquakes, animal migration, or point-source pollution by revealing the underlying map,
providing a bird's eye view of the phenomenon. Check out multiple blending and groupLayer blending
samples to see composite blend modes in action.
The following screenshots show feature and imagery layers on the left side on their own in the order they are drawn in the view. The imagery layer that contains land cover classification rasters.
The feature layer contains 2007 county crops data. The right image shows the result of layer blending where destination-in blendMode is set on the imagery layer. As you can see, the effect is
very different from the original layers. The blended result shows areas of cultivated crops only (where both imagery and feature layers overlap).
| Blend mode | Description |
|---|---|
| destination-over | Destination/background layer covers the top layer. The top layer is drawn underneath the destination layer. You'll see the top layer peek through wherever the background layer is transparent or has no data. |
| destination-atop | Destination/background layer is drawn only where it overlaps the top layer. The top layer is drawn underneath the background layer. You'll see the top layer peek through wherever the background layer is transparent or has no data. |
| destination-in | Destination/background layer is drawn only where it overlaps with the top layer. Everything else is made transparent. |
| destination-out | Destination/background layer is drawn where it doesn't overlap the top layer. Everything else is made transparent. |
| source-atop | Source/top layer is drawn only where it overlaps the background layer. You will see the background layer peek through where the source layer is transparent or has no data. |
| source-in | Source/top layer is drawn only where it overlaps with the background layer. Everything else is made transparent. |
| source-out | Source/top layer is drawn where it doesn't overlap the background layer. Everything else is made transparent. |
| xor | Top and background layers are made transparent where they overlap. Both layers are drawn normal everywhere else. |
Invert blend modes:
The following blend modes either invert or cancel out colors depending on colors of the background layer.
These blend modes look for variations between top and background layers.
For example, you can use difference or exclusion blend modes on two imagery layers of forest covers to visualize how forest covers changed from one year to another.
The invert blend mode can be used to turn any light basemap into a dark basemap to accommodate those who work in low-light conditions. The following screenshots show
how setting the invert blend mode set on a feature layer with a simple renderer turns the world Hillshade
into a dark themed basemap in no time.
| Blend mode | Description |
|---|---|
| difference | Subtracts the darker of the overlapping colors from the lighter color. When two pixels with the same value are subtracted, the result is black. Blending with black produces no change. Blending with white inverts the colors. This blending mode is useful for aligning layers with similar content. |
| exclusion | Similar to the difference blend mode, except that the resulting image is lighter overall. Overlapping areas with lighter color values are lightened, while darker overlapping color values become transparent. |
| minus | Subtracts colors of the top layer from colors of the background layer making the blend result darker. In the case of negative values, black is displayed. |
| invert | Inverts the background colors wherever the top and background layers overlap. The invert blend mode inverts the layer similar to a photographic negative. |
| reflect | This blend mode creates effects as if you added shiny objects or areas of light in the layer. Black pixels in the background layer are ignored as if they were transparent. |
- See also
- Default value
- "normal"
defaultSymbols
- Type
- RouteSymbols
- Since
- ArcGIS Maps SDK for JavaScript 4.24
The default symbol used for new stops and route results generated by solve().
Example
// When a route is solved, display the direction lines with a thick cyan line and hide both diection points and the// overall route line.const layer = new RouteLayer({ defaultSymbols: { directionLines: { type: "simple-line", color: [105, 220, 255], width: 7, cap: "round", join: "round" }, directionPoints: { type: "simple-marker", size: 0 }, routeInfo: { type: "simple-line", width: 0 } }}); directionLines
- Type
- Collection<DirectionLine> | null | undefined
A collection of DirectionLine that represent the linear path between directionPoints of the solved route.
directionPoints
- Type
- Collection<DirectionPoint> | null | undefined
A collection of DirectionPoint that represent the turn-by-turn directions along a solved route.
effect
Effect provides various filter functions that can be performed on the layer to achieve different visual effects similar to
how image filters work. This powerful capability allows you to apply css filter-like
functions to layers to create custom visual effects to enhance the cartographic quality of your maps. This is done by applying the desired
effect to the layer's effect property as a string or an array of objects to set scale dependent effects.
Notes
Set featureEffect property on a layer if different effects need to be applied features that meet or fail a specified filter. If all of the following four properties are applied, then they will be applied in this order: featureEffect, effect, opacity and blendMode.
Known Limitations
- The effect is not supported in 3D SceneViews.
- The effect cannot be applied to a layer with a heatmap renderer.
- The effect is not supported in layers with FeatureLayer.featureReduction of type
clusterenabled. - See print for known printing limitations.
Examples
// the following effect will be applied to the layer at all scales// brightness will be applied first, then hue-rotate followed by contrast// changing order of the effects will change the final resultlayer.effect = "brightness(5) hue-rotate(270deg) contrast(200%)";// set a scale dependent bloom effect on the layerlayer.effect = [ { scale: 36978595, value: "drop-shadow(3px, 3px, 4px)" }, { scale: 18489297, value: "drop-shadow(2px, 2px, 3px)" }, { scale: 4622324, value: "drop-shadow(1px, 1px, 2px)" }]; fullExtent
- Type
- Extent
The full extent of the layer.
Example
// Once the layer loads, set the view's extent to the layer's full extentlayer.when(function(){ view.extent = layer.fullExtent;}); listMode
- Type
- LayerListMode
Indicates how the layer should display in the Layer List component. The possible values are listed below.
| Value | Description |
|---|---|
| show | The layer is visible in the table of contents. |
| hide | The layer is hidden in the table of contents. |
| hide-children | If the layer is a GroupLayer, BuildingSceneLayer, KMLLayer, MapImageLayer, SubtypeGroupLayer, TileLayer, or WMSLayer, hide the children layers from the table of contents. |
- Default value
- "show"
loadError
The Error object returned if an error occurred while loading.
loadStatus
- Type
- "not-loaded" | "loading" | "failed" | "loaded"
Represents the status of a load() operation.
| Value | Description |
|---|---|
| not-loaded | The object's resources have not loaded. |
| loading | The object's resources are currently loading. |
| loaded | The object's resources have loaded without errors. |
| failed | The object's resources failed to load. See loadError for more details. |
- Default value
- "not-loaded"
loadWarnings
- Type
- any[]
A list of warnings which occurred while loading.
maxScale
- Type
- number
The maximum scale (most zoomed in) at which the layer is visible in the view.
If the map is zoomed in beyond this scale, the layer will not be visible.
A value of 0 means the layer does not have a maximum scale.
The maxScale value should always be smaller than the minScale value,
and greater than or equal to the service specification.
- Default value
- 0
Examples
// The layer will not be visible when the view is zoomed in beyond a scale of 1:1,000layer.maxScale = 1000;// The layer's visibility is not restricted to a maximum scale.layer.maxScale = 0; minScale
- Type
- number
The minimum scale (most zoomed out) at which the layer is visible in the view.
If the map is zoomed out beyond this scale, the layer will not be visible.
A value of 0 means the layer does not have a minimum scale.
The minScale value should always be larger than the maxScale value,
and lesser than or equal to the service specification.
- Default value
- 0
Examples
// The layer will not be visible when the view is zoomed out beyond a scale of 1:3,000,000layer.minScale = 3000000;// The layer's visibility is not restricted to a minimum scale.layer.minScale = 0; opacity
- Type
- number
The opacity of the layer. This value can range between 1 and 0, where 0 is 100 percent
transparent and 1 is completely opaque.
Known Limitations
In a 3D SceneView, modifying opacity is not supported for DimensionLayer, GaussianSplatLayer, IntegratedMesh3DTilesLayer, IntegratedMeshLayer, LineOfSightLayer, PointCloudLayer, ViewshedLayer, and VoxelLayer.
- Default value
- 1
Example
// Makes the layer 50% transparentlayer.opacity = 0.5; parent
- Type
- Map | Basemap | Ground | GroupLayer | CatalogDynamicGroupLayer | CatalogLayer | null | undefined
- Since
- ArcGIS Maps SDK for JavaScript 4.27
The parent to which the layer belongs.
persistenceEnabled
- Type
- boolean
- Default value
- true
pointBarriers
- Type
- Collection<PointBarrier>
A collection of PointBarrier are used to prevent navigation through the street network.
polygonBarriers
- Type
- Collection<PolygonBarrier>
A collection of PolygonBarrier are used to prevent navigation through the street network.
polylineBarriers
- Type
- Collection<PolylineBarrier>
A collection of PolylineBarrier are used to prevent navigation through the street network.
portalItem
- Type
- PortalItem | null | undefined
The portal item from which the layer is loaded. If the portal item references
a feature or scene service, then you can specify a single layer
to load with the layer's layerId property.
Loading non-spatial tables
Non-spatial tables can be loaded from service items hosted in ArcGIS Online and ArcGIS Enterprise. This only applies to:
- FeatureLayer if the layer's isTable returns
trueat version 4.17. - SubtypeGroupLayer if the layer's isTable returns
trueat version 4.32.
Examples
// While this example uses FeatureLayer, this same pattern can be// used for other layers that may be loaded from portalItem ids.const layer = new FeatureLayer({ portalItem: { // autocasts as new PortalItem() id: "caa9bd9da1f4487cb4989824053bb847" } // the first layer in the service is returned});// Set hostname when using an on-premise portal (default is ArcGIS Online)// esriConfig.portalUrl = "http://myHostName.esri.com/arcgis";
// While this example uses FeatureLayer, this same pattern can be// used for SceneLayers.const layer = new FeatureLayer({ portalItem: { // autocasts as new PortalItem() id: "8d26f04f31f642b6828b7023b84c2188" }, // loads the third item in the given feature service layerId: 2});// Initialize GeoJSONLayer by referencing a portalItem id pointing to geojson file.const layer = new GeoJSONLayer({ portalItem: new PortalItem({ id: "81e769cd7031482797e1b0768f23c7e1", // optionally define the portal, of the item. // if not specified, the default portal defined is used. // see https://developers.arcgis.com/javascript/latest/references/core/config/#portalUrl portal: new Portal({ url: "https://jsapi.maps.arcgis.com/" }) }});// This snippet loads a table hosted in ArcGIS Online.const table = new FeatureLayer({ portalItem: { // autocasts as esri/portal/PortalItem id: "123f4410054b43d7a0bacc1533ceb8dc" }});
// Before adding the table to the map, it must first be loaded and confirm it is the right type.table.load().then(() => { if (table.isTable) { map.tables.add(table); }});// While this example uses FeatureLayer, this same pattern can be// used for other layers that may be loaded from portalItem ids.const layer = new FeatureLayer({ portalItem: { // autocasts as esri/portal/PortalItem id: "caa9bd9da1f4487cb4989824053bb847", // Set an API key to access a secure portal item configured with API key authentication. apiKey: "APIKEY" }}); stops
- Type
- Collection<Stop>
A collection of Stops define the start, end, waypoint, or break of the route.
Example
// Define a route between Cancun Airport and Playa del Carmen with a break at Chichén Itzá.const routeLayer = new RouteLayer({ stops: [ { locationType: "stop", geometry: { x: -86.9074392, y: 21.0847238 } }, // Cancun Airport { locationType: "break", geometry: { x: -88.1331506, y: 20.6354437 } }, // Chichén Itzá { locationType: "stop", geometry: { x: -87.1067159, y: 20.6538687 } } // Playa del Carmen ]}); uid
- Type
- string
- Since
- ArcGIS Maps SDK for JavaScript 4.33
An automatically generated unique identifier assigned to the instance. The unique id is generated each time the application is loaded.
url
- Type
- string
The URL of the REST endpoint of the Route service.
By default, the layer will use the global routing serice (see Config).
If connected to a Portal you can use the route service advertised on the portal's helper services as demonstrated below.
- See also
Examples
// Solve routes using the route service advertised on the portalconst portal = Portal.getDefault();await portal.load();const routeLayer = new RouteLayer({ url: portal.helperServices.route.url});// Solve routes using a defined route serviceconst routeLayer = new RouteLayer({ url: "https://route-api.arcgis.com/arcgis/rest/services/World/Route/NAServer/Route_World"}); visibilityTimeExtent
- Type
- TimeExtent | null | undefined
- Since
- ArcGIS Maps SDK for JavaScript 4.30
Specifies a fixed time extent during which a layer should be visible. This property can be used to configure a layer that does not have time values stored in an attribute field to work with time. Once configured, the TimeSlider widget will display the layer within the set time extent. In the case that only one of the TimeExtent.start or TimeExtent.end date values are available, the layer remains visible indefinitely in the direction where there is no time value.
Aerial imagery can capture seasonal variations in vegetation, water bodies, and land use patterns. For example, in agricultural regions, aerial imageries taken during different growing seasons provide insights into crop health and productivity. Defining a fixed time extent on imageries from specific time periods provides temporal context and facilitates focused analysis based on specific time periods or events.
visible
- Type
- boolean
Indicates if the layer is visible in the View. When false,
the layer may still be added to a Map
instance that is referenced in a view, but its features will not be visible in the view.
- Default value
- true
Example
// The layer is no longer visible in the viewlayer.visible = false;
// Watch for changes in the layer's visibility// and set the visibility of another layer when it changesreactiveUtils.watch( () => layer.visible, (visible) => { if (visible) { anotherLayer.visible = true; } else { anotherLayer.visible = false; } });Methods
| Method | Signature | Class |
|---|---|---|
fromArcGISServerUrl inherited static | fromArcGISServerUrl(params: string | FromArcGISServerUrlParameters): Promise<Layer> | |
fromPortalItem inherited static | fromPortalItem(params: LayerFromPortalItemParameters): Promise<Layer> | |
cancelLoad inherited | cancelLoad(): this | |
createLayerView inherited | createLayerView<T extends LayerView = LayerView>(view: View<T>, options?: AbortOptions): Promise<T> | |
destroy inherited | destroy(): void | |
emit inherited | emit<Type extends EventNames<this>>(type: Type, event?: this["@eventTypes"][Type]): boolean | |
fetchAttributionData inherited | fetchAttributionData(): Promise<any> | |
hasEventListener inherited | hasEventListener<Type extends EventNames<this>>(type: Type): boolean | |
isFulfilled inherited | isFulfilled(): boolean | |
isRejected inherited | isRejected(): boolean | |
isResolved inherited | isResolved(): boolean | |
load inherited | load(options?: AbortOptions | null | undefined): Promise<this> | |
on inherited | on<Type extends EventNames<this>>(type: Type, listener: EventedCallback<this["@eventTypes"][Type]>): ResourceHandle | |
save(): Promise<PortalItem> | | |
saveAs(portalItem: PortalItem, options?: LayerSaveAsOptions): Promise<PortalItem> | | |
solve(routeParameters?: RouteParameters, requestOptions?: RequestOptions): Promise<RouteLayerSolveResult> | | |
update(routeLayerSolveResult: RouteLayerSolveResult): void | | |
when inherited | when<TResult1 = this, TResult2 = never>(onFulfilled?: OnFulfilledCallback<this, TResult1> | null | undefined, onRejected?: OnRejectedCallback<TResult2> | null | undefined): Promise<TResult1 | TResult2> |
fromArcGISServerUrl
- Signature
-
fromArcGISServerUrl (params: string | FromArcGISServerUrlParameters): Promise<Layer>
Creates a new layer instance from an ArcGIS Server URL. Depending on the URL, the returned layer type may be a BuildingSceneLayer, CatalogLayer, ElevationLayer, FeatureLayer, GroupLayer, ImageryLayer, ImageryTileLayer, IntegratedMeshLayer, KnowledgeGraphLayer, MapImageLayer, OrientedImageryLayer, PointCloudLayer, SceneLayer, StreamLayer, SubtypeGroupLayer, TileLayer, or VideoLayer.
This is useful when you work with various ArcGIS Server URLs, but you don't necessarily know which layer type(s) they create. This method creates the appropriate layer type for you. In case of a feature service or a scene service, when the URL points to the service and the service has multiple layers, the returned promise will resolve to a GroupLayer.
Beginning with version 4.17, it is possible to load tables from hosted feature services.
This only applies to feature layers, and will successfully load if FeatureLayer.isTable returns true.
The following table details what is returned when loading specific URL types.
| URL | Returns |
|---|---|
| Feature service with one layer | FeatureLayer where FeatureLayer.isTable returns false. |
| Feature service with one table | FeatureLayer where FeatureLayer.isTable returns true. |
| Feature service with more than one layer(s)/table(s) | GroupLayer with layers and tables. |
| Layers with type other than "Feature Layer" are discarded, e.g. Utility Network Layers | N/A |
- See also
Parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| params | Input parameters for creating the layer. | |
Examples
// This snippet shows how to add a feature layer from an ArcGIS Server URL// Get an ArcGIS Server URL from a custom functionconst arcgisUrl = getLayerUrl();
Layer.fromArcGISServerUrl({ url: arcgisUrl, properties: { // set any layer properties here popupTemplate: new PopupTemplate() }}).then(function(layer){ // add the layer to the map map.add(layer);});// This snippet shows how to add a table from an ArcGIS Server URL// Get an ArcGIS Server URL from a custom functionconst arcgisUrl = getLayerUrl();
Layer.fromArcGISServerUrl({ url: arcgisUrl}).then(function(layer){ // Load the table before it can be used layer.load().then(function() { // Check that it is the right type if (layer.isTable) { // Add table to map's tables collection map.tables.add(layer); } });}); fromPortalItem
- Signature
-
fromPortalItem (params: LayerFromPortalItemParameters): Promise<Layer>
Creates a new layer instance of the appropriate layer class from an ArcGIS Online or ArcGIS Enterprise portal item. If the item points to a feature service with multiple layers, then a GroupLayer is created. If the item points to a service with a single layer, then it resolves to a layer of the same type of class as the service.
Note
- At version 4.29, MediaLayer can be loaded from portal items.
- At version 4.28, GroupLayer and OrientedImageryLayer can be loaded from portal items.
- At version 4.25, CSVLayer and GeoJSONLayer can be loaded from CSV and GeoJSON portal items respectively.
- At version 4.17, it is possible to load tables from feature service items hosted in ArcGIS Online and ArcGIS Enterprise.
This only applies to feature layers, and will successfully load
if FeatureLayer.isTable returns
true.
The following table details what is returned when loading specific item types.
| Item(s) | Returns |
|---|---|
| Feature service with one layer | FeatureLayer where FeatureLayer.isTable returns false. |
| Feature service with one table | FeatureLayer where FeatureLayer.isTable returns true. |
| Feature service with more than one layer(s)/table(s) | GroupLayer with layers and tables. |
| Feature collection with one layer | FeatureLayer where FeatureLayer.isTable returns false. |
| Feature collection with one table | FeatureLayer where FeatureLayer.isTable returns true. |
| Feature collection with more than one layer(s)/table(s) | GroupLayer with layers and tables. |
Known Limitations
- This method does not currently work with OGCFeatureServer portal items.
Parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| params | The parameters for loading the portal item. | |
Examples
// Create a layer from a specified portal item and add to the mapLayer.fromPortalItem({ portalItem: { // autocasts new PortalItem() id: "8444e275037549c1acab02d2626daaee" }}).then(function(layer){ // add the layer to the map map.add(layer);});// Create a table from a specified portal item and add it to the map's tables collectionLayer.fromPortalItem({ portalItem: { // autocasts new PortalItem() id: "123f4410054b43d7a0bacc1533ceb8dc" // This is a hosted table stored in a feature service }}).then(function(layer) { // Necessary to load the table in order for it to be read correctly layer.load().then(function() { // Confirm this reads as a table if (layer.isTable) { // Add the new table to the map's table collection map.tables.add(layer); } });}); cancelLoad
- Signature
-
cancelLoad (): this
Cancels a load() operation if it is already in progress.
- Returns
- this
createLayerView
- Signature
-
createLayerView <T extends LayerView = LayerView>(view: View<T>, options?: AbortOptions): Promise<T>
Called by the views, such as MapView and SceneView, when the layer is added to the Map.layers collection and a layer view must be created for it. This method is used internally and there is no use case for invoking it directly.
- See also
Parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| view | The parent view. | | |
| options | An object specifying additional options. See the object specification table below for the required properties of this object. | |
destroy
- Signature
-
destroy (): void
Destroys the layer and any associated resources (including its portalItem, if it is a property on the layer). The layer can no longer be used once it has been destroyed.
The destroyed layer will be removed from its parent object like Map, WebMap, WebScene, Basemap, Ground, or GroupLayer.
- Returns
- void
emit
- Signature
-
emit <Type extends EventNames<this>>(type: Type, event?: this["@eventTypes"][Type]): boolean
- Type parameters
- <Type extends EventNames<this>>
Emits an event on the instance. This method should only be used when creating subclasses of this class.
hasEventListener
- Signature
-
hasEventListener <Type extends EventNames<this>>(type: Type): boolean
- Type parameters
- <Type extends EventNames<this>>
Indicates whether there is an event listener on the instance that matches the provided event name.
Parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| type | Type | The name of the event. | |
- Returns
- boolean
Returns true if the class supports the input event.
isFulfilled
- Signature
-
isFulfilled (): boolean
isFulfilled() may be used to verify if creating an instance of the class is fulfilled (either resolved or rejected).
If it is fulfilled, true will be returned.
- Returns
- boolean
Indicates whether creating an instance of the class has been fulfilled (either resolved or rejected).
isRejected
- Signature
-
isRejected (): boolean
isRejected() may be used to verify if creating an instance of the class is rejected.
If it is rejected, true will be returned.
- Returns
- boolean
Indicates whether creating an instance of the class has been rejected.
isResolved
- Signature
-
isResolved (): boolean
isResolved() may be used to verify if creating an instance of the class is resolved.
If it is resolved, true will be returned.
- Returns
- boolean
Indicates whether creating an instance of the class has been resolved.
load
- Signature
-
load (options?: AbortOptions | null | undefined): Promise<this>
Loads the resources referenced by this class. This method automatically executes for a View and all of the resources it references in Map if the view is constructed with a map instance.
This method must be called by the developer when accessing a resource that will not be loaded in a View.
The load() method only triggers the loading of the resource the first time it is called. The subsequent calls return the same promise.
It's possible to provide a signal to stop being interested into a Loadable instance load status.
When the signal is aborted, the instance does not stop its loading process, only cancelLoad() can abort it.
on
- Signature
-
on <Type extends EventNames<this>>(type: Type, listener: EventedCallback<this["@eventTypes"][Type]>): ResourceHandle
- Type parameters
- <Type extends EventNames<this>>
Registers an event handler on the instance. Call this method to hook an event with a listener.
Parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| type | Type | An event or an array of events to listen for. | |
| listener | EventedCallback<this["@eventTypes"][Type]> | The function to call when the event fires. | |
- Returns
- ResourceHandle
Returns an event handler with a
remove()method that should be called to stop listening for the event(s).Property Type Description remove Function When called, removes the listener from the event.
Example
view.on("click", function(event){ // event is the event handle returned after the event fires. console.log(event.mapPoint);}); save
- Signature
-
save (): Promise<PortalItem>
Update the currently assigned portal item using information in this RouteLayer.
- See also
- Returns
- Promise<PortalItem>
Saved portal item.
Example
// Create a route layer from an existing route portal itemconst routeLayer = await Layer.fromPortalItem({ portalItem: { id: "3828dfec3a0749a1b1aff9e2fa53157c" }});
// Add the route layer to a mapmap.add(routeLayer);
// Wait for both the view and route layer to loadawait view.whenLayerView(routeLayer);
// Zoom to the extent of the route layerawait view.goTo(routeLayer.fullExtent);
// Update the route portal item on mouse clickview.on("click", async (event) => { // Reset the route layer's stops with the mouse click location being a waypoint routeLayer.stops = [ { geometry: { x: -86.9074392, y: 21.0847238 } }, // Cancun Airport { geometry: event.mapPoint }, // Mouse click location { geometry: { x: -88.1331506, y: 20.6354437 } } // Chichén Itzá ];
// Solve the route const result = await routeLayer.solve({ apiKey });
// Use the results of the solve to update the route layer routeLayer.update(result);
// Refresh the route portal-item using the route layer await routeLayer.save();}); saveAs
- Signature
-
saveAs (portalItem: PortalItem, options?: LayerSaveAsOptions): Promise<PortalItem>
Saves the route layer to a new portal item. If saving is completed successfully the new portal item will be assigned to the portalItem property.
If you want to update an existing portal item without changing ownership please use save().
- See also
Parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| portalItem | The new portal item to which the layer will be saved. | | |
| options | Save options. Currently, there is only one property that can be set, which is | |
- Returns
- Promise<PortalItem>
Saved portal item.
Example
// Create a route between Cancun Airport and Chichén Itzá// Save the route to AGOL as a new route portal item
const apiKey = "<your api key here>";
const routeLayer = new RouteLayer({ stops: [ { geometry: { x: -86.9074392, y: 21.0847238 } }, // Cancun Airport { geometry: { x: -88.1331506, y: 20.6354437 } } // Chichén Itzá ]});
const webMap = new WebMap({ basemap: "dark-gray-vector", layers: [ routeLayer ]});
const view = new MapView({ container: "viewDiv", map: webMap});await view.when();
const result = await routeLayer.solve({ apiKey });routeLayer.update(result);
const extent = routeLayer.routeInfo.geometry.extent.clone().expand(1.5);await view.goTo(extent);
await routeLayer.saveAs({ title: "Route from Cancun Airport to Chichén Itzá"}); solve
- Signature
-
solve (routeParameters?: RouteParameters, requestOptions?: RequestOptions): Promise<RouteLayerSolveResult>
This method will solve the route using the route service referenced by url and the network objects pointBarriers, polylineBarriers, polygonBarriers, and stops.
Pass a reference to a RouteParameters to specify or override route settings such as RouteParameters.travelMode or the stops used. If a global apiKey is not defined, the RouteParameters.apiKey property can be used.
- See also
Parameters
| Parameter | Type | Description | Required | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| routeParameters | The following properties are preset and cannot be overridden:
The following properties will also be set automatically, but can be overridden:
| | |||||||||||||||||||||||||||||||
| requestOptions | Additional options to be used for the data request (will override requestOptions defined during construction). | |
- Returns
- Promise<RouteLayerSolveResult>
When resolved, returns a RouteLayerSolveResult.
Example
// Solve and display a route between Cancun Airport and Chichén Itzá.const apiKey = "<your api key>"
// Create a route consisting of two stops.const routeLayer = new RouteLayer({ stops: [ { geometry: { x: -86.9074392, y: 21.0847238 } }, // Cancun Airport { geometry: { x: -88.1331506, y: 20.6354437 } } // Chichén Itzá ]});
const map = new Map({ basemap: "dark-gray-vector", layers: [routeLayer]});
const view = new MapView({ container: "viewDiv", map});await view.when();
// Solve the route and use the results to update the layer.const result = await routeLayer.solve({ apiKey });routeLayer.update(result);
// Zoom to the extent of the solved route.view.goTo(routeLayer.routeInfo.geometry); update
- Signature
-
update (routeLayerSolveResult: RouteLayerSolveResult): void
Updates the layer with the results from a solved route layer.
- See also
Parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| routeLayerSolveResult | The results from a solved route layer. | |
- Returns
- void
when
- Signature
-
when <TResult1 = this, TResult2 = never>(onFulfilled?: OnFulfilledCallback<this, TResult1> | null | undefined, onRejected?: OnRejectedCallback<TResult2> | null | undefined): Promise<TResult1 | TResult2>
when() may be leveraged once an instance of the class is created. This method takes two input parameters: an onFulfilled function and an onRejected function.
The onFulfilled executes when the instance of the class loads. The
onRejected executes if the instance of the class fails to load.
Parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| onFulfilled | OnFulfilledCallback<this, TResult1> | null | undefined | The function to call when the promise resolves. | |
| onRejected | The function to execute when the promise fails. | |
- Returns
- Promise<TResult1 | TResult2>
Returns a new promise for the result of
onFulfilledthat may be used to chain additional functions.
Example
// Although this example uses MapView, any class instance that is a promise may use when() in the same waylet view = new MapView();view.when(function(){ // This function will execute once the promise is resolved}, function(error){ // This function will execute if the promise is rejected due to an error});Events
| Name | Type |
|---|---|
layerview-create inherited | |
layerview-create-error inherited | |
layerview-destroy inherited |
layerview-create
layerview-create: CustomEvent<LayerLayerviewCreateEvent> Fires after the layer's LayerView is created and rendered in a view.
- See also
Example
// This function will fire each time a layer view is created for this// particular view.layer.on("layerview-create", function(event){ // The LayerView for the layer that emitted this event event.layerView;}); layerview-create-error
layerview-create-error: CustomEvent<LayerLayerviewCreateErrorEvent> Fires when an error emits during the creation of a LayerView after a layer has been added to the map.
- See also
Example
// This function fires when an error occurs during the creation of the layer's layerviewlayer.on("layerview-create-error", function(event) { console.error("LayerView failed to create for layer with the id: ", layer.id, " in this view: ", event.view);}); layerview-destroy
layerview-destroy: CustomEvent<LayerLayerviewDestroyEvent> Fires after the layer's LayerView is destroyed and no longer renders in a view.

