SOURCE REGISTER
The source should stay visible.
ParkVisitCheck is useful only if a visitor can tell where a fact came from, when it was retrieved and what the source does not establish.
OFFICIALNational Park Service
Used for: Authenticated NPS Data API alerts and same-date events when a private API key is connected; official park Current Conditions and calendar links are always available.
Limits: NPS requires an API key and documents a default 1,000-request/hour limit. NPS also notes its API load can lag NPS.gov by about two hours. ParkVisitCheck never interprets a missing or unavailable API response as zero closures.
OFFICIALNOAA / National Weather Service
Used for: Official point metadata, hourly forecasts and active weather alerts for a representative point in each park, matched to the park-local visit date and selected hours.
Limits: NWS describes the API as open data free to use for any purpose, with reasonable rate limits. A point forecast is not continuous park coverage and does not establish trail, road, air-quality or activity safety.
USE & ATTRIBUTIONGovernment data, trademarks and third-party material
NPS states that material created by federal employees as part of official duties is generally public domain, while some photos, media and other material can carry third-party rights. ParkVisitCheck does not use the NPS Arrowhead or other protected NPS marks and makes no claim to original U.S. Government works.
NWS describes its API information as open data, free to use for any purpose, subject to reasonable rate limits. ParkVisitCheck caches upstream calls and keeps provider/source boundaries visible.
Source documentation reviewed October 6, 2026. NPS API defaults to 1,000 requests per hour per key and can lag NPS.gov by about two hours according to NPS developer guidance. APIs and government pages can change; retrieval failures remain visible instead of becoming empty-success claims.