`aadt_near_point`

Pack: hpms-aadt · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/aadt_near_point for the schema, then POST the same URL with its arguments for the data.

US road traffic volume (AADT, annual average daily traffic) for road segments within a radius of a lat/lon, busiest first. Data: FHWA Highway Performance Monitoring System, per roadway section as reported by the state (not a counter reading). state is required. Returns route_id, functional class, AADT with single-unit and combination-truck splits, milepost range, data_year.

Parameters

Name	Type	Required	Description
`lat`	number	yes	Latitude, WGS84 decimal degrees.
`lon`	number	yes	Longitude, WGS84 decimal degrees (negative in the US).
`radius_m`	number	no	Search radius in metres (10-5000, default 500).

Example call

Arguments

{
  "lat": 34.0522,
  "lon": -118.2437,
  "state": "CA",
  "radius_m": 1000,
  "limit": 5
}

curl

curl -X POST https://gateway.pipeworx.io/hpms-aadt/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"aadt_near_point","arguments":{"lat":34.0522,"lon":-118.2437,"state":"CA","radius_m":1000,"limit":5}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('aadt_near_point', {
  "lat": 34.0522,
  "lon": -118.2437,
  "state": "CA",
  "radius_m": 1000,
  "limit": 5
});

Response shape

Field	Type	Description
`state`	string
`data_year`	number
`data_as_of`	string
`source`	string
`caveat`	string
`total_matching`	number
`returned`	number
`truncated`	boolean
`narrowing_hint`	string
`segments`	array

Full JSON Schema

{
  "type": "object",
  "properties": {
    "state": {
      "type": "string"
    },
    "data_year": {
      "type": "number"
    },
    "data_as_of": {
      "type": "string"
    },
    "source": {
      "type": "string"
    },
    "caveat": {
      "type": "string"
    },
    "total_matching": {
      "type": "number"
    },
    "returned": {
      "type": "number"
    },
    "truncated": {
      "type": "boolean"
    },
    "narrowing_hint": {
      "type": "string"
    },
    "segments": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "route_id": {
            "type": "string"
          },
          "f_system": {
            "type": "number"
          },
          "aadt": {
            "type": "number"
          },
          "aadt_single_unit": {
            "type": "number"
          },
          "aadt_combination": {
            "type": "number"
          },
          "county_id": {
            "type": "number"
          },
          "begin_point": {
            "type": "number"
          },
          "end_point": {
            "type": "number"
          },
          "data_year": {
            "type": "number"
          },
          "speed_limit": {
            "type": "number"
          },
          "through_lanes": {
            "type": "number"
          },
          "urban_id": {
            "type": "number"
          },
          "ownership": {
            "type": "number"
          },
          "f_system_name": {
            "type": "string"
          }
        },
        "additionalProperties": true
      }
    }
  },
  "additionalProperties": true
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

Connect to just the hpms-aadt pack

{
  "mcpServers": {
    "hpms-aadt": {
      "url": "https://gateway.pipeworx.io/hpms-aadt/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

aadt_near_point