Count segments in a geometry

StreetLight Advanced Traffic Counts API

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
geometry
required

Geometry used in a query, provided as one of the following geometry types:

  • segment_id: An array of segment IDs
  • radius: A radius around a point
  • nearest: Segments nearest to a point
  • polygon: A bounding polygon
  • tract_id, zip_id, blockgroup_id, taz_id,: IDs for various local aggregations (US-only)
  • places_2020: 7-digit FIPS code from the 2020 U.S. census, where the first 2 digits are the state code and the last 5 digits are the place code. (US-only)
  • dissemination_area_id, census_division_id, census_subdivision_id: IDs for various local aggregations (CAN-only)
  • osm_id: An array of OSM IDs
string
enum
required
Defaults to us
Allowed:
string
enum
required
Defaults to vehicle
Allowed:
string
enum

The data source that will be used. Check the Available Metrics and Date Ranges for each data source. Requests that do not specify this parameter will use lbs_plus. For more information, see What are data sources? .

Allowed:
integer
2000 to 2099

Specify the year for which you want metrics to get the relevant geometry; this ensures that the segments in the road network used are consistent with the year you are querying.

osm_vintage
array of integers

The OpenStreetMap (OSM) snapshot that defines segments queried, where 202302 is February 2023 and 202501 is January 2025. Only required for the agps data source.

  • Use 202302 for metrics from December 2024 and earlier.
  • Use 202501 for metrics from January 2025 and later.
  • Use both vintages for a date range across 2024 and 2025.
osm_vintage
roadway_classification
object

If specified, only segments with the given OSM roadway classifications will be returned.

Responses

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json