BTS National Transportation Atlas Infrastructure API

What you can build

Official aviation facilities, rail lines/nodes/yards/intermodal terminals, principal-port polygons and National Bridge Inventory points. Preserve native identifiers, codes, sentinel values, country coverage and independent source dates. Geodesic proximity supports screening; it does not establish road/siding access, freight service, terminal capacity or heavy-haul clearance. Port tonnage refers to CY2023 and bridge inventory to June 2025. Use this dataset as a sourced input to an application, analytical model or retrieval tool. Retain its native dimensions when joining it with your own records.

Query BTS National Transportation Atlas Infrastructure

The example below is a real bounded request against the available release. Replace the environment variable with your server-side API credential. Review endpoint parameters and response schemas before changing selectors.

curl --fail --get "https://api.geoamcan.com/v1/transportation/infrastructure?layer=airports&source_id=1&include_details=True&include_geometry=True&limit=1" \
  -H "Authorization: Bearer $GEOAMCAN_API_KEY"

Saved response excerpt

{
  "requested_area": {
    "layer": "airports",
    "source_id": 1,
    "native_id": null,
    "q": null,
    "country": null,
    "state": null,
    "lat": null,
    "lon": null,
    "radius_m": 10000,
    "bbox": null,
    "include_geometry": true,
    "include_details": true
  },
  "data": [
    {
      "layer": "airports",
      "source_id": 1,
      "native_id": "00103.",
      "name": "ABBEVILLE MUNI",
      "country": "US",
      "state": "AL",
      "geometry_status": "source_geometry",
      "located": true,
      "distance_m": null,
      "source_attributes": {
        "CTA": "",
        "TPA": null,
        "CITY": "ABBEVILLE",
        "ELEV": 468.3,
        "FSS_ID": "ANB",
        "ACREAGE": 36,
        "ARPT_ID": "0J0",
        "ICAO_ID": "",
        "LAT_DEG": 31,
        "LAT_MIN": 36,
        "LAT_SEC": 6.193,
        "SITE_NO": "00103."
      }
    }
  ],
  "availability": {
    "status": "available",
    "layer": {
      "layer": "airports",
      "title": "Aviation Facilities",
      "records": 19434,
      "repaired": 0,
      "countries": [
        {
          "country": "AI",
          "records": 1
        }
      ],
      "unlocated": 0,
      "source_url": "https://services.arcgis.com/xOi1kZaI0eWDREZv/arcgis/rest/services/NTAD_Aviation_Facilities/FeatureServer/0",
      "geometry_type": "esriGeometryPoint",
      "reference_period": {
        "native_effective_dates": [
          "2026/10/29"
        ]
      },
      "source_description": "The Aviation Facilities dataset is updated every 28 days from the Federal Aviation Administration (FAA) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). The Aviation Facilities dataset is a geographic point database of all official and operational aerodromes in the United States and U.S. Territories. Attribute data is provided on the physical and operational characteristics of the aerodrome, current usage including enplanements and aircraft operations, congestion levels and usage categories. This geospatial data is derived from the FAA's National Airspace System Resource Aeronautical Data Product. For more information about these data, please visit: https://www.faa.gov/air_traffic/flight_info/aeronav/Aero_Data/NASR_Subscription. A data dictionary, or other source of attribute information, is accessible at https://doi.org/10.21949/1529011",
      "source_revision_ms": 1793733308000,
      "source_revision_utc": "2026-11-03T19:15:08+00:00"
    },
    "confirmed_site_access": false
  },
  "snapshot": {
    "bts-ntad": {
      "release_id": 125,
      "release": "BTS NTAD per-layer snapshots revision 60063582f1e1",
      "fingerprint": "ec1081cfd40dd2999936764ed609bd75"
    }
  },
  "returned_count": 1,
  "complete": true,
  "next_offset": null,
  "limitations": [
    "BTS NTAD infrastructure screening, with independently dated FAA, FRA, USACE and FHWA layers. Rail includes US, Canada and Mexico. Airports include multiple aerodrome types, not only commercial passenger airports. Ports are source polygons; yards are source linework. Nearness is geodesic distance to published geometry, not road travel or verified driveway/siding access, service agreements, capacity, current operating status or heavy-haul clearance. NBI codes, missing values and sentinel values remain native; a bridge record is not a route clearance. Port tonnage is CY2023; bridge inventory is June 20, 2025. Source revision timestamps are separate from observation dates."
  ],
  "source_attribution": {
    "bts-ntad": "US DOT / BTS NTAD; FAA, FRA, USACE and FHWA — https://www.bts.gov/ntad"
  },
  "metric_definitions": {
    "distance_m": "Geodesic distance to the source point, line or polygon; zero inside a port polygon. Not driving distance or confirmed infrastructure access.",
    "native_id": "Source native identifier; bridge keys combine native state and structure number. Object IDs require the release and layer.",
    "state": "Native source state representation: abbreviations where published; NBI uses source state codes. No inferred state for layers without it.",
    "country": "Native source country code when published; null when absent. No inferred country from a nearby point.",
    "source_attributes": "Original named fields and raw numeric/code/sentinel values; definitions are available from the layers endpoint with include_fields=true."
  }
}

Captured 2026-11-07. Excerpt omits pagination credentials and may shorten nested records. Download verified source responses.

Coverage and interpretation

BTS NTAD infrastructure screening, with independently dated FAA, FRA, USACE and FHWA layers. Rail includes US, Canada and Mexico. Airports include multiple aerodrome types, not only commercial passenger airports. Ports are source polygons; yards are source linework. Nearness is geodesic distance to published geometry, not road travel or verified driveway/siding access, service agreements, capacity, current operating status or heavy-haul clearance. NBI codes, missing values and sentinel values remain native; a bridge record is not a route clearance. Port tonnage is CY2023; bridge inventory is June 20, 2025. Source revision timestamps are separate from observation dates.

The active release shown here is a catalog snapshot. Check the live catalog and response provenance for current readiness. The underlying public source and Geoamcan access terms are separate; consult the source’s licensing and attribution requirements.

Source and methodology

Source: US DOT / BTS; FAA, FRA, USACE and FHWA. Geoamcan is an independent API provider, with no agency affiliation or endorsement. Read our data methodology for source handling, geographic joins and update practices.

Related data

• FDIC Summary of Deposits
• BLS Occupational Employment and Wage Statistics
• CDC/ATSDR Social Vulnerability Index
• NCES School and Postsecondary Locations