How to calculate Vector and Traffic Tile transactions

Traffic tiles (both vector and raster):

Real-time traffic data is updated ever 1 min. Imagine if we see 6 vector tiles in the map view and the map is not panned/zoomed and we see the same tiles for 1 hour when real-time traffic data is updated (every min), would I have new traffic tile transactions (e.g., 1 hour = 60 minutes, 60 min * 6 tiles = 360 vector tile transactions per 1 hour for my map view)? if yes, can we change the frequency of real-time traffic data update? or the vector tile transactions are independent from real-time traffic content update?

Answer: Traffic Vector Tile and Raster Tile sets the expiry in response-headers as 60 seconds. If the client wants, they can request at the 60 seconds interval. If they request later there would be a period where they see expired contents.

From transactional calculation point of view, Please see answers to below questions:

1. There are new traffic tile transactions calculated after every 60 seconds since the expiry of the traffic tiles?

Answer: Every Traffic Tile request is considered as a transaction. If the client requests for traffic tile after every 60 second, there is a traffic tile transaction.

2. Example: If I have 6 traffic tiles in any map view, for 1 hour I will have

6 (Traffic tiles) × 60 (minutes) = 360 traffic tile transactions

6 (Raster tiles) × 60 (minutes) = 360 rater tile transactions

in total I would have 720 transactions without touching my screen. Is this correct?

Answer - For the traffic tile, we can confirm that if the client has 6 traffic tiles and for 1 hour, they request tiles after each expiry then there are 360 tile requests. As each tile request is mapped to 1 transaction. There are 360 traffic tile transactions.

3. Underlying raster tiles of traffic tiles are expired every 60 seconds, so new raster tile transactions are calculated?
4. Why are underlying raster tiles expired? Their content is not changed.

Answer - We set expiry in response headers for the traffic tile in Traffic Vector Tile API and Traffic Raster Tile API services. Underlying raster tiles served by Raster Tile API service which is independent of traffic services.

PS: If customer wants to directly use the Traffic Vector Tile API or Traffic Raster Tile API, they can disregard the "expires" response header in traffic tile responses. Customer can Initiate traffic requests every 5 minutes or as per their needed frequency. I have attached the JS example on how to reload and calculate the traffic tiles on static map(without pan and zoom) on current viewport.

For Vector and Raster Tiles:

In general, Vector tile transactions should be lower than raster tile v3 transactions for the same map view. Is this correct?

Answer: No. same # of transactions if we use same map tile size (512x512)

Each zoom level has multiple raster tile transactions, but zoom level does not impact vector tile transactions. Is this correct?

Answer: VTS also have tiles for every zoom level. But vector tile rendering allows smoother zooming, by utilizing intermediate zoom levels, e.g. 14,3 (not just 14 or 15)

For caching purpose and reducing transactions, what is the caching expiry of vector tiles?

Answer: Max-age = 1hr for both Vector Tile API and Raster Tile API

What is the caching expiry of raster tiles v3?
What is the caching expiry of satellite imagery?

Answer: It is 1 day for legacy Map Tile API v2, but = 1hr for new Raster Tile API v3 and 1 day for satellite imagery.