Assets (Feature Service/Layer)

Description

An asset is a chunk of binary data such as a texture, image, or a 3D geometry. Assets can be bulky. Their efficient exchange between a client and a service is key to achieving low latency in editing workflows.

An asset is identified by its hash using a hash algorithm such as SHA-256. The hash algorithm is a part of the layer description (assetHashAlgorithm). The assets can be shared between layers depending on the settings of the 3D Object feature class, where assets can be shared within a feature class or across feature classes in a workspace. However to keep the API simple, assets are kept as part of the layer not the service.

If a client already has an asset, it should not be requested again. If the server already has an asset, the client should be able to find that and not upload that asset again. To facilitate their efficient exchange, the service has separate asset operations on the layer resource.

Request parameters

Example usage

The following is a sample request URL used to access the assets endpoint where f = bin:

https://machine.domain.com/webadaptor/rest/services/City_Park_Assets/FeatureServer/0/assets/8cc3ab5b3a14309c9465707d3a0a095b217ec683303dc3670a21f755fc9414c9

The following is a sample request URL used to access the assets endpoint where f = json:

https://machine.domain.com/webadaptor/rest/services/City_Park_Assets/FeatureServer/0/assets/8cc3ab5b3a14309c9465707d3a0a095b217ec683303dc3670a21f755fc9414c9?f=json

JSON Response syntax

Where f = json

{  
  "assetHash": "<hash>",  
  "contentType": "<mimeType>", 
  "assetData": "<base64EncodedAssetBytes>"  
}

JSON Response example

Where f = json

{  
  "assetHash": "6486ee53c8faba18045ef29d382f1c8227bde3a25d37f7a62fe0d2259a3a14dd",  
  "contentType": "model/gltf-binary", 
  "assetData": "Z2xURgIAAACoiRAAsFcAAEpTT057ImFjY2Vzc29ycyI6W3siYnVmZmVyVmlldyI6MSwiY29tcG9uZ..."  
}