Print
5.4.1 TileLayer
Description:
- displays a full dataset using a series of adjacent tiles (smaller individual images that you can think of as snapshots of the complete map)
- a different set of tiles is created for each level of detail (zoom level)
- referred to as a cached service because the tiles are pre-created (i.e., not dynamically at the time the request for the layer is received by the server)
- can show data from many different underlying datasets at once
- often used as a basemap; in fact, most of the options when setting a Map’s basemap property result in the addition of a TileLayer
- changes in the underlying data cause the service to be out of date, so this layer type is best suited to data that changes infrequently
- tile creation can be a time consuming process; often automated to run overnight
- because you’re dealing with a picture of your data, you can’t implement popup windows
- can create your own using ArcMap or ArcGIS Pro (see GEOG 865)
How do I know I’m dealing with a TileLayer?
- labeled as a MapServer service in the REST Services Directory
- the service’s Single Fused Map Cache property will be true and it will have a Tile Info section
Class description in the SDK:
Example service:
Code sample:
- ArcGIS API for JavaScript: Get started with layers
- TileLayer objects are created and stored in the transportationLyr and housingLyr variables