Reverse Geocoding Web Service

The Texas A&M Geoservices Reverse Geocoding engine can be used from desktop and/or web applications via the Web Service interfaces listed below. The only required information is the API key, which is available in your account profile page. You may want to read the technical details.

We currently provide reverse geocoding for US addresses only.

API Version - 5.0.0

Available Web Services

API #1 - .Net k-Nearest Neighbor Geographic Feature Search Web Service

• API that can be used from scripts, http, and SOAP compatible clients

• API URL

  https://geoservices.tamu.edu/Api/ReverseGeocoding/V5/Soap/

API #2 - HTTP k-Nearest Neighbor Geographic Feature Search Web Service

• API that can be used from scripts and http

• API URL

  https://geoservices.tamu.edu/Api/ReverseGeocoding/V5/?

  API Input Fields

  Parameter	Required	Description	Example	Possible Values
  apiKey	true	click here for your API key	api-key-value	text string
  version	true	the version of the parser to use	5.0.0	5.0.0
  latitude	true	the latitude of the input coordinate	34.0726207	double
  longitude	true	the longitude of the input coordinate	-118.397965	double
  state	false	abbreviation of state (speeds up processing)	TX	Two character state abbreviation
  format	false	output format	csv	csv, tsv, xml, json
  notStore	false	indicates if the transaction details should not be historically stored in your account	true	true, false

  API Output Fields and Index (for non-XML output)

  Position	Field	Required	Description	Possible Values
  0	Query Status Code	true	Result code	See list
  1	API Version	true	Vesion of the API used	5.0.0.0
  2	Transaction Id	true	Query Id	Unique Id
  3	Street Address	true	Closest street address to the input point	NineteenNinety, TwoThousand, TwoThousandTen, TwoThousandTwenty, AllAvailable
  4	City	true	Closest city to the input point
  5	State	true	Closest state to the input point
  6	Zip	true	Closest ZIP Code to the input point
  7	ZipPlus4	true	Closest ZIP+4 to the input point
  8	Time Taken	true	Processing time	Milliseconds

• API Examples

  Example 1 - 34.0726207994348, -118.397965182076, ca (CSV)
  
  Example 2 - 34.0726207994348, -118.397965182076, ca (XML)
  
  Example 3 - 34.0726207994348, -118.397965182076, ca (JSON)