thinkgeo_cloud
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
thinkgeo_cloud [2020/04/01 21:50] admin [Pricing] |
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 along a polyline 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 addresses. | * 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 addresses. | * One transaction is one geocoding request. For example, it takes 100 transactions for a batch geocoding with 100 addresses. | ||
thinkgeo_cloud.1585777837.txt.gz · Last modified: 2020/04/01 21:50 by admin