Forum Discussion
Understanding of transactions
Hi!
We are going to create a drone app, where you will fly at some height over the ground. We'd like to use Azure imagery tiles. But it's hard to understand and calculate how much can it potentially cost. Could someone explain please, what actually "transaction" means? Is it like each time you enter the app, or is it more likely tiles requests and 1 transaction == one request?
For example, how many transactions would there be if we needed the drone to fly 1km from point A to B?
Thanks!
- What is a Transaction?
Transaction Definition: In this case, a transaction is essentially a single request for imagery data. When your drone app requests an image tile from Azure, that's counted as one transaction.
How Transactions Are Counted:
Tile Requests:
Each time your app requests a tile of imagery, it counts as one transaction. The number of transactions depends on the number of tiles requested. For instance, if your drone is capturing images at a high zoom level, it will require more tiles to cover the area.
Flying from Point A to B:
If your drone flies 1 km from point A to point B, you need to calculate how many tiles are covered over that distance. This depends on the zoom level and resolution of the imagery tiles.
For example, if each tile represents a 100m x 100m area and your drone covers 1 km (which is 10 times the tile width), you would need at least 10 tiles along the direction of flight. If your drone also moves side-to-side, you might need additional tiles.
Estimating the Number of Transactions:
To estimate the number of transactions:
Determine Tile Size:
Identify the size of each tile and the resolution of the imagery.
Calculate Area Covered:
Determine how many tiles are needed to cover the area of interest. For a 1 km flight, estimate how many tiles are required based on the tile size.
Factor in Flight Path:
Consider if the drone's flight path requires multiple passes or different angles, which may increase the number of tiles requested.
Add Tile Requests:
Multiply the number of tiles by the number of requests or passes your drone makes.
Example Calculation:
Tile Size: 100m x 100m
Flight Distance: 1 km (10 x 100m)
Tiles Needed for Flight Path: 10 tiles (if moving in one direction)
If your drone also moves side-to-side and takes multiple passes, the number of tiles and thus transactions will increase.
Cost Estimation:
Check Azure Pricing: Azure typically charges based on the number of transactions. Check Azure’s pricing page for the specific imagery service you’re using to get the cost per transaction.
Estimate Based on Usage: Multiply the estimated number of transactions by the cost per transaction to estimate your costs.
- What is a Transaction?
Transaction Definition: In this case, a transaction is essentially a single request for imagery data. When your drone app requests an image tile from Azure, that's counted as one transaction.
How Transactions Are Counted:
Tile Requests:
Each time your app requests a tile of imagery, it counts as one transaction. The number of transactions depends on the number of tiles requested. For instance, if your drone is capturing images at a high zoom level, it will require more tiles to cover the area.
Flying from Point A to B:
If your drone flies 1 km from point A to point B, you need to calculate how many tiles are covered over that distance. This depends on the zoom level and resolution of the imagery tiles.
For example, if each tile represents a 100m x 100m area and your drone covers 1 km (which is 10 times the tile width), you would need at least 10 tiles along the direction of flight. If your drone also moves side-to-side, you might need additional tiles.
Estimating the Number of Transactions:
To estimate the number of transactions:
Determine Tile Size:
Identify the size of each tile and the resolution of the imagery.
Calculate Area Covered:
Determine how many tiles are needed to cover the area of interest. For a 1 km flight, estimate how many tiles are required based on the tile size.
Factor in Flight Path:
Consider if the drone's flight path requires multiple passes or different angles, which may increase the number of tiles requested.
Add Tile Requests:
Multiply the number of tiles by the number of requests or passes your drone makes.
Example Calculation:
Tile Size: 100m x 100m
Flight Distance: 1 km (10 x 100m)
Tiles Needed for Flight Path: 10 tiles (if moving in one direction)
If your drone also moves side-to-side and takes multiple passes, the number of tiles and thus transactions will increase.
Cost Estimation:
Check Azure Pricing: Azure typically charges based on the number of transactions. Check Azure’s pricing page for the specific imagery service you’re using to get the cost per transaction.
Estimate Based on Usage: Multiply the estimated number of transactions by the cost per transaction to estimate your costs.
