To ensure good performance, the HERE platform has limits on data storage and throughput. Some limits can be controlled by layer configuration, which may impact your cost since you are charged based on how you have configured the layers and data usage. As a general rule, the more data you send and receive from the HERE platform, and the more data you store, the more you will be charged. You will also be charged more if you configure layers for higher performance.

For more information on costs associated with each layer type, see the Cost Management Guide.

For more information on pipeline logging, see Pipeline logging.

Catalog limits

Layer limits

• Storage and throughput limits
  • Catalog limits
  • Layer limits
    • Index layer limits
    • Interactive map layer limits
    • Object store layer limits
    • Stream layer limits
    • Versioned layer limits
    • Volatile layer limits
  • Data API quotas
  • Artifact Service API quotas

Index layer limits

Cost considerations:

• You are charged for the amount of metadata and data stored in the layer
• You are charged based on the amount of data you read and write using the blob and index APIs
• You are charged based on the retention setting configured for the layer

Interactive map layer limits

Cost considerations:

• You are charged for the amount of metadata and data stored in the layer
• You are charged based on the amount of data you read and write using the interactive API
• Indexing of layers happens on the fly, so no additional IO is charged, but the indexes add to the data stored.

Object store layer limits

Cost considerations:

• You are charged for the amount of metadata and data stored in the layer
• You are charged based on the amount of data you read and write using the blob API
• There are no layer configuration settings that affect cost

Stream layer limits

Cost considerations:

• Usage does not affect cost
• You are charged based on the maximum throughput configured for the layer
• You are charged based on the retention setting configured for the layer

Versioned layer limits

Cost considerations:

• HERE charges you for the amount of metadata and data stored in the layer
• HERE charges you based on the amount of data you read and write using the blob and metadata APIs
• There are no layer configuration settings that affect cost
• Deleting catalog versions to manage storage costs gives you more granular data lifecycle management controls for your versioned layers. You can delete catalog versions manually or use the config service to delete catalog versions automatically by enabling the automaticVersionDeletion and setting the numberOfVersionsToKeep with a maximum value of 50,000. For more information, see Delete catalog versions.
• HERE recommends your data partitions have homogenous sizes and use as high of a zoom level as possible. For more information, see Considerations when designing data models for versioned layers.

Volatile layer limits

Cost considerations:

• You are charged based on the amount of data you read and write using the blob API
• You are charged based on the storage capacity configured for the layer. The price increases as the storage capacity increases.
• You are charged based on the data redundancy configured for the layer. For multi-instance mode, your cost triples because two additional copies of your data are created, for a total of 3 copies, to provide durability.

Data API quotas

Artifact Service API quotas