thinkgeo_cloud
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
thinkgeo_cloud [2019/11/18 16:35] brianr Added getting started video. |
thinkgeo_cloud [2020/04/01 22:02] (current) admin [Pricing] |
||
|---|---|---|---|
| Line 154: | Line 154: | ||
| Here is what one transaction means for different services: | Here is what one transaction means for different services: | ||
| - | * One transaction is one elevation request for up to 100 points. For example, if I get elevation information within a polygon and get 1,500 elevation points, it takes 15 transactions. | + | * One transaction is one elevation request (including batch request) for up to 100 points. For example, if I request elevation information along a polyline and get 1,500 elevation points, it takes 15 transactions. If I send a batch request with 250 points, it counts as 3 transactions. |
| - | * One transaction is one reverse geocoding request. For example, it takes 100 transactions for a batch reverse geocoding with 100 address. | + | * One transaction is one reverse geocoding request. For example, it takes 100 transactions for a batch reverse geocoding with 100 addresses. |
| - | * One transaction is one geocoding request. For example, it takes 100 transactions for a batch geocoding with 100 address. | + | * One transaction is one geocoding request. For example, it takes 100 transactions for a batch geocoding with 100 addresses. |
| - | * One transaction is one map view, which is 10 XYZ tile request, including vector tile request or raster tile request. | + | * One transaction is one map view, which is 10 XYZ tile request, including vector tile, raster tile or hybrid tile request. |
| * One transaction is one WMS tile request. | * One transaction is one WMS tile request. | ||
| * One transaction is one Color Scheme request. | * One transaction is one Color Scheme request. | ||
| * One transaction is one projection conversion for up to 100 vertices. For example, if I project one polygon with 1,500 vertices from projection A to projection B, it takes 15 transactions. | * One transaction is one projection conversion for up to 100 vertices. For example, if I project one polygon with 1,500 vertices from projection A to projection B, it takes 15 transactions. | ||
| + | * One transaction is one Time Zone request. | ||
| + | * One transaction is one World Maps Query request. | ||
| + | * One transaction is one Routing request with 10 or less waypoints, it takes 2 transactions if it's more than 10 waypoints. | ||
| + | * One transaction is one Cost Matrix request with 10 or less waypoints, it takes 2 transactions if it's more than 10 waypoints. | ||
| + | * One transaction is one TSP (Traveling Sales Man) request with 10 or less waypoints, it takes 2 transactions if it's more than 10 waypoints. | ||
| + | * One transaction is one Service Area request. | ||
| + | |||
| ===== Change Logs ===== | ===== Change Logs ===== | ||
thinkgeo_cloud.1574094953.txt.gz · Last modified: 2019/11/18 16:35 by brianr