Texas A&M Geoservices Geocoding APIs

API Version - 2.95

The Texas A&M Geoservices Geocoder can be used from desktop and/or web applications via the Geocoding 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 and the known bugs.

Available API Endpoints

API #1 - .Net Geocode Web Service

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

• API URL

  https://geoservices.tamu.edu/Services/Geocode/WebService/GeocoderService_V02_95.asmx

API #2 - HTTP Geocode Web Service (Non-parsed)

• API for non-parsed address data that can be used from scripts and http

• API URL

  https://geoservices.tamu.edu/Services/Geocode/WebService/GeocoderWebServiceHttpNonParsed_V02_95.aspx?

  API Input Fields

  Parameter	Required	Description	Example	Possible Value
  apiKey	true	Click here for your API key	api-key-value	some text
  version	true	api version	2.95	2.95
  streetAddress	false	non-parsed street address value	3620 North Vermont Ave W.	some text
  city	false	city value	Beverly Hills	some text
  state	false	state value	CA	some text
  zip	false	zip code value	90089	some text
  census	false	calculate census variables (takes longer)	true	true, false
  verbose	false	output full details	true	true, false
  format	false	output format	csv	csv, (results in comma separated values) tsv, (results in tab separated values) xml, (results in XML format) kml, (results in a KML file) googleMapsUrl, (results in a URL to show the output in Google Maps)
  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	Transaction Id	true	Query Id	Unique Id
  1	API Version	true	Vesion of the API used	2.95
  2	Query Status Code	true	Result code	See list
  3	Latitude	true	Decimal
  4	Longitude	true	Decimal
  5	Match Score	true	Match percentage between input data and reference feature
  6	Match Type	true	Geocode match type	See list
  7	Matching Geography Type	true	Geographic level of the output	See list
  8	Interpolation Type	true	Interpolation method used	See list
  9	Interpolation Sub-Type	true	Interpolation sub-method used	See list
  10	Matched Location Type	true	Type of input data identified	See list
  11	Feature Matching Result Type	true	Result of the feature matching algorithm	See list
  12	Time Taken	true	Processing time	Milliseconds
  13	Census 2000 Block	false	Census 2000 block value for the output point
  14	Census 2000 Block Group	false	Census 2000 block group value for the output point
  15	Census 2000 Tract	false	Census 2000 tract value for the output point
  16	Census 2000 County Fips	false	Census 2000 county fips value for the output point
  17	Census 2000 CBSA Fips	false	Census 2000 core base statistical area fips value for the output point
  18	Census 2000 CBSA Micro	false	Census 2000 core base statistical area micropolitan flag for the output point
  19	Census 2000 MCD Fips	false	Census 2000 minor civil division fips value for the output point
  20	Census 2000 MetDiv Fips	false	Census 2000 metropolitan division fips value for the output point
  21	Census 2000 MSA Fips	false	Census 2000 metropolitan statistical area fips value for the output point
  22	Census 2000 Place Fips	false	Census 2000 place fips value for the output point
  23	Census 2000 State Fips	false	Census 2000 state fips value for the output point
  24	MNumber	false	Street number of the address that matched
  25	MNumberFractional	false	Street number fractional of the address that matched
  26	MPreDirectional	false	Street predirectional of the address that matched
  27	MPreQualifier	false	Street prequalifier of the address that matched
  28	MPreType	false	Street pretype of the address that matched
  29	MPreArticle	false	Street prearticle of the address that matched
  30	MName	false	Street name of the address that matched
  31	MPostArticle	false	Street postarticle of the address that matched
  32	MPostQualifier	false	Street postqualifier of the address that matched
  33	MSuffix	false	Street suffix of the address that matched
  34	MPostDirectional	false	Street postdirectional of the address that matched
  35	MSuiteType	false	Suite type of the address that matched
  36	MSuiteNumber	false	Suite number of the address that matched
  37	MPostOfficeBoxType	false	Post office box type of the address that matched
  38	MPostOfficeBoxNumber	false	Post office box number of the address that matched
  39	MCity	false	City of the address that matched
  40	MConsolidatedCity	false	Consolidated city of the address that matched
  41	MMinorCivilDivision	false	Minor civil division of the address that matched
  42	MCountySubRegion	false	County sub region of the address that matched
  43	MCounty	false	County of the address that matched
  44	MState	false	State of the address that matched
  45	MZip	false	Zip of the address that matched
  46	MZipPlus1	false	Zip+1 of the address that matched
  47	MZipPlus2	false	Zip+2 of the address that matched
  48	MZipPlus3	false	Zip+3 of the address that matched
  49	MZipPlus4	false	Zip+4 of the address that matched
  50	MZipPlus5	false	Zip+5 of the address that matched
  51	PNumber	false	Street number of the parsed address
  52	PNumberFractional	false	Street number fractional of the parsed address
  53	PPreDirectional	false	Street predirectional of the parsed address
  54	PPreQualifier	false	Street prequalifier of the parsed address
  55	PPreType	false	Street pretype of the parsed address
  56	PPreArticle	false	Street prearticle of the parsed address
  57	PName	false	Street name of the parsed address
  58	PPostArticle	false	Street postarticle of the parsed address
  59	PPostQualifier	false	Street postqualifier of the parsed address
  60	PSuffix	false	Street suffix of the parsed address
  61	PPostDirectional	false	Street postdirectional of the parsed address
  62	PSuiteType	false	Suite type of the parsed address
  63	PSuiteNumber	false	Suite number of the parsed address
  64	PPostOfficeBoxType	false	Post office box type of the parsed address
  65	PPostOfficeBoxNumber	false	Post office box number of the parsed address
  66	PCity	false	City of the parsed address
  67	PConsolidatedCity	false	Consolidated city of the parsed address
  68	PMinorCivilDivision	false	Minor civil division of the parsed address
  69	PCountySubRegion	false	County sub region of the parsed address
  70	PCounty	false	County of the parsed address
  71	PState	false	State of the parsed address
  72	PZip	false	Zip of the parsed address
  73	PZipPlus1	false	Zip+1 of the parsed address
  74	PZipPlus2	false	Zip+2 of the parsed address
  75	PZipPlus3	false	Zip+3 of the parsed address
  76	PZipPlus4	false	Zip+4 of the parsed address
  77	PZipPlus5	false	Zip+5 of the parsed address
  78	FNumber	false	Street number of the matched reference feature
  79	FNumberFractional	false	Street number fractional of the matched reference feature
  80	FPreDirectional	false	Street predirectional of the matched reference feature
  81	FPreQualifier	false	Street prequalifier of the matched reference feature
  82	FPreType	false	Street pretype of the matched reference feature
  83	FPreArticle	false	Street prearticle of the matched reference feature
  84	FName	false	Street name of the matched reference feature
  85	FPostArticle	false	Street postarticle of the matched reference feature
  86	FPostQualifier	false	Street postqualifier of the matched reference feature
  87	FSuffix	false	Street suffix of the matched reference feature
  88	FPostDirectional	false	Street postdirectional of the matched reference feature
  89	FSuiteType	false	Suite type of the matched reference feature
  90	FSuiteNumber	false	Suite number of the matched reference feature
  91	FPostOfficeBoxType	false	Post office box type of the matched reference feature
  92	FPostOfficeBoxNumber	false	Post office box number of the matched reference feature
  93	FCity	false	City of the matched reference feature
  94	FConsolidatedCity	false	Consolidated city of the matched reference feature
  95	FMinorCivilDivision	false	Minor civil division of the matched reference feature
  96	FCountySubRegion	false	County sub region of the matched reference feature
  97	FCounty	false	County of the matched reference feature
  98	FState	false	State of the matched reference feature
  99	FZip	false	Zip of the matched reference feature
  100	FZipPlus1	false	Zip+1 of the matched reference feature
  101	FZipPlus2	false	Zip+2 of the matched reference feature
  102	FZipPlus3	false	Zip+3 of the matched reference feature
  103	FZipPlus4	false	Zip+4 of the matched reference feature
  104	FZipPlus5	false	Zip+5 of the matched reference feature
  105	FArea	false	Area of the matched feature
  106	FAreaType	false	Area metric of the matched feature
  107	FGeometrySRID	false	Geometry SRID of the matched feature
  108	FGeometry	false	Geometry of the matched feature as OGC GML
  109	FSource	false	Source of the matched feature
  110	FVintage	false	Vintage of the matched feature
  111	FPrimaryIdField	false	Name of the primary Id field of the matched feature
  112	FPrimaryIdValue	false	Value of the primary Id field of the matched feature
  113	FSecondaryIdField	false	Name of the secondary Id field of the matched feature
  114	FSecondaryIdValue	false	Value of the secondary Id field of the matched feature

  
  Notes
  - M____: The attribute value of your input address that used in finding a reference feature
  - P____: The equivalent parsed attribute value of your input address
  - F____: The attribute value of the matched reference feature used for interpolation
  

• API Examples

  Example 1 - 9355 Burton Way, Beverly Hills, ca, 90210 (CSV, with census)
  
  Example 2 - 9355 Burton Way, Beverly Hills, ca, 90210 (XML, without census)
  
  Example 3 - 9355 Burton Way, Beverly Hills, ca, 90210 (XML, with census)
  
  Example 4 - 9355 Burton Way, Beverly Hills, ca, 90210 (KML, with census)
  
  Example 5 - 9355 Burton Way, Beverly Hills, ca, 90210 (Google Maps URL, with census)
  
  Example 6 - 9355 Burton Way, Beverly Hills, ca, 90210 (CSV, Verbose, with census)
  
  Example 7 - 9355 Burton Way, Beverly Hills, ca, 90210 (TSV, Verbose, with census)
  
  Example 8 - 9355 Burton Way, Beverly Hills, ca, 90210 (XML, Verbose, without census)
  
  Example 9 - 9355 Burton Way, Beverly Hills, ca, 90210 (XML, Verbose, with census)
  
  Example 10 - PO Box 221, Beverly Hills, ca, 90210 (XML, Verbose, with census)
  
  Example 11 - PO Box 221 9355 Burton Way, Beverly Hills, ca, 90210 (CSV, Verbose, with census)
  
  

API #3 - HTTP Geocode Web Service (Non-parsed) with Advanced Options

• API for non-parsed address data that can be used from scripts and http that allows advanced options to be specified

• API URL

  https://geoservices.tamu.edu/Services/Geocode/WebService/GeocoderWebServiceHttpNonParsedAdvanced_V02_95.aspx?

  API Input Fields

  This API's input field set includes all of the input and output parameters from API #2 above with the additions in the following table. Each of these are described in the techincal details. The default values used here are automatically used in API #2 above.

  Parameter	Required	Description	Values	Default value
  r	false	whether or not to use attribute relaxation	true, false	true
  ratts	false	the attributes allowed to be relaxed; only applies if shouldUseRelaxation is true	comma separated list from the following options: pre, suffix, post, city, zip	pre,suffix,post,city,zip
  sub	false	whether or not to use substring matching	true, false	true
  sou	false	whether or not to use soundex	true, false	true
  souatts	false	the attributes allowed to be soundex'ed; only applies if shouldUseSoundex is true	comma separated list from the following options: name, city	name,city
  h	false	which feature matching hierarchy to use	uncertaintyBased, u, FeatureMatchingSelectionMethod, f,	FeatureMatchingSelectionMethod
  refs	false	which reference data sources to use	all - or one or more of the following - PreComputedPoints, countyParcelData, OpenAddresses, MicrosoftFootprints, navteqAddressPoints2022, navteqAddressPoints2021, navteqAddressPoints2017, navteqAddressPoints2016, navteqAddressPoints2014, navteqAddressPoints2013, navteqAddressPoints2012, parcelCentroids, boundarySolutionsParcelCentroids, parcelGeometries, navteqStreets2022, navteqStreets2021, navteqStreets2012, navteqStreets2008, Census2022TigerLines, Census2016TigerLines, Census2015TigerLines, Census2010TigerLines, USPSTigerZipPlus4, census2020Places, census2010Places, census2000Places, census2020ConsolidatedCities, census2010ConsolidatedCities, census2020ZCTAs, census2010ZCTAs, census2000ZCTAs, ZipCodeDownloadZips2013, census2020CountySubRegions, census2010CountySubRegions, census2000CountySubRegions, census2020Counties, census2010Counties, census2000Counties, census2020States, census2010States	all

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

  The output fields for this API are the same as API #2 above

• API Examples

  Example 1 - 9355 NE Burton Rd, Wrong City, ca, 90210 (XML, Verbose, All options false, with census)
  - will fail to match a parcel because city is wrong
  
  Example 2 - 9355 NE Burton Rd, Wrong City, ca, 90210 (XML, Verbose, Attribute Relxation on pre,suffix,city, with census)
  - will succeed in matching a parcel even though city is wrong because the city attribute will be relaxed
  
  Example 3 - 9355 Berrton Way, Beverly Hills, ca, 90210 (XML, Verbose, All options false, with census)
  - will fail to match a parcel because the street name is wrong
  
  Example 4 - 9355 Berrton Way, Beverly Hills, ca, 90210 (XML, Verbose, Soundex on street name, with census)
  - will succeed in matching a parcel even though the street name is wrong because soundex is being used on the street name
  
  Example 5 - 9355 Berton Way, Bevirrly Hills, ca, 90210 (XML, Verbose, All options false, with census)
  - will fail to match a parcel because the city name is wrong
  
  Example 6 - 9355 Berton Way, Bevirrly Hills, ca, 90210 (XML, Verbose, Soundex on city, with census)
  - will succeed in matching a parcel even though the city is wrong because soundex is being used on the city
  
  Example 7 - PO Box 123, Beverly Hills, ca, 90210 (XML, Verbose, Feature matching hierarchy, with census)
  - will match to ZIP 90210 (ZIP comes before city in the feature matching hierarchy)
  
  Example 8 - PO Box 123, Beverly Hills, ca, 90210 (XML, Verbose, Uncertainty hierarchy, with census)
  - will match to city Beverly Hills (smaller area = less geographic uncertainty = more accurate geocode)