It’s a hunting day

Where the numbers come from

Every fact on this site traces to a free, public, authoritative source. Nothing is scraped from behind a paywall, and nothing about the regulations is filled in from memory.

National Weather Service

The forecast behind every score: air temperature, wind speed and direction, sky cover, precipitation, forecast snowfall, and active alerts, pulled per coordinate from the NWS gridpoint. It is the single largest input to the day’s conditions.

For a spot you mark yourself, your browser asks for a block of nine forecast cells around it and reads the spot’s own cell from the block, and reads the active alerts for the whole state, filtered to your county. The spot itself is never sent.

api.weather.gov →

NWS observation stations

Barometric pressure and its 3-hour tendency, read from the nearest reporting station where the gridpoint forecast carries no pressure. This drives the pressure factor, which matters to deer more before a front than after one.

USGS Elevation Point Query Service

Surface elevation at any coordinate, used for pin context and to help rank one tract against another.

USGS EPQS →

Terrain Tiles (Terrarium)

Elevation tiles from the Terrain Tiles set on the AWS Registry of Open Data, assembled by Mapzen from public elevation data including USGS 3DEP. The site reads about 40 km of them around every tract, and around any spot you mark, for the skyline that sets when the sun reaches and leaves the ground, and for the fall line the thermals follow.

Terrain Tiles →

MRLC / National Land Cover Database

The dominant land cover at a point (hardwood forest, cropland, wetland, brush), sampled across each tract to read its habitat, including the food-to-cover edge deer favor. Feeds the habitat portion of the land ranking.

MRLC NLCD →

US Census Bureau

County land area and internal-point coordinates, from the Census Gazetteer and TIGERweb. Land area turns a county’s deer harvest into a per-square-mile herd-density proxy; the centroids anchor the county and near-a-city pages.

Census Gazetteer →

Census county boundaries, 1:500,000

The Census Bureau’s 2023 county boundaries. A spot you mark is placed in its county in your browser, with its distance to the county line, so a spot near a line can ask which side it is on.

Cartographic boundary files →

FCC Area API

Resolves any coordinate to the county it falls in, so a dropped pin picks up the right regulations, harvest, and CWD status. It is also the check that confirms every public-land pin sits in the county we filed it under.

FCC Area API →

OpenStreetMap / Nominatim

When you type a place name into the scout tool, a single request to the public OSM geocoder turns it into a coordinate. A coordinate or your device location never leaves your browser; only a name you type is looked up.

Nominatim →

USDA Forest Service & state GIS

National-forest boundaries and acreage come from the USFS. Where a state publishes harvest by wildlife-management unit rather than county (Pennsylvania), each county’s unit is resolved against the authoritative PASDA GIS layer rather than guessed.

State wildlife agencies

Season dates, bag limits, legal shooting hours and Chronic Wasting Disease zones come from each state’s wildlife agency, and often from the state’s Administrative Code, which is usually the most current text. County deer-harvest totals come from the agency’s annual harvest report. Every value is tied to the page it was read from and the date it was checked, and the pages that use it link that source. The source pages are re-checked for changes, so an edited season date is caught. Where a rule hasn’t been confirmed, the page says so instead of calling a season open or closed.

Ohio: ODNR and the Ohio Administrative Code. Indiana: DNR. Kentucky: KDFWR. Maryland: MD DNR. West Virginia: WVDNR. Pennsylvania: the Game Commission.

Sunrise, sunset, legal shooting light, moon phase and illumination, and the solunar feeding periods are calculated locally from the coordinate and date using published astronomical formulas. The rut calendar is the site’s scoring model, anchored to the state agency’s peak breeding window where the agency publishes one. For a spot you check yourself, all of this is worked out in your browser.

  • We don’t aggregate user-submitted harvest reports or trail-camera photos.
  • We don’t invent conditions where there’s no real source. A spot you check gets the Weather Service forecast for the cell it sits in; where a source has nothing, the page says so instead of filling the gap.
  • We don’t license proprietary hunting-data feeds.
  • We don’t reorder anything editorial for advertising money. See the methodology.

itsafishingday.com data sources — the fishing site’s equivalent page, built on many of the same public APIs.