TAMU GeoServices
About Services Pricing Support News
Log In Sign Up
  • Address Processing
  • Geocoding
  • Geocode Correction
  • Census Intersection
    • Platform Details
    • Interactive
    • Batch Processing
    • Web APIs
  • 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.01
    • v 3.01
    • v 2.96
    • v 2.95
    • v 2.94
    • v 2.93

Web Services

Services › Census Intersection › Web Services

The Texas A&M Geoservices point-in-polygon Census Intersection 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.

API Version - 3.01

Available API Endpoints


API #1 - .Net Point-In-Polygon Census Intersction Web Service


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

    https://geoservices.tamu.edu/Services/CensusIntersection/WebService/CensusIntersectionWebService_V03_01.asmx


API #2 - HTTP Point-In-Polygon Census Intersction Web Service


  • API that can be used from scripts and http
  • API URL

    https://geoservices.tamu.edu/Services/CensusIntersection/WebService/CensusIntersectionWebServiceHttp_V03_01.aspx?

    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 3.01 3.01
    censusYear true the requested year of census data 2010 1990, 2000, 2010
    lat true the latitude of the input coordinate 34.0726207996348 double
    lon true the longitude of the input coordinate -118.397965182076 double
    s false the abbreviation of the state of the input CA text string
    format false output format csv csv, tsv, xml
    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 3.01
    2 Transaction Id true Query Id Unique Id
    3 Census Year true Year of the census data returned NineteenNinety, TwoThousand, TwoThousandTen, TwoThousandTwenty, AllAvailable
    4 Census Block true Census block value for the output point
    5 Census Block Group true Census block group value for the output point
    6 Census Tract true Census tract value for the output point
    7 Census Place Fips true Census place fips value for the output point
    8 Census MCD Fips true Census minor civil division fips value for the output point
    9 Census MSA Fips true Census metropolitan statistical area fips value for the output point
    10 Census CBSA Fips true Census core base statistical area fips value for the output point
    11 Census CBSA Micro true Census core base statistical area micropolitan flag for the output point
    12 Census MetDiv Fips true Census metropolitan division fips value for the output point
    13 Census County Fips true Census county fips value for the output point
    14 Census State Fips true Census state fips value for the output point
    15 Time Taken true Processing time Milliseconds
  • API Examples

    Example 1 - 34.0726207996348, -118.397965182076, CA (CSV, 2010)

    Example 2 - 34.0726207996348, -118.397965182076, CA (XML, 2000)

    Example 3 - 34.0726207996348, -118.397965182076 (CSV, 2010)

    Example 4 - 34.0726207996348, -118.397965182076 (XML, 2010)

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