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/08/23 20:23] brianr Fixed URL to online samples |
thinkgeo_cloud [2020/04/01 22:02] (current) admin [Pricing] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== ThinkGeo Cloud ====== | ====== ThinkGeo Cloud ====== | ||
| - | ThinkGeo Cloud is a set of cloud-hosted RESTful APIs, which have been designed to optimize your productivity in the world of mapping by taking away the complicated deployments, data warehousing and IT concerns that you would normally encounter. It can be consumed from a web page, as well as Desktop applications or Mobile Apps on a different platform. | + | ThinkGeo Cloud is a set of cloud-hosted RESTful APIs that have been designed to optimize your productivity in the world of mapping by taking away the complicated deployments, data warehousing and IT concerns that you would normally encounter. It can be consumed from web applications, desktop applications, mobile apps or services on a wide variety of platforms. |
| ===== Getting Started ===== | ===== Getting Started ===== | ||
| - | ThinkGeo Cloud is easy to get started for anyone including those without too much coding background. Just log into the console, create a key and go ahead and use it. Here is how to do it in general: | + | ThinkGeo Cloud is easy to get started for anyone including those without too much coding background. Just log into the Cloud web console, grab your API key and get to work! We've put together a video that will give you a high-level overview of how to get started: |
| + | |||
| + | {{youtube>vM9OGfeiVv4?size=560x315}} | ||
| === ThinkGeo Cloud Console === | === ThinkGeo Cloud Console === | ||
| Line 151: | 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.1566591839.txt.gz · Last modified: 2019/08/23 20:23 by brianr