TAMU GeoServices
About Services Pricing Support News
Log In Sign Up
  • Address Processing
  • Geocoding
    • Platform Details
    • Interactive Geocoding
    • Batch Processing
    • Geocoding API
    • Desktop Client
    • Esri ToolBox
    • Other Geocoders
  • Geocode Correction
  • Census Intersection
  • k-Nearest Search
  • Reverse Geocoding
  • Drag & Drop Mapping
  • Privacy & Security
  • Terms of Use
  • Get Started Now!
    v 5.0.0 API
    • Overview
    • REST
    • SOAP
    • Examples
    Previous Versions
    • v 4.05
    • v 4.04
    • v 4.03
    • v 4.02
    • v 4.01
    • v 3.01
    • v 2.96
    • v 2.95
    • v 2.94
    • v 2.93
    • v 2.92
    • v 2.91

Texas A&M Geoservices Geocoding APIs

Services › Geocoding › API

API Version - 2.96

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_96.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_96.aspx?

    API Input Fields

    (* Fields in bold are new for this API version)
    Parameter Required Description Example Possible Value
    apiKey true Click here for your API key api-key-value some text
    version true api version 2.96 2.96
    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
    censusYear* false the year of census data to intersect with 2010 1990, 2000, 2010
    geom false return the full geometry of the reference feature (creates a very large response) 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)

    (* Fields in bold are new for this API version)
    Position Field Required Description Possible Values
    0 Transaction Id true Query Id Unique Id
    1 API Version true Vesion of the API used 2.96
    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 FeatureMatchingResultCount true Number of features returned from feature matching algorithm
    13 FeatureMatchingResultTypeNotes true Notes about the feature matching processing results
    14 TieHandlingStrategyType true Tie breaking strategy used in feature matching See list
    15 FeatureMatchingResultTypeTieBreakingNotes true Notes about the tie breaking results
    16 FeatureMatchingSelectionMethod true Feature matching selection method used See list
    17 FeatureMatchingSelectionMethodNotes true Notes about the feature matching selection method used
    18 Time Taken true Processing time Milliseconds
    19 Census Year* true Year of the census data returned NineteenNinety, TwoThousand, TwoThousandTen, TwoThousandTwenty, AllAvailable
    20 Census Block false Census block value for the output point
    21 Census Block false Census block value for the output point
    22 Census Block Group false Census block group value for the output point
    23 Census Tract false Census tract value for the output point
    24 Census County Fips false Census county fips value for the output point
    25 Census CBSA Fips false Census core base statistical area fips value for the output point
    26 Census CBSA Micro false Census core base statistical area micropolitan flag for the output point
    27 Census MCD Fips false Census minor civil division fips value for the output point
    28 Census MetDiv Fips false Census metropolitan division fips value for the output point
    29 Census MSA Fips false Census metropolitan statistical area fips value for the output point
    30 Census Place Fips false Census place fips value for the output point
    31 Census State Fips false Census state fips value for the output point
    32 MNumber false Street number of the address that matched
    33 MNumberFractional false Street number fractional of the address that matched
    34 MPreDirectional false Street predirectional of the address that matched
    35 MPreQualifier false Street prequalifier of the address that matched
    36 MPreType false Street pretype of the address that matched
    37 MPreArticle false Street prearticle of the address that matched
    38 MName false Street name of the address that matched
    39 MPostArticle false Street postarticle of the address that matched
    40 MPostQualifier false Street postqualifier of the address that matched
    41 MSuffix false Street suffix of the address that matched
    42 MPostDirectional false Street postdirectional of the address that matched
    43 MSuiteType false Suite type of the address that matched
    44 MSuiteNumber false Suite number of the address that matched
    45 MPostOfficeBoxType false Post office box type of the address that matched
    46 MPostOfficeBoxNumber false Post office box number of the address that matched
    47 MCity false City of the address that matched
    48 MConsolidatedCity false Consolidated city of the address that matched
    49 MMinorCivilDivision false Minor civil division of the address that matched
    50 MCountySubRegion false County sub region of the address that matched
    51 MCounty false County of the address that matched
    52 MState false State of the address that matched
    53 MZip false Zip of the address that matched
    54 MZipPlus1 false Zip+1 of the address that matched
    55 MZipPlus2 false Zip+2 of the address that matched
    56 MZipPlus3 false Zip+3 of the address that matched
    57 MZipPlus4 false Zip+4 of the address that matched
    58 MZipPlus5 false Zip+5 of the address that matched
    59 PNumber false Street number of the parsed address
    60 PNumberFractional false Street number fractional of the parsed address
    61 PPreDirectional false Street predirectional of the parsed address
    62 PPreQualifier false Street prequalifier of the parsed address
    63 PPreType false Street pretype of the parsed address
    64 PPreArticle false Street prearticle of the parsed address
    65 PName false Street name of the parsed address
    66 PPostArticle false Street postarticle of the parsed address
    67 PPostQualifier false Street postqualifier of the parsed address
    68 PSuffix false Street suffix of the parsed address
    69 PPostDirectional false Street postdirectional of the parsed address
    70 PSuiteType false Suite type of the parsed address
    71 PSuiteNumber false Suite number of the parsed address
    72 PPostOfficeBoxType false Post office box type of the parsed address
    73 PPostOfficeBoxNumber false Post office box number of the parsed address
    74 PCity false City of the parsed address
    75 PConsolidatedCity false Consolidated city of the parsed address
    76 PMinorCivilDivision false Minor civil division of the parsed address
    77 PCountySubRegion false County sub region of the parsed address
    78 PCounty false County of the parsed address
    79 PState false State of the parsed address
    80 PZip false Zip of the parsed address
    81 PZipPlus1 false Zip+1 of the parsed address
    82 PZipPlus2 false Zip+2 of the parsed address
    83 PZipPlus3 false Zip+3 of the parsed address
    84 PZipPlus4 false Zip+4 of the parsed address
    85 PZipPlus5 false Zip+5 of the parsed address
    86 FNumber false Street number of the matched reference feature
    87 FNumberFractional false Street number fractional of the matched reference feature
    88 FPreDirectional false Street predirectional of the matched reference feature
    89 FPreQualifier false Street prequalifier of the matched reference feature
    90 FPreType false Street pretype of the matched reference feature
    91 FPreArticle false Street prearticle of the matched reference feature
    92 FName false Street name of the matched reference feature
    93 FPostArticle false Street postarticle of the matched reference feature
    94 FPostQualifier false Street postqualifier of the matched reference feature
    95 FSuffix false Street suffix of the matched reference feature
    96 FPostDirectional false Street postdirectional of the matched reference feature
    97 FSuiteType false Suite type of the matched reference feature
    98 FSuiteNumber false Suite number of the matched reference feature
    99 FPostOfficeBoxType false Post office box type of the matched reference feature
    100 FPostOfficeBoxNumber false Post office box number of the matched reference feature
    101 FCity false City of the matched reference feature
    102 FConsolidatedCity false Consolidated city of the matched reference feature
    103 FMinorCivilDivision false Minor civil division of the matched reference feature
    104 FCountySubRegion false County sub region of the matched reference feature
    105 FCounty false County of the matched reference feature
    106 FState false State of the matched reference feature
    107 FZip false Zip of the matched reference feature
    108 FZipPlus1 false Zip+1 of the matched reference feature
    109 FZipPlus2 false Zip+2 of the matched reference feature
    110 FZipPlus3 false Zip+3 of the matched reference feature
    111 FZipPlus4 false Zip+4 of the matched reference feature
    112 FZipPlus5 false Zip+5 of the matched reference feature
    113 FArea false Area of the matched feature
    114 FAreaType false Area metric of the matched feature
    115 FGeometrySRID false Geometry SRID of the matched feature
    116 FGeometry false Geometry of the matched feature as OGC GML
    117 FSource false Source of the matched feature
    118 FVintage false Vintage of the matched feature
    119 FPrimaryIdField false Name of the primary Id field of the matched feature
    120 FPrimaryIdValue false Value of the primary Id field of the matched feature
    121 FSecondaryIdField false Name of the secondary Id field of the matched feature
    122 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 2010 census)

    Example 2 - 9355 Burton Way, Beverly Hills, ca, 90210 (XML, without census)

    Example 3 - 9355 Burton Way, Beverly Hills, ca, 90210 (XML, with 2000 census)

    Example 4 - 9355 Burton Way, Beverly Hills, ca, 90210 (KML, with 2010 census)

    Example 5 - 9355 Burton Way, Beverly Hills, ca, 90210 (Google Maps URL, with 2010 census)

    Example 6 - 9355 Burton Way, Beverly Hills, ca, 90210 (CSV, Verbose, with 2010 census and reference geometry)

    Example 7 - 9355 Burton Way, Beverly Hills, ca, 90210 (TSV, Verbose, with 2010 census and reference geometry)

    Example 8 - 9355 Burton Way, Beverly Hills, ca, 90210 (XML, Verbose, without census and reference geometry)

    Example 9 - 9355 Burton Way, Beverly Hills, ca, 90210 (XML, Verbose, with 2010 census and reference geometry)

    Example 10 - PO Box 221, Beverly Hills, ca, 90210 (XML, Verbose, with 2010 census and reference geometry)

    Example 11 - PO Box 221 9355 Burton Way, Beverly Hills, ca, 90210 (CSV, Verbose, with 2010 census and reference geometry)



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_96.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 2010 census and reference geometry)
    - 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 2010 census and reference geometry)
    - 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 2010 census and reference geometry)
    - 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 2010 census and reference geometry)
    - 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 2010 census and reference geometry)
    - 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 2010 census and reference geometry)
    - 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 2010 census and reference geometry)
    - 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 2010 census and reference geometry)
    - will match to city Beverly Hills (smaller area = less geographic uncertainty = more accurate geocode)

Texas A&M University © 2022 · GeoInnovation Service Center · B-GSVCSWEB | Version-20240612.5 | Release-122
About Contact Careers Security Policy Privacy Policy