User Tools

Site Tools


thinkgeo_cloud_reverse_geocoding

This is an old revision of the document!


ThinkGeo Cloud Reverse Geocoding

ThinkGeo Cloud Reverse Geocoding provides RESTful APIs to find an address from a location/location coordinates. Check out the online sample for a quick look.

RESTful APIs

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

ThinkGeo Cloud ReverseGeocoding provides the following Restful APIs.

<!-- Get reverse geocoding for point -->
HTTP GET 
https://cloud.thinkgeo.com/api/v1/location/reverse-geocode/{pointY},{pointX}

URL Parameters

  • pointY: The Y coordinate of the point.
  • pointX: The X coordinate of the point.
  • srid: Optional. The SRID (coordinate system) in which to express the result. Defaults to 4326.
  • proj4String: Optional. The Proj4String (coordinate system) in which to express the result.
  • lang: Optional. The language in which to express the result.
  • searchRadius: Optional. The maximun radius around the input point to search for places. Defaults to 200.
  • searchRadiusUnit: Optional. The unit of measure in which the SearchRadius is expressed. Defaults to “Meter”.
  • maxResults: Optional. The maximum number of results to return. Defaults to 20.
  • locationCategories: Optional. The categories of locations to include in the result set. The default value is “Common”.
  • locationTypes: Optional. Filters the resulting locations by type. Multiple types should be separated by a comma. Defaults to no filter.
  • verboseResults: Optional. Indicates whether the results should be verbose or not. When false, the results will have fewer properties. Defaults to false.
  • distanceFromQueryFeatureUnit: Optional. The unit of measure in which the distance is expressed. Defaults to “Meter”.
<!-- Get reverse geocoding for points -->
HTTP POST
https://cloud.thinkgeo.com/api/v1/location/reverse-geocode/multi

URL Parameters

/* POST parameters, if a parameter specified in both POST and GET, the value from POST parameter will be applied. */
[
  {
    "coord": "string", // The coordinates of the point. The format is: y,x.
    "srid": int, // Optional. The SRID (coordinate system) in which to express the result. Defaults to 4326.
    "proj4String": "string", // Optional. The Proj4String (coordinate system) in which to express the result.
    "lang": "string", // Optional. The language in which to express the result.
    "searchRadius": int, // Optional. The maximun radius around the input point to search for places. Defaults to 200.
    "searchRadiusUnit": "Meter", // Optional. The unit of measure in which the SearchRadius is expressed. Defaults to "Meter".
    "maxResults": int, // Optional. The maximum number of results to return. Defaults to 20.
    "locationCategories": "string", // Optional. The categories of locations to include in the result set. The default value is "Common".
    "locationTypes": "string", // Optional. Filters the resulting locations by type. Multiple types should be separated by a comma. Defaults to no filter.
    "verboseResults": bool, // Optional. Indicates whether the results should be verbose or not. When false, the results will have fewer properties. Defaults to false.
    "distanceFromQueryFeatureUnit": "Meter" // Optional. The unit of measure in which the distance is expressed. Defaults to "Meter".
  }
]
  • srid: Optional. The SRID (coordinate system) in which to express the result. Defaults to 4326.
  • proj4String: Optional. The Proj4String (coordinate system) in which to express the result.
  • lang: Optional. The language in which to express the result.
  • searchRadius: Optional. The maximun radius around the input point to search for places. Defaults to 200.
  • searchRadiusUnit: Optional. The unit of measure in which the SearchRadius is expressed. Defaults to “Meter”.
  • maxResults: Optional. The maximum number of results to return. Defaults to 20.
  • locationCategories: Optional. The categories of locations to include in the result set. The default value is “Common”.
  • locationTypes: Optional. Filters the resulting locations by type. Multiple types should be separated by a comma. Defaults to no filter.
  • verboseResults: Optional. Indicates whether the results should be verbose or not. When false, the results will have fewer properties. Defaults to false.
  • distanceFromQueryFeatureUnit: Optional. The unit of measure in which the distance is expressed. Defaults to “Meter”.
<!-- Get reverse geocoding for area -->
HTTP GET 
https://cloud.thinkgeo.com/api/v1/location/reverse-geocode/area?wkt={polygon}

URL Parameters

  • wkt: The Well Known Text (WKT) of the polygon feature to use as the search area.
  • srid: Optional. The SRID (coordinate system) in which to express the result. Defaults to 4326.
  • proj4String: Optional. The Proj4String (coordinate system) in which to express the result.
  • lang: Optional. The language in which to express the result.
  • searchRadius: Optional. The maximun radius around the input point to search for places. Defaults to 200.
  • searchRadiusUnit: Optional. The unit of measure in which the SearchRadius is expressed. Defaults to “Meter”.
  • maxResults: Optional. The maximum number of results to return. Defaults to 20.
  • locationCategories: Optional. The categories of locations to include in the result set. The default value is “Common”.
  • locationTypes: Optional. Filters the resulting locations by type. Multiple types should be separated by a comma. Defaults to no filter.
  • verboseResults: Optional. Indicates whether the results should be verbose or not. When false, the results will have fewer properties. Defaults to false.
  • distanceFromQueryFeatureUnit: Optional. The unit of measure in which the distance is expressed. Defaults to “Meter”.
<!-- Get reverse geocoding for line -->
HTTP GET 
https://cloud.thinkgeo.com/api/v1/location/reverse-geocode/line?wkt={line}

URL Parameters

  • wkt: The Well Known Text (WKT) of the line feature to use as the search area.
  • srid: Optional. The SRID (coordinate system) in which to express the result. Defaults to 4326.
  • proj4String: Optional. The Proj4String (coordinate system) in which to express the result.
  • lang: Optional. The language in which to express the result.
  • searchRadius: Optional. The maximun radius around the input point to search for places. Defaults to 200.
  • searchRadiusUnit: Optional. The unit of measure in which the SearchRadius is expressed. Defaults to “Meter”.
  • maxResults: Optional. The maximum number of results to return. Defaults to 20.
  • locationCategories: Optional. The categories of locations to include in the result set. The default value is “Common”.
  • locationTypes: Optional. Filters the resulting locations by type. Multiple types should be separated by a comma. Defaults to no filter.
  • verboseResults: Optional. Indicates whether the results should be verbose or not. When false, the results will have fewer properties. Defaults to false.
  • distanceFromQueryFeatureUnit: Optional. The unit of measure in which the distance is expressed. Defaults to “Meter”.
<!-- Get place by Id -->
HTTP GET 
https://cloud.thinkgeo.com/api/v1/location/place/{placeId}

URL Parameters

  • placeId: The OpenStreetMap ID of the place.
  • lang: Optional. Sets the language for the search result. The default value is “en”.
  • Hit Try it Out button below GetPlaceById to test it online.
<!-- Get location cateogires -->
HTTP GET 
https://cloud.thinkgeo.com/api/v1/location/reverse-geocode/location-categories

URL Parameters

No parameters.

<!--  Get common location cateogires -->
HTTP GET 
https://cloud.thinkgeo.com/api/v1/location/reverse-geocode/location-categories/common

URL Parameters

No parameters

Consume from Client Side

ThinkGeo Cloud Reverse 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.

SDK for .NET

The SDK for .NET enables developers to build .NET application that uses 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 the ThinkGeoCloudReverseGeocodingSample-ForWpf for the start.

API Documentation

  • ThinkGeo.Cloud.ReverseGeocodingClient

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

SDK for JavaScript

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 ReverseGeocoding sample shows how to work with this SDK.

thinkgeo_cloud_reverse_geocoding.1552023089.txt.gz · Last modified: 2019/03/08 05:31 by tgwikiupdate