Name: US Forest Service Boundaries
Creator: US Forest Service Enterprise Data Warehouse Basic Ownership

API access

Your AI client reaches US Forest Service Boundaries through one ParcelOps MCP endpoint, so there is no separate key to hold for it and no per-source client to write. Reaching it takes no credentials of your own.

Set up US Forest Service Boundaries in Claude, ChatGPT, or Cursor Get every fact on this page as JSON

Where it came from

PublisherUS Forest Service Enterprise Data Warehouse Basic Ownership

Sourcehttps://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_BasicOwnership_01/MapServer/0

API basehttps://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_BasicOwnership_01/MapServer

Docshttps://data.fs.usda.gov/geodata/edw/edw_resources/meta/S_USA.BasicOwnership.xml

Freshness and coverage

FreshnessScheduled · Follows the Forest Service Enterprise Data Warehouse publication.

Places coveredUnited States Forest Service-published basic ownership polygons

Time coveredNot declared

CredentialsNo credentials required

What this source cannot tell you

⚠ Anything outside United States Forest Service-published basic ownership polygons. A request past that edge comes back empty rather than approximated.
⚠ Which years it spans, because the covered period is not declared.
⚠ Anything US Forest Service Enterprise Data Warehouse Basic Ownership does not publish. ParcelOps returns this source as it stands and never fills a blank field from a different one.
⚠ No point match does not prove private ownership or absence of other public land.
⚠ The Forest Service states the layer must not be used to determine title, ownership, legal boundaries, jurisdiction, or restrictions.
⚠ PAD-US remains the broader multi-agency public-land inventory.

Methods (2)

A method is one call your agent can make against this source.

getBasicOwnershipAtLocation
read
Check one WGS84 point against the Forest Service Basic Ownership layer.
What you must providelatitudelongitude
Records returnedforest-service-basic-ownership-area
How to get more resultsnone
FreshnessScheduled (source-level)
Input schema
```
{
  "type": "object",
  "properties": {
    "latitude": {
      "type": "number",
      "minimum": -90,
      "maximum": 90
    },
    "longitude": {
      "type": "number",
      "minimum": -180,
      "maximum": 180
    }
  },
  "required": [
    "latitude",
    "longitude"
  ],
  "additionalProperties": false
}
```
- ⚠ Screening context only; not title, a boundary survey, jurisdiction, or a restriction determination.
getServiceInfo
read
Return the exact layer, metadata, access constraints, redundancy, and legal-use caveats.
FreshnessScheduled (source-level)
Input schema
```
{
  "type": "object",
  "properties": {},
  "required": [],
  "additionalProperties": false
}
```

Where this source is used

Land research
Parcel records, ground conditions, and what reaches the property line, for raw and rural land.
Data center siting
Power, water, transport, airspace, and hazard screening for a site before anyone signs anything.
Commercial real estate
Parcel and assessment records, building programs, and the entity on the other side of the deal.
Residential real estate
The parcel record, the housing programs that touch an address, and the conditions a buyer asks about.
Real estate law
Federal rule text, rulemaking dockets, party records, and the property facts a filing has to state.
Realtors and brokerages
The facts behind a listing, the programs a buyer may qualify for, and your own files in the same place.

US Forest Service Boundaries API and MCP server