ThinkGeo Cloud Geocoding provides RESTful APIs to find the Geolocation from an address in the United States. Check out the online sample for a quick look.

* Try it Online: All the ThinkGeo Cloud RESTful APIs can be tested online following the instructions below:

• Get a ThinkGeo Cloud Client Key. Check out ThinkGeo Cloud Client Keys Guideline see how to apply one. It's free for 60 days.
• Authorize with the key at the top of ThinkGeo Cloud APIs and you are then free to play with all the APIs online.

ThinkGeo Cloud Geocoding provides the following 2 Restful APIs:

<!-- Get location from an address -->
HTTP GET 
https://cloud.thinkgeo.com/api/v1/location/geocode/{searchText}

URL Parameters

• searchText: The address to be geocoded.
• locationType: Optional. Specifies what types of locations will be considered a match. Possible values are Address, Street, State, City, County, Zipcode, Country. Defaults to Default.
• fuzzyMatch: Optional. Specifies whether to attempt approximate, as well as exact, matching when performing geocodes. Defaults to false.
• maxResults: Optional. The maximum number of possible matches to return, if multiple candidates are found. Defaults to 10.
• verboseResults: Optional. Indicates whether the results should be verbose or not. When false, the results will have fewer properties. Defaults to false.
• srid: Optional. The SRID (coordinate system ID) in which to express the result. Mutually exclusive from the Proj4String parameter.
• proj4String: Optional. The Proj4 projection string (coordinate system) in which to express the result. Mutually exclusive from the Srid parameter. Defaults to “+proj=longlat +datum=WGS84 +no_defs”.

• Hit Try it Out button below GeocodeAddress to test it online.

<!-- Get locations from multiple addresses -->
HTTP POST
https://cloud.thinkgeo.com/api/v1/location/geocode/multi

Parameters

/* POST parameters, if a parameter specified in both POST and GET, the value from POST parameter will be applied. */
[
  {
    "searchText": "string", // Free-form text representing the address or location to be geocoded.
    "locationType": "string", // Optional. Specifies what types of locations will be considered a match. Possible values are Address, Street, State, City, County, Postcode, Zipcode, Country. Defaults to all types.
    "fuzzyMatch": bool, // Optional. Specifies whether to attempt approximate, as well as exact, matching when performing geocodes. Defaults to false.
    "maxResults": int, // Optional. The maximum number of possible matches to return, if multiple candidates are found. Defaults to 20.
    "verboseResults": bool, // Optional. Indicates whether the results should be verbose or not. When false, the results will have fewer properties. Defaults to false.
    "srid": int, // Optional. The SRID (coordinate system ID) in which to express the result. Mutually exclusive from the Proj4String parameter.
    "proj4String": "string" // Optional. The Proj4 projection string (coordinate system) in which to express the result. Mutually exclusive from the Srid parameter. Defaults to "+proj=longlat +datum=WGS84 +no_defs".
  }
]

• locationType: Optional. Specifies what types of locations will be considered a match. Possible values are Address, Street, State, City, County, Zipcode, Country. Defaults to Default.
• fuzzyMatch: Optional. Specifies whether to attempt approximate, as well as exact, matching when performing geocodes. Defaults to false.
• maxResults: Optional. The maximum number of possible matches to return, if multiple candidates are found. Defaults to 10.
• verboseResults: Optional. Indicates whether the results should be verbose or not. When false, the results will have fewer properties. Defaults to false.
• srid: Optional. The SRID (coordinate system ID) in which to express the result. Mutually exclusive from the Proj4String parameter.
• proj4String: Optional. The Proj4 projection string (coordinate system) in which to express the result. Mutually exclusive from the Srid parameter. Defaults to “+proj=longlat +datum=WGS84 +no_defs”.

• Hit Try it Out button below GeocodeAddressesBatch to test it online.

ThinkGeo Cloud Geocoding does not allow anonymous users to access the API. Before working with these APIs, you will need to register with ThinkGeo Cloud and create your own clients. A new account comes with two clients: NativeConfidential and JavaScript. See more details at here.

ThinkGeo Cloud provides standard RESTful APIs which can be consumed on any platform through any language. ThinkGeo also offers two prepackaged API clients to make it easier to integrate into .NET and JavaScript applications.

The SDK for .NET enables developers to build .NET applications that use the ThinkGeo Cloud services. The NuGet package can be found at ThinkGeo.Cloud.Client or you can install this package with PM by running the command: Install-Package ThinkGeo.Cloud.Client -Version VERSION_TO_BE_INSTALLED, here is the complete API List. Also you can check out ThinkGeoCloudGeocodingSample-ForWpf for a a jump-start.

• ThinkGeo.Cloud.GeocodingClient

  This documentation covers the ThinkGeo.Cloud.GeocodingClient class. It contains all of the members such as Constructors, Methods, Properties and Events.

The SDK for JavaScript enables developers to directly access ThinkGeo Cloud services from JavaScript code running in brower. This SDK can be found at thinkgeocloudclient-js. The Geocoding sample shows how to work with this SDK.

• ThinkGeo Cloud Reverse Geocoding
• ThinkGeo Cloud Maps WMS
• ThinkGeo Cloud Maps Vector Tiles
• ThinkGeo Cloud Maps Raster Tiles
• ThinkGeo Cloud Elevation
• ThinkGeo Cloud Projection
• ThinkGeo Cloud Colors